1 |
Daniel D Jones wrote: |
2 |
> I have KDE 3.5 and 4.1 installed and am trying to upgrade to 4.2. I'm getting |
3 |
> the following: |
4 |
> |
5 |
> <=kde-base/kdebase-3.5.9-r4 ("<=kde-base/kdebase-3.5.9-r4" is blocking |
6 |
> kde-base/kdelibs-4.2.0) |
7 |
> |
8 |
> Is there an issue with 3.5 and 4.2 being installed together? Is the above |
9 |
> block a known issue that's being worked out as 4.2 is integrated into the |
10 |
> stable tree? (I was unable to find a bug filed on it or any other hits on |
11 |
> Google.) |
12 |
|
13 |
I recommend that you edit your world file by hand |
14 |
(/var/lib/portage/world) and remove everything from in there that you |
15 |
wish to unmerge. Then run "emerge -p --depclean" and take a good look |
16 |
at the output. Put in the world file every package listed that should |
17 |
NOT be removed. When everything looks fine, do the final "emerge -a |
18 |
--depclean". |
19 |
|
20 |
Take care though after that not clutter your world file again. That |
21 |
mainly means that if you emerge some dependency of a package manually |
22 |
(for whatever reason) do so with the -1 or --oneshot option of emerge. |
23 |
|
24 |
Note that you can put slotted packages in the world file. For example |
25 |
if all you have in there is "kde-base/kdelibs" and you remove it, |
26 |
depclean will remove both KDE3 and well as KDE4 libs. Simply put |
27 |
"kde-base/kdelibs:3.5" in the world file. depclean will not remove the |
28 |
3.5.x versions that way. Personally, I keep the 3.5 slots and an |
29 |
unslotted version: |
30 |
|
31 |
kde-base/kdelibs |
32 |
kde-base/kdelibs:3.5 |
33 |
|
34 |
This will provide easy updates to future 4.x versions but will not mess |
35 |
with 3.5. |
36 |
|
37 |
I find that having a clean world file makes package management in Gentoo |
38 |
a lot easier :) |