EESSI
eessi-init command to facilitate initializing of EESSI environment
We should look into providing an eessi-init command that makes it easier/less awkward to initialize the EESSI environment.
By default, it should simply run source source /cvmfs/pilot.eessi-hpc.org/latest/init/bash, but it could also provide options, for example to use a specific subtree rather than letting archspec figuring it out.
This is perhaps easiest by implementing a small Python package, since that can be installed by a non-admin user easily via pip install --user, and it shouldn't be difficult to generate an RPM or .deb file either for a simple Python package that follows standard practice.
(hat tip @hmeiland who raises this idea in a recent meeting)
In a module environment, one should be able to also do module load EESSI that performs a similar task.
@terjekv Yes, we should just offer all these different "access methods" for the EESSI repo, for different systems/use cases.
(Relevant issue about the module: https://github.com/EESSI/software-layer/issues/68)
Another feature of this eessi-init I would like to see is ability to do its job in non-interactive environment as well, for example in a container startup scenario where we currently fail on $BASH_SOURCE being undefined.
rough starting point here... https://github.com/EESSI/software-layer/pull/166
Another feature of this
eessi-initI would like to see is ability to do its job in non-interactive environment as well, for example in a container startup scenario where we currently fail on $BASH_SOURCE being undefined.
Just want to second this point. The current init script is not supporting zsh for example. Not a big deal, but a more generic shell script is probably a good idea.
