From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Mdq4g-000762-Jr for garchives@archives.gentoo.org; Wed, 19 Aug 2009 18:39:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FE6FE02AC; Wed, 19 Aug 2009 18:39:52 +0000 (UTC) Received: from mail.askja.de (mail.askja.de [83.137.103.136]) by pigeon.gentoo.org (Postfix) with ESMTP id EA3DCE02AC for ; Wed, 19 Aug 2009 18:39:51 +0000 (UTC) Received: from static-87-79-89-40.netcologne.de ([87.79.89.40] helo=zone.wonkology.org) by mail.askja.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Mdq4d-0008KF-2Q for gentoo-user@lists.gentoo.org; Wed, 19 Aug 2009 20:39:51 +0200 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by zone.wonkology.org with local; Wed, 19 Aug 2009 22:08:55 +0200 id 0001047B.4A8C5BD7.000022CC From: Alex Schuster To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question Date: Wed, 19 Aug 2009 20:39:42 +0200 User-Agent: KMail/1.11.4 (Linux/2.6.28-tuxonice-r3_3; KDE/4.2.4; i686; ; ) References: In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Disposition: inline X-Length: 2947 X-UID: 362 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200908192039.42647.wonko@wonkology.org> X-Archives-Salt: bacdf169-a721-4da1-a3c0-117db8cc82af X-Archives-Hash: 30d2267400a8393b159ca76ef2cd630c Roy Wright writes: > kde-4.3 is now unmasked for ~x86. Whooooop! I'm also happy, and I want to upgrade soon. I hope many of those little annoyances I experience will be fixed. > But it is looking like a non-trivial upgrade. :( Yeah. > When I installed kde-4.2, I followed the advice of unmasking portage > and using sets. Also followed the recommendation to use -kdeprefix. > Further I removed kde-3.5 and added a mask on kdelibs-3.5 to help keep > 3.5 off of the system. > > So for the kde-4.3 upgrade, it looks like this is what will be > necessary: > > 1) grab the sets again from the kde-testing overlay and put them in / > etc/portage/sets (assumption is to do a replace). I did that, too, but got errors from portage (Error during set creation: Redefinition of set...). Looks like the sets are found in the kde-testing overlay, so I removed them from /etc/portage/sets, and all was fine. Coool. > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2 Not really necessary I heard. But: I am still using the dreaded kdeprefix use flag. It sounded like a good idea to use it, and I would also like to have different minor KDE versions alongside. Okay, it's hard to maintain, I understand it will be dropped. Now, do I REALLY REALLY have to unmerge all @kde-4.2 first, remove the kdeprefix use flag, and proceed to step 3? > 3) merge kde-4.3 using: emerge -av @kde-4.3 Hopefully this runs through. If it takes a night, it's okay, but if it stops in the middle, I have no KDE for a while. And I need much of the stuff in there, like the wallet with its passwords. What about this: I update my system's backup (I'm using rdiff-backup), chroot into the backup, sudo to my account, and issue startkde. Could I get a running KDE 4.2? Then I would have time to install 4.3. > 4) recustomize kde as the ~/.kde will not be migrated I really hope I can just copy .kde4.2 to .kde4 and all (okay, most) settings will be kept. I think it just _should_ work. Customizing all over again every time a new KDE arrives would be no good. Wonko