Bug#317082: Not just a dpkg bug

[Frank Lichtenheld <djpig@debian.org>]

On Tue, Jan 24, 2006 at 07:06:47PM +0300, Nikita V. Youshchenko wrote:
> But if ldd does not dislike unresolved libraries, I see no other problems 
> with dropping -l. Library files from non-standard paths won't be found by 
> dpkg anyway, so can't be processed in way other than shlibs.local

shlibs.local isn't even normally needed in this case because dpkg-shlibdeps
happily searchs for _all_ shlibs files below debian/ before attempting
to search for "external" packages.

The problem with shlibs.local is that it easily produces packages
depending on themself since there is no check against that in the
code currently. For other "local" shlibs files dpkg-shlibdeps already
detects if they are from the same package as the executable and ignores
those dependencies.

I somehow doubt that many people know about these differences, though...

> In this sence, new information that comes from ldd finding libraries in 
> LD_LIBRARY_PATH dirs, is useless.

Yeah, I'm still searching for a counter example myself.

Gruesse,
-- 
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/