From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 83333139694 for ; Sun, 9 Jul 2017 01:32:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 986642740A4; Sun, 9 Jul 2017 01:32:11 +0000 (UTC) Received: from mail1.obsidian-studios.com (mail.obsidian-studios.com [173.230.135.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3F042214108 for ; Sun, 9 Jul 2017 01:32:11 +0000 (UTC) Received: (qmail 13889 invoked from network); 9 Jul 2017 01:32:10 -0000 Received: from unknown (HELO assp1.obsidian-studios.com) (wlt-ml@::ffff:127.0.0.1) by ::ffff:127.0.0.1 with ESMTPA; 9 Jul 2017 01:32:10 -0000 X-Assp-Version: 2.5.5(17073) on assp1.obsidian-studios.com X-Assp-ID: assp1.obsidian-studios.com m1-63930-19811 X-Assp-Session: 36FA1EF63D0 (mail 1) X-Assp-Envelope-From: wlt-ml@o-sinc.com X-Assp-Intended-For: gentoo-dev@lists.gentoo.org X-Assp-Server-TLS: yes Received: from unknown ([fdbe:bad:a55:0:1::211] helo=localhost) by assp1.obsidian-studios.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.5.5); 8 Jul 2017 21:32:09 -0400 Date: Sat, 8 Jul 2017 21:32:09 -0400 From: "William L. Thomson Jr." To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Sets vs Meta ebuilds Message-ID: In-Reply-To: <20170709002738.GA28879@waltdnes.org> References: <7513ca72-4ca2-ae77-3321-cdb12263af2f@gentoo.org> <20170709002738.GA28879@waltdnes.org> Organization: Obsidian-Studios, Inc. X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-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; micalg=pgp-sha1; boundary="Sig_/iKZ6Jez+8Rm1u4QKEVk0ss8"; protocol="application/pgp-signature" X-Archives-Salt: 3477c0a1-5c77-470f-8555-24cb8c215d71 X-Archives-Hash: 9fdef95fc2d41bf327aa9fa4db20c79e --Sig_/iKZ6Jez+8Rm1u4QKEVk0ss8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 8 Jul 2017 20:27:38 -0400 "Walter Dnes" wrote: > > > Though I will have to see what happens if a package is listed in > > more than one set. I think there is a hierarchy there. =20 >=20 > I tried "emerge -pv --unmerge @palemoon_build", and it was ready to > delete all the stuff, including gcc, etc. Did you get any warnings? Your about to remove a system package, etc. =20 > > Not to mention if it was removed. I think the world or system set > > would pull it back in. =20 >=20 > Kind of hard to "pull it back in" if gcc or glib or ncurses isn't > present. This is rather dangerous. The problem is that, unlike an > ebuild, "emerge --unmerge @set" removes all packages in the set, > regardless of whether they're required by another package or not. It is the same as doing emerge -C gcc. At the same time if you built and generated a binary package. On re-emerge you could pull in the gcc binary you made when it was installed the first time. I love binary packages, I make and use them all the time. Invaluable for re-emerging. If you are making sets, adding system packages, and removing those. I would assume you are doing that as some sort of testing. Which would want to re-emerge/install those packages. Depending on what your doing very likely would want to make and use binaries in that process. Surely if removing system packages :) > I deleted /etc/portage/sets/palemoon_build, and the entry > "@palemoon_build" from /var/lib/portage/world_sets. It turns out that > all these packages are required anyways. Meaning little was removed after you did emerge --depclean world ? --=20 William L. Thomson Jr. --Sig_/iKZ6Jez+8Rm1u4QKEVk0ss8 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTEeldqZjmVut8bVHJNcbKkg6ozUAUCWWGHmQAKCRBNcbKkg6oz UL28AKC+Qp/FVQhkMsxVFr/q4h+exNhAqQCgjNyyy/cXU0l/qBEez0DH3Cpor+s= =Zj7Q -----END PGP SIGNATURE----- --Sig_/iKZ6Jez+8Rm1u4QKEVk0ss8--