I find it not very much in the style of sensible defaults not to include a Makefile.PL. To recommend such a "solution" in the face of the fact that older versions "propably have problems installing your module" defies the use of a module to handle the installation. If I wanted to create problems during installation, I would write the Makefile myself. If I give up installation to a module, I expect that the module tries its best to work in all situations. ExtUtils::MakeMaker works in all situations, while Module::Build doesn't unless I make special provisions, like including a passthrough Makefile.PL for compatibility.

Why can it be a design decision to make it easier for people to create broken distributions that won't install using CPAN by default?

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.