Thanks everyone!
I'd like to follow the Duncan's approach but I am not sure if it solves the
issue:
* if I put the private tests into a separate folder and ignore it when
building the package, then I still cannot run these checks without creating
the tarball (Maintainer, Author not built into DESC
On 21.04.2021 00:02, Barbara Lerner wrote:
When checking my package with R-devel, I get the following notes. In
the current and earlier versions of R, I got the same note concerning
incoming feasibility, but the NOTE about the package not being available
for checking did not occur. What do I
You can default to have 'few tests'. That then happens at CRAN too when
nothing else is set (as there simply is no variable to rely upon).
You can then try to detect when you would want to run 'more tests'. Placing
the tests somewhere else (as Duncan suggested) to explicitly opt in is one
way (t
Am 21.04.21 um 08:35 schrieb Mark van der Loo:
> Hi Ott,
>
> There is no documented way to detect whether you are running on CRAN. So
> there is nothing to rely on, on that side.
>
> You can only make your own machine detectable by the test code. For example
> by setting an environment variable t
On 21/04/2021 1:16 a.m., Ott Toomet wrote:
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
On 20/04/2021 11:18 p.m., Marcelo Araya Salas wrote:
I am trying to build the website for my NatureSounds package with pkgdown
but I got the following error message:
Warning: Vignettes missing from index:
That probably means you have an "articles:" section in your _pkgdown.yml
file, but you a
