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

[Carsten Leonhardt]

Hi,

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

if I remember right, I've had my own fights with those when I took over
the package maintenance.

There was even a need to manually adapt the package build process every
time a new version was released (c.f. commit
0436818413f4426a843b324b073f8fcb485f5674).

> 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.

In the beginning there were multiple runs of the build process, one for
each supported database. I think Jan Hauke Rahm enhanced the process to
only need one pass.

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

I agree. At the time I took over I wasn't confident enough that
everything is done ok, but we've seen many releases go by without
problems by now.

I'll change it, there are several places I'd adjust in relation to that.

 - Carsten