On 08/01/02 12:41 -0800, Russ Allbery said ...
> *-dbg packages should depend on the package for which they're providing
> debugging symbols, generally with an (= ${binary:Version) dependency,
> to ensure consistency between the debugging symbols and the package.A stronger check would be to check if the files installed by a -dbg package in the /usr/lib/debug directory are present in one of the packages that it depends on. Both the packages would be a created from the same source package, so this wouldn't be an "external" check. e.g. if libfoo0-dbg installs /usr/lib/debug/usr/lib/libffoo.so.0.0.0 then /usr/lib/libffoo.so.0.0.0 should be installed by one of the packages that libfoo0-dbg depends on (and built from the same source package as libfoo0 was built from). I was looking at the flickcurl source package and noticed that the libflickcurl0-dbg has symbols for /usr/bin/flickcurl and /usr/bin/flickrdf but both these binaries are in the flickcurl-utils package and not in the libflickcurl0 package. But libflickcurl0-dbg declares a Depends only on libflickcurl0. The intention here was to probably provide debugging symbols only for libflickcurl0. Hence the motivation for this followup comment. Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/
signature.asc
Description: Digital signature
