KDE4 Patch to allow testing/execution of uninstalled kparts/XMLGUI applications

Adam Treat treat at kde.org
Tue Aug 9 02:30:53 BST 2005


On Monday 08 August 2005 9:17 pm, David Faure wrote:
> On Monday 08 August 2005 22:52, Hans Meine wrote:
> > 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 = .
>
> Very cool.
>
> > > 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 ;)
>
> What's "a parameter" in this context? Do you mean something in the file,
> or a command-line argument?

I understood it to mean a new command line argument that would specify 
the .krcdirs filename.  This way, if the flag isn't present, everything takes 
place as normal.  I can't really see where this is a big security 
improvement, but I could take this approach instead, rather than use the 
current working directory...  

It wouldn't mean anything other than the app would have to be executed with 
the a '--resources' command line parameter in order to run locally...  Does 
this sound better to you, David?  Or do you think we should just go with the 
CWD?

Adam

-- 
I'm running a Marathon in December!
HELP ME SAVE LIVES and Donate Today!
http://helpmesavelives.blogspot.com/




More information about the kde-core-devel mailing list