[FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
u at pkh.me
Sun Oct 22 13:40:27 EEST 2017
On Sun, Oct 22, 2017 at 10:51:38AM +0200, Marton Balint wrote:
> 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.
July 10th, 2016, ffserver program being dropped
After thorough deliberation, we're announcing that we're about to drop
the ffserver program from the project starting with the next release.
ffserver has been a problematic program to maintain due to its use of
internal APIs, which complicated the recent cleanups to the
libavformat library, and block further cleanups and improvements which
are desired by API users and will be easier to maintain. Furthermore
the program has been hard for users to deploy and run due to
reliability issues, lack of knowledgable people to help and confusing
configuration file syntax. Current users and members of the community
are invited to write a replacement program to fill the same niche that
ffserver did using the new APIs and to contact us so we may point
users to test and contribute to its development.
Removal was announced, people were aware, we got discussions, but no one
cared enough to do something about it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the ffmpeg-devel