public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP 29 (USE groups) and negatives
Date: Tue, 08 Mar 2005 14:51:04 -0500	[thread overview]
Message-ID: <1110311465.9520.247.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <422DF989.3090206@hub.net.nz>

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

On Wed, 2005-03-09 at 08:14 +1300, Jerome Brown wrote:
> How about another option?
> 
> 6) Disallow -USE within groups, but allow -@GROUP

I like this option.

> The issue comes with resolving the individual (@KDE -@GNOME or vice
> versa) as both define X, and a -X comes from the other. I guess that
> this could be resolved by defining that if a USE flag is defined in a
> group, and another group negates it, that portage ignores the negation,
> however if the negation is specified by the user in their USE line then
> the negation is allowed: Therefore

Why is X in either GNOME or KDE anyway?  It is separate from either, and
should probably have its own group, if necessary.

When I think of KDE stuff, I don't think of X + KDE, I think of KDE and
arts and Qt.  I think of X as a separate beast entirely.

Then again, I don't think that flags should be specified in more than
one group.

If it doesn't fit into a group, then don't group it.  If it fits into
multiple groups, then either pick one and stick with it, or don't group
it.

Groups are supposed to simplify using large numbers of USE flags, it
isn't supposed to completely replace them.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-08 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 16:28 [gentoo-dev] GLEP 29 (USE groups) and negatives Ciaran McCreesh
2005-03-07 19:24 ` Maurice van der Pot
2005-03-08 15:21   ` Ciaran McCreesh
2005-03-08 17:35     ` Maurice van der Pot
2005-03-08 22:41       ` Ciaran McCreesh
2005-03-08 23:17         ` Olivier Crête
2005-03-08 23:26         ` Jason Wever
2005-03-08  2:29 ` Philip Webb
2005-03-08 19:14 ` Jerome Brown
2005-03-08 19:51   ` Chris Gianelloni [this message]
2005-03-08 20:43     ` Jerome Brown
2005-03-08 22:43     ` Ciaran McCreesh
2005-03-09 12:54       ` Maurice van der Pot
2005-03-09 16:21         ` Ciaran McCreesh
2005-03-08 23:48   ` Luca Barbato
2005-03-09  1:18 ` Marius Mauch

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=1110311465.9520.247.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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