I would actually go a step in the other direction: per project
libraries. For example by adding a .Rprofile file to your project
directory. This ensures that everybody working on a project uses the
same version of the packages (even on different machines e.g. on shared
folders).
This can
Hi Gene,
"It's complicated". (Not really, but listen for a sec...)
We need to ship a default policy that makes sense for all / most
situations. So
- users cannot write into /usr/local/lib/R/site-library -- unless they are
set up to, but adding them to the 'group' that owns that directory
gt;Warning in install.packages :
> 'lib = "/usr/local/lib/R/site-library"' is not writable
>
>In this question they suggest using the personal library, which is what
>I
>end up doing as well, but some people suggest changing your group.
>This
>actually seems like
/library-is-not-writable
>
> The warning message hasn't changed over the years:
>
> install.packages("randomForest")
> Installing package into ‘/usr/local/lib/R/site-library’
> (as ‘lib’ is unspecified)
> Warning in install.packages :
> 'lib = "/usr/
The warning message hasn't changed over the years:
install.packages("randomForest")
Installing package into ‘/usr/local/lib/R/site-library’
(as ‘lib’ is unspecified)
Warning in install.packages :
'lib = "/usr/local/lib/R/site-library"' is not writable
In this questio
5 matches
Mail list logo
