Description
See spack/spack-packages#2508
Solution
We will need help from JCSDA with updating/testing newer boost versions. I noticed that many JEDI components still require 1.64.0 (e.g. https://github.com/JCSDA-internal/oops/blob/24e5485b40b0310930a4a863045df5482d9a64dd/CMakeLists.txt#L63), but it's written such that newer versions are also supported - there is no EXACT clause.
I remember there were issues with certain newer versions of boost, but I don't recall the details.
Because of that, we pinned boost to 1.64.0 in
years ago.
Alternatives
Do nothing and wait until boost 1.64.0 is removed entirely from Spack after being deprecated for some time.
Timeline
This is not needed for spack-stack-2.2. We have enough time to update boost in 2.3.
Description
See spack/spack-packages#2508
Solution
We will need help from JCSDA with updating/testing newer boost versions. I noticed that many JEDI components still require 1.64.0 (e.g. https://github.com/JCSDA-internal/oops/blob/24e5485b40b0310930a4a863045df5482d9a64dd/CMakeLists.txt#L63), but it's written such that newer versions are also supported - there is no
EXACTclause.I remember there were issues with certain newer versions of boost, but I don't recall the details.
Because of that, we pinned boost to 1.64.0 in
spack-stack/configs/common/packages.yaml
Line 31 in b3ce4f6
Alternatives
Do nothing and wait until boost 1.64.0 is removed entirely from Spack after being deprecated for some time.
Timeline
This is not needed for spack-stack-2.2. We have enough time to update boost in 2.3.