Skip to content
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

Default User Home Personal Library creation in Linux is still prefixed 3.3 for MRO 3.4.0/3.4.1/3.4.2 #27

Closed
mjmg opened this issue May 27, 2017 · 4 comments

Comments

@mjmg
Copy link

mjmg commented May 27, 2017

On Linux , the default library install location proposed/used is still on the subdirectory named "3.3"

Tested under both RPM and Debian based environments.

> install.packages("packagename")                                                                                                
Warning in install.packages("packagename") :
  'lib = "/usr/lib64/microsoft-r/3.4/lib64/R/library"' is not writable
Would you like to use a personal library instead?  (y/n) y
Would you like to create a personal library
~/R/x86_64-pc-linux-gnu-library/3.3
to install packages into?  (y/n) 

For Windows, it is correctly on a "3.4" subdirectory.

~/R/win-library/3.4
@mjmg mjmg changed the title Default User Home Personal Library creation in Linux is still prefixed 3.3 for MRO 3.4.0 Default User Home Personal Library creation in Linux is still prefixed 3.3 for MRO 3.4.0/3.4.1 Sep 19, 2017
@mjmg
Copy link
Author

mjmg commented Sep 19, 2017

This issue still exists for MRO 3.4.1 under Linux.

@mjmg
Copy link
Author

mjmg commented Oct 29, 2017

This issue still exists for MRO 3.4.2 under Linux. I will be surely disappointed if this gets carried over to MRO 3.5.X

@mjmg mjmg changed the title Default User Home Personal Library creation in Linux is still prefixed 3.3 for MRO 3.4.0/3.4.1 Default User Home Personal Library creation in Linux is still prefixed 3.3 for MRO 3.4.0/3.4.1/3.4.2 Oct 29, 2017
@mjmg
Copy link
Author

mjmg commented Jan 25, 2018

Seems to be fixed in MRO 3.4.3 under Linux

@richcalaway
Copy link

Yes, this was fixed in MRO 3.4.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants