From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] punting the use.defaults feature
Date: Tue, 22 Nov 2005 19:22:42 +0100 [thread overview]
Message-ID: <20051122192242.5247f123@sven.genone.homeip.net> (raw)
In-Reply-To: <20051121000638.00459520@eusebe>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
On Mon, 21 Nov 2005 00:06:38 +0100
Thomas de Grenier de Latour <degrenier@easyconnect.fr> wrote:
> On Sun, 20 Nov 2005 23:23:19 +0100
> "Spider (D.m.D. Lj.)" <spider@gentoo.org> wrote:
>
> > On Sun, 2005-11-20 at 11:55 -0800, Michael Marineau wrote:
> >
> > > For users who do like the functionality just properly document
> > > the existance of USE_ORDER in the install guide.
> >
> > However, I'd -also- want the IUSE="+auto -bongodrums alpha beta
> > +zeta" to be set, perhaps with a new USE_ORDER variable
> > ":ebuild:" ?
>
> Imho, that's the problem with documenting USE_ORDER (although
> it's a minor one): if a user set USE_ORDER="env:pkg:conf:defaults"
> in his make.conf and a later version of portage introduces some new
> interesting value, he will miss this new feature without noticing.
>
> Since it seems that the common usage of user-defined USE_ORDER is
> to remove values, but not actually to change their priorities
> (probably because the default ones are the only ones which really
> make sense), i would rather see a split in two distinct vars:
> - FOO (i'm not good to invent names) would be portage internal
> and define valid values and their respective priorities.
> - BAR would be accessible to the users as an incremental var, and
> would define what values should be taken into account.
>
> FOO default would be "env:pkg:conf:auto:defaults".
> BAR default would be "auto conf default env pkg".
>
> This way, users could set BAR="-auto" in make.conf, which would
> really mean "take all of the default USE_ORDER but the auto thing".
> And the day "ebuild" or any other new feature is implemented, this
> user will have it automatically (just like he would get any new
> enabled-by-default FEATURES flag for instance).
Personally I'd just kill auto-use support in the next "big" portage
upgrade (and USE_ORDER with it as disabling auto-use is the only
real application of it that I'm aware of).
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-22 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 15:33 [gentoo-dev] use.defaults and pointless commits Jakub Moc
2005-11-18 15:37 ` [gentoo-dev] " Jakub Moc
2005-11-18 15:37 ` [gentoo-dev] " Donnie Berkholz
2005-11-18 15:43 ` [gentoo-dev] punting the use.defaults feature Mike Frysinger
2005-11-18 15:59 ` Re[2]: " Jakub Moc
2005-11-18 19:18 ` Drake Wyrm
2005-11-18 19:31 ` Ciaran McCreesh
2005-11-18 19:45 ` Kurt Lieber
2005-11-18 20:03 ` Ciaran McCreesh
2005-11-18 20:08 ` Re[2]: " Jakub Moc
2005-11-18 20:31 ` Zac Medico
2005-11-18 23:14 ` Mike Frysinger
2005-11-20 19:55 ` Michael Marineau
2005-11-20 22:23 ` Spider (D.m.D. Lj.)
2005-11-20 23:06 ` Thomas de Grenier de Latour
2005-11-22 18:22 ` Marius Mauch [this message]
2005-11-22 19:00 ` Mike Frysinger
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=20051122192242.5247f123@sven.genone.homeip.net \
--to=genone@gentoo.org \
--cc=gentoo-dev@lists.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