Packrat presentation at useR! 2014

[This article was first published on Data Science Los Angeles » R, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

There comes a time in a software toolchain’s lifecycle where the focus shifts from developer productivity and preference to the ability to deploy solutions in production which coexist gracefully in the enterprise. Configuration management and dependency management are two of the first points of friction in this transition, as the free-wheeling methods preferred by developers are at odds with the structured methods and isolation desired by administrators, who serve as gatekeepers to enterprise deployment. R is currently at this very point in the transition, in the midst of transformation from a language and environment used primarily in academic research to its growing place in the enterprise. At useR! 2014 there were a series of presentations on how dependency management can be addressed within the R ecosystem, ranging from “provider” side options (e.g. freezing CRAN and private repositories) to the client side options, where a project maintains its own dependencies as part of its codebase.

In the video above, JJ Allaire and Kevin Ushey give a detailed presentation of Packrat at useR! 2014. Packrat is a client-side solution which allows a project to manage dependencies within its own directory tree. This is a tried and true approach, currently utilized in communities from Ruby to Perl. Packrat allows the developer to isolate projects from each other, even though they may share the same operating system image and physical hardware. This allows two separate projects to use completely different versions of the same library and coexist gracefully, an impossibility without such solutions. Packrat also allows for greater reproducibility, as underlying changes in system libraries will no longer impact the results of a run. Finally, packrat provides deployment portability by bundling all of an R application’s dependencies within the project, thereby freeing the DevOps group from having to build Puppet/Ansible/Chef code which installs R packages as a dependency for deploying a project.

I have adopted this package for all new R projects and have personally experienced greater peace of mind in knowing that in some small part, this approach makes the integration of my projects easier on the enterprise and helps make R a “well behaved” member of the enterprise toolchain. I hope you find similar benefits by using Packrat in your own work!

To leave a comment for the author, please follow the link and comment on their blog: Data Science Los Angeles » R. offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)