[Module-build-checkins] Module-Build/lib/Module Build.pm,1.189,1.190

[Randy W. S. <si...@us...>]

Update of /cvsroot/module-build/Module-Build/lib/Module
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8898/lib/Module

Modified Files:
	Build.pm 
Log Message:
Removed the gen_manpages, gen_html, install_manpages, install_html properties that were a failed attempt to provide user control of generation of documentation in favor of method introduced below.

Introduced two actions: html & manpages that will generate documentation for POD when the respective feature is enabled. The actions will generate the documents even if there is no set place to install to. However, if the actions are invoked as a dependency of another action (e.g. build), the documentation will only be built when there is a default place to install to.

Index: Build.pm
===================================================================
RCS file: /cvsroot/module-build/Module-Build/lib/Module/Build.pm,v
retrieving revision 1.189
retrieving revision 1.190
diff -u -d -r1.189 -r1.190
--- Build.pm	20 Oct 2005 16:45:19 -0000	1.189
+++ Build.pm	23 Oct 2005 02:18:15 -0000	1.190
@@ -94,6 +94,7 @@
 sub os_type { $OSTYPES{$^O} }
 
 1;
+
 __END__
 
 
@@ -330,12 +331,21 @@
 test>), the 'help' action will show you any POD documentation it can
 find for that action.
 
+=item html
+
+This will generate HTML documentation for any binary or library files
+under B<blib/> that contain POD. The HTML documentation will only be
+installed if the install paths can be determined from values in
+C<Config.pm>. You can also supply or override install paths by
+specifying there values on the command line with the C<binhtml> and
+C<libhtml> installation targets.
+
 =item install
 
 This action will use C<ExtUtils::Install> to install the files from
-C<blib/> into the system.  See L<How Installation Paths are Determined> for details
-about how Module::Build determines where to install things, and how to
-influence this process.
+C<blib/> into the system. See L<How Installation Paths are Determined>
+for details about how Module::Build determines where to install
+things, and how to influence this process.
 
 If you want the installation process to look around in C<@INC> for
 other versions of the stuff you're installing and try to delete it,
@@ -373,6 +383,15 @@
 See the L<distcheck> and L<skipcheck> actions if you want to find out
 what the C<manifest> action would do, without actually doing anything.
 
+=item manpages
+
+This will generate man pages for any binary or library files under
+B<blib/> that contain POD. The man pages will only be installed if the
+install paths can be determined from values in C<Config.pm>. You can
+also supply or override install paths by specifying there values on
+the command line with the C<bindoc> and C<libdoc> installation
+targets.
+
 =item ppd
 
 Build a PPD file for your distribution.