-
Notifications
You must be signed in to change notification settings - Fork 76
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
Copying packages between minor versions of R can result in broken packages #172
Comments
I agree with removing; clean installing prevents a lot of annoying problems. NB above issues could have been caused by installr, but especially for Windows (e.g., institute-managed computers) another possible culprit could be using a non-R-version-specific R_LIBS_USER (as unfortunately is common in our institute :( ) |
I just got confirmation from the lubridate user that they used installr when they updated, so their frustration was probably because of this issue tidyverse/lubridate#1041 (comment) |
R_LIBS_USER was the culprit in my case. I'm on a corporate system where shared/network/virtual drives are increasingly being used, particularly for common Windows locations - some of them with limited write permissions. This wreaks havoc on some package installs, which could be avoided by specifying a local package directory. It never occurred to me that "up-to-date" packages built in prior versions could be problematic. Hopefully this workaround won't be required given the change to the default Win package location in 4.2 |
It seems like
copy.packages.between.libraries()
can, for example, copy packages from R 4.1.3 over into a package library for R 4.2.0.installr/R/updateR.R
Line 589 in eb2bdc3
I think this is going to cause problems for a lot of people, as packages built with different minor versions of R (4.1 -> 4.2) are not compatible with each other. See this section of the R Windows FAQ:
https://cran.r-project.org/bin/windows/base/rw-FAQ.html#What_0027s-the-best-way-to-upgrade_003f
This kind of problem has resulted in frustrated Windows users with multiple packages:
I don't know if they used installr to update, but it seems like they have a situation that could have been caused by this issue.
Is there any way you could discourage usage of this function, or remove it entirely?
The text was updated successfully, but these errors were encountered: