When new rubies come out (like 2.0.0-p353), it would be nice to be able to just add the ruby name like 2.0.0-p353 and have your module re-clone git://github.com/sstephenson/rbenv.git. Right now, it complains that 2.0.0-p353 doesn't exist in ~/.rbenv/plugins/ruby-build/share/ruby-build, but that would be solved if the repo were re-cloned.
This is a great project. Thank you for sharing.
When new rubies come out (like 2.0.0-p353), it would be nice to be able to just add the ruby name like
2.0.0-p353
and have your module re-clonegit://github.com/sstephenson/rbenv.git
. Right now, it complains that2.0.0-p353
doesn't exist in~/.rbenv/plugins/ruby-build/share/ruby-build
, but that would be solved if the repo were re-cloned.Is there a way to force this to re-evaluate? Or could the
schedule
metaparameter solve this? http://docs.puppetlabs.com/references/latest/metaparameter.html#schedule