[R-pkg-devel] JSS article as package vignette introduces a dependency on R >= 4.0.4

[Bennett Nicolas]

Dear all

First, the underlying problem is explained in 
rstudio/rticles#399 (along with 
a reproducible example), but I’ll try to summarize the issue:

As discussed in 
rstudio/rticles#329, a change in 
hook management for LaTeX (see this 
comment) 
broke the jss.cls file included with R (share/texmf/tex/latex/jss.cls). This 
was fixed in R 4.0.4 but as far as I can tell, leaves us with a slightly 
unsatisfying situation for any R package that include a JSS article as vignette 
(and is being built with LaTeX newer than fall 2020):

- either you add a recent copy of jss.cls to the package source and do not 
build-ignore this file; for this you incur a note saying that “The following 
files are already in R ... Please remove them from your package.”
- or the package now depends on R >= 4.0.4

Does anyone know of a way out of this? Or am I missing something?

Thanks,
Nicolas

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] Non-mainstream repository dependence for CRAN vignette building

[Bennett Nicolas]

Dear list

I’m in the process of submitting a package to CRAN that uses a non-mainstream 
repository for several data packages that are too large for CRAN (~50 MB in 
total) and therefore live in a drat repository hosted by gh. Data from these 
packages is used during vignette building and unsurprisingly, CRAN checks throw 
a “re-building of vignette” warning.

1. Is such a warning acceptable or is vignette re-build required to run through?
2. Is it allowed to create a set-up that essentially runs `install.packages()` 
during CRAN checks to make the non-mainstream repo packages available?
3. Are there any go-to solutions for such a scenario? I tried knitr caching, 
but was unsuccessful, to get that to work. What I’m currently doing is masking 
the package function that loads data and supplying the required data with the 
package. But this unnecessarily inflates package size (and adds complexity), as 
the data is already conveniently and separately available as an R package.

Best,
Nicolas
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel