On Sat, Mar 8, 2008 at 1:52 AM, Trans <[EMAIL PROTECTED]> wrote: > On Mar 8, 1:20 am, Trans <[EMAIL PROTECTED]> wrote: > > I know the immediate reaction this is likely to get --half of which is > > probably just b/c it is coming from me. But putting these gut- > > reactions aside, consider it objectively. It makes sense... > > > > RubyGems should not be generating rdocs. > > > > As good an example as any for when convention ought to triumph over > > configuration, this is it. As it stands we currently must fill out > > gemspec options: has_rdoc, rdoc_options and extra_rdoc_files, to get > > rdocs generated on install, but that's still not enough to get them > > right. For starters, --main README's are missing across the board.
Instead of preventing rdoc generation, RubyGems should make it easier to generate docs in a straightforward, standard way. Specifically, it should provide some accessors that correspond to common RDoc command-line options (e.g., main page, title, etc.) that make for better documentation results. Then, hoe and similar tools should generate gemspecs that use these accessors. The situation could definitely use some improvement. -austin -- Austin Ziegler * [EMAIL PROTECTED] * http://www.halostatue.ca/ * [EMAIL PROTECTED] * http://www.halostatue.ca/feed/ * [EMAIL PROTECTED] _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
