Protocol doesn't demand it - but human decency sure as heck does. I just wanted to apologize to everyone for my erroneous commit to the 1Q-2006 file yesterday.
The boring background is that some upstream cpan authors use a numbering scheme that makes sense in a decimal fashion, where .29001 is less than .30 (expand the 0's, yada yada yada, ask your kid sibling about math at school today), but portage expects that numbering scheme to actually be a version identifier (so to speak, its the gist I'm going for here, don't flame me on the technicalities of how portage reads a version number). dev-perl/DateTime came out with a .2901 release, which I put in the tree as such many a moon ago (about 1.4 moons ago to be exact), and recently .30 came out. Because of the math business I just mentioned, .30 would never get picked up by anyone since (dropping the decimal point) 2901 > 30. I 'moved' .2901 to .29.01 to make this work better. All was good. Then I had this brilliant idea - use the quarterly file to help people migrate that number, no bizarre downgrades when the emerge world. 'cept move in the quarterly isn't for moving a version, its for moving between categories, package names, etc., and as such I made a mistake. No need to respond to this message (i'd prefer it if you didn't actually - between the 'stuff happens' and the 'your an idiot, revoke that bad boys right to a keyboard' messages, i think it would all even out). ~mcummings
signature.asc
Description: This is a digitally signed message part
