> Duncan Murdoch
> on Fri, 13 Nov 2020 17:45:44 -0500 writes:
> On 13/11/2020 4:32 p.m., Gábor Csárdi wrote:
>> On Fri, Nov 13, 2020 at 9:02 PM Duncan Murdoch
wrote:
>> [...]
>>> Things may have changed since Henrik and I wrote the code, but his
>>> description m
On 13/11/2020 4:32 p.m., Gábor Csárdi wrote:
On Fri, Nov 13, 2020 at 9:02 PM Duncan Murdoch wrote:
[...]
Things may have changed since Henrik and I wrote the code, but his
description matches my understanding as well (and I think he's
contributed more recently than I have).
The way non-Sweave
On Fri, Nov 13, 2020 at 9:02 PM Duncan Murdoch wrote:
[...]
> Things may have changed since Henrik and I wrote the code, but his
> description matches my understanding as well (and I think he's
> contributed more recently than I have).
>
> The way non-Sweave vignettes work is that some packages re
On 13/11/2020 1:48 p.m., Gábor Csárdi wrote:
On Fri, Nov 13, 2020 at 6:10 PM Henrik Bengtsson
wrote:
I'm quite sure you want to use the following:
Suggests: knitr, rmarkdown, formatR
VignetteBuilder: knitr
So this means that WRE is wrong? It says:
> "Note that if, for example, a vignette
On Fri, Nov 13, 2020 at 6:10 PM Henrik Bengtsson
wrote:
>
> I'm quite sure you want to use the following:
>
> Suggests: knitr, rmarkdown, formatR
> VignetteBuilder: knitr
So this means that WRE is wrong? It says:
"Note that if, for example, a vignette has engine ‘knitr::rmarkdown’,
then knitr pr
Thank you for the clarification.
J Park
On 11/13/20 1:09 PM, Henrik Bengtsson wrote:
> I'm quite sure you want to use the following:
>
> Suggests: knitr, rmarkdown, formatR
> VignetteBuilder: knitr
>
> Here are the details. For the 'VignetteBuilder' field, you want to
> put all packages that pro
I'm quite sure you want to use the following:
Suggests: knitr, rmarkdown, formatR
VignetteBuilder: knitr
Here are the details. For the 'VignetteBuilder' field, you want to
put all packages that provide the **vignette engines** you are using.
For example, if your package vignettes use either of
Thank you.
On 11/13/20 10:31 AM, Gábor Csárdi wrote:
> >From WRE:
>
> "Note that if, for example, a vignette has engine ‘knitr::rmarkdown’,
> then knitr provides the engine but both knitr and rmarkdown are needed
> for using it, so both these packages need to be in the
> ‘VignetteBuilder’ field an
>From WRE:
"Note that if, for example, a vignette has engine ‘knitr::rmarkdown’,
then knitr provides the engine but both knitr and rmarkdown are needed
for using it, so both these packages need to be in the
‘VignetteBuilder’ field and at least suggested (as rmarkdown is only
suggested by knitr, an
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: k
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
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 wi
12 matches
Mail list logo
