Tels wrote:
Moin,
On Friday 10 March 2006 12:26, Shlomi Fish wrote:
Hi all!
We had a discussion here about the pros and cons of using
Module::Install with "use inc::Module::Install" in the Makefile.PL, and
bundling it along. Well, now a showstopping bug happened in
Module::Install and several modules that included the affected version
suffered:
http://search.cpan.org/src/AUTRIJUS/Module-Install-0.59/Changes
http://rt.cpan.org/Public/Bug/Display.html?id=18020
http://rt.cpan.org/Public/Bug/Display.html?id=18090
Just a litte bit of information: Module::Install 0.58 worked on my system,
but didn't work on others. So the bug might not affect everyone - but it
is bad and makes me re-consider using Module::Install only when
necessary.
Actually, that it worked on your system was intended behaviour. The bug
that was introduced meant that installation failed only for authors
(that is, that had Module::Install installed on their local system) and
only if their installed version differed from the one bundled.
Yes, I fucked up. But it's hardly a "showstopper".
It only caused problems for authors. Although that was a little
unfortunate given that Catalyst users seem to now all be authors by
definition, it meant normal end-users shouldn't have been effected (I
think).
Module::Install was broken for less than a week, and only for authors.
Any author who upgrades to the just uploaded 0.60 will be fixed now.
As mentioned before, the design of Module::Install tends to favour the
end-user over authors, because authors are a small subset of all users
and are also more capable of locating and fixing problems.
I apologise for any inconvenience over the last week.
But I think this demonstrates the strength of the design of MI, rather
than is being a negative.
In the cases MI does have a major problem, it can be located fairly
quickly, fixed fairly quickly, and once fixed leaves minimal residue
around to bother us down the track. There's no back-compatibility issues
to deal with once we have fixed the problem.
And yes, I agree with TELS. MI is NOT 1.00 yet, and so various small
problem may occur from time to time as we go through the refactoring of
it to add VMS support and all the other things that take it from being a
cool installer into a highly robust system that works everywhere.
But then the ONLY things that are production grade and completely stable
are EU:MM and CPAN.pm.
And if your module is simple enough that using raw EU:MM is
satisfactory, I recommend people stick with it for now. I'm not going to
hype MI just because it's new and shiny.
And if you do need a feature in MI we welcome the additional user, and
we'll help you in any way we can. I hope the responsiveness to your bugs
for example have been appreciated (btw, the security information leak is
fixed now in the newly uploaded 0.60).
Module::Install, Module::Build and CPANPLUS are all not yet ready for
prime time yet, and so if absolute back-compatibility is essential,
stick to EUMM for now.
And I make no apologies for preferencing millions of end users over
thousands of authors, even though I happen to talk to authors more than
to users.
All authors are recommended to upgrade to Module::Install 0.60 as soon
as possible. Modules released with 0.58 should be upgraded to at least
0.59 or higher. All modules released with 0.59 do not need to be upgraded.
Thanks for your patience, and I hope you keep those bug reports rolling in.
Adam K
