public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Toby Dickenson <tdickenson@devmail.geminidataloggers.co.uk>
To: Josep Sanjuas <kl4rkmail@jazzfree.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Tue, 1 Jul 2003 17:32:56 +0100	[thread overview]
Message-ID: <200307011732.56525.tdickenson@devmail.geminidataloggers.co.uk> (raw)
In-Reply-To: <20030701174923.35cefb97.kl4rkmail@jazzfree.com>

On Tuesday 01 July 2003 16:49, Josep Sanjuas wrote:

> I think there could be more advantages.

they dont seem very compelling.....

> It would make make.conf faster to
> parse from scripts,

There isnt much to be saved.....

$ time bash /etc/make.conf

real    0m0.005s
user    0m0.000s
sys     0m0.000s

> It'd also make portage easier to maintain, because for
> example, if I want to change the disftile or rsync mirrors then I can edit
> /etc/make.conf.f/fetch, or whatever its name would be, instead of finding
> the appropiate vars in the big make.conf.

And editing a 250 line file is hard because......

> In the files, all flags could
> have their detailed descriptions, so that you wouldn't need to open another
> file eg a make.conf.help. 

I agree that splitting the documentation into make.conf.help would be a step 
backwards.



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-01 16:32 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
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 [this message]
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=200307011732.56525.tdickenson@devmail.geminidataloggers.co.uk \
    --to=tdickenson@devmail.geminidataloggers.co.uk \
    --cc=gentoo-dev@gentoo.org \
    --cc=kl4rkmail@jazzfree.com \
    --cc=tdickenson@geminidataloggers.com \
    /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