[PATCH modular] Process a user-supplied list of module/components.

[Gaetan Nadon]

On Tue, 2010-10-05 at 17:35 -0400, Trevor Woerner wrote:

> From: Trevor Woerner <twoerner at gmail.com>
> 
> New feature.
> 
> Using the new "--modlist <file>" option, the user can specify a file
> which
> contains a list of the module/component items to process. The file can
> contain
> blank lines and comment lines which start with a hash mark (#).
> 
> The list can be in any arbitrary order, the script will process them
> in the
> correct dependency order. The script can't figure out what the
> dependencies
> are, it expects the list to contain the necessary module/component
> items.
> 
> The script attempts to process any unknown items at the end of the
> known list.

Any reasons why this is better for the user? I think 99 out of a 100
users will expect the module
to be build in the order specified in the provided list.
If it is not doable, we should have a way for users to quickly find out
it's the way it works so
he does not waste time debugging.

> 
> Suggested usage:
>     1. run script go generate the list of known items, redirecting to
> a file

                                   || type? "to" prehaps

>         $ util/modular/build.sh -L > modulefile
>     2. edit file, commenting or deleting out unnecessary items
>     3. run the build off the list:
>         $ util/modular/build.sh $PREFIX --modfile modulefile ...
> 


This is great stuff. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101006/4cbda1af/attachment.htm>
-------------- 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/20101006/4cbda1af/attachment.pgp>