forked from mirrors/gecko-dev
9b7eee2c37
On POSIX platforms there can be `lib` and `lib64` for `site-packages`. On Fedora35 once a virtualenv is created, `lib64` is a symlink of `lib`. Since we can determine what these paths will be before the virtualenv is created, `realpath` has different results before/after, which is problematic for our `pthfile`. Since we only care about resolving the symlink in the prefix (to keep it in line with the `topobjdir`, we can simply only `realpath` that and disregard that there's a symlink between `lib` and `lib64`, which makes our `pthfile` that's created and expected always the same on all platforms. Differential Revision: https://phabricator.services.mozilla.com/D162136 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| 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