Requires: You should not rely on bundler's auto-requires in a gem at all. Always explicitly require anything you use directly in library code.
Gems from git: in bundler 1.0.9 (I think) and later, you can put overrides in the Gemfile. E.g.:
# gemspec
s.add_development_dependency 'factory_girl', '~> 2.0'
# Gemfile
group :development do
gem 'factory_girl', :git => 'git://github.com/thoughtbot/factory_girl.git'
end
For a development dependency, this is fine. For a runtime dependency, you should only depend on the edge version while you are waiting for a new release to become available -- before you release your gem, you should remove all references to unreleased versions of runtime deps and ensure that your gem still works.
Further discussion: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
Rhett
>
> --
> You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
> To post to this group, send email to ruby-b...@googlegroups.com.
> To unsubscribe from this group, send email to ruby-bundler...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ruby-bundler?hl=en.
>
s.add_development_dependency 'capybara', '>= 0.4.0'
s.add_development_dependency 'launchy'
but `bundle install` ignores them (I am not excluding any groups). Am I doing something wrong?
Earle
All is good. Thanks for the help.
Earle