Egbert Eich
b5eb808f49
- 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
* package ++variant:
enabled variant that will be propagated to dependencies
* git. prefix to specify git tags or branches as versions. All of these are
valid git versions in
* spack ci generate --tests will generate a .gitlab-ci.yml file that not only
does builds but also runs tests for built packages
* spack test run --explicit will only run tests for packages that are
explicitly installed, instead of all packages.
* You can add a new shared_linking option to config.yaml to make Spack embed absolute paths
to needed shared libraries in ELF executables and shared libraries on Linux
* spack spec prints dependencies more legibly. Dependencies in the output now
appear at the earliest level of indentation possible (#33406)
* You can override package.py attributes like url, directly in packages.yaml
* There are a number of new architecture-related format strings you can use
in Spack configuration files to specify paths
- Improvement from v0.18.0
* spack install --reuse was introduced in v0.17.0, and --reuse is now the
default concretization mode. Spack will try hard to resolve dependencies
using installed packages or binaries
OBS-URL: https://build.opensuse.org/request/show/1037625
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=49
|
||
|---|---|---|
| _constraints | ||
| _multibuild | ||
| .gitattributes | ||
| .gitignore | ||
| Adapt-shell-scripts-that-set-up-the-environment-for-different-shells.patch | ||
| Add-support-for-container-building-using-a-SLE-base-container.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 | ||
| Make-spack-paths-compliant-to-distro-installation.patch | ||
| objects.inv | ||
| README-oo-wiki | ||
| README.SUSE | ||
| run-find-external.sh.in | ||
| Set-modules-default-to-lmod.patch | ||
| spack-0.19.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.