Hi Jack, This is very timely, for me.
As I mentioned on IRC, one of our groups has stated that they want *all* of Bioconductor available on our new system. I wonder whether your approach is the best I’ve seen so far for dealing this this. I think it will actually be easier to deal with the individual package dependencies this way, rather than in a single, very large bundle file, as we have for Bioconductor at the moment. Cheers, Adam — Adam Huffman Senior HPC and Cloud Systems Engineer The Francis Crick Institute Gibbs Building 215 Euston Road London NW1 2BE T: 020 7611 2244 E: [email protected] W: www.crick.ac.uk > On 22 Apr 2016, at 04:54, Jack Perdue <[email protected]> wrote: > > Howdy all, > > Here is an experiment I tried this week. The goal was to automagically create > needed EasyBuild easyconfig (.eb) files for R module known to be used by our > users. > > We have an alternative tree using the traditional tools but I wanted to see > if I could > somehow deliniate specifics. 500 modules (so far) may be a problem. > > I'm a __REALLY___ big fan of version tracking. Others in my group, > not so much. I think we as a group are curious how strict they are > in R module updates and tracking. > > Anyway.... I offer the following (especially the easyconfigs directory) > > http://www.siliconslick.com/easybuild/R_madness/ > > :) > > BTW/FWIW, I took a brief jaunt onto Lonestar 5 yesterday and saw what might > be a place holder for such madness... > > -- > Jack Perdue > Lead Systems Administrator > High Performance Research Computing > TAMU Division of Research > [email protected] http://hprc.tamu.edu > HPRC Helpdesk: [email protected] > The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.
