In a number of places internal to R, we need to know which files have
changed (e.g. after building a vignette). I've just written a general
purpose function changedFiles that I'll probably commit to R-devel.
Comments on the design (or bug reports) would be appreciated.
The source for the
On 04/09/2013 19:58, Geoff Jentry wrote:
Can you add some details?
Suppose i have the package Model.tar.gz and my writable are is in
user/area, what i have to do next to install the package?
What I was picturing was something like this (forgive me if syntax isn't
100%):
mkdir user/area/myRLib
Can you add some details?
Suppose i have the package Model.tar.gz and my writable are is in user/area,
what i have to do next to install the package?
What I was picturing was something like this (forgive me if syntax isn't
100%):
mkdir user/area/myRLib
R CMD INSTALL
Hi Duncan,
I think this functionality would be much easier to use and understand if
you split it up the functionality of taking snapshots and comparing them
into separate functions. In addition, the 'timestamp' functionality seems
both confusing and brittle to me. I think it would be better to
On 13-09-04 8:02 PM, Karl Millar wrote:
Hi Duncan,
I think this functionality would be much easier to use and understand if
you split it up the functionality of taking snapshots and comparing them
into separate functions.
Yes, that's another possibility. Some more comment below...
In
On Wed, Sep 4, 2013 at 1:53 PM, Duncan Murdoch murdoch.dun...@gmail.com wrote:
In a number of places internal to R, we need to know which files have
changed (e.g. after building a vignette). I've just written a general
purpose function changedFiles that I'll probably commit to R-devel.
Some experimentation with the below function should convince you that the
runtime of the bit inside sys.time is proportional to size*number*times. I
think it should only be proportional to number*times. The function is only
manipulating a list of references to vectors and not trying to make
