[Rails] Re: running bundle sometimes installs other gems than ones specified in Gemfile

John Merlino wrote in post #1106692:
> So this means I don't need to add devise to my Gemfile now and run a
> bundle because devise is already isntalled and fully functioning in my
> app?

No. This means that if you have devise in your gem file, and run bundle,
all gems that devise depends on will also be installed whether they are
specifically listed in the gem file or not.

For example, devise depends on warden. So if you install devise, either
manually using the "gem install" command, or indirectly by including
devise in your gem file and running "bundle [install]" then warden
(along with devises' other dependencies) will be installed.

However, if you were to include warden in your gem file, and NOT devise,
then only warden would be installed (along with all of warden's
dependencies) and devise would NOT. Warden does not depend on devise.

--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.