nicer gemspec + install tasks

Author: grosser

Gemfile

@@ -1,4 +1,4 @@
-source "http://rubygems.org"
+source "https://rubygems.org"
 
 gemspec
 gem 'debugger'

Gemfile.lock

@@ -5,7 +5,7 @@ PATH
       grit
 
 GEM
-  remote: http://rubygems.org/
+  remote: https://rubygems.org/
   specs:
     bump (0.4.2)
     columnize (0.3.6)

MIT-LICENSE.txt

@@ -0,0 +1,20 @@
+Copyright (C) 2013 Ben Osheroff <ben@zendesk.com>
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -2,12 +2,12 @@
 
 This is git-spelunk, an interactive tool for exploring blame history.
 
-## Huh? 
+## Huh?
 
-`git blame` is a great tool for determining code responsibility.  But sometimes when you 
-fire up git-blame, you'll find yourself in a loop of `git-blame`, `git-show`, and then 
+`git blame` is a great tool for determining code responsibility.  But sometimes when you
+fire up git-blame, you'll find yourself in a loop of `git-blame`, `git-show`, and then
 `git-blame` again in order to find the true owner of a line of code.
-`git-spelunk` is the tool for situations like this, when you want to 
+`git-spelunk` is the tool for situations like this, when you want to
 skip past syntactic and refactoring commits to find the true owner of a line, or see how
 a piece of source code has evolved over time.
 
@@ -22,15 +22,16 @@ git spelunk lib/git_spelunk/offset.rb
 ![git spelunk, main page](images/screenshot_1.png)
 
 You can see we've highlighted line 45.  `git-spelunk` here is telling us that this line was introduced
-in commit 33465d2.  You can also see that all other lines that were involved in 33465d2 are picked out 
+in commit 33465d2.  You can also see that all other lines that were involved in 33465d2 are picked out
 in green.  The output of `git show` is present as well for adding more context to the information.
 
-Now we press '['.  What we're asking here is "show me the file just before 33465d2" was introduced, 
+Now we press '['.  What we're asking here is "show me the file just before 33465d2" was introduced,
 essentially replacing the content of the current screen with `git blame [file] 33465d2~1`.
 
 ![git spelunk, back one](images/screenshot_2.png)
 
-There's other stuff to do; you can hit "s" to do a `git show` of the commit underneath the cursor, you 
+There's other stuff to do; you can hit "s" to do a `git show` of the commit underneath the cursor, you
 can search and page through the file like you would with "less".
 
-
+# License
+MIT

Rakefile

@@ -1 +1,3 @@
+require 'bundler/setup'
+require 'bundler/gem_tasks'
 require 'bump/tasks'

git_spelunk.gemspec

@@ -1,18 +1,13 @@
-Gem::Specification.new do |s|
-  s.name        = "git_spelunk"
-  s.version     = "0.2.2"
-  s.platform    = Gem::Platform::RUBY
+Gem::Specification.new "git_spelunk", "0.2.2" do |s|
   s.authors     = ["Ben Osheroff", "Saroj Yadav"]
   s.email       = ["ben@zendesk.com", "saroj@zendesk.com"]
   s.homepage    = "https://github.com/osheroff/git-spelunk"
   s.summary     = "A git tool for exploring history and blame"
   s.description = "git-spelunk is a terminal based exploration tool for git blame and history, based on the notion of moving in history based on file context"
 
-  s.required_rubygems_version = ">= 1.3.6"
-
   s.add_runtime_dependency("grit")
 
-  s.files        = Dir.glob("lib/**/*")
+  s.files = `git ls-files lib bin MIT-LICENSE.txt`.split("\n")
+  s.license = "MIT"
   s.executables  << "git-spelunk"
-  s.require_path = 'lib'
 end