On Nov 15, 2010, at 17:59, Eric Hodel wrote: > I think we need at least the following hooks: > > 1) Before install, after download, "pre-install". I'm not sure what this > would be used for. The hook should be able to abort the install.
I have modified pre-install to abort the install only if false (not nil) is returned. > 2) After files have been written and extensions have been built but before > executable stubs have been written or specification is written, "post-build". > This would be used for test tasks. The hook should be able to abort the > install, cleaning up the unpacked files and built extensions. I have implemented post-build hooks that abort the install only if false (not nil) is returned. > 3) After executable stubs and specification has been written, "post-install". > This could be used for documentation generation. Gem::DocManager should be > rewritten to use this hook. The hook should not be able to abort the install. post-install hooks work as-is. > For each hook both the installer and the gemspec from the .gem file should be > provided to the callback. Per Jon's comments, a install hook user can retrieve the spec from the installer. _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
