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

List:       kde-core-devel
Subject:    Re: Use of bin versus libexec
From:       David Faure <faure () kde ! org>
Date:       2012-09-20 22:13:00
Message-ID: 5445032.PVonScxFVL () asterix ! site
[Download RAW message or body]

On Thursday 20 September 2012 19:36:39 Sune Vuorela wrote:
> On 2012-09-20, Kevin Krammer <krammer@kde.org> wrote:
> > Do you mean $PREFIX/libexec, where $PREFIX will often be /usr (for=20
> > distribution packages)?
> 
> that only works in redhat/fedora land. In other distributiotns, like
> debian and ubuntu, libexec is placed in directories under
> prefix/libdir/libraryname/  -  e.g. /usr/lib/kde4/libexec or
> /usr/lib/utempter/

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).

The problem is that it means one can't move stuff later on. Not sure we need to 
support that, but it's nice when it's possible (e.g. for cases like cross-
compilation).

(KF5 currently uses $PREFIX/libdir/kde5/libexec/kioslave,
I should s/kde5/kf5/ though)

-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5

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