Re: Usage of language specific profiles in build dependencies

2021-02-11 Thread Thorsten Glaser
Hi Paul, > FTBFS) but it avoids busywork for maintainers that are not involved in > bootstrapping java. Machine time is cheap, volunteer time is not. this is not for bootstrapping. This is to prevent building of language bindings for e.g. Java on platforms where there is simply no Java. This is

Re: Usage of language specific profiles in build dependencies

2021-02-11 Thread Matthias Klose
On 2/11/21 10:40 AM, Paul Gevers wrote: > Hi, > > On 11-02-2021 10:16, Matthias Klose wrote: >> 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

Re: Usage of language specific profiles in build dependencies

2021-02-11 Thread Paul Gevers
Hi, On 11-02-2021 10:16, Matthias Klose wrote: > 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

Usage of language specific profiles in build dependencies

2021-02-11 Thread Matthias Klose
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 , maven-repo-helper and also in db5.3. A more cooperative usage of such build