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