Slides from E4S meeting on June 29, 2023: https://drive.google.com/drive/folders/1u6DR04jjqgoiXfhWXOv14k0X3PCNq-0h

Cheat-Sheet of Common Commands

...

common configuration files that need to be tweaked: packages.yaml, compiler.yaml

Binary Caches

Spack's documentation on binary caches is good in providing a sufficient level of detail without being too verbose:

https://spack.readthedocs.io/en/latest/binary_caches.html

One thing to note is that however long the path is where you initially build the packages, that's the upper limit for how long the path can be when installing downstream. For this reason, one of the things we do, when possible, that isn't documented in Spack's official guide, is we make sure to use a long path length to build the binaries we intend to populate the build cache with.

We tell Spack to pad the install tree to 256 characters in length like this before doing the initial builds:

$> spack config add config:install_tree:padded_length:256

Then we do the builds, push to binary cache, update the cache index and install the public key there. Then users can install packages from the cache so long as they aren't trying to install to a path more than 256 characters in length.

Plusses And Minuses

Minuses

...