(This crossed with Martin Ondrus's reply).
In the past few years CRAN screeners have gotten more strict about
\dontrun{}; a first-round screening often comes back requesting that
\dontrun{}, and commented-out examples, not be used.
https://stat.ethz.ch/pipermail/r-package-devel/2018q3/003
Hi Guido,
Yes \dontrun works fine for me as well when I'm running the package check
on my own, as well as the win-builder link you've sent. The problem I
always run into is that when it first gets inspected by CRAN it is always
flagged and I am asked to change \dontrun to \donttest, or remove \don
Am 16.11.21 um 20:16 schrieb Martin Ondrus:
Hi Duncan,
That's a fair point, and I think making the examples run quicker probably
makes the most sense. I have bad experiences with using dontrun - my
package always gets flagged. Although not ideal, it's probably better to
include some very fast r
Hi Duncan,
That's a fair point, and I think making the examples run quicker probably
makes the most sense. I have bad experiences with using dontrun - my
package always gets flagged. Although not ideal, it's probably better to
include some very fast running examples rather than none at all. Apprec
On 15/11/2021 2:30 p.m., Martin Ondrus wrote:
Hello,
I am a package maintainer for the package "fabisearch" which is now
archived on CRAN. The package includes many examples which take a long time
to run. In past versions of R, I used to simply wrap these in \donttest and
the examples ran as exp
