Bump to version 2.1.1, here's the changelog: Changes for libmusicbrainz 2.1.1 ------------------------------------- - Return special TRMs for special conditions for TRM generation: c457a4a8-b342-4ec9-8f13-b6bd26c0e400 -- Sigserver busy and overloaded f9809ab1-2b0f-4d78-8862-fb425ade8ab9 -- Source file is too short to calculate TRM 7d154f52-b536-4fae-b58b-0666826c2bac -- File is slience - If the TRM signature server becomes overloaded, it will now start returning HTTP 503 error codes and the TRM generator will catch that and return the Sigserver busy TRM shown above. Changes for libmusicbrainz 2.1.0 ------------------------------------- - moved the python bindings into a new seperate project - rewrote the mp3 duration detection code to be more robust by making it vastly easier. In the process the bitzi related code has been tossed. This should make the libary smaller and the mp3 duration checking faster. - Due to the bitzi code being removed, the SHA1 and Bitprint related functions have been removed. - Added query items for Release Dates/Countries, Amazon Asins and Amazon cover art URLs - Move include files into include/musicbrainz so that the example files will compile outside of the libmusicbrainz client source tree. The python bindings were removed, so the ebuild is noticeably simpler. The LICENSE was incorrect, it is LGPL-2.1
Created attachment 29753 [details] musicbrainz-2.1.1.ebuild
Note: this new verion provides /usr/lib/libmusicbrainz.so.4 the other versions (2.0.1, 2.0.2) provide /usr/lib/libmusicbrainz.so.2 So an upgrade breaks the applications that depend on musicbrainz.
And symlinking libmusicbrainz.so.2 to libmusicbrainz.so.4.0.0 may break some older apps, so I am told. Suggested fix (IANAExpert, and I'm more or less paraphrasing Robert Kaye on the issue) is to somehow leave libmusicbrainz.so.2 intact when removing 2.0.{1,2,2-r2}. I'm not experienced enough with Gentoo ebuilds to fix this properly.
Musicbrainz-2.1.1 is in portage.
