[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE4 Patch to allow testing/execution of uninstalled
From:       Hans Meine <hans_meine () gmx ! net>
Date:       2005-08-08 20:52:09
Message-ID: 200508082252.09671.hans_meine () gmx ! net
[Download RAW message or body]

Hi!

On Monday 08 August 2005 21:41, Friedrich W. H. Kossebau wrote:
> > I have a simple patch to KStandardDirs that will allow developers to test
> > and run KParts/XMLGUI applications without having to install them first.
> >
> > What I've done is to simply look for a '.krcdirs' file in the same
> > directory where the application is currently being executed.  This file
> > is a simple INI file like so:
> >
> > [KStandardDirs]
> > module = .libs
> > data = .
>
> With shell commands you have to explicitly state that you want to use the
> executable of the current directory. I think this security approach should
> also be taken here (think e.g. of the libs). Better add a parameter to
> state the explicit wish for the usage of the local settings. Adds some
> little burden, but so does "./", too. (no free lunch, isn't there ;)

Maybe I am blind, but what's the advantage compared to 
KDEDIRS="`pwd`/my_locally_setup_tree:$KDEDIRS"?
Is it just for convenience?
Is is much less work to setup such a file than a KDEDIR?
Is it worth the slight ugliness factor that cwd-approaches have under UNIX?

-- 
Ciao, /  /                                                    .o.
     /--/                                                     ..o
    /  / ANS                                                  ooo
[prev in list] [next in list] [prev in thread] [next in thread]