On 01/07/03 02:58 -0700, Seemant Kulleen wrote:
> Hi All,
<insert bitching about wordwrap here>
> 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.
Instead of a make.conf.d or make.d, why not ship with a set of
sample-make.foo.conf files? The detailed comments can go in the sample
files, while the main make.conf has a few short comments.

I would suggest make.conf.global and make.conf.local. The global file
will summarily be overwritten by any upgrades, the make.conf.local file
will never be touched by it.

make.conf will include make.conf.global and make.conf.local
make.conf.local can have flags set in two ways:
append to flags in global:
	foo += flag flag flag
override global flags
	bar = flag flag flag
If there are two conflicting flags, the flags in .local take precedence,
with a warning logged to the user.

This should enable you not to have to bother about what has changed,
while allowing for local configuration specific customization.

<snip>

Devdas Bhagat