PostGIS 3.5.0alpha1 released supports PG17

[Regina Obe]

> On 7/5/24 7:03 AM, Regina Obe wrote:
> > To take advantage of all SFCGAL features, SFCGAL 1.5.0+ is needed.
> 
> Note that SFCGAL won't support CGAL 6 any time soon [0], so SFCGAL support
> was disabled in the Debian package.
>
 
> [0] https://gitlab.com/sfcgal/SFCGAL/-/issues/267

Ah okay and I see CGAL 5 can't be bundled with Debian SFCGAL either cause 49 MB when extracted 
Is deemed too fat.  I do still wonder how many headers SFCGAL uses, I'm guessing a lot of it.
So the fact that CGAL 5 is a header-only package is not much of help here.


> Loïc Bartoletti mentioned that "Time, Money and/or Contributions" are
> needed to make SFCGAL work with CGAL 6. If SFCGAL support in PostGIS is
> considered important enough you should consider contributing to the CGAL
> 6 support in SFCAL.
> 
> 
> Kind Regards,
> 
> Bas
> 
> --
>   GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

I haven't looked into how much effort there is involved.  I'll talk with Loïc about that.
But my guess is such work even if funded will be too late for PostGIS 3.5.0 release which we'll probably need to get out
by September-October 2024

 To Paul Norman's point:
> They also said that SFCGAL 1.x will stick with CGAL 5, so there won't be any compatibility until SFCGAL 2.0

If such a change will not happen until SFCGAL 2.0, then it is almost not likely to happen by 3.5.0 release time so our hands are tied here.
Debian/Ubuntu folks will just have to not have postgis_sfcgal as an option and remove from their GDAL packages if they are part of GDAL.

Thanks Regina