[FFmpeg-devel] [RFC] [PATCH] Cleanup obsoleted libavfilter notes

[Stefano Sabatini]

On date Monday 2011-01-24 22:02:51 +0100, Reinhard Tartler encoded:
> 
> Hi,
> 
> This patch is provocative on purpose with the intent to stimulate a
> discussion about a) how to proceed with the SOC repo and b) to declare
> the (external) libavfilter API stable, which means that future API
> changes require either a symbol versioning hack or a major bump.
> 
> Comments?
> 
> diff --git a/doc/libavfilter.texi b/doc/libavfilter.texi
> index 8745928..906fb01 100644
> --- a/doc/libavfilter.texi
> +++ b/doc/libavfilter.texi
> @@ -13,20 +13,6 @@
>  Libavfilter is the filtering API of FFmpeg. It is the substitute of the
>  now deprecated 'vhooks' and started as a Google Summer of Code project.
>  
> -Integrating libavfilter into the main FFmpeg repository is a work in
> -progress. If you wish to try the unfinished development code of
> -libavfilter then check it out from the libavfilter repository into
> -some directory of your choice by:
> -
> - at example
> -   svn checkout svn://svn.ffmpeg.org/soc/libavfilter
> - at end example
> -
> -And then read the README file in the top directory to learn how to
> -integrate it into ffmpeg and ffplay.
> -
> -But note that there may still be serious bugs in the code and its API
> -and ABI should not be considered stable yet!

Updated, I believe it's safe to apply this patch now, as the
libavfilter-soc repo now contains only few filters, and the movie
source in it is incompatible with the one contained in the main repo.

As for the git repo, I settled a personal ffmpeg clone and created a
branch with the 6 uncommitted soc filters, but I don't want to
advertise it since I may screw it up at each moment, and I don't
believe it makes sense to keep a separate branch for those filters,
hopefully someone will have a further reason for porting them to the
main repo.
-- 
FFmpeg = Fancy and Frenzy Meaningful Pure Extended Guide