[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#203211: RFP: avidemux -- A small editing software for avi (especially DivX)

Hi all,

I have checked the rpmfusion package for avidemux and they have patched it to use the system libraries for libass, liba52, llibmad and libtwolame at least. Furthermore, the package has "BuildRequires: ffmpeg-devel" but I could not found a patch to force it to use the system ffmpeg libraries.

I have put Richard Shaw, the maintainer of this package in rpmfusion into CC. Richard, can you tell us more about avidemux' usage of the ffmpeg libraries in your package?

Best Regards,

PS: Sorry for top-posting, but the following text is a rather decent summary of our previous discussion...

Am 03.01.2012 00:14, schrieb Reinhard Tartler:
On Mon, Jan 2, 2012 at 5:03 PM, Fabian Greffrath<fabian@greffrath.com>  wrote:
Am 02.01.2012 16:53, schrieb Reinhard Tartler:

Does it nowadays work properly with the system libav, or does it still
require its internal copy? If the latter, then it's going to be a lot of
work to get it in shape.

I haven't had a look at the source, but according to the 2.5.6 release notes
they "Updated the FFmpeg libraries (version 0.9)". So this sounds like they
still use an internal copy, but since it's recent enough, maybe it's not
that hard to use the system libav headers and link against the system libs?

I've now found the time to look at how avidemux "uses" ffmpeg, but
I have bad news:

avidemux specifically downloads an ffmpeg-0.9 tarball (we use libav in
debian), and
then applies a larger number of patches:

Most of those patches actually look pretty scary to me. Additionally, most
of the comments in those patches don't really make sense to me either.

I conclude that trying to link avidemux dynamically against the system
is not feasible. Shipping a static copy of avcodec and friends doesn't make me
feel too happy either :-/

Reply to: