diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2022-04-23 01:46:45 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-04-22 16:46:45 -0700 |
commit | a9fbc0175d8a1a3e444febac9edc84d42500d79a (patch) | |
tree | 183562e71578da3bbd3a789a7ffcad375cc1b6de /CITATION.cff | |
parent | 58ee1647778f7dd799848119236e6831ba26daee (diff) | |
download | spack-a9fbc0175d8a1a3e444febac9edc84d42500d79a.tar.gz spack-a9fbc0175d8a1a3e444febac9edc84d42500d79a.tar.bz2 spack-a9fbc0175d8a1a3e444febac9edc84d42500d79a.tar.xz spack-a9fbc0175d8a1a3e444febac9edc84d42500d79a.zip |
Move "installed" and "installed_upstream" from PackageBase to Spec (#30191)
This PR moves the `installed` and `installed_upstream` properties from `PackageBase` to `Spec` and is a step towards being able to reuse specs for which we don't have a `package.py` available. It _should_ be sufficient to complete the concretization step and see the spec in the concretized DAG.
To fully reuse a spec without a package.py though we need a way to serialize enough data to reconstruct the results of calls to:
- `Spec.libs`, `Spec.headers` and `Spec.ommand`
- `Package.setup_dependent_*_environment` and `Package.setup_run_environment`
- [x] Add stub methods to packages with warnings
- [x] Add a missing "root=False" in cmd/fetch.py
- [x] Assert that a spec is concrete before checking installation status
Diffstat (limited to 'CITATION.cff')
0 files changed, 0 insertions, 0 deletions