On Jan 29, 2009, at 7:50 PM, Colin Summers wrote:
> I have faced some of this. I found that doing > sudo gem update --system > sudo gem cleanup Thanks! I'll definitely try that. In the end, I managed to fix it by simply installing everything in ~/.gem Not the prettiest solution, but at least it seems to work for now. I guess some gem overview file got corrupted or something then? > The error about Rails 2.1.0 already running (or something like that) > might have to do with the environment.rb file you have, which might > specify a particular rails version. environment.rb specified Rails 2.2.2 (and 2.1.1 before that), but despite that at some point ruby tried to load 2.1.0 modules. Removing 2.1.0 meant it tried to load Rails 1.x, which I think was installed in a completely different location even. > That also used to happen to me, > and I usually had several versions of Rails on one machine. I don't > believe that's ideal, so now there's just one and I edit > environment.rb for each project accordingly. I prefer working in the same version of Rails as my co-workers, so if one project is upgraded and another isn't, I need both versions of Rails. mcv. --~--~---------~--~----~------------~-------~--~----~ 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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
