3 ms·
That says to me that understanding bundler is REALLY important. If someone understood how bundler worked, there is NO reason therubyracer, twitter-bootstrap-ra
by jrochkind1 14y ago
That says to me that understanding bundler is REALLY important.
If someone understood how bundler worked, there is NO reason therubyracer, twitter-bootstrap-rails, libv8, or any other gem should get in the way of upgrading (say for example) from Rails 3.2.5 to 3.2.11. `bundle update rails`, then check in your new Gemfile.lock
That should change nothing but Rails and rails' own upstream dependencies (not any of the ones you mention). And indeed it did that for me on a bunch of apps. If you're going up a minor or major Rails version, then your other gems (like say twitter-bootstrap-rails, hypothetically) might not be compatible with the new rails version, and you might have some dependency hell.
But to apply a security release, when you are on a maintained minor release (3.0, 3.1 or 3.2)? If you understand how bundler works, you are HIGHLY unlikely to have any troubles.
- steveklabnik 14y ago> But to apply a security release, when you are on a maintained minor release (3.0, 3.1 or 3.2)? If you understand how bundler works, you are HIGHLY unlikely to have any troubles. Right, but it DID happen. Updating the Rails version updated the versions of other gems too. I know what you're saying, but the reality was different.