From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage
Date: Fri, 4 Jul 2003 16:12:00 +0200 [thread overview]
Message-ID: <20030704161200.4b425d9c.spider@gentoo.org> (raw)
In-Reply-To: <20030701025824.64ecc18a.seemant@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
begin quote
On Tue, 1 Jul 2003 02:58:24 -0700
Seemant Kulleen <seemant@gentoo.org> wrote:
> Hi All,
>
> Before I go and invalidate a bug, I thought I might take the idea
> around here to see if it has any merit in terms of
> usefulness/interest.
>
O have to disagree/agree.
you can already do "source /some/other/place/useflags" and declare
local USE flags there..
or, as I have mine structured:
GNOME="gnome esound gtk gtk2"
KDE="-kde -arts -qt"
CRYPT="crypt ssl gpg ldap"
USE="${GNOME} ${KDE} ${CRYPT} ipv6"
if you take care to re-define variables, and add a nice blank line
before, then etc-update won't barf on the config and think you changed
as much, meaning merge will be simpler.
So in this term, I'm against doing any modifications to the current
system, theres little need to do so, and to split configuration from
documentation is a bad thing in a configfile of this sort.
//Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-04 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
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 [this message]
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=20030704161200.4b425d9c.spider@gentoo.org \
--to=spider@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