> You mean like how Module::Build broke over a YAML release and we spent over > a year cleaning up after it because every single user who ran into that > version mismatch had to have the problem explained to them? > > I still regularly see -ancient- versions of Module::Build installed lots of > places, often pre-INSTALL_BASE-behaviour-change, which causes great fun when > I upgrade it past that release. > > I know that's crap. I know it's sad. But it's the real world, and I live in > it. >
You guys are way beyond me when it comes to understanding this stuff. But as the average dodo, I really appreciate the "real world" attitude. I regularly have to deal with older perls supporting production installed software. I don't want to (or can't) upgrade it. I want the modules I use to "work", especially the variety of "work" that involves not barfing when I try to install it. If autobundling (or whatever) solves that problem, then yay for that solution, as long as the amount of extra space involved isn't completely onerous. Essentially I agree with that f-word laden run on sentence you espoused earlier. Please to just be working. Austin