I always run R CMD BUILD before R CMD CHECK. I popped open the tar.gz
file and the folder did include DESCRIPTION. So it's there, all right.
I notice the 'build' folder contains one file, 'partial.rdb' . I don't
have anything requiring compilation, so I'm not sure why there's a
'build'
AFAIK tgz is one possible file name extension equivalent to .tar.gz, which
implies gzip compression, so I think Bob was just being a bit sloppy when he
wrote tar.tgz.
Key point is not that a particular compression makes a difference, but that the
check needs to be run on a source archive
I plead ignorance here: I don't see an option to create .tgz . The
R CMD BUILD --help just lists "gzip" (default), "none", "bzip2", "xz"
.Does one of those create the .tgz -type compression?
Carl
On 6/6/20 2:37 PM, Bob Rudis wrote:
Does it still do it if you build a tar.tgz archive and run
Does it still do it if you build a tar.tgz archive and run it on that?
I could not dup your problem, but when I tried to run it on a couple
of my packages that work fine with tar.gz (I use Authors@R) in dir (`R
CMD check --as-cran .` or parent dir and specify the pkg dir) I get:
Required
Hi,
I recently upgraded to a new iMac w/ Catalina. Something really strange
is happening when I try to run "R CMD CHECK --as-cran " .
If I run it on various older packages that have previously passed the
check, all is well.
I am writing a new package, and here's the response I get:
*
