On the excessively long road to the next stable Picard release I need to do a stable release of libmusicbrainz and libtunepimp. Both of those are now complete with all the bug fixes that I want to get into these before the next release. If you run Linux or Mac OS X, please take a moment to download, compile, test and install these two tarballs:
Please note that the independent python bindings for libmusicbrainz have been wrapped back into libmusicbrainz itself and can be found in the python directory of the tarball. libmusicbrainz has a new example program called getrels that shows how to retrieve AR links via the web service. libtunepimp has undergone major changes and now sports a plug in system that will make it easier to add more formats.
Unless these tarballs have major issues, I plan to update the version numbers to 2.1.2 and 0.4.0, respectively, and release them in the coming days. Then I’ll focus on getting stable release of Picard out the door.
Technorati Tags: libmusicbrainz, musicbrainz, picard, libtunepimp
MetaBrainz Blog 
Quick question: Do these libraries break existing APIs? If I install them, will amarok or whatever still work?
libmb shouldn’t break anything. libtp, on the other hand, will break things if they weren’t built on top of 0.4.0.
I agree with you the way you view the issue. I remember Jack London once said everything positive has a negative side; everything negative has positive side. It is also interesting to see different viewpoints & learn useful things in the discussion.
I agree with you the way you view the issue. I remember Jack London once said everything positive has a negative side; everything negative has positive side. It is also interesting to see different viewpoints & learn useful things in the discussion.
I agree with you the way you view the issue. I remember Jack London once said everything positive has a negative side; everything negative has positive side. It is also interesting to see different viewpoints & learn useful things in the discussion.