Ah, yes... I see it now in Writing R Extensions. Apologies for the
oversight.
Regarding rmarkdown, is it redundant to include rmarkdown in
VignetteBuilder if it is in Suggests, or is perhaps needed in the build
config as a separate entity?
e.g:
Suggests: knitr, rmarkdown
VignetteBuilder: knitr, formatR
or
Suggests: knitr, rmarkdown
VignetteBuilder: knitr, rmarkdown, formatR
Thank you.
J Park
On 11/13/20 8:58 AM, Gábor Csárdi wrote:
I think you need to Suggest the formatR package, because your
vignettes use it. From 'Writing R extensions':
"Many packages using knitr also need the package formatR which it
suggests and so the user package needs to do so too and include this
in ‘VignetteBuilder’."
Gabor
On Fri, Nov 13, 2020 at 1:49 PM Joseph Park <josephp...@ieee.org> wrote:
Dear r-package-devel,
The rEDM package is failing the automated check, as noted here:
https://win-builder.r-project.org/incoming_pretest/rEDM_1.7.0_20201113_131811/Windows/00check.log
When running rhub::check_for_cran(), disk file errors were reported.
The automated check seems to be failing with:
Error in loadNamespace(x) : there is no package called 'formatR'
This package does not explicitly use formatR:
Imports: methods, Rcpp (>= 1.0.1)
LinkingTo: Rcpp, RcppThread
Suggests: knitr, rmarkdown
VignetteBuilder: knitr
Could it be these errors (disk full, no formatR) are related? If not,
does formatR need to be listed as a dependency?
If the former (R server config/resource build errors), do I need to
resubmit the package?
Thank you.
J Park
[[alternative HTML version deleted]]
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel