I am for $HOME/.trinity as well. That avoids all potential conflicts.

That would be the default for when $KDEHOME is not explictly defined by the OS.

If we go that route we should have some kind of simple automated migration tool to copy /duplicate $HOME/.kde settings to $HOME/.trinity, but the code needs some sanity checks to ensure the profile is from KDE3 and not KDE4.

Another potential conflict is what happens when the OS uses KDE4 and explictly defines $KDEHOME. The current Trinity code will use that envrironment variable and trash the user's KDE4 settings. Not good.

Darrell


--- On Tue, 3/15/11, Kristopher Gamrat <pikidalto@...> wrote:

> From: Kristopher Gamrat <pikidalto@...>
> Subject: Re: [trinity-devel] $KDEHOME
> To: trinity-devel@...
> Date: Tuesday, March 15, 2011, 5:14 PM
> On Tue, Mar 15, 2011 at 4:34 PM,
> Darrell Anderson
> <humanreadable@...>
> wrote:
> > I don't read c++ very well. Seems to me that if
> $KDEHOME is not explicitly defined then Trinity defaults to
> $HOME/.kde3. Yet the comments in kstandardirs.h declare
> $HOME/.kde as the default.
> >
> > =============================================
> > kdelibs/kdecore/kstandardirs.cpp:
> > =============================================
> > if (!localKdeDir.isEmpty())
> > {
> >    if (localKdeDir[localKdeDir.length()-1] !=
> QChar('/'))
> >      localKdeDir += QChar('/');
> > }
> > else
> > {
> >    localKdeDir =  TQDir::homeDirPath() +
> "/.kde3/";
> > }
> > =============================================
> >
> > =============================================
> > kdelibs/kdecore/kstandardirs.h:
> > =============================================
> >  * @li KDEHOME: The directory where changes are saved
> to. This directory is
> >  *          used to search for resources first.
> If KDEHOME is not
> >  *          specified it defaults to
> "$HOME/.kde"
> > =============================================
> >
> > 1. Should the comment be updated or the code in
> kstandardirs.cpp?
> >
> > 2. With all the branding issues that have arised, is
> $HOME/.kde3 a good choice? Or should the default be changed
> to $HOME/.trinity?
> >
> > 3. Trinity is supposed to be compatible with KDE4. In
> KDE4 the default for $KDEHOME is $HOME/.kde. Seems then that
> if $KDEHOME is explicitly declared in a KDE4 environment
> that Trinity will trash a user's KDE4 settings. Seems the
> best way to avoid any mess is to use a default $KDEHOME
> setting like $HOME/.trinity or $HOME/.kde3. I prefer the
> former as that avoids potential conflicts with older KDE3
> systems too.
> >
> > I think this issue needs attention.
> >
> > Darrell
> 
> 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
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> 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
> 
>