public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@inforead.com>
To: Seemant Kulleen <seemant@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Tue, 1 Jul 2003 10:32:58 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.56.0307011032240.27778@lacewing.inforead.com> (raw)
In-Reply-To: <20030701025824.64ecc18a.seemant@gentoo.org>

On Tue, 1 Jul 2003, 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.
>
I like the idea.

 
> Ciao,
> 
> -- 
> Seemant Kulleen
> Developer and Project Co-ordinator,
> Gentoo Linux					http://www.gentoo.org/~seemant
> 
> Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
> Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
> 
Regards,
--
Ferris McCormick (P44646, MI) <fmccor@inforead.com>
Phone: (703) 392-0303
Fax:   (703) 392-0401


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-01 11:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-01  9:58 [gentoo-dev] Interest Check: Dynamic config files for portage Seemant Kulleen
2003-07-01 10:32 ` Ferris McCormick [this message]
2003-07-01 10:35 ` Rigo Ketelings
2003-07-01 10:46 ` [gentoo-dev] " sf
2003-07-01 11:28 ` [gentoo-dev] " Georgi Georgiev
2003-07-01 11:34 ` Lisa M.
2003-07-01 12:12 ` Stewart Honsberger
2003-07-01 13:41 ` Troy Dack
2003-07-01 14:07   ` Lisa M.
2003-07-01 14:27   ` William Kenworthy
2003-07-01 15:37     ` Alex Veber
2003-07-01 22:25     ` Troy Dack
2003-07-01 22:49   ` Georgi Georgiev
2003-07-01 14:05 ` Toby Dickenson
2003-07-01 15:49   ` Josep Sanjuas
2003-07-01 16:32     ` Toby Dickenson
2003-07-01 22:29       ` Owen Gunden
2003-07-02  9:57         ` Toby Dickenson
2003-07-01 22:57     ` Georgi Georgiev
2003-07-01 14:12 ` Dhruba Bandopadhyay
2003-07-01 18:13   ` Svyatogor
2003-07-01 14:49 ` Svyatogor
2003-07-02  0:40 ` Robert Bragg
2003-07-02  2:56 ` Aron Griffis
2003-07-02  3:03   ` Aron Griffis
2003-07-02  3:51   ` Grant Goodyear
2003-07-03  5:36     ` Kumba
2003-07-03  6:04       ` Owen Gunden
2003-07-04 14:12 ` Spider
2003-07-04 23:38   ` Troy Dack
2003-07-05 17:38 ` Devdas Bhagat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.56.0307011032240.27778@lacewing.inforead.com \
    --to=fmccor@inforead.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=seemant@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox