Closed abugosh closed 10 years ago
The first portion of this has been implemented and merged (was done in the update_rubiez branch). This isn't dynamic by any means, but currently the rubies.yml.example has only the most recent versions of 1.9.3, 1.9.2, 1.9.1, 1.8.7, 1.8.6, JRuby, and RBX (stable). It also included upating to RVM 1.13.0 and RubyGems 1.8.24. I had to tweak the install script slightly due to RVM downloaded tarballs changing their naming convention (they moved to GitHub for hosting the downloads). Rather than try to use their detailed / extensive download tool I just modified the basic script from a few years back to spit out the tarball directory (via tzf | tail -1 | some awk command that worked well).
It's all in master so feel free to play with it and let me know how it works for you. If we can get a few tests added in to verify that the boot:strap process can actually download a sample file (maybe just latest RVM tarball) and then a follow up test to verify that retrieving that file through the RVM::FW URL works properly I'd feel much better about tagging this is a less than perfect, but stable and usable 1.0 at this point.
Thoughts?
The rake bootstrap task should by default download and install the newest Rubies only. If provided with an argument (or perhaps as rake bootstrap:all) it should pull down all of the Rubies currently listed by RVM (not firewall).