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

List:       kde-core-devel
Subject:    Re: Use of bin versus libexec
From:       Jonathan Marten <jjm2 () keelhaul ! demon ! co ! uk>
Date:       2012-09-26 9:42:07
Message-ID: ov627186j4.fsf () keelhaul ! local
[Download RAW message or body]

After a lot of discussion, is seems that there are some executables
(as per Thiago's list) that can be moved out.  For others
(e.g. Akonadi) it is problematic because there is no standardization
on the location for a "system-wide" libexec as per David's comments
below, so they will have to stay unless a better solution can be
found.

I'm willing to do some work on those that can be moved, but would it
be acceptable to do such changes (in trunk) at this stage - or would
they have to wait for the next major release (i.e. "KDE 5")?

Regards, Jonathan


David Faure <faure@kde.org> writes:
> We really need a FHS addition for libexec.
> Due to the current mess, QStandardPaths::findExe can't look into libexec, so 
> the only way to find stuff there is to compile the install prefix into the 
> library (that's what I do in KF5 for now).

-- 
Jonathan Marten                         http://www.keelhaul.demon.co.uk
Twickenham, UK                          jjm2@keelhaul.demon.co.uk
[prev in list] [next in list] [prev in thread] [next in thread]