Hi,
Last week I submitted a new package to CRAN, and it was rejected
because there were no examples in any of the man pages. That's a
reasonable requirement--I just didn't know it was one. When I looked
back at the R CMD check results locally, I saw
* checking examples ... NONE
but the run st
are packages where examples do not make sense, hence we do not
> generally reject such packages.
>
> But if adding examples are reasonable we ask for them.
>
> Best,
> Uwe Ligges
>
>
>
>
> On 10.05.2017 17:28, Neal Richardson wrote:
>>
>> Hi,
>> Last wee
Hi,
CRAN's policy on using external C/C++/Fortran/other libraries says:
"Where a package wishes to make use of a library not written solely for the
package, the package installation should first look to see if it is already
installed and if so is of a suitable version. In case not, it is desirable
CRAN policy [1] says: "If the sources are too large, it is acceptable
to download them as part of installation, but do ensure that the
download is of a fixed version rather than the latest." So you could
try downloading the source in your configure script. Though be careful
not to be bitten by this
A couple of ideas:
1. Both `sf` and `sp` packages Suggest rgdal and rgeos. If your
package were to Suggest them, the dependencies will be available for
CRAN checks, but they won't be available if they're only Suggested by
a package you Import.
2. Except sometimes when they are available. I've expe
I've used the https://hub.docker.com/r/rstudio/r-base images for this, and
they appear to go back to R 3.1. Likewise
https://hub.docker.com/r/rocker/r-ver. The latter uses MRAN to install
packages from a CRAN snapshot corresponding to the release, so that should
also help with dependencies.
Neal
