<!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 14:55 -0400, Trevor Woerner wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#737373">> What we could consider though is a minimal or default set that</FONT></TT><BR>
<TT><FONT COLOR="#737373">> just gets the basic five or six modules that covers 99% of our testers</FONT></TT><BR>
<TT><FONT COLOR="#737373">> (xserver, evdev, intel, etc.).</FONT></TT><BR>
<BR>
<TT><FONT COLOR="#1a1a1a">What would you like to see as an interface?</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
This is a good opportunity to make a little publicity about the "module set" feature<BR>
I have been thinking about. You will never get an agreement on what the minimal default set should be. <BR>
<BR>
There should be an arbitrary number of module sets and an option to auto-clone modules<BR>
missing on disk. That would make everybody happy.<BR>
<BR>
The first step is to separate the modules list from build.sh. This means build.sh has no module list at all.<BR>
Users can create module sets in addition to the one that came out of build.sh.<BR>
<BR>
It won't be as easy as it sounds. The module set specification must also supply host/cpu information<BR>
for some modules (e.g. video-geode).
</BODY>
</HTML>