On Oct 1, 2007, at 17:11 , Luis Lavena wrote: > On 10/1/07, Luis Lavena <[EMAIL PROTECTED]> wrote: >> On 10/1/07, Luis Lavena <[EMAIL PROTECTED]> wrote: >>> >>> I'm working on a up-to-date patch for this. >>> >> >> As we talk on #irc, this is the patch for this. >> >> I don't like the #self.local stuff... but with inline condition >> ( a == >> b ? true : false ) looks worse. >> > > Forgot to mention: > > Gem that match new Gem::Platform.local will be 'x86-mswin32-60'... > > Current available gems will be compatible with that platform. > > Future gems using that local will not be compatible when > Gem::Platform.local match 'x86-mswin32-80' (due version mismatch?) > > Guess that cover all the cases, except for old gems that lack the new > Gem::Platform specification (odd cases as you said). > > Regards and hope this helps.
Yes, I think this the best we can do. I have set the new constant Gem::Platform::MSWIN32 to match VC6 also, so maybe this will help. Hopefully people will use CURRENT instead. Thanks for your help and time! -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
