Comment # 15 on bug 1206957 from Ludwig Nussel

(In reply to Egbert Eich from comment #10)
> (In reply to Ludwig Nussel from comment #5)
> > No it's not a duplicate. lmod is doing nasty things here and pollutes the
> > shell environment via /etc/profile.d/lmod.sh. My strong advice would be not
> > do that. Instead there could be eg. only something like an "lmod-activate"
> > or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on
> > demand* rather than for each and every shell of each and every user.
> 
> This would break every existing job scripts for users. We cannot do this.
> 'module load' needs to work in a batch environment from inside shell
> scripts. This is why BASH_ENV is set. 
> Also, it is expected that every (physical) user logging into a system with
> Lmod installed will actually need it. On non-HPC systems, the lua-lmod
> package should not be installed.

There is nothing that prevents lua-lmod from being installed in a normal
system. In fact the description sounds very generic and has no reference to
specific HPC setups. Introducing a generic command called "module" and even a
two letter one, ie "ml" looks rather dangerous to me.
How can we as distribution make sure that no other package introduces those
commands too? How to make sure noone else uses BASH_ENV for some other magic?