> > That last one is quite a nasty one, do take a look. The fact that we have a > major correctness issue argues for quick release. > > > > https://github.com/libgeos/geos/issues/408 > > With the soft freeze this Friday, it's too late to get this into the next Debian > stable release. > > Patches for the latter three issues could be included if they don't break the > C++ ABI. Do they? > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel
Do we still have projects that rely on GEOS C++ABI being stable? I thought we made it clear -- packagers will not carry your crap if you choose to code against the C++ API. So C++ API should only be used for those who choose to ship their own stuff. _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel