I took a stab at this and it might be blocked on bug 1695312 (which in turn depends on bug 1388894). I think the list of packages in `mach.txt` might *actually be* what it currently needs. This is because when you invoke `mach`, it'll import every `mach_commands.py` file which means that each of the imports at the top of those files must be importable from the `mach` scope. So we need to get to the point where we can run mach without importing every single `mach_commands.py` file. Note that there are excellent reasons for us to do this anyway, e.g much less of a performance hit when running `mach`.
Bug 1808732 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I took a stab at this and it might be blocked on bug 1695312. I think the list of packages in `mach.txt` might *actually be* what it currently needs. This is because when you invoke `mach`, it'll import every `mach_commands.py` file which means that each of the imports at the top of those files must be importable from the `mach` scope. So we need to get to the point where we can run mach without importing every single `mach_commands.py` file. Note that there are excellent reasons for us to do this anyway, e.g much less of a performance hit when running `mach`.