On Mon, Mar 31, 2008 at 4:11 AM, Chad Woolley <[EMAIL PROTECTED]> wrote: > On Sun, Mar 30, 2008 at 9:11 AM, Luis Lavena <[EMAIL PROTECTED]> wrote: > > I recommend you switch to Gem::Platform::CURRENT, since mswin32 is > deprecated. > ... > > Trying to install it with 0.9.4 also fails and rollback to RUBY > > version, and not the pre-compiled one. > > Why should we need to issue this warning manually? >
This warns the user during gem building > Are some legacy gems not downloadable with the latest version of RubyGems? > No, all old and legacy gems are supported, only new gems should use Gem::Platform::CURRENT > Does RubyGems issue a warning whenever a gem with a deprecated spec is > downloaded? If not, should it? > No, it install just fine. > Is it wrong to break install support for legacy gems in newer RubyGems > versions? yes, it is very wrong... see what happened between 0.9.4 and 0.9.5, I blogged about it: http://blog.mmediasys.com/2007/12/19/latest-rubygems-and-rails-is-a-deadly-combo/ -- Luis Lavena Multimedia systems - 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 [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
