Yep, bundle exec is useful but for longer time it won't solve your problems at all. Avoiding gem dependency problems with bundle exec is like plaster against cancer. RVM and Gemsets are the only way to avoid conflicts in future.
If you follow that tutorial: in later chapters there will be other new gems too. When you install them like first writing it to Gemfile then bundle install pay attention to specify the gemname properly: "bundle install <gemname>" (for example: "bundle install autotest"). This way bundle will only install that gem and it won't touch the others. Also it might be useful to export your Gemset. It's a really good practise for all your projects in future. Ask me in private if you have further problems, good luck: gezope On Jul 18, 8:27 am, 7stud -- <[email protected]> wrote: > Conrad Taylor wrote in post #1011293: > > > On Sat, Jul 16, 2011 at 4:34 AM, 7stud -- <[email protected]> wrote: > > >> versions back to the old versions, but now I get that spork error. Is > >> there a way to 'unactivate' spork 0.9.0 and 'activate' spork 0.8.4? > > > Hi, if you're installing gems using bundler, the recommended way to run > > their associated executables is by doing the following: > > > bundle exec <executable-name> > > Thanks. I read about that at the Bundler website, and now I am > executing all excutables with bundle exec. > > -- > Posted viahttp://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 [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.
