
pkendall64 at gmail
May 8, 2012, 9:10 PM
Post #83 of 85
(296 views)
Permalink
|
On Wed, May 9, 2012 at 8:45 AM, Gavin Hurlbut <gjhurlbu [at] gmail> wrote: > On Tue, May 8, 2012 at 1:25 PM, Paul Kendall <pkendall64 [at] gmail> wrote: >> Would it be at all possible to keep the mythtv specific patches to ffmpeg >> in the external directory so we can attempt to get them included in the >> ffmpeg trunk? I know that some of them are very specific and not likely to >> be accepted, but at least we'll have them available so it should be easier >> to apply each time there's a sync going on. > > Well, I'll be working on that through this release cycle a bit. When > I sync them, I basically do: > a) remove all of FFmpeg > b) add in new sync > c) patch with the delta from before a) to the version of FFmpeg a) was based on > d) fight with it until we find all the discrepancies > e) update all our uses to match the new API > > It's a lot of juggling of branches and merging with squashes, etc. > Rather fun... heh. > > However, I'd like to work on getting that delta earlier, and chipping > off parts to send upstream to make it disappear over time. There are > parts that likely never will go upstream though, but I'm sure parts of > it easily can. Yes, that's why I'd like to see the patches separated rather than an uber-patch merge-of-doom style that happens once a release. If they were individual patches more people could be involved in keeping an eye on what's happening in ffmpeg and how changes there will affect the mythtv patches. Basically I'd like to get a bit more involved in this but it's quite hard with just a pull of ffmpeg git and an uber patch. Cheers, Paul _______________________________________________ mythtv-dev mailing list mythtv-dev [at] mythtv http://www.mythtv.org/mailman/listinfo/mythtv-dev
|