summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2019-09-17 20:45:37 -0600
committerPeter Scheibel <scheibel1@llnl.gov>2019-09-17 19:45:37 -0700
commit56894b880548181a3b8f98a5b902deb03a208539 (patch)
treed93e33b61b26d520ac353cfa3d8153afb55f5e7a /var
parenteb4dd4a51aa33462d0a0defb56b77eeefd9bf2cb (diff)
downloadspack-56894b880548181a3b8f98a5b902deb03a208539.tar.gz
spack-56894b880548181a3b8f98a5b902deb03a208539.tar.bz2
spack-56894b880548181a3b8f98a5b902deb03a208539.tar.xz
spack-56894b880548181a3b8f98a5b902deb03a208539.zip
Support yaml paths anywhere specs are handled on CLI (#12561)
Update command-line (CLI) parsing to understand references to yaml files that store Spack specs. Where a file reference is encountered, the full Spec in the file will be read in. A file reference may appear anywhere that a spec could appear before. For example, if you write "spack spec -y openmpi > openmpi.yaml" you may then install the spec using the yaml file by running "spack install ./openmpi.yaml"; you can also refer to dependencies in this way (e.g. "spack install foo^./openmpi.yaml"). There are two requirements for file references: * A file path entered on the CLI must include a "/" even if the file exists in your current working directory. For example, if you create an openmpi.yaml file as above and run "spack install openmpi.yaml" from the same directory, it will report an error. * A file path entered on the CLI must end with ".yaml" This commit adds error messages to clearly inform the user of both violations.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions