[postgis-devel] PostGIS 2.5 what should be minimum requirements?

Mateusz Loskot mateusz at loskot.net
Sat Sep 30 10:09:16 PDT 2017


On 30 September 2017 at 16:19, Greg Troxel <gdt at lexort.com> wrote:
> "Regina Obe" <lr at pcorp.us> writes:
>>>On 09/29/2017 06:28 PM, Darafei "Kom?pa" Praliaskouski wrote:
>>>> Please don't hesitate to raise minimum versions to latest released at
>>>> the time of release.
>>>> If someone needs an older version, they are free to comment out the
>>>> checks and build at their own risk.
>>>> Otherwise we're going to have distros with older versions of
>>>> libraries, because "it's not required to upgrade so let's not".
>>
>>> Or distributions are forced to stick to older versions of the
>>> libraries because the newer versions cannot be integrated properly
>>> with all their reverse dependencies. As is currently the case for
>>> GEOS >= 3.6.
>>
>> That's why I'm not pushing GEOS >= 3.6.  I know that packagers at
>> least in past had issue with upgrading GEOS 3.6 because of osm2pgsql
>> referencing c++ apis instead of geos c-api.
>> Though I thought that issue was resolved since.  Perhaps not.
>
> There isn't agreement about whether it is a bug for packages to use the
> GEOS C++ API.  If it really is a bug, GEOS is buggy for installing the
> headers.

Please, can we stop this heresy?
I'm tired of explaining GEOS C++ API status.


Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net



More information about the postgis-devel mailing list