On 4/12/2011 3:20 PM, Loren Segal wrote:
Again, I'd really opt for the extra docs package, I think it's the
way to go and solves more of the problems than post install hooks.
That said, I think your solution should be implemented as well, and
should be the fallback. ie. RubyGems should look for a static docs
packaged-- but if not present, we can use the great post install
hook idea with --document, etc.
I recommend implementing static documentation as a plugin to
rubygems. If it becomes a proven solution it can be merged in.
Thanks, I will look into using the new post install hooks then.
In this case, is there a way to disable another "post install hook"
from running? For instance, if a static documentation plugin ran, we
would want to disable RDoc/RI from generating. Is this feasible with
the APIs, or do we have to resort to unsupported monkeypatching again?
Is there any followup on this? It would be fairly important to have this
kind of functionality in order to add proper YARD support, and/or
generalized support for "skipping" the doc generation process and
downloading static doc tarballs via a plugin.
Perhaps RDoc/RI themselves should be installing post install hooks like
everybody else. That way, at least they could be unregistered by other
plugins.
I'm not sure if API is still being developed; if so, it would be nice to
have this scenario as a consideration (if it isn't already being
considered).
- Loren
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
