[Ironruby-core] Heads Up: RubyGems.org and universal-dotnet

Just a heads up: If you do manage to upgrade your Ruby Gems version to 1.3.7 (as I demonstrate here: http://hotgazpacho.org/2010/05/ironruby-gem-update-system/), you will not be able to install gems that have a platform of universal-dotnet. It appears that this is because: 1. RubyGems 1.3.7 inc

Re: [Ironruby-core] What's next?

In terms of MRI compatibility, I'd suggest that 1.9.2 would be a good target. 1.9.1 has various issues and has been largely ignored in favour of 1.8.7, but I'm seeing a lot of people recommending 1.9.2 even in its current pre state. Beyond compatibility, I think VS integration would be sweet, and

Re: [Ironruby-core] Heads Up: RubyGems.org and universal-dotnet

That's pretty bad! So basically all IronRuby gems won't be installable on RubyGems 1.3.7. Sounds like this will be fixed when RubyGems.org updates to it? In the meantime is there a downside to suggesting no one upgrade until RubyGems.org does? ~Jimmy

Re: [Ironruby-core] Heads Up: RubyGems.org and universal-dotnet

On May 25, 2010, at 11:08 AM, "Jimmy Schementi" mailto:jimmy.scheme...@microsoft.com>> wrote: That's pretty bad! So basically all IronRuby gems won't be installable on RubyGems 1.3.7. Correction ... IronRuby gems won't be installable if you upgrade to RubyGems 1.3.7 before RubyGems.org

Re: [Ironruby-core] Heads Up: RubyGems.org and universal-dotnet

That is the way I understand it, yes. I may be wrong, but this is the conclusion I came to poking around a bit in RubyGems last night. In the mean time, putting this file: http://github.com/hotgazpacho/ironruby/blob/gem-update-fix/Merlin/External.LCA_RESTRICTED/Languages/Ruby/redist-libs/ruby/site

[Ironruby-core] Class System::Int64 does not have a valid constructor

http://www.ruby-forum.com/topic/206766 Someone posted about this error back in March, but I didn't see any resolution posted. Any one discovered a workaround or fix for the issue described in the original post? -- "The explanation requiring the fewest assumptions is most likely to be correct."

Re: [Ironruby-core] Git push

What do I need to do to get my etc updates ready? http://github.com/panesofglass/ironruby/blob/master/Merlin/Main/Languages/Ruby/Libs/etc.rb http://github.com/panesofglass/ironruby/tree/master/Merlin/Exter

Re: [Ironruby-core] What's next?

+1 except for targeting 1.8.7. The Ruby community as a whole is really pushing to get off of 1.8, so the faster IronRuby gets there, the better. Ryan On Wed, May 12, 2010 at 9:14 AM, Will Green wrote: > Vim ;-) > > While it would be nice to have something like the IronPython Tools for > Visual

Re: [Ironruby-core] What's next?

>From the peanut gallery: the lack of VS integration has definitely held me >back from trying to push IronRuby in any capacity at work - I've been happy >using Ruby without an IDE, but I am fairly certain that my colleagues would >politely and firmly decline any suggestion of switching to text e

Re: [Ironruby-core] Git push

I'll pull them in as is. From: Ryan Riley Sent: Tuesday, May 25, 2010 12:09 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] Git push What do I need to do to get my etc updates ready? http://github.com/panesofglass/ironruby/blob/master/Merlin/M