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.
"lazy" is a really bad word here. We're ALL lazy. I use Module::Install
_because_ I'm lazy. I'm too lazy to write detailed complex EU::MM or M:B
installers, and I wan't something that is extremely compact, easy to
read, and quick to write.
The current problem is just that because authors haven't been
discriminated against before when it comes to installers, there's not a
lot of programatic support there for assisting authors.
It really just means we need to write more code to automate the
authorship process more.
I have a spindly prototypical Module::Inspector sitting in SVN which I'm
hoping to use as the basis of a module auto-increment script, which
could then be enhanced to take someone ELSE'S tarball, munge it to do
the auto-increment, and then spit out a tarball of the replacement.
So it's rough on authors for now, but it will get better as the
authorship tools get smarter.
Adam K
