Can we fault the author of the Acme:: module for using Module::Build and following the recommended usage of that module?
Yes, we can fault the author of the Acme:: module for doing exactly that.

We can also fault the author of Module::Build for making that recommendation (personally I do, and will send email to that effect), but the fact that the author of a module that you are using makes a recommendation does not mean that you shouldn't exercise your best judgement about whether to follow that recommendation.

And the fact is that until the installed base of Perl programmers mostly has Module::Build, and is using a version of CPAN that supports it, a nod to backwards compatibility makes sense. And that will take years to happen. The fact is that people don't upgrade things like CPAN nearly as often as those who like shiny new toys want to believe. And certainly not as often as the creators of those toys would wish.

About whether Randal's message was appropriate. I think that he should not have quoted private emails in a public forum without better cause. However I also think it appropriate to post to meditations things that are intended to spark discussions that are relevant to the community. Which this did. Therefore I agree with having the post, but wish that he had not quoted private email in the post.

An incidental note about Randal. Love him or hate him, one of the things that he does do well is keep track of everything on CPAN, and popularizes modules that he thinks are useful. Quality review is a thankless job that CPAN needs more of, not less. And doing things like pointing out that modules won't install - even joke modules - is part of that quality review. (My view is that a joke poorly executed is a poor joke, unless the poor execution is the point of the joke. Writing a module that doesn't readily install through standard systems is poor execution.)

A side note. I recommended it once already in this discussion, but another recommend is justified. If you want to understand better why quality review of CPAN is something that people will perpetually say we need more of but not generally provide, I can would recommend The Logic of Collective Action.

In reply to Re: Re: Re: Re: Acme::Lingua::Pirate::Perl author needs encouragement to add Makefile.PL by tilly
in thread Acme::Lingua::Pirate::Perl author needs encouragement to add Makefile.PL by merlyn

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.