From csardi.gabor at gmail.com  Fri Dec 13 21:24:40 2013
From: csardi.gabor at gmail.com (=?ISO-8859-1?B?R+Fib3IgQ3PhcmRp?=)
Date: Fri, 13 Dec 2013 15:24:40 -0500
Subject: [Rd] Strategies for keeping autogenerated .Rd files out of a
	Git tree
In-Reply-To: <0C2772D3-C8CD-4437-B112-4DD0AD7D084C@r-project.org>
References: <52A905CB.4020701@ivt.baug.ethz.ch>
	<CABtg=KkgGqaQOYSfzAnXfdgfK0UojLEjsd=amzc=BThS4EV7+w@mail.gmail.com>
	<52AAE990.1050102@ivt.baug.ethz.ch>
	<175312B6-9672-4C71-AB2F-AFA05A06162C@r-enthusiasts.com>
	<52AB10EF.9070503@ivt.baug.ethz.ch>
	<0C2772D3-C8CD-4437-B112-4DD0AD7D084C@r-project.org>
Message-ID: <CABtg=Kn4H8yz7bV7QK+nGqd0XXoGawNwqTQD5_460iXS-JzfYw@mail.gmail.com>

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

Gabor

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.
>
[...]



[Rd] Strategies for keeping autogenerated .Rd files out of a Git tree
=?ISO-8859-1?B?R+Fib3IgQ3PhcmRp?=