Le Tue, 6 Dec 2011 12:50:07 -0800 (PST),
Darrell Anderson <humanreadable(a)yahoo.com> a écrit :
A check list
of cautions will help people run both in order
to use that baseline for testing.
Currently I am dual booting KDE3 and TDE with mirror
partitions of my base Slackware 13.1. Dual booting is, um,
annoying. I have a couple of user accounts dedicated to
testing. Installing TDE on my primary system would allow me
to test under the exact same conditions without rebooting. I
have a virtual machine with TDE installed, but I can't test
everything there --- such as the video issues I discovered
with the proprietary Nvidia drivers.
I need to run both with reasonable safety. Hence my desire
to encourage some conversation about the topic.
Let me throw a question out to you coders:
Installing TDE alongside KDE should not be a problem with both using
different a $PREFIX.
Will running both concurrently cause conflicts because the various
app names and libraries use the same name?
That is, will be able to run one user account in KDE3 and another in
TDE? Or will all accounts need to exit the desktop before running the
other desktop? Or will be there no conflict because each environment
is linked to different locations.
I didn't do it with KDE3/Trinity but with
KDE4/Trinity I can run a
regular KDE4 session, and a Trinity session as another user either in
another X server or in Xnest; but I can't run both KDE3 and KDE4 as the
same user on different X servers. There is no $PATH conflict since
Trinity automatically adds $PREFIX/bin in top of the $PATH.
But with KDE3/Trinity ld.so may get confused if Tim didn't make the
necessary internal version number upgrades (and it seems libkdecore is
still at 4.2.0 so it's a bad sign… with KDE 4.5 libkdecore is at
version 5.5.0).
Having all accounts exit is a tad better than rebooting, but only a
tad. :)
Opinions?
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting