[mythtv] Decision on FFmpeg repository

[David Engel]

On Thu, May 17, 2018 at 05:51:43PM +0200, Jean-Yves Avenard wrote:
> 
> 
> > On 17 May 2018, at 4:51 pm, David Engel <david at istwok.net> wrote:
> >> 
> >> That’s all good, but then that means that support for MediaCoded in FFmpeg is experimental anyway.. Do we want that in our release so soon?
> >> 
> >> Are we willing to make everything unstable (from an API point of view) just to have support for something experimental that we didn’t support up to now anyway?
> > 
> > Of course we don't want to intentionally break other things, but in
> > case you haven't noticed, the Android port is the *only* significant
> > work being done right now.  IOW, there is no other work to be
> > destabilized for the time being.  If any other work does comes up and
> > is affected, we can move one effort or the other to a branch.
> > 
> >> If you ever ask a developer what version of his you should use, of course he/she’s always going to tell you to use the latest and greatest, luckily most team have a release manager :)
> >> 
> >> 4.0 was a snapshot of ffmpeg done not even a month ago. By the time we’re ready with Peter’s change anyway, 4.1 would be out. FFmpeg make release frequently, when they are confident current master is in a stable state.
> > 
> > We're, well, mainly Peter, are ready to start now.  If we wait for
> > ffmpeg 4.1 and it changes as much as you expect, wouldn't we have to
> > start over again?  In a sense, we're trying to get ahead of the curver
> > and targeting for 4.1 now.  Note that I don't think anyone is
> > proposing to closely track ffmpeg master forever.  After the
> > MediaCodec support, I expect we'll go back to updating to newer ffmpeg
> > versions on an as needed bases.
> 
> 
> If the aim is to only code support for MediaCodec, could always go with master temporarily, and switch to 4.1 once its frozen.
> and then go from stable to stable

My only current aim for ffmpeg is MediaCodec.  Ater that is done, I
wouldn't mind going back to stable, ffmpeg releases.  The git handling
with subtrees would probably be more complicated, but I have to
believe it can be done.  In theory, it should boil down to a rebase.

David
-- 
David Engel
david at istwok.net