See the old Module::Build::Compat. Scan for Scenarios, and read what his preferred Scenario was. (Do not use Module::Build::Compat. Include instructions in the README telling people to download and install Module::Build by hand.)

The text said:

Just include a Build.PL script (without a Makefile.PL script), and give installation directions in a README or INSTALL document explaining how to install the module. In particular, explain that the user must install Module::Build before installing your module. I prefer this method, mainly because I believe that the woes and hardships of doing this are far less significant than most people would have you believe. It's also the simplest method, which is nice. But anyone with an older version of CPAN or CPANPLUS on their system will probably have problems installing your module with it.

For me there is a very big difference between "I prefer"/"I believe" and "The preferred method is"/"you should", and he also mentions the major downside. I don't see the problem with somebody expressing a preference. I don't agree with it either - but I didn't see it as a diktat.

To the best of my knowledge, Ken has never released a CPAN module with this setting.

That was the official last word for years. And remained that way through many rounds of complaints.

The first report I'm aware of was 19 Sep 2003. Ken agreed to tweak the text on 20 May 2004. Eight months isn't "years".

I'm not sure what changed his mind in the end, but I doubt that it was me.

I think it might have been me :-)

And until I see something to convince me that he really has changed, my impression of Ken will remain strongly flavoured by this episode.

Fair enough. I'll just raise a hand and say that my experiences have been very different, and I'll still go along with the opinions of the M::B developers I expressed last year.

In reply to Re^6: Why Module::Build? by adrianh
in thread Why Module::Build? by Ovid

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.