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

[Troy Dack]

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.
>
Nice idea, something that I have thought about before.

The generated make.conf should have a *big fat* warning at the top 
specifying that it is a generated file and changes are to be made to the 
appropriate files in /etc/make.conf.d (or even just /etc/make.d).

Installation documents will have to be updated to specify the individual 
files to be editted.  Also utilities like ufed and the compiler flag 
generator will also need to be modified.

Suggested files in /etc/make.conf.d :
    use - use flags
    compiler - CFLAGS, CHOST, CXXFLAGS, MAKEOPTS
    distcc - DISTCC_HOSTS
    ccache - CCACHE_DIR, CCACHE_SIZE
    directories - PORTDIR, PORTDIR_OVERLAY, etc
    fetch - FETCHCOMMAND, SYNC,  GENTOO_MIRRORS
    advanced - FEATURES,  AUTOCLEAN

To those that suggest having a full make.conf.sample or add the comments 
to make.globals:
1. I can't say that I've read through make.globals, the install 
instructions say to avoid make.globals and edit make.conf (as does 
make.globals)
2. How many users read a sample file and then go and edit the real 
config? I generally copy the .sample to the .config and then edit it, 
with all comments in place.

-- 
    Troy Dack



--
gentoo-dev@g.o mailing list