Hey folks, I've had this problem enough times that I decided I want to get to the bottom of it, rather than just put on band-aids.
Whenever I set up a rails project with a bunch of gem dependencies, I get all kinds of dependency errors of the "can't activate , already activated such_and_such-2.0.4" variety. The band-aid solution is to figure out the exact version of the gem that's required by the app and uninstall all other versions. But that's a super annoying process. And god help me if I have two projects with conflicting requirements someday. It seems like maybe the issue is plugins that will accept any old gem, and therefore activate the newest version, and then the app requires an older gem, and it then can't activate it. Is that what's going on? And is there any way around it? And is this the reason for the new bundler? Should I just upgrade all my projects to Rails 3? Thanks for any enlightenment. The web doesn't seem to have any clear guidance for me on this one. Best, Erik -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
