Dale wrote:
Neil Bothwick wrote:
On Mon, 22 Dec 2008 03:57:22 +0200, Nikos Chantziaras wrote:
And how is putting KDE4 in /usr/kde going to help in this? What
difference does it make if the wrong path is chosen? Surely, it
doesn't matter a bit how that path looks like if it's wrong. If a KDE4
path would come before a KDE3 path in a KDE3 session, the last thing
you care about is whether that path is /usr/bin or /usr/kde/4.1/bin.
Because /usr/bin will always be in your PATH, so even if you are running a
KDE 3 session, KDE4 programs will be loaded. By keeping the separate,not
only from one another but also from other programs, you can ensure that
your PATH includes only KDE3 or KDE4 programs.
So to clarify a bit more, for me at least. If you login to KDE 3.5 then
/usr/kde/3.5/bin is in your path but not /usr/kde/kde/4.*. The same
could be said in the reverse I assume?
If you don't use the flag and login to KDE 3.5 then all the KDE 4.*
stuff is in your path and anytime you try to open a KDE 3.5 app, it sees
the KDE 4.* apps first? Correct? If it is, I can only imagine how
confused a computer would be.
I wonder if a person could change the order that those paths are
searched? Could you put in a config file somewhere to search one first
then the others or would that just not work well in the reverse situation?
That's already the case. /usr/bin comes first in KDE4 sessions, while
/usr/kde/3.5/bin is first in KDE 3 sessions. Same goes for LDPATH.
