From: Eric Hodel <drbrain@...7.net>
Date: 2008-04-11T06:58:17+09:00
Subject: Re: gem build documentation for new gems?

On Apr 7, 2008, at 06:33 AM, Gerardo Santana Gómez Garrido wrote:
> On 4/6/08, Phillip Gawlowski <cmdjackryan@googlemail.com> wrote:
>> Gerardo Santana Gómez Garrido wrote:
>> |
>> | And it should be documented.
>> |
>> |
>> | This is outdated:
>> | http://docs.rubygems.org/read/chapter/20#page85
>> |
>> | Look at platform:
>> | http://docs.rubygems.org/read/chapter/20#platform
>> |
>> | it's even given me an example with Gem::Platform::Win32
>> Bitter? Me? Never...
>
> Hahahaha
>
> Yeah, there are some people like that writing open source software.
> Fortunately it doesn't happen everywhere. OpenBSD for example, they do
> not add any feature if it is not documented.
>
> I have checked the page again, it was generated in 2005. This is
> unacceptable. Being gratis or open source is not an excuse.


I'm sorry that I chose to devote my free time to something other than  
updating an old page with proper documentation, but thank you for  
volunteering to update the documentation for me.

I believe Jim Weirich currently is hosting and originally generated  
this documentation, so you'll need to contact him to regenerate or  
replace it with correct documentation.

However, I think the best place to document `gem build` is at `gem  
help build` which will save you lots of time, as I can quickly check  
in a documentation patch.  The file you want to look at is lib/ 
rubygems/commands/build_command.rb.  You can find the repository on  
the RubyGems project at RubyForge.