Frank Lichtenheld wrote: > Yeah, that's indeed a problem. But that isn't solved by the current > implementation either. When I think about it there is now way the > -l option (if pointing to a directory that is not known to dpkg) > changes anything about the build currently since the local shlibs > information is considered before using the ldd paths. And the ldd paths > are only used in conjunction with dpkg --search ... > The only thing it does is supressing the error "couldn't find path for > X". You're right. BTW, dpkg-shlibdeps -l does not seem to be documented in its manual page or help text ATM. -- see shy jo
Attachment:
signature.asc
Description: Digital signature