[PATCH build] Implement auto-clone.

[Trevor Woerner]

On Mon, Sep 20, 2010 at 10:33 PM, Gaetan Nadon <memsize at videotron.ca> wrote:
> This opens up new possibilities.

The last time I tried to work on too many things at once they got
applied in an order I wasn't expecting so reports came back my patches
wouldn't apply (which doesn't make me look so good). So this time I'll
just wait patiently for things to be applied before submitting new
patches.

So far the list of patches I have ready include:

- a way of passing any arbitrary "git" or "make" command from the
cmdline to apply to all modules being built
- centralizing the list-only, no-stop, and one-shot logic (I'd still
like to switch the "no-stop" to "keep-going" the way "make" does)
- implement auto-configuration (the script can easily determine when
configuration needs to be called and can do it automatically, the user
should have to specify a cmdline arg if they explicitly want it done
again, rather than specify an argument to not have it reconfigure each
time it builds)
- implement auto-cloning (under certain situations, but not on by default)
- this new "provide a list of modules to build" functionality which
will build them in the correct order irrespective of the order in
which they're given. TODO: based on the feedback I'll probably want to
also allow pseudo-module names which would include various related
modules as a group

These patches are ready, all that remains is the inevitable style and
portability discussions :-D
(not to mention additional testing)