On Mon, 2010-09-20 at 14:55 -0400, Trevor Woerner wrote: > > What we could consider though is a minimal or default set that > > just gets the basic five or six modules that covers 99% of our > testers > > (xserver, evdev, intel, etc.). > > What would you like to see as an interface? >
This is a good opportunity to make a little publicity about the "module set" feature I have been thinking about. You will never get an agreement on what the minimal default set should be. There should be an arbitrary number of module sets and an option to auto-clone modules missing on disk. That would make everybody happy. The first step is to separate the modules list from build.sh. This means build.sh has no module list at all. Users can create module sets in addition to the one that came out of build.sh. It won't be as easy as it sounds. The module set specification must also supply host/cpu information for some modules (e.g. video-geode).
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
