зеркало из https://github.com/mozilla/gecko-dev.git
848c9b1c1e
All that is really required for this ticket is to invoke |mach android archive-geckoview| after |mach package| in the right place. But it's actively unhelpful to have this magic in mozharness -- especially since the documentation in `locales.rst` is subtly incorrect (the environment variables and Make variables don't quite work as written). So this commit adds a Mach command to do the actual work and replaces most of the mozharness magic with that command. Since the l10n Make targets check out the l10n HG repositories locally, this basically Just Works without the mozharness checkout steps when developing locally. Differential Revision: https://phabricator.services.mozilla.com/D12455 --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