<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Renv on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/renv/</link>
    <description>Recent content in Renv on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 15 Mar 2022 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/renv/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Reproducible {distill} posts with {renv} profiles</title>
      <link>https://www.rostrum.blog/2022/03/15/renv-profiles/</link>
      <pubDate>Tue, 15 Mar 2022 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2022/03/15/renv-profiles/</guid>
      <description>tl;dr I think you can use the {renv} package to create separate reproducible environment profiles for each of your {distill} blog posts.
 Profiled Functionality comes and goes in R packages. How do you deal with that in the context of a blog built with R? What if you need to go back and change something in a post from four years ago?1
I built a demo {distill} blog to test whether the {renv} package might be a viable solution for reproducibility on a post-by-post basis.</description>
    </item>
    
  </channel>
</rss>