1 |
On 2005-07-15 00:46:45 +0100 (Fri, Jul), Edward Catmur wrote: |
2 |
> On Thu, 2005-07-14 at 17:58 -0500, Qv6 wrote: |
3 |
> > I am currently running kde-3.3, and do not want to have both 3.3 and 3.4 |
4 |
> > on the box. How can I update kde or any other app and not have the old |
5 |
> > version still installed. |
6 |
> |
7 |
> Update kde as usual, then |
8 |
> |
9 |
> # emerge -av --depclean |
10 |
> |
11 |
> Make sure that portage doesn't offer to remove packages you want to keep |
12 |
> installed! Also a good idea to run revdep-rebuild afterwards. |
13 |
|
14 |
As this version of kde is slotted I believe that after your compilation |
15 |
finishes, and you find the new KDE in working state, you should: |
16 |
|
17 |
emerge prune kde |
18 |
emerge -va prune arts |
19 |
|
20 |
and then run emerge -av --depclean |
21 |
|
22 |
After depclean there will be a few leftovers from kde if I recall well. |
23 |
You may find them looking at /usr/kde/3.3/ and finding packages that own |
24 |
files left there. |
25 |
|
26 |
qpkg -f /usr/kde/3.3/some-file |
27 |
emerge -va prune the-package-found-if-it-is-part-of-kde |
28 |
|
29 |
Some files will not belong to any package, you may delete them, some |
30 |
packages will have to be rebuild to use the new KDE version and leave |
31 |
the old - dev-db/knoda in my case... |
32 |
|
33 |
Surely you may cook a nice script that will find and clear the KDE |
34 |
leftovers in more hackish way, but it was very hot the day I was doing |
35 |
this and my brain cooling system was not working properly... :-) |
36 |
|
37 |
Remember to run revdep-rebuild -p after you remove some packages. It may |
38 |
help you to find ones that need to be unmerged, and it is anyway a good |
39 |
habit to run it. |
40 |
|
41 |
HTH. |
42 |
|
43 |
-- |
44 |
No virus found in this outgoing message. |
45 |
Checked by 'grep -i virus $MESSAGE' |
46 |
Trust me. |