Howdy Fotis (deferring to Fotis's preference to bottom posting),
On 04/01/2015 05:54 PM, Fotis Georgatos wrote:
Hi Jack,
On Mar 31, 2015, at 5:01 PM, Jack Perdue <[email protected]> wrote:
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...
OK, interesting. This may actually be a reproducible use-case.
If it get’s automated I’d call that: R-ugly or R-...-1st_of_April :)
(no offense to the TAMU work, you guys are doing your part just decently).
Why not poke fun with some build processes which are just plainly insane?!
F.
Just a note from our in-house Nederlander, eR, R extension maintainer:
-----
happy to hear we are doing our part "just decently"
I'm not familiar how easybuild does it with the exts_list. So whenever
you want to install a new packages you have to add it to the exts_list
and then rebuild R (although it will skip the already installed parts)?
How does it handle packages that require non standard install?
R has a very powerful easy-to-use build-in technique of installing new
packages (and yes it can be automated). To me it seems better to use a
specialized automated approach than to use a generic technique
I think TACC is doing it in a similar way with installing packages
-----
It provides flexibility... when a user needs an extension, done.
The magic is just:
prepend-path R_LIBS_USER
"/software/tamusc/R-packages/3.1.0-ictce-7.1.2-default-mt"
(all EB software is in /software/easybuild).
But just for you, Fotis, I'll see if I can come up with R-ugly using
the CmdCp easyblock.
jack (who has some ideas in mind)
