![]() When you start an R session in a packrat project directory, R will only look for packages in your private library and anytime you install or remove a package, those changes will be made to your private library. We call this directory your private package library (or just private library). Packrat enhances your project directory by storing your package dependencies inside it, rather than relying on your personal R library that is shared across all of your other R sessions. If you’re like the vast majority of R users, when you start working on a new R project you create a new directory for all of your R scripts and data files. The last ‘snapshotted’ state, which can be used to save and restore the state of the private library. The project private library, containing R packages your project is using, and.Maintains two components of your project:.Packrat is an R package that implements a dependency management system for R:Ĭreates a private package library for a given R project (i.e. working directory) Individual projects should be able to freeze arbitrary combinations of R packages with a guarantee of being able to use them in the future. This is already a widely observed problem with R scripts and Sweave/knitr documents that users attempt to re-run years (or even months) after they are originally developed.įreezing is the answer, but what to freeze?įreezing CRAN solve only a subset of the problem, and introduces its own problems.No changes to CRAN are required to provide a highly robust system of R package dependency management The only complete answer to this problem is freezing projects. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |