IF $KDEHOME is not explicitly defined, what then is the default user profile directory location in Trinity?
Darrell
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
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
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
On Tue, Mar 15, 2011 at 4:34 PM, Darrell Anderson humanreadable@yahoo.com 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" =============================================
Should the comment be updated or the code in kstandardirs.cpp?
With all the branding issues that have arised, is $HOME/.kde3 a good choice? Or should the default be changed to $HOME/.trinity?
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.
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@gmail.com wrote:
From: Kristopher Gamrat pikidalto@gmail.com Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 15, 2011, 5:14 PM On Tue, Mar 15, 2011 at 4:34 PM, Darrell Anderson humanreadable@yahoo.com 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"
=============================================
- Should the comment be updated or the code in
kstandardirs.cpp?
- With all the branding issues that have arised, is
$HOME/.kde3 a good choice? Or should the default be changed to $HOME/.trinity?
- 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@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
On Tue, Mar 15, 2011 at 4:34 PM, Darrell Anderson humanreadable@yahoo.com 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.
<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
Yes, startkde tries to check this variable. If not already explictly set, startkde presumes to set the variable to $HOME/.kde.
That will trash the user's KDE4 profile even if the OS does not explictly define $KDEHOME because $HOME/.kde is the default profile location for KDE4.
Further, the default in startkde conflicts with kdelibs/kdecore/kstandardirs.cpp.
Bug report 459 filed.
Darrell
--- On Tue, 3/15/11, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 15, 2011, 5:55 PM
On Tue, Mar 15, 2011 at 4:34 PM,
Darrell Anderson
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.
<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
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
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@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 15, 2011, 6:19 PM Yes, startkde tries to check this variable. If not already explictly set, startkde presumes to set the variable to $HOME/.kde.
That will trash the user's KDE4 profile even if the OS does not explictly define $KDEHOME because $HOME/.kde is the default profile location for KDE4.
Further, the default in startkde conflicts with kdelibs/kdecore/kstandardirs.cpp.
Bug report 459 filed.
Darrell
--- On Tue, 3/15/11, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] $KDEHOME To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 15, 2011, 5:55 PM
On Tue, Mar 15, 2011 at 4:34 PM,
Darrell Anderson
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.
<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
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
-
Darrell Anderson -
Kristopher Gamrat -
Timothy Pearson