[FFmpeg-devel] [PATCH] configure: Remove deprecated incompatible_fork_abi option

[wm4]

On Fri, 18 Apr 2014 05:11:28 +0200
Michael Niedermayer <michaelni at gmx.at> wrote:

> On Thu, Apr 17, 2014 at 03:51:21AM -0300, James Almer wrote:
> > On 03/04/14 10:38 PM, James Almer wrote:
> > > It's been deprecated since ffmpeg 2.0
> > > 
> > > Signed-off-by: James Almer <jamrial at gmail.com>
> > > ---
> > >  configure | 7 -------
> > >  1 file changed, 7 deletions(-)
> > 
> > Ping.
> 
> googling
> "enable-incompatible-fork-abi" gives 1040 hits
> "enable-incompatible-libav-abi" gives 692 hits
> 
> so iam a bit reluctant to drop the first, as the internet
> predominantly "points" users to it.
> but i didnt investigate deeper like what forums / mails / docs point
> to ...
> 
> but its sure annoying when a user finds some article saying that one
> option fixes something and then that option just doesnt work

OK, I also googled these terms. Results:

- lots of results that are various ffmpeg-devel mailing list archives
- some results in ffmpeg git mirrors
- the ffmpeg AUR package, which lists all unused/disabled configure
  options and the reason why it's disabled - it has this descriptive
  entry:

    # --enable-incompatible-fork-abi  # DO NOT WANT

- one link with a chinese translation of all configure scripts
- one hit is the #ffmpeg-devel stuff, where some ffmpeg developers and
  myself discuss how useless this switch is
- one hit to a debian packaging discussion, which mentions that this
  switch is useless and that they don't want it

And nothing else. That's where google actually stops delivering
results, saying that there are only duplicate hits left.

Conclusion: this switch is
1. unused
2. useless
3. not worth maintaining

So just drop the discussion about dropping the alias - can this horrible
ifdeffery hairball be removed entirely already?