Buildout vs Spack

Buildout has no write-up on Specifiction yet; its figures are above.

Spack is a package manager for installing scientific software on supercomputers, Linux, macOS, and Windows. It is designed for large supercomputing centers that share software across clusters and varied architectures, and is available at free. Users can choose package versions, compiler choices, target architectures, and compile-time options, while controlling direct and transitive dependencies. Spack can build stacks that combine Python or R packages with C, C++, or Fortran libraries. Each distinct package and dependency configuration receives its own prefix, so different builds can coexist without a new installation disrupting an existing one. Software can be installed to a user-selected directory without administrator privileges. Spack primarily builds customized software from source and also supports binary installation through build caches. It supports lockfiles, environment management, and private registries. Package recipes are Python scripts, and the `spack create` command generates starter boilerplate. The project is distributed under either the MIT license or Apache License 2.0, at the user's option.