[Modules] How to implement module commands as scripts instead of shell functions?

[Frank T. <f.t...@dk...>]

Dear all,

is there a way to use (shell) scripts instead of shell functions for all 
the required Environment Modules functionalities?

In our cluster, shell functions are currently not inherited by cluster 
jobs from the users' local environments, leading to a non-functional 
(better: non-existent) `module` command within the batch jobs, which 
breaks many of our established pipelines. I considered to implement the 
required shell functions as plain shell scripts, but in contrast to 
Environment Modules 3.x, where there was just a single shell function, 
there is now a loooong list of functions. Implementing them all as 
scripts would require to check each of them after each Environment 
Module upgrade, to be sure to always use up-to-date code. That's too 
much overhead on the admin side.

Question: Is there way to convert the shell functions into scripts, 
which does not conflict with the Environment Modules' design and which 
could also be integrated into automated Environment Modules updates 
(Debian Linux using `apt`)?

Side question: Why are the Environment Modules' functions implemented as 
shell functions instead of plain shell scripts?

I'm grateful for all ideas and pointers.

Cheers, Frank