[FFmpeg-devel] [PATCH] Merge libavcore into libavutil

Stefano Sabatini stefano.sabatini-lala
Sun Feb 13 16:53:20 CET 2011

On date Sunday 2011-02-13 16:06:10 +0100, Luca Barbato encoded:
> On 02/13/2011 03:53 PM, Kostya wrote:
> > On Wed, Feb 09, 2011 at 07:36:15AM +0100, Reinhard Tartler wrote:
> >> It is pretty hopeless that other considerable projects will adopt
> >> libavutil alone in other projects. Projects that need small footprint
> >> are better off with more specialized libraries such as gnulib or rather
> >> just copy the necessary parts that they need. With this in mind, nobody
> >> is helped by having libavutil and libavcore split. In order to ease
> >> maintenance inside and around FFmpeg and to reduce confusion where to
> >> put common code, avcore's functionality is merged (back) to avutil.
> > 
> > I think that's right thing to do and patch looks ok to me.
> Just to be clear, the patch looks fine and we should try to first agree
> on what's in what before splitting libraries in the future.

This situation is quite paradoxical, as when the library was created
no-one objected to it, or I wouldn't have committed the change in the
first place.

Now I know that my question will be ignored again, but who is going to
approve such patches according to the new "regime", considering that
there is the file maintainer veto and/or there is no general agreement
amongst the developers?

The fact that there are no clear rules is generating tension, any
decision system would be better than this, a vote, a dice cast, asking
to the fist guy passing around the corner, so please resolve this once
and for all.

As for me I already stated which is my position (after some thought
the --configurable thing can't work with public API functions), but
then I don't think that having a merge is *sooo* unacceptable if most
developers prefer that way, and I can see the advantages of that
FFmpeg = Frenzy Funny Majestic Pure Exciting Gangster

More information about the ffmpeg-devel mailing list