Differences

This shows you the differences between two versions of the page.

--- clusters:minerva:spack [2021/08/03 12:26] – ↷ Page moved from minerva:spack to clusters:minerva:spack Steffen Grunewald
+++ clusters:minerva:spack [2021/08/03 12:29] (current) – Steffen Grunewald
@@ Line 4: / Line 4: @@
 It can be used together with, or as a replacement for, the old modules environment that has been used for a long time.
-To use the SPack repository on Minerva, you must **source** a config file:
+To use the latest SPack repository on Minerva (there are some older ''/home/SPACK*'' left), you must **source** a config file:
-  . /home/SPACK/share/spack/setup-env.sh
+  . /home/SPACK2021/share/spack/setup-env.sh
 After that, you may use ''spack help''. Most important commands I use:
@@ Line 32: / Line 32: @@
 In general, ''spack load'' is slow, and prone to ambiguity errors. Use ''module list -t'' to identify such situations, and get the names of loaded modules one-per-line.
-Package dependencies may not be resolved.
+Package dependencies **are now resolved automatically** (even if not invoked with ''-r'').
-**IMPORTANT: The ''/home/SPACK/'' tree is read-only** (and there are no means yet to make it collaborative)**. Therefore ''spack install'' will not work for you! If you need a package that hasn't been installed yet, ask me (Steffen), if possible keep the right options (variants, includes) at hand!**
+**IMPORTANT: The ''/home/SPACK2021/'' tree is read-only** (and there are no means yet to make it collaborative)**. Therefore ''spack install'' will not work for you! If you need a package that hasn't been installed yet, ask me (Steffen), if possible keep the right options (variants, includes) at hand!**
 (To be extended.)