From marc_schwartz at me.com  Tue Jul  1 18:17:54 2014
From: marc_schwartz at me.com (Marc Schwartz)
Date: Tue, 01 Jul 2014 11:17:54 -0500
Subject: [Rd] creating a package from a development source tree
In-Reply-To: <54522.1404228398@greg-minshalls-mbp.local>
References: <54522.1404228398@greg-minshalls-mbp.local>
Message-ID: <67FEF72F-20B8-41E2-AFE4-A8B7D0A0614F@me.com>

On Jul 1, 2014, at 10:26 AM, Greg Minshall <minshall at acm.org> wrote:

> hi.  this is sort of a software methodology question.
> 
> i'm working on developing a package (with C source code).  developing
> it, i use autotools, git, make, and such like.  as a result, there are
> random files in my source code directory that "R CMD check" would rather
> not see.  some of these files (such as .git and friends) i could arrange
> to move to "just above" my development subtree; others of these (such as
> configure.ac and the random crud autoreconf(1) and friends leave laying
> around) can't be moved (afaik).
> 
> i'm curious how people move from their personal development tree to a
> tree from which the package can be passed to "R CMD *".  do "you" have a
> makefile in their tree that creates this?  during development, is this
> the path you use for building and testing?
> 
> cheers, Greg Minshall


Hi,

Run 'R CMD check' on the file built from 'R CMD build', rather than on the actual package source file tree, as per:

  http://cran.r-project.org/doc/manuals/r-patched/R-exts.html#Checking-packages

from the Writing R Extensions manual.

You can also use the file .Rbuildignore to define files that should be excluded. See the fifth paragraph in:

  http://cran.r-project.org/doc/manuals/r-patched/R-exts.html#Building-package-tarballs


Regards,

Marc Schwartz



[Rd] creating a package from a development source tree
Marc Schwartz