Yup, that's the fix! The process outlined here: http://wiki.github.com/ironruby/ironruby/contributing is still valid, yes?
-- Will Green http://hotgazpacho.org/ On Tue, May 18, 2010 at 2:08 PM, Jimmy Schementi < jimmy.scheme...@microsoft.com> wrote: > You're talking about rubygems/defaults/ironruby.rb? The normal contribution > process would do just fine; the version of rubygems we redist is in > external.lca_restricted/languages/ruby/redist-libs. > > ~Jimmy > > On May 18, 2010, at 10:14 AM, "Will Green" <w...@hotgazpacho.org> wrote: > > I've got a fix that will allow IronRuby to update RubyGems. It's a > refinement of the technique here: > <http://marcinobel.com/index.php/bug-invalid-exec_format-ir/comment-page-1/#comment-428> > http://marcinobel.com/index.php/bug-invalid-exec_format-ir/comment-page-1/#comment-428 > > Judging by the source of RubyGems, and the RubyGems source distributed with > JRuby, this is an override within RubyGems that is provided by the Ruby > implementation. > > What do I need to do to get this into the Ruby Gems source that is > distributed with IronRuby? > > -- > Will Green > <http://hotgazpacho.org/>http://hotgazpacho.org/ > > _______________________________________________ > > Ironruby-core mailing list > 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 > >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
