This is achieved by automatically updating the RPATH of every. The main technical issue here is that libraries are search for only in a few pre-configured places that belong to the system (such as /usr/lib), and thus we need a mechanism to feed our new user-hosted library paths to R packages, hopefully without restarting R and managing environment variables. More specifically, this package uses the path ~/.local/share/R/rspm for this. This is done following the same complementary philosophy: everything is installed as user packages under the home directory. To fill this gap, this package not only provides an easy setup of RSPM, but also monitors and scans every installation for missing system requirements, and then automatically downloads, installs and configures them, relieving the user of this task. The main issue is that the user has still to manage run-time system requirements themselves (i.e., shared libraries required by some packages to work), so this method by itself produces installations that are fundamentally broken. In contrast to the previous solutions, this method allows the user to install binary packages as user packages under their home directory (virtually anywhere), instead of as system packages. On the other hand, RStudio recently took a complementary approach by building binaries-for various distributions, R versions and architectures-and serving them via their own CRAN mirror, also called the RStudio Public Package Manager (RSPM). These are tightly integrated and can be fully managed without leaving the R console thanks to the bspm package. See e.g. the c2d4u.team/c2d4u4.0+ PPA repo for Ubuntu or, more recently, the autoCRAN OBS repo for OpenSUSE, the iucar/cran Copr repo for Fedora, the ArchRPkgs repo for Arch and the r2u repo again for Ubuntu. Several projects over the years tried to lessen this pain by building repositories of binaries that complement and scale up the offer by various distributions. Since always, Linux R users have been struggling with source installations and manual management of build dependencies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |