On Jul 5, 2011, at 4:29 PM, Aaron Patterson wrote: > Eric proposed a workaround of always shipping an empty directory, but I don't > think that is a good long term solution. It requires that gem packagers > to know that rdoc behaves in a certain way when provided with a > directory that doesn't exist, and to ship an empty directory to avoid > that warning. > > Instead, I would rather see this validation removed so that I can > specify an empty list of require paths and avoid this warning. > > I've put together a patch, but I'm not sure that it's complete. Without > applying the patch, I get errors running 1.8.7. The errors and failures > do not seem to increase after applying my patch, but I cannot be sure > I've not broken something. > > https://gist.github.com/1065473
I think the lack of a require path should be a warning instead of an error. Most people won't want to use this feature. I don't think the errors are your fault. _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
