[postgis-devel] Bumping dependencies versions for PostGIS 3.0

Regina Obe lr at pcorp.us
Sat Dec 1 10:31:12 PST 2018


Postgres to 9.5 is already done.  Raul did it and broke Debbie and Winnie and told me to stop testing 9.4.  I did the final nail by updating the documentation to reflect 9.5 https://postgis.net/docs/manual-dev/postgis_installation.html#install_requirements   :)

 

GEOS 3.7.0 – do we really need to enforce this.  I've got mixed feelings about this one.  I think there are quite a few packages stuck on 3.6, and people using PostGIS 3.0 WAY MORE than I want GEOS 3.7.0 to be a required.  We already have a warning saying – that you will be missing some functionality if using 3.7.  We can augment that to "Missing some enhancements and stability improvements as well".  I'd like to hear what packagers think on this one.  In particular I am concerned about apt.postgresql.org and yum.postgresql.org

As I recall I think they rely on the main distribution for GDAL (and I think possibly GEOS as well).  So I wouldn't want to screw their ability to provide PostGIS 3.0 on older OS versions.

 

I also don't like kicking off 2 versions of GEOS in one release.  PostGIS 2.5, we made GEOS 3.5 the minimum.  Jumping to 3.7, seems cruel.

 

I know Paul is laughing and thinking.  "Ms. Sade thinks that's cruel, we must be in a parallel universe".

 

 

SFCGAL to 1.3.1  - I'm okay with this one especially when we detach postgis_sfcgal from the postgis library.  I think the 1.2 series had some severe issues anyway so a lot of people using 1.2 wouldn't be very happy with it.

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Saturday, December 01, 2018 11:02 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Bumping dependencies versions for PostGIS 3.0

 

I used to be chary about this kind of thing, but since it seems like most use happens via packaging and most packaging happens by building everything in our dependency chain, I think all these sound fine. 

 

P





On Dec 1, 2018, at 4:18 AM, Darafei Komяpa Praliaskouski <me at komzpa.net <mailto:me at komzpa.net> > wrote:

 

Hi,

 

I propose to bump minimum versions to these for PostGIS 3.0:

 

 - Postgres to 9.5. This will make sure KNN is right for anyone using PostGIS 3.0, and BRIN are always present.

- GEOS to 3.7.0. Guarantees that all the GEOS functions are unconditionally present. I also believe some corner case fixes weren't backported to 3.6 branch, but not sure which exactly.

 

- SFCGAL to 1.3.1. This guarantees binary distros will have options to not ship openscenegraph as part of postgis dependencies, and all the SFCGAL functions are unconditionally present.

Thoughts?

-- 

Darafei Praliaskouski
Support me: http://patreon.com/komzpa

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20181201/d0f5f7a6/attachment.html>


More information about the postgis-devel mailing list