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
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
On 11/9/20 1:41 AM, Robin Sommer wrote:
Yeah, agree, that sounds better than maintaining the information
separately.
Cool. I've updated the wiki page to refer to our CI configs for the details.
I'm definitely not the expert here but it all looks like Catalina
with varying additions:
Yeah,
On Fri, Nov 06, 2020 at 12:27 -0800, you wrote:
> we could just point at our CI? That'd be Dockerfiles for anything
> Linux and prepare.sh for FreeBSD and macOS. The benefit would be
> that we'd maintain this in one place only. We could invest a bit of
> time in documenting the
On 11/6/20 2:03 AM, Robin Sommer wrote:
- Which of these come with additional requirements beyond just OS base
packages? We should note those. What I can think of:
- CentOS: We require devtoolset (which version?) and probably
EPEL? I don't recall how people get some of the
This looks great to me. Some questions/notes:
- Which of these come with additional requirements beyond just OS base
packages? We should note those. What I can think of:
- CentOS: We require devtoolset (which version?) and probably
EPEL? I don't recall how people get some of the
