Egbert Eich
cb5a005ede
- Update to version 0.20.0 with the following features:
* Exact versions: Spack did not previously have a way to distinguish a
version if it was a prefix of some other version. For example, @3.2 would
match 3.2, 3.2.1, 3.2.2, etc. You can now match exactly 3.2 with @=3.2.
This is useful, for example, if you need to patch only the 3.2 version of a
package
* More stable concretization: Now, spack concretize will only concretize the
new portions of the environment and will not change existing parts of an
environment unless you specify --force. This has always been true for
unify:false, but not for unify:true and unify:when_possible environments.
* The concretizer has a new --reuse-deps argument that only reuses dependencies.
That is, it will always treat the roots of your environment as it would with
--fresh. This allows you to upgrade just the roots of your environment while
keeping everything else stable
* Specs in buildcaches can be referenced by hash: Previously, you could run
spack buildcache list and see the hashes in buildcaches, but referring to
them by hash would fail. You can now run commands like spack spec and
spack install and refer to buildcache hashes directly, e.g. spack install
/abc123
* New package and buildcache index websites
Our public websites for searching packages have been completely revamped
and updated. You can check them out here:
Package Index: https://packages.spack.io
Buildcache Index: https://cache.spack.io
Both are searchable and more interactive than before. Currently major
releases are shown; UI for browsing develop snapshots is coming soon.
* Default CMake and Meson build types are now Release: Spack has historically
defaulted to building with optimization and debugging, but packages like
llvm can be enormous with debug turned on. Our default build type for all
Spack packages is now Release. This has a number of benefits:
OBS-URL: https://build.opensuse.org/request/show/1088985
OBS-URL: https://build.opensuse.org/package/show/network:cluster/spack?expand=0&rev=72
70 lines
2.9 KiB
Diff
70 lines
2.9 KiB
Diff
From 1221c1f6b68cbba3a14592a686aec742b5fd02d2 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 4dc8d1249d..42b67425ab 100644
|
|
--- a/lib/spack/docs/developer_guide.rst
|
|
+++ b/lib/spack/docs/developer_guide.rst
|
|
@@ -758,7 +758,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 3c077490a2..0a0a0d0913 100644
|
|
--- a/lib/spack/docs/getting_started.rst
|
|
+++ b/lib/spack/docs/getting_started.rst
|
|
@@ -204,7 +204,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 586fdcec6e..1a7e23c426 100644
|
|
--- a/lib/spack/docs/packaging_guide.rst
|
|
+++ b/lib/spack/docs/packaging_guide.rst
|
|
@@ -6382,13 +6382,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
|
|
@@ -6403,7 +6403,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.40.1
|
|
|