[R-pkg-devel] recreating CRAN Testing environment
avraham.adler at gmail.com
Mon Jul 20 20:15:23 CEST 2015
Even if you don't use Windows, it pays to submit your package to the
Winbuilder test of buth R-release and R-devel. The error reports, if any,
are often not-OS dependant and will serve as a good gaage as to how the
real CRAN will respond.
On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker <bbolker at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 15-07-20 01:50 PM, Jonathan Callahan wrote:
> > I am (hopefully) at the end of a series of back-and-forth
> > submissions of a package to the CRAN upload site.
> > I have done my best to test things by:
> > - using devtools - running "R CMD check --as-cran" on the command
> > line - checking my package on OSX, win-builder.R and various 32 and
> > 64 bit linux virtual machines at DigitalOcean
> > But I have never managed to recreate all of the notes and warning
> > messages that the CRAN testing comes up with.
> > In an effort to save time and effort on both ends, can anyone
> > advise on what I need to do to generate ALL the warning messages
> > that the CRAN testing will find?
> The most important thing that you haven't explicitly mentioned is
> to test on the most recent development version of R (check out via
> Subversion/configure/make/make install from scratch). Can you adjust
> your DigitalOcean settings accordingly?
> Ben Bolker
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> -----END PGP SIGNATURE-----
> R-package-devel at r-project.org mailing list
[[alternative HTML version deleted]]
More information about the R-package-devel