KStandardDirs and Autopackage

Arend van Beelen jr. arend at auton.nl
Fri May 14 17:39:21 BST 2004


Good idea. The only thing I don't really get is, won't this inflate your path 
and the other environment variables, even when the application is removed? 
I'm not very familiar with klauncher though, so if it automatically solves 
this, please forgive me for asking ;)

Arend jr.

On Friday 14 May 2004 18:20, Klas KalaƟ wrote:
> Hi folks - sorry I don't reply correctly to the thread, but I only read it
> on lists.kde.org and don't have the mails handy
> The thread was about putting an application in a self contained dir. The
> question popped up how one could register it correctly with KDE so that it
> appears in the KMenu and such.
> The proposed solution was to use symlinks, but symlinks need to be removed
> again and result in quite some clutter. There is a better way to achieve
> this. After all, this is KDE, right ? ;-)
> I build a small script which does something similar: It adds self-contained
> applications to the KDE environment, please have a look at the attachement
> What it basically does is that it sets the environment variables, registers
> them via DCOP with klauncher and calls kbuildsycoca. Voila - everything is
> groovy :-)
> Your application is in its own folder, yet you can access it from KDE
> without logging out or creating symlinks or such :-)
> Regards,
>   Klas
> PS: I really love autopackage and am dying to see version 1.0!

Arend van Beelen jr.

For nature hates virginity, I wish to be touched.
-- Nightwish

More information about the kde-core-devel mailing list