I've had projects break before when I've updated plugins (my own and others'). It's a little more clear what version of a gem you have installed versus a plugin, which may or may not be the most recent revision.
On Oct 19, 10:54 am, Robert Walker <[email protected]> wrote: > Hassan Schroeder wrote: > > Trying out Authlogic for the first time -- somewhere, can't find it now > > of course :-) I saw a recommendation to use the plugin form, but the > > Ryan Bates railscast recommends the gem (without explanation). > > > Comments or recommendations? > > I believe that Ryan tends to prefer using gem dependencies instead of > plugins when possible. This is also my own preference. I would guess > that there is no further explanation provided because it seems to depend > upon personal preference. > > I tend to prefer managing shared libraries outside of my application. I > feel it eases management of shared libraries and makes upgrading my > applications to use the newer version easier. Plus it also reduces the > amount of code that lives inside my project (and hence my version > control system). I don't really see the necessity to version control > shared library code. > > It is also my understanding that Rails 3 will contain some improvements > to the way gem dependencies are currently handled. > -- > 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 -~----------~----~----~----~------~----~------~--~---
