* Ken Williams <[EMAIL PROTECTED]> [2008-10-01T21:34:28] > On Wed, Oct 1, 2008 at 12:02 PM, Ricardo SIGNES > >> latest.pm doesn't ever get installed on anyone's computer. If you > >> install it, we have a backup plan for that too - the guys in black > >> coats will come and take your computer away. > > > > Well, at this point we're back to "everybody must upgrade everything." > > Presumably latest.pm knows to use the installed latest.pm if it's later, > > even if this is rarely true and even more rarely needed. > > Ricardo: there's no such thing as "installed latest.pm". Please go > back and read what I wrote above.
I read and understood what you said. Perhaps I should've said, "presumably it would be better if..." This thread started with "Module::Install is a time bomb" because, in large part, it bundles code that will not use later code found on the installing system. Then when there is a bug, every author must re-release a dist. That means that a fix to Module::Install means that there must be a thousand more upgrades, one for each dist using it. Module::Build is going to fix that by correctly using the latest Module::Build -- either the one in ./inc or the one in @INC. It will accomplish that by using code that is only found in the dist. That means that when there is a bug, every author must re-release a dist. That means that a fix to latest.pm means that there must be a thousand more upgrades, one for each dist using it. I will admit that bugs in latest.pm (which I have not seen, but can imagine) are less likely than bugs in Module::Install (which I have seen, and wish I could not imagine). It still seems sort of bizarre to have absolutely no nuclear option by which one can deal with 1,234 deployed and broken latest.pms. -- rjbs
