structure.gemspec in structure-0.1.0 vs structure.gemspec in structure-0.2.0

- old
+ new

@@ -1,16 +1,31 @@ # -*- encoding: utf-8 -*- +$:.push File.expand_path('../lib', __FILE__) +require 'structure/version' + Gem::Specification.new do |s| s.name = "structure" - s.version = "0.1.0" + s.version = Sucker::VERSION s.platform = Gem::Platform::RUBY s.authors = ["Paper Cavalier"] s.email = ["code@papercavalier.com"] - s.homepage = "" - s.summary = %q{Structure is a nested OpenStruct implementation.} - s.description = %q{A nested OpenStruct implementation} + s.homepage = "http://rubygems.com/gems/structure" + s.summary = "Structure is a better Struct." + s.description = <<-END_OF_DESCRIPTION.strip + Structure is a better Struct. + Like Struct, it is great for setting up ephemeral models. It also handles + typecasting and, unlike Struct, dumps nicely-formatted JSON. + END_OF_DESCRIPTION + s.rubyforge_project = "structure" + + { + 'rspec' => '~> 2.6.0', + 'ruby-debug19' => '~> 0.11.6' + }.each do |lib, version| + s.add_development_dependency lib, version + end s.files = `git ls-files`.split("\n") s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n") s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) } s.require_paths = ["lib"]