[FFmpeg-devel] [PATCH] configure: don't build ffserver unless explicitly enabled

Clément Bœsch u at pkh.me
Sun Sep 11 20:57:48 EEST 2016

On Sun, Sep 11, 2016 at 06:52:50PM +0100, Sven C. Dack wrote:
> On 11/09/16 18:27, Clément Bœsch wrote:
> > Aside from the stdout output in ffprobe, no stdout/stderr output is
> > standardized in FFmpeg and thus can be changed at will (and does
> > regularly). You can try to parse it, but there is zero warranty that it
> > will work the next day.
> > 
> > Regards,
> Did you at least read the second part of my mail? Because I sure do get you
> don't care. It's all you, Nicolas and Hendrik have been saying here really.
> What I want you to do is to snap out of it and to start caring. Put the
> message where it belongs, meaning, put it into the documentation. ffserver
> is not dead just yet and you should really follow the regular coding rules
> until it is. And of course do users often have to accept the consequences of
> a changes, but they also only ever will do so when a change brings an actual
> gain. Nobody wants to accept a useless change. Your change, to put a message
> to stderr into the code, just has no gain for anyone who is using it and can
> only upset. Can we agree on this or am I talking to a wall?

I think we disagree, because no user of a working setup will ever read the
documentation just to check for deprecated tools. Having the warning at
runtime is the most efficient way to reach out a maximum of users as soon
as possible so they have time to migrate their setup. A bit like
deprecation warning in API at build time.

Clément B.

More information about the ffmpeg-devel mailing list