gecko/python
Gregory Szorc b2f7410078 Bug 968245 - Regenerate mozinfo.json as part of build backend; r=glandium
Previously, mozinfo.json was only generated as configure time.
Unfortunately, the build dependencies did not capture this relationship.
So, changes to mozinfo.py (or any supporting Python file) would not
trigger mozinfo regeneration, possibly leading to clobbers.

This patch moves mozinfo.json generation from the body of config.status
to the build backend. We had to add an AC_SUBST so the build config
knows when to build mozinfo.json. This was needed because js/src's build
system doesn't define all the required variables to create mozinfo.json.
Once js/src's configure/config.status is merged into the main build
config tree, this workaround can be removed.

While we were here, mozinfo.json was made to have consistent output and
its changes are now viewable with config.status --diff.

--HG--
extra : rebase_source : e91ed7173efdcde5831ae13b1ce69fc3cf32af97
extra : amend_source : 1610bcc6c3af764fdf685ee76188fb211bd828de
2014-02-05 20:53:47 -08:00
..
blessings
codegen
configobj
lldbutils Fix error in lldb string serialiation; no bug. (DONTBUILD, NPOTB) 2014-02-17 15:22:59 +11:00
mach Bug 909522 - Run mach's unit tests as part of make check; r=mshal 2014-01-09 11:20:41 -08:00
mock-1.0.0
mozboot Bug 950107 - Support ALL_PROXY in bootstraper; r=gps 2014-02-05 13:10:00 -08:00
mozbuild Bug 968245 - Regenerate mozinfo.json as part of build backend; r=glandium 2014-02-05 20:53:47 -08:00
mozversioncontrol/mozversioncontrol Bug 941833 - mach mercurial-setup should define host fingerprints during repo operations; r=nalexander 2013-11-21 12:19:32 -08:00
psutil
virtualenv
which
mach_commands.py Bug 952280 - mach python commands now use virtualenv APIs; r=mshal 2013-12-19 13:48:37 -08:00
Makefile.in Bug 909522 - Run mach's unit tests as part of make check; r=mshal 2014-01-09 11:20:41 -08:00
moz.build Bug 939367 - Allow Sphinx docs to come from all over the tree; r=glandium 2013-11-20 12:37:22 -08:00
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