Expand description
Constants defining available versions of spack.
Currently, this crate avoids maintaining a git repository (the typical way
spack is distributed) in favor of a checksummed directory corresponding to a
precise spack release. The main reason for this is to enable experimental
support for wasm compilation via emscripten (see the
wasm module). Until upstream support for emscripten
is merged, the cached build output in opt/ may refer to packages which are
unavailable in spack proper, causing an exception when spack is invoked.
Figuring out a nicer way to select a compatible spack version (which also works across the entire cargo build graph, which may invoke this crate multiple times) is on the horizon, but until then hardcoding this information is slightly easier to work with.