Changes in CI file allow to use existing spack deployments w/o cache.

Eric Müller authored 3 months ago and Eleni Mathioulaki committed 2 months ago

This introduces a submodule for yashchiki.

We need to check if the flexibility of the script is actually needed.
(And how this ever could have worked with a moving target spack ;).)

Lia Domide authored 3 months ago and Eleni Mathioulaki committed 3 months ago

Pinned dependency on vtk@9.2.6 (that should be avoided anyway) conflicts with gcc@13. vtk@9 was selected as a lower limit to avoid using older versions since compatibility has not been tested.

spack does not support ! when parsing version in URL

new SYSTEMNAME is chosen on purpose.

- adjust git clone command to clone correct spack version
- remove creation of enviroement (already present due to `spack.yaml`)
- provide a example for `SYSTEMNAME`