I was going to make Rails use "bundler/setup" instead of calling Bundler.setup manually, but I have noticed two small but important differences.
Any chance we can change bundler/setup file to act the same way?
bundler/setup has pretty different behaviour than boot.rb. Are you sure you want to catch all BundlerErrors instead of just GemNotFound?
Yehuda told me require "bundler/setup" is the recommended way and that we should go for it. :D
So I changed it in one of my apps and got this error:
jose:~/Work/devs_at_work[ree-1.8.7-2010.02][master*]$ rails s
Could not find i18n-0.4.1 in any of the sources
If I was a beginner, I would be completely clueless at this point. So it may be ok to rescue all BundlerErrors, but we may need (and not only for Rails) a slightly better message in cases a Gem is not found. What do you think?
I think that's a good idea. :)
Hey Andre, do you want me to provide a patch for this then?
if you could provide a patch that would be great :)
Re-open with patch.