[Module-build-general] documenting ./Build docs

[Mark S. <ma...@su...>]

Hello,

Today I looked into seeing what the "docs" action does. When I ran it,
the output looks identical to just running "./Build". 

So I looked at the code. It looks like they are in fact doing the exact
same thing. If you don't specify an action, "build" is the default. 
"build" calls the "code" action, and then "docs" action.

If you call the "docs" action directly, it depends on the "code" action, 
so again the "code" ation gets called, followed by the "docs" action.

So it doesn't seem an incredibly useful action at the moment.
:). It would seem more useful if you could build the docs without
depending on the code being built, but I'm not sure if that will make
sense from a technical perspective.

At any rate, the docs could say something like:

docs

Builds all the man pages for the binary and library POD.
This action depends on the code being built, and will call the
'code' action if it hasn't already run. By default this action
gives the exact seems results as simply running "./Build".

	Mark

-- 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . 
   Mark Stosberg            Principal Developer  
   ma...@su...     Summersault, LLC     
   765-939-9301 ext 202     database driven websites
 . . . . . http://www.summersault.com/ . . . . . . . .