d1d51f6dec
- updated to version 0.17.0 (Upstream feature/bug references (<ID>) are relative to https://github.com/spack/spack/issues/<ID>). * New concretizer is now default The new concretizer introduced as an experimental feature in v0.16.0 is now the default (#25502). The new concretizer is based on the clingo logic programming system, and it enables us to do much higher quality and faster dependency solving The old concretizer is still available via the concretizer: original setting, but it is deprecated and will be removed in v0.18.0. * Binary Bootstrapping To make it easier to use the new concretizer and binary packages, Spack now bootstraps clingo and GnuPG from public binaries. If it is not able to bootstrap them from binaries, it installs them from source code. With these changes, you should still be able to clone Spack and start using it almost immediately. * Reuse existing packages (experimental) The most wanted feature from our 2020 user survey and the most wanted Spack feature of all time (#25310). spack install, spack spec, and spack concretize now have a --reuse option, which causes Spack to minimize the number of rebuilds it does. The --reuse option will try to find existing installations and binary packages locally and in registered mirrors, and will prefer to use them over building new versions. This will allow users to build from source far less than in prior versions of Spack. This feature will continue to be improved, with configuration options and better CLI expected in v0.17.1. It will become the default concretization mode in v0.18.0. * Better error messages We have improved the error messages generated by the new concretizer by OBS-URL: https://build.opensuse.org/request/show/931907 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/spack?expand=0&rev=15 |
||
|---|---|---|
| _constraints | ||
| _multibuild | ||
| .gitattributes | ||
| .gitignore | ||
| Adapt-shell-scripts-that-set-up-the-environment-for-different-shells.patch | ||
| added-target-and-os-calls-to-output-of-spack-spec-co.patch | ||
| Fix-error-during-documentation-build-due-to-recursive-module-inclusion.patch | ||
| Fix-Spinx-configuration-to-avoid-throwing-errors.patch | ||
| fix-tumbleweed-naming.patch | ||
| Make-spack-paths-compliant-to-distro-installation.patch | ||
| objects.inv | ||
| README-oo-wiki | ||
| README.SUSE | ||
| run-find-external.sh | ||
| Set-modules-default-to-lmod.patch | ||
| spack-0.17.0.tar.gz | ||
| spack-rpmlintrc | ||
| spack.changes | ||
| spack.spec | ||
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.