1 |
Neil Bothwick wrote: |
2 |
> On Mon, 22 Dec 2008 03:57:22 +0200, Nikos Chantziaras wrote: |
3 |
> |
4 |
> |
5 |
>> And how is putting KDE4 in /usr/kde going to help in this? What |
6 |
>> difference does it make if the wrong path is chosen? Surely, it |
7 |
>> doesn't matter a bit how that path looks like if it's wrong. If a KDE4 |
8 |
>> path would come before a KDE3 path in a KDE3 session, the last thing |
9 |
>> you care about is whether that path is /usr/bin or /usr/kde/4.1/bin. |
10 |
>> |
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 |
> |
18 |
> |
19 |
|
20 |
So to clarify a bit more, for me at least. If you login to KDE 3.5 then |
21 |
/usr/kde/3.5/bin is in your path but not /usr/kde/kde/4.*. The same |
22 |
could be said in the reverse I assume? |
23 |
|
24 |
If you don't use the flag and login to KDE 3.5 then all the KDE 4.* |
25 |
stuff is in your path and anytime you try to open a KDE 3.5 app, it sees |
26 |
the KDE 4.* apps first? Correct? If it is, I can only imagine how |
27 |
confused a computer would be. |
28 |
|
29 |
I wonder if a person could change the order that those paths are |
30 |
searched? Could you put in a config file somewhere to search one first |
31 |
then the others or would that just not work well in the reverse situation? |
32 |
|
33 |
I think I am out of cents again. o~o I'm starting to see why this is |
34 |
so confusing to a computer now. Whew ! |
35 |
|
36 |
Dale |
37 |
|
38 |
:-) :-) |