[PATCH build] Implement auto-clone.

[Gaetan Nadon]

On Mon, 2010-09-20 at 21:25 -0400, Trevor Woerner wrote:

> This was done within the existing functionality of build.sh, so the
> list doesn't need to be removed from build.sh or stored externally to
> it in any way. Just a small patch to the existing build.sh is all that
> is required.
> 

So as long as it is possible to have several modules list and chose
which one to build.

A few examples here, out of my head:

- a list of modules to build release 7.5, 7.6, etc...
- a list of modules to build xserver with it's dependencies
- a list of modules to build on the MAC (which is significantly
different)

If you look at the tinderbox build farm, you will notice each build
machine has a different
list of modules to build. It is easy to imagine that several developers
could each desire 
to write their own custom modules list and expect build.sh to use it.

This opens up new possibilities. One can write a custom script that uses
one or many of the modules list
to perform whatever task the developer has in mind.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100920/888be566/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100920/888be566/attachment.pgp>