|
From: Frank T. <f.t...@dk...> - 2022-04-05 21:58:39
|
they are defined in etc/modulespath. If I leave ~/.modulerc empty, $MODULEPATH is $CENTRALLY_SET_MODULEPATHS On 05.04.22 17:45, Xav...@CE... wrote: > Hi Frank, > > Could you describe where and how the $CENTRALLY_SET_MODULEPATHS are > defined ? > > Cheers, > Xavier > > > On Tue, 2022-04-05 at 17:28 +0200, Frank Thommen wrote: >> Hi, >> >> this is most probably a silly error on my side, but I haven't found >> the >> solution: When having a custom ~/.modulerc with >> >> #%Module >> module use --append /a/b/c >> append-path MODULEPATH /d/e/f >> >> the resulting $MODULEPATH is "/a/b/c:/d/e/f". I would have >> expected it >> to be "$CENTRALLY_SET_MODULEPATHS:/a/b/c:/d/e/f". When only using >> `append-path` it looks similar: >> >> #%Module >> append-path MODULEPATH /d/e/f >> >> results in $MODULEPATH being "/d/e/f" instead of >> "$CENTRALLY_SET_MODULEPATHS:/d/e/f". >> >> This is with Modules 5.0.1 on CentOS 7.9 systems. We have not >> changed >> any of the other configuration files after the installation other >> than >> populating etc/modulespath with our central modulefile repository >> pathes. >> >> What have I overlooked? >> >> Cheers, Frank >> > > _______________________________________________ > Modules-interest mailing list > Mod...@li... > https://lists.sourceforge.net/lists/listinfo/modules-interest |
