forked from pool/spack
d5e157f9bf
- Move-site-config-scope-before-system-scope.patch:
Give 'site' scope a lower precedence than 'system' scope.
The 'site wide' config scope was meant to be per Spack
installation. A single system may have multiple Spack
installations, so was is meant for overriding the
'system' wide setting per installation.
The Spack package is OS-vendor provided. The vendor provides
pr generates a configuration which a local admin may want to
override. This can now be done from within the 'system' scope.
Previously the vendor-supplied configuration was mixed with
the 'system' scope - local modifications collided with
vendor autoconfiguration.
- Add a build-dependency package which will cause build tools
and libraries used frequently by Spack to be installed.
All these packages are recommended by the main Spack package
already. This package may be used in environments where the
installation of recommended packages is disabled by default.
- Update Spack to version 0.22.0
* New features:
- Compiler dependencies:
Spack is in the process of making compilers proper dependencies.
For this, compiler dependencies are moving from `compilers.yaml`
to `packages.yaml` to make this consistent with other externals.
For this, dependency graphs will not show the compiler runtime
libraries like `gcc-runtime` or `libgfortran`.
To minimize disruption, an existing `compilers.yaml` file will
continue to work, however, users are encourage to migrate
before v0.23.
+ Packages compiled with `%gcc` now depend on a new package
OBS-URL: https://build.opensuse.org/request/show/1179953
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/spack?expand=0&rev=44
openSUSE/SUSE specific Settings ============================================= The packages build by a regular user are stored in the home directory and so only available for this user. When the packages should be available for all users on a system, the user who builds the packages, must be able to write to the global spack user directories under /usr/lib/spack/ Packages stored under this path are available for all user via lmod. To add a user to the group spack so that he can write to the global spack directory, execute (as root): # usermod -a -G spack <user_login> and change the setting for 'install_tree:' to the global spack directory in the configuration '~/.spack/config.yaml' for this user. NOTE: As the recipes are contributed by the spack community and rely also on external packages, a signification part of the recipes may fail to create packages.