Menu
I'm working with a distributed team of developers and I'm getting this issue of having to commit the Gemfile.lock with bundled with info added to the bottom:
BUNDLED WITH
1.10.2
We're obviously using different versions of things, ie rvm/rbenv, and I'm wondering if there's a way to stop my system doing this.
Bundler version 1.10.2 (obviously)
539
Gemfile. lock is automatically generated when you run bundle install or bundle update . It should never be edited manually.
The Gemfile is where you specify which gems you want to use, and lets you specify which versions. The Gemfile. lock file is where Bundler records the exact versions that were installed. This way, when the same library/project is loaded on another machine, running bundle install will look at the Gemfile.
The Gemfile. lock allows you to specify the versions of the dependencies that your application needs in the Gemfile , while remembering all of the exact versions of third-party code that your application used when it last worked correctly. By specifying looser dependencies in your Gemfile (such as nokogiri ~> 1.4.
You should always include your Gemfile. lock if you are writing an application. The community seems to (largely) agree that you should include it in any Gems you create as well.
After digging around a bit, and looking through those issues and comments shared by Jorge, you really only have two options:
Ask your whole team to update their versions of bundler to something later than 1.10
gem uninstall bundler
gem install bundler -v 1.9.9
But as long as the downgrade doesn't cause any issues, it should be fine.
The developers for the bundler gem are not going to make any changes to the gem that will eliminate this problem. They're reasoning is that eventually everyone will be upgraded to something after 1.10.
126
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
