Hi,
Lintian informs about the use of ldconfig
in postrm script of libgphoto2. It says even
where to put the cmd. Good!
What I understood reading the manpage is to
put the cmd without options is enough. Is
like this:
libgphoto2-6.postrm
remove)
rm -f /usr/share/hal/fdi/information/20thirdparty/$PACKAGE.fdi || true
rm -f
/usr/share/hal/fdi/information/10freedesktop/10-camera-$PACKAGE.fdi || true
rm -f
/usr/share/hal/fdi/information/10freedesktop/10-camera-$PACKAGE-device.fdi ||
true
ldconfig
;;
Lintian is quiet now.
Debian-policy (8.1.1) says that postinst script also
have to call ldconfig. But lintian is not complaining
about postinst not having it.
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-ldconfig
I put the cmd in libgphoto2-6.postinst:
case "$1" in
configure)
# remove old fdi files
rm -f
/usr/share/hal/fdi/information/10freedesktop/10-camera-$PACKAGE.fdi
rm -f /usr/share/hal/fdi/information/20thirdparty/$PACKAGE.fdi
rm -f
/usr/share/hal/fdi/information/10freedesktop/10-camera-$PACKAGE-device.fdi
ldconfig
;;
Doubts:
- follow the policy and put ldconfig in postinst script
even with lintian saying nothing about this ?.
- run the cmd without options on both cases ? Since
everything seems to be in standard place.
- I received a email (debian-devel) about 'debhelper/9.20151004'
"dh_makeshlibs is now using triggers rather than maintainer
scripts to invoke ldconfig."
"* Lintian in untable + testing is already aware of this
* Lintian has /not yet/ been backported. Lintian from
backports still (incorrectly) reports this an issue."
I have debhelper 9.20151005 and lintian 2.5.37
At mentors site, QA information there is a message about
'postinst-must-call-ldconfig' for libgphoto2-port12. It
doesn't have a postinst script.
Mentors site:
https://mentors.debian.net/package/libgphoto2
http://mentors.debian.net/debian/pool/main/libg/libgphoto2/libgphoto2_2.5.8-2.dsc
regards,
--
Herbert Parentes Fortes Neto (hpfn)
