Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

clarification about Bundler.require #3

ericgj opened this Issue Oct 14, 2010 · 2 comments


None yet
2 participants

ericgj commented Oct 14, 2010

Thanks for this useful write-up.

One thing I'm not clear on is if you want your gem to be used either with or without bundler, it's great that bundler now picks up on the .gemspec dependencies but don't you still need to rescue every time you require 'bundler' and Bundler.require() ? I think it would be helpful to have an example of that here. Unless I'm missing something.


radar commented Oct 16, 2010

There should only be one require 'bundler' anywhere in the gem, and that would be in the Rakefile, which is only used for developing the gem. In this case, anybody attempting to do any development work on the gem should have Bundler installed since without it they'll be unable to build the gem.

Does this answer your question?

ericgj commented Oct 18, 2010

So if I understand, in your examples, activesupport and thor are not managed through Bundler at all (you don't call Bundler.setup :default before they are required)? In which case what is the advantage of bundle installing them?

Not sure I like the sound of requiring Bundler to build the gem. I guess I'm kind of left scratching my head whether the advantage of Bundler over plain old rubygems in this case (sandboxing the development gems) is really worth it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment