<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I am more and more sympathetic to Regina’s use of version dropping as the whip hand to push distribution versions forward...<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 23, 2019, at 2:29 PM, Darafei Komяpa Praliaskouski <<a href="mailto:me@komzpa.net" class="">me@komzpa.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Counterexample: <a href="https://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main/binary-amd64/" class="">https://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main/binary-amd64/</a> ships PostGIS 2.5.1 (which is latest released) and does not ship any GEOS, relying on xenial-provided GEOS 3.5.0, released back in 2015. </div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 23, 2019 at 10:02 PM Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" class="">pramsey@cleverelephant.ca</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The PGDG packagers are pretty good now about pushing forward to more recent GEOS. I’m not sure who would package a super-fresh PostGIS for LTS and then not bother to package an equivalent GEOS… ?<br class="">
Might be trying to fix a condition that rarely occurs.<br class="">
P.<br class="">
<br class="">
> On Jan 23, 2019, at 6:35 AM, Raúl Marín Rodríguez <<a href="mailto:rmrodriguez@carto.com" target="_blank" class="">rmrodriguez@carto.com</a>> wrote:<br class="">
> <br class="">
> Hi,<br class="">
> <br class="">
>> I had taken it out with the<br class="">
>> assumption we'd skip PostgreSQL 12 cycle and do a 2 year run.<br class="">
> <br class="">
> I've always thought that plan was to match 3.0 with 12, if possible.<br class="">
> <br class="">
> I have mixed feelings about this. GEOS 3.5 is still receiving commits (last<br class="">
> one in Oct 20, 2018) but, on the other hand, its last release (3.5.1) was in<br class="">
> Oct 2016 which will be 3 years old by the time we plan to release 3.0.<br class="">
> Considering that I expect Postgis 3.0 to be supported for at least ~4 years,<br class="">
> that will mean that we'll need to support an 8 year-old GEOS with its bugs<br class="">
> and differences from 3.7.<br class="">
> <br class="">
> I'm personally happy to kill GEOS 3.5 support but I can accept that it will be<br class="">
> a pain in the ass for anyone using a LTS distribution. Nevertheless, those<br class="">
> distributions are already stuck with old GEOS and Postgis. For example Xenial<br class="">
> (Ubuntu 16.04) has GEOS 3.5 and Postgis 2.2, and Bionic (18.04) has GEOS 3.6<br class="">
> and Postgis 2.4.<br class="">
> This means that if you want Postgis 3 and you are using a LTS distro, you<br class="">
> already need to either use some unofficial repo or package postgis yourself.<br class="">
> I don't think that asking to also package a newer GEOS is too much to ask.<br class="">
> <br class="">
> I share with Komяpa the feeling that we should push people to also update GEOS<br class="">
> as part of their Postgis update, but personally I might more comfortable telling<br class="">
> people that I'm not going to workaround a bug that isn't present in newer<br class="">
> (major) release, alas that isn't trully supporting 3.5.<br class="">
> <br class="">
> So basically I don't have a strong opinion either way, but I'm more inclined<br class="">
> towards dropping it.<br class="">
> <br class="">
> -- <br class="">
> Raúl Marín Rodríguez<br class="">
> <a href="http://carto.com/" rel="noreferrer" target="_blank" class="">carto.com</a><br class="">
> _______________________________________________<br class="">
> postgis-devel mailing list<br class="">
> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank" class="">postgis-devel@lists.osgeo.org</a><br class="">
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank" class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br class="">
<br class="">
_______________________________________________<br class="">
postgis-devel mailing list<br class="">
<a href="mailto:postgis-devel@lists.osgeo.org" target="_blank" class="">postgis-devel@lists.osgeo.org</a><br class="">
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank" class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></blockquote></div><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class="gmail_signature"><div dir="ltr" class=""><div class=""><div class="">Darafei Praliaskouski</div><div class="">Support me: <a href="http://patreon.com/komzpa" target="_blank" class="">http://patreon.com/komzpa</a></div></div></div></div>
_______________________________________________<br class="">postgis-devel mailing list<br class=""><a href="mailto:postgis-devel@lists.osgeo.org" class="">postgis-devel@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/postgis-devel</div></blockquote></div><br class=""></body></html>