Feature/update fnal setup #110
Closed
Conversation
This file contains 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
|
Shelving this atm, an actually correct implementation will take some more work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not high priority, but I've had an error or two using the existing one so decided to update.
Old setup_FNAL.sh would sometimes not fully set LD_LIBRARY_PATH for all packages, so have made it more resilient against weird spack/GPVM behaviour.
It should also not spam your environment if you source it repeatedly.
The tradeoff is that the script is far more disgusting.
To test
git checkout feature/update_fnal_setupand source the script, you'll know if it works.