[Module-build-checkins] Module-Build/lib/Module Build.pm,1.184,1.185

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

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

Modified Files:
	Build.pm 
Log Message:
More fixes for splitting html install path up into binhtml & libhtml entries to parallel manpages and to match newer Config.pm entries.

Index: Build.pm
===================================================================
RCS file: /cvsroot/module-build/Module-Build/lib/Module/Build.pm,v
retrieving revision 1.184
retrieving revision 1.185
diff -u -d -r1.184 -r1.185
--- Build.pm	20 Jun 2005 18:11:09 -0000	1.184
+++ Build.pm	4 Aug 2005 03:13:05 -0000	1.185
@@ -306,10 +306,13 @@
 
 =item docs
 
-This will generate documentation (ie: Unix man pages) for any binary and
-library files under B<blib/> that contain POD.  If there are no C<bindoc> or
-C<libdoc> installation targets defined (as will be the case on systems that
-don't support Unix manpages) this action does nothing.
+This will generate documentation (ie: Unix man pages and html
+documents) for any binary and library files under B<blib/> that
+contain POD.  If there are no C<bindoc> or C<libdoc> installation
+targets defined (as will be the case on systems that don't support
+Unix manpages) no action is taken for manpages. If there are no
+C<binhtml> or C<libhtml> installation targets defined no action is
+taken for html documents.
 
 =item fakeinstall
 
@@ -561,17 +564,25 @@
 something.  Pretty rare to see this in a perl distribution, but it
 happens.
 
+=item bindoc
+
+Documentation for the stuff in C<script> and C<bin>.  Usually
+generated from the POD in those files.  Under Unix, these are manual
+pages belonging to the 'man1' category.
+
 =item libdoc
 
 Documentation for the stuff in C<lib> and C<arch>.  This is usually
 generated from the POD in F<.pm> files.  Under Unix, these are manual
 pages belonging to the 'man3' category.
 
-=item bindoc
+=item binhtml
 
-Documentation for the stuff in C<script> and C<bin>.  Usually
-generated from the POD in those files.  Under Unix, these are manual
-pages belonging to the 'man1' category.
+This is the same as C<bindoc> above, but applies to html documents.
+
+=item libhtml
+
+This is the same as C<bindoc> above, but applies to html documents.
 
 =back
 
@@ -596,8 +607,13 @@
  arch    => installarchlib  installsitearch     installvendorarch
  script  => installscript   installsitebin      installvendorbin
  bin     => installbin      installsitebin      installvendorbin
- libdoc  => installman3dir  installsiteman3dir  installvendorman3dir
  bindoc  => installman1dir  installsiteman1dir  installvendorman1dir
+ libdoc  => installman3dir  installsiteman3dir  installvendorman3dir
+ binhtml => installhtml1dir installsitehtml1dir installvendorhtml1dir [*]
+ libhtml => installhtml3dir installsitehtml3dir installvendorhtml3dir [*]
+
+ * Under some OS (eg. MSWin32) the destination for html documents is
+   determined by the C<Config.pm> entry C<installhtmldir>.
 
 The default value of C<installdirs> is "site".  If you're creating
 vendor distributions of module packages, you may want to do something
@@ -652,6 +668,8 @@
  bin     => /home/ken/bin
  bindoc  => /home/ken/man/man1
  libdoc  => /home/ken/man/man3
+ binhtml => /home/ken/html
+ libhtml => /home/ken/html
 
 Note that this is I<different> from how MakeMaker's C<PREFIX>
 parameter works.  Module::Build doesn't support MakeMaker's C<PREFIX>