From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dirt: To shove under the rug or not shove under the rug? (aka another round of USE_EXPAND)
Date: Tue, 27 Sep 2005 08:38:18 -0400 [thread overview]
Message-ID: <1127824698.31328.14.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200509271912.22758.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Tue, 2005-09-27 at 19:12 +0900, Jason Stubbs wrote:
> On Tuesday 27 September 2005 18:38, Diego 'Flameeyes' Pettenò wrote:
> > On Tuesday 27 September 2005 11:23, Jason Stubbs wrote:
> > > So what needs to be done to fix it? Well, what is the purpose of
> > > USE_EXPAND? Put simply, it is to allow the user to select one or more
> > > features of a package from a list of choices. How is this different to
> > > USE flags? The choices all pertain to one aspect of the package(s).
> >
> > The way ELIBC, KERNEL, USERLAND are used, is instead something different.
> > They don't allow users to select what they want, they allow profiles to
> > declare what they are created for.
>
> Which leads me to the one thing I didn't say but feel strongest about.. What
> is the real point of USE_EXPAND? What can/does it do that USE flags do not?
As far as I can tell, it was created to keep people from adding a huge
number of USE flags to IUSE on a package. I can't see any other reason
for it.
--
Chris Gianelloni
Release Engineering - Strategic Lead
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-27 12:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 9:23 [gentoo-dev] Dirt: To shove under the rug or not shove under the rug? (aka another round of USE_EXPAND) Jason Stubbs
2005-09-27 9:38 ` Diego 'Flameeyes' Pettenò
2005-09-27 10:12 ` Jason Stubbs
2005-09-27 10:41 ` Diego 'Flameeyes' Pettenò
2005-09-27 12:51 ` Jason Stubbs
2005-09-27 13:44 ` Diego 'Flameeyes' Pettenò
2005-09-27 14:07 ` Kito
2005-09-27 16:27 ` Stephen Bennett
2005-09-27 16:48 ` Brian Harring
2005-09-27 14:25 ` Jason Stubbs
2005-09-27 15:40 ` [gentoo-dev] " Duncan
2005-09-27 12:38 ` Chris Gianelloni [this message]
2005-09-27 15:36 ` [gentoo-dev] " Donnie Berkholz
2005-09-27 10:54 ` Thomas de Grenier de Latour
2005-09-27 12:31 ` Jason Stubbs
2005-09-27 12:35 ` Chris Gianelloni
2005-09-27 13:07 ` Thomas de Grenier de Latour
2005-09-27 13:50 ` Chris Gianelloni
2005-09-27 14:20 ` Jason Stubbs
2005-09-27 15:35 ` Donnie Berkholz
2005-09-28 1:23 ` Jason Stubbs
2005-09-28 3:13 ` Jason Stubbs
2005-09-28 3:58 ` Jason Stubbs
2005-09-28 4:19 ` Donnie Berkholz
2005-09-28 4:45 ` Jason Stubbs
2005-09-28 6:23 ` Donnie Berkholz
2005-09-28 8:03 ` Jason Stubbs
2005-09-28 4:21 ` Jason Stubbs
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=1127824698.31328.14.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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