From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KlN9H-0004cQ-Ci for garchives@archives.gentoo.org; Thu, 02 Oct 2008 12:19:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ED20FE0154; Thu, 2 Oct 2008 12:19:13 +0000 (UTC) Received: from rabble.robbieab.com (rabble.robbieab.com [213.79.38.74]) by pigeon.gentoo.org (Postfix) with ESMTP id 9130AE0154 for ; Thu, 2 Oct 2008 12:19:13 +0000 (UTC) Received: from [192.168.1.67] (helo=localhost) by rabble.robbieab.com with esmtp (Exim 4.69) (envelope-from ) id 1KlN9E-0004uc-6a for gentoo-dev@lists.gentoo.org; Thu, 02 Oct 2008 13:19:12 +0100 Date: Thu, 2 Oct 2008 13:19:08 +0100 From: Robert Bridge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets Message-ID: <20081002131908.20627562@robbieab.com> In-Reply-To: <48E3A745.4070709@gentoo.org> References: <48DECDFE.7010606@gentoo.org> <20080929000257.7bfd0905@snowmobile> <48E0151F.1020404@gentoo.org> <200809291713.30783.bo.andresen@zlin.dk> <48E131E3.80103@gentoo.org> <48E1AF7B.4020800@gentoo.org> <48E1B9C2.4080700@gentoo.org> <20080930223525.4ab18d4b@halo.dirtyepic.sk.ca> <48E3A745.4070709@gentoo.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/ETK+YRebb92lm/k4LGkeojU"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 7772b214-fc08-4d5b-8e54-597e1aa17acc X-Archives-Hash: ef52c37e7692f8a3e2c43a7fab934fa2 --Sig_/ETK+YRebb92lm/k4LGkeojU Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 01 Oct 2008 09:37:25 -0700 Zac Medico wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Ryan Hill wrote: > > On Mon, 29 Sep 2008 22:31:46 -0700 > > Zac Medico wrote: > >=20 > >>> 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? > >=20 > > Maybe a nested set could inherit the USE flag settings of its > > parent set unless it has its own entry in package.use. > >=20 > > 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. >=20 > 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: >=20 > @kde-meta foo bar > @kdeedu-meta -foo >=20 > 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? =46rom a lowly users perspective, I would say this is more intuitive. It fits with the expected policy of the closest flag to the package taking precedence... Rob. --Sig_/ETK+YRebb92lm/k4LGkeojU Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjkvD8ACgkQZr0UhZgPVmzmnQCg+EyBj9vN9XRrBt9JEBuL4FKq MFMAoK5+XWcQGVkWJfMfyMD0JYYhlBew =OTKq -----END PGP SIGNATURE----- --Sig_/ETK+YRebb92lm/k4LGkeojU--