Hi everyone! I'm writing my first ever Rails plugin, and I'm trying to figure out what the best way (in 2.3) to manage plugin dependencies is. Google doesn't seem to yield much that is applicable to my current situation, and the Rails docs themselves are quite weak in this area (or I'm looking at the wrong class).
Basically, the situation is this: I have some common model functionality dealing with street addresses that I abstracted into a couple of modules. I decided it was worth wrapping up those modules into an acts_as plugin (acts_as_addressed). One of the modules uses only core Rails features, and that was pretty easy to move into the plugin. The problem now is my other module, which uses some of the geocoding features provided by the YM4R plugin. So...in this case, what's the best way to specify that certain features of the acts_as_addressed plugin depend on the YM4R plugin? I'm hoping to release acts_as_addressed as a standalone plugin, and I'd like to enforce the dependency somehow so that my users don't get random NameErrors. Does Rails provide a mechanism for this? Is there some other way I should structure my plugin? Any ideas would be appreciated. Sorry if this is a stupid question -- I'm not really all that familiar with the Rails plugin system, beyond using plugins in my applications. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
