[gst-devel] ffmpeg troubles

[Ronald Bultje]

Hi,

On Tue, 2 Mar 2004, Thomas Vander Stichele wrote:
> We first need to decide whether we want
> a) track upstream ffmpeg cvs in our cvs, and have our cvs be a patched
> version of that (ie, we can still sync with upstream ffmpeg cvs, and
> have one big patch set against that)
> or
> b) track upstream ffmpeg cvs, and have our cvs contain a set of patches
> against that.

I'd go for (B), purely for community reasons.

> The first is slightly easier but doesn't need extra tools; the second
> would require us to use something like quilt for building it from CVS -
> which is a small dependency.

Doesn't sound too bad to me.

> I prefer the second, it makes us better community members :)
>
> Also, I've always felt that the whole patching step should move to
> autogen.sh - it's autogen's job to get the source tree in a state where
> you can just run configure - make - make install, but the source should
> already be ok.  Ie, patching should be done before configure.  In
> gst-plugins this would have caused everyone killing me because it would
> have forced them to rerun autogen for each change to our patchset of
> ffmpeg.  So one of the reasons for moving to gst-ffmpeg was that running
> autoregen.sh could be made a rule from the Makefile when the patches
> change...

I was hoping for someone to propose that - I forgot to say this myself.
WIll you do this? :).

Ronald