during my last world with the file collision protect patch (see bug 28228) portage failed on mad as it tries to install the following files which are owned by either libmad or libid3tag: /usr/lib/libid3tag.la /usr/lib/libid3tag.a /usr/lib/libmad.la /usr/lib/libmad.a /usr/lib/pkgconfig/id3tag.pc /usr/lib/pkgconfig/mad.pc /usr/include/id3tag.h /usr/include/mad.h emerge -uD world wants all of mad-0.14.2b-r2, libmad-0.15.0b-r1 and libid3tag-0.15.0b installed.
I feel the need to point out that mad-0.14.2b-r2, also has a collision with libid3tag-0.15.0b over the /usr/lib/libid3tag.so symlink and it was casuing my emerge of rhythmbox to fail since the order of installation of the libid3tag-0.15.0b and the mad-0.14.2b-r2 packages was important. Since libid3tag-0.15.0b was installed first and had /usr/lib/libid3tag.so pointing at /usr/lib/libid3tag.so.0.2.0, that would make rhythmbox happy. However, between the installation of libid3tag-0.15.0b and rhythmbox, I installed mad-0.14.2b-r2 which overwrote that symlink so that /usr/lib/libid3tag.so now points to /usr/lib/libid3tag.so.0.1.0, and that version of the lib is missing the id3_frame_field which rhythmbox wants. Whew. I propose that mad and libid3tag block each other until such time as mad is updated to depend on libid3tag and not include an outdated version itself which conflicts with libid3tag.
mad 0.15 is now stable (metapackage)
