diff options
| author | Peter Scheibel <scheibel1@llnl.gov> | 2020-01-28 17:26:26 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-28 17:26:26 -0800 |
| commit | 69feea280d5504b0ff72a0e309ed7cfcb7fb43a4 (patch) | |
| tree | cd1dc6892e75ecd1d136b51f3760d099483b2bbc /var | |
| parent | e7106563109276f0dbb472ae88fc14575a001db2 (diff) | |
| download | spack-69feea280d5504b0ff72a0e309ed7cfcb7fb43a4.tar.gz spack-69feea280d5504b0ff72a0e309ed7cfcb7fb43a4.tar.bz2 spack-69feea280d5504b0ff72a0e309ed7cfcb7fb43a4.tar.xz spack-69feea280d5504b0ff72a0e309ed7cfcb7fb43a4.zip | |
env: synchronize updates to environments (#14621)
Updates to environments were not multi-process safe, which prevented them from taking advantage of parallel builds as implemented in #13100. This is a minimal set of changes to enable `spack install` in an environment to be parallelized:
- [x] add an internal lock, stored in the `.spack-env` directory,
to synchronize updates to `spack.yaml` and `spack.lock`
- [x] add `Environment.write_transaction` interface for this lock
- [x] makes use of `Environment.write_transaction` in `install`,
`add`, and `remove` commands
- `uninstall` is not synchronized yet; that is left for a future PR.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions