Hi Corion, for the record, "Dist::Zilla not working or not intending to support Windows" is not the case. I checked and found that at least one CPAN author of two or three dozen modules is using Windows and Dist::Zilla: Mithaldu, aka Christian Walde, who told me:

"The main advice I can give is: before releasing to cpan, grab the previous tarball, unpack it, put it in a git repo, add all, delete everything, make a build, unpack that into the git repo, and git diff. Reason being: sometimes you end up with tools applying OS newlines, which means the entire file changes if it was released on linux previously.

Also, some of the less attentively coded 3rd-party plugins (some of the git stuff) can refuse to test/work on windows.

dzil itself had some rough patches on certain systems due to not being aware of asynch file deletion on windows, but all of those things should be fixed via 1 second sleep loops now.

Also I note that, while v.5x appears to have had some Win32 test failures, the current distribution has 100% passing on Win32.


The way forward always starts with a minimal test.

In reply to Re^8: 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.