I had problems in Slackware with the 3.5.13 startkde script. Biggest problem was starting
KDE 4 apps on its own because $KDEDIRS was explicitly declared in the script and
hard-coded to include /usr/share. That variable is intended to be user defined and should
not be hard-coded in Trinity.
Second problem was duplication of several snippets of code.
Third problem was snippets of code that never got executed because a previous condition
was satisfied.
Fourth problem was the $XDG_DATA_DIRS path. I raised this issue in a previous post. I want
the option of whether KDE4 apps appear in my Trinity menu. I can solve that problem easily
in Slackware for both types of people using /etc/profile.d scripts. I don't know how
other distros would handle that when there is no support for /etc/profile.d. I don't
think this variable should be hard-coded in startkde unless completely undeclared.
So I added conditions to set these variables only if they don't include Trinity
paths.
I don't want to submit this (yet) as a bug report. I would be grateful if some of you
would test this new script in your distro.
I suspect we need more work with this script in order to function correctly in all
distros. We probably need a lot of conditional tests.
Here are links to an updated script --- a patch and full script.
http://humanreadable.nfshost.com/trinity/patches/kdebase/startkde.diff
http://humanreadable.nfshost.com/trinity/patches/kdebase/startkde.new
The patch allows you to quickly see the changes and the full script is there for easier
copying to your system.
Darrell