Hi, On Jan 16, 2016, at 2:57 PM, Kenneth Hoste <[email protected]> wrote: > Here's what I would recommend: > * create a directory named 'my_tweaked_easyconfigs' > * copy the OpenMPI easyconfig file to there, and keep the filename the same > * modify the copied easyconfig file to include --with-pmi in configopts > * add the 'my_tweaked_easyconfigs' to the default robot search path, see > http://easybuild.readthedocs.org/en/latest/Using_the_EasyBuild_command_line.html#controlling-the-robot-search-path > and especially > http://easybuild.readthedocs.org/en/latest/Using_the_EasyBuild_command_line.html#prepending-and-or-appending-to-the-default-robot-search-path > * check with "eb --dry-run OpenMPI-1.8.8-GNU-4.9.3-2.25.eb" whether your > tweaked OpenMPI easyconfig is found first > * (re)install OpenMPI > > With a setup like this, your tweaked easyconfigs will always be considered > first, both when specified explicitly or when using to resolve a dependency. > Note that the name of the easyconfig file *does* matter here. > With a setup like this, you can typically modify an easyconfig file once, and > forget about it, even when upgrading EasyBuild to a newer version (your > tweaked easyconfigs will still have preference).
This. I’ve tried most of other alternative options and using this approach turns to be optimal, at least in first stages of setting up EB environments. You can then have this dir committed under git, along with automation scripts which will rebuild your environment when the new EB versions come out. As you build experience, this directory will eventually find its way into a dedicated git branch, which you may refresh with upstream changes (tip of the day: use temp branches, when in doubt - they are cheap) enjoy, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
