Remove "./mach vendor python [package]", mandate that package is in "requirements.in"
Categories
(Firefox Build System :: Mach Core, task)
Tracking
(firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: mhentges, Assigned: mhentges)
Details
Attachments
(1 file)
This ensures that we have pinned packages and that the package is compatible with the other ones we have pinned.
This doc will need to be updated.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
./mach vendor python <package>
was already adding its new package
to requirements.txt
, so we were getting full resolver support, which
is good. However, it caused our requirements.in
file to start
getting out-of-date, and made it harder to identify the top-level
dependencies.
Arguably, we could have ./mach vendor python <package>
automatically
update requirements.in, too, but then we need to solve the edge cases,
such as "What if the package is already in requirements.in
? What if
that existing item had a different version?"
The hardest part of updating requirements.in
is finding it, so I've
also modified the ./mach vendor python
help text to make it more
identifiable.
Comment 3•3 years ago
|
||
bugherder |
Description
•