Skip to content

Spack Setup (2): Developer Build Tool#7846

Closed
citibeth wants to merge 21 commits intofeatures/contextfrom
features/context_setup
Closed

Spack Setup (2): Developer Build Tool#7846
citibeth wants to merge 21 commits intofeatures/contextfrom
features/context_setup

Conversation

@citibeth
Copy link
Copy Markdown
Member

Continuation of #7830

Elizabeth Fischer added 12 commits April 22, 2018 20:40
# 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
@AndrewGaspar
Copy link
Copy Markdown
Contributor

AndrewGaspar commented Jun 22, 2018

Finally got around to testing this branch with spack install --setup, and I think it could actually solve my issues raised in #7904. One think I've noticed is that packages installed via "make install" using foo-setup.py don't show up when I run spack find foo. Is that expected?

@AndrewGaspar
Copy link
Copy Markdown
Contributor

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.

@citibeth
Copy link
Copy Markdown
Member Author

citibeth commented Jun 22, 2018 via email

@AndrewGaspar
Copy link
Copy Markdown
Contributor

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!

@davydden
Copy link
Copy Markdown
Member

Given that this PR should solve the long standing spack setup problem, @citibeth could you please resolve merge conflicts and hopefully @tgamblin or @alalazo (or someone else) can review it some time soon?

@citibeth
Copy link
Copy Markdown
Member Author

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

During the recent Spack Environments work, I made a request to change the grammar of the YAML file to accommodate Spack Setup:

Change YAML grammar to accommodate future inclusion of Spack Setup. See for example: https://github.com/citibeth/spack/blob/efischer/giss/var/spack/environments/twoway-dev-gibbs/env.yaml

It was decided at the time that this change is NOT needed, and there's another way to do what Spack Setup requires. Can you please elaborate on this, as I don't really know what to do here or how it will work? I would like to get a (final) Spack Setup PR ready soon, now that Environments are in.

@davydden
Copy link
Copy Markdown
Member

thanks for the clarification @citibeth .

@scheibelp scheibelp self-assigned this Jan 18, 2019
@tgamblin tgamblin closed this Jan 1, 2020
@alalazo alalazo deleted the features/context_setup branch January 2, 2020 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants