<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>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?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Here is the thing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>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).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So if you force such a thing, PLEASE MAKE SURE IT'S OPTIONAL so I can count myself out.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Paul Ramsey [mailto:pramsey@cleverelephant.ca] <br><b>Sent:</b> Monday, September 28, 2015 8:35 AM<br><b>To:</b> Sandro Santilli <strk@keybit.net>; PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br><b>Cc:</b> Paragon Corporation <lr@pcorp.us><br><b>Subject:</b> Re: [postgis-devel] liblwgeom symbols exported by postgis module<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div id="bloop_customfont"><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'>If anything I’ve become more rabid, frankly. <o:p></o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p><p style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black'>On September 28, 2015 at 12:12:24 AM, Sandro Santilli (<a href="mailto:strk@keybit.net">strk@keybit.net</a>) wrote:<o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'>On Sun, Sep 27, 2015 at 10:25:05AM +0200, Sebastiaan Couwenberg wrote: <br>> On 27-09-15 10:23, Markus Wanner wrote: <br>> > On 09/21/2015 04:49 PM, Sandro Santilli wrote: <br>> >> is there anyone with ideas on what the best way to deal with <br>> >> these static-linking pollution matters ? <br>> > <br>> > I think you're missing a fourth option: Having PostGIS link to liblwgeom <br>> > dynamically. That's what we do for Debian, anyways - for good reasons. <br>> <br>> And the patch in question has been forwarded: <br>> <br>> <a href="https://trac.osgeo.org/postgis/ticket/3290">https://trac.osgeo.org/postgis/ticket/3290</a> <br><br>I'd be actually happy with this move, but I recall Paul and Regina had <br>some trouble with that. Did anything change since then ? <br><br>--strk; <o:p></o:p></span></p></div></div></blockquote><div id="bloop_sign_1443443694467278080"><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'>-- <br><a href="http://postgis.net">http://postgis.net</a><o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'><a href="http://cleverelephant.ca">http://cleverelephant.ca</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p></div></div></div></body></html>