mass rebuild for x264/ffmpeg/mplayer on F19

Tomasz Torcz tomek at pipebreaker.pl
Tue May 28 21:34:23 CEST 2013


On Tue, May 28, 2013 at 07:57:06PM +0200, Julian Sikorski wrote:
> W dniu 25.05.2013 14:00, Sérgio Basto pisze:
> > On Sáb, 2013-05-25 at 10:27 +0200, Andrea Musuruane wrote: 
> >> On Sat, May 25, 2013 at 1:43 AM, Sérgio Basto <sergio-iCFKjj3otdHQT0dZR+AlfA at public.gmane.org>
> >> wrote:
> >>         [...]
> >>         9 - build what requires ffmpeg.
> >>         repoquery --releasever=19 --whatrequires ffmpeg\*1.1\*
> >>         --source
> >>         --alldeps | grep -vP "x264|ffmpeg-1.1|gpac|^mplayer|vlc|
> >>         mythtv|
> >>         libquicktime|mjpegtools" | sort -u
> >>         
> >>
> >> These queries seems wrong to me because you are extracting both BR and
> >> Requires. For example devede does not BR ffmpeg, it just requires it
> >> at runtime. Rebuilding it is unneeded.

> It's probably too late now, but here are my 2 cents:
> - packages having mplayer in dependencies (like gmtk) do not need to be
> rebuilt at all - they don't link to mplayer, they just use the executable
> - this is what I use to get the deps whenever I am testing a new ffmpeg
> build:
> 
> repoquery --disablerepo=* --enablerepo=rpmfusion-{non,}free-rawhide
> --whatrequires --source `repoquery --provides --disablerepo=*
> --enablerepo=rpmfusion-free-rawhide ffmpeg-libs` | sort | uniq | sed
> 's/-[^-]*-[^-]*\.[^.]*\.[^.]*$//'

  Does this issue affect packages using ffmpeg-compat?  My package – motion – appears
in none of those lists.

-- 
Tomasz Torcz                                                       72->|   80->|
xmpp: zdzichubg at chrome.pl                                          72->|   80->|


More information about the rpmfusion-developers mailing list