Oops, forgot an important point,
On 4/5/2011 7:53 PM, Loren Segal wrote:
2. If extra bloat to gem package size is an issue with #1, perhaps
we can give gem authors the ability to package these documentation
files separately from the gem itself and push the documentation
package independently of the gem (gem push_docs …).
I'm not fond of this as newer versions of rdoc (or yard) may fix bugs
or add useful features that will Just Work on existing sources.
I should add: having a push_docs feature would (could?) allow
maintainers to re-push docs for an existing version-- in other words
they could retroactively push docs for version X.Y.Z. So if new versions
of RDoc (or YARD) start to look better and/or fix bugs, they could
re-generate and re-push the docs for that version. Optionally, they
could remove the docs if they're stale, letting the client side
generation kick in-- and of course, users could be allowed to override
doc fetching and let the client side do its thing instead
(--no-fetch-doc or something?)
- Loren
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
