spack environment (2): expose a subset of packages to a user#7843
Closed
spack environment (2): expose a subset of packages to a user#7843
Conversation
… and writes stop early if an inconcistency is detected
…d the Spec back, all the build deps are present)
…compilers/architectures
…esn't prevent it from appearing multiple times as a dependency)
…package to the context repo if it is already there
…ing them into a yaml and json file)
…es precedence over all others
…-modules with loads
scheibelp
reviewed
May 10, 2018
lib/spack/docs/environments.rst
Outdated
|
|
||
| .. note:: | ||
|
|
||
| Currently, only "bare" user specs may be added to an environment, |
Member
Member
Author
There was a problem hiding this comment.
OK, I removed the text.
…kage repository; this enables use of the environment-maintained package repository at the highest precedence (so e.g. 'spack env concretize' will use package definitions stored in the environment)
Member
I thought from our discussion that this issue was acceptable since the |
Member
Author
|
I think it's fine for now. Later, I think we can make it more useful with
enough clever thinking.
…On Wed, May 9, 2018 at 10:00 PM, scheibelp ***@***.***> wrote:
Suppose I have package builtin:P. When that package gets copied into the
environment's repo, it should maintain the same name builtin:P. It
shouldn't suddenly change namespace.
I thought from our discussion that this issue was acceptable since the
--use-env-repo was off by default: the idea is that normally you can
reconcretize as much as you want and the dag hashes are preserved but if
you copy the environment directory to another spack instance you can
reconcretize with the packages maintained in the environment. Or is this an
additional issue I overlooked?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7843 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB1cd_LDR91jXxHJUgG26k_RZBygO7nKks5tw584gaJpZM4Tcp0T>
.
|
Member
Author
|
I just checked over the whole PR. Looks good to me, let's get this merged please! |
Member
6 tasks
…ically update the config when initialized; enforce rule that command_line scope is always of highest precedence (even if config scopes are added after it)
Member
Author
|
Superceded by #8231 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a continuation of #4585, moving the branch into the main Spack repo. My latest commits have fixed bugs that became apparent in trying to use Spack Environments.