Re: [Ironruby-core] IronRuby version of existing gems

2010-03-19 Thread Shri Borde
Thanks a lot for pushing on this! From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Friday, March 19, 2010 3:45 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems FYI, my patch

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-12 Thread Shri Borde
Sounds great. Thanks for pushing on this! From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Thursday, March 11, 2010 7:19 PM To: ironruby-core Subject: Re: [Ironruby-core] IronRuby version of existing gems Updated my patch

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Shri Borde
: Re: [Ironruby-core] IronRuby version of existing gems Attached is a new patch I would propose to address the feedback from the Ruby Gems team. I would love some feedback on it. It is a patch against rev 2463 of trunk of Ruby Gems source. -- Will Green http://hotgazpacho.org/ On Wed, Mar 10

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Will Green
-universal-dotnet. *From:* ironruby-core-boun...@rubyforge.org [mailto: ironruby-core-boun...@rubyforge.org] *On Behalf Of *Will Green *Sent:* Wednesday, March 10, 2010 8:57 PM *To:* ironruby-core *Subject:* Re: [Ironruby-core] IronRuby version of existing gems Attached is a new patch I

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Ivan Porto Carrero
To: ironruby-core@rubyforge.orgironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems ___ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Tomas Matousek
Wouldn’t “clr” be better after all? Tomas From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Thursday, March 11, 2010 8:47 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Jim Deville
] IronRuby version of existing gems Wouldn’t “clr” be better after all? Tomas From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Thursday, March 11, 2010 8:47 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Shri Borde
-dotnet4.0” From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Tomas Matousek Sent: Thursday, March 11, 2010 9:11 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems Wouldn’t “clr” be better after all

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Will Green
than just gemname-universal-dotnet. From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Wednesday, March 10, 2010 8:57 PM To: ironruby-core Subject: Re: [Ironruby-core] IronRuby version of existing gems Attached is a new patch I

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Orion Edwards
The name is spelled as “.NET”, and so gemname-universal-dotNET would read better than just gemname-universal-dotnet. dotNET looks awful. Microsoft are well known for terrible marketing and terrible naming, so I'd argue that use the correct spelling is an anti-feature :-) Personally, I like

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Ivan Porto Carrero
I don't care either way as long as it's lower-case On Thursday, March 11, 2010, Orion Edwards orion.edwa...@gmail.com wrote: The name is spelled as “.NET”, and so gemname-universal-dotNET would read better than just gemname-universal-dotnet. dotNET looks awful. Microsoft are well known for

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-11 Thread Will Green
Updated my patch to Ruby Gems to match on universal-dotnetX.X, where X.X is the version number. This will allow for the creation of .NET-specific gems with names like: - gemname-dotnet - gemname-dotnet-2.0 - gemname-dotnet-4.0 - gemname-universal-dotnet - gemname-universal-dotnet-2.0 -

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-10 Thread Will Green
...@rubyforge.org] *On Behalf Of *Shri Borde *Sent:* Sunday, March 07, 2010 6:53 PM *To:* ironruby-core@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems Will, could you recreate the universal-.net gem again and push it? I think it might have been created incorrectly

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-10 Thread Will Green
: ironruby-core-boun...@rubyforge.org] *On Behalf Of *Shri Borde *Sent:* Sunday, March 07, 2010 6:53 PM *To:* ironruby-core@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems Will, could you recreate the universal-.net gem again and push it? I think it might have

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-07 Thread Daniele Alessandri
On Sun, Mar 7, 2010 at 08:07, Will Green w...@hotgazpacho.org wrote: I would appreciate if someone running the latest from git would try ir -S gem install iron-term-ansicolor on both the .Net 2 and the .Net 4 runtimes, and let me know which gem gets installed.

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-07 Thread Will Green
Thanks, Daniele! I've got three version of iron-term-ansicolor out there on RubyGems.org: - iron-term-ansicolor-0.0.3 (gemspec.platform=ruby) - iron-term-ansicolor-0.0.3-universal-.net (gemspec.platform=universal-.net) -

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-07 Thread Shri Borde
-core Subject: Re: [Ironruby-core] IronRuby version of existing gems Thanks, Daniele! I've got three version of iron-term-ansicolor out there on RubyGems.org: * iron-term-ansicolor-0.0.3 (gemspec.platform=ruby) * iron-term-ansicolor-0.0.3-universal-.net

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-07 Thread Shri Borde
: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde Sent: Sunday, March 07, 2010 2:27 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems My guess is that RubyGems tries to look for an exact platform

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-07 Thread Jim Deville
...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde Sent: Sunday, March 07, 2010 6:53 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems Will, could you recreate the universal-.net gem again and push it? I think it might have

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Will Green
@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. -- Will Green http://hotgazpacho.org

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Shri Borde
...@rubyforge.org] On Behalf Of Will Green Sent: Friday, March 05, 2010 7:08 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems Cool beans! I noticed in the latest push that a change was made to Ruby Gems itself: http://github.com/ironruby/ironruby/commit

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Will Green
*To:* ironruby-core@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. -- Will Green

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Shri Borde
as a courtesy heads-up… From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Friday, March 05, 2010 8:11 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems I'd have to talk to Luis Lavena

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Will Green
[mailto: ironruby-core-boun...@rubyforge.org] *On Behalf Of *Will Green *Sent:* Friday, March 05, 2010 8:11 AM *To:* ironruby-core@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems I'd have to talk to Luis Lavena, the current maintainer of win32console. I might also

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Shri Borde
-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Friday, March 05, 2010 9:46 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems I may not fully understand the Gem process here, so please pardon any ignorance. As I understand it, the ability

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Will Green
...@rubyforge.org [mailto:ironruby-core- boun...@rubyforge.org] On Behalf Of Will Green Sent: Friday, March 05, 2010 9:46 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems I may not fully understand the Gem process here, so please pardon any ignorance

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-05 Thread Shri Borde
: ironruby-core-boun...@rubyforge.org [ironruby-core-boun...@rubyforge.org] on behalf of Will Green [w...@hotgazpacho.org] Sent: Friday, March 05, 2010 9:46 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems I may not fully understand the Gem process here

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-04 Thread Shri Borde
: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Will Green Sent: Tuesday, March 02, 2010 11:52 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Shri Borde
: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. -- Will Green http://hotgazpacho.org/ On Tue, Mar 2, 2010 at 1:07 PM

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Jim Deville
: Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. -- Will Green http://hotgazpacho.org/ On Tue, Mar 2, 2010 at 1

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Will Green
@rubyforge.org ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems It does seem like there isn’t a way to distinguish between IronRuby and MRI. C:\ ir.exe require rubygems = true Gem::Platform.local() = #Gem::Platform:0x1409 @cpu=x86, @os=mswin32

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Will Green
Of *Will Green *Sent:* Tuesday, March 02, 2010 11:52 AM *To:* ironruby-core@rubyforge.org *Subject:* Re: [Ironruby-core] IronRuby version of existing gems That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Ivan Porto Carrero
? -- From: Shri Borde shri.bo...@microsoft.com Sent: Wednesday, March 03, 2010 9:55 AM To: ironruby-core@rubyforge.org ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems It does seem like there isn’t a way to distinguish between IronRuby

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Shri Borde
To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems we need to update rbconfig. it should also detect the runtime correctly --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Web: http://whiterabbitconsulting.eu - http

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Shri Borde
: Wednesday, March 03, 2010 5:05 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems I will set RUBY_PLATFORM to “.net” and RbConfig::CONFIG[“arch”] to “universal-.net-2.0” (or “universal-.net-4.0” for the .NET 4 builds) From: ironruby-core-boun

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-03 Thread Shri Borde
: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde Sent: Wednesday, March 03, 2010 6:31 PM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] IronRuby version of existing gems Does anyone know if this will allow authoring of IronRuby

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-02 Thread Jim Deville
I believe JRuby is doing the 1st one, which makes sense in my opinion. If possible we should prefer platform == “ironruby”, (or .net, do we need to differentiate .net and mono?), but accept others. JD From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On

Re: [Ironruby-core] IronRuby version of existing gems

2010-03-02 Thread Will Green
That all depends on how Gem checks the platform. If it uses the RUBY_PLATFORM variable, then IronRuby needs to change what it reports here. Currently, it reports i386-mswin32. -- Will Green http://hotgazpacho.org/ On Tue, Mar 2, 2010 at 1:07 PM, Jim Deville jdevi...@microsoft.com wrote: I