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
