comment on

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.

Perl 6 - second systems done right

In reply to Re: RFC: How to Release Modules on CPAN in 2011 by moritz
in thread RFC: How to Release Modules on CPAN in 2011 by ELISHEVA

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks