![]() This allows for a clean and safe upgrade of R. To make R upgrades easy the R GUI Package Installer offers specifically the option to install packages from the previous R version. Packages are not compatible beyond the patch version so the current setup avoids the most common problem where users inadvertently use packages installed for an incompatible previous R version leading to crashes. Also note that packages are never removed by the installer. The choice is deliberate: the admin group on macOS corresponds to users that are allowed to install system-wide software so it allows all admins on the machine to install packages which is the expected way on macOS.Īlso the versioning of the R framework as x.y is also deliberate - upgrading R to a new patch version does *not* require re-installation of packages, they work by design so in fact the system location is the safest way to do that. R-SIG-Mac mailing for starting the discussion. Getting to know the reason for this decision. If this is not possible for some reason, I would also be interested in Publicly available? I could not find it and would be interested to take Last, I wanted to ask if the source code for the CRAN installer is If for some reasons 755 cannot be set for the `R.frameworks`ĭirectories, then the group defined for `R.frameworks` (and recursiveĭirectories) could possibly be changed to prevent direct writes access `R -q -e ".libPaths()"` (should return two libraries, with the user `R -q -e ".libPaths()"` (should only return the system library)ĥ. `sudo chmod -R 755 /Library/Frameworks/R.framework/`ģ. Install R for Mac via the CRAN installerĢ. RStudio does it even silently in the background (which is quite niceġ. ![]() Would you like to create a personal library Would you like to use a personal library instead? (yes/No/cancel) "/Library/Frameworks/R.framework/Versions/4.1-arm64/Resources/library"' "/Library/Frameworks/R.framework/Versions/4.1-arm64/Resources/library" While R in the terminal offers the creation of the user lib if I've tested this in a few scenarios and did not face any issues.Īlso I've come across an interesting observation while doing so: I don't see a reason why write permissions for the `admin` group would # How can the following possibly be solved?ĪFAICS the easiest way would be to set 755 instead of 775 permissionsįor the `/Library/Frameworks/R.framework/` folder. However, most R users don't want to bother with this and are no experts `$HOME/Library/R/arm64/4.1/library`), R will pick it up and packages ![]() If a user manually creates a user library at the expected path (e.g In case you are wondering why R does not offer to create a user libraryĪs on other platforms: if the system library is writable (or R detectsĪny writable library configured in the repos option), the prompt will users are forced to reinstall all packages for every patch version Platforms), the above also causes many unneeded R package downloads,Į.g. Platforms (which constantly causes confusion for R users switching on other platforms (Windows, Linux) the system library is not writableīy default, hence the behaviour of the macOS CRAN installer is differentīesides the differing experience for users on macOS compared to other if a new R version is installed, all packages in the system libraryĪre lost as they are getting overwritten by the CRAN installer user packages are mixed with system packages the library which stores the package which areīundled with the installer (base, MASS, parallel, etc.). the user is a member of theīeing a member of `admin` group gives subsequently write access into the This is usually also an administrator, i.e. Many users use a Mac in a single-user setup, i.e. The group for `/Library/Frameworks/R.framework/` is `admin`. In contrast to 755, 775 also gives the defined group write permissions. The installers installs R into `/Library/Frameworks/R.framework/` with I'd like to discuss the current directory permissions set by the CRAN
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |