I had problems getting R to build moments after
EB 2.0 was released. Unfortunately, the bio repo
for extensions updates too quickly and buries old
versions.
I've played the "bump" the version number game
before.... but as soon as you get up to date, they
bump another version number upstream.
Around these parts, our approach to R is:
a) install one of the "default" versions in EB
(e.g. R-3.1.1-ictce-6.3.5-default-mt.eb)
which only installs the extensions that come
with R (as opposed to "bare" which excludes
them)
b) in a non-EasyBuild tree, we install extensions
the usual R way, which takes care of the latest
versions and dependencies
c) provide a module that loads the EB R-default
and sets a path to the extensions
Seems to work nicely...
Jack Perdue
Lead Systems Administrator
High Performance Research Computing
TAMU Division of Research
[email protected] http://sc.tamu.edu
SC Helpdesk: [email protected]
On 03/31/2015 10:41 AM, Martin wrote:
Hi,
I'm trying to install R-3.1.2-goolf-1.5.14.eb.
I'm running a simple:
eb R-3.1.2-goolf-1.5.14.eb --robot -s fetch
but it fails on most of the packages in exts_list. How are people
dealing with this?
Are you just going thru the list and manually fix the versions, I keep
thinking there has to be a better way.
Also how do you (later) install an additional package? Extend the list
in exts_list and "reinstall" or provide another module? Are there
established best practices for this?
thanks,
Martin
