I think it's great for the users, if you are willing to do it, but be careful because if someone complains about installation problems you'll have an extra variable to consider ("did you use Makefile.PL, or Build.PL?").

Perhaps something that you can do is use a templating system to generate both Makefile.PL and Build.PL from a common source so that you only have to change things once. :)

Update: After looking at things in more detail, I see that perhaps you don't need to use templates at all. Module::CoreList autogenerated its Makefile.PL by using Module::Build::Compat with the create_makefile_pl => 'traditional' option in Build.PL.

In reply to Re: Makefile.PL and Build.PL by itub
in thread Makefile.PL and Build.PL by dragonchild

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.