| View previous topic :: View next topic |
| Author |
Message |
i92guboj
Moderator
Joined: 30 Nov 2004
Posts: 9316
Location: Córdoba (Spain)
|
 Posted: Tue Jul 07, 2009 2:35 pm Post subject: |
 |
|
| VoidMage wrote: | I think that should be 'emerge -1av kdebase-meta' to
avoid future problems. |
You definitely want to avoid --oneshot/-1. That package must be in the world file, otherwise the next --depclean will try to uninstall it and all its dependencies (which means the whole kde).
Whether that command will solve the issue or not entirely depends on what do you have installed, how up to date are the system and portage and a few other things, there's no easy way to predict it and it isn't worth the trouble to predict it because that's what -a and -p exist for. You will know for sure when you try to run it. Use always -a so you can take a look at what is to be performed without actually doing any real thing until you answer "yes".
_________________
Gentoo Handbook |
|
| Back to top |
|
 |
sparc
n00b
Joined: 18 Aug 2005
Posts: 67
Location: Stockholm, Sweden
|
| Posted: Mon Aug 31, 2009 10:59 pm Post subject: |
|
|
Well, let's take a few steps back and think computer architecture for a moment...
I had the same problem, unmerged all monolithic ebuilds, emerged the new meta packages and while doing all that my GUI was perfectly up and running. This is because of the way computers work. You see, when you load a program (whatever that is) it is loaded into RAM. If you delete the corresponding file the program will still be running from memory, in perfect shape. So as long as you do not need to execute/use any new files/parts (of the program) after having unmerged the monolithic ebuilds, your GUI will stay up and wont transfer to 3.5.10 before a new log in.
To make it clearer think of the following. Open a text file in some editor. Delete the file. Did the text disappear from within the editor? Of course not. This is even easier to comprehend when done with media files. Start a movie using a huge buffering setting. Delete the movie file while playing. The player wont stop until its buffer runs out.
But a GUI is a bit more complex than a single media file since it is made out of thousands of files. The main reason behind this phenomenon in kde is the kdelibs package. This package hosts 80% of what we call kde and any kde-app will only depend on that package after execution. This package does not have to be uninstalled before the upgrade since it is not part of any other package (except of course the kde package), and after the upgrade the new version is 100% compatible with the old one. For that reason, all applications you have kept running will continue to run by using the only thing they actually need, the kdelibs package. Even when at some point you change to the new version of it, the application will never understand the difference. Of course I am again refering to libraries which have probably not been already loaded into memory before the process begins...
Anyhow, what I did, was:
1) executed all the kde apps I would need for the next 4-5 hours.
2) unmerged all monolithic ebuilds (I had to include kdebase here, no harm done)
3) did a
| Code: |
# emerge -avnuDN kdelibs *-meta *-meta *-meta etc (where '*' substitute with the name of each monolithic package unmerged earlier)
|
4) just to be safe...
| Code: |
# emerge -avnuDN world
|
5) logout - login. Or maybe you could run...
| Code: |
# /etc/init.d/xdm restart &
|
from within kde so that you even get a new run of kdm 
... and all done! Welcome to kde-3.5.10 
PS: The same way I solved the qt blocks also, when upgrading to 4.5. On the fly. I actually uninstalled all qt related packages while kde was up and running non-stop. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
