Clarify uenv spack view #70
Conversation
|
preview available: https://docs.tds.cscs.ch/70 |
2 similar comments
|
preview available: https://docs.tds.cscs.ch/70 |
|
preview available: https://docs.tds.cscs.ch/70 |
|
preview available: https://docs.tds.cscs.ch/70 |
| You can then set the uenv as an [upstream Spack instance](https://spack.readthedocs.io/en/latest/chain.html) as follows: | ||
|
|
||
| ```bash | ||
| export SPACK_SYSTEM_CONFIG_PATH=$UENV_SPACK_CONFIG_PATH |
There was a problem hiding this comment.
This is good, but may be dangerous if users don't know to use separate indexes, user config paths, etc. per uenv. I don't know if we want/need to provide a full guide on how to do that (I can share what I do), but a warning may be useful at least at this point?
There was a problem hiding this comment.
Merged too quickly. =)
I actually did not realize that the reminder of the documentation was about uenv-spack; I thought it was still very much WIP and undocumented. Therefore, the above is probably bad for the end user, which should be encouraged to use the tool (I suppose). I can rephrase it to make it clearer that things are not set automatically but one should do so if they wish (without giving too many suggestions).
There was a problem hiding this comment.
I didn't realize either 😬 Yeah, I think the idea is that the uenv-spack tool consumes UENV_SPACK_CONFIG_PATH etc. but it sets up a clone of spack etc. on its own, right? If that's the case, exporting SPACK_SYSTEM_CONFIG_PATH here probably isn't going to harm anyone, but it won't help either...
I think the current description of the
spackview is misleading. I tried to improve things, trying to make clear that thespackview sets some environment variables that are not automatically used by Spack.