gecko/python/mach
Gregory Szorc 989dd1896e Bug 1139100 - Apply proper checking for command existence; r=ahal
Previously, we raised errors attempting to register a mach sub-command
if the parent command was not defined on the Registrar. This broke B2G
because its mach command Registrar imposes restrictions on which
commands it exposes. Commands there were not getting registered on the
Registrar, leading mach to give a false positive that the parent command
was never defined.

We change the verification logic to take present but unregistered
commands into consideration and to skip registering sub-commands if the
parent isn't present in the Registrar.
2015-03-04 11:03:07 -08:00
..
docs Bug 1115278 - Fix mach documentation issues; r=glandium 2014-12-24 10:26:34 -08:00
mach Bug 1139100 - Apply proper checking for command existence; r=ahal 2015-03-04 11:03:07 -08:00
bash-completion.sh
README.rst Bug 1108399 - Move mach docs into sphinx; r=ahal 2014-12-07 10:40:19 -08:00
setup.py Bug 957856 - Synchronize mach with upstream repository; r=ahal 2014-01-08 16:14:39 -08:00

====
mach
====

Mach (German for *do*) is a generic command dispatcher for the command
line.

To use mach, you install the mach core (a Python package), create an
executable *driver* script (named whatever you want), and write mach
commands. When the *driver* is executed, mach dispatches to the
requested command handler automatically.

To learn more, read the docs in ``docs/``.