Hi,
I am currently learning EasyBuild/Lmod and strategizing for deployment to a
common network shared mountpoint, say $HPCBC, for use by about half-dozen HPC
linux running CentOS7.
I wonder if there is any information that would help me with pros/cons on
waiting for EB 2.x before deployment, such as:
intended scope of changes
intended backward compatibility (should all existing modules
'just work')
ETA for first release intended for general availability
(non-beta)
Also, I am somewhat struggling with my EB 1.x evaluation/testing (also on
CentOS7) and wonder about relative value of using the various installation
methods, being
1) python bootstrap_eb.py $HPCBC/easybuild # currently yields version 1.16.1
2) pip install --install-option "--prefix=${HPCBC}/EasyBuild" easybuild
3)
> pip install --install-option "--prefix=1.16.1" easybuild
b) pip install --install-option "--prefix=1.16.1" easybuild
My impression is that the advantage of using the bootstrap procedure is that it
builds a 'module' file. Is there more that I am missing?
Finally, I have the following observations about the install that I hope you
find worthy additions to your installation documentation:
xmlrunner is python module optionally used by eb boostrap unit
test which allows them to run faster! NB - in my hands the test results are
DIFFERENT if present - perhaps a "bad thing". Can be installed with: `pip
install xmlrunner` -- add to
http://easybuild.readthedocs.org/en/latest/Installation.html#optional-dependencies
tcl need be installed (in my experience) (regardless of whether
Tcl/C environment modules are to be used - i.e. even if only Lmod is to be
used) - add to
http://easybuild.readthedocs.org/en/latest/Installation.html#requirements
if Lua is built and installed in a non standard location,
LUA_ROOT should be redefined accordingly, for example:
> sed -i '/#define
LUA_ROOT/s:/usr/local/:${INSTALL_TOP}/:' src/luaconf.h
Thanks,
Malcolm
python-pip
~ Malcolm Cook
Computational Biology - Stowers Institute for Medical Research - Kansas City
