(In reply to Andrew Halberstadt [:ahal] from comment #1) > I think the list of packages in `mach.txt` might *actually be* what it currently needs. That's my understanding. Though, we don't have anything that proves that the list of dependencies in there is the current 'minimal' set. At one point or another, all of the dependencies listed in there were required for baseline `mach`, but there's no easy way to tell if something changed and any particular dependency is or is not longer required.(In reply to Andrew Halberstadt [:ahal] from comment #0) > However it also includes all of the vendored packages under `third_party/python`. I don't think this is 100% correct. Most things from `third_party/python` are included in `mach.txt`, but not all. Some of the packages specified in `build.txt` and `python-tests.txt` are in `third_party/python`, but are not included in `mach.txt`.
Bug 1808732 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Andrew Halberstadt [:ahal] from comment #1) > I think the list of packages in `mach.txt` might *actually be* what it currently needs. That's my understanding. Though, we don't have anything that proves that the list of dependencies in there is the current 'minimal' set. At one point or another, all of the dependencies listed in there were required for baseline `mach`, but there's no easy way to tell if something changed and any particular dependency is or is not longer required. (In reply to Andrew Halberstadt [:ahal] from comment #0) > However it also includes all of the vendored packages under `third_party/python`. I don't think this is 100% correct. Most things from `third_party/python` are included in `mach.txt`, but not all. Some of the packages specified in `build.txt` and `python-tests.txt` are in `third_party/python`, but are not included in `mach.txt`.
(In reply to Andrew Halberstadt [:ahal] from comment #1) > I think the list of packages in `mach.txt` might *actually be* what it currently needs. That's my understanding. Though, we don't have anything that proves that the list of dependencies in there is the current 'minimal' set. At one point or another, all of the dependencies listed in there were required for baseline `mach`, but there's no easy way to tell if something changed and any particular dependency is or is no longer required. (In reply to Andrew Halberstadt [:ahal] from comment #0) > However it also includes all of the vendored packages under `third_party/python`. I don't think this is 100% correct. Most things from `third_party/python` are included in `mach.txt`, but not all. Some of the packages specified in `build.txt` and `python-tests.txt` are in `third_party/python`, but are not included in `mach.txt`.