(1) worked fine. I chose Ruby 1.9.2. (2) failed, perhaps because
current Ruby already has gems. Once I figured out that it didn’t
matter that (2) didn’t work, (3) worked fine.
As this is somewhat confusing, I’d like to suggest that http://rubyonrails.org/download be updated to note that installing
gems is unnecessary with current Ruby.
(1) worked fine. I chose Ruby 1.9.2. (2) failed, perhaps because
current Ruby already has gems. Once I figured out that it didn’t
matter that (2) didn’t work, (3) worked fine.
I’m guessing 2 must have worked in some manner, as the command “gem
install rails” is calling RubyGems.
Hi,
what about asking or suggesting it in Rails Core mailing list? I’m
sure they have official answer or they can change the note there.
Anyway with Ruby1.9 you got Gems installed, but not in earlier
versions, this is why the note is still there.
Best Regards,
gezope
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.