|
From: <sup...@cc...> - 2022-01-24 17:35:14
|
Dear Xavier, Thanks for your explanations! It helps a lot, and we now understand better how to use the initrc and rc files. However there is still something we need to do which we don't know how to achieve following your recommendations. > Different kind of commands are found in each kind of files: > * initrc: module config, module use, module load, module restore, ... > * rc: module-alias, module-version, module-hide, module-tag, > module-forbid, ... We are providing Modules for all of our users. We would like them to be able to add their own softwares using their own, customized rc files. To do so, we first tried to use the 'module use' command inside a rc file, but as you explained above, this is not the right way to go.We initially did not understand that, and this is what we believed to be an "unexpected behaviour". In fact, we can use the 'module use' command inside a rc file, without any explicite error, but it will overwrite the initrc configuration (so we will lose our default Modules configuration). So is there a way for usersto add a path to the MODULEPATH variable using theirown rc file ? Thanks & cheers, Sébastien & Natthan |
