Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 26774 - New musicbrainz library (2.0.2) available
Summary: New musicbrainz library (2.0.2) available
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal minor
Assignee: Nick Hadaway
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-16 22:52 UTC by ajs
Modified: 2003-08-17 23:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Proposed ebuild for musicbrainz 2.0.2 client library (musicbrainz-2.0.2.ebuild,646 bytes, text/plain)
2003-08-16 23:16 UTC, ajs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ajs 2003-08-16 22:52:08 UTC
A new version of the musicbrainz client library is available: 2.0.2

Amongst other things, they claim to have improved their build system in this
release. The CFLAGS/CPPFLAGS fix during src_unpack() is no longer needed, and
the entire function can be removed from the ebuild.

I haven't yet investigated dependencies and/or USE flags. During ./configure,
however, I've noticed it looks for expat; I don't yet know the implications if
it's not found. There also appears to be perl and python bindings included in
the distribution.

 - Andrew
Comment 1 ajs 2003-08-16 23:16:09 UTC
Created attachment 16204 [details]
Proposed ebuild for musicbrainz 2.0.2 client library

This is the ebuild I've used to install musicbrainz 2.0.2 on my system. It's a
copy of the 2.0.1 ebuild, with the src_unpack() function removed since it's no
longer needed.

 - Andrew
Comment 2 Nick Hadaway 2003-08-17 02:56:51 UTC
musicbrainz-2.0.2 is now in portage.  Please test this new build and let me know if you find any problems or if it works for you.
Comment 3 ajs 2003-08-17 23:15:27 UTC
Works fine for me; testing has been limited to zinf fetching CD metadata, which appears to work fine.

One final note is that the includes INSTALL doc appears to be erroneous when it talks about the --enable-cpp-headers option for ./configure (although it doesn't do any harm). I suspect it's something from the 1.x releases. At any rate, ./configure --help doesn't mention the option, and a quick search for 'cpp' in configure.in doesn't show any obvious logic for such an option.

Thanks for the fast turnaround, :)

 - Andrew