On Tue, Nov 25, 2008 at 20:59, Donald Ball <[EMAIL PROTECTED]> wrote:
> > I would guess the > thing to do would be to create a new gems task, gems:plugin:install or > similar, which would invoke the install scripts on all config.gems > that have been tagged with :plugin => true. I agree that there should be an install hook. Gem plugins are just plugins that have the benefits of rubygems. But it's not easy. Plugins had an interface for installing: "script/plugin install". Gems, on the other hand, can be installed in a variety of ways: from referencing them in environment.rb to freezing them in the application. But now, less and less people use "script/plugin" in favor of dependencies management tools. Same could be used for "freezing" gems (see recent discussions on this list). http://github.com/gary/dependency_management_talk/tree/master/notes.markdown This poses a question: how to trigger an install hook when you don't control the means of installation anymore? Maybe the 3rd party tools should follow the standard to execute install.rb when they see it. But how will they provide the same environment Rails did when it executes them in "script/plugin"? Another question is are installation hooks worth this trouble? All they do is show README on the console or copy assets to "public/". The former is just luxury, while the latter can easly be available through rake/thor tasks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
