зеркало из https://github.com/mozilla/gecko-dev.git
eafe4905bb
When determining the path of a possible mozilla-central checkout, bootstrap currently considers the existence of a `.git` directory as sufficient proof that the containing directory is a git checkout. Unfortunately, if you happen to execute standalone bootstrap from a git checkout of something else, you're gonna have a bad time. To prevent this, check for the existence of a moz.configure file. This is not an ideal proof, but it is better than what we currently have. |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozversioncontrol/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