[postgis-devel] liblwgeom symbols exported by postgis module
Paragon Corporation
lr at pcorp.us
Mon Sep 28 06:31:00 PDT 2015
Oh god no. Please don't force that on me. I was accepting just having my executables screwed and now you want my postgresql lib files screwed as well?
Here is the thing.
I run PostGIS 2.1 and 2.2 on the same PostgreSQL instance (heck I also run PostGIS 1.5 sometimes on same instance). If we make changes to liblwgeom in a minor release, even if the api did not change, I don't want my older PostGIS affected by it. Because I use that for easier regression testing knowing that the only thing that changed is PostGIS is PostGIS (e.g. I'm fine they share the same geos etc. cause I'm not testing that and like all else being equal).
So if you force such a thing, PLEASE MAKE SURE IT'S OPTIONAL so I can count myself out.
Thanks,
Regina
From: Paul Ramsey [mailto:pramsey at cleverelephant.ca]
Sent: Monday, September 28, 2015 8:35 AM
To: Sandro Santilli <strk at keybit.net>; PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Cc: Paragon Corporation <lr at pcorp.us>
Subject: Re: [postgis-devel] liblwgeom symbols exported by postgis module
If anything I’ve become more rabid, frankly.
On September 28, 2015 at 12:12:24 AM, Sandro Santilli (strk at keybit.net <mailto:strk at keybit.net> ) wrote:
On Sun, Sep 27, 2015 at 10:25:05AM +0200, Sebastiaan Couwenberg wrote:
> On 27-09-15 10:23, Markus Wanner wrote:
> > On 09/21/2015 04:49 PM, Sandro Santilli wrote:
> >> is there anyone with ideas on what the best way to deal with
> >> these static-linking pollution matters ?
> >
> > I think you're missing a fourth option: Having PostGIS link to liblwgeom
> > dynamically. That's what we do for Debian, anyways - for good reasons.
>
> And the patch in question has been forwarded:
>
> https://trac.osgeo.org/postgis/ticket/3290
I'd be actually happy with this move, but I recall Paul and Regina had
some trouble with that. Did anything change since then ?
--strk;
--
http://postgis.net
http://cleverelephant.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150928/7b8312a2/attachment.html>
More information about the postgis-devel
mailing list