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 1Kk5IC-00019q-Op for garchives@archives.gentoo.org; Sun, 28 Sep 2008 23:03:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3CD84E0513; Sun, 28 Sep 2008 23:03:08 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.146]) by pigeon.gentoo.org (Postfix) with ESMTP id EEC7FE0513 for ; Sun, 28 Sep 2008 23:03:07 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 4so458777eyk.10 for ; Sun, 28 Sep 2008 16:03:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=fagWQ8OtSwWgff4cmTajuUUF+cYMsNQIS9x5cVpmmq4=; b=Q1SgnX/cpilUPRHUFz4lIQT+KpmVNBkEMTsjrbMtFN79C/g8A8cqTIY3Q3vO4EEvd3 0nQKB2BayUlC8c/ypFwQwt2DseAijeEK55OztNMgXKdet4lu6ZfK+MEb4SIMjWIbkV9f 4CPNEp8Fw+7RNHZnjs+2rO6adswTE3VXk+iL4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=nP/R6DzC0FFVGpOyg63b972OTiy3iqhD8rXv7pw8LfnDw0D4jXbeq8wJ8KIfR1LyNI 02qZq35HzcsS7eX+PsKoWmlCgKGaRQ9vy6uNESfMXHkpoXists1Y17XTPmgkB+kxNe1V 0M6+msk9NNEMDIpc0qbLZ4pZgy5YsL/qGFnyg= Received: by 10.210.30.1 with SMTP id d1mr5310776ebd.57.1222642986557; Sun, 28 Sep 2008 16:03:06 -0700 (PDT) Received: from snowmobile (92-235-187-79.cable.ubr18.edin.blueyonder.co.uk [92.235.187.79]) by mx.google.com with ESMTPS id i6sm2837440gve.2.2008.09.28.16.03.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 28 Sep 2008 16:03:05 -0700 (PDT) Date: Mon, 29 Sep 2008 00:02:57 +0100 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets Message-ID: <20080929000257.7bfd0905@snowmobile> In-Reply-To: <48E00B9B.3060600@gentoo.org> References: <48DECDFE.7010606@gentoo.org> <20080928213219.66a30341@snowmobile> <48DFEEB8.5040608@gentoo.org> <20080928220151.33656aca@snowmobile> <48E0011E.7040808@gentoo.org> <20080928232853.6540b31d@snowmobile> <48E00B9B.3060600@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_/Qu/ApLdg/YEgGk8C0g7RX=y"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: fd386005-12d4-446f-b92d-e5d6cb0b40b9 X-Archives-Hash: 9529bcb174f48efb63cc7685861f8021 --Sig_/Qu/ApLdg/YEgGk8C0g7RX=y Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 28 Sep 2008 15:56:27 -0700 Zac Medico wrote: > As I've tried to explain, the an ebuild which exhibits > PROPERTIES=3Dset doesn't necessarily have to behave any differently > than a meta-package currently does. What we would do is create a > configuration that maps the set-property ebuild into set space. For > example, `emerge kde-meta` would behave as as normal meta-package > currently does, and `emerge @kde-meta` would reference the same > package as a set and could thereby trigger different behavior which > is appropriate for a set. ...and what would that behaviour be? What does a PDEPEND mean for a set? > > Here's an alternate proposal: Repositories can ship sets via files > > in sets/*.conf. The format is as described in [1]. In configuration > > files, operations applied to a set are applied to anything matching > > any spec listed in that set (or any set that set contains, and so > > on). On the command line, sets and non-sets cannot be mixed, and > > multiple sets cannot be specified. > >=20 > > [1]: http://paludis.pioto.org/configuration/sets.html > >=20 >=20 > Perhaps can use something like you've got there in addition to the > PROPERTIES=3Dset approach. Why the need for multiple solutions at all? PROPERTIES=3Dset is too weird and involves too much nonsensical behaviour to be useful. --=20 Ciaran McCreesh --Sig_/Qu/ApLdg/YEgGk8C0g7RX=y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjgDSQACgkQ96zL6DUtXhFdwwCeOa7xi+pEJ/V0fh4go6FWtf63 fpEAn12ZBf2pxXiNTbd2IHIdwoHutZ7E =30sh -----END PGP SIGNATURE----- --Sig_/Qu/ApLdg/YEgGk8C0g7RX=y--