[OE-core] [PATCH 1/7] bitbake.conf: fix definition of ${libexecdir}

Burton, Ross ross.burton at intel.com
Mon Apr 29 16:20:46 UTC 2013


On 29 April 2013 16:52, Enrico Scholz <enrico.scholz at sigma-chemnitz.de> wrote:
>> with buildhistory to verify that nothing else moved around?
> Things *are* expected to move around.  E.g. /usr/lib/openssh/sftp-server
> becomes /usr/lib/sftp-server now.

Right, so don't use Debian as a rationale for this approach.  On Debian:

$ ls /usr/lib/openssh/
sftp-server  ssh-keysign  ssh-pkcs11-helper

For reference, on Fedora this binary is
/usr/libexec/openssh/sftp-server, with the split between dropping
binaries directly into /usr/libexec or using a subdirectory apparently

Every package that I looked at on Debian is using
/usr/lib/[packagenameish]/[binary].  /usr/lib/upower/upowerd.
/usr/lib/telepathy/telepathy-gabble.   I say packagenameish as it's
often changed to be a more general name - i.e. all of the Telepathy
backends use /usr/lib/telepathy.

There are no *executables*, only libraries, in /usr/lib on Debian or Fedora.

I'm really not liking dropping the executables into a directory that
on non-multilib is the same as libdir.  If we want to be like the half
of the world that does the same as Fedora then we can revert back to
/usr/libexec.  Or we can be like the half of the world that does the
same as Debian and use something similar to
${prefix}/lib/$(DEB_SOURCE_PACKAGE) (as used in CDBS and Debhelper):

+export libexecdir = "${exec_prefix}/lib/${BPN}"


More information about the Openembedded-core mailing list