-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install does not offer the user a chance to create a personal library #431
Comments
I had the same issue today. Will this issue resolved soon? |
Just a +1, and also I don't think this is a feature request. IMO it's a bug. None of our users have write access to BTW, manually creating the Adding a |
R only puts uses I don't believe remotes is doing anything to prevent the normal behavior, the dialog is coming from a call to There is also an straightforward way to work around this issue, create a writable directory manually and put it on your library path. |
Line 46 in ac34fc6
Then So it fails on the case when no element of I wish I had put this in the initial report. |
So can you see the same behavior outside of remotes with the following? lib <- paste(.libPaths(), collapse = .Platform$path.sep)
Sys.setenv("R_LIBS_USER" = lib)
install.packages("xyz") |
Yes, I think so. Edit: Just tried and yes.
|
This seems like a bug in |
I think this is still a remotes issue, remotes munges |
https://github.com/r-lib/remotes/blame/ac34fc67a3d6a56a2c850f77ed3139174747c397/R/install.R#L57 clearly says: lib <- paste(.libPaths(), collapse = .Platform$path.sep)
[...]
with_envvar(
c(R_LIBS = lib,
R_LIBS_USER = lib,
R_LIBS_SITE = lib,
RGL_USE_NULL = "TRUE"), [...] @jimhester you've been around that code, maybe you can do something about it? I can't install on a machine where I have a user but not root. |
Can you create the user library before calling remotes? |
this is still an issue, the "not writable" directory is held by
|
Works for me if I specify lib = .libPaths()[2] as argument, where .libPaths()[2] has the path to my personal library |
The reason why this is an important issue for us is that we have many relatively inexperienced users, and we would really like |
Hi devtools devs, I ran into some somewhat surprising behavour. I administer a multi-user R environment that makes use of modules. I use the modules to point to centrally installed packages, this involves
R_USER_LIBS
. I noticed that across an R version upgrade my users could no longer install packages with devtools. This issue is that users do not have write access to anything on the.libPaths()
,install.packages
prompts the user to create a library whereasinstall_*
does not. Here's a quick example:whereas installing with
install.packages
prompts me to create a user libraryOnce the directory is created
devtools
works fine. Obviously this is not a common issue, but if it was simple to add it would be nice.The text was updated successfully, but these errors were encountered: