Linus--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/gPGqXIyHy-gJ.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Should one do rake rails:update also, just in case any scripts have
changed? Or is that no longer required under rails 3?
Colin
--
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Is it not better just to run it anyway? It is easier to run it than
it is to try and work out whether it is necessary to run it.
Colin
gem 'sass-rails', '~> 3.1.4'
gem 'coffee-rails', '~> 3.1.1'
gem 'uglifier', '>= 1.0.3'
> Hasn't some other gems changed?
> Are these still the default in 3.1.3?
Easiest way to find out is to create a dummy project using 3.1.3 and
see what gets installed when you run `bundle install` :-)
Alternatively, you can run `bundle update` on your existing 3.1.1 app,
edit the Gemfile to specify rails 3.1.3 and run `bundle update` again to
see what changes...
FWIW,
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
http://about.me/hassanschroeder
twitter: @hassan