CODEWITHSUNDEEP
ruby-on-railsruby-on-rails-3rubygemsgemfile
Crashalot
Crashalot

Reputation: 34513

Understanding Gemfile.lock: Is it okay to delete Gemfile.lock then run bundle install again?

We would test this, but don't want to risk ruining our dev environment if this isn't supposed to happen.

Is it okay to delete Gemfile.lock?

We're on Rails 3.0.6.

Upvotes: 39

Views: 30822

Answers (4)

Hywel Griffiths
Hywel Griffiths

Reputation: 368

I've recently worked with this and there is a significant issue when deleting the gemfile.lock. If it is being generated in a separate remote environment, it could be created with separate platforms. Deleting the gemfile.lock locally would cause it to generate with the local platforms, that may be absent from the remote environment. This will cause it to fail in the remote environment.

Upvotes: 0

mpalencia
mpalencia

Reputation: 6007

It's ok to delete Gemfile.lock, just run 

bundle install

to generate a new Gemfile.lock. Take note that if you didn't specify any version of a gem on your Gemfile, you will always get the latest

Upvotes: 10

AnthonyAlmighty
AnthonyAlmighty

Reputation: 135

I know this has been answered already, but for everyone else that happens to come across this post on Google, you should know that command bundle init will regenerate the Gemfile.

Upvotes: 4

jdl
jdl

Reputation: 17790

You're probably not going to ruin your dev environment. However, you might end up with newer versions of gems than you had before. It depends on how you have defined them in Gemfile.

If you're using entries like:

gem "rails"

Then you'll get the latest rails gem, whatever that might be.

If you're using entries like:

gem "rails", "3.2.11"

Then you'll get 3.2.11 again.

Having said all of that, this is what branches are for. Make a branch in git, hg, or whatever you're using, blow away Gemfile.lock, run bundle install, and then check your test suite. If it's horrible, then you can abandon the branch while you figure out what went wrong.

Another tip: Any time I've ever wanted to do this, I found that it was useful to clear out all of my installed gems as well. If you're using rvm with gemsets this is as simple as running

rvm gemset empty [gemset_name]

Upvotes: 39

Related Questions