←back to thread

68 points Keats | 1 comments | | HN request time: 0.203s | source

We have been building a package manager for R inspired by Cargo in Rust. The main idea behind rv is to be explicit about the R version in use as well as declaring which dependencies are used in a rproject.toml file for a given project. There's no renv::snapshot equivalent, everything needs to be declared up front, the config file (and resulting lockfile) is the source of truth. This avoids issue where renv might miss information about the installation and is also easy to tweak some packages, eg install one from source and install suggests from another.

If you have used Cargo/npm/any Python package manager/etc, it will be very familiar.

Show context
mbeavitt ◴[] No.44007409[source]
Can this be used to effectively create R environments? I’m desperate for such a solution.
replies(5): >>44007427 #>>44007510 #>>44007561 #>>44008773 #>>44009817 #
1. Keats ◴[] No.44007561[source]
By default, rv will create a library folder in the same folder as your rproject.toml and there's rv activate/deactivate to add it to your loaded libs. Pretty much the same stuff as a virtualenv in Python.