[Rubygems-developers] WARNINGS

Eric Hodel drbrain at segment7.net
Thu Jan 31 18:50:18 EST 2008

On Jan 31, 2008, at 14:56 PM, Trans wrote:
> On Jan 31, 2008 5:23 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> On Jan 30, 2008, at 13:10 PM, Trans wrote:
>>> On Jan 30, 12:48 pm, "Luis Lavena" <luislav... at gmail.com> wrote:
>>>> On Jan 30, 2008 3:43 PM, Trans <transf... at gmail.com> wrote:
>>>>> Why is Rubygems now issuing warnings when building, eg.
>>>>> WARNING:  no rubyforge_project specified
>>>>> WARNING:  RDoc will not be generated (has_rdoc == false)
>>>>> I've never seen it do this before. How to I silence it? (Using  
>>>>> ruby,
>>>>> not command line).
>>>> These warnings where introduced due bad gem specifications.
>>>> Setting the correct values in the gem specification will silent
>>>> these warnings.
>>> That's not so. The has_rdoc is set to false for a reason.
>> Then you're a bad person.
> I'm a bad person? Eric do your ever listen to the things you say?

Yes, and you take things too seriously.

> The reason I don't have rdocs generated for one of my projects is
> becuase it has special requirements for the docs.

Then you'll have to live with the warnings, or fix the special  

>> Not generating RDoc/ri is hostile to your users.
> If this is what you think why is is even an option?

Backwards compatibility.

More information about the Rubygems-developers mailing list