Odd. I have KDE2.2 and KDE3 running nicely on the same system.
Installation directly from cooker (on a cooker base). Yes, I had to
rename "KDE 3" to "KDE3". I must say however, that I'm confused by the
statement on the PATH setting. The ONLY time that I see the PATH
modified to have /opt/kde3/bin prepended to it, is if I'm running KDE3.
If that weren't done, then I'd be starting KDE2 apps under KDE3 (not
good). Of course I don't use startx, I use the kdm graphical login.
On Sun, 2002-04-07 at 01:17, Borsenkow Andrej wrote:
� ���, 06.04.2002, � 23:34, Robert Fox �������:
> I found this on the news groups - it's very helpful stuff . . .
>
it mostly has been known already. Also in most cases author did not
understand the real reason of problems.
> Maybe it'll help with the packaging . . .
>
You can't have KDE2 and KDE3 on one (Mandrake) system peacefully coexist
even if only because of menu problem. In any case if you do want have
them together and be able to run both KDE2 and KDE3 application you
_must_ compile KDE3 with different KDEHOME by default. Else you can't
run KDE2 applications under KDE3 (they start but fonts are screwed up).
Most of the workarounds in quoted post are not needed. You just need to
remove space from KDE3 session name and remove setting of /opt/kde3/bin
in path by default (God knows why it has been put there at all, I
understand it made life of developer simpler. But not users'). Then you
can normally use startx (or any session manager) to start either of
them.
Desktop issue is true but again it must be handled by default.
-andrej
--
TTFN,
Lonnie Borntreger
