Bug#513423: lintian: false positive: libmx4j-java source: missing-build-dependency-for-dh_-command

[Russ Allbery <rra@debian.org>]

Raphael Geissert <atomo64+debian@gmail.com> writes:
> Damien Raude-Morvan wrote:
> [...]
>> I'm getting :
>> [...]
>> libmx4j-java source: missing-build-dependency-for-dh_-command
>> dh_nativejava=java-gcj-compat-dev
>> [...]
>> 
>> but libmx4j-java Build-Depends on default-jdk-builddep
>> which in turn Depends on default-jdk
>> which Depends on java-gcj-compat-dev.
>> 
>> I don't want to add explicit B-D on java-gcj-compat-dev package.
>
> That's exactly what you should do; if default-jdk stops depending on
> java-cgj-compat-dev, or default-jdk-builddep stops depending on
> default-jdk, your package will fail to build. You should not rely on
> whether a build dependency pulls another package if you use something
> from that other package.  If it was used only by some component of, for
> example, default-jdk then neither lintian would know you use it nor you
> should depend on it.

In general, I agree with this, but in this specific case, I think this is
the purpose of that package.

Package: default-jdk-builddep
Description: Standard Java or Java compatible build dependencies
 This package points to the build dependencies used to build
 packages requiring a Java or Java compatible Development Kit.

I think the intention of this package is to be a sort of "build-essential"
for Java packages, so one can view the debhelper script as part of its
defined interface.

I think we need to add this one as a special exception.  I'll do that now.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>