<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Wed, 2010-09-22 at 11:57 -0400, Trevor Woerner wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">That sounds okay to me. Note that if you invoke "build.sh -L" it will</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">output this list for you. If that a useful feature? Could that feature</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">be used by other build systems?</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
<BR>
I am not sure, I have the impression you think there is only one list of modules (as I once did).<BR>
So, yes, the -L will output the list. Where does that list comes from? It's hard coded in build.sh.<BR>
Is that list useful to everyone? No. Are there many valid and useful lists out there? Yes.<BR>
Can I start a build using one of the many lists I have in mind? No. <BR>
<BR>
That's the feature I have in mind. Even better if the modules lists can be in a format that other tools<BR>
can understand (data integration).<BR>
<BR>
It took me quite a while to figure out that there is no "fixed and cast in stone" list of modules in xorg.<BR>
Compare the number of modules in the freedesktop repositories with the list in build.sh<BR>
and the lists in tinderbox. That will give you an idea of the many ways to slice and dice xorg.<BR>
<BR>
I'll have a look at your patch later today. <BR>
<BR>
Thanks!<BR>
<BR>
Gaetan<BR>
<BR>
</BODY>
</HTML>