That's pretty bad! So basically all IronRuby gems won't be installable on RubyGems 1.3.7. Sounds like this will be fixed when RubyGems.org<http://RubyGems.org> updates to it? In the meantime is there a downside to suggesting no one upgrade until RubyGems.org<http://RubyGems.org> does?
~Jimmy On May 25, 2010, at 3:06 AM, "Will Green" <w...@hotgazpacho.org<mailto:w...@hotgazpacho.org>> wrote: Just a heads up: If you do manage to upgrade your Ruby Gems version to 1.3.7 (as I demonstrate here: <http://hotgazpacho.org/2010/05/ironruby-gem-update-system/> http://hotgazpacho.org/2010/05/ironruby-gem-update-system/), you will not be able to install gems that have a platform of universal-dotnet. It appears that this is because: 1. RubyGems 1.3.7 includes my patch for IronRuby platform (universal-dotnet) 2. RubyGems.org<http://RubyGems.org> have not updated to 1.3.7, and appear to be marshaling the platform over the wire as universal-unknown (and of course, universal-dotnet != universal-unknown) If you want to use bundler, however, you can upgrade to 1.3.6, as both ends treat universal-dotnet as universal-unknown. -- Will Green <http://hotgazpacho.org/>http://hotgazpacho.org/ _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org<mailto:Ironruby-core@rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
