Front page | perl.qa |
Postings from April 2006
I can't remember the exact list off the top of my head. At the time, I did the cascade tracing by hand using the CPANTS webpage, it took for-bloody-ever. The only reason I kept doing as deep as I did was that I kept being astonished at what was getting caught in the web. There's been something of a shuffle in there since, a lot of people dropped Test::Warn (which was a big branch) and Test::Builder::Tester merged in. I'm hoping, if we can get this CDBI-SQLite stuff working, to have similar things running automatically in future, so I could actually answer your question. Adam K Fergal Daly wrote: > On 4/18/06, Adam Kennedy <adam@phase-n.com> wrote: >> The aformentioned change to Test::Builder broke 3 different Test-Testing >> modules that relied on it. > > 3? I only know of 2 - Test::Builder::Tester (which scrapes and broke) > and Test::Tester (which doesn't scrape and didn't break). Is there > another Test-Testing module? > > F > >> That broke 28 Test modules which used them. >> >> That broke 115 various CPAN modules. >> >> That broken 880 other CPAN modules. >> >> And so on and so forth, until the end number ended up somewhere between >> 2000 and 3000 distributions. >> >> So 30% of all CPAN modules broke. >> >> This included things like almost ALL of WWW::, because Mechanize got >> sucked into it. God knows how many darkpan Mech modules got hurt as well. >> >> Do we blame ALL of those 100s of developers? >> >> Does blame even matter at that point? >> >> This is what I mean by becoming an API even though you didn't want to be. >> >> Adam K >>Thread Previous | Thread Next