On 13 October 2018 at 10:42, Kevin Ushey wrote:
| I can reproduce if the 'pkgKitten' package is not installed. In that
| case, I see in man/<pkg>-package.Rd:
|
| \examples{
| ~~ simple examples of the most important functions ~~
| }
|
| which of course is just a stub and not valid example code (and so
| fails during check).
|
| I think this is just gunk that gets inserted by R's own
| package.skeleton(), which pkgKitten normally tries to clean up for
| you. See e.g.
|
|
https://github.com/wch/r-source/blob/ff36007c3562e8c7a8517ae15196429fd9f8fb6d/src/library/utils/R/prompt.R#L379-L380
|
| tl;dr: install pkgKitten and make your life easier.
Now *that* is a recommendation I can get behind :)
It is in fact a suggested package for Rcpp too.
And ...
| On Fri, Oct 12, 2018 at 1:18 PM Dirk Eddelbuettel <e...@debian.org> wrote:
[...]
| > Thanks for posting versions. This sounds ... weird.
| >
| > 1) The issue of 'failing' over these left-overs from the skeleton annoyed me
| > so much (many years ago!!) that I wrote a new helper package 'pkgKitten'.
| >
| > 2) 'pkgKitten' is used (if present) by
| > Rcpp.package.skeleton() # in Rcpp
| > RcppArmadillo.package.skeleton() # in RcppArmadillo
Now we are reminded that RStudio's package generator uses it too.
| > 3) They work.
| >
| > 4) I just tried your example (of using RStudio's facilities -- which I also
| > use regularly) and COULD NOT reproduce this on
| > RStudio 1.1.456
| > RStudio 1.2.1030
... because I keep pkgKitten around on my systems.
All good, Dirk
| > So I am stumped. Kevin: Any idea?
| >
| > Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
