You can catch errors of the type you mention by doing

$ make disttest
before you upload -- or
$ ./Build disttest
as the case may be. This makes your tarball if needed, and then unpacks it again into a subdirectory and runs your tests. I do this routinely before releasing, and occasionally catch MANIFEST omissions.

Editorial comments: Perl's testing culture is one of the things that makes me enthusiastic about the language. Any other language could do this, but no other that I know of does so. All hail CPAN testers.

What we do not have (I think -- I would love to be shown that I am in error) is a complete how-to on publishing a module. There are pieces/parts various places: the CPAN FAQ has the basics, the Perl foundation has recommended licensing, PAUSE has something on naming modules, CPANTS (not to be confused with CPAN Testers) recommends and tests for ways to structure modules, but nothing I know of ties it all together in a place where the budding module author is bound to find it.


In reply to Re: CPAN module versioning for slight changes by Anonymous Monk
in thread CPAN module versioning for slight changes by jdv

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.