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
--- On Mon, 3/14/11, Darrell Anderson humanreadable@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Monday, March 14, 2011, 6:32 PM 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@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Thursday, March 10, 2011, 7:49 AM Related to this question, starting X from the command line and from a login manager do not
work
the same. Different set of scripts. Placing the
variables
in, say an xinitrc or profile.d is not a sure bet. The
only
place I see that is consistent across both types of
logins
is the startkde script.
How are you folks ensuring the Trinity environment variables do not clash with those of the same name in
KDE4?
Darrell
--- On Wed, 3/9/11, Darrell Anderson humanreadable@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 12:20 PM IF $KDEHOME is not explicitly defined, what then is the default user profile
directory
location in Trinity?
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net 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
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net 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
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net 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