David Winter | 19 Jan 16:59

Re: Rails/Gem errors?


Alan Francis wrote:
> David Winter wrote:
>> Alan Francis wrote:
> 
>>> You can fix it in environment.rb.  Find the 'require_gem' lines and 
>>> replace them with 'gem'
>> 
>> Actually, do:
>> 
>>     gem pristine --all
>> 
>> From: http://comments.gmane.org/gmane.comp.lang.ruby.rails/117220
> 
> I don't think that'll work. I did it on my machine immediatly I upgraded 
> gems, and *still* had to fix my rails app.
> 
> I got the impression it only fixed the binstubs - 'rails', 'rake', 'cap' 
> etc  I dont think it'll search out uses of require_gem in rb files on 
> your machine ?
> 
> A.

You're right. The moment I saw it, I thought it was the 'official' fix. 
I was wrong. Doing a `rake db:migrate` produces the warning. Very 
irritating.

--

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@...
To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---


Gmane