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

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.