taglib-extras 0.1.7 vs. taglib 1.6

[Jason A. Donenfeld]

What's the issue here? Taglib finally supports what taglib-extras has
been adding to it forever. So why not now just drop taglib-extras and
use taglib's new features? Undoubtedly distros will soon start
shipping 1.6, especially if amarok requires it. You say that it could
be problematic since asf/mp4 are optional at compile time. Well, so is
MySQLe, and it seems like distro's pretty quickly adapted to Amarok's
requirement for this.  Or if users have no mp4 or asf files, on
distros like Gentoo, they just won't compile it with that support (use
flags...). If taglib-extras still has things that taglib 1.6 does not
have, then keep only those necessary parts, and chuck the rest. No
need for code duplication here.

So in summary my advice is:

1. Remove duplicated functionality in taglib-extras that is now in taglib 1.6
2. If this means taglib-extras no longer has any functionality, get
rid of it. Otherwise just ship it smaller.
3. Inform distros that because Amarok relies on taglib, if they want
mp4/asf support, they need to ship with it enabled in taglib.
4. Most distros will comply.

Evidently there are a lotta problems with header conflicts... These
would all be resolved by removing the duplicate functionality, right?
Or maybe the issue is that you don't want to introduce a new dep when
2.2 is in beta-phase. This is understandable, but taglib 1.6 came as a
surprise - maybe this would have been planned for earlier. In this
case, make an exception.

Or maybe I just don't see what the issue is here exactly...