Stopping generating gemspec file.

[junaruga]

This fixes #169

Summary

• I stopped generating gemspec file from Thorfile.
  That confusing us including contributors.
  There is a way to manage gemspec file statically.
  Ref:

  • Listen: https://github.com/guard/listen/blob/master/listen.gemspec
  • RSpec-Core: https://github.com/rspec/rspec-core/blob/master/rspec-core.gemspec
  • Rack: https://github.com/rack/rack/blob/master/rack.gemspec

• I created new file lib/rack/test/version.rb newly to manage version string.
  Because when I tried to load require "rack/test" in the gemspec file , then bundle install, that causes install error. When I searched internet (Issue with administrate-field-image thoughtbot/administrate#717), it is related that rack/test is recursively loaded. So, I referred above Listen's way.

• I added Release way to README again because that is useful for people who do release.
  You can check modified README here: https://github.com/junaruga/rack-test/blob/feature/stop-generating-gemspec/README.md

• I added release test to `.travis.yml. This is because I wanted to test gemspec file and release script.

Detail

• rack-test.gemspec
  • Replacing from double quote " to single quote ' is to pass rubocop latest version 0.49.0 test. There is one violation error for the rubocop test for here document. But can not avoid it.
  • s.files: I only included files under lib and some document files.
    This way removing test files is maybe new popular. For example you can see it on rails/rails, rspec/rspec-*, the merit is we can reduce the file size of gem.
  • s.required_rubygems_version: Removed. Removing it looks no harmful, referring other packages' gemspec files. The item looks auto-generated by RubyGems. See the result of gem specification on Travis CI.
  • s.extra_rdoc_files: Removed. It looks no harmful.
  • s.rubyforge_project: Removed. Outdated? We don't use Rubyforge.
  • s.rubygems_version: Removed. We don't want to maintain the version.
    I did not see this item at rais/rails, rspec-core.
    http://guides.rubygems.org/specification-reference/#rubygems_version

    Do not set this, it is set automatically when the gem is packaged.

  • s.test_files: Removed. Seeing http://guides.rubygems.org/specification-reference, it look outdated tag. Also I did not see it on rails.
  • s.add_dependency or s.add_runtime_dependency ?
    Both are same meaning items. But maybe add_runtime_dependency is newer than add_dependency. Seeing rails/rails add_dependency is used. So, I used it for the compativility of older Rubies.

I also removed/updated those items referring http://guides.rubygems.org/specification-reference/ , rails/rails and rspec/rspec-core. So, if you have questions, please let me know.

• .travis.yml

  • The release test is too much? :)

• Thorfile

  • My concern is $ bundle exec thor :install itself is not useful. Because gem install --local pkg/rack-test-*.gem is run in the Bundler world.

$ bundle show rack-test
/home/jaruga/git/rack-test

$ bundle exec thor :build
gem build rack-test.gemspec
  Successfully built RubyGem
  Name: rack-test
  Version: 0.6.3
  File: rack-test-0.6.3.gem

$ bundle exec thor :install

$ bundle show rack-test
/home/jaruga/git/rack-test

How to test

$ bundle exec thor :build

$ gem install --user-install pkg/rack-test-0.6.3.gem

$ gem list | grep rack-test
rack-test (0.6.3)

irb(main):003:0> require 'rack/test'
=> true

$ gem specification pkg/rack-test-0.6.3.gem --ruby

$ cd pkg/

$ gem unpack rack-test-0.6.3.gem 
Unpacked gem: '/home/jaruga/git/rack-test/pkg/rack-test-0.6.3'

$ ls rack-test-0.6.3
History.md  lib/  MIT-LICENSE.txt  README.md

[perlun]

Looks good to me. Thanks @junaruga!

[junaruga]

@perlun thanks for checking my code!