[postgis-devel] liblwgeom symbols exported by postgis module

[Sandro Santilli]

So I've tried locally with mixing -release and -version-info so that
we produce (on Linux):

 liblwgeom-2.2.so.2.2.0
 liblwgeom-2.2.so.2 -> liblwgeom-2.2.so.2.2.0
 liblwgeom.so -> liblwgeom-2.2.so.2.2.0

With:

 Library soname: [liblwgeom-2.2.so.2]

How do you like that ?

I haven't access to BSD machines to see what would happen there.
Should I commit the change for broader testing ?

--strk;

On Wed, Sep 30, 2015 at 08:51:26PM +0200, Sandro Santilli wrote:
> On Wed, Sep 30, 2015 at 01:38:21PM -0400, Paragon Corporation wrote:
> 
> > So our liblwgeom versioning should ideally follow our minor versioning as I
> > had originally asked for.
> 
> ...
> 
> > But normally liblwgeom-2.so would always be what you get with 2.2.x
> 
> With the current setup, liblwgeom.so.2 is what you get with any 2.x.x.
> Shall we break the application binary interface, for example by changing
> the type of an argument (think BOX2D vs. GBOX which happened with 2.0.0)
> then we'll have to encode that brokage by changing soname to liblwgeom.so.3.
> 
> As long as changes are backward compatible there's no need to ever
> change the SONAME. This worked for the C-API of GEOS since it was
> introduced, with the single SONAME "libgeos_c.so.1" ever existed from
> GEOS-2.2.0 (2005) to GEOS-3.5.0 (2015).
> 
> That said, if we want to _pretend_ we break the ABI on every Minor
> release (just so not to think about it) I guess we could do that, 
> but what would that buy us, exactly ?
> 
> --strk;