[postgis-devel] moving liblwgeom forward

[Paragon Corporation]

Congrats strk. 

I agree with Chris.  If we separate the two then liblwgeom should be
versioned and each version of postgis should use a different version of
liblwgeom to allow for sideline installs.  I don't care too much about the
versioning you give it.

I can see how it could deviate from PostGIS versioning in the long-term (if
other tools/databases choose to build on top of it), but not in the
short-term so just assume give it same version number as PostGIS 2.0 for now
and see what happens later.

Besides who wants to start a new library on version 1.0.  

Thanks,
Regina


> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
> bounces at postgis.refractions.net] On Behalf Of Chris Hodgson
> Sent: Friday, August 05, 2011 2:20 PM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] moving liblwgeom forward
> 
> Good to hear you've got some funding to do work on PostGIS!
> 
> I'm a little bit worried about the effects of installing liblwgeom into
> the system lib dir on the ability to have multiple different versions of
> PostGIS installed simultaneously (for development, testing, migration,
> etc.). Tell me this won't be any different than it is now and I'll
> probably believe you.
> 
> I can't imagine a situation where it makes sense for liblwgeom to have a
> different version than postgis. IIRC the only reason they are separated
> is to provide a C-based interface to test the liblwgeom functions
> without having to go through postgres.
> 
> Cheers,
> Chris
> 
> Sandro Santilli wrote:
> > Guys, I've got some fundings to move liblwgeom forward.
> >
> > After moving all geos functions into it the next big step
> > seems to be cleaning up / extracting a streamlined and
> > documented API, working on build scripts and decide on a
> > version policy.
> >
> > Do you agree on having liblwgeom installed systemwide and
> > dynamically linked starting with PostGIS 2.0 ?
> >
> > Should liblwgeom versioning follow PostGIS version (easier)
> > or should we introduce a separate versioning scheme (stricter) ?
> >
> > For simplicity, I'd have it follow PostGIS version, starting
> > with 2.0. Comments are welcome.
> >
> > --strk;
> >
> >   ()   Free GIS & Flash consultant/developer
> >   /\   http://strk.keybit.net/services.html
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> >
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel