From: Donnie Berkholz <spyderous@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:35:53 -0700 [thread overview]
Message-ID: <433966D9.3040401@gentoo.org> (raw)
In-Reply-To: <200509271823.25788.jstubbs@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Stubbs wrote:
| Removing the QA check while the QA problem still exists is, in my
mind, just
| plain ludicrous. Removing the QA check once the QA problem is fixed
doesn't
| make much sense to me either. However, adjusting the check where
necessary to
| match the fix is reasonable.
|
| 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).
What I have done in my ebuilds using USE_EXPAND is add extra IUSE-like
variables, for example:
IUSE_VIDEO_CARDS="radeon sis mga"
IUSE_INPUT_DEVICES="synaptics wacom"
for `use video_cards_sis` etc..
This would allow for possible QA checks. Potentially, portage could look
through and display things at --verbose like:
[ebuild N ] x11-base/x11-drm-20050807 +dga -nls VIDEO_CARDS="+sis
+mga -radeon" 538 kB [2]
USE_EXPAND allows grouping a similar set of USE flags together to
indicate their relatedness, and it is particularly useful when there are
both USE_EXPAND and non-USE_EXPAND flags on the same ebuild. It is also
useful when a number of packages make use of the same group of
USE_EXPAND variables.
The main problem with USE_EXPAND right now is that people just don't
realize it exists, so they don't take advantage of it. We need a way to
tell them, such as the --verbose output I suggested and some more
documentation.
Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDOWbZXVaO67S1rtsRAulnAKCkevKbDcd1ib2S9W3m8Ila797KGgCeLWNS
ZY+Fat5UX9sjVA0r+yB159U=
=Kysv
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-27 15:40 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 ` [gentoo-dev] " Chris Gianelloni
2005-09-27 15:36 ` 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 [this message]
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=433966D9.3040401@gentoo.org \
--to=spyderous@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