KDE-Forum.org

Quoted

Using Suse 9 with KDE 3.2, is there any way to integrate an application (menu shortcuts, file associations, etc) with a user's KDE destop which does NOT involve any copying or linking of desktop files and icons to /opt/kde3/share/... or $HOME/.kde/share/... or anywhere else. In other words, can a user simply expand the search path for desktop integration files to more than these directories?

On Redhat 9 with KDE 3.1, for example, we use the KDEDIRS path variable to do this, so that the desktop files, icons etc only reside in our application installation directory $MYAPP/share/... and a user only needs to append $MYAPP/share to their KDEDIRS path variable, if they want to integrate our application with their KDE desktop. This makes desktop integration (or nonintegration), uninstallation, updating of our app more manageable both for us and users.

The KDEDIRS approach doesn't seem to work with SUSE 9 and KDE 3.2. Is there another way?

Quoted

I found that the reason adding $MYAPP/share to KDEDIRS doesn't work as expected under SUSE is that KDEDIRS is unset in SUSE's modified version of the startkde script (/opt/kde3/bin/startkde), which, of course, is executed after a user's .profile is read. Changing KDEDIRS after KDE is already started has no effect. If I undo SUSE's change to the startkde script, everything works as documented for KDEDIRS.

Why does SUSE modify KDE's startkde script in this way? Makes no sense to me.