Jonathan Rockway schrieb:
1) Module authors need to re-release their modules whenever
Module::Install is updated.
This is the only viable solution. Anybody using Module::Install for
their modules should be aware of that. Of course, if the changes between
the Module::Install releases don't matter for your specific module, you
needn't re-release. (E.g. better XS support and a pure Perl module.)
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!).
This is out of the question. It would never be allowed to go into the core.
Module::Install has a very different philosophy from other build tools
(like Module::Build and ExtUtils::Makemaker): Only the module author
installs it. The users get the bundled version.
Actually now I see a third resolution: don't use M::I for CPAN modules.
CPAN (the software) handles dependency installing, it's standard with
perl, good enough. I do like M::I, I just can't think of why it's
really necessary for CPAN modules. (For non-CPAN perl packages, though,
it's a GREAT idea.)
IMHO, it's convenient.
Steffen
