wpoely86
I'm not following, what should be integrated? The only thing Lmod does is read some files and output something which can be interpreted by a shell. Start a new shell...
@blappm Can't you put the stuff that changes in a separate file and load that in the module? So the actual module file remains unchanged.
@blappm why don't you make it a module instead of a collection? You can use `try_load`? It is much easier to share then a collection?
Another question: would it make sense to use `MODULEPATH_ROOT` as default value for the starting point of creating the spider cache?
For the moment, we cannot fix this. Using an older GCC than the system GCC can only work with a strict separation of both (and all the programs that use...
yes and no. We have newer toolchain (up to GCC 5.2 for the moment). The problem is that you cannot mix system and EB GCC if the latter is older...
@boegel I thought you looked at the nix road? Or rpath, this has been discussed before?
No, there isn't it. It has popped up before. As soon as we put a older gcc lib in the `LD_LIBRARY_PATH`, we're in trouble with system libs.
Why put the sources to `'%(version)s.tar.gz'`? I would drop the `.tar.gz`. Gives us the freedom to changes if we want later on and, if you have multiple source_urls and sources,...
Moving will cause all kinds of issues. The 'easiest' way is to take all the easyconfigs in de `easybuild` subdirectory of every software install and use those to reinstall everything....