[postgis-devel] PostGIS 2.3 release plans
lr at pcorp.us
Sat Jul 30 20:35:28 PDT 2016
Probably is same for all. It was just geography that got hit first. But I found all of them and renamed.
I'll go ahead and commit now.
Thanks for confirming,
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Giuseppe Broccolo
Sent: Saturday, July 30, 2016 5:22 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PostGIS 2.3 release plans
2016-07-29 20:29 GMT+02:00 Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> >:
I've tested this out and looks generally good. I'm ready to commit, assuming no one has any issues with that (speak now or forever hold your peace), except for one small little thing which I noted in the pull request.
The work as it stands fails our non-extension uninstall test. To resolve this I'd like to rename the operator families to the same name as the operator classes so it's consistent with the rest of our code base and also so I don't have to muck with our perl uninstall generation script. As I mentioned, extension installs don't use this script for uninstall (they just use the built-in uninstall plumbing of extension), but our pre-extension test uses this.
I've already done this locally, so just a Yes that's okay is all I'm looking for or why you are against that.
There is no problem in renaming the OpFamily. Sorry, I've understood that you already proceeded with this. So yes, please rename it (is the problem present just for the geography OpFamily?).
Giuseppe Broccolo - 2ndQuadrant Italy
PostgreSQL & PostGIS Training, Services and Support
giuseppe.broccolo at 2ndQuadrant.it <mailto:giuseppe.broccolo at 2ndQuadrant.it> | www.2ndQuadrant.it <http://www.2ndQuadrant.it>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel