MyGit

v0.21.0

spack/spack

版本发布时间: 2023-11-12 10:35:58

spack/spack最新发布版本:v0.21.3(2024-10-03 18:44:31)

v0.21.0 is a major feature release.

Features in this release

  1. 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. For example:

    $ spack solve hdf5 ^cmake@3.0.1
==> Error: concretization failed for the following reasons:

   1. Cannot satisfy 'cmake@3.0.1'
   2. Cannot satisfy 'cmake@3.0.1'
        required because hdf5 ^cmake@3.0.1 requested from CLI
   3. Cannot satisfy 'cmake@3.18:' and 'cmake@3.0.1
        required because hdf5 ^cmake@3.0.1 requested from CLI
        required because hdf5 depends on cmake@3.18: when @1.13:
          required because hdf5 ^cmake@3.0.1 requested from CLI
   4. Cannot satisfy 'cmake@3.12:' and 'cmake@3.0.1
        required because hdf5 depends on cmake@3.12:
          required because hdf5 ^cmake@3.0.1 requested from CLI
        required because hdf5 ^cmake@3.0.1 requested from CLI

    More details in #40173.

  2. 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
$ spack buildcache push my_registry [specs...]

    And you can optionally add a base image to get runnable images:

    $ spack buildcache push --base-image ubuntu:23.04 my_registry python
Pushed ... as [image]:python-3.11.2-65txfcpqbmpawclvtasuog4yzmxwaoia.spack

$ docker run --rm -it [image]:python-3.11.2-65txfcpqbmpawclvtasuog4yzmxwaoia.spack

    This creates a container image from the Spack installations on the host system, without the need to run spack install from a Dockerfile or sif file. It also addresses the inconvenience of losing binaries of dependencies when RUN spack install fails inside docker build.

    Further, the container image layers and build cache tarballs are the same files. This means that spack install and docker pull use the exact same underlying binaries. If you previously used spack install inside of docker build, this feature helps you save storage by a factor two.

    More details in #38358.

  3. Multiple versions of build dependencies

    Increasingly, complex package builds require multiple versions of some build dependencies. For example, Python packages frequently require very specific versions of setuptools, cython, and sometimes different physics packages require different versions of Python to build. The concretizer enforced that every solve was unified, i.e., that there only be one version of every package. The concretizer now supports "duplicate" nodes for build dependencies, but enforces unification through transitive link and run dependencies. This will allow it to better resolve complex dependency graphs in ecosystems like Python, and it also gets us very close to modeling compilers as proper dependencies.

    This change required a major overhaul of the concretizer, as well as a number of performance optimizations. See #38447, #39621.

  4. Cherry-picking virtual dependencies

    You can now select only a subset of virtual dependencies from a spec that may provide more. For example, if you want mpich to be your mpi provider, you can be explicit by writing:

    hdf5 ^[virtuals=mpi] mpich

    Or, if you want to use, e.g., intel-parallel-studio for blas along with an external lapack like openblas, you could write:

    strumpack ^[virtuals=mpi] intel-parallel-studio+mkl ^[virtuals=lapack] openblas

    The virtuals=mpi is an edge attribute, and dependency edges in Spack graphs now track which virtuals they satisfied. More details in #17229 and #35322.

    Note for packaging: in Spack 0.21 spec.satisfies("^virtual") is true if and only if the package specifies depends_on("virtual"). This is different from Spack 0.20, where depending on a provider implied depending on the virtual provided. See #41002 for an example where ^mkl was being used to test for several mkl providers in a package that did not depend on mkl.

  5. License directive

    Spack packages can now have license metadata, with the new license() directive:

        license("Apache-2.0")

    Licenses use SPDX identifiers, and you can use SPDX expressions to combine them:

        license("Apache-2.0 OR MIT")

    Like other directives in Spack, it's conditional, so you can handle complex cases like Spack itself:

       license("LGPL-2.1", when="@:0.11")
   license("Apache-2.0 OR MIT", when="@0.12:")

    More details in #39346, #40598.

  6. spack deconcretize command

    We are getting close to having a spack update command for environments, but we're not quite there yet. This is the next best thing. spack deconcretize gives you control over what you want to update in an already concrete environment. If you have an environment built with, say, meson, and you want to update your meson version, you can run:

    spack deconcretize meson

    and have everything that depends on meson rebuilt the next time you run spack concretize. In a future Spack version, we'll handle all of this in a single command, but for now you can use this to drop bits of your lockfile and resolve your dependencies again. More in #38803.

  7. UI Improvements

    The venerable spack info command was looking shabby compared to the rest of Spack's UI, so we reworked it to have a bit more flair. spack info now makes much better use of terminal space and shows variants, their values, and their descriptions much more clearly. Conditional variants are grouped separately so you can more easily understand how packages are structured. More in #40998.

    spack checksum now allows you to filter versions from your editor, or by version range. It also notifies you about potential download URL changes. See #40403.

    image image

  8. Environments can include definitions

    Spack did not previously support using include: with The definitions section of an environment, but now it does. You can use this to curate lists of specs and more easily reuse them across environments. See #33960.

  9. Aliases

    You can now add aliases to Spack commands in config.yaml, e.g. this might enshrine your favorite args to spack find as spack f:

    config:
  aliases:
    f: find -lv

    See #17229.

  10. Improved autoloading of modules

    Spack 0.20 was the first release to enable autoloading of direct dependencies in module files.

    The downside of this was that module avail and module load tab completion would show users too many modules to choose from, and many users disabled generating modules for dependencies through exclude_implicits: true. Further, it was necessary to keep hashes in module names to avoid file name clashes.

    In this release, you can start using hide_implicits: true instead, which exposes only explicitly installed packages to the user, while still autoloading dependencies. On top of that, you can safely use hash_length: 0, as this config now only applies to the modules exposed to the user -- you don't have to worry about file name clashes for hidden dependencies.

    Note: for tcl this feature requires Modules 4.7 or higher.

  11. Updated container labeling

    Nightly Docker images from the develop branch will now be tagged as :develop and :nightly The :latest tag is no longer associated with :develop, but with the latest stable release. Releases will be tagged with :{major}, :{major}.{minor} and :{major}.{minor}.{patch}. ubuntu:18.04 has also been removed from the list of generated Docker images, as it is no longer supported. See #40593.

Other new commands and directives

Performance improvements

Other new features of note

Windows

This release has the best Windows support of any Spack release yet, with numerous improvements and much larger swaths of tests passing:

Notable refactors

Binary cache and stack updates

Removals, deprecations, and syntax changes

Notable Bugfixes

Spack community stats

相关地址：原始地址 下载(tar) 下载(zip)

1、 spack-0.21.0.tar.gz 10.12MB

查看：2023-11-12发行的版本

微信小程序
MyGit:GitHub仓库更新&通知小工具