Introduce $EESSI_SOFTWARE_LAYER_VERSION_SUFFIX to make build scripts more dynamic
#131
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I still ran into one more issue with the RISC-V bot, and that's because the build scripts were not flexible enough to handle a version
2025.06-001:$EESSI_VERSIONis used in different scripts for different purposes, and sometimes we need it with the suffix and sometimes without. This PR introduces a$EESSI_SOFTWARE_LAYER_VERSION_SUFFIX, which should solve the issue.The default behavior for non-RISCV systems shouldn't change: the suffix is set to an empty string by both
init/eessi_defaultsand the module, unless $EESSI_OVERRIDE_VERSION contains a suffix.Tested manually on a RISC-V system.