[postgis-devel] GEOS changes breaking PostGIS testcases

[Paul Ramsey]

Or 2.0.4 requires a MAXIMUM of 3.3.x. Just totally segregate the change.
P.


-- 
Paul Ramsey
http://cleverelephant.ca
http://postgis.net


On Thursday, May 30, 2013 at 3:20 PM, dustymugs wrote:

> On 05/30/2013 01:36 PM, Sandro Santilli wrote:
> > FYI: I've committed improvements for the GEOS snapping algorithm, so that
> > ST_Snap is less likely to return invalid (collapsed) geometries.
> > 
> > Unfortunately some of the topology tests in PostGIS are expecting
> > outputs due to collapses and thus will now fail until tweaked.
> > 
> > I'm planning to change the expectances to match the new GEOS results
> > but of course doing so would mean the tests will fail with latest
> > GEOS release instead. Better ideas ?
> > 
> > Ticket: http://trac.osgeo.org/postgis/ticket/2346
> > 
> > --strk; 
> 
> I'd guess that this wouldn't be a problem for 2.1 since that version
> requires GEOS 3.4. As for 2.0, can we require a specific GEOS version
> for a minor version of PostGIS? Such as 2.0.4 requires GEOS 3.4?
> 
> -bborie
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org (mailto:postgis-devel at lists.osgeo.org)
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel