Heads Up: RubyGems.org and universal-dotnet

Ruby IronRuby
1

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/), 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 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.

2

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.orghttp://RubyGems.org updates to it? In the meantime is
there a downside to suggesting no one upgrade until
RubyGems.orghttp://RubyGems.org does?

~Jimmy

On May 25, 2010, at 3:06 AM, “Will G.”
<[email protected]mailto:[email protected]> 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.orghttp://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 G.
http://hotgazpacho.org/http://hotgazpacho.org/

Ironruby-core mailing list
[email protected]mailto:[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core

3

On May 25, 2010, at 11:08 AM, “Jimmy S.”
<[email protected]mailto:[email protected]>
wrote:

That’s pretty bad! So basically all IronRuby gems won’t be installable
on RubyGems 1.3.7.

Correction … IronRuby gems won’t be installable if you upgrade to
RubyGems 1.3.7 before RubyGems.orghttp://RubyGems.org upgrades, right?

Sounds like this will be fixed when http://RubyGems.org
RubyGems.orghttp://RubyGems.org updates to it? In the meantime is
there a downside to suggesting no one upgrade until
http://RubyGems.org RubyGems.orghttp://RubyGems.org does?

~Jimmy

On May 25, 2010, at 3:06 AM, “Will G.”
<mailto:[email protected][email protected]mailto:[email protected]>
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/
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. http://RubyGems.org RubyGems.orghttp://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 G.
http://hotgazpacho.org/http://hotgazpacho.org/http://hotgazpacho.org/

Ironruby-core mailing list
mailto:[email protected][email protected]mailto:[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-corehttp://rubyforge.org/mailman/listinfo/ironruby-core

Ironruby-core mailing list
[email protected]mailto:[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core

4

That is the way I understand it, yes. I may be wrong, but this is
the conclusion I came to poking around a bit in RubyGems last night.

In the mean time, putting this file:
http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA_RESTRICTED/Languages/Ruby/redist-libs/ruby/site_ruby/1.8/rubygems/defaults/ironruby.rb

http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA_RESTRICTED/Languages/Ruby/redist-libs/ruby/site_ruby/1.8/rubygems/defaults/ironruby.rbin
IronRuby\lib\ruby\site_ruby\1.8\rubygems\defaults directory will allow
you
to install gems whose platform is not marshaled correctly.

–
Will G.
http://hotgazpacho.org/

On Tue, May 25, 2010 at 11:09 AM, Jimmy S. <