[pkg-bacula-devel] Overriding Lintian warning "unused-shlib-entry-in-control-file"

Sven Hartge sven at svenhartge.de
Mon Dec 10 17:10:59 GMT 2018


Hi!

I've been playing with the shlibs system for the past two days, looking
into library SOnames, how the database library system works with Bacula
and how all that interacts with dpkg-shlibs and I've come to the
conclusion that we can override the unused-shlib-entry-in-control-file
Lintian warning.

I've tried different ways, but it either resulted in broken programs or
broken dependencies.

The Bacula build system explicitly sets the SOname of the library to
exclude the DB flavour (src/cats/Makefile.in, lines 134..147).

I expect all sorts of things breaking if we patch that out, mainly
because all rest of the binaries are just linked with "-lbaccats", again
excluding the flavor.

As far as I can see, if we want to (pointlessly, IMHO) work around this,
we would need to compile nearly all packages separately for each DB
flavour supprted *and* change all the libraries a tool links to each time.

IMHO this Lintian warning is a false positive for the Bacula packages,
which admittedly do some "advanced" stuff with libtool and their libraries.

Comments?

Grüße,
Sven.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20181210/2a355666/attachment.sig>


More information about the pkg-bacula-devel mailing list