Bug#480636: lintian: rpath check fails to detect private libraries

[Frank Lichtenheld <djpig@debian.org>]

On Sun, May 11, 2008 at 11:10:06AM +0200, Aurelien Jarno wrote:
> But lintian outputs a warning anyway for private libraries:
> 
> | W: libc6: binary-or-shlib-defines-rpath ./usr/lib/gconv/EUC-CN.so $ORIGIN
> | W: libc6: binary-or-shlib-defines-rpath ./usr/lib/gconv/EUC-JISX0213.so $ORIGIN
> | W: libc6: binary-or-shlib-defines-rpath ./usr/lib/gconv/EUC-JP-MS.so $ORIGIN
> | ...
> 
> It probably misses the point that $ORIGIN in an rpath means the same
> directory as the current library, which is here a private directory.

Even if we would expand the $ORIGIN, lintian would currently output the
warning, since it only allows for a very narrow definition of private
directories currently:

grep { !m,^/usr/lib/(games/)?\Q$pkg\E(?:/|\z), } split(/:/, $RPATH{$file})

After looking over the tag page at lintian.debian.org I think we should
consider allowing any subdirectories below /usr/lib instead of only the
package name itself.

Then we can worry about the $ORIGIN support.

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