[Ffmpeg-devel] versions, ABIs and sonames
Michael Niedermayer
michaelni
Sun Jul 24 00:09:47 CEST 2005
Hi
On Saturday 23 July 2005 23:48, Jacob Meuser wrote:
> On Sat, Jul 23, 2005 at 11:43:54PM +0200, Michael Niedermayer wrote:
> > Hi
> >
> > On Saturday 23 July 2005 22:52, Jacob Meuser wrote:
> > > On Sat, Jul 23, 2005 at 10:39:26PM +0200, Michael Niedermayer wrote:
> > > > Hi
> > > >
> > > > On Saturday 23 July 2005 22:20, Jacob Meuser wrote:
> > > > > On Sat, Jul 23, 2005 at 01:00:28AM +0200, Michael Niedermayer wrote:
> > > > > > Hi
> > > > > >
> > > > > > would there be some interrest in having nice standard a.b.c
> > > > > > versions for each lib (libavformat, libavcodec, libpostproc)?
> > > > > > so that an increase of
> > > > > > c means no binary compatibility breakage
> > > > > > b means backward compatibility (added function, ...)
> > > > > > a means no compatibility (function removial, ...)
> > > > >
> > > > > yes, but (c) seems pointless. if there is no compatability issue,
> > > > > then why bother?
> > > >
> > > > the version is stored in encoded files, encoders have bugs (every non
> > > > trivial thing does and an encoder is non trivial) decoders need to
> > > > know which encoder exactly was used if they wish to workaround these
> > > > bugs
> > >
> > > the build number, not the library version, right?
> > >
> > > I think they should be separate,
> >
> > proposal rejected (lack of any arguments)
>
> the argument was in what you cut. why mess with the current use
> of LIBAV*_BUILD? wouldn't changing the way this currently works
> be a major compatability issue?
no
--
Michael
More information about the ffmpeg-devel
mailing list