sys-cpu.gemspec in sys-cpu-0.7.1 vs sys-cpu.gemspec in sys-cpu-0.7.2

@@ -1,25 +1,27 @@
 require 'rubygems'
 
 Gem::Specification.new do |spec|
-  spec.name      = 'sys-cpu'
-  spec.version   = '0.7.1'
-  spec.author    = 'Daniel J. Berger'
-  spec.email     = 'djberg96 at nospam at gmail dot com'
-  spec.homepage  = 'https://github.com/djberg96/sys-cpu'
-  spec.summary   = 'A Ruby interface for providing CPU information'
-  spec.test_file = 'test/test_sys_cpu.rb'
-  spec.files     = Dir['**/*'].reject{ |f| f.include?('git') }
+  spec.name       = 'sys-cpu'
+  spec.version    = '0.7.2'
+  spec.author     = 'Daniel J. Berger'
+  spec.email      = 'djberg96 at nospam at gmail dot com'
+  spec.license    = 'Artistic 2.0'
+  spec.homepage   = 'https://github.com/djberg96/sys-cpu'
+  spec.summary    = 'A Ruby interface for providing CPU information'
+  spec.test_file  = 'test/test_sys_cpu.rb'
+  spec.files      = Dir['**/*'].reject{ |f| f.include?('git') }
+  spec.cert_chain = ['certs/djberg96_pub.pem']
 
-  spec.rubyforge_project = 'sysutils'
   spec.extra_rdoc_files  = ['CHANGES', 'README', 'MANIFEST']
 
   # The ffi dependency is only relevent for the Unix version. Given the
   # ubiquity of ffi these days, I felt a bogus dependency on ffi for Windows
-  # and Linux was worth the tradeoff of having to create 3 separate gems.
-  spec.add_dependency('ffi', '>= 1.0.0')
+  # and Linux was worth the tradeoff of not having to create 3 separate gems.
+  spec.add_dependency('ffi')
 
-  spec.add_development_dependency('test-unit', '>= 2.4.0')
+  spec.add_development_dependency('test-unit')
+  spec.add_development_dependency('rake')
 
   spec.description = <<-EOF
     The sys-cpu library provides an interface for gathering information
     about your system's processor(s). Information includes speed, type,
     and load average.