Hmmm…you’re right…this doesn’t look like a true Ruby file, although
it’ll be difficult to filter it out because of it’s .rb extension.
How does the Rakefile know what to scan and what not? I guess that’ll be
my next area of research. Would it be easier to modify gem itself to do
this task? Perhaps this should be a candidate for inclusion as an option
Apparently, someone had already thought of doing this and didn’t, as
evidenced by the following lines in rubygems/doc_manager.rb:
#TODO: Why is this throwing an error?
#ri = RDoc::RDoc.new
#ri.document([’-R’] + source_dirs)
Anyway, I was successful…I’ll look at making this more integrated and
submitting as a patch, but for the quick hack all it took was changing
the following line (58 in my version):
r.document([’–quiet’, ‘–op’, rdoc_dir] + @rdoc_args.flatten +
r.document([’–quiet’, ‘–op’, ‘–merge’, ‘-r’, ‘–ri-system’, rdoc_dir]
@rdoc_args.flatten + source_dirs)
It worked perfectly…all Rails classes, etc, are now in ri.