Package: d-shlibs Version: 0.44 Severity: normal Dear Jonas,
this is the bug report that you asked me for in <http://lists.alioth.debian.org/pipermail/pkg-multimedia- maintainers/2010-June/010668.html>. To sum up, d-devlibdeps simply prints out the corresponding -dev packages for the libraries that the given shared library is linked against. IMHO this is neither right nor common practice. The "dependencies of development library packages" are not necessarily the -dev packages of the libraries that the package in question is linked to. I mean, if libfoo0 is linked against liba0, libb0 and libc0, then liba-dev, libb-dev and libc-dev are *not* necessarily dependencies of libfoo-dev! Imagine what this would mean for e.g. libavcodec-dev. Things are different for static libraries, though. To find out hard dependencies for shared libraries development packages, you should (1) check which headers are included by the public API, (2) check which libraries are referenced by the .pc files and (3) check which libraries are referenced by the .la files. - Fabian -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (550, 'unstable'), (400, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages d-shlibs depends on: ii binutils 2.20.1-11 The GNU assembler, linker and bina d-shlibs recommends no packages. d-shlibs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
