<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="auto"><div>Dear Paul,<div dir="auto"><br></div><div dir="auto">Many thanks for your reply. May I kindly ask you guidance on how to implement the solution you suggested? </div><div dir="auto"><br></div><div dir="auto">We will closely follow any futur change in liblwgeom's public API and perform any required adaptation in MobilityDB code.</div><div dir="auto"><br></div><div dir="auto">Regards </div><div dir="auto"><br></div><div dir="auto">Esteban </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 2, 2021, 18:15 Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The simplest expedient is to vendor in a versioned copy of liblwgeom.h and then trust us when we pinky-swear that the we don't change the public API between releases.<br>
<br>
P<br>
<br>
> On Jul 2, 2021, at 8:34 AM, Esteban Zimanyi <<a href="mailto:esteban.zimanyi@ulb.be" target="_blank" rel="noreferrer">esteban.zimanyi@ulb.be</a>> wrote:<br>
> <br>
> Alas MobilityDB only works with PostGIS 2.5. It was never possible to upgrade to version 3 since liblwgeom.h is not exported anymore.<br>
> <br>
> On Fri, Jul 2, 2021, 17:23 Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" target="_blank" rel="noreferrer">pramsey@cleverelephant.ca</a>> wrote:<br>
> <br>
> <br>
> > On Jun 25, 2021, at 2:38 AM, Esteban Zimanyi <<a href="mailto:ezimanyi@ulb.ac.be" target="_blank" rel="noreferrer">ezimanyi@ulb.ac.be</a>> wrote:<br>
> > <br>
> > Now that our user base has considerably increased, we are continuously receiving the same question "What about PostGIS 3.1 support?"<br>
> > <br>
> <br>
> I'm not sure I even understand the thrust of the question... what about it? Nothing has changed substantially in 3.1 in terms of code structure, etc. Why are not the same things you are doing with earlier versions working for 3.1?<br>
> <br>
> P.<br>
> _______________________________________________<br>
> postgis-devel mailing list<br>
> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank" rel="noreferrer">postgis-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
> _______________________________________________<br>
> postgis-devel mailing list<br>
> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank" rel="noreferrer">postgis-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
<br>
_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@lists.osgeo.org" target="_blank" rel="noreferrer">postgis-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
</blockquote></div></div></div>