public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Local USE defaults
Date: Fri, 19 Aug 2005 06:53:43 -0500	[thread overview]
Message-ID: <20050819115343.GJ19947@nightcrawler> (raw)
In-Reply-To: <430585F4.40008@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

On Fri, Aug 19, 2005 at 12:10:44AM -0700, Donnie Berkholz wrote:
> Brian Harring wrote:
> | Yeah, but the angle I'm pushing for default IUSE's ...er.. use is
> | eliminating no* flags, and giving ebuild maintainers more flexibility
> | in breaking the package down into conditionals.
> |
> | I really don't see -* being all that useful long term frankly, since
> | the major usage of it I've seen is either within cascaded profiles, or
> | nuking autouse; people do block profile use flags also, but killing
> | autouse falls in with killing profiles :)
> 
> I don't think that having -* not actually do -* is a good idea. And most
> people adding local flags don't really consider the -* case so creating
> no* flags isn't a major concern.
> 
> ~From my POV, -* is expected to not work well, but it should do what it
> suggests: subtract everything.
Meh.
-* 's meaning right now is to nuke all USE flags that portage tries to 
'help' in adding.  Having it nuke all default use seems wrong, since 
people *currently* use -* to block autouse crap, and -* isn't what 
they signed up for initially.

Different flag imo seems wise, rather then grandfathering people into 
it; nuking what the profile offers should be available, but I don't 
think nuking default IUSE should be nuked as an added bonus of trying 
to disable auto-use/profile cruft.

Thoughts?
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-19 11:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 14:28 [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Christian Parpart
2005-08-18 14:23 ` Luca Barbato
2005-08-18 15:24   ` Francesco R
2005-08-18 14:27 ` Brian Jackson
2005-08-18 14:40 ` Mike Frysinger
2005-08-18 15:13   ` Lance Albertson
2005-08-18 15:24     ` Ciaran McCreesh
2005-08-18 15:28     ` Francesco R
2005-08-18 15:37     ` Chris Gianelloni
2005-08-18 15:56       ` Brian Harring
2005-08-18 16:08         ` [gentoo-dev] Local USE defaults Donnie Berkholz
2005-08-18 16:31           ` Brian Harring
2005-08-18 17:16             ` Alec Warner
2005-08-18 17:36               ` Brian Harring
2005-08-18 17:18             ` Mike Frysinger
2005-08-18 17:38               ` Brian Harring
2005-08-19  7:10                 ` Donnie Berkholz
2005-08-19 11:53                   ` Brian Harring [this message]
2005-08-18 17:24         ` [gentoo-dev] ebuild design issue regarding some {I need the lib and api only}-DEPENDs Ciaran McCreesh
2005-08-18 18:13           ` Brian Harring
2005-08-19  0:06             ` Ciaran McCreesh
2005-08-19  1:59               ` Brian Harring
2005-08-18 15:17 ` Brian Harring
2005-08-18 15:44   ` Chris Gianelloni
2005-08-19  3:30     ` Christian Parpart
2005-08-19  3:09       ` Brian Harring
2005-08-18 17:01 ` Georgi Georgiev
2005-08-19  2:59   ` Luke-Jr
2005-08-19  5:01     ` Georgi Georgiev
2005-08-19  3:19   ` Christian Parpart

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=20050819115343.GJ19947@nightcrawler \
    --to=ferringb@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