Re: Useless call to ldconfig and shared libraries issue

[Jakub Wilk <jwilk@debian.org>]

* Corentin Desfarges <corentin.desfarges@gmail.com>, 2015-01-23, 21:27:
> I'm still working on the packaging of fw4spl (a medical software) for 
> the Debian-Med project [1], and I'm faced to an issue for a few days. 
> I've this lintian warnings ;
>
> W: fw4spl: postinst-has-useless-call-to-ldconfig
> W: fw4spl: postrm-has-useless-call-to-ldconfig
>
> and I don't understand why. Here are the two concerned scripts :
>
> https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=debian-med/fw4spl.git;a=blob_plain;f=debian/postinst;hb=HEAD
>
> https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=debian-med/fw4spl.git;a=blob_plain;f=debian/postinst;hb=HEAD
>
>
> It works like it but I get the two lintian warnings. I did these 
> operations 

By "these two operations" you presumably mean

	sh -c "echo '/usr/lib/fw4spl' > /etc/ld.so.conf.d/fw4spl.conf"

and

	rm /etc/ld.so.conf.d/fw4spl.conf

(To be clear, those are NOT the commands Lintian is complaining about. 
The allegedly useless calls to ldconfig were automatically generated by 
debhelper.)

This is incorrect. You must not put anything to /etc/ld.so.conf.d/. This 
directory is reserved for glibc and for the system administrator.

Moreover, the postrm script is not idempotent, which is also a serious 
bug.

> because the shared libraries weren't found by ldconfig.

Could you explain what exactly was wrong?

--
Jakub Wilk