<!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 Mon, 2010-09-20 at 21:25 -0400, Trevor Woerner wrote: <BLOCKQUOTE TYPE=CITE> <TT>This was done within the existing functionality of build.sh, so the</TT> <TT>list doesn't need to be removed from build.sh or stored externally to</TT> <TT>it in any way. Just a small patch to the existing build.sh is all that</TT> <TT>is required.</TT> </BLOCKQUOTE> 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. </BODY> </HTML>