How are you folks ensuring the Trinity run-time environment variables do not clash with those of the same name in KDE4? I would appreciate a response to this. I intend to start trying to build in the latest Slackware release, which has KDE4 installed. As Slackware no longer supports KDE3, those KDE4 environment variables point to the same locations previously used in KDE3. I'm not looking for the variables used in building --- those variables are documented in the wiki. I'm referring to those variables used in running Trinity. Possibly $KDEHOME is the only one not documented at the wiki. What is the default location for that variable in Trinity? When I build packages for Slackware I suspect I need to define $KDEHOME as $HOME/.trinity or $HOME/.kde3 to avoid conflicts with $HOME/.kde being used by KDE4. Thanks. Darrell --- On Thu, 3/10/11, Darrell Anderson <humanreadable(a)yahoo.com> wrote:

On Tue, Mar 15, 2011 at 4:34 PM, Darrell Anderson <humanreadable(a)yahoo.com> wrote: It doesn't really matter what $KDEHOME is, as long as TDE and KDE4 use a different one to avoid interfering with each other. The only reason to be specific is to stay organized and tell the difference between the two. I'm for $HOME/.trinity for consistency with the name Trinity. -- Kris "Piki" Ark Linux Webmaster Trinity Desktop Environment Packager

<snip> The startkde script primarily determines $KDEHOME IIRC. If there is a secondary default in the code, then it should be set to $HOME/.trinity. If this is not the case, then a bug report should be filed. Tim

I filed bug report 459 against the problem of the Trinity default $KDEHOME location trashing a user's KDE4 profile. I think I have a solution and I'll submit patches, but first here is the basic idea that I ask others to consider and approve/disapprove. 1. To avoid potential conflicts with KDE3 and KDE4 users, $HOME/.trinity will become the Trinity default for $KDEHOME. Many people might have KDE4 and Trinity installed, but I envision people such as developers, packagers, and testers having KDE3 installed too. Possibly then there would be three profile directories. So let's avoid any conflict at all. 2. kstandardirs.h, kstandardirs.cpp, and startkde would be updated to be consistent to $HOME/.trinity. Are there any other locations in the source code that need the same attention? I don't know. 3. As $KDEHOME would then always default to $HOME/.trinity when using Trinity, some quiet automated migration code will be added to startkde. That snippet would run only once. Basically something like this: $KDEHOME=$HOME/.trinity # If $HOME/.trinity exists then skip this one-time migration section. if [ ! -d $HOME/.trinity ]; then # If $HOME/.kde3 exists, probably safe to presume that is from KDE3. Go ahead and migrate that profile. if [ -d $HOME/.kde3 ]; then cp -a $HOME/.kde3 $HOME/.trinity elif [ -d $HOME/.kde ]; then # This is tricky --- ensure this profile directory is NOT KDE4. if [ ! -f $HOME/.kde/share/config/nepomukstrigirc ] && [ ! -f $HOME/.kde/share/config/plasmarc ] && [ ! -f $HOME/.kde/share/config/krunnerrc ]; then # That was three different tests. Probably not a KDE4 profile. Go ahead and migrate that profile. cp -a $HOME/.kde $HOME/.trinity fi fi fi I am not a KDE4 guru. If you can think of more robust tests then please let me know. Darrell --- On Tue, 3/15/11, Darrell Anderson &lt;humanreadable(a)yahoo.com&gt; wrote: