[Rd] Strategies for keeping autogenerated .Rd files out of a Git tree

Gábor Csárdi csardi.gabor at gmail.com
Fri Dec 13 21:24:40 CET 2013

Oh, I didn't know RForge.net supported external git repos, cool!


On Fri, Dec 13, 2013 at 3:14 PM, Simon Urbanek
<simon.urbanek at r-project.org> wrote:
> FWIW this is essentially what RForge.net provides. Each GitHub commit triggers a build (branches are supported as the branch info is passed in the WebHook) which can be either "classic" R CMD build or a custom shell script (hence you can do anything you want). The result is a tar ball (which includes the generated files) and that tar ball gets published in the R package repository. R CMD  check is run as well on the tar ball and the results are published.
> This way you don't need devtools, users can simply use install.packages() without requiring any additional tools.
> There are some talks about providing the above as a cloud service, so that anyone can run and/or use it.

More information about the R-devel mailing list