Hi Fabian, On Wed, Jun 30, 2010 at 12:56:50PM +0200, Fabian Greffrath wrote:
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.
Thanks (again) for your input.I do not understand in what situations -dev packages need not depend on -dev packages corresponding to what packages the library links against. As I see it, this is contained in 1st paragraph of Debian Policy ยง8.4.
Perhaps if you elaborate a bit more on your libavcodec-dev example, I may better understand your point?
Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
