On 20.07.2015 19:50, 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
Not needed at all.
- running "R CMD check --as-cran" on the command lin
Thanks to all so far for excellent suggestions!
On Mon, Jul 20, 2015 at 11:18 AM, Gábor Csárdi
wrote:
> On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker wrote:
> [...]
> >The most important thing that you haven't explicitly mentioned is
> > to test on the most recent development version of R (ch
On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker wrote:
[...]
>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
Jonathan,
On 20 July 2015 at 13:59, Ben Bolker wrote:
| On 15-07-20 01:50 PM, Jonathan Callahan wrote:
| > 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 impor
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.
Avi
On Mon, Jul 20, 2015 at 1:59 PM, Ben Bolker 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
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
