2023-11-19 15:30:34 +00:00
|
|
|
vendored:testing/web-platform/tests/tools/third_party/h2/src
|
|
|
|
|
vendored:testing/web-platform/tests/tools/third_party/hpack/src
|
Bug 1808732 - Move various dependencies out of the `mach` site to either the specific site they're needed in (like `build, or `lint`), and/or to `common` r=firefox-build-system-reviewers,glandium
Now that we selectively load command modules, and activate the command
virtualenv much earlier in the mach process, a lot of the module
dependencies specified in `mach.txt` are no longer necessary there. With
their removal from `mach.txt` they will no longer be automatically
inherited by every site, which reduces potential dependency conflicts
for specific sites.
The `common` site still effectively has the same set of dependencies.
This is the default site that all commands use unless otherwise
specified. Most commands use this site, and going through every command
and seeing if a dependency is or isn't needed, then deciding if or if
not to create a new site for that command made sense was too time
consuming to do here.
Essentially the idea here going forward is that if you're trying to
add/update a new dependency to a command that is currently defaulting to
the `common` site and there is a conflict with one of the dependencies
in `common` you can move your command to a new site specifically for
your command, and you will have the minimal possible set of dependencies
a mach command can have, improving the odds that you can add the
module(s) you need for your command.
Depends on D180500
Differential Revision: https://phabricator.services.mozilla.com/D180501
2023-07-25 00:24:53 +00:00
|
|
|
vendored:testing/web-platform/tests/tools/third_party/html5lib
|
2023-11-19 15:30:34 +00:00
|
|
|
vendored:testing/web-platform/tests/tools/third_party/hyperframe/src
|
Bug 1808732 - Move various dependencies out of the `mach` site to either the specific site they're needed in (like `build, or `lint`), and/or to `common` r=firefox-build-system-reviewers,glandium
Now that we selectively load command modules, and activate the command
virtualenv much earlier in the mach process, a lot of the module
dependencies specified in `mach.txt` are no longer necessary there. With
their removal from `mach.txt` they will no longer be automatically
inherited by every site, which reduces potential dependency conflicts
for specific sites.
The `common` site still effectively has the same set of dependencies.
This is the default site that all commands use unless otherwise
specified. Most commands use this site, and going through every command
and seeing if a dependency is or isn't needed, then deciding if or if
not to create a new site for that command made sense was too time
consuming to do here.
Essentially the idea here going forward is that if you're trying to
add/update a new dependency to a command that is currently defaulting to
the `common` site and there is a conflict with one of the dependencies
in `common` you can move your command to a new site specifically for
your command, and you will have the minimal possible set of dependencies
a mach command can have, improving the odds that you can add the
module(s) you need for your command.
Depends on D180500
Differential Revision: https://phabricator.services.mozilla.com/D180501
2023-07-25 00:24:53 +00:00
|
|
|
vendored:testing/web-platform/tests/tools/third_party/pywebsocket3
|
|
|
|
|
vendored:testing/web-platform/tests/tools/third_party/webencodings
|
|
|
|
|
vendored:testing/web-platform/tests/tools/wptrunner
|
|
|
|
|
vendored:testing/web-platform/tests/tools/wptserve
|
2023-10-23 13:25:07 +00:00
|
|
|
pypi:tcfetch==0.4.0
|
|
|
|
|
pypi:wpt-interop==0.2.0
|