I can't see how that would be the case. At least I've never encountered it. I agree that some implementations can make some things difficult or impossible: you can't read the Pod in a module using perldoc if dzil hasn't built the distro, for example (I don't use Pod::Weaver's "magical" features for that reason). However, I have never encountered a situation where writing or running tests was affected. The tests should be able to use the library irrespective of the condition of Pod or the inclusion of dzil-specific directives. While you can run tests with dzil test you can equally just use prove.

I am not sure whether Dist::Zilla runs or passes its tests on Windows. I would say it's quite rare in general for a CPAN author to develop on Windows, and the fact of the matter is that Dist::Zilla has become the de facto standard for releasing to CPAN. This is simply because once you spend the time to learn it, it saves you hours of time and aggravation when updating a distribution. I urge anyone who contributes original or patched content to CPAN to bite the bullet and spend half a day getting up to speed. You'll be glad you did!


The way forward always starts with a minimal test.

In reply to Re^6: Making the CPAN/GitHub updating process painless by 1nickt
in thread Making the CPAN/GitHub updating process painless by nysus

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.