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

On 2009/07/28 12:05 AM, Orcan Ogetbil wrote: > > On Thu, Jul 23, 2009 at 4:29 PM, Stewart Adam wrote: > > I would contact upstream and ask if they are planning to release any > of the plugins separately in the future. If the plugins will always be > distributed inside the main tarball, then it makes sense to proceed > with option 1. > > Orcan I've made attempts to contact upstream multiple times (IRC, forums, bugtracker) and none have worked so at this point I've given up on trying to get in touch with the avidemux developers. It looks like they're not going to release plugins individually so I've closed the plugins package review, but if some very popular plugins are released from a 3rd party or if a plugins tarball is released upstream then I'll reopen the bug for a review. Anyways, avidemux 2.5 still fails to build properly on ppc and I don't have any knowledge of how altivec works (nor a PPC machine to test on)... Full build logs are here [1], but this is the error causing all the problems since 2.4.4: /builddir/build/BUILD/avidemux_2.5.0/avidemux/ADM_libraries/ADM_libmpeg2enc/altivec/build_sub22_mests.c:540: error: incompatible types when assigning to type '__vector unsigned int' from type '__vector __bool int'

Would somebody be able to help create a patch? I'm going to ExcludeArch ppc* in the mean time since 2.4.4 packages are *really* broken and 2.5 has worked a bit better from my tests on F11. From my foreign eyes, if altivec would be disabled in ADM_libmpeg2enc,