Thanks $code_or_die. The rudif link was the one I was after. In the meantime I got an attack of RTFS and whipped up the script below anyway. It is very simple to use. Just install it in you path somewhere like C:\Perl\bin for instance and call it something like intstalldoc.bat Then after you have done the usual you just call it: 

C:\>perl makefile.PL
C:\>nmake
C:\>nmake test
C:\>nmake install
C:\>installdoc

It reads the Makefile for the TO_INST_PM list of just installed modules, does the pod2html bit and rewrites the AS documentation TOC. If also forces overwrites of existing HTML documentation. The stuff at the start is the standard batch file wrapper so you can just call the script with a one word name.

Update

Fixed bug when TO_INST_PM contains file with .pm.html extension. 

@rem = '--*-Perl-*--
@echo off
if "%OS%" == "Windows_NT" goto WinNT
perl -x -S "%0" %1 %2 %3 %4 %5 %6 %7 %8 %9
goto endofperl
:WinNT
perl -x -S "%0" %*
if NOT "%COMSPEC%" == "%SystemRoot%\system32\cmd.exe" goto endofperl
if %errorlevel% == 9009 echo You do not have Perl in your PATH.
if errorlevel 1 goto script_failed_so_exit_with_non_zero_val 2>nul
goto endofperl
@rem ';
#!/usr/bin/perl -w
use strict;
use ActivePerl::DocTools;
use Pod::Html;
my $makefile;
my $htmlbase = $ActivePerl::DocTools::TOC::dirbase;
$htmlbase =~ tr|\\|/|;
my ($dirbase) = $htmlbase =~ m|(.*)/html|;
open MF, './Makefile' or die "Can't open Makefile: $!\n";
{ local $/; $makefile = <MF>; }
close MF;
my ($files) = $makefile =~ m/TO_INST_PM = (.*?)PM_TO_BLIB/s;
$files =~ tr/\n\\//d;
for my $file ( split ' ', $files ) {
    my ($name) = $file =~ m/(.*)\.pm$/;
  next unless $name;
    print "Writing $htmlbase/$name.html\n";
    (my $winpath = "$htmlbase/site/$name.html" ) =~ tr|/|\\|;
    `attrib -r -a $winpath` if -e "$htmlbase/site/$name.html";
    pod2html(   "--infile=$dirbase/site/$file",
                "--header",
                "--htmlroot=$htmlbase",
                "--podroot=$dirbase",
                "--podpath=site/lib:lib", 
                "--css=$htmlbase/Active.css",
                "--outfile=$htmlbase/site/$name.html",
                "--quiet" );
}

ActivePerl::DocTools::WriteTOC();
__END__
:endofperl

[download]

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to Re: Re: ppm and autogeneration of documentation by tachyon
in thread ppm and autogeneration of documentation by tachyon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.