Practical {renv}
summary
Example project jsonlite-example shows that renv::restore() can download nineteen packages in twenty-five seconds and still fail when binaries for that R/package/R-version combo are unavailable. The workflow diagnoses failures with pkgbuild::check_build_tools() to confirm compilation ability, uses rig to revert to the original R (4.4.2) or points to P3M for older binaries, or uses renv::checkout()/renv::upgrade()+renv::install()+snapshot to manage or update; claim: renv helps but demands explicit user configuration and regular updates.
AI-written summary · about
chapters (13)
- 0:00Introduction to {renv}
- 2:09What {renv} does and doesn’t
- 4:42Package libraries and {renv}
- 7:18{renv.lock} file explained
- 8:22Source vs binary install
- 9:07Projects over time decisions
- 10:54Diagnosing restore errors
- 13:55Avoiding uncharted territory
- 14:41Freezing project with {renv}
- 16:08Managing project environments
- 17:37Long-term sustainability
- 18:44Beyond {renv} with containers
- 19:05Closing and resources
related talks
11mYou should be using renv
59mEmbracing multi-lingual data science
27muv: Ultimate Victory over Installation and Dependency Chaos
31mBuilding an extremely fast Python package manager, in Rust
36mPipenv: The Future of Python Dependency Management
10mHow to Run Your Favorite Python Package in R
34mAdventures in pip land
35mEffective Python and R collaboration