[gentoo-dev] Re: Interest Check: Dynamic config files for portage

[sf <sf@b-i-t.de>]

Seemant Kulleen wrote:
> Hi All,
> 
> Before I go and invalidate a bug, I thought I might take the idea around here to see if it has any merit in terms of usefulness/interest.
> 
> The idea stems from the fact that etc-updating a make.conf file can be a bit of a stressful event.  And as portage's set of features grows, so too will the size of the make.conf file.  I get the impression that the make.conf file is a little hard to parse, with the huge comment blocks etc etc.  So my proposal is this: a make.conf.d directory which contains files for each section of the make.conf: use, flags, fetch, packagevars.  That way, USE flags can be explained and specified in use, compiler flags in the flags file, fetch will contain the fetchcommands, mirrors (both distfiles and rsync), and packagevars can contain things like ALSA_CARDS for those of us on 2.4 kernels, and VIDEO_CARDS for those of us who have xfree/xfree-drm/whatever-future-windowing-system-we-add, and so on.  This way, the actual make.conf file (which tends to be about 10 lines of uncommented items in the usual case) can be dynamically generated from the information in those files.
> 
> Anyway, it's not an urgent issue by any means, but a thought.
> 
> Ciao,
> 

Why not leave make.conf alone and put the comments into make.globals?



--
gentoo-dev@gentoo.org mailing list