I''ve got rails set up on OSX using the Mac installer from http://homepage.mac.com/discord/Ruby/. Using the installer I opted to install gems (which I think is version 0.8.4 in the installer package) but not Rails. "ruby -v" gives: ruby 1.8.2 (2004-12-25) [powerpc-darwin7.8.0] I then updated gems using: gem install rubygems-update update_rubygems Which got me to 0.8.10 Finally, "gem install rails" seemed to grab all the necessary stuff successfully. However, doing "rails -v" gives: rails: unknown version So far, I haven''t seen any weird stuff going on during the course of development. But I can''t help but think something low-level is causing the above error which is a symptom of a larger (configuration?) issue, and it''s going to bite me somewhere down the line. This behaviour has existed after a "fresh" install of 0.11.1 and through an upgrade to 0.12.0 today. Anyone encounter this behaviour? Is it something I should be worried about? If so, what can I do to correct it? Thanks!
Running Slackware 10.1 Linux here with ruby 1.8.2, gem 0.8.10. And i have the same "unknow version" message when I run "rails -v" I think its not a big deal. Everything works fine. 2005/4/19, Lester <dumpingrounds-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:> > I''ve got rails set up on OSX using the Mac installer from > http://homepage.mac.com/discord/Ruby/. Using the installer > I opted to install gems (which I think is version 0.8.4 in > the installer package) but not Rails. "ruby -v" gives: > > ruby 1.8.2 (2004-12-25) [powerpc-darwin7.8.0] > > I then updated gems using: > > gem install rubygems-update > update_rubygems > > Which got me to 0.8.10 > > Finally, "gem install rails" seemed to grab all the > necessary stuff successfully. However, doing > "rails -v" gives: > > rails: unknown version > > So far, I haven''t seen any weird stuff going on > during the course of development. But I can''t > help but think something low-level is causing the > above error which is a symptom of a larger > (configuration?) issue, and it''s going to bite > me somewhere down the line. This behaviour has > existed after a "fresh" install of 0.11.1 and > through an upgrade to 0.12.0 today. > > Anyone encounter this behaviour? Is it something > I should be worried about? If so, what can I do > to correct it? > > Thanks! > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Giovanni Degani tiefox-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ICQ 965609 _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 19.4.2005, at 20:44, Lester wrote:> > > Anyone encounter this behaviour? Is it something > I should be worried about? If so, what can I do > to correct it?Don''t worry about it. I''ve been running rails for ages (well, ages in Rails'' world) and seem to get the same (haven''t run rails -v before). You should probably file a ticket on it at http://dev.rubyonrails.com, tho. //jarkko> > Thanks! > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails