On Dec 1, 4:25 pm, Chad Woolley <thewoolley...@gmail.com> wrote:
> On Wed, Dec 1, 2010 at 1:19 PM, Trans <transf...@gmail.com> wrote:
> > The other option is to just present an error page saying why
> > the rdocs could not be generated and what can be done about it.
>
> If they need sudo access to install the rdoc, won't they also need it
> to install the gem files?  And doesn't that just fail now with a write
> permission error?  Why can't rdoc behave the same way, or is there
> something else to consider?

Yes, I think you are right. So, I made a nice error page that
explains.

I just made a pull request for the patch. If you want to try it out,
gem install some package with the --no-rdoc option, clone my repo
(trans/rubygems) and run `ruby -Ilib bin/gem server`, find the gem and
click on the rdoc link.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers

Reply via email to