public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Date: Thu, 02 Oct 2008 02:51:53 +0000	[thread overview]
Message-ID: <48E43749.3000304@gentoo.org> (raw)
In-Reply-To: <48E3A745.4070709@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zac Medico wrote:
> Ryan Hill wrote:
>> On Mon, 29 Sep 2008 22:31:46 -0700
>> Zac Medico <zmedico@gentoo.org> wrote:
> 
>>>> Can package.use syntax be extended to allow set entries?
>>>> @compiz-fusion -gnome kde kde4
>>> Perhaps, but we need to clarify how that sort of setting will affect
>>> nested sets. For example, if @compiz-fusion contains nested sets,
>>> would those USE settings apply to the nested sets as well? Will
>>> nested sets be allowed to have independent USE settings from the
>>> sets that nest them?
>> Maybe a nested set could inherit the USE flag settings of its parent set
>> unless it has its own entry in package.use.
> 
>> Though what happens if a package is in both sets which have
>> conflicting flags in package.use?  I would say that the nested set has
>> to have priority.  If not, I can easily imagine people getting confused
>> when their USE settings for a set are being applied to all but
>> one or two packages.
> 
> It seems to me that the most logical approach would be to do some
> sort of "incremental" stacking, similar to the way that USE flags
> stack in the profiles. Suppose that we have the following settings
> in package.use:
> 
>  @kde-meta    foo bar
>  @kdeedu-meta -foo
> 
> If the flags are stacked incrementally, analogously to the way that
> they are stacked in profiles, then the above setting would apply the
> "foo" and "bar" flags to all of @kde-meta except for the
> @kdeedu-meta subset which would only have "bar" applied since "foo"
> has been disabled incrementally. Does this approach seem reasonable?

This sounds a good approach.

Ryan, I disagree with your proposal. If I enable a use flag for the
"meta" @kde and also disable it for @kdenetwork, I don't expect my
option for the @kde "meta" to override my option for @kdenetwork.
As Zac proposed, an incremental stack makes more sense. Before we had
sets, when we enabled a use flag for a meta and disabled it for an
ebuild pulled by the meta, we never expected the option for the ebuild
to be overridden by the option for the meta.

- --
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / SPARC / KDE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjkN0kACgkQcAWygvVEyAK2iQCcDgNPwNlgw3MfV1WZj+S6L+xW
RZ4An0UONUAt60WeQAUbDk2rEMduUub9
=VYib
-----END PGP SIGNATURE-----



  reply	other threads:[~2008-10-02  2:52 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 [this message]
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
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=48E43749.3000304@gentoo.org \
    --to=jmbsvicetto@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