From geoffjentry at hexdump.org  Tue Mar  5 15:50:48 2013
From: geoffjentry at hexdump.org (Geoff Jentry)
Date: Tue, 5 Mar 2013 06:50:48 -0800 (PST)
Subject: [Rd] [BioC] enabling reproducible research & R package
 management & install.package.version & BiocLite
In-Reply-To: <D4772401B9D976478C0895769BE3E792072B7C@MBSRV02.sgc.loc>
References: <D4772401B9D976478C0895769BE3E7920716E6@MBSRV02.sgc.loc>
	<CAErFSogyfzMQ9UEK7e=Ukvgdg-NfxS60cPtppvvvN0MKnogyzw@mail.gmail.com>
	<CAHA9McNqVxFAdBYMqJm=avjA8wsS0uVSGQ=6eviXU6iPzPVXVQ@mail.gmail.com>
	<CAF42j23OD664yG7rgVMYzsEgges97=mn+DcQihne8CQUM0DmOQ@mail.gmail.com>
	<D4772401B9D976478C0895769BE3E792072B7C@MBSRV02.sgc.loc>
Message-ID: <Pine.LNX.4.64.1303050647190.22360@cardinals.dreamhost.com>

On Tue, 5 Mar 2013, Cook, Malcolm wrote:
> Thus, I might rather consider an approach that at 'publish' time tarzips 
> up a copy of the R package dependencies based on a config file defined 
> from sessionInfo and caches it in the project directory.

If you had a separate environment for every project, each with its own R 
installation and R installation lib.loc this becomes rather easy. For 
instance, something like this:

myProject/
    projectRInstallation/
       bin/
         R
       library/
         Biobase
         annotate
         .....
       ....
    projectData/
    projectCode/
    projectOutput/

The directory structure would likely be more complicated than that but 
something along those lines. This way all code, data *and* compute 
environment are always linked together.

-J



[Rd] [BioC] enabling reproducible research & R package management & install.package.version & BiocLite
Geoff Jentry