On Friday 27 November 2009 11:17:08 Josef Reidinger wrote:

If we found security issue and want update that plugin. Is possible to release update just for this plugin instead of all projects which uses it?

Yes it's possible. Go to the plugin repo, fix the code and push the changes. According to your svn/git configuration the updates will be automatically picked up inside the rails app when you update your code. BTW, are you using git or svn? Another question: why don't you package this plugin? This is the approach we use most of the times with SUSE Studio. Cheers Flavio -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ruby+help@opensuse.org

Marcus Rueckert write:

On 2009-11-27 09:34:13 +0100, Josef Reidinger wrote:

...

nowadays, we share gems between our application. Is possible to share rails plugins? I know at least about one ( maybe two if we use smartly rest-auth) which is packed in vendor/plugins/ of two projects. Is there any way how we could package plugin and use it from all project (so we could fix problem in one place?)

package the plugins as a gem e.g. i added packages for will_paginate and other plugins recently in dlre. that way you can also specify requirements for specific versions of a plugin.

darix

Yeah, thanks that is what I need. I think that plugins cannot be packed as gems. Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ruby+help@opensuse.org

Hi Josef, On 27.Nov, 2009, at 13:49 , Marcus Rueckert wrote:

On 2009-11-27 12:55:48 +0100, Josef Reidinger wrote:

...

Yeah, thanks that is what I need. I think that plugins cannot be packed as gems. you think wrong. plugins can be packaged as gem very nicely zypper in rubygem-will_paginate

yes, plugins can be packaged (and loaded) as Rubygems. In fact, it's the preffered way to package Rails plugins as gems ("plugems") -- see "high-profile" ones as http://github.com/thoughtbot/clearance, http://github.com/mislav/will_paginate . It has several great advantages, as this: * enables you to use the code outside of Rails' context (Sinatra application, generic Ruby, etc) * allows you much cleaner dependencies declaration (`config.gem` in environment.rb|test.rb, etc) * makes possible to work with different versions of the "plugem" in a clean way * makes release management, versioning, etc really easy [see eg. http://github.com/technicalpickles/jeweler ] * allows clean dependency loading, see eg. the Bundler post from Yehuda Katz [http://yehudakatz.com/2009/11/03/using-the-new-gem-bundler-today/ ] In the case of WebYaST, I have adviced to convert all the plugins to Rubygems, precisely for this purpose, as you may remember. It would enable to get rid of messing with load paths to enable plugins elsewhere than in `vendor/plugins`, and generally would be *much* easier for vendors/users to build & load in their own code. Karel -- www.karmi.cz -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ruby+help@opensuse.org