Usage of language specific profiles in build dependencies
Please see https://bugs.debian.org/982085
I think it's wrong to encode build dependencies for language stacks that are not
available on some platforms, just using a profile.
Seen in gettext:
default-jdk <!nojava>, maven-repo-helper <!nojava>
and also in db5.3.
A more cooperative usage of such build dependencies can be seen in brltty
collectd gdcm liblouisutdml link-grammar octave opencv openmpi r-base rjava
swi-prolog ucx vtk7 vtk9 z3 and probably other packages.
These dependencies should look like:
default-jdk [!hppa !hurd-i386 !kfreebsd-any]
or
default-jdk [alpha amd64 arm64 armel armhf i386 ia64 m68k mips64el mipsel
powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 x32]
It's also ok to use something like
default-jdk [!hppa !hurd-i386 !kfreebsd-any] <!nojava>
to be able to build with the nojava profile. I also see this used in many mono
related build dependencies.
Having such build dependencies in a package that is a required package for
almost everything isn't helpful.
Matthias
Reply to: