cache hugo dependency

[maxheld83]

I'm a big fan of making projects self-contained, and I particularly for scientific projects, I worry about whether I will be able to change (something small) a couple of years down the road, without going into dependency hell.

packrat does a nice job of this, and so does bookdown, which, I understand, actually ships with all of its dependencies (for example, all of the gitbook.io stuff).

As far as I understand, this also extends to blogdown, with the exception of Hugo itself via blogdown::install_hugo().

I worry that this might make it hard to reproduce and/or fix small things in projects years down the road, when hugo may have changed quite a lot.

I've been burnt by this with regard to Jekyll, which kept changing (improving) over the years, but has made it hard to edit old projects.

Is there any chance to somehow cache the hugo dependency with blogdown or even via packrat?

[maxheld83]

blogdown::install_hugo(version = ) of course, does some of this (unless/until past versions are no longer available), so this maybe is a fairly low probability, low priority issue.