I'm looking to ensure that rubinius and jruby are supported as first-class
members in our test suite; I haven't gotten a response either way that's
definitive. Is this an ok endeavor? It seems like it would be a healthy
patchset so I'd like to ask first.
Also, some notes on the suite as it stands in rubinius, pasted from IRC:
13:28:21 erikh | hrm... there has to be an implicit to_sym happening in
rubinius' run of the test
| suite
13:28:54 erikh | the codebase only has like ... 5 to_sym calls, and things
breaks before the test
| suite is even able to run... it's trying to coerce the
.gemspec files.
13:29:06 erikh | I can't seem to find where that should be happening.
13:29:44 erikh | anyhow, adding a def to_sym; @path.to_sym; end to Gem::Path
gets the test suite
| limping along, but there are a lot of SSL and Fetcher related
errors (very similar
| to the ones seen when running against JRuby)
Any kind of feedback on this would be great. Thanks!
-Erik
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
