| 1 |
On Monday 13 April 2009 19:14:25 Dale wrote: |
| 2 |
> Paul Hartman wrote: |
| 3 |
|
| 4 |
> > I would suggest totally getting rid of everything KDE3 related before |
| 5 |
> > trying to go KDE4... I also had lots of problems and conflicts with |
| 6 |
> > both installed. Once I got rid of all traces of KDE3 and started |
| 7 |
> > "fresh" with KDE4, it has been working well. |
| 8 |
> |
| 9 |
> I suspect using the kdeprefix USE flag would fix a lot of that. |
| 10 |
|
| 11 |
No it won't. It just moves different things around in your PATH and you have |
| 12 |
the same basic problem with problematic things having a different name. |
| 13 |
|
| 14 |
USE="kdeprefix" will install KDE-4 into /usr/kde/<slot> just like 3.5 always |
| 15 |
did. You still have to manipulate your PATH so that the install dir for the |
| 16 |
version you are using comes before other versions and /usr/ itself. |
| 17 |
|
| 18 |
USE="-kdeprefix" will install KDE-4 into /usr/ just like the vast majority of |
| 19 |
apps in portage do. In this case you have to ensure that /usr/ is FIRST in |
| 20 |
your PATH before other KDE slots (otherwise the loader will find the wrong |
| 21 |
version of identically named KDE apps from other versions first). This |
| 22 |
approach is sensible as it's a bit pointless having more than one KDE-4 |
| 23 |
version installed. How many bash versions do you have? |
| 24 |
|
| 25 |
The kdeprefix USE flag is not the problem. |
| 26 |
The handling of the PATH is the problem. |
| 27 |
|
| 28 |
-- |
| 29 |
alan dot mckinnon at gmail dot com |
Archives