From 2b04c352280a86517ea8893b1f3b761b0faa5655 Mon Sep 17 00:00:00 2001 From: Hadley Wickham Date: Tue, 9 Aug 2022 09:19:47 -0500 Subject: [PATCH] Packrat -> renv Fixes #960 --- rmarkdown-workflow.qmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rmarkdown-workflow.qmd b/rmarkdown-workflow.qmd index 720c4dd..48964a8 100644 --- a/rmarkdown-workflow.qmd +++ b/rmarkdown-workflow.qmd @@ -56,7 +56,7 @@ I've drawn on my own experiences and Colin Purrington's advice on lab notebooks That will let you fix any problems while the code is still fresh in your mind. - If you want your code to be reproducible in the long-run (i.e. so you can come back to run it next month or next year), you'll need to track the versions of the packages that your code uses. - A rigorous approach is to use **packrat**, , which stores packages in your project directory, or **checkpoint**, , which will reinstall packages available on a specified date. + A rigorous approach is to use **renv**, , which stores packages in your project directory. A quick and dirty hack is to include a chunk that runs `sessionInfo()` --- that won't let you easily recreate your packages as they are today, but at least you'll know what they were. - You are going to create many, many, many analysis notebooks over the course of your career.