jejacks0n/mercury — pull request #166 by mixonic (2012-03-01 04:21:27+00:00)
Title: Drop Gemfile.lock

This commit removes Gemfile.lock. Why?

It is considered best practice not to commit a Gemfile.lock for a Gem, but to commit it for a Rails app. I know Mercury is kind of both.

http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/

Regardless, without removing the Gemfile.lock from the repo, Mercury cannot be developed on Ruby 1.9.3 (which requires linecache19 0.5.13 and ruby-debug-base19 0.11.26) and on Ruby 1.9.x (which only provides linecache19 0.5.12 and ruby-debug-base19 0.11.25). It is my opinion that using a Gemfile.lock leads to a false sense of shared-library-versions in the real world as well- when deving again the test Rails all everybody has the same library versions, but in real world use the library versions are only decided by the requirements in the gemspec.

So, I think we should be leaning on the gemspec for minimum version requirements where required, and not committing Gemfile.lock.