RStudio just released the public beta of the RStudio Package Manager. What's up next?
On the short term horizon, we’re working on two exciting features:
- The ability to version repositories and “freeze” them. You may have noticed that in RStudio Package Manager a repository URL includes “/latest”. RStudio Package Manager automatically versions every change to a repository with a unique ID that can be used in place of “latest”. In the next release, we’ll provide users access to these IDs so that in certain contexts they can install packages from a “frozen” repository. For example, the following line in a Dockerfile would be guaranteed to always return the same packages when the container is rebuilt:
RUN R -e "install.packages(..., repo = "https://our-rspm.example.com/repo/118")
- RStudio Package Manager allows organizations to host internal R packages alongside packages from CRAN. This mechanism can also be used to host packages from GitHub. However, we recognize that updating these packages can be a pain. (Today, someone has to create the bundled version of the package and then an admin has to use the CLI). In the near future, you’ll be able to point RStudio Package Manager at a Git repo and RStudio Package Manager will handle automatically watching for commits or tagged releases and deploying those changes automatically.
In the longer term horizon, we’re excited to work on package binaries. As part of this work, RStudio Package Manager will also be able to answer an age-old question for Linux admins, “What system dependencies do I need for package xyz?”
What else should we be working on?