Matt S Trout wrote:
> use inc::Module::Install;
I will say it again: Module::Install is the greatest threat to CPAN stability.
Module::Install bundles itself, but will not use a newer installed version.
[1] At some point something is going to happen which will break
Module::Install. A subtle perl upgrade bug, some new operating system quirk,
a dependency change, or more probably, MakeMaker will change something in its
guts and one of the many hacks MI does will no longer work.
At that point every dist which bundles MI will fail and we will have to wait
while every one of them releases an update. From experience, this is a very,
very slow process which will have repercussions for months and years after the
initial OMGUBROKECPAN event.
This breaks the "move to the latest version" way that CPAN normally defends
against this sort of problem. In addition, because each bundled copy of MI
might have been custom hacked by the author, a user can't even do a manual
upgrade.
That said, people choose based on convenience, not abstract, long term safety.
So it's for the best that Module::Build absorb every convenience feature from
MI.
[1] Yes, it does this for reasons.
--
You are wicked and wrong to have broken inside and peeked at the
implementation and then relied upon it.
-- tchrist in <[EMAIL PROTECTED]>
