|
From: Xavier D. <xav...@gm...> - 2021-11-25 19:16:57
|
Hi, I have just added new installaton options to define a specific directory for the bash, fish and zsh completion script. When set for zsh, the FPATH environment variable is not defined by Modules zsh initialization script: https://modules.readthedocs.io/en/latest/INSTALL.html#instopt---with-zshcompletiondir This change will be part of v5.1. I will update the rpm spec file to make use of these options right away. Regards, Xavier Le mar. 19 oct. 2021 à 23:14, Xavier Delaruelle <xav...@gm...> a écrit : > > Hi, > > I will look if I can improve the installation for the zsh function > files not to rely on FPATH. > > However if the host environment is inherited within the container it > implies that both environment should match to get something > consistent. Especially if some module is loaded in the host prior > running the container, all the environment variables set by loaded > modules on host will get inherited in the container env. So FPATH is > the visible part, but this issue affects every environment variable > set on the host and some warning/error message could pop as soon as > related software differ between host and container. > > Regards, > Xavier > > Le mar. 19 oct. 2021 à 20:57, Götz Waschk <goe...@de...> a écrit : > > > > Am 19.10.21 um 19:15 schrieb Paul Markfort: > > > I forgot to ask - what version of modules in installed with CentOS 8 (A > > > search seems to suggest it is 4.5.2)? > > > Keep in mind that the current version is 5.0.1 > > > > Hi Paul, > > > > CentOS8 has 4.5.2, but I have tested 5.0.1 as well. > > > > > The page you reference has a warning about potential incompatibilities > > > with modules. > > > There is also an example on that page, on how to set an environment > > > variable on the command line. > > > Additionally - you could create a script (start-singularity.sh) that > > > presets some environment variables before running singularity (since > > > scripts run in a sub-shell - it won't affect your main shell's > > > environment). > > > > That would work and I guess it is the right thing to do for certain > > applications. > > > > > I think a possible fix (for you) is to just remove (remark out) the > > > 'export FPATH' line in the modules init/zsh script - it is worth a test > > > (I note that FPATH is not exported by default in zsh - and that line is > > > not in the init script for modules 4.1.4, but is there for 4.5.2 - I > > > don't know which version made that change). > > > I personally remark out the export lines in the init/bash script myself > > > - as I don't see a need to export the module functions - as they > > > generally get loaded again when a new interactive shell is started, and > > > I don't want to accidentally depend on them in scripts. > > > > Thanks, I have just tested this, removing the "export FPATH" line did > > the trick for me. > > > > Regards, > > Götz > > > > -- > > Götz Waschk ° Phone: +49 33762 77169 > > Deutsches Elektronen-Synchrotron DESY ° E-Mail: goe...@de... > > Platanenallee 6 > > 15738 Zeuthen Germany > > > > _______________________________________________ > > Modules-interest mailing list > > Mod...@li... > > https://lists.sourceforge.net/lists/listinfo/modules-interest |
