Howdy guys. Sorry for the crosspost. Patch to speed up taglib.

Manuel Amador (Rudd-O) rudd-o at
Fri Oct 12 14:42:32 CEST 2007

The right way to ward off these issues is to build a sizable corpus of 
multimedia files and a decent test suite that stress-tests the code before 

El Vie 12 Oct 2007, Scott Wheeler escribió:
> Jeff Mitchell wrote:
> > On Thursday 11 October 2007, Scott Wheeler wrote:
> > I do understand that there are some drawbacks in the form of keeping
> > various API versions online on your website (unless you remove old ones),
> > etc.  But most packagers are quite happy to package a new official
> > release of a small library like taglib once a month or once every few
> > months, when they're not at all happy to package SVN snapshots even if
> > the last release hasn't been for years.
> The biggest problem there is that unlike an Amarok bug that makes the
> app crash, a TagLib bug can destroy a user's music collection.  (In
> fact, there was an off-by-one bug in one of TagLib's betas that would
> render every FLAC that it touched unplayable.)  That's why I don't just
> throw together a release every time that it seems like there are a few
> fixes in.  In general, that theory is nice, in practice it's just meant
> that the fixed amount of work to do a release (traditionally reviewing
> all bugs in the repo and reviewing the entire diff since the last
> version) is something that I rarely have time to do.
> -Scott
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at


	Manuel Amador (Rudd-O) <rudd-o at> -
	GPG key ID 0xC8D28B92 at

Be careful!  UGLY strikes 9 out of 10!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : 

More information about the taglib-devel mailing list