SHA256
1
0
forked from pool/spack
Egbert Eich 20a4f61c1e Accepting request 1141708 from home:mslacken:sp
- update to 0.21.1
  * Add support for reading buildcaches created by Spack v0.22 
  * Bugfixes
    + spack graph: fix coloring with environments
    + spack info: sort variants in --variants-by-name
    + Spec.format: error on old style format strings
    + ASP-based solver:
        fix infinite recursion when computing concretization errors
        don't error for type mismatch on preferences
        don't emit spurious debug output
    + Improve the error message for deprecated preferences
    + Fix MSVC preview version breaking clingo build on Windows
    + Fix multi-word aliases
    + Add a warning for unconfigured compiler
    + environment: fix an issue with deconcretization/reconcretization of specs
    + buildcache: don't error if a patch is missing, when installing from binaries
- updated to 0.21.0
  * following new features:
    + Better error messages with condition chaining:
      In v0.18, we added better error messages that could tell you what problem
      happened, but they couldn't tell you why it happened. 0.21 adds condition
      chaining to the solver, and Spack can now trace back through the conditions
      that led to an error and build a tree of causes potential causes and where
      they came from.
    + OCI build caches:
      You can now use an arbitrary OCI registry as a build cache:
      ```
      $ spack mirror add my_registry oci://user/image # Dockerhub
      $ spack mirror add my_registry oci://ghcr.io/haampie/spack-test # GHCR
      $ spack mirror set --push --oci-username ... --oci-password ... my_registry  # set login creds

OBS-URL: https://build.opensuse.org/request/show/1141708
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=90
2024-01-31 09:55:54 +00:00
2021-12-10 16:45:58 +00:00

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.
Description
No description provided
Readme 374 KiB
Languages
Shell 100%