From Rainer at krugs.de  Thu Mar 20 10:04:25 2014
From: Rainer at krugs.de (Rainer M Krug)
Date: Thu, 20 Mar 2014 10:04:25 +0100
Subject: [Rd] [RFC] A case for freezing CRAN
References: <CABFfbXt0PjHEw-4=VfeWeeosm_wOBH-fVsj85j9LMe81Lx0gWQ@mail.gmail.com>
	<CAPPM_gS1Ey2UyyBSCqecT=NzWXKtREBoXmqNBussR8Hv1Zok3g@mail.gmail.com>
	<CAC2h7utmzLPR-cT1pDpnH7gvE0Fzjy5JO363sqBj-f621t22MQ@mail.gmail.com>
	<CABdHhvHyKqu4mSn6Ziw=GgOR8pQOXnGRXW4fZr8H0z41Gkpo4g@mail.gmail.com>
Message-ID: <m2mwgl9r6u.fsf@krugs.de>

Hadley Wickham <h.wickham at gmail.com> writes:

>> What would be more useful in terms of reproducibility is the capability of
>> installing a specific version of a package from a repository using
>> install.packages(), which would require archiving older versions in a
>> coordinated fashion. I know CRAN archives old versions, but I am not aware
>> if we can programmatically query the repository about this.
>
> See devtools::install_version().
>
> The main caveat is that you also need to be able to build the package,
> and ensure you have dependencies that work with that version.

The compiling will always be the problem when using older source
packages, whatever is done.

But for the dependencies: an automatic parsing of the dependencies
(DEPENDS, IMPORTS, ...) would help a lot. 

Together with a command which scans the installed package in the session
and stores them in a parsable human readable format so that all packages
(with the specified version) required can be installed with one command,
and I think the problem would be much closer to be solved.

Rainer

>
> Hadley

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 494 bytes
Desc: not available
URL: <https://stat.ethz.ch/pipermail/r-devel/attachments/20140320/f8b1e895/attachment.bin>


[Rd] [RFC] A case for freezing CRAN
Rainer M Krug