rework Anaconda easyconfigs based on changes to Anaconda easyblock #1
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
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.
for
easybuilders#3173easybuilders#3337@jerowe changes that accompany the changes to the
Anacondaeasyblock, cfr. jerowe/easybuild-easyblocks#1Anaconda2/Anaconda3as software namesourcesThe one thing I'm not sure 100% about is the
name/versionchange...The benefit of using
Anaconda2andAnaconda3asnameis that you can then load these modules at the same time, depending on your needs. Also, it fits better with the actual version of Anaconda which is4.0.0currently (not2.4.xand3.4.x).Downside is that these easyconfigs will need to be moved to dedicated
Anaconda2andAnaconda3directories, so that they can be picked up by the EasyBuild dependency resolver (--robot) if needed (but that's a very minor thing imho)...Let me know what you think!