in reply to Re^6: Making the CPAN/GitHub updating process painless
in thread Making the CPAN/GitHub updating process painless

Even if it is rare for a Perl developer to develop under Windows, that statistic doesn't help me. I develop 90% of my CPAN modules on Windows, so Dist::Zilla not working or not intending to support Windows directly rules it out for me.

  • Comment on Re^7: Making the CPAN/GitHub updating process painless

Replies are listed 'Best First'.
Re^8: Making the CPAN/GitHub updating process painless
by 1nickt (Canon) on Dec 18, 2017 at 12:52 UTC

    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.