On Mon, Nov 24, 2008 at 5:05 PM, Kenneth Kalmer <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 2:38 PM, Kenneth Kalmer> > The code is available at > git://github.com/kennethkalmer/rails-broken-gems-example.git and shows > exactly how to simulate the breakage mentioned by Steven. Please > review the README file > (http://github.com/kennethkalmer/rails-broken-gems-example/tree/master) > for a complete breakdown of the issue and how to fix it. > > In a nutshell, it boils down to the one-line patch below: > > --- a/vendor/rails/railties/lib/initializer.rb > +++ b/vendor/rails/railties/lib/initializer.rb > @@ -284,7 +284,7 @@ module Rails > def check_gem_dependencies > unloaded_gems = @configuration.gems.reject { |g| g.loaded? } > if unloaded_gems.size > 0 > - @gems_dependencies_loaded = false > + @gems_dependencies_loaded = false || $rails_gem_installer > # don't print if the gems rake tasks are being run > unless $rails_gem_installer > abort <<-end_error > > Any feedback would be appreciated, including pointers to the correct > Lighthouse tickets for making my case.
Seems I was in a too big a hurry, this does solve the initial issue but creates a new one upon running 'rake gems', which now complains about the gem specifications... I'll investigate and report my findings. Best -- Kenneth Kalmer [EMAIL PROTECTED] http://opensourcery.co.za --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
