17 Feb
2011
17 Feb
'11
8:18 a.m.
On 02/17/2011 07:41 AM, Kristopher Gamrat wrote:
<snip>
I think that is definitely the way to go. Maybe when kdelibs or kdebase gets
built and the install prefix is set: (i.e.
-DCMAKE_INSTALL_PREFIX=${trinity_prefix} where trinity_prefix=/opt/trinity or
/opt/kde3 etc), we set the Trinity autostart directory to:
${trinity_prefix}/share/autostart
I think it is imperative we find a way to prevent the kde4 autostart files from
running when you launch Trinity.
Also, I don't know if this can be handled with a simple modification to the
startup script "startkde" from kdebase? If so then setting the Trinity
autostart
dir when kdebase is built seems like the easy way to handle this.
--
David C. Rankin, J.D.,P.E.
In order to
make Trinity play nicely with an existing kde4 install, can
something be changed in the Trinity code to tell it to ignore all the kde4
autostart files?
Perhaps we can make an autostart directory for Trinity, and have it
use only that?