<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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{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'>As much as I hate agreeing with Paul on this as what he has reiterated over and over sounds selfish and unfriendly, I think that's the best solution in the long run for everybody, that other projects fork liblwgeom into a separate repo they can share and PostGIS re-internalize our version of the library so it doesn't get installed in system.<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'>Not being able to rely on an exact version of liblwgeom is very troubling for PostGIS. Unlike GEOS where we can live with some people running say 3.4 or 3.3 (when we prefer 3.5), we absolutely have to be insured that what we test in our cunits is what's being shipped with said version of PostGIS as that is 80% of what PostGIS is. Not to mention the hassle of having to contribute to two projects just to make a change to something that probably 80% of the time affects only us.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Not having that reassurance is just too much stress, I feel on the PostGIS project. <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'>As more projects use liblwgeom this butting of heads of our needs versus theirs will become more of an issue that I fear significantly dwarfs any contributions we might get from others. In this case we are just better off copy sharing rather than binary sharing.<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><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'> postgis-devel [mailto:postgis-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Paul Ramsey<br><b>Sent:</b> Friday, October 23, 2015 10:10 AM<br><b>To:</b> Sandro Santilli <strk@keybit.net>; PostGIS Development Discussion <postgis-devel@lists.osgeo.org>; Greg Troxel <gdt@ir.bbn.com><br><b>Cc:</b> PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-devel] A letter to the Postgis Developers and Packagers<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'>I think a great deal depends on how this new library is going to be used. <o:p></o:p></span></p></div><div id="bloop_customfont"><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'>If the expectation is that it will supplant use of the postgis/liblwgeom for spatialite, qgis, etc, then we should just re-internalize ours so we’re not installing a system library anymore.<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'>P. <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 October 23, 2015 at 6:59:30 AM, Greg Troxel (<a href="mailto:gdt@ir.bbn.com">gdt@ir.bbn.com</a>) wrote:<o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black'>If liblwgeom is going to be used by other packages -- and it really<span class=apple-converted-space> </span><br>seems it is -- the only reasonable thing to do in the long term is make<span class=apple-converted-space> </span><br>it a separate package. (I realize that this may not be reasonable in<span class=apple-converted-space> </span><br>the short term.)<span class=apple-converted-space> </span></span><span style='font-size:10.0pt;font-family:"Helvetica",sans-serif'><o:p></o:p></span></p></div></blockquote><div id="bloop_sign_1445609348245455104"><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>