I can't say for sure, but I'm guessing because Ken wants people to think about how they want to do this. The passthrough option seems to work reasonably well, but it is doing pretty funky stuff under the hood. The other methods that use a Makefile.PL also have their drawbacks, so it's really up to each developer to decide how they want to handle this.

As corion said, the problem here is that a module like M::B shouldnt make each developer decide how to handle this. It should simply default to the solution that breaks the least things and provide an opt out for power users. Breaking CPAN by default is just plain wrong, wrong, wrong.

Somebody else has created a Makefile.PL => Build.PL converter tat works for simple Makefile.PL scripts.

So wait, if I choose to convert to using Module::Build not only do I inconvenience all of my users who dont have Module::Build, I also lock out the ones who can't get it to work, and as an added bonus get to spend hours converting non trivial Makefile.Pl's over to Build.Pl framework? Gee sign me up.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi

In reply to Re^7: Module::Build and the PPM by demerphq
in thread Module::Build and the PPM by barbie

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.