| 1 |
On Tuesday 24 March 2009 19:26:45 James wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> Confidence is high that I've mucked_up this upgrade to |
| 5 |
> kde-4.2.1. |
| 6 |
> |
| 7 |
> I was content to leave the system at 3.5.9 and while |
| 8 |
> I was messing around, I guess I triggered a kde 4.2.1 install |
| 9 |
> (I had started the upgrade and decide to wait some weeks ago.) |
| 10 |
> |
| 11 |
> |
| 12 |
> Long story short, I'm now running kde-4.2.1 [OK] |
| 13 |
> |
| 14 |
> I moved my world file to a backup so as to avoid all |
| 15 |
> of those dependency issues. It worked pretty well. |
| 16 |
> However, now I'm adding the packages back a few at a |
| 17 |
> time and lots of stuff calls for kdelibs-3.5.9-r1. |
| 18 |
> |
| 19 |
> |
| 20 |
> Where I'm confused is can I have 2 versions |
| 21 |
> of kdelibs installed at the same time? |
| 22 |
> My gut tells me NO? |
| 23 |
|
| 24 |
Yes, you can. In fact, this is the whole point of SLOTs. The versions are kept |
| 25 |
separate by putting them in different directories. KDE-3.5 stuff always goes |
| 26 |
in /usr/kde/3.5 whereas KDE-4 can go in one of two places depending on the |
| 27 |
setting of the kdeprefix USE flag: |
| 28 |
|
| 29 |
with USE=kdeprefix /usr/kde/4.x |
| 30 |
with USE=-kdeprefix /usr/ |
| 31 |
|
| 32 |
The apps don't get confused becuase when they are built and linked, the |
| 33 |
relevant tools are instructed where the correct libs are. So, KDE-4 apps do |
| 34 |
not get told to link against KDE-3.5 libraries. If they do, then it is a bug. |
| 35 |
|
| 36 |
> What am I missing. Kde-4.2.1 is up and running. |
| 37 |
> Although I have not extensively tested it, I can |
| 38 |
> run konqueror and seamonkey and many other apps. |
| 39 |
> just fine. |
| 40 |
|
| 41 |
As it is supposed to. |
| 42 |
|
| 43 |
> So what I think I need to do (again) is |
| 44 |
> |
| 45 |
> Mask kdelibs 3.5.x completely? |
| 46 |
|
| 47 |
Not really necessary |
| 48 |
|
| 49 |
> (syntax suggestions here for package.mask are welcome) |
| 50 |
> |
| 51 |
> emerge -C kde-3.5.9* (can I do this?) |
| 52 |
> emerge --depclean -a |
| 53 |
> |
| 54 |
> and then watch closely what I emerge? |
| 55 |
|
| 56 |
Honestly, the best way is to just not install stuff that needs kde-3.5 |
| 57 |
packages. I use KDE-4, but I still have kdelibs-3.5 installed - I have a few |
| 58 |
3.5 apps that are not yet ported to 4 (like luma). Getting to this point can |
| 59 |
happen in several ways, depending on how you installed kde-3.5 originally. |
| 60 |
|
| 61 |
1. If you ran 'emerge kde' and have monolithic versions, get rid of them with |
| 62 |
emerge -C (or just delete them out of your world file). |
| 63 |
|
| 64 |
2. If you emerge the kde -meta ebuilds, then unmerge them (or delete them from |
| 65 |
world) |
| 66 |
|
| 67 |
3. If you installed a bunch of kde apps individually, then find them in world |
| 68 |
and delete them. |
| 69 |
|
| 70 |
Now run 'emerge -av --depclean' and closely inspect what portage wants to |
| 71 |
nuke. With luck, it'll be a whole horde of 3.5 stuff, so let it rip when you |
| 72 |
are happy with it. Then run 'emerge -pvuND world' and see if portage wants to |
| 73 |
re-install anything from kde-3.5 (this is indeed highly likely...). Now use |
| 74 |
your various portage tools (q, equery, etc) to find out why portage wants to |
| 75 |
add 3.5 apps back in, and deal with that issue. One at a time. Rinse, repeat |
| 76 |
in a recursive process till 3.5 is gone. |
| 77 |
|
| 78 |
You don't really need to mask anything, unless you are a thick idiot who never |
| 79 |
checks emerge output before giving the go-ahead. Previous posts from you |
| 80 |
suggest that "thick idiot" is not an accurate description :-) |
| 81 |
|
| 82 |
Avoiding having kde-3.5 stuff installed is exactly the same as avoiding having |
| 83 |
firefox installed - don't emerge it. |
| 84 |
|
| 85 |
-- |
| 86 |
alan dot mckinnon at gmail dot com |
Archives