From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: 01 Jul 2003 23:51:53 -0400 [thread overview]
Message-ID: <1057117913.16770.10.camel@localhost> (raw)
In-Reply-To: <20030702025637.GH20197@time>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
On Tue, 2003-07-01 at 22:56, Aron Griffis wrote:
> Somebody mentioned that it would be possible to consolidate the comments
> to make.globals, and leave make.conf uncommented. I think that would be
> fine. Alternatively, I'd just leave the situation as-is.
I'm fairly agnostic on whether or not make.conf should be broken into
pieces. Personally, I'm quite happy w/ a single file, but I wouldn't
complain about a make.conf.d directory.
I do want to argue against moving the comments from make.conf to
make.globals, however. Given the standard Gentoo policy that users
should never make changes to make.globals, I don't think it would make
sense for us to tell the same users: "Just look in make.globals to see
what you can do w/ make.conf". I think that such a plan would lead to a
lot more users editing make.globals directly.
I also _like_ having the comments in make.conf. As it is the first part
of portage that our users encounter, I think it behooves us to document
it as well as possible. (That said, I do realize that we do have a very
nice make.conf man page, so the comments in /etc/make.conf are not
entirely necessary.)
Well past my bedtime,
g2boojum
--
Grant Goodyear <g2boojum@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-02 3:52 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 [this message]
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=1057117913.16770.10.camel@localhost \
--to=g2boojum@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