[FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver

Marton Balint cus at passwd.hu
Sun Oct 22 11:51:38 EEST 2017


On Sun, 22 Oct 2017, Clément Bœsch wrote:

> On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote:
>> On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote:
>>> On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote:
>>>> This patchset removes the long-deprecated ffserver program and all
>>>> its privately exposed things from libavformat.
>>>>
>>>> Rostislav Pehlivanov (6):
>>>>   Remove the ffserver program
>>>>   libavformat: remove the ffmenc and ffmdec muxer and demuxers
>>>>   libavformat: unexpose the ff_inet_aton function
>>>>   libavformat: remove the ff_rtp_get_local_rtcp_port function
>>>>   libavformat: unexpose private ff_ functions needed by ffserver
>>>>   libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag
>>>
>>> This set will be applied a month or so from now, when the unstable ABI
>>> period is over.
>>>
>>> If you can do in a month what was not done in a year plus, anyone is
>>> welcome to fix all ffserver issues or preferably replace it altogether
>>> with a new tool with a more user friendly syntax/interface.
>>
>> Can you list the technical problems that require dropping ffserver,
>> so that someone interrested in fixing them can do so ?
>
> It's probably too late, one month is not enough. We already had that
> discussion:
> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html
>
> The goal was ZERO internal API usage + at least partial FATE coverage. We
> gave it a year and nothing changed because no one cared.

It is natural that people only care if it gets removed otherwise.

A list is important so anybody interested can estimate the amount of work 
needed.

What abouth the ffmenc/ffmdec? That needs to go as well? Or if internal 
api usage is fixed, and some fate coverate is added, ffmenc and ffmdec can 
stay?

Thanks,
Marton


More information about the ffmpeg-devel mailing list