Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=459979
--- Comment #35 from Dan Dennedy dan@dennedy.org 2008-12-18 02:54:07 EDT --- (In reply to comment #31)
I don't want this project to be a nuisance with too many configurations. First of all, I think I should split up my ffmpeg module because there are some elements for deinterlace and color space conversion that are unencumbered and then encumbered format/codec-oriented elements. That would let you or someone else just make a separate package with the encumbered elements similar to gstreamer-ffmpeg. MLT has libdv and libvorbis modules that still make it usable without the encumbered ffmpeg elements. I do not yet think it is necessary to
In MLT SVN trunk, I have added a configure option --avformat-no-codecs. This will build the MLT avformat plugin without exposing *any* of the codecs or muxers. This does make a plugin that contains the deinterlace, resampling, and color space converter. The color space converter is required at the moment to make this usable. The --avformat-svn configure option will checkout a specific revision of FFmpeg and then statically link the MLT plugin against it if that makes it any easier (no shared ffmpeg libs to link against).
Someone can then make a mlt-ffmpeg package for rpmfusion.org that does something along the lines of: ./configure ... make -C src/framework make -C src/modules/avformat all install
This would put only that plugin into the package, but at this point it is a replacement for the one from the main mlt package. IOW, it shares the same file path/name. Is that a problem?