[mozproxy] Use mozbuild's tooltool in mozproxy
Categories
(Testing :: Mozbase, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: alexandrui, Unassigned, Mentored)
References
Details
Mozproxy's utils.py is currently using a subprocess for teching files and we want to replace it with mozbuild's fetch_files.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Tarek, maybe we could change the purpose of this bug to use tooltool canonical.
Comment 2•5 years ago
|
||
I think step 1 is to have the tooltool on github vendored in m-c, and then we can use it here. So I would sync with Ben to see when we want to go ahead and add it in our vendored libs in /python
Comment 3•5 years ago
|
||
(In reply to Tarek Ziadé (:tarek) from comment #2)
I think step 1 is to have the tooltool on github vendored in m-c, and then we can use it here. So I would sync with Ben to see when we want to go ahead and add it in our vendored libs in /python
We already have it in /python, actually: https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/action/tooltool.py
Does that work for this case?
Reporter | ||
Comment 4•5 years ago
|
||
As I understood, the purpose of this was to avoid having n hardcopies of it, but to import it from one single place wherever we want to use it. I presume tarek is talking about adding it as dependency. Am I right, tarek?
Comment 5•5 years ago
|
||
https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/action/tooltool.py is not mozilla-tooltool-client , I was talking about having a vendored version of https://github.com/mozilla-releng/tooltool/blob/master/client/setup.py
so we don't rely on a copy that is somewhere in another project, but use a "mozilla-tooltool-client " release.
Comment 6•5 years ago
|
||
(In reply to Tarek Ziadé (:tarek) from comment #5)
https://searchfox.org/mozilla-central/source/python/mozbuild/mozbuild/action/tooltool.py is not mozilla-tooltool-client , I was talking about having a vendored version of https://github.com/mozilla-releng/tooltool/blob/master/client/setup.py
so we don't rely on a copy that is somewhere in another project, but use a "mozilla-tooltool-client " release.
At the moment, copying tooltool.py
is the supported way to vendor :), which is what the linked version is (at least, it's supposed to be). I want to change that later, but it's where we are now.
I wouldn't be opposed to an additional copy in the tree in https://searchfox.org/mozilla-central/source/third_party/python as a more officially vendored copy, if that's what you mean though.
Comment 7•5 years ago
|
||
At the moment, copying tooltool.py is the supported way to vendor
ok. if we do this, can we at least change the version number that is in tooltool.py ?
I wouldn't be opposed to an additional copy in the tree in https://searchfox.org/mozilla-central/source/third_party/python as a more officially vendored copy, if that's what you mean though.
that sounds good. my goal is mostly to reduce the number of occurences of tooltool.py in mozilla-central to a single one.
and maybe change the documentation that says it should be copied around, and propose to use that canonical version everywhere.
Comment 8•5 years ago
|
||
Comment 9•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Updated•3 years ago
|
Description
•