> 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
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 v
> 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:
env <- c(
"LC_ALL" = "C",
"R_LIBS" = paste(.libPaths
On Wed, Jan 16, 2013 at 8:59 AM, Henrik Bengtsson wrote:
> On Wed, Jan 16, 2013 at 7:25 AM, Gavin Simpson
> wrote:
>> As a follow-up, shortly after I clicked send I decided to do something
>> silly and rename my ~/.Renviron (which set R_LIBS too). Silly because
>> the Writing R Extensions (WRE)
On Wed, Jan 16, 2013 at 7:25 AM, Gavin Simpson wrote:
> As a follow-up, shortly after I clicked send I decided to do something
> silly and rename my ~/.Renviron (which set R_LIBS too). Silly because
> the Writing R Extensions (WRE) manual says that these startup files are
> not read as R is invoke
As a follow-up, shortly after I clicked send I decided to do something
silly and rename my ~/.Renviron (which set R_LIBS too). Silly because
the Writing R Extensions (WRE) manual says that these startup files are
not read as R is invoked with --vanilla.
Once I renamed ~/.Renviron so it was not bei
