Since Adam Kennedy is busy with $real_life, I'll say what he might have
said.
Jonathan Rockway wrote:
I see two resolutions to this problem:
1) Module authors need to re-release their modules whenever
Module::Install is updated.
This is the philosophy of M::I. Authors (i.e. experienced developers)
are inconvenienced in preference to users when things are broken and
don't work well together. The M::I philosophy is that users shouldn't
have to worry about what versions of CPAN, CPANPLUS, EU::MM, or M::B
they have. That does make life tougher for "lazy" authors who want to
fire and forget.
But then, you aren't forced to use it, either. Don't use M::I if you
just want declarative syntax for a Makefile.PL and aren't willing to
monitor M::I and re-release.
2) Get M::I into the core of perl, so that everyone has a known-good
tested-everywhere version.
This is the best idea. CPAN works so well because everyone has it and
it's a good piece of software (lately CPANPLUS has gotten rather buggy
and I've gone back to regular CPAN!).
First, M::I isn't anywhere near ready. Second, the point is for it to
be able to be upgraded more frequently than core Perl as issues are
discovered. Many of the issues that module users have are that all they
have is some old version of core Perl with out-of-date CPAN.pm and
EU::MM that are buggy. And they're stuck. That's what M::I is trying
to solve.
Regards,
David Golden
