On Fri, Jul 24, 2015 at 8:35 AM Pieter Neerincx <[email protected]> wrote:
> No I completely missed that :o. Is this the "Standard Operating Procedure" > the community has standardised on? If yes, I'd be happy to modify the > generateEasyConfig.R to create to *.eb files - on for core and another for > BioConductor. The more generic question I have is whether there is a SOP or > good practice on when to make separate easyconfigs en when to bundle a > bunch of tools/packages together in a single easyconfig. Making a separate > easyconfig for each and every R package won't be fun, but updating the R > name+version each time you add one R package also does not sound like a > practical solution... The issue with Perl and additional Perl module, > Python and additional eggs, etc... > > I think it generally makes our lives easier if we bundle up packages like this, so I think you'll see more of it. I have been playing with RStudio server and it is a bit of a pain to get the bundle working with the main libraries, but I think it is worth it. I think we are primarily interested in it from the development side as it reduces the build time and thus allows a bit more testing (and perhaps allows us to move forward easier as new versions are necessary). I can definitely see it working with something like easybuild.experimental to provide faster moving groups of deps in tighter subject areas.
