use separate gemspec for windows

- allows us to explicitly version pin in the gemspec on gem installs
  rather than getting different behavior from 'gem install' and
  'bundle install' (gemspec vs. Gemfile).
- the mingw deps had been in the Gemfile because it needed to be a
  group since gemspecs do not have groups.  this builds two different
  gems for publication to rubygems instead.
- see mixlib-shellout for the prototype of where this has been done
  (successfully).

1 files changed, 1 insertions, 20 deletions

diff --git a/Gemfile b/Gemfile
index 21f7744ba6..1fe4580c0b 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,6 +1,5 @@
 source "https://rubygems.org"
-
-gemspec
+gemspec :name => "chef"
 
 gem "activesupport", "< 4.0.0", :group => :compat_testing, :platform => "ruby"
 
@@ -18,24 +17,6 @@ group(:development, :test) do
 #  gem 'pry'
 end
 
-platforms :mswin, :mingw do
-  gem "systemu", "2.2.0"  # CHEF-3718
-  gem "ffi", "1.3.1"
-  gem "rdp-ruby-wmi", "0.3.1"
-  gem "windows-api", "0.4.2"
-  gem "windows-pr", "1.2.2"
-  gem "win32-api", "1.4.8"
-  gem "win32-dir", "0.4.1"
-  gem "win32-event", "0.6.0"
-  gem "win32-mutex", "0.4.0"
-  gem "win32-process", "0.7.3"
-  gem "win32-service", "0.7.2"
-end
-
-platforms :mingw_18 do
-  gem "win32-open3", "0.3.2"
-end
-
 # If you want to load debugging tools into the bundle exec sandbox,
 # add these additional dependencies into chef/Gemfile.local
 eval(IO.read(__FILE__ + '.local'), binding) if File.exists?(__FILE__ + '.local')