[debhelper-devel] Bug#204975: [Build-common-hackers] Bug#204975: cdbs: postrm and postinst have useless call to ldconfig

[Loïc Minier]

Hi,

Re-reading this bug – filed 12 years ago – I have to agree with Joey Hess (and I find my own tone from 12 years ago pretty bad, sorry about that!): it’s not a good idea to rely on the contents of /etc/ld.so.conf.

It’s less big a deal than it used to be because of /etc/ld.so.conf.d/* which is where other packages would change the search path, but it’s still an issue because an admin might have changed the local config and this will affect package builds.

> Le 30 sept. 2016 à 02:42, Olly Betts <olly at survex.com> a écrit :
> $ /sbin/ldconfig -N -X -v -f /dev/null 2>/dev/null|sed 's,^\(/.*\):\( (.*)\)\?$,\1,p;d’

This approach looks very good to me; here’s perhaps a lighter sed:
sed -n '/^\//s#:$##p’
(match lines leading with slash, remove trailing colon and print them)

However it might be worth bringing this discussion to Debian Policy as this currently said that /etc/ld.so.conf contents must be used.
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-ldconfig <https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-ldconfig>

Another perhaps smarter approach would be to do away with postinst requirements entirely by installing a ldconfig file-based trigger in libc for *.so files under interesting directories. This would let libc define when to run libc’s ldconfig rather than having each shared library package carry a build-time and install time snippet…

Cheers,
- Loïc Minier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debhelper-devel/attachments/20161002/8a158032/attachment-0001.html>