Jim Weirich wrote: > * Specification comparison errors. > > This is an issue that is really impacting the JRuby team. It seems that > Gem::Specification equals operator is poorly written in that it blows up > if compared to a non-specification object. I don't think the RubyGems > code ever explicity does this, but the JRuby folk think that it might be > related to Marsh activity (we do store our cache in marshal format). > Also, if the == operator is defined, a compatible hash should be defined > as well. I have fixed the Specification, Version and Requirements > classes, and have updated the unit tests to cover those issue. > > You can update to this beta version with: > > sudo gem update --system --source http://onestepback.org/betagems > > The second issue is rather hot for the JRuby team and I would like to > make a new minor release soon. I know there are several patches I > haven't gotten around to yet, but if there are other hot issues for > RubyGems that should be addressed, give a hollar now. > > Thanks. > > -- Jim Weirich >
Yay! Thank you, Jim! (Btw, have you been thinking about that YAML validation problem?) -- Ola Bini (http://ola-bini.blogspot.com) JvYAML, RbYAML, JRuby and Jatha contributor System Developer, Karolinska Institutet (http://www.ki.se) OLogix Consulting (http://www.ologix.com) "Yields falsehood when quined" yields falsehood when quined. _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
