From: Kumba <kumba@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Thu, 03 Jul 2003 01:36:23 -0400 [thread overview]
Message-ID: <3F03C0D7.5080705@gentoo.org> (raw)
In-Reply-To: <1057117913.16770.10.camel@localhost>
Hmmm, Pondering this thread leads me to a few opinions of my own. One,
I have to sway away from splitting make.conf into multiple files. I
kinda like only having to tweak one file to alter the settings of the
one system wide feature of Gentoo that makes it Gentoo -- Portage.
Breaking this up into multiple files I think would anger the user base.
Honestly, it's not that complex of a file. And I rather like the
large comment blocks that explain various features and settings of
portage. More information, the better, I always say.
Maybe if make.conf was in the format of a sendmail config file,
something like this might be more warranted. Users who don't want to
have the comment blocks can simply delete them, and etc-update after
merging a new portage takes very little time. IMHO, I'd say this is
extremely trivial right now.
On the other hand, perhaps some small changes could be made. I do think
the USE variable is just pointless. There are *way* too many use flags,
and setting these manually in make.conf is self-defeating. Better to
train people to make use of "ufed" to set the USE settings, and keep
that file separate from make.conf, say /etc/env.d/useflags.
Other suggested changes are removing variables that affect tools outside
portage, such as distcc and ccache. They have their own userland tools
to configure them. At most, a comment block in make.conf, or more
preferably, a note in the man page for these might be better.
Otherwise, I don't see much of a point to change the make.conf file. I
think it serves it's purpose well, and centralizes things nicely. I
think alot of the tools available for Gentoo outside of 'emerge' and
'ebuild' should also be centralized in some form, like ufed,
mirrorselect, etc.., either by being merged into a single utility, or
individually called from a central utility.
Just food for thought.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world:
small hands do them because they must, while the eyes of the great are
elsewhere." --Elrond
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-03 5:31 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
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 [this message]
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=3F03C0D7.5080705@gentoo.org \
--to=kumba@gentoo.org \
--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