Bug#553109: guile-gnutls: postinst-must-call-ldconfig /usr/lib/libguile-gnutls-v-1.so.0.0.0 by the dynamic library loader. Therefore, the package must call "ldconfig" in its postinst script.
Andreas Metzler
ametzler at downhill.at.eu.org
Sat Oct 31 07:07:24 UTC 2009
On 2009-10-29 Manoj Srivastava <srivasta at debian.org> wrote:
> On Thu, Oct 29 2009, Andreas Metzler wrote:
> > These are not proper shared libraries but are dlopened bindings for
> > guile, which takes them outside the scope of the abovementioned part of
> > policy.
> Then should they not be in a private path?
This seems to be a project for guile-1.9. As Simon already noted using
/usr/lib/ is current practice.
> As long as they are
> in the public library directories, you are still under the policy
> directive, as far as I can see.
Why? Shouldn't intent matter more than than binary format? Does
running ldconfig provide any benefit?
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
More information about the Pkg-gnutls-maint
mailing list