I’ve noticed that most plugins are available from SVN repositories. I’m using SVN to manage my project code. I have been using the -x option because it allowed me to easily get the latest changes to the plugins. But, when I went to another computer, and attempted to checkout my project from another computer, it failed when grabbing one of the plugins. Aparently, a plugin vendor changed their repository url. So, I’m wondering whether it is better to install plugins using the SVN -x (external) option, or to checkout the plugin directly? I’d like to know how others are/have delt with this issue.
Hi, Larry
It all depends on how stable the plugin is, and how much you trust the author to maintain backwards compatibility. Personally, I only install with the -x option when I'm installing my plugins from my svn server.
Cheers - Starr
Hi, Larry
It all depends on how stable the plugin is, and how much you trust the author to maintain backwards compatibility. Personally, I only install with the -x option when I'm installing my plugins from my svn server.
Cheers - Starr
Personally I never use this because a rails upgrade might (and has) broken plugin functionality. It’s better to upgrade manually with another checkout.
Vish
For anything I use in my application, I keep my own svn copy of the plugin (and even rails). Then I can upgrade when I have/want to, but I always know that I have working code that I tested.
Those plugins are installed in the app using an external setting of svn. So I have one trusted source, and when needed I just update my repository with the latest plugin.
This has an additional advantage of letting me tag versions with the matching plugin. So that if I have a future version using a newer rails and a newer set of plugins, I can easilly go back to a previous version, knowing that every tag is stable.
Bye,
Guy.
Rick: seems nice 
Would be better if it had a ‘piston rollback’ also 
Thanks!
Vish
