Rails - Mar 2007 - Plugin update management - can someone explain please??/

Hi guys,

I''m just after clarification regarding how plugins can be managed
(updated,
frozen etc).  Like:

a) Once installed what are the options for updating a plugin?

b) Are there global "update" methods available that may update ALL
plugins,
or all items in the vendor directory (e.g. rails) available?

c) If there are "update all/multiple" plugins facilities, is there a
means
of "freezing" some plugins so they won''t be automatically
updated?

d) Following on from c) if one was to make changes to a plugin what is the
recommended approach for ensuring (i) an update can''t be kicked off
which
overwrites the changes and/or (ii) the changes could be merged in?

Thanks
Greg

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Take a look at piston (http://piston.rubyforge.org/).
--
Building an e-commerce site with Rails?
http://agilewebdevelopment.com/rails-ecommerce

Meet up at RailsConf:
http://railsconf2007.conferencemeetup.com/

On Mar 28, 2007, at 7:40 PM, Greg Hauptmann wrote:
> Hi guys,
>
> I''m just after clarification regarding how plugins can be managed
> (updated, frozen etc).  Like:
>
> a) Once installed what are the options for updating a plugin?
>
> b) Are there global "update" methods available that may update
ALL
> plugins, or all items in the vendor directory ( e.g. rails) available?
>
> c) If there are "update all/multiple" plugins facilities, is
there
> a means of "freezing" some plugins so they won''t be
automatically
> updated?
>
> d) Following on from c) if one was to make changes to a plugin what  
> is the recommended approach for ensuring (i) an update can''t be  
> kicked off which overwrites the changes and/or (ii) the changes  
> could be merged in?
>
> Thanks
> Greg
>
> >

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---