i seem to be using the same plugins for all my sites and was wondering if there is a way to make the process easier and faster? is this what is called by "packing your own gems"? -- 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 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 -~----------~----~----~----~------~----~------~--~---
Jeremy McAnally
2006-Dec-27 00:01 UTC
Re: is there a way to not repeat installing plugins?
It mostly depends on what plugins you want to use; here''s a tutorial on using acts_as_authenticated as a system wide generator: http://www.nullsense.net/2006/5/31/installing-acts_as_authenticated-as-a-system-wide-generator You could probably use the same basic principles with any "generator-ish" plugin. --Jeremy On 12/26/06, koloa <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > i seem to be using the same plugins for all my sites and was wondering > if there is a way to make the process easier and faster? > > is this what is called by "packing your own gems"? > > -- > 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 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 -~----------~----~----~----~------~----~------~--~---
Check out the GemsOnRails project. I included it in my list of 5 Gems you might not know about but should: http://anthonyeden.com/2006/12/20/gems-you-might-not-know-about-but-should This assumes of course that the plugin is available as a gem. If not, poke the author and tell them they should make it a gem. :-) V/r Anthony On 12/26/06, koloa <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > i seem to be using the same plugins for all my sites and was wondering > if there is a way to make the process easier and faster? > > is this what is called by "packing your own gems"? > > -- > Posted via http://www.ruby-forum.com/. > > > >-- Cell: 808 782-5046 Current Location: Melbourne, FL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I think the OP asked a slightly different question (although this is a very valuable answer). The way I read the question it was, "say I always start out with the same set of base plugins -- say engines, login_engine, user_engine, exception_notification, ez_where. Does anyone know an elegant way to press a magic button to achieve a base plugin configuration much as ''rails foo'' achieves a base Rails app configuration. Just my interpretation of the question. --steve On Dec 26, 2006, at 8:08 PM, Anthony Eden wrote:> > Check out the GemsOnRails project. I included it in my list of 5 Gems > you might not know about but should: > > http://anthonyeden.com/2006/12/20/gems-you-might-not-know-about-but- > should > > This assumes of course that the plugin is available as a gem. If not, > poke the author and tell them they should make it a gem. :-) > > V/r > Anthony > > On 12/26/06, koloa <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote: >> >> i seem to be using the same plugins for all my sites and was >> wondering >> if there is a way to make the process easier and faster? >> >> is this what is called by "packing your own gems"? >> >> -- >> Posted via http://www.ruby-forum.com/. >> >> > >> > > > -- > Cell: 808 782-5046 > Current Location: Melbourne, FL > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
yes, for all my applications i am using acts as ferret, acts as rateable, commentable, attachment, taggable, redcloth, google_map, and a few more. installing all of them everytime takes some time! Steve Ross wrote:> I think the OP asked a slightly different question (although this is > a very valuable answer). The way I read the question it was, "say I > always start out with the same set of base plugins -- say engines, > login_engine, user_engine, exception_notification, ez_where. Does > anyone know an elegant way to press a magic button to achieve a base > plugin configuration much as ''rails foo'' achieves a base Rails app > configuration. > > Just my interpretation of the question. > > --steve-- 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 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 -~----------~----~----~----~------~----~------~--~---
use svn[1] to install the plugin - then when you install, the svn checkout will extract the external references to your plugin directory. script/plugin install -X can be used to setup the svn externals reference, or you can use "svn propedit svn:externals vendor/plugin" to define all the external refs. The benefit you have here is you can ''freeze'' to specific version of a plugin - which comes in real handy when you''re mirroring production in your tests. [1] http://svnbook.red-bean.com/ Cheers, Jodi General Partner The nNovation Group inc. www.nnovation.ca/blog On 27-Dec-06, at 2:19 PM, koloa wrote:> > yes, for all my applications i am using acts as ferret, acts as > rateable, commentable, attachment, taggable, redcloth, google_map, > and a few more. installing all of them everytime takes some time! > > > > > Steve Ross wrote: >> I think the OP asked a slightly different question (although this is >> a very valuable answer). The way I read the question it was, "say I >> always start out with the same set of base plugins -- say engines, >> login_engine, user_engine, exception_notification, ez_where. Does >> anyone know an elegant way to press a magic button to achieve a base >> plugin configuration much as ''rails foo'' achieves a base Rails app >> configuration. >> Just my interpretation of the question. >> --steve > > > -- > 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 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 -~----------~----~----~----~------~----~------~--~---
I think something more along these lines would be a start toward what
the OP was looking for:
# Yikes! Hard coded stuff. Put your stock plugins here
{
"exception_notification" =>
"http://dev.rubyonrails.org/svn/
rails/plugins/exception_notification/",
"acts_as_authenticated" =>
"http://svn.techno-weenie.net/
projects/plugins/acts_as_authenticated",
"rspec" =>
"svn://rubyforge.org/var/svn/rspec/
tags/REL_0_7_4/vendor/rspec_on_rails/vendor/plugins/rspec"
}.each_pair do |plugin, repos|
force = ''''
if File.exist?("vendor/plugins/#{plugin}")
puts "Plugin #{plugin} appears to be installed already.
Force? [yN]"
next if gets.downcase != ''y''
force = '' --force''
end
system("script/plugin install #{repos} #{plugin}#{force}")
end
# ------------------------------------------------------
Clearly, this was a quick hack, but it will install a base set of
plugins from their repositories. TODOs would be to install them as
svn externals and/or add to repository.
Thoughts?
On Dec 27, 2006, at 11:31 AM, Jodi Showers wrote:
>
> use svn[1] to install the plugin - then when you install, the svn
> checkout will extract the external references to your plugin
> directory.
>
> script/plugin install -X can be used to setup the svn externals
> reference, or you can use "svn propedit svn:externals vendor/
> plugin" to define all the external refs. The benefit you have here
> is you can ''freeze'' to specific version of a plugin -
which comes
> in real handy when you''re mirroring production in your tests.
>
> [1] http://svnbook.red-bean.com/
>
> Cheers,
> Jodi
> General Partner
> The nNovation Group inc.
> www.nnovation.ca/blog
>
>
> On 27-Dec-06, at 2:19 PM, koloa wrote:
>
>>
>> yes, for all my applications i am using acts as ferret, acts as
>> rateable, commentable, attachment, taggable, redcloth,
>> google_map, and a few more. installing all of them everytime
>> takes some time!
>>
>>
>>
>>
>> Steve Ross wrote:
>>> I think the OP asked a slightly different question (although this
is
>>> a very valuable answer). The way I read the question it was,
"say I
>>> always start out with the same set of base plugins -- say engines,
>>> login_engine, user_engine, exception_notification, ez_where. Does
>>> anyone know an elegant way to press a magic button to achieve a
base
>>> plugin configuration much as ''rails foo'' achieves
a base Rails app
>>> configuration.
>>> Just my interpretation of the question.
>>> --steve
>>
>>
>> --
>> 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 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
-~----------~----~----~----~------~----~------~--~---
Correction. Line 9 should read:
next if gets.downcase.strip != ''y''
--steve
On Dec 27, 2006, at 11:31 AM, Jodi Showers wrote:
>
> use svn[1] to install the plugin - then when you install, the svn
> checkout will extract the external references to your plugin
> directory.
>
> script/plugin install -X can be used to setup the svn externals
> reference, or you can use "svn propedit svn:externals vendor/
> plugin" to define all the external refs. The benefit you have here
> is you can ''freeze'' to specific version of a plugin -
which comes
> in real handy when you''re mirroring production in your tests.
>
> [1] http://svnbook.red-bean.com/
>
> Cheers,
> Jodi
> General Partner
> The nNovation Group inc.
> www.nnovation.ca/blog
>
>
> On 27-Dec-06, at 2:19 PM, koloa wrote:
>
>>
>> yes, for all my applications i am using acts as ferret, acts as
>> rateable, commentable, attachment, taggable, redcloth,
>> google_map, and a few more. installing all of them everytime
>> takes some time!
>>
>>
>>
>>
>> Steve Ross wrote:
>>> I think the OP asked a slightly different question (although this
is
>>> a very valuable answer). The way I read the question it was,
"say I
>>> always start out with the same set of base plugins -- say engines,
>>> login_engine, user_engine, exception_notification, ez_where. Does
>>> anyone know an elegant way to press a magic button to achieve a
base
>>> plugin configuration much as ''rails foo'' achieves
a base Rails app
>>> configuration.
>>> Just my interpretation of the question.
>>> --steve
>>
>>
>> --
>> 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 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
-~----------~----~----~----~------~----~------~--~---
Steve, I like it. How about making it so the plugin list is a simple text file somewhere and then making a Rake task which will handle the installation? V/r Anthony On 12/27/06, s.ross <cwdinfo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I think something more along these lines would be a start toward what > the OP was looking for: > > # Yikes! Hard coded stuff. Put your stock plugins here > { > "exception_notification" => "http://dev.rubyonrails.org/svn/ > rails/plugins/exception_notification/", > "acts_as_authenticated" => "http://svn.techno-weenie.net/ > projects/plugins/acts_as_authenticated", > "rspec" => "svn://rubyforge.org/var/svn/rspec/ > tags/REL_0_7_4/vendor/rspec_on_rails/vendor/plugins/rspec" > }.each_pair do |plugin, repos| > force = '''' > if File.exist?("vendor/plugins/#{plugin}") > puts "Plugin #{plugin} appears to be installed already. > Force? [yN]" > next if gets.downcase != ''y'' > force = '' --force'' > end > system("script/plugin install #{repos} #{plugin}#{force}") > end > # ------------------------------------------------------ > > Clearly, this was a quick hack, but it will install a base set of > plugins from their repositories. TODOs would be to install them as > svn externals and/or add to repository. > > Thoughts? > > > On Dec 27, 2006, at 11:31 AM, Jodi Showers wrote: > > > > > use svn[1] to install the plugin - then when you install, the svn > > checkout will extract the external references to your plugin > > directory. > > > > script/plugin install -X can be used to setup the svn externals > > reference, or you can use "svn propedit svn:externals vendor/ > > plugin" to define all the external refs. The benefit you have here > > is you can ''freeze'' to specific version of a plugin - which comes > > in real handy when you''re mirroring production in your tests. > > > > [1] http://svnbook.red-bean.com/ > > > > Cheers, > > Jodi > > General Partner > > The nNovation Group inc. > > www.nnovation.ca/blog > > > > > > On 27-Dec-06, at 2:19 PM, koloa wrote: > > > >> > >> yes, for all my applications i am using acts as ferret, acts as > >> rateable, commentable, attachment, taggable, redcloth, > >> google_map, and a few more. installing all of them everytime > >> takes some time! > >> > >> > >> > >> > >> Steve Ross wrote: > >>> I think the OP asked a slightly different question (although this is > >>> a very valuable answer). The way I read the question it was, "say I > >>> always start out with the same set of base plugins -- say engines, > >>> login_engine, user_engine, exception_notification, ez_where. Does > >>> anyone know an elegant way to press a magic button to achieve a base > >>> plugin configuration much as ''rails foo'' achieves a base Rails app > >>> configuration. > >>> Just my interpretation of the question. > >>> --steve > >> > >> > >> -- > >> Posted via http://www.ruby-forum.com/. > >> > >> > > > > > > > > > > > > >-- Cell: 808 782-5046 Current Location: Melbourne, FL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Ok, there''s a rake task on: http://rtfm.calicowebdev.com/2006/12/24/installing-stock-plugins Steve On Dec 27, 2006, at 1:03 PM, Anthony Eden wrote:> > Steve, > > I like it. How about making it so the plugin list is a simple text > file somewhere and then making a Rake task which will handle the > installation? > > V/r > Anthony > > On 12/27/06, s.ross <cwdinfo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> >> I think something more along these lines would be a start toward what >> the OP was looking for: >> >> # Yikes! Hard coded stuff. Put your stock plugins here >> { >> "exception_notification" => "http://dev.rubyonrails.org/svn/ >> rails/plugins/exception_notification/", >> "acts_as_authenticated" => "http://svn.techno-weenie.net/ >> projects/plugins/acts_as_authenticated", >> "rspec" => "svn://rubyforge.org/var/svn/rspec/ >> tags/REL_0_7_4/vendor/rspec_on_rails/vendor/plugins/rspec" >> }.each_pair do |plugin, repos| >> force = '''' >> if File.exist?("vendor/plugins/#{plugin}") >> puts "Plugin #{plugin} appears to be installed already. >> Force? [yN]" >> next if gets.downcase != ''y'' >> force = '' --force'' >> end >> system("script/plugin install #{repos} #{plugin}#{force}") >> end >> # ------------------------------------------------------ >> >> Clearly, this was a quick hack, but it will install a base set of >> plugins from their repositories. TODOs would be to install them as >> svn externals and/or add to repository. >> >> Thoughts? >> >> >> On Dec 27, 2006, at 11:31 AM, Jodi Showers wrote: >> >> > >> > use svn[1] to install the plugin - then when you install, the svn >> > checkout will extract the external references to your plugin >> > directory. >> > >> > script/plugin install -X can be used to setup the svn externals >> > reference, or you can use "svn propedit svn:externals vendor/ >> > plugin" to define all the external refs. The benefit you have here >> > is you can ''freeze'' to specific version of a plugin - which comes >> > in real handy when you''re mirroring production in your tests. >> > >> > [1] http://svnbook.red-bean.com/ >> > >> > Cheers, >> > Jodi >> > General Partner >> > The nNovation Group inc. >> > www.nnovation.ca/blog >> > >> > >> > On 27-Dec-06, at 2:19 PM, koloa wrote: >> > >> >> >> >> yes, for all my applications i am using acts as ferret, acts as >> >> rateable, commentable, attachment, taggable, redcloth, >> >> google_map, and a few more. installing all of them everytime >> >> takes some time! >> >> >> >> >> >> >> >> >> >> Steve Ross wrote: >> >>> I think the OP asked a slightly different question (although >> this is >> >>> a very valuable answer). The way I read the question it was, >> "say I >> >>> always start out with the same set of base plugins -- say >> engines, >> >>> login_engine, user_engine, exception_notification, ez_where. Does >> >>> anyone know an elegant way to press a magic button to achieve >> a base >> >>> plugin configuration much as ''rails foo'' achieves a base Rails >> app >> >>> configuration. >> >>> Just my interpretation of the question. >> >>> --steve >> >> >> >> >> >> -- >> >> Posted via http://www.ruby-forum.com/. >> >> >> >> > >> > >> > >> > > >> >> >> > >> > > > -- > Cell: 808 782-5046 > Current Location: Melbourne, FL > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
There is a replacement for the plugin script called Rapt: http://rapt.rubyforge.org/ Rapt has the concept of a "plugin pack", that is a set of plugins you can install in one swell foop. I''ve never used this functionality --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
quick question... since ive been learning more about svns....couldnt i just create a base rails application, install all the plugins i need, check it back into the svn, and when ever i want to build a new application, i can just start with the base and branch off into a new svn application? -- 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 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 -~----------~----~----~----~------~----~------~--~---
http://blog.hasmanythrough.com/2006/12/28/stop-using-the-rails-command/ might be what you''re after if that''s your preferred approach. On 12/29/06, koloa <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > quick question... > > since ive been learning more about svns....couldnt i just create a base > rails application, install all the plugins i need, check it back into > the svn, and when ever i want to build a new application, i can just > start with the base and branch off into a new svn application? > > -- > Posted via http://www.ruby-forum.com/. > > > >-- * J * ~ --~--~---------~--~----~------------~-------~--~----~ 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 james, thanks for the post...that article led me to this article http://lesscode.org/2005/10/27/rails-simplest-plugin-manager/ ///// If you want to use svn:externals, make sure you have your vendor/plugins directory under subversions control before installing any plugins . If your not sure, do something like this: $ svn info vendor/plugins foo: (Not a versioned resource) $ svn mkdir vendor/plugins $ svn ci -m "adding teh plugins directory so I can use this r0x3ring plugin manager..." ///// after i do the above, i check out the folder, and then i can do the normal script/install plugin .... and just check back into the svn? actually, i just came across this.. http://dev.subimage.com/projects/substruct/wiki/GettingTheCode i will see if this is what i need. thanks! -- 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 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 -~----------~----~----~----~------~----~------~--~---
found an example! @ http://blog.teksol.info/articles/2006/03/09/subversion-primer-for-rails-projects ////// $ svn propset svn:externals "file_column http://opensvn.csie.org/rails_file_column/plugins/file_column/tags/rel_0-3-1/" vendor/plugins property ''svn:externals'' set on ''vendor/plugins'' $ svn update vendor/plugins Fetching external item into ''vendor/plugins/file_column'' A vendor/plugins/file_column/test ... U vendor/plugins/file_column Updated external to revision 58. Updated to revision 4. /////// i also found piston...http://piston.rubyforge.org/usage.html -- 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 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 -~----------~----~----~----~------~----~------~--~---
i guess to install a plugin under svn, just use the -x option? -- 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 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 -~----------~----~----~----~------~----~------~--~---