public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@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: Wed, 28 Sep 2005 10:23:50 +0900	[thread overview]
Message-ID: <200509281023.50075.jstubbs@gentoo.org> (raw)
In-Reply-To: <433966D9.3040401@gentoo.org>

On Wednesday 28 September 2005 00:35, Donnie Berkholz wrote:
> 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]

This output is exactly what my patch gives, but it currently works by 
inspecting IUSE. However, it should be possible to indirectly pull the 
information from the above flags instead. Adding support for a 
USE_EXPAND_HIDDEN var should cover USERLAND and friends as well (although 
those would still need to be defined in IUSE_USERLAND="...")

> 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.

This still doesn't cover the discrepencies in behaviour between different 
packages though. How to handle that in the short term? einfo and/or ewarn?

--
Jason Stubbs
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-09-28  1:26 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
2005-09-28  1:23   ` Jason Stubbs [this message]
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=200509281023.50075.jstubbs@gentoo.org \
    --to=jstubbs@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