As shown in one of my example CPAN Makefile.PL, I use Pod::Simple::Select to extract sections of my POD to put into the README.md and LICENSE files (so I can use my POD for the single-source for those, rather than separately maintaining them.

# auto-generate the README from the lib/Win32/Mechanize/NotepadPlusPlu
+s.pm
README.md :: lib/Win32/Mechanize/NotepadPlusPlus.pm Makefile.PL
    $(PERL) -MPod::Simple::Select -e 'my $$p = Pod::Simple::Select->ne
+w();$$p->output_file(qq(README.pod));$$p->select({head1 => [qq(NAME),
+qq(SYNOPSIS),qq(DESCRIPTION),qq(LIMITATIONS),qq(INSTALLATION),qq(TODO
+),qq(AUTHOR),qq(COPYRIGHT),qq(LICENSE)]});$$p->parse_file(qq(lib/Win3
+2/Mechanize/NotepadPlusPlus.pm));'
    pod2markdown README.pod README.md
    $(RM_F) README.pod
# auto-generate the LICENSE file from the lib/Win32/Mechanize/NotepadP
+lusPlus.pm
LICENSE :: lib/Win32/Mechanize/NotepadPlusPlus.pm Makefile.PL
    $(PERL) -MPod::Simple::Select -e 'my $$p = Pod::Simple::Select->ne
+w();$$p->output_file(qq(LICENSE.pod));$$p->select({head1 => [qw/AUTHO
+R COPYRIGHT LICENSE/]});$$p->parse_file(qq(lib/Win32/Mechanize/Notepa
+dPlusPlus.pm));'
    pod2text LICENSE.pod LICENSE
    $(RM_F) LICENSE.pod

[download]

The VERSION weirdity appears to be that the author didn't put the newline after =for comment, which made the POD paragraphs not be what they thought it was.

That author doesn't seem to have updated any of their repositories in the last couple of years, but that doesn't necessarily mean that it's abandonware (though it makes it more likely). The only open issue is about the minimum required Tie::File version, which isn't a super-critical issue. And, as of yet, with my example usage above, I haven't had any difficulty in using the distribution as published for v0.002. (The number in a version number is just that -- a number. Being low doesn't indicate that it's not usable; many authors just start at 0.001 or 0.01 instead of 1.00. It's just a personal preference on where to start.)

In reply to Re: Is Pod::Simple::Select a recommended replacement for Pod::Select? Or is there a better choice? by pryrt
in thread Is Pod::Simple::Select a recommended replacement for Pod::Select? Or is there a better choice? by Darkwing

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.