[Slackbuilds-users] ffmpeg update - request for testers

[Heinz Wiesinger]

Am Freitag, 23. Mai 2008 02:36:39 schrieb Antonio Hernández Blas:
> Hi all.
>
> I'm the MAINTAINER of ffmpeg and want to announce a new SlackBuild for
> ffmpeg(version 20080521), you can find it at:
> http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/
>
> Please, read this before you screw your system ;)
> http://hba.nonlogic.org/projects/slackbuilds/testing/README.WARNING
>
> The main reason to make this announce is to request for persons that
> can/want to test it before i upload it into pending/. Please, take a
> look to
> http://hba.nonlogic.org/projects/slackbuilds/testing/ffmpeg-20080521/README
> to know the changes i've made.
>
> Also, i've updated x264(version 20080521 too):
> http://hba.nonlogic.org/projects/slackbuilds/testing/x264-20080521/
> I tested ffmpeg with the current SlackBuild in SBo and this update too
> without any problem.
>
This is actually rather cool ;)
I thought about that too packages a lot in the last few weeks, so now's 
probably the right time to share my thoughts.

Both apps are rather critical, as they do not release tarballs and there are 
still many apps depending on them. Making sure everything does *work*, is not 
easy, as every app using ffmpeg or x264 has to be tested.

From my point of view, those two should not be updated that often. I first 
thought about an update right after the release of a new Slackware-version, 
but I think coordinating those updates with MPlayer-releases would be much 
better. There are a few reasons for that.

MPlayer has a similar development philosophy as ffmpeg (as those are 
affiliated), but at least it gets released sometimes. As MPlayer is using 
ffmpeg internally we can probably state that the version used by MPlayer is 
pretty stable.
MPlayer is also adjusting the interface to x264 in svn, which means that the 
perfect combination of those two would be snapshots of about the same time.
Updating x264 and leaving MPlayer behind would probably end up with problems 
on runtime.

Based on that versions we can than start syncing the other apps using them, 
which I am not sure about how many there are currently. Anyway, this will be 
a huge effort and in no way be a one-an job, as there are just too many deps 
to be looked through.

On a sidenote, I had a look at your README Antonio and want to inform you, 
that libamr-nb/wb ARE in the repo. You can find them in audio as amrnb/amrwb.

My two cents :)

Grs,
Heinz