Re: Lintian package-has-a-duplicate-relation
Russ Allbery <rra@debian.org> writes:
> Andreas Metzler <ametzler@downhill.at.eu.org> writes:
>> rocheml@httrack.com wrote:
>>> Is there a way to force a specific library version known in
>>> ${shlibs:Depends} ?
>>> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
>>> force the library to be upgraded when the primary binary package is
>>> updated.
>> Why would you want to do that?
> Usually because the binaries shipped with the package use internal,
> undocumented interfaces that are not available to the rest of the world
> and hence are not considered part of the SONAME (i.e., upstream doesn't
> bump the SONAME when they change).
Sorry, that's not quite enough. shlibs of course handles changes less
than the SONAME. But I've run into this problem with krb5, which
historically adds a tight dependency between the binaries and the
libraries because the binaries sometimes use internal interfaces
(particularly in libkadm55), and the concept made some intuitive sense to
me. Maybe not, though... even changing internal interfaces used only by
binaries built out of the same package might be worth a bump in shlibs.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: