Skip to content
Browse files

Remove Gemfile.lock.

This file should not be checked into version control when developing
gems, because it imposes very specific dependencies on app authors
attempting to use it.

See: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
  • Loading branch information...
1 parent 97a72ca commit c6b626429cdb67a9cc589b43085b9584b9c1b5cc @adammck adammck committed May 8, 2012
Showing with 3 additions and 47 deletions.
  1. +2 −0 .gitignore
  2. +0 −45 Gemfile.lock
  3. +1 −2 health_graph.gemspec
View
2 .gitignore
@@ -1,3 +1,5 @@
+Gemfile.lock
+
# rcov generated
coverage
View
45 Gemfile.lock
@@ -1,45 +0,0 @@
-GEM
- remote: http://rubygems.org/
- specs:
- addressable (2.2.6)
- crack (0.3.1)
- faraday (0.7.4)
- addressable (~> 2.2.6)
- multipart-post (~> 1.1.0)
- rack (>= 1.1.0, < 2)
- faraday_middleware (0.7.0)
- faraday (~> 0.7.3)
- git (1.2.5)
- hashie (1.2.0)
- jeweler (1.6.4)
- bundler (~> 1.0)
- git (>= 1.2.5)
- rake
- json (1.6.5)
- multi_json (1.0.4)
- multipart-post (1.1.3)
- oauth2 (0.5.2)
- faraday (~> 0.7)
- multi_json (~> 1.0)
- rack (1.3.4)
- rake (0.9.2)
- rcov (0.9.10)
- shoulda (2.11.3)
- webmock (1.7.4)
- addressable (~> 2.2, > 2.2.5)
- crack (>= 0.1.7)
-
-PLATFORMS
- ruby
-
-DEPENDENCIES
- bundler (~> 1.0.0)
- faraday (= 0.7.4)
- faraday_middleware (= 0.7.0)
- hashie (= 1.2)
- jeweler (~> 1.6.4)
- json
- oauth2 (= 0.5.2)
- rcov
- shoulda
- webmock (= 1.7.4)
View
3 health_graph.gemspec
@@ -9,7 +9,7 @@ Gem::Specification.new do |s|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Kenny Ma"]
- s.date = "2012-03-11"
+ s.date = "2012-05-08"
s.description = "This is a wrapper for RunKeeper Health Graph RESTful API."
s.email = "kenny@kennyma.me"
s.extra_rdoc_files = [
@@ -19,7 +19,6 @@ Gem::Specification.new do |s|
s.files = [
".document",
"Gemfile",
- "Gemfile.lock",
"LICENSE.txt",
"README.rdoc",
"Rakefile",

0 comments on commit c6b6264

Please sign in to comment.
Something went wrong with that request. Please try again.