On September 17, 2016 1:51:42 PM GMT+02:00, Mattia Rizzolo <mat...@debian.org>
>On Sat, Sep 17, 2016 at 12:36:01PM +0200, Bas Couwenberg wrote:
>> On September 17, 2016 9:10:56 AM GMT+02:00, Mattia Rizzolo
>> >On Sun, Sep 11, 2016 at 11:08:03AM +0200, Sebastiaan Couwenberg
>> >> 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
>> >> dropping the package is an option. Now is not the time to do that
>> >Why not? Would you like/need a patch for it?
>> Because we've just had a proj transition for which the last rdep only
>migrated to testing today.
>That's really totally irrelevant.
>The package already migrated. More: all rdeps migrated too.
>that transition is done, and the package is just open for business as
>There are no rdeps of libproj-java, so you wouldn't trig any transition
>by removing the package, be it only in kfreebsd or everywhere.
It is relevant, because not building the Java package drops symbols for that
support which strictly speaking is an ABI break of the library requiring a new
At the time of Andreas mail not all rdeps had migrated yet, because today the
I find your lack of attention to detail disturbing.
>> I don't like packaging differences between architectures, so I'm
>> currently doubting whether to drop the Java package entirely or
>> complicate matters by only removing it from the problematic
>I don't personally find such variation across architectures a
>complication that needs to be taken into account as "excessive
>Though if you would be just happy to drop the whole libproj-jave
>from everywhere, that would be just fine to me too.
Based on your hostile attitude I'm not willing to work on this issue. More
friendly people will need to convince me to deal with the proj issue on
Pkg-grass-devel mailing list