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 1KuhLX-0002W7-Ga for garchives@archives.gentoo.org; Tue, 28 Oct 2008 05:42:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D61BFE02A8; Tue, 28 Oct 2008 05:42:25 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by pigeon.gentoo.org (Postfix) with ESMTP id 8650EE02A8 for ; Tue, 28 Oct 2008 05:42:25 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KuhLQ-0001hM-2R for gentoo-amd64@lists.gentoo.org; Tue, 28 Oct 2008 05:42:20 +0000 Received: from ip68-230-99-190.ph.ph.cox.net ([68.230.99.190]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Oct 2008 05:42:20 +0000 Received: from 1i5t5.duncan by ip68-230-99-190.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Oct 2008 05:42:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Following the kde4.1 upgrade guide Date: Tue, 28 Oct 2008 05:42:11 +0000 (UTC) Message-ID: References: <4906004B.4030707@ercbroadband.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-99-190.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7cbbeeb5-7149-4c27-b142-3392611cfc7d X-Archives-Hash: 698209aaabadb714894ccc4d64bccb99 "Mark Haney" posted 4906004B.4030707@ercbroadband.org, excerpted below, on Mon, 27 Oct 2008 13:54:19 -0400: > I'm finally to the point that I'm read yo move to KDE4.1.2 now, but I'm > missing something I think. >=20 > Using the KDE4.1 guide, I try to unmerge the KDE4.1.1 packages using > sets (as the guide states to do if you're using the kdesvn-portage > overlay), but it doesn't work. I apparently don't have any sets when I > setup the overlay? >=20 > I've upgraded portage so I know it's a version that supports sets, but > for some reason it's not working. >=20 > Ideas? Well, first off as all the kdesvn and earlier kde-4 packages were masked=20 and you had to unmask them for installation, it should be a simple matter= =20 of deleting all those package.unmask entries you added to unmask them,=20 running emerge --update, and portage should take care of the details on=20 its own. Of course, don't forget the --depclean and revdep-rebuild steps= =20 afterward, cleaning up the loose ends. Given the flexibility of portage,=20 there are several other ways to do it, some of which are listed below,=20 but this might be the simplest, particularly since you should really do=20 it anyway, thus cleaning up your portage config after your testing. As for the other ways... Note that the upgrade guide mentions sets (under installation in the=20 guide) , providing a link to the overlay versions, since the sets=20 themselves aren't in the tree yet. There's a kde-4 set, listing all=20 kde-4 packages complete with :kde-4 slot specifiers. If you were using the kde-4 slot, removal should be a simple as pointing=20 emerge --unmerge at that set. It's the "raw" link if you're downloading from the git tree, or unpack=20 the tarball somewhere, browse it if desired, and point portage at it. =20 Note that the default sets directory is /etc/portage/sets. You can=20 unpack the tarball there if desired (I did), but you may also find that=20 too cluttered, and unpack it elsewhere and either point portage at your=20 chosen location specifically or copy/move specific sets as needed to the=20 default location, thus avoiding the clutter and confusion of all those=20 extra sets you may not use. If you were using the kdesvn slot or something else, you should be able=20 to do the same, only use your favorite text editor to search-and-replace=20 all the ":kde-4" slot specifiers with the appropriate slot as necessary. As the upgrade guide mentions, don't forget --depclean. Of course,=20 that'll be much simpler and less prone to error if you've maintained a=20 clean install all along. (Of course, don't forget --ask or --pretend=20 before actually doing it, either, but that should be habit, by now, and=20 should go without saying.) If you used kde-prefix or packages from before that USE flag was=20 introduced, you can also try the unmerge example using qfile. =20 Alternatively you can use equery belongs /usr/kde/%PREFIX%=20 (replace %PREFIX% as necessary) to get a list of packages using that=20 directory, and unmerge all of them. If you don't have kde-3 merged, or do but don't care if it gets unmerged,= =20 you can also use the generic kde sets from the location above, and/or use= =20 emerge --pretend --emptytree | grep kde > kdepkg.lst to get a list, edit=20 that file to format it correctly for feeding back to emerge, then use=20 that as an unmerge list. I've done the emptytree grep thing (using cut=20 and etc to trim it down further as well) myself a few times on various=20 things. When the packages weren't masked and before sets, it was at=20 times necessary to do something like that, particularly with slotted=20 split package projects like kde-3. The proper use of sets should=20 dramatically ease the problem in the future. =3D:^) --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman