I believe that the problem arises on ActivePerl's side, as both PPM::Make and Module::Build appear to use the module name as the title in these cases, instead of the path to the local file. You can see this by doing 

   perl Makefile.PL
   nmake

[download]
and noticing the nmake step generates already the html files. Amongst other things, this will insert ActivePerl-specific stuff like links to JavaScript scripts used in the local ActivePerl html docs, but will also have the problem with the path to the local file being used as the title. If you then run PPM::Make's make_ppm on this, the script will see a blib/html directory present, and will not regenerate the html docs.

If you want to not use the html docs generated by ActivePerl, using PPM::Make, you can do 

   perl Makefile.PL
   nmake
   deltree blib\html
   make_ppm

[download]
which will generate the html files using PPM::Make and leads to, for example, a title of Perl::Critic::Policy::BuiltinFunctions::ProhibitLvalueSubstr, rather than the path to the local file that results using ActivePerl's html generation. If you're using Module-Build, this problem can be avoided by using 
  perl Build.PL
  perl Build

[download]
directly, instead of some Makefile.PL compatibility mode, as this will use Module::Build directly to generate the html docs. However, not using ActivePerl's generated docs will lose the JavaScript functionality that ActivePerl provides.

Unfortunately, after all this, even if you fix these problems before you make up the ppm package, if you're installing this on a recent ActivePerl, the ppm utility won't install the docs present under blib/html, but instead will generate the html docs directly from the module files. This results in these cases in the path to the local file being used in the title.

It's probably worth filing a bug report with ActiveState about this.

In reply to Re: Question about creating PPM's... by randyk
in thread Question about creating PPM's... by CSJewell

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.