[FFmpeg-devel] [libav-devel] [PATCH 0/20] removal of deprecated features

Hendrik Leppkes h.leppkes at gmail.com
Thu Jul 30 18:00:58 CEST 2015

Am 30.07.2015 17:50 schrieb "Andreas Cadhalpun" <
andreas.cadhalpun at googlemail.com>:
> On 30.07.2015 17:38, Anton Khirnov wrote:
> > Quoting Andreas Cadhalpun (2015-07-30 17:05:12)
> >> Ideally you should make sure that patches for all of them are
> >> before these APIs get removed.
> >>
> >> Considering how widespread the use of FF_API_PIX_FMT and
> >> still is, it might make sense to delay their removal.
> >
> > Past experience indicates that if we wanted to wait for all (or even
> > most) of the downstreams to adapt before breaking compatiblity, we'd
> > have to wait forever.
> I think that keeping some of these APIs "forever" is much less of a
> then breaking the majority of reverse dependencies.
> > Most of then, unfortunately, have to be forced into adopting the new
> Have you tried sending them patches before breaking compatibility?

Patching dozens of downstream projects is clearly not in the scope of what
should be expected from any Libav or FFmpeg developer.

Adapting to most of the changes being deprecated here is trivial however,
so if those projects have any maintainers at all, maybe you should notify
them instead to fix their project, instead of expecting us to do it for

More information about the ffmpeg-devel mailing list