Package manager for HPC systems

Edit Package spack

Spack is a configurable Python-based HPC package manager, automating the installation and fine-tuning of simulations and libraries. It operates on a wide variety of HPC platforms and enables users to build many code configurations. Software installed by Spack runs correctly regardless of environment, and file management is streamlined. Spack can install many variants of the same build using different compilers, options, and MPI implementations.

Refresh
Refresh
Source Files
Filename Size Changed
Adapt-shell-scripts-that-set-up-the-environment-for-different-shells.patch 0000004980 4.86 KB
Add-support-for-container-building-using-a-SLE-base-container.patch 0000001096 1.07 KB
Fix-Spinx-configuration-to-avoid-throwing-errors.patch 0000001027 1 KB
Fix-error-during-documentation-build-due-to-recursive-module-inclusion.patch 0000000931 931 Bytes
Make-spack-paths-compliant-to-distro-installation.patch 0000001420 1.39 KB
README-oo-wiki 0000005329 5.2 KB
README.SUSE 0000000877 877 Bytes
Set-modules-default-to-lmod.patch 0000000733 733 Bytes
_constraints 0000000205 205 Bytes
_multibuild 0000000052 52 Bytes
added-target-and-os-calls-to-output-of-spack-spec-co.patch 0000002980 2.91 KB
objects.inv 0000112726 110 KB
run-find-external.sh.in 0000001697 1.66 KB
spack-0.19.0.tar.gz 0009420149 8.98 MB
spack-rpmlintrc 0000000886 886 Bytes
spack.changes 0000017667 17.3 KB
spack.spec 0000018622 18.2 KB
Revision 55 (latest revision is 74)
Christian Goll's avatar Christian Goll (mslacken) committed (revision 55)
- updated to version 0.19.0 with follwoinig changes:
  * Spack's traditional package preferences are soft, but we've added hard
    requriements to packages.yaml and spack.yaml
  * spack install in an environment will no longer add to the specs: list; you'll
    need to either use spack add <spec> or spack install --add <spec>.
  * spack uninstall will not remove from your environment's specs:
    list; you'll need to use spack remove or spack uninstall --remove.
  * concretizer:unify:true is now the default mode for new environments
  * include environment configuration from URLs
  * An increasing number of packages in the ecosystem need the ability to
    support multiple build systems
Comments 0
openSUSE Build Service is sponsored by