Open willfurnass opened 1 year ago
Hi @willfurnass
There are a few ways of getting later versions of the various ecosystems as you mentioned.
The way that ecosystems are made available to the flight-env
tool is via flight-env-types. An "env type" provides installation and activation scripts to the tool, allowing users to create instances of ecosystems with them.
When installed from the RPM, these types will be present under /opt/flight/usr/lib/env/types/
. New types can be installed into this directory and will immediately be available to the tool (which you can check with flight env avail
).
In some cases it may be possible to simply tweak version numbers inside an existing ecosystem's *-install.sh
scripts to install later versions.
Hope this helps!
How should one upgrade Lmod/Lua/Easybuild etc in an Ecosystem? Or should one deploy newer versions of those things using the older Ecosystem tooling e.g. use EasyBuild in an Ecosystem to install a newer version of EasyBuild? Or, alternatively, should users create new Ecosystems if they want access to newer tooling?