[postgis-tickets] [PostGIS] #3365: Remove code for unsupported GEOS versions

[PostGIS]

#3365: Remove code for unsupported GEOS versions
----------------------+---------------------------
  Reporter:  dbaston  |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.3.0
 Component:  postgis  |    Version:  trunk
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 dbaston - we usually bring this up to vote in postgis-dev, might be good
 to bring it up now and get it out of the way early.

 I'm usually the evil one saying down with history and strk saying -- oh we
 must support GEOS 2.2 - think of all those people stuck on GEOS 2.2 and
 then we settle on one version less than what I want and at least one
 version greater than he wants as a requirement.

 I would like 2.3 to require 3.5.  For several reasons

 1) There is a lot of fixes that just never get backported to older geos
 just cause they are too much hassle. So only serious crashers do.  The
 more people are stuck using the old geos the more burden of backporting
 fixes or people just getting annoyed.  Besides GEOS versions can coexist
 and a newer GEOS from as far back as I can recall is always backward
 compatible with older GEOS minor.

 2) PostGIS 2.3 is probably like a year away (IF we are lucky), so by that
 time, GEOS 3.6 might be out already or close to being out.

 3) We'll have ST_Voronoi which will be yet another function requiring 3.5

 4) I think most package maintainers are shipping 2.2 with GEOS 3.5 already
 -- thanks package maintainers :).

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3365#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.