-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion for a new spack era environment variable #109
Comments
it is not the Mu2e online, it is spack itself which defines SPACK_ENV via |
What is spack-env.sh and where does SPACK_VIEW get set online? |
@pavel1murat do you know the answers? I don't. |
, the same as
|
I'm sorry to be slow, but I still don't see SPACK_VIEW anywhere, not in scripts or docs, and we don't get it when activating an env. Maybe it is something Eric customized for online? (I created SPACK_LOCAL to point into the padded build area, for example)
Maybe I am being slow. Was the point here to ask me to go into the script and add it myself? I think I was reading this thread wrong. |
try without |
to have $SPACK_ENV showing up, I first had to deactivate
|
SPACK_ENV should only be present when you have an active env, which you seem to agree with. But I still don't understand how to do SPACK_VIEW, so I'd like to see how it is done online. Obviously SPACK_VIEW would not be defined until you activate a env with a view. Since an env can have multiple views, the system picks one based on your activate command, so that would have to be tracked. This information does exist deep in the bowels of spack env activate code, which I can modify, but there is some risk to touching that. So I'm wondering if Eric did this mod, or am I missing something? A different approach is to set SPACK_VIEW in the muse envset, Here, muse is acting as a wrapper to "spack env activate" so it has control of the activate and has the opportunity to set this, but of course this is outside of spack. |
My advice is to do this as natively as possible but from time to time it may make sense to use muse as a helper, perhaps only a transient helper. |
On the is_it_me_or_a_bug slack channel Pasha points out:
https://mu2e.slack.com/archives/C72755LAE/p1719187991527409
The online spack environment defines SPACK_VIEW, which points at, for example:
/cvmfs/mu2e.opensciencegrid.org/packages/spack/v0.21.0-dev.fermi/NULL/var/spack/environments/mu2e-3-14-03-al9-e28-prof-3/.spack-env/view
In the offline environment we have SPACK_ENV, which is similar but omits the last two elements of the path.
Do we want to define SPACK_ENV in the offline environment?
The text was updated successfully, but these errors were encountered: