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

[Sandro Santilli]

On Wed, Aug 05, 2015 at 12:44:28PM -0400, Greg Troxel wrote:
> 
> Sandro Santilli <strk at keybit.net> writes:
> 
> > On Tue, Aug 04, 2015 at 09:41:45AM +0200, Sandro Santilli wrote:
> >> On Mon, Aug 03, 2015 at 01:30:10PM -0400, Paragon Corporation wrote:
> >
> >> > 2) Revise our configure scripts so it is possible to build liblwgeom without
> >> > the PostgreSQL and other dependencies.  This I think we should table until
> >> > PostGIS 2.3 since our plate is full with PostGIS 2.2 loose ends.
> >> 
> >> +1 to both.
> >> I agree on not rushing too much on the spin-off path.
> >
> > --without-postgresql support added to configure here:
> > https://trac.osgeo.org/postgis/changeset/13882
> >
> > Tests from packagers are welcome.
> > Note I did not attempt at avoiding failures when dependencies are not
> > met, so you'll probably still have a configure error if PostgreSQL is
> > not around (something that can be improved)
> 
> I haven't tested, but if there's going to be a --with-lwgeom-only
> option, there should also be an option to only build postgresql,
> assuming that liblwgeom is already installed, not building it and
> linking with the installed version.  Then there can be separate
> packages.  Otherwise, there will be two copies of liblwgeom and things
> get messy.

Messy it should never get, as SONAME would guard against using
ABI-incompatible libraries, and the PostgreSQL module links statically
against liblwgeom anyway.

But a switch like --with-external-liblwgeom might be useful in the future.

--strk;