You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"title": "Restricted spack environment file schema for ACCESS-NRI continuous deployment",
5
+
"description": "This schema was adapted from https://github.com/ACCESS-NRI/spack/blob/releases/v0.21/lib/spack/spack/schema/env.py to specify a restricted form of spack.yaml to design generic deployment infrastructure.",
Copy file name to clipboardexpand all lines: au.org.access-nri/model/spack/environment/deployment/CHANGELOG.md
+8
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,11 @@
1
1
# `spack.yaml` Schema Changelog
2
2
3
+
## 1-0-7
4
+
5
+
* Allow the use of `@latest` in `spack.specs[0]`. This is allowed for Prereleases, but not for Releases. This keeps continuity with local builds which can't use not-yet-existing `@git.TAG`s like Prerelease builds can.
6
+
7
+
This has full interoperability with the earlier schema/data.
8
+
3
9
## 1-0-6
4
10
5
11
* Added special case for `spack.packages.gcc-runtime.require[0]` - it does not have to be a `@VERSION` as it dynamically creates it's version. That way, we can still put compiler constraints on the package without having to specify a version as the first element. For example:
@@ -12,6 +18,8 @@ spack:
12
18
- '%gcc@8.5.0'# Note, not a '@VERSION'
13
19
```
14
20
21
+
This has full interoperability with the earlier schema/data.
22
+
15
23
## 1-0-5
16
24
17
25
* Updated `spack.specs` to allow > 1 specs allowed. The first spec is still used as a basis for deployment information.
0 commit comments