Changed default behavior for module generation#43
Open
jirudaya wants to merge 2 commits intoARCHER2-HPC:v1.0.2from
Open
Changed default behavior for module generation#43jirudaya wants to merge 2 commits intoARCHER2-HPC:v1.0.2from
jirudaya wants to merge 2 commits intoARCHER2-HPC:v1.0.2from
Conversation
Signed-off-by: jirudaya <j.irudayasamy@epcc.ed.ac.uk>
jirudaya
changed the title
- setting $env causes error when user install packages without an environment - the default is changed to $user_cache_path to avoid this error Signed-off-by: jirudaya <j.irudayasamy@epcc.ed.ac.uk>
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.
This is a similar change the PR for Cirrus-ex (EPCCed/cirrus-ex-spack#39) enabling users to create module files in their local spack environment.
Following is an example flow the users can follow:
module load other-software module load spack spack env create -d my_test_env spack env activate my_test_env spack add gromacs %gcc spack install spack module lmod refresh --delete-tree -y module use $SPACK_USER_CONFIG_PATH/share/spack/modules/Core module load gromacsBy default the module files are created in
$SPACK_USER_CONFIG_PATH/share/spack/modules/Core. To change this, the user can use the following command and create the module files again:spack config add "modules:default:roots:lmod:<full_path_to_modulefiles>" spack module lmod refresh --delete-tree -yTo verify the path: