зеркало из https://github.com/mozilla/gecko-dev.git
6bfaa82f51
Fennec has a value of OMNIJAR_NAME that contains a directory, contrary to other platforms, and relies in post-packaging, pre-unpacking steps to accommodate with the difference. With this change, we just make the packaging and unpacking steps aware of this setup, and make allow them to pack/unpack resources in foo/ under foo/$OMNIJAR_NAME, whether $OMNIJAR_NAME is a file name or a path. This will, further down the road, allow the packager code to handle jar logs from PGO instrumentation without munging them. Differential Revision: https://phabricator.services.mozilla.com/D21654 --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