This has been generating lot of issues for several folks, including the ones using Jruby, not only Windows.
Description: An existing version of a gem (1.1.0) was installed on the system. The gem was a platform specific one. The developer releases a new version of his gem (1.2.0), doing the pure ruby one. Users doing "gem update" will have issues when RubyGems tries to install version 1.2.0 and bomb out due: platform lack of support for native gems (jruby) lack of development tool chain (windows). All these issues has been lately showing up in different places, including stack overflow, ruby-talk, merb and datamapper mailing list. Charles Oliver Nutter suggested (dunno if was ruby-talk or here) we should alter the platform preference order and give more weight/priority to local platform than ruby one. For References: http://stackoverflow.com/questions/43778/sqlite3-ruby-gem-failed-to-build-gem-native-extension http://stackoverflow.com/questions/134581/gem-update-on-windows-is-it-broken The idea will be: "gem update" will only install the latest version of gem to the latest one with current-platform. Also, this can be overwritten if specific version is indicated, like the new prerelease functionality. Thoughts? -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
