Thanks for this (RFC) tutorial, such a thing has been missed for some time now. While there is no One True Way to build a CPAN distribution, the described way is a good one.
. If the third component is preceded by '_', CPAN counts the upload as a development release. It will be available for testing but not as a published download.
More precisely, CPAN clients (such as CPAN.pm, CPANPLUS and cpanminus) are encouraged not to install development releases by default. That and the big red marker on the search.cpan.org page seem to be the only real difference between development and "production" releases.
Regarding the alternatives, maybe Dist::Zilla is worth mentioning - it automates much of the module maintenance, including CPAN uploads.
For Debian packages the dh-make-perl tool can also help creating .debs from CPAN modules.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||