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 1Kk0IN-00085R-6J for garchives@archives.gentoo.org; Sun, 28 Sep 2008 17:42:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 47920E04C5; Sun, 28 Sep 2008 17:42:58 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 09BE5E04FC for ; Sun, 28 Sep 2008 17:42:58 +0000 (UTC) Received: from [192.168.22.10] (ip68-4-152-120.oc.oc.cox.net [68.4.152.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id C8B1C64389 for ; Sun, 28 Sep 2008 17:42:56 +0000 (UTC) Message-ID: <48DFC20F.4040107@gentoo.org> Date: Sun, 28 Sep 2008 10:42:39 -0700 From: Zac Medico User-Agent: Thunderbird 2.0.0.17 (X11/20080914) 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] PROPERTIES=set for meta-packages that should behave like package sets References: <48DECDFE.7010606@gentoo.org> <20080928172423.5544cc51@sheridan> In-Reply-To: <20080928172423.5544cc51@sheridan> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 9ec8b8d2-14fc-4772-818d-88688139db55 X-Archives-Hash: d858a9a516fe3d1996c3809fba56f1db -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marius Mauch wrote: > On Sat, 27 Sep 2008 17:21:18 -0700 > Zac Medico wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi everyone, >> >> Please consider a PROPERTIES=set value that allows an ebuild to >> indicate that it should behave like a package set when selected on >> the command line. This is behavior is somewhat difficult to describe >> in words but the following example should be sufficient to convey >> the general idea. Consider a case where all of the kde-base/*-meta >> packages exhibit the "set" property, and these packages and their >> dependencies are currently installed. In such a case, the default >> behavior for a command such as `emerge kde-base/kde-meta` should be >> to reinstall the the selected kde-base/kde-meta ebuild and the set >> of packages which includes it's direct dependencies and it's >> recursive "set" dependencies. So, assuming that all USE flags are >> enabled for the selected kde-base/kde-meta ebuild, it would >> reinstall the direct dependencies of kdeartwork-meta, kdebase-meta, >> kdeedu-meta, kdegames-meta, kdegraphics-meta, kdemultimedia-meta, >> kdenetwork-meta, kdetoys-meta, kdeutils-meta, and >> kdeaccessibility-meta ebuilds. Similarly, the default behavior for a >> command such as `emerge --unmerge kde-base/kde-meta` would be to >> uninstall the same set of packages. > > I'm not convinced that this is a good idea if some packages suddenly > behave _vastly_ different than others (from a users POV) without any > clear indication (a -meta somewhere in the name IMO doesn't count). > > Maybe we can just create a PackageSet class that wraps a package though > to get the same behavior while keeping the two behaviors separated by > syntax. Some some sort of mapping of packages into sets space does seem better than changing the behavior of these packages other cases. However, PROPERTIES=set will still be useful for governing recursion, since recursion into dependencies is probably not desired for non-meta packages in the same sense that it might be desired for meta-packages. - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjfwg4ACgkQ/ejvha5XGaMkYACdF/uvOatcWaw1DsQkY/nBZ6RW N4YAn2VFsZztPLzHO6V6T9eQER4b2tO9 =z2qG -----END PGP SIGNATURE-----