On Fri, Mar 4, 2011 at 12:06 PM, David C. Rankin <drankinatty@...> wrote: > On 03/03/2011 10:51 PM, Kristopher Gamrat wrote: >> On Thu, Mar 3, 2011 at 5:06 PM, David C. Rankin >> <drankinatty@...> wrote: >>> Guys, >>> >>> Just a note. After going through nightmares early on with kdelibs and kdebase >>> pulling in Qt4 files, I have gotten trinity to build fine with Qt4 installed on >>> arch. I'm not sure what has changed. Whether there were updates to cmake files >>> that helped or whether it was not having kde4 installed that makes the >>> difference. However, with Qt4 installed, I can now build trinity without conflicts. >> >> I'm leaning toward cmake updates. KDE4 shouldn't interfere with >> building TDE (other than to take up extra memory when loaded that >> could be used to speed up building), unless you are trying to install >> them to the same directories. They are supposed to be able coexist >> with each other -- just make sure that you are using a different >> directory to install TDE than is used for KDE4. >> > > I don't know about currently installing kde4 along side trinity (at least on > Arch) For some reason starting trinity with kde4 present causes all the > autostart files in /usr/share/autostart to be executed resulting in the kde4 > plasma panel to load on top of the trinity kicker and nepomuk/akonadi, etc. to > be started. > > I know trinity will run along side kde4 because Albert's 3.5.12 build for Arch > (updated kdemod3) runs fine with kde4 present. We will have to look at how that > is modified to handle kde4. > > Albert, if you know, please chime in :) If Albert has a patch to fix it, it may be worth submitting to the bugtracker (see if the bug is filed first, I haven't visited in awhile). -- Kris "Piki" Ark Linux Webmaster Trinity Desktop Environment Packager