Because I have been performing a PkgUser build, I have
noticed, when coming to install Xen, that Eudev appears
to install its two PkgConfig files in seperate locations.
pkg xen:xen-master> ls -l /usr/lib/pkgconfig/
-rw-r--r-- 1 eudev eudev 503 Mar 24 11:29 libudev.pc
pkg xen:xen-master> ls -l /usr/share/pkgconfig/
-rw-r--r-- 1 eudev eudev 95 Mar 24 11:29 udev.pc
FWIW, the reason that this comes to light is that Xen, by
default, was looking to install its PkgConfig files into
the latter, however, as that directory had been created by
the Eudev PkgUser, it couldn't write files there.
If, after the configure step has been preformed, I look
at Eudev's
src/udev/Makfile
I can see that Eudev apparently makes a distinction between
a "pkgconfiglibdir" and a "sharepkgconfigdir", vis:
...
pkgconfiglibdir = /usr/lib/pkgconfig
prefix = /usr
program_transform_name = s,x,x,
psdir = ${docdir}
rootlibdir = /lib
rootlibexecdir = /lib/udev
rootprefix =
rootrundir = /run
sbindir = /sbin
sharedstatedir = ${prefix}/com
sharepkgconfigdir = ${datarootdir}/pkgconfig
...
and the latter of Eudev's PkgConfig files being installed into
against the sharepkgconfigdir.
Should LFS modify its install of Eudev, so that both PkgConfig
files end up in the pkgconfiglibdir, which is where every other
package that gets installed appears to place them ?
I have to say that,whilst I have followed the FHS over the years,
I've never quite worked out why /usr/lib/pkgconfig seems to have
gained favour, as PkgConfig files are not "libs" and can provide
non-lib info, as opposed tobeing below /usr/share.
Perhaps though, this is one for the Eudev developers to come slean
about, given that they so appear to have made a distinction between
a PkgConfig file for a "lib" and one for a "utility", by seperating them ?
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
