summaryrefslogtreecommitdiff
path: root/COPYRIGHT
diff options
context:
space:
mode:
authorPeter Scheibel <scheibel1@llnl.gov>2021-02-23 11:45:50 -0800
committerGitHub <noreply@github.com>2021-02-23 11:45:50 -0800
commit76b1d97ca5a57ec504097df233f352462ebebc06 (patch)
treeda55433dfe93262759923f5b4d0691868018710f /COPYRIGHT
parente72ad6223a8d48b064d4a344b3a68d71fe47a953 (diff)
downloadspack-76b1d97ca5a57ec504097df233f352462ebebc06.tar.gz
spack-76b1d97ca5a57ec504097df233f352462ebebc06.tar.bz2
spack-76b1d97ca5a57ec504097df233f352462ebebc06.tar.xz
spack-76b1d97ca5a57ec504097df233f352462ebebc06.zip
"spack build-env" searches env for relevant spec (#21642)
If you install packages using spack install in an environment with complex spec constraints, and the install fails, you may want to test out the build using spack build-env; one issue (particularly if you use concretize: together) is that it may be hard to pass the appropriate spec that matches what the environment is attempting to install. This updates the build-env command to default to pulling a matching spec from the environment rather than concretizing what the user provides on the command line independently. This makes a similar change to spack cd. If the user-provided spec matches multiple specs in the environment, then these commands will now report an error and display all matching specs (to help the user specify). Co-authored-by: Gregory Becker <becker33@llnl.gov>
Diffstat (limited to 'COPYRIGHT')
0 files changed, 0 insertions, 0 deletions