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

[Diego Biurrun]

On Tue, Feb 08, 2011 at 09:08:27PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Monday, 07 February 2011 at 22:11, M?ns Rullg?rd wrote:
> > Stefano Sabatini <stefano.sabatini-lala at poste.it> writes:
> > 
> > > On date Monday 2011-02-07 14:39:06 -0500, Ronald S. Bultje encoded:
> > >> 
> > >> On Mon, Feb 7, 2011 at 2:34 PM, Stefano Sabatini
> > >> <stefano.sabatini-lala at poste.it> wrote:
> > >> > Use case: hey, I need a small library for {RNG/base64/checksum/CPU
> > >> > detection/expression evaluation} but I need it to have a small
> > >> > footprint, what can I use?
> > >> 
> > >> Then we should allow selectable units, similar to
> > >> --disable-decoder=XYZ or --disable-encoders in lavc, as part of lavu.
> > >> Randomly splitting it in 10 sublibs is not an appropriate solution.
> > >
> > > This is a valid point. But yet there is the API/ABI breakage problem
> > > (and which is the best timing for doing it, just after/before
> > > release),
> > 
> > The previous release did not include libavcore.  Merging it back
> > before the next release would cause the least trouble for release
> > users.
> 
> And yet you actively discourage using releases and encourage using
> SVN/git HEAD instead. Which makes your statement kind of hypocritical.

Please refrain from such ad-hominem attacks, thank you.

Mans was stating a simple fact: Release users are not (yet) affected by
the merge.  A merge before the release makes no difference to HEAD users,
but simplifies life for release users.  Thus, if the merge is to happen,
then before the release is the right moment.

Diego