[Ffmpeg-devel] versions, ABIs and sonames
Sat Jul 23 22:20:14 CEST 2005
On Sat, Jul 23, 2005 at 01:00:28AM +0200, Michael Niedermayer wrote:
> 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?
> and just to clarify, yes for cvs not the yearly releases, the later would be
> pointless as they always break compatiblity entirely
why remove it for the release? what harm is it? some packaging
systems actually use (and expect) .so versioning.
> if theres some interrest then ill change the meaning of the current
> LIBAV*_BUILD number from integer to aabbcc 3 element version vector or do we
> need more then 100 of each?
I would say use .so versions and keep the build numbers as integers.
the build numbers would serve the purpose of (c) from above.
<jakemsr at jakemsr.com>
More information about the ffmpeg-devel