From: Dhruba Bandopadhyay <dhruba@codewordt.co.uk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Tue, 01 Jul 2003 15:12:20 +0100 [thread overview]
Message-ID: <3F0196C4.7000002@codewordt.co.uk> (raw)
In-Reply-To: <20030701025824.64ecc18a.seemant@gentoo.org>
Seemant Kulleen wrote:
> 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've always thought that /etc/make.conf should consist of env. variables
only, have no comments and be generated dynamically not from other
smaller files but from a utility or tool of some sort. Currently, the
size of the make.conf file is huge and doing the following gives the
essential structure that I'm talking about.
grep -v '#' /etc/make.conf | cat -s > ~/make.conf.basic; more
~/make.conf.basic
You'll see that this is much more readable and easily editable.
Comments can be placed in a different file such as /etc/make.conf.help.
However, given that this method also results in more than one file it
also brings about the need for a directory.
I suggest /etc/portage/. There is already a dir structure for
/etc/portage/package.unmask. As a result, it would make sense for all
portage/gentoo related files to be placed in there. This would include
make.conf, rc.conf, help files and any others.
To summarise, directory structure: yes, dynamic: yes, from zillions of
smaller files: no (that's backward progress).
A few of my thoughts.
With regards.
--
Dhruba Bandopadhyay | dhruba[AT]codewordt.co.uk | ICQ: 31628525
Gentoo-sources-2.4.20-r5 | XFree-4.3.0-r3 | Nvidia-1.0.4363 |
E-0.16.6-pre4 | ~x86
D8250 | Intel P4 I850E | Nvidia GeForce4 MX420 | Turtle Beach Santa Cruz
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-01 14:12 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
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 [this message]
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=3F0196C4.7000002@codewordt.co.uk \
--to=dhruba@codewordt.co.uk \
--cc=gentoo-dev@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