[R-pkg-devel] need some help to understand package build workflow

Kevin Ushey kevinushey at gmail.com
Sat Aug 1 00:14:44 CEST 2015

I'm not sure if that's correct -- from what I see, in the generated Rd

- The 'usage' is drawn from the S4 generic,
- The 'arguments' are drawn from the function.

I think R CMD check is correctly warning about that.

On Fri, Jul 31, 2015 at 2:56 PM, Hadley Wickham <h.wickham at gmail.com> wrote:
>>> It seems arguable that this is actually a roxygen bug - the function
>>> that's actually exported from the package does not have a type
>>> argument.
>> The package fails R CMD check because of a bad .Rd file.  If a user had
>> written that file, it would be user error, but roxygen2 wrote it, so I'd
>> say it's pretty clearly a roxygen2 bug.
> It would really help me if you'd explain a little bit more. I think
> the essential problem is that the package has two definitions of f:
> f <- function(x, y) {}
> setGeneric(f, function(x) {})
> Roxygen uses the second definition (because it's the last defined),
> and expects the function to have one argument. R CMD check clearly
> excepts it two have two arguments. It's not obvious to me which is
> correct.
> Hadley
> --
> http://had.co.nz/

More information about the R-package-devel mailing list