Re: [gdal-dev] libkml: providing more information about builds that include LIBKML to steer users away from security pitfalls and questions for packagers who may build with libkml

2024-10-03 Thread Simon Eves via gdal-dev
We include *libkml* in our GDAL build. We are still using v1.3.0 from August 12, 2015. It still works fine for our requirements with GDAL 3.7.3 (current production) and 3.9.2 (imminent deps bump). The build script for it predates me, but it appears we also had issues with *uriparser*. We build tha

[gdal-dev] libkml: providing more information about builds that include LIBKML to steer users away from security pitfalls and questions for packagers who may build with libkml

2024-10-03 Thread P O'Toole via gdal-dev
Hello list — I recently built GDAL 3.9.0 from source on a new Amazon Linux 2023 system, which sadly lacks all of the wonderfulness of EPEL, which previously provided most of the necessary stuff on the RHEL-family operating systems we used before. Since we've historically provided support for ex

[gdal-dev] GDAL Maintainers Meeting Minutes

2024-10-03 Thread Howard Butler via gdal-dev
Howard Butler, Even Rouault, Dan Baston, Alessandro Pasotti, Michael Sumner, and Javier Jimenez Shaw held the monthly GDAL Maintainers Meeting on 09/26/2024. The following items were discussed and reported upon: Discussion Items * Two bronze sponsors have declined t

Re: [gdal-dev] [PROJ] RFC 102: Embedding resource files into libgdal (and PROJ)

2024-10-03 Thread Kurt Schwehr via gdal-dev
For my weird google production setup: I haven't heard of any bugs along those lines. I only build cs2cs and gie for running tests and users have no access to any of the proj binaries in production. I don't think folks do much with sqlite (most db usage are things like Spanner or FireBase) and most

Re: [gdal-dev] [PROJ] RFC 102: Embedding resource files into libgdal (and PROJ)

2024-10-03 Thread Even Rouault via gdal-dev
Hi, I've now a PROJ branch with proj.db embedding working at https://github.com/OSGeo/PROJ/pull/4265. And contrary to the current wording of the RFC text, I've actually invested in making it work with non-C23 compilers too (C23 mechanism used when available), by adapting https://gitlab.com/jh