rig v0.11 - initial breakdown

r
rig
tooling
Author
Published

November 6, 2026

Rambling

Understanding

  • rig now indeed has package/proj managmenet making on feature parity with uvr
  • It seems to be more ergonomic than uvr as its maintaind by posit and thus tighter seams with posit tools. highlights include
    • rtools management 
    • IDE (Rstudio and POsitorn) auto-integration
  • These are two very big feature additions that make it a  no-brainer not to adopt
  • However currently rig pck/proj features ar elabled as expeirmental. so lets hold off on this untel they become GA
  • Looking forward to it!! 

References

1. Agent Bullet Points (make a toggle colabspoible later)

Part 1: R installations

  • User mode: installs R without admin rights
  • Portable Linux builds run on any glibc/musl distro
  • rig rtools installs and manages Rtools on Windows
  • Sets up RStudio and Positron automatically
  • P3M is now the default; new repos add and status
  • User mode is less tested than admin mode

Part 2: R packages (rig pkg)

  • Installs packages like pak, without starting R
  • Sources: CRAN, GitHub, git, URLs, local paths
  • Version constraints: @==, ^, ~
  • Dependency solver, parallel downloads, shared cache
  • doctor finds broken or missing dependencies
  • info, deps, tree, search look up packages
  • Installs system deps automatically on major Linux distros
  • The rig website labels it experimental

Part 3: R projects (rig proj)

  • Works like uv or cargo: rproj.toml plus rproj.lock
  • One lockfile covers several platforms and R versions
  • Locked versions stay put until you --upgrade
  • sync builds .rvenv and installs R if missing
  • Projects share package files on disk, so libraries are cheap
  • rig run runs project code or inline-dependency scripts
  • Imports a project from DESCRIPTION or renv.lock
  • devtools and similar tools live in a shared tools library
  • The rig website labels it experimental

2. Feature parity: uvr vs rig

Feature rig v0.11.1 uvr
Install R without admin rights ✅ user mode (admin is still the default) ✅ always
Rtools management ✅ ❌
Default R in RStudio/Positron ✅ set system-wide ⚠️ per-project Positron settings only
Packages outside a project ✅ rig pkg ❌
CRAN/Bioc/GitHub/git/URL/local sources ✅ ✅
Multi-platform lockfile ✅ ✅
Linux system deps ✅ installs them when run as root ✅ installs with a flag
Inline-dependency scripts ✅ ✅
Import from renv ✅ also from DESCRIPTION ✅ renv only
Search/info commands ✅ ❌
Resolution strategies, overrides ❌ ✅
Stability pkg/proj labeled experimental no label; pre-1.0 (v0.4.x)
  • No roadmap exists: no milestones or issues, and no date for dropping the label
  • What the label means: commands, rproj.toml, and rproj.lock formats may change
  • Risk is similar for both: uvr is unlabeled but still pre-1.0
  • Recommendation: try rig now, but expect lockfile churn; asking in rig’s GitHub Discussions is the only way to get an ETA