зеркало из https://github.com/mozilla/gecko-dev.git
347044e672
reftest and crashtest manifests can now be added to the build configuration via REFTEST_MANIFESTS and CRASHTEST_MANIFESTS, respectively. The master manifest files have been added to layout/moz.build. This patch enables the deprecation of master reftest manifests but stops short of doing it. In the future, we could declare reftest and crashtest manifests in their nearest moz.build file and generate the master manifest (consisting of a bunch of "include" directives) as part of config.status. --HG-- extra : rebase_source : 3503f787b14b24c38daf577a710e67b583476858 extra : histedit_source : 21e55b3d28ee83afb47f3f779251a13c2a90db5f |
||
---|---|---|
.. | ||
blessings | ||
codegen | ||
configobj | ||
jsmin | ||
lldbutils | ||
mach | ||
mock-1.0.0 | ||
mozboot | ||
mozbuild | ||
mozversioncontrol/mozversioncontrol | ||
psutil | ||
virtualenv | ||
which | ||
Makefile.in | ||
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: * 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