nanogui@linuxhacker.org

Greg Haerr wrote:
> 
> : I'm peeking in the pre5 code right now and I was just wondering what's
> : the point for multiple config files ? The point of having one config
> : file was in the maintainer's point of view. What if I want to add and
> : option ? I will have to copy it everywhere ? And if an architecture is
> : added ? Beside, no need to multiply config files, if one wants to change
> : an option, he just edit the config file and thats all !
> 
> I agree with you.  I just put together the various config files
> so that people could test quickly, and the distribution would have
> pre built versions so that people wouldn't have to dig in too much
> in order to make Microwin on various platforms.  It's already been
> a pain copying between them as I've added options though...
> 

I also agree. If you have a maintained working configuration tool you
should not need these files as they should be able to be generated.

-- 
 Chris Johns, mailto:ccj@acm.org