public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John H. Moe" <johnmoe@optushome.com.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question
Date: Thu, 20 Aug 2009 07:56:06 +1000	[thread overview]
Message-ID: <4A8C74F6.10506@optushome.com.au> (raw)
In-Reply-To: <200908192039.42647.wonko@wonkology.org>

Alex Schuster wrote:
> 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
>
>
>   

Well, I don't know about necessary, but on my box, when I tried to
update from kde-meta:4.2 to kde-meta:4.3, there were a few blockers that
wouldn't let it go through, so I ended up unmerging 4.2, then emerging
4.3 (which took about 4-6 hours, but I have distcc set up between two
boxes, so that probably sped things up).  However, I seem to remember
that the blockers were with PyQt, Python and eselect-python; I hadn't
thought about it, cause I'm still not THAT experienced with Linux in
general, and Gentoo in particular, but the Python update was a Big Deal,
so perhaps updating Python before the KDE upgrade would have been a good
idea.  :-P  Granted though, I didn't use sets, so it may be a bit
different for you.

Oh, and I didn't touch my .kde or .kde4 folders during this process, and
as far as I can tell, it's still using all of my customizations...

--==**==--
John Moe



  reply	other threads:[~2009-08-19 21:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16 19:02 [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question Roy Wright
2009-08-16 19:12 ` Dirk Heinrichs
2009-08-16 19:26   ` Dirk Heinrichs
2009-08-26  7:25     ` Helmut Jarausch
2009-08-26  7:40       ` Alan McKinnon
2009-08-26  7:48       ` Dale
2009-08-26  9:23         ` Helmut Jarausch
2009-08-26  9:54           ` Dale
2009-08-26 10:08             ` Helmut Jarausch
2009-08-26 10:10           ` Alan McKinnon
2009-08-26 16:31       ` Dirk Heinrichs
2009-08-16 19:29   ` Alan McKinnon
2009-08-16 19:46     ` Volker Armin Hemmann
2009-08-16 20:48       ` Alan McKinnon
2009-08-16 21:09         ` Volker Armin Hemmann
2009-08-16 21:18           ` Alan McKinnon
2009-08-16 21:33             ` Volker Armin Hemmann
2009-08-16 22:12               ` Roy Wright
2009-08-17  5:37                 ` Dirk Heinrichs
2009-08-17 22:40                 ` [gentoo-user] [solved] " Roy Wright
2009-08-17  5:44             ` [gentoo-user] " Dirk Heinrichs
2009-08-19 18:39 ` Alex Schuster
2009-08-19 21:56   ` John H. Moe [this message]
2009-08-19 22:44     ` Alex Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A8C74F6.10506@optushome.com.au \
    --to=johnmoe@optushome.com.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox