My goal was to clear the blocking issues. If someone can get to the “gem
update --system†before RC3, that’s cool. Else, there is a workaround
for folks who want to use Rails 3.
From: [email protected]
[mailto:[email protected]] On Behalf Of Jim D.
Sent: Saturday, March 06, 2010 6:13 PM
To: [email protected]
Subject: Re: [Ironruby-core] Basic Rails 3 app works (FYI review)
Or can’t we do a gem update --system???
JD
From: [email protected]
[mailto:[email protected]] On Behalf Of Ivan Porto
Carrero
Sent: Saturday, March 06, 2010 3:25 PM
To: [email protected]
Subject: Re: [Ironruby-core] Basic Rails 3 app works (FYI review)
You can use bundler 0.9 perhaps that will install on gems 1.3.5
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Web: http://whiterabbitconsulting.eu - http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
Microsoft IronRuby/C# MVP
On Sat, Mar 6, 2010 at 11:35 PM, Shri B.
<[email protected]mailto:[email protected]> wrote:
tfpt review “/shelveset:r3;REDMOND\sborde”
Add a stub implementation of YAML.add_builtin_type. With this fix, I can
create a Rails 3 app, add a controller, start the server, and request
the main page! See
http://weblog.rubyonrails.org/2010/2/5/rails-3-0-beta-release for setup
instructions. The caveats are:
• You need to use MRI to install the dependency gems since Rails
3 uses the bundler gem specifies RubyGems 1.3.6 as a dependency, whereas
IronRuby includes 1.3.5.
• You need to use ir.exe -1.8.7
• None of the ActiveRecord IronRuby adapters have been updated
to work with Rails 3. So you cannot use ActiveRecord
Also, Enables Rails 3 tests that now work after Tomas’s fixes for
Symbol#to_proc and encoding
Ironruby-core mailing list
[email protected]mailto:[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
