Need to update RVM::FW to work with RVM 1.0.16's known rubies

[stevenhaddox]

Utilize: http://github.com/wayneeseguin/rvm/blob/master/config/known to help us identify which versions of Ruby are worth keeping in RVM::FW.

I don't have the largest Github plan and so we need to be specific as to which Rubies will be most used... initial thoughts from me are:

# Rubies
ruby_1.9.1_patch_level=378
ruby_1.9.2_patch_level=0
ruby_1.8.5_patch_level=231
ruby_1.8.6_patch_level=399
ruby_1.8.7_patch_level=299
ruby_1.8.7_patch_level=302
rubygems_1.3.6_url=http://rubyforge.org/frs/download.php/69365
rubygems_1.3.7_url=http://rvm.beginrescueend.com/src/
rbx_1.1.0_patch_level=20100923
ree_1.8.7_patch_level=2010.02
jruby_version=1.5.3
macruby_version=0.7.1
#maglev_version=24407  
#ironruby_version=1.0

These versions need to be placed into: rvm_fw_root/public/rubies/ and older / non-working versions (e.g. IronRuby, plaintext typo files from RailsConf) deleted.

Also, make sure that you maintain any folder structure currently in place. The folder name "prefixes" come from RVM's abbreviation for the Ruby version in order to ensure consistency.

This also requires us properly updating the user custom config file: http://github.com/stevenhaddox/rvm_fw/blob/master/views/db.txt

[codelotus]

Why store all supported rubies in the project src? Would it make sense to create a 'bootstrap' rake task, that a user would run, which downloads the necessary versions and places them in the appropriate directory?

[stevenhaddox]

If it's not in source... how does it work behind a firewall as a standalone app? To clarify: I want to be able to have users point their tech support to a Github tarball, import it, and have it run by itself with a simple config.ru tweak.

[codelotus]

I would imagine this workflow:

1. user clones the rvm_fw repo
2. user runs a bootstrap rake task does the following
   • reads a config file and downloads all of the specified rubies and places them in the public/rubies folder
   • pulls the supported rvm tag from wayneeseguin's repo and adds it to the public folder

The user can now burn the bootstrapped repo to a cd or copy it to a thumb drive and bring it to their corporate env.

[stevenhaddox]

I'm open to this as long as we create / document in the README the folder structure / versions of Rubies that are supported and pulled in. I definitely want links to all the proper download URLs that we'll maintain in the README for users in case they don't have git installed. Feel free to hack away ;)

[codelotus]

cool

[stevenhaddox]

Let's go ahead and run with the following Rubies for the bootstrapper:

• MRI Rubies:
  • 1.9.2-p0
  • 1.9.1-p378
  • 1.8.7-p302
  • 1.8.6-p399
• JRuby:
  • 1.5.3
• REE:
  • 1.8.7
• Rubinius:
  • 1.1.0-p20100923
• MacRuby:
  • 0.7.1

[stevenhaddox]

Bootstrap started at: http://github.com/stevenhaddox/rvm_fw/issues/issue/6