[Rd] Best practices in developing package: From a single file
h.wickham at gmail.com
Wed Jan 31 05:44:31 CET 2018
>> There is package.skeleton() in base R as you already mentioned. It drove
>> bonkers that it creates packages which then fail R CMD check, so I wrote a
>> wrapper package (pkgKitten) with another helper function (kitten()) which
>> calls the base R helper and then cleans up it---but otherwise remains
>> faithful to it.
> Failing R CMD check isn't a big deal: you want to be reminded to edit those
> incomplete help files. But I think I recall that you couldn't even build
> the package that package.skeleton() created, and that indeed would be
> irritating, especially if you had a lot of functions so you had a lot of
> cleanup to do. I don't know if that's still true because I generally use
> RStudio to create the initial package structure rather than calling
> package.skeleton myself.
Personally, I think the biggest problem with package.skeleton() is
that it assumes that the source of truth is objects in an environment.
This seems the wrong way around to me.
More information about the R-devel