BUN-DLER. This is exactly the problem that Bundler was designed to solve. Although Bundler is required for Rails 3, you can also use it with Rails 2.3 (or Sinatra, or whatever). When you switch a Rails 2.3 app over to Bundler, you need to move the config.gem statements from your environment.rb into "gem" statements in the Gemfile, and remove the vendored gems. Then do a little config (per the Bundler website) and you'll be off to the races.
http://gembundler.com/rails23.html Do it, you won't regret the the time it takes to learn Bundler, it's a great technology. On Sep 7, 2010, at 11:29 AM, Erik Pukinskis wrote: > 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 -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
