Re: dpkg-scanlibs

[Wichert Akkerman <wichert@cistron.nl>]

Previously Richard Braakman wrote:
> That's not necessarily a bug.  If a package has a shared library, but
> does not want other packages to link to it (for example, if the library
> does not have a stable interface), then it needs no shlibs entry and
> probably shouldn't have one.

It should put a dummy entry in debian/shlibs.local then. The check is
needed to catch errors that have gone undetected so far. An example:

[fog;~/sources/cvs/debian/dpkg2/dpkg-dev/scripts]-7> ./dpkg-shlibdeps.py -vvv /usr/bin/enlightenment 
[.. snip snip ..]
Try to determine which package contains 'libFnlib.so.0' using dpkg
Check if /usr/lib/libFnlib.so.0 is a possible match
Conflicting versions of libungif used, aborting
Checking for library in system defaults shlibs file
Unable to find dependency information for libFnlib.so.0

And indeed:

[fog;~/sources/cvs/debian/dpkg2/dpkg-dev/scripts]-8> ldd /usr/bin/enlightenment | grep ungif
        libungif.so.4 => /usr/lib/libungif.so.4 (0x40126000)
	libungif.so.3 => /usr/lib/libungif.so.3 (0x40388000)


Wichert.

-- 
  _________________________________________________________________
 /       Nothing is fool-proof to a sufficiently talented fool     \
| wichert@cistron.nl                  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |