Jon,
I have had a similar problem when installing librarys. I have written a
script which uses biocLite to install librarys.
I have included the following code which hides .Rprofile by renaming it
and then renaming it back again after it has finished.
#Hide .Rprofile whilst this script is run
I would also be interested in knowing what the rationale is for this.
Moreover, it seems that the "standard" (and documented) approach to
this of calling "options(defaultPackages=c(...))" in ~/.Rprofile does
not get ignored when installing. The environment variable approach may
work, but it seems
On 02/16/2011 10:57 AM, Prof Brian Ripley wrote:
The most obvious answer is not to do that. You have not used the
standard mechanism to to do that (which should work here as R CMD
INSTALL overrides that one). It's all in ?Startup (look for
R_DEFAULT_PACKAGES).
Note that R CMD INSTALL is not men
The most obvious answer is not to do that. You have not used the
standard mechanism to to do that (which should work here as R CMD
INSTALL overrides that one). It's all in ?Startup (look for
R_DEFAULT_PACKAGES).
The simplest way to ignore ~/.Rprofile is to set R_PROFILE_USER to
something el
Dear all,
Is there a way to force R CMD INSTALL to ignore ~/.Rprofile and
similar? I presume it sources these startup files for a reason, but
I've found that it can cause confusion or problems. In particular, my
~/.Rprofile loads a few packages which I very frequently use, but this
stops me from i
