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

[Paul Ramsey]

Please, take liblwgeom out, so I can rename our internal functions postgiscore and end this long national nightmare...

P.

> On Jul 30, 2015, at 8:21 AM, Sandro Santilli <strk at keybit.net> wrote:
> 
>> On Thu, Jul 30, 2015 at 05:09:00PM +0200, Sebastiaan Couwenberg wrote:
>> 
>> I don't think linking the libtool version-info to the postgis version in
>> this way is correct. The changes in r13855 for PostGIS 2.18 result in
>> -version-info 3:1:8 which is an invalid value as documented in the
> 
> You might have misread the code.
> For version 2.1.8, the version info would be 3:8:1,
> as in <current>:<revision>:<age>
> 
>> I sugges to start with -version-info 2:0:0 in PostGIS 2.2.0, and keep
>> the libtool versioning of liblwgeom separate from the PostGIS version.
> 
> It might be better to postpone this to when liblwgeom gets
> its own release cicle.
> 
> --strk; 
> 
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel