Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Well, the problems have been there the whole time.

    The reason it hasn't come up sooner is that installer deficiencies of this nature are creeping problems.

    They build up gradually, and only start to impact strongly as the number of MB packages increases, and as the number of production versions of MB increases.

    As long as few people are using it, and it isn't changing quickly, you have a Pattern 1 situation. The installers don't break if the installer infrastructure is static.

    Add to that that most 9 out of 10, or more, users won't take the social risk of complaining in an open forum, and it takes even longer for things to come to light.

    Look at the Apache2:: problem, which was a serious problem but didn't really come to a head until they release the first mod_perl2 release candidate and the number of higher level people installing it shot up.

    The same sort of situation applies here. When I (for example) start to hear talk of it going core, and some of my private concerns that seem obvious still haven't been fixed, I start asking more questions.

    The problems been there, it just wasn't as much attention paid to it, possibly on the assumption that it was obvious and would be fixed before it went core.