Do others think I should add the Module::Build recipe as well?

Thankfully, many modules that were originally built to use Module::Build, also provide a Makefile.PL. (One of those modules is Module::Build itself.)
I suppose there are still some modules that don't provide a Makefile.PL.

I guess the responsible thing to do would be to specify that the Module::Build mantra be used in those rare instances that a Makefile.PL is not provided.

I, however, would be tempted to provide a far more irresponsible (tongue-in-cheek) handling:

"If a Makefile.PL has not been provided then the module is not worth installing";
or (slightly less offensive):
"If a Makefile.PL has not been provided, file a bug report".

The former is, of course, not necessarily true - and the latter is probably little other than arrogant.
By way of explanation, I have always found Module::Build to be intensely annoying, and I try to avoid making any statements that might infer that the use (or even the mere existence) of that build process is valid or useful.

Cheers,
Rob

In reply to Re^2: RFC: A guide to installing modules for Win32 (2022 Edition) by syphilis
in thread RFC: A guide to installing modules for Win32 (2022 Edition) by pryrt

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.