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
70 lines
2.9 KiB
Diff
70 lines
2.9 KiB
Diff
From a80d5cd883263271650925926dfd734f488bb731 Mon Sep 17 00:00:00 2001
|
|
From: Christian Goll <cgoll@suse.de>
|
|
Date: Fri, 11 Dec 2020 15:37:48 +0100
|
|
Subject: [PATCH] added target and os calls to output of spack spec commands
|
|
|
|
---
|
|
lib/spack/docs/developer_guide.rst | 2 +-
|
|
lib/spack/docs/getting_started.rst | 2 +-
|
|
lib/spack/docs/packaging_guide.rst | 6 +++---
|
|
3 files changed, 5 insertions(+), 5 deletions(-)
|
|
|
|
diff --git a/lib/spack/docs/developer_guide.rst b/lib/spack/docs/developer_guide.rst
|
|
index 6b67ef9f77..695e3a84bc 100644
|
|
--- a/lib/spack/docs/developer_guide.rst
|
|
+++ b/lib/spack/docs/developer_guide.rst
|
|
@@ -761,7 +761,7 @@ supply ``--profile`` to Spack on the command line, before any subcommands.
|
|
|
|
``spack --profile`` output looks like this:
|
|
|
|
-.. command-output:: spack --profile graph hdf5
|
|
+.. command-output:: spack --profile graph hdf5 os=SUSE target=x86_64
|
|
:ellipsis: 25
|
|
|
|
The bottom of the output shows the top most time consuming functions,
|
|
diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst
|
|
index 1bf99e09b3..6b01bf4950 100644
|
|
--- a/lib/spack/docs/getting_started.rst
|
|
+++ b/lib/spack/docs/getting_started.rst
|
|
@@ -206,7 +206,7 @@ Check Installation
|
|
With Spack installed, you should be able to run some basic Spack
|
|
commands. For example:
|
|
|
|
-.. command-output:: spack spec netcdf-c
|
|
+.. command-output:: spack spec netcdf-c target=x86_64 os=SUSE
|
|
|
|
In theory, Spack doesn't need any additional installation; just
|
|
download and run! But in real life, additional steps are usually
|
|
diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst
|
|
index 5b0e556b34..600f0fb72e 100644
|
|
--- a/lib/spack/docs/packaging_guide.rst
|
|
+++ b/lib/spack/docs/packaging_guide.rst
|
|
@@ -6099,13 +6099,13 @@ Spack provides the ``spack graph`` command for graphing dependencies.
|
|
The command by default generates an ASCII rendering of a spec's
|
|
dependency graph. For example:
|
|
|
|
-.. command-output:: spack graph hdf5
|
|
+.. command-output:: spack graph hdf5 target=x86_64 os=SUSE
|
|
|
|
At the top is the root package in the DAG, with dependency edges emerging
|
|
from it. On a color terminal, the edges are colored by which dependency
|
|
they lead to.
|
|
|
|
-.. command-output:: spack graph --deptype=link hdf5
|
|
+.. command-output:: spack graph --deptype=link hdf5 target=x86_64 os=SUSE
|
|
|
|
The ``deptype`` argument tells Spack what types of dependencies to graph.
|
|
By default it includes link and run dependencies but not build
|
|
@@ -6120,7 +6120,7 @@ dependencies. The default is ``--deptype=all``, which is equivalent to
|
|
You can also use ``spack graph`` to generate graphs in the widely used
|
|
`Dot <http://www.graphviz.org/doc/info/lang.html>`_ format. For example:
|
|
|
|
-.. command-output:: spack graph --dot hdf5
|
|
+.. command-output:: spack graph --dot hdf5 target=x86_64 os=SUSE
|
|
|
|
This graph can be provided as input to other graphing tools, such as
|
|
those in `Graphviz <http://www.graphviz.org>`_. If you have graphviz
|
|
--
|
|
2.38.0
|
|
|