Even if I know most about testing and I know about prove and yath, my usual start is always the same:

  1. Get the dist
    git clone / cpan + get / get the tgz
  2. Prepare
    $ cd Module-dir
    $ perl Makefile.PL

    If it complains about no Makefile.PL, curse loudly, check if there is a Build.PL

    $ perl Build.PL

    If there is no Build.PL either, curse even louder and ask myself the question if applying my patch is worth the trouble. If not, just give up.

  3. Test
    $ make test

    If it complains about missing Makefile, curse again and try Build.PL

    $ perl Build test

    If I really cared enough, and installed enough of dzil

    $ dzil test

    If that still complains about yet another missing plugin, give up and remove the dist dir: My time is valuable too.

  4. Hack
    If this module now passes all tests, check if my change still applies. (It might have been fixed in the git repo already). Otherwise, make the change, make a test case, update ChangeLog (or any other legal name) and submit a PR.

Even as a seasoned perl programmer with enough knowledge to get the ball rolling, I see plenty of decision points where I would decide to leave the annoyance/bug to what it is and maybe just add an issue, which in most cases is much easier than going through the installation of dependencies I won't need for anything but this single module.


Enjoy, Have FUN! H.Merijn

In reply to Re^8: What do I use to release a module to CPAN for the first time? by Tux
in thread What do I use to release a module to CPAN for the first time? by Lady_Aleena

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.