Solution was simple, once I found it. Change the bang line in the rake.rb, found via 'which rake' to point to the ruby version that houses the gems. Now things work.
Put differently, now its not broken. The breakage came as a result of Rails using the $PATH variable when installing gems, not when it runs rake. So, yes, rails is broken in this case – this underdocumented behaviour arose not out of misconfiguration, but the normal use of the $PATH producing a non-functional behaviour. Next time, feel free to provide an actual answer, or refrain from answering if the best contribution is limited to patronizing snark. BTW, are you wearing shoes these days? Don't want to hurt your feet when you're Morris Dancing Ze'ev. Or should I call you Lord Marnen of Wolfhurst? heheheh. On Oct 5, 5:22 pm, Marnen Laibow-Koser <li...@ruby-forum.com> wrote: > omnivore wrote: > > I love Rails, but I'm beginning to think that there are some very > > broken things about it. > > [...] > > As Fred said, Rails isn't broken. Your Ruby installation is. Next > time, ask for help without creating FUD. > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > mar...@marnen.org > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
