Add hint to use correct Spack tag for ICON #74
Merged
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
|
Good point. I agree that this should also be in the c2sm-spack documentation directly. For our page, could we even link to the file directly? https://github.com/C2SM/icon/blob/main/config/cscs/SPACK_TAG |
mjaehn
requested changes
Nov 6, 2023
mjaehn
approved these changes
Nov 7, 2023
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.
So far, I don't think there is any hint that one should not use the Spack tag suggested in the C2SM Spack documentation.
It would also make sense to adapt the C2SM Spack documentation accordingly (make it clear that one can clone Spack with different tags).