I think part of the problem is that the corresponding section in "Writing R
extensions" is not very clear for newcomers. I admit I have read it
several times as I have been confused about the difference between suggest,
imports and depends, and so combed section 1.1.3 repeatedly. But from this
upport")
> q("no")
> }
>
> Don't run such code in an interactive session if you don't want to quit
> R. ;)
>
> An alternative is the R CMD check --test-dir=inst/slowTests approach
> mentioned in the WRE manual at
>
> https://CRAN.R-project.org/doc/manu
Hi packagers,
what is the best way to skip certain tests on CRAN? So far I have included
certain test files in .Rbuildignore and run the tests on the package
directory. But now when moving to Authors@R format, I get errors about
missing maintainer etc.
I know there are options in testthat,
As I read the docs (a few months ago though), you are supposed to include
the pdf and encouraged to include sources, but the process to get pdf from
source may depend on your private libraries/data/software, and is not
replicated on CRAN checks. This seemed to work for me as my vignette
includes
x86_64 x86_64 GNU/Linux w/gcc 5.4.0, libgomp1.0.0
> [2]
>
> https://builder.r-hub.io/status/gower_0.0.1.tar.gz-8c487e92f4af364ee73f85ca8f59775c
> [3] https://travis-ci.org/markvanderloo/gower#L619
>
> [[alternative HTML version deleted]]
>
> _______
useNULL = TRUE)
>
> doesn't stop rgl from running, it just stops it from trying to display
> anything. So you could put code like
>
> if (!interactive())
> options(rgl.useNULL = TRUE)
>
> into your .onLoad function for your package, and it wouldn't try to open
> a displa
