[FFmpeg-devel] [PATCH] web: Remove recommandition to upgrade to 3.1

Ronald S. Bultje rsbultje at gmail.com
Thu Jun 30 14:21:07 CEST 2016


Hi,

On Thu, Jun 30, 2016 at 8:16 AM, Michael Niedermayer <michael at niedermayer.cc
> wrote:

> On Thu, Jun 30, 2016 at 07:57:29AM -0400, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Thu, Jun 30, 2016 at 4:32 AM, Michael Niedermayer
> <michael at niedermayer.cc
> > > wrote:
> >
> > > On Wed, Jun 29, 2016 at 11:21:48PM -0300, James Almer wrote:
> > > > On 6/29/2016 9:27 PM, Carl Eugen Hoyos wrote:
> > > > > Ronald S. Bultje <rsbultje <at> gmail.com> writes:
> > > > >
> > > > >> For the record: there was some discussion related to this on IRC.
> > > > >
> > > > > Would you mind adding some relevant points here?
> > > > > I was under the impression that this mailing list
> > > > > is the main place for FFmpeg patch discussions, no?
> > > > >
> > > > > Carl Eugen
> > > >
> > > > [18:37:47] <@BBB> we should recommend that people upgrade to 3.1
> > > tools-and-libs-at-the-same-time
> > > > [18:45:42] <jamrial> and i agree with BBB, instead of removing the
> > > recommendation, just make it clear that tools and libraries should
> ideally
> > > be updated at the same time and not mixed
> > > > [18:48:11] <michaelni> jamrial, can you post a patch that changes
> thre
> > > recomandition to all libs/tools or changes the release notes ?
> > > > [18:50:13] <jamrial> michaelni: alright
> > > >
> > >
> > > > I'm fine with this patch or the one i sent. I'm not going to block
> > > either.
> > >
> > > ok, i will wait until 24h have passed from the point of patch
> > > submission, and in absence of objections on the ML, apply it
> > > we should IMO pull this recomandition at least until 3.1.1
> > > Iam also happy if others apply it or another solution sooner
> >
> >
> > I prefer James' approach (recommending to update tools+libs together). I
> > have two reasons:
> > A) pulling a recommendation to update will be conceived as negative
> press.
> > Negative press is always bad. Media can always blow things out of
> > proportion and all sort of crap will follow. I prefer to just keep this
> > simple.
>
> do you realize that a distro upgrading to 3.1 will cause basically
> almost every application that uses our libs to break ?
> so far there are reports of kodi, mpv, chromium, ffplay and mlt
> breaking. (breaking in the sense of not working at all IIRC)


But won't any update of these apps to any future (same-major) version of
ffmpeg break them? And isn't that because of a bug in the apps (use of
private API)? And even if we worked around that bug in our libs (by making
the fields public), wouldn't that still require us to move them and thus
break ABI?

So I don't see how keeping the update from 3.0 to 3.1 from users _alone_
will help anything, other than buying time.

Ronald


More information about the ffmpeg-devel mailing list