зеркало из https://github.com/mozilla/gecko-dev.git
7fa84b1acd
We don't actually ship XPT files anymore, but it's still useful for the packager code to handle old Firefox versions. But for that, we don't really need the complexity of "linking" XPT files in a single unit per directory. We can just as well keep the XPT files intact, as long as we retain individual `interfaces` manifest entries for each. And since those entries used to be all merged into one, we now instead group them all together in manifests (which also happens to make it easier on unit test changes). Differential Revision: https://phabricator.services.mozilla.com/D5221 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| l10n/fluent_migrations | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| README | ||
| mach_commands.py | ||
| moz.build | ||
README
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025