forked from mirrors/gecko-dev
a1d60ae1c0
Thunderbird has a separate .cargo/config.in file at comm/rust/.cargo/config.in that cargo vet needs to use. It's set in the config variable MOZ_OVERRIDE_CARGO_CONFIG. Additionally, cargo vet's working directory needs to be `comm/rust`. This change has no effect on how `mach cargo vet` works for Firefox. To verify, `mach cargo vet suggest --verbose debug` shows the supply-chain path in use. Differential Revision: https://phabricator.services.mozilla.com/D205896 |
||
|---|---|---|
| .. | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| sites | ||
| 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