On Sun, Sep 11, 2016 at 11:08:03AM +0200, Sebastiaan Couwenberg wrote: > On 09/11/2016 12:32 AM, Andreas Beckmann wrote: > > Or is it possible to just not build libproj-java on kfreebsd*? > > Removing proj from kfreebsd* would affect a lot of packages: > > libproj-java doesn't have reverse dependencies are a very low popcon, so > dropping the package is an option. Now is not the time to do that though.
Why not? Would you like/need a patch for it?
> Since kfreebsd-* isn't a release architecture any more, this kind of
> breakage is expected. hurd-i386 and x32 have similar issue for example.
[whereas both hurd-i386 and x32 built just fine...]
> Because maintainers don't care enough about the ports essential GIS
> packages cannot be built. And apparently the porters don't care enough
> either to assist the maintainers to get the packages fixed on those
> architectures.
The difference between kfreebsd/hurd and i.e. x32 is that they live on
ftp-master. Being on ftp-master means they get to be under the radar of
several QA people, and are tracked during transitions in the transition
trackers, and hinder decrufting of old libraries.
Could you please explain why it wouldn't be possible for you to make
libproj-java building only on 'linux-any hurd-any'?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
