diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2019-10-07 18:53:23 +0200 |
|---|---|---|
| committer | Peter Scheibel <scheibel1@llnl.gov> | 2019-10-07 09:53:23 -0700 |
| commit | 9faee51e22967b289dc7d8aabe0dffd36a0f85ba (patch) | |
| tree | 09ccb90b328d656fdd91c6f1d18b1804a3990f39 /LICENSE-MIT | |
| parent | c8c795e7dbde22dc47c9ae285a4dd59004b115b1 (diff) | |
| download | spack-9faee51e22967b289dc7d8aabe0dffd36a0f85ba.tar.gz spack-9faee51e22967b289dc7d8aabe0dffd36a0f85ba.tar.bz2 spack-9faee51e22967b289dc7d8aabe0dffd36a0f85ba.tar.xz spack-9faee51e22967b289dc7d8aabe0dffd36a0f85ba.zip | |
Spack environments can concretize specs together (#11372)
This PR adds a 'concretize' entry to an environment's spec.yaml file
which controls how user specs are concretized. By default it is
set to 'separately' which means that each spec added by the user is
concretized separately (the behavior of environments before this PR).
If set to 'together', the environment will concretize all of the
added user specs together; this means that all specs and their
dependencies will be consistent with each other (for example, a
user could develop code linked against the set of libraries in the
environment without conflicts).
If the environment was previously concretized, this will re-concretize
all specs, in which case previously-installed specs may no longer be
used by the environment (in this sense, adding a new spec to an
environment with 'concretize: together' can be significantly more
expensive).
The 'concretize: together' setting is not compatible with Spec
matrices; this PR adds a check to look for multiple instances of the
same package added to the environment and fails early when
'concretize: together' is set (to avoid confusing messages about
conflicts later on).
Diffstat (limited to 'LICENSE-MIT')
0 files changed, 0 insertions, 0 deletions