public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Date: Sun, 5 Oct 2008 11:55:33 -0600	[thread overview]
Message-ID: <20081005115533.2658ea39@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: 48E7A511.2050004@gentoo.org

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

On Sat, 04 Oct 2008 10:17:05 -0700
Zac Medico <zmedico@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ryan Hill wrote:
> > Though I'm still not sure what happens when a package is in two
> > unrelated sets..
> > 
> > @gnome:
> >    RDEPEND=">=gnome-extra/gnome-screensaver-2.22.2"
> > 
> > @xfce4:
> >    RDEPEND="gnome-extra/gnome-screensaver"
> > 
> > package.use:
> > @gnome             opengl
> > @xfce              -opengl
> > 
> 
> I suppose we could use the order that they are listed in package.use
> to apply the incremental stacking, so opengl would be disabled since
> @xfce comes after @gnome.

I guess I'll need to stop sorting my package.use then. :p

But yeah, I have no better idea.  If someone really needs to lock down
a USE flag on a pkg they can put the pkg atom itself into p.use.


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-05 17:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28  0:21 [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets Zac Medico
2008-09-28 15:24 ` Marius Mauch
2008-09-28 17:42   ` Zac Medico
2008-09-28 20:26     ` Ciaran McCreesh
2008-09-28 20:44       ` Zac Medico
2008-09-28 20:32 ` Ciaran McCreesh
2008-09-28 20:53   ` Zac Medico
2008-09-28 21:01     ` Ciaran McCreesh
2008-09-28 22:11       ` Zac Medico
2008-09-28 22:28         ` Ciaran McCreesh
2008-09-28 22:56           ` Zac Medico
2008-09-28 23:02             ` Ciaran McCreesh
2008-09-28 23:37               ` Zac Medico
2008-09-29 15:13                 ` Bo Ørsted Andresen
2008-09-29 19:52                   ` Zac Medico
2008-09-30  4:47                     ` Jorge Manuel B. S. Vicetto
2008-09-30  5:31                       ` Zac Medico
2008-10-01  4:35                         ` [gentoo-dev] " Ryan Hill
2008-10-01 16:37                           ` Zac Medico
2008-10-02  2:51                             ` Jorge Manuel B. S. Vicetto
2008-10-04  6:05                               ` Ryan Hill
2008-10-04  6:42                                 ` Ryan Hill
2008-10-04 17:17                                   ` Zac Medico
2008-10-05 17:55                                     ` Ryan Hill [this message]
2008-10-13  2:11                                       ` Steve Long
2008-10-02 12:19                             ` Robert Bridge
2008-09-29  2:52             ` Duncan
2008-09-29  6:40               ` Zac Medico
2008-09-29 11:52                 ` Duncan
2008-09-29  6:04 ` [gentoo-dev] " Rémi Cardona
2008-09-29  6:33   ` Zac Medico
2008-09-29 19:52     ` [gentoo-dev] " Steve Long
2008-09-29 20:28       ` Zac Medico
2008-09-29 20:42         ` [gentoo-dev] " Steve Long

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=20081005115533.2658ea39@halo.dirtyepic.sk.ca \
    --to=dirtyepic@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