Thanks so much for tidying things up, Christian!
I’m really glad to see the new policy taking shape. 👏
One more thing besides available C++ features worth tracking is CMake availability. In the CAF CI (Jenkins), I’ve made all the various compiler and CMake versions used throughout a build available as artifact. Still work in progress, but this is the current list for the Docker images (the Linux versions currently listed in the Zeek Wiki minus Fedora 33):
I’m a bit sad to see CMake 3.5 still around (released in 2016). Anyway, "it is what it is”. Versions to watch out for in particular IMHO are 3.12 (allows target_link_libraries for object libraries) and 3.15 (introduced FetchContent).
In any case, might be worth tracking the current lower bound for CMake and library dependencies (like OpenSSL) to know when it’s safe to drop existing workarounds or start using new features. Not sure if Cirrus CI can collect data from all builds for providing a single artifact, but otherwise one could provide a script to combine the individual artifacts locally via curl or some other means.
At least CMake 3.5 seems safe as minimum requirement in Zeek/Broker for now. Already a step up from the current 3.0 dependency. 😉
On Mon, Nov 09, 2020 at 14:16 -0800, Christian Dreibach wrote:
Hah, I asked them too and they actually mentioned their email reply to you!
Yeah, and in a further followup email they went a bit further even and committed to generally keeping the previous base image around in the future when new macOS release come out (but not the Xcode image).
Excellent. Look like we're all good with our new policy. Thanks for driving this forward, Christian!
zeek-dev mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org