building and installing via devtools reports success ( ** testing if
installed package can be loaded from temporary location ), however, a
subsequent attempt to load hangs.
On Sat, Jun 11, 2022 at 6:33 AM Joseph Park wrote:
> Apologies for the pages of minutia. I endeavored to post reproducea
knitr
> VignetteDepends: rmarkdown, formatR
>
> It should make the above process a bit clearer. It would also make it
> clear to those who are only interested in viewing vignettes, but have
> no interest in rebuilding vignettes, what packages they need to
> install in order to acces
in ‘VignetteBuilder’."
>
> So I think you need
>
> Suggests: knitr, rmarkdown, formatR
> VignetteBuilder: knitr, rmarkdown, formatR
>
> On Fri, Nov 13, 2020 at 3:23 PM Joseph Park wrote:
>> Ah, yes... I see it now in Writing R Extensions. Apologies for the
>> o
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 wrote:
Dear r-package-devel,
The rEDM package is failing the automated check, as noted here:
h
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
ve another follow-up. Private
> email is not efficient / has no second or third or ... set of eyes.
>
> On 15 October 2020 at 07:53, Joseph Park wrote:
> | Thanks for the clarification.
> |
> | One last caveat: the C++ code already has a hook presuming #define
> | USING_R. D
Dear R-devel,
The Writing R Extensions manual states:
6.14 Platform and version information
The header files define USING_R, which can be used to test if the code
is indeed being used with R.
I suppose this only applies to building R itself? Or, perhaps when Rcpp
is used for the interface,
