[Henning Makholm] > I have written a Lintian check which attempts to flag instances of > this problem. It looks for ELF objects that flag shared libraries in > the default search path as NEEDED without actually importing symbols > that the library exports. This produces a lot of noise in a case where a package has multiple binaries or libraries (sometimes in multiple packages), and a Makefile that links everything to a common set of libs which not everything needs. Your check flags this correctly, but it can be a real pain to fix, and doesn't usually cause practical problems - particularly the problem Steve writes about. Remember, the granularity of testing migrations and library transitions is not the file or even the binary package, but the source package. For example, I have a case here where everything is linked to libapr and libaprutil, but only some files actually need libaprutil. I could fix this, but is it really worth the bother?
Attachment:
signature.asc
Description: Digital signature