Hi,
Avidemux 2.5 was released recently which changed the build procedure
quit a bit. Much of the functionality that was included in avidemux 2.4
has been split out into plugins which are now build separately from the
main package. This introduces some problems for building, as the plugins
require a installation of the main package (some shared libraries) to
build properly.
The two ways to package avidemux are:
1. Build main package, "make install" to a local directory in order
to build plugins and then install everything together into $RPM_BUILD_ROOT
2. Split out the plugins into a different package and BR avidemux-libs
I prefer option 2 since the plugins can be patched/updated without
having to redownload the shared libraries again. However, it looks like
upstream is packaging plugins in the main tarball so this point is null.
Would there be any other reasons for sticking with option 2? avidemux
2.4 is very broken (it crashes when open videos and doesn't compile on
ppc) so if in a few days nothing has come up I'm going to close the
review for avidemux-plugins [1] and go ahead with option 1.
Thanks,
Stewart
[1] https://bugzilla.rpmfusion.org/show_bug.cgi?id=719
