Hi Joachim,
On 01/12/15 12:38, Joachim Hein wrote:
Hi,
After all the recent discussions on building EasyBuild sandboxes on a
machine with an EasyBuild installation (e.g. conflicts due to config
files) I am now wondering what is the recommended procedure to upgrade
an EasyBuild installation from 2.3 to 2.4. I assumed I would just
build that within the old EasyBuild 2.3 and have that creating modules
etc for me. Though eb --search EasyBuild does only provide blocks for
legacy versions.
Sorry if this is in the user guide and I missed it. Please advised -
thanks.
I include the different options to upgrade in every release
announcement, see for example:
https://lists.ugent.be/wws/arc/easybuild/2015-11/msg00016.html .
This really deserves to be mentioned in the documentation too though,
thanks for pointing that out.
The easiest way is definitely using the easyconfig file for the latest
EasyBuild version, which is typically available in the 'develop' branch
of the easybuild-easyconfigs repo shortly after the release, as Jack
pointed out.
In fact, the pull request for the new EasyBuild easyconfig file is
traditionally the first pull request that gets merged after a new
release, and its referenced from the release announcement (see above).
That being said, I understand the confusion, and as Martin mentions, it
does point out the need for a new feature.
Maybe something like "eb --update", which would be equivalent to: i)
determine the latest available version (probably via PyPI), ii) find the
corresponding easyconfig file in the easyconfigs 'develop' branch, iii)
fire up EB as "eb --from-pr <PR#>".
Another easy way is just to re-bootstrap EasyBuild, which will also
result in a module for the last available version of EasyBuild, and
should also work if EasyBuild is not available yet (but currently may
fail if an EasyBuild module is loaded at the time, as a recent bug
report pointed out).
regards,
Kenneth
