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

[Trevor Woerner]

On Wed, Oct 6, 2010 at 3:59 PM, Gaetan Nadon <memsize at videotron.ca> wrote:
> On Tue, 2010-10-05 at 17:35 -0400, Trevor Woerner wrote:
>> 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.

I agree... but to be honest I think the more pertinent question is:
why would a user be trying to build unknown sub-projects? Shouldn't
all the projects be known to the build.sh script? Should the script
even support unknown projects? If a new project is being added to the
X.Org family, shouldn't it be patched into the build script the way
the others are already?

> 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.

I'll think about ways to build unknown projects in whatever order
they're specified, but I really think projects that aren't known to
the script shouldn't be supported at all.

Let's say you're working on a new project to be added:
"xf86-video-gaetan". I would hope that as part of your development you
would determine where in the sub-project list it should be built, add
it to the build.sh script, then submit it when you send in the patches
for the rest of your work. In other words, if you're working on
something locally that isn't yet available publicly, just patch your
build.sh to support your new project, then send it in when the rest of
your work gets accepted.

I was under the impression one of the most important things the
build.sh script provides for the user is the ability to build all the
sub-projects of X.Org in the correct order. So in that case no matter
how the user supplies the list of projects they want built, the script
should build them in the order it knows will work correctly. I think
that's important to retain; more important than supporting
sub-projects which aren't known to the script.

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

Yes, typo. Sorry.