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 g
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
-
1. Use a personal library. Mucking with the default library puts you at risk of
changing file permissions on your personal files inadvertently and making them
unusable by your normal user. Even if you did alter your user permissions so
you could mess with it without elevating privileges, POSIX i
Hi Gene,
This is probably not best practice, but I install packages as root,
which allows me to write into the default library. The restriction on
non-root users being blocked from making changes to appications is
pretty standard.
Jim
On Thu, Apr 8, 2021 at 8:18 AM Gene Leynes wrote:
>
> Hello R
Hello R Community,
I've been using R for a long time, and this is a question that still makes
me think twice every single time I install R, which is more and more often .
The first search hit is this StackOverflow question:
https://stackoverflow.com/questions/32540919/library-is-not-writable
The
5 matches
Mail list logo
