summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorbecker33 <becker33@llnl.gov>2017-01-25 20:38:10 -0800
committerTodd Gamblin <tgamblin@llnl.gov>2017-01-25 21:38:10 -0700
commit8ae380fb71eefc288a532b4574cf53cec32f74e4 (patch)
treede25deea24aa6735cfb37ed245fd1939efb5d59e /var
parenta4f594a68da6fb50799961d2ef81be1dac772d19 (diff)
downloadspack-8ae380fb71eefc288a532b4574cf53cec32f74e4.tar.gz
spack-8ae380fb71eefc288a532b4574cf53cec32f74e4.tar.bz2
spack-8ae380fb71eefc288a532b4574cf53cec32f74e4.tar.xz
spack-8ae380fb71eefc288a532b4574cf53cec32f74e4.zip
Fixes for parsing specs with hashes (#2889)
- Allows hashes to be specified after other parts of the spec - Does not allow other parts of the spec to be specified after the hash - The hash must either end input or be followed by another separate spec - The next spec cannot be an anonymous spec (it must start with a package name or a hash) See #2769 (after it was merged) for further discussion of this interface addition. That discussion resulted in these requirements: ``` python # 1 spec /abc123 # 1 spec python /abc123 # 1 spec /456789 # 1 spec python /abc123 /456789 # 2 specs python /456789 /abc123 # 2 specs /abc123 /456789 # 2 specs /456789 /abc123 # 2 specs /456789 /abc123 python # 3 specs ``` assuming `abc123` and `456789` are both hashes of different python specs.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions