Hello, which is the difference of installing a plugin using script/ plugin install, and installing it using svn export? --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Hi,> Hello, which is the difference of installing a plugin using script/ > plugin install, and installing it using svn export? >If you use svn export you are just copying the code tree to your vendor directory. When you use plugin/install you are also copying the code tree, but the script named "install.rb" at the plug-in root is executed too. If the plug-in needs any kind of installation (like copying some files) then it''s likely the code for that will be at the install.rb script. The same is true for uninstalling and the uninstall.rb script. There a number of plug-ins that don''t use the install.rb script but rake tasks instead. Thus, you can install the plug-in either by using install, a checkout, or even by copying the code directly between two projects and then running the installation task. My personal preference is not to use any code at install.rb but just a simple output of the README file, in which I explain which dependencies -if any- the plugin has, which tasks are included within, which configuration variables are available, and a simple use case. There is also another difference between using plugin/install and a svn checkout. By using plugin/install you can install a plugin via http, without having subversion installed, so for some cases that would be a plus. regards, javier ramírez --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Thank you, I didn''t know the interaction with install.rb file. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Eduardo Yáñez Parareda wrote:> Hello, which is the difference of installing a plugin using script/ > plugin install, and installing it using svn export?Use piston. script/plugin install just copies the files in. But script/plugin install -x uses svn:externals to bond your files to two repositories, yours and the plugin''s. That''s bad because each time that plugin''s author commits, you get a new version. That author might practice Continuous Integration! svn:externals is for sharing code within one team, so you can trust each others'' practices. piston fixes this issue by putting the plugin truly into your own repository, and storing its home repository in its secret properties. Then ''piston update vendor/plugins/thing'' will re-download the source, on command. This is ideal, because you can track that plugin''s changes and only get what you need. -- Phlip http://assert2.rubyforge.org/ --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
A couple of simple questions about plugins: 1. Is the rapt plugin installer tool actively in use? I like the idea of the plugin pack and keyword searching, but it doesn''t seem like there is much activity on this project since it was posted a couple of years ago. Perhaps it has been obsoleted by developments with script/ plugin? 2. Some of the plugins out there have the source located in the svn "trunk" directory. When you install such a thing using "ruby script/ plugin install svn://blah.com/pluginname/trunk" (for example), then you end up with a a plugin called "trunk" in vendor/plugins. This seems less than ideal. Is there some way to name the plugin directory when it is installed? Thanks in advance for any answers. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 7 Mar 2008, at 06:47, ewo wrote:> > A couple of simple questions about plugins: > > 1. Is the rapt plugin installer tool actively in use? I like the idea > of the plugin pack and keyword searching, but it doesn''t seem like > there is much activity on this project since it was posted a couple of > years ago. Perhaps it has been obsoleted by developments with script/ > plugin? >dunno> 2. Some of the plugins out there have the source located in the svn > "trunk" directory. When you install such a thing using "ruby script/ > plugin install svn://blah.com/pluginname/trunk" (for example), then > you end up with a a plugin called "trunk" in vendor/plugins. This > seems less than ideal. Is there some way to name the plugin directory > when it is installed? >script/plugin doesn''t do anything very magic. You could just check it out yourself or rename it after it''s been installed. Fred> Thanks in advance for any answers. > --~--~---------~--~----~------------~-------~--~----~ > 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > For more options, visit this group at http://groups.google.com/group/rubyon--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---