Re: [trinity-devel] $KDEHOME

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 <humanreadable(a)yahoo.com> wrote: