Spack Setup (2): Developer Build Tool#7846
Spack Setup (2): Developer Build Tool#7846citibeth wants to merge 21 commits intofeatures/contextfrom
Conversation
# Conflicts: # lib/spack/spack/cmd/env.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/diy.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/env.py
…/context_setup # Conflicts: # lib/spack/spack/cmd/env.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/env.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/env.py # lib/spack/spack/schema/env.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/env.py
…s/context_setup # Conflicts: # lib/spack/spack/cmd/env.py
|
Finally got around to testing this branch with |
|
Something else I was curious about is where we're expected to put our spackage manifest? Should we have a dedicated repo for all the related projects? I was following Developing Software with Spack (I know it's out of date), and it didn't seem to specify. For now I've gone with a dedicated repo for just my related projects. I suppose you could have a super fine-grained approach where each project is its own repo. |
|
Try spack module refresh and see what happens. I don’t use spack find
…On Fri, Jun 22, 2018 at 11:04 AM Andrew Gaspar ***@***.***> wrote:
Finally got around to testing this branch with spack install --setup, and
I think it could actually solve my issues raised in #7904
<#7904>. One think I've noticed is
that packages installed via "make install" using -setup.py don't show up
when I run spack find foo. Is that expected?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7846 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB1cd-b-WaorwEdwFWmf7HK8txqAAFQPks5t_QdpgaJpZM4Tc0PQ>
.
|
|
I'm not sure if I was doing something wrong at first, but it's working now. So far I'm very happy with this feature. I think it resolves the issue I opened. Let me know if you'd like me to test anything out! |
|
Sorry, this will not be merged. Spack Setup has morphed a little bit with Spack Environments, and a new Spack Setup needs to be put together given the current context. At this point, a change to the grammar is required so the YAML files can accommodate Spack Setup functionality. I don't know how to change the grammar appropriately. If someone can come up with the right YAML grammar, that would really help things. .. Elizabeth
|
|
thanks for the clarification @citibeth . |
Continuation of #7830