зеркало из https://github.com/mozilla/gecko-dev.git
e6e627c61f
The former is broken because of a lack of a app.mozbuild file and has been broken for years. The latter doesn't do anything useful outside --enable-project=extensions because all the subdirectories of extensions/ are already covered by other flags (or always used): - auth, via --enable-negotiateauth (default on) - permissions, always - pref, via --enable-pref-extensions (default on) - spellcheck, always - universalchardet, via --enable-universalchardet (default on) Also, nothing sets MOZ_EXTENSIONS_DEFAULT anymore. Differential Revision: https://phabricator.services.mozilla.com/D133970 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| 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