spack/README.SUSE
Egbert Eich d67b8bdc5b - Update to version 0.22.2
* Bugfixes
    - Forward compatibility with Spack 0.23 packages with language
      dependencies.
    - Forward compatibility with `urllib` from Python 3.12.6+.
    - Bump vendored `archspec` for better aarch64 support.
    - Fix regression in `{variants.X}` and `{variants.X.value}`
      format strings.
    - Ensure shell escaping of environment variable values in load
      and activate commands.
    - Fix an issue where `spec[pkg]` considers specs outside the
      current DAG.
    - Do not halt concretization on unknown variants in externals.
    - Improve validation of `develop` config section/
    - Explicitly disable `ccache` if turned off in config, to
      avoid cache pollution.
    - Improve backwards compatibility in `include_concrete`.
    - Fix issue where package tags were sometimes repeated.
    - Make `setup-env.sh` "sourced only" by dropping execution bits.
    - Make certain source/binary fetch errors recoverable instead
      of a hard error.
    - Remove debug statements in package hash computation.
    - Remove redundant clingo warnings.
    - Remove hard-coded layout version.
    - Do not initialize previous store state in `use_store`.
  * Package updates
    - `chapel` major update/

OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=109
2024-11-01 12:27:09 +00:00

22 lines
877 B
Plaintext

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.