Bug#340934: lintian check for unneeded/transitive shlibs dependencies
Scripsit Jeroen van Wolffelaar
> On Sun, Nov 27, 2005 at 04:30:49AM +0100, Henning Makholm wrote:
> > The check is a bit unorthodox in that it needs to have the referenced
> > libraries present on the host system (where lintian is run) and runs
> > objdump over them to figure out which symbols they export.
> This is, unfortunately, exactly something that I'd really rather not have
> in lintian: different results depending on what you've installed on your
> system. This causes confusion, and for example lintian.debian.org will then
> provide really different results,
Point noted. Lintian.d.o was not quite on my mind here.
> For this case, I'd seek to either run this on the whole archive and provide
> some interface to the results via people.debian.org, or look whether
> piuparts maybe can incorporate something like this
My immediate goal was more to provide an easy way for maintainers to
check for this problem _before_ uploading, rather than running
automated tests over packages that are already in the archive.
How would you think about a package that provided the checker script
as a "third-party drop-in" to Lintian?
Or, arguably cleaner: an explicit option to enable "local" checks,
defined as ones that are designed to work only on the system where the
package has just been built?
> I'm leaving this bugreport open for now to allow other lintian maintainers
> to comment.
If you decide against, please reassign to 'general' rather than
closing. I think we do need some way to check for this, even if
lintian turns out not to be place.
--
Henning Makholm "I ... I have to return some videos."
Reply to: