libexec (Re: "kde5" or "kf5" ?)

[Alexander Neundorf]

On Thursday 21 February 2013, Alexander Neundorf wrote:
> On Thursday 21 February 2013, David Faure wrote:
> > On Thursday 21 February 2013 18:38:46 Alexander Neundorf wrote:
> > > On Thursday 21 February 2013, David Faure wrote:
> > > > On Wednesday 20 February 2013 22:47:15 Alexander Neundorf wrote:
> > > > > please have a look at the attached patch.
> > > > > Ok to commit ?
> > > > 
> > > > This looks good, but it will break the code, if you don't also update
> > > > the code to look into these paths :)
> > > > 
> > > > Don't forget to run
> > > > perl -pi -e 's,kde5/service,kf5/service,g' `git grep -l kde5/service`
> > > > perl -pi -e 's,kde5/libexec,kf5/libexec,g' `git grep -l kde5/libexec`
> > > > in kdelibs (and plasma-framework?) when you commit.
> > > 
> > > Ah, I didn't expect that to be hardcoded.
> > 
> > Yeah, it's a subdir, and without kstandarddirs we need to write down the
> > subdir name, I don't have a better solution (of course KPlugin*
> > encapsulates that for apps, but in kdelibs itself the subdir name appears
> > in a few places).
> > 
> > > How does
> > > QStandardPaths::writableLocation(QStandardPaths::GenericDataLocation)
> > > actually work, how does it determine the directory ?
> > 
> > That line is basically $XDG_DATA_HOME, on unix.
> > 
> > and standardLocations(GenericDataLocation) is $XDG_DATA_DIRS.
> > 
> > > Via KDEDIRS ?
> > 
> > KDEDIRS is dead in KF5.

Why not have a KF5DIRS variable ?
This is stuff which needs some runtime support, i.e. not "Functional addons", 
so having an environment variable doesn't sound too bad for me.

Alex