From: "C. Brewer" <cbrewer@stealthaccess.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] make.conf
Date: Sat, 6 Sep 2003 23:17:36 -0700 [thread overview]
Message-ID: <20030906231736.3347b648.cbrewer@stealthaccess.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
I was thinking that it might be nicer to do 2 files instead of the one.
granted it's not too much trouble to do an interactive merge, and since my
.nanorc is runs it so comments are colored, I really have no trouble picking
out what I don't have commented. However, I see a real benefit to having a
make.conf and make.conf.example (ala lilo,prozilla,etc.) so that the
operator could have their six or seven line make.conf, only overriding the
usual functions (CFLAGS,mirrors,PORT_OVERLAY,etc.) This would make it so
that the make.conf.example could be auto-updated, and then those interested
in playing with their make.conf could just periodically browse the
make.conf.example to see if any new features have been added. Also, I seem
to recall the when new user-affecting feature get added, there's usually
some sort of announce here, so you really wouldn't need to look at it unless
you see something here. I think this solution would provide amiable results
for both camps:)
--
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-09-07 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 6:17 C. Brewer [this message]
2003-09-07 10:46 ` [gentoo-dev] make.conf Martin Schlemmer
2003-09-08 6:35 ` C. Brewer
[not found] <000a01c1a6f6$647688a0$0200a8c0@mike1>
2002-01-27 6:11 ` Chad M. Huneycutt
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 4:04 BoehmeSilvio
2001-04-19 9:19 ` Daniel Robbins
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=20030906231736.3347b648.cbrewer@stealthaccess.net \
--to=cbrewer@stealthaccess.net \
--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