Module::Release' release will support wildcards when you have multiple versions of perl to test against. This is very useful when you have threaded and unthreaded perls, 64bitall and/or 64bitint and/or longdouble supported perl releases installed. I have now 111 versions of perl available on my external disk ranging from 5.003_07 to 5.17.0. Picking the versions that ought to be supported by your module could be something like this:

$ cat .releaserc
cpan_user HMBRAND
automated_testing 1
skip_kwalitee 1
skip_manifest 1
skip_prereqs 1
allow_glob_in_perls 1
perls /pro/bin/perl:/pro/bin/perl5.00504:/usr/bin/perl:/media/Tux/perl
+s/bin/perl5.6.2:/media/Tux/perls/bin/perl5.8.*:/media/Tux/perls/bin/p
+erl5.1[024567]*:/media/Tux/perls/bin/tperl5.6.2:/media/Tux/perls/bin/
+tperl5.8.*:/media/Tux/perls/bin/tperl5.1[024567]*
$

[download]

I explicitely disable the quality checks for release as most of the modules that are needed for those are only installed in my "normal" perl and not in the test set so release would fail. I run the quality tests using Module::CPANTS::Kwalitee's cpants_lint.pl after release is done.

My Makefile.PL contains a special target "tgzdist", which checks spelling, dependency versions, minimal (declared) perl version and more:

Text-CSV_XS $ make tgzdist
pod-spell-check --aspell --ispell
    ok 1 - CSV_XS.pm
    ok 2 - sandbox/genMETA.pm
    ok 3 - sandbox/i-ttt/lib/i/ttt.pm
    1..3
ok 1 - CommonMistakes
    ok 1 - CSV_XS.pm
    ok 2 - sandbox/genMETA.pm
    ok 3 - sandbox/i-ttt/lib/i/ttt.pm
    1..3
ok 2 - Spell-check with aspell
    ok 1 - CSV_XS.pm
    ok 2 - sandbox/genMETA.pm
    ok 3 - sandbox/i-ttt/lib/i/ttt.pm
    1..3
ok 3 - Spell-check with ispell
1..3
perl sandbox/genPPPort_h.pl
ppport.h updated to 3.20
perl sandbox/genMETA.pl -c
Checking generated YAML ...
Checking for Text::CSV_XS-0.89
Check if ChangeLog and README are still valid UTF8 ...
Check required and recommended module versions ...
Check distribution module versions ...
Checking if 5.006 is still OK as minimal version for examples
    1..5
    ok 1 - examples/parser-xs.pl
    ok 2 - examples/speed.pl
    ok 3 - examples/csv2xls
    ok 4 - examples/csvdiff
    ok 5 - examples/csv-check
ok 1 - Minimum perl version 5.006
:
:
gzip --best Text-CSV_XS-0.89.tar
/pro/bin/perl "-MExtUtils::Manifest=fullcheck" -e fullcheck
Not in MANIFEST: MYMETA.json
Checked dist            Text-CSV_XS-0.89.tgz
Kwalitee rating         133.33% (32/24)
Ignoring metrics        is_prereq, prereq_matches_use, build_prereq_ma
+tches_use

[download]

Enjoy, Have FUN! H.Merijn

In reply to Re^2: My Perl Module Toolchain by Tux
in thread My Perl Module Toolchain by tobyink

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.