Bug#480636: lintian: rpath check fails to detect private libraries
Frank Lichtenheld <djpig@debian.org> writes:
> 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.
I think we should allow any directory that's included in the same package.
There's an unfortunate trend of packages linking to "private" shared
libraries in other packages, which has been discussed on debian-devel a
few times and which I think is more questionable. Once there are
cross-package dependencies, it's hard to argue that this is really a
"private" library. However, we may still want to special-case things from
the same source package (not that this is easy to do).
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: