From gavin.simpson at ucl.ac.uk  Wed Jan 16 22:06:16 2013
From: gavin.simpson at ucl.ac.uk (Gavin Simpson)
Date: Wed, 16 Jan 2013 22:06:16 +0100
Subject: [Rd] Trouble building package using R in development
In-Reply-To: <CABdHhvH8rMf+7_1vSXErW142vR=xctwXw6YyO6m0QyADxt-=nQ@mail.gmail.com>
References: <1358348706.4687.25.camel@chrysothemis.geog.ucl.ac.uk>
	<1358349920.4687.34.camel@chrysothemis.geog.ucl.ac.uk>
	<CAFDcVCQmyZYLpT=vkFaT5feJSS4VcSBKR+VoNAtosVKXBhzU_A@mail.gmail.com>
	<CABdHhvH8rMf+7_1vSXErW142vR=xctwXw6YyO6m0QyADxt-=nQ@mail.gmail.com>
Message-ID: <1358370376.4687.48.camel@chrysothemis.geog.ucl.ac.uk>

On Wed, 2013-01-16 at 14:39 -0600, Hadley Wickham wrote:
> > To circumvent this, I check using:
> >
> > R --no-init-file CMD check foo_1.0.tar.gz
> 
> In devtools, we take considerable care to match the R you're running
> with the R you're checking in, so we also set the following
> environmental variables:
<snip />

Thanks Henrik & Hadley,

> and always run /path/to/current/R --vanilla CMD check ...

To what end is the --vanilla here? Writing R Extensions says that R CMD
check (and R CMD build) are invoked via R --vanilla so that would seem
redundant, although my experience from several hours working this
through today suggests there is a difference between R --vanilla CMD
check and R CMD check.

G

> Hadley
> 

-- 
%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%
 Dr. Gavin Simpson             [t] +44 (0)20 7679 0522
 ECRC, UCL Geography,          [f] +44 (0)20 7679 0565
 Pearson Building,             [e] gavin.simpsonATNOSPAMucl.ac.uk
 Gower Street, London          [w] http://www.ucl.ac.uk/~ucfagls/
 UK. WC1E 6BT.                 [w] http://www.freshwaters.org.uk
%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%



[Rd] Trouble building package using R in development
Gavin Simpson