Matthew L. Curry
Matthew L. Curry
Hey, I added a commit to make the change you suggested.
Does commit d193b1 "fix" this issue as well?
Hi there, I have hit this issue, as well, and it's pretty easy to reproduce. Here is my procedure: 1. Get a fresh checkout of Spack 0.14.2. Delete ~/.spack, get...
I've driven this around extensively, poking in particular at upstream use cases. It would appear that upstreams has advanced enough since #11871 that a number of problems fixed in the...
I generally think this is very useful, and is specifically useful for pip/apt. What do we need to do to get this beyond a draft? What can I do to...
It would be good to add to the documentation for scopes. Here's something I wrote for configuration.rst, but would go much better in this PR: ``` #. **site-admin**: Stored in...
# TL;DR: Data locations Existing instances of Spack that upgrade in-place will continue to use the same data locations that have been used previously. However, new installs of Spack will...
# Configuration scopes This PR introduces two configuration scopes that are intended to streamline the ability for system administrators to provide Spack instances and trees to system users. These two...