The musicbrainz client library includes python bindings, but they're not installed by the 2.0.2 ebuild. I've tried to trivially add building the bindings to the musicbrainz-2.0.2 ebuild, but the build chokes because it can't find the headers yet since they're not yet installed. It appears the bindings have their own version number (according to the included README file). I guess it's a bit like libapr being included in apache. At any rate, I've created a pymusicbrainz-0.4 ebuild that builds and installs the bindings that accompany pymusicbrainz-2.0.2. I'll attach it as a comment after the initial submission, since there doesn't appear to be a way to add an attachment from the initial bug submission screen. - Andrew
Created attachment 16843 [details] New ebuild: dev-python/pymusicbrainz-0.4.ebuild This is the ebuild for pymusicbrainz-0.4 (the bindings included in the musicbrainz-2.0.2 library). - Andrew
Created attachment 17708 [details] pymusicbrainz-0.4.ebuild I added the examples and tests to /usr/share/doc/${PF}. Alastair, I tested the examples I could and they seem to be working fine.
Hey Alastair, sound@g.o., I tested this and it works, but would this be best added to media-libs/musicbrainz-2.0.2 as a python USE flag?
i think adding them under a python useflag would be more appropriate if they were bundled with musicbrainz
The bindings are included in the libmusicbrainz-2.0.2 release, but in CVS have been moved to a new module (python-musicbrainz). See: <http://lists.musicbrainz.org/pipermail/musicbrainz-devel/2003-September/000468.html> This seems to imply that soon they'll be released independently. In addition, there's a circular dependency for the python bindings... the library has to be installed before bindings can be built properly. It's bitten the Debian people as well. See: <http://lists.musicbrainz.org/pipermail/musicbrainz-devel/2003-October/000486.html> - Andrew
I added a python USE flag to media-libs/musicbrainz.
