Saturday, December 25, 2010
On 25 December 2010 17:27, Marnen Laibow-Koser <lists@ruby-forum.com> wrote:
-- Gordon Yeong wrote in post #970555:
[...]
> Problem solved but i somehow think removingWhere did you get that idea? Removing vendor/rails is exactly right in
> vendor/rails is not so right....
this case -- it's only purpose is to override the system Rails gems. If
you want to freeze 2.3.8 into vendor/rails, you can do so.
Marnen, you were right on the money!
"Probably because it's picking up 2.3.2 from vendor/rails.".
thank you for that :)
Note, however, that 2.3.9, and I think 2.3.8, have serious security
holes. I'd recommend upgrading to 2.3.10 as soon as possible.
Yep, I m testing the application and making sure it works on 2.3.8. Once it is stable, I shall look at 2.3.10
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-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment