I think you've misunderstood that excerpt. By "temporary development
state", it means _between_ CRAN releases; packages in a development
state are not suitable for CRAN, as the policy states:
> CRAN hosts packages of publication quality and is not a development platform.
You'll need to stop
Hi,
I have a package (dartR) that needs to be updated by CRAN (and got a time set
until a certain date). It depends on a package that is currently showing errors
in the CRAN results and therefore fails. The maintainer of that package is
busily trying to rectify the error (as can be seen be
Hello,
I have a short question on the number of processes which are spawned
during parallelization. My package passes R CMD check –as-cran on MacOS
and Linux, but the vignettes fail with the following error on Windows
and Debian:
|--- re-building 'gettingstarted.Rmd' using rmarkdown Quitting
В Wed, 16 Nov 2022 07:29:25 +0100
Riko Kelter пишет:
> if (nzchar(chk) && chk == "TRUE") {
> # use 2 cores in CRAN/Travis/AppVeyor
> num_workers <- 2L
> }
The check in parallel:::.check_ncores is a bit different:
chk <- tolower(Sys.getenv("_R_CHECK_LIMIT_CORES_", ""))
if (nzchar(chk) && (chk
