Re: GEOS 3.5.1/3.6.0
On Wed, Oct 26, 2016 at 06:36:52PM +0200, Sebastiaan Couwenberg wrote:
> osmium (0.0~20160425-e2e4368-2) FTBFS due to the same issue.
> Reported upstream in: https://github.com/joto/osmium/issues/100
> Since osmium has been deprecated in favour of libosmium, a fix for this
> issue is unlikely. But perhaps the fix is easy and we can just patch it.
I think it is time to retire the old Osmium. It has not been supported
for years now and I am not aware of any supported software that still
uses it. If anybody needs it, they can still get it from source. It is
a header-only library after all, so this is not a huge burden.
I don't think it is a good idea to keep it around for another three
years or so until the next stable arrives after Stretch. This is just
too long a time for a software that is already hopelessly out of date.
Especially because it is rather confusing for new users who sometimes
find the old osmium rather than the new libosmium and are confused if
nothing fits the documentation they find on the web.
> libosmium (2.9.0-2) FTBFS due to the same issue too.
> Reported upstream in: https://github.com/osmcode/libosmium/issues/168
The next version of libosmium will deprecate the use of GEOS. As far as
I know, nobody is using it and the approach using the C++ API of GEOS is
wrong anyway, because the GEOS project considers this to be internal and
recommends use of the C API. I have added a check to the code which will
disable building of the parts that use GEOS for versions from 3.6
onwards, so it shouldn't stand in the way of upgrading GEOS, but will
keep working with older GEOS versions.
Jochen
--
Jochen Topf jochen@remote.org https://www.jochentopf.com/ +49-351-31778688
Reply to: