[Rd] Please explain your workflow from R code -> package -> R code -> package

From: Paul Johnson <pauljohn32_at_gmail.com>
Date: Fri, 09 Sep 2011 11:38:12 -0500


I'm asking another one of those questions that would be obvious if I could watch your work while you do it.

I'm having trouble understanding the workflow of code and package maintenance.

Stage 1. Make some R functions in a folder. This is in a Subversion repo


Stage 2. Make a package:

After the package.skeleton, and R check, I have a new folder with the project in it,


I to into the man folder and manually edit the Rd files. I don't change anything in the R folder because I think it is OK so far.

And eventually I end up with a tarball mypackage_1.0.tar.gz.

Stage 3. How to make the round trip? I add more R code, and re-generate a package.

package.skeleton obliterates the help files I've already edited.

So keeping the R code in sync with the documentation appears to be a hassle.

In other languages, I've seen to write the documentation inside the code files and then post-process to make the documentation. Is there a similar thing for R, to unify the R code development and documentation/package-making process?


Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas

R-devel_at_r-project.org mailing list
Received on Fri 09 Sep 2011 - 16:42:22 GMT

This quarter's messages: by month, or sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

All messages

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Sun 11 Sep 2011 - 01:10:28 GMT.

Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-devel. Please read the posting guide before posting to the list.

list of date sections of archive