when installing KDE 3.5 in addition to existing KDE 3.4.3 installation, found that I'm not able to run KDE 3.4.* applications (basically cannot run KDE 3.4.3) due to $PATH variable is changed. file /etc/env.d/45kdepaths-3.5 puts the variables for KDE 3.5 before variables for 3.4.* from /etc/env.d/46kdepaths-3.4
step to reproduce:
1. install next KDE version
2. try to run previous
expected results: run flawlessly
real results: many application do not work correctly
"dirty hack" I made for my system is described in forum http://forums.gentoo.org/viewtopic-t-421995.html
Actually you should be able to run a kde 3.4 session (by setting XSESSION or using kdm) and inside the 3.4 session the path should be right (see the startkde script).
Have you found other solutions in the meantime?
> Have you found other solutions in the meantime?
unfortunately described solution is incorrect. I gave up to find correct one...
(In reply to comment #2)
> > Have you found other solutions in the meantime?
> unfortunately described solution is incorrect. I gave up to find correct one...
but you can choose to run a kde-3.4 session or a kde-3.5 session, or not?
would it be possible to add a use flag --no-slots (I've seen this on some other package) to all kde builds. I use some kde programs but fluxbox is my window manager. I think updating kde should also make the /etc files that need updating from say 3.4 to 3.5 be detected by etc-update and such.
login manager selection is not an option for me. so is not an acceptable solution for all.
Maybe I don't get it, but if you run a full kde session the path inside the session should be correct. If you are inside a fluxbox session, there must be a way to decide if applications from kde-3.4 or kde-3.5 have precedence, and it seems reasonable to default to the newer version.
This can be changed easily by setting a custom PATH in the script that starts fluxbox, for instance.
kde-3.4.x isn't in portage any more, and if you're going to install more than one kde slot, a) you'd better know what you're doing and therefore b) you can set paths in /etc/env.d/ yourself.