[postgis-devel] For PostGIS 2.2 moving forward make liblwgeom compatible between micro releases

[Bborie Park]

I'm hesitant about providing guarantees across major versions at the
library level. This restricts how development to benefit PostGIS may
proceed. I have no problem about guarantees at the minor level as they
should only contain bug fixes...

Decoupling liblwgeom from PostGIS, though it sounds nice, may not be in the
best interest of the PostGIS project (overhead, divergent
interests/requirements). I think providing stable/predictable access to the
library is a nice to have, not a requirement. For me, the same is true for
librtcore...

-bborie

On Tue, Jul 28, 2015 at 11:04 AM, Paragon Corporation <lr at pcorp.us> wrote:

> Markus,
>
> I think backwards-compatibility guarantees we can work on.  As strk said,
> Sandro hope I'm not shoving you too much in a cubby hole -- I think for
> PostGIS minors we can give some assurance the api won't change.
>
> However decoupling from PostGIS would be at least in my mind, difficult,
> since much of the logic of PostGIS is embedded in liblwgeom.  Perhaps when
> we move to Git we can have it as a sub-repo and then the decoupling at some
> level will be easier, albeit it would probably still be very much in line
> with PostGIS releases.
>
>
> Sandro, Paul, Bborie, Nicklas -- any comments on my assumptions here?
>
> Thanks,
> Regina
>
>
>
>
>
> -----Original Message-----
> From: Markus Wanner [mailto:markus at bluegap.ch]
> Sent: Tuesday, July 28, 2015 2:03 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>;
> Paragon Corporation <lr at pcorp.us>
> Subject: Re: [postgis-devel] For PostGIS 2.2 moving forward make liblwgeom
> compatible between micro releases
>
> On 07/20/2015 05:45 PM, Sandro Santilli wrote:
> > But given Spatialite is already using liblwgeom, I don't think PostGIS
> > statically linking to it makes it any less interesting for packagers
> > to ship it as a separate package.
>
> Speaking for Debian, we've already gone through the liblwgeom packaging,
> reverting that won't buy us anything (but rather pose issues with
> spatialite, I guess).
>
> I'd rather like to see liblwgeom becoming *less* coupled with Postgis and
> instead providing a more stable API and/or some sort of
> backwards-compatibility guarantees.
>
> Regards
>
> Markus Wanner
>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150728/055ee349/attachment.html>