GNOME Bugzilla – Bug 327078
mad and id3mux plugin should be seperate
Last modified: 2006-05-09 13:00:43 UTC
Since libmad and libid3tag are distributed in seperate tarballs and can be installed completely independently of each other, the plugins based on those libraries should also be seperate.
Created attachment 57407 [details] [review] patch against gst-plugins-ugly cvs
Sounds good to me, although we can move the files better using CVS surgery and preserve the history in the new location.
Sounds good to me too. Another 'solution' would be to drop the libid3tag-based id3mux element entirely and move the taglib-based id3v2mux element into -good and make that as backwards-compatible with id3mux as possible (and register it under the 'id3mux' name as well of course).
What is the current status of this? I know there has been a lot of tag changes to various modules of the last month.
IMHO the libid3tag-based id3mux should be removed completely once the taglib-based id3v2mux has been moved to -good (and given a compatible interface), or alternatively be rewritten to be sane code that works (and I can't really see anyone volunteering to do this). I'm not sure there's much point in splitting mad and id3tag now if it's scheduled for removal soon anyway.
Can we close this bug out now?
It's still not possible to build the mad plugin without having libid3tag installed, but if the id3tag gets removed soon, that's good enough for me.
> ..., but if the id3tag gets removed soon, that's good enough for me. Great, closing then.