Rails 0.14.1 fails to even generate a simple model and controller correctly, though I'm guessing that's only since Ruby 1.8.3. Could be wrong. Having just started with Rails, this was very off-putting! I was told in #rubyonrails that I needed to update to 0.14.2. It said it needed Active Record 1.12.2 and that needed Active Support 1.2.2. It also needed Action Pack 1.10.2, Action Mailer 1. 1.2 and Action Web Service 0.9.2. I bumped all that (which was trivial but time consuming) and it worked. Phew! Also, could you make an emerge fail when a gem doesn't meet all its dependencies? It kept trying to replace Rails with a bunch of empty folders.
bumped all of the packages up. not sure what you mean on the last statement, though.
Before updating the dependencies, I tried emerging Rails and it didn't stop even though the required versions were not there.
Via portage or via "gem update" ? Can you give a quick step by step runthrough of what you did and how it failed/kept going when it shouldn't have?
I renamed the ebuild to bump the version. The ebuild still had a dependency for Active Record 1.12.1 because I didn't know it needed 1.12.2 until I tried it. During the emerge, an error appeared saying that I needed 1.12.2 but the emerge process didn't stop.
gotcha. will check into it.
Looks to be a bug/limitation in rubygems itself. I filed a request with the rubygems folks to see if they can fix it: http://rubyforge.org/tracker/index.php?func=detail&aid=2773&group_id=126&atid=575
Going to close this one as fixed, since it is. The other issue is an upstream bug, as noted on my previous entry.
