Permalink
Browse files

removed gemfile.lock

  • Loading branch information...
1 parent e02c33a commit 04cc914060a0425b25de3d4e14ef3431fdad622f @scottdavis committed Dec 15, 2011
Showing with 0 additions and 21 deletions.
  1. +0 −21 Gemfile.lock
View
@@ -1,21 +0,0 @@
-PATH
- remote: .
- specs:
- tesseract (0.0.1)
-
-GEM
- remote: http://rubygems.org/
- specs:
- mocha (0.9.12)
- rake (0.8.7)
- shoulda (2.11.3)
-
-PLATFORMS
- ruby
-
-DEPENDENCIES
- bundler (>= 1.0.0)
- mocha (~> 0.9.12)
- rake (~> 0.8.7)
- shoulda (~> 2.11.3)
- tesseract!

3 comments on commit 04cc914

Contributor

lawrencewoodman commented on 04cc914 Dec 16, 2011

Why would you want to remove the Gemfile.lock? It would be good if anyone who wanted to contribute, could use bundler to ensure the same dependency version numbers.

Owner

scottdavis replied Dec 16, 2011

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

When developing a gem, use the gemspec method in your Gemfile to avoid duplication. In general, a gem’s Gemfile
 should contain the Rubygems source and a single gemspec line. Do not check your Gemfile.lock into version control, 
since it enforces precision that does not exist in the gem command
Contributor

lawrencewoodman replied Dec 17, 2011

Thanks for the link. I hadn't thought about the problem of creating false test environments. Now I need to reassess some of my gems. Keep up the good work!

Please sign in to comment.