mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-27 04:38:02 +00:00
9ca9b3074c
We have very few directories where we have SOURCES declared that are not part of a library or program in some way. In fact, there is only one where it is legitimate because we only use the object file (build/unix/elfhack/inject). Others are the result of moz.build control flow (see e.g. netwerk/standalone), and we end up building more objects than we need to. There are other cases where we need objects without actually linking them anywhere, but there are other sources in the same directory, and a corresponding Linkable is emitted. And in fact, the only case I knew about (media/libvpx), doesn't use such objects since bug 1151175.
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 ## pyyaml | pystache Used in taskcluster related mach commands to update download from github and remove .git and tests. Then run tests in taskcluster/tests/