[Pkg-sdl-commits] [SCM] Debian packaging of SDL_image 1.2 branch, master, updated. debian/1.2.11-2-2-g0d19077

Felix Geyer debfx-pkg at fobos.de
Tue Feb 7 10:14:18 UTC 2012

On 06.02.2012 23:14, Manuel A. Fernandez Montecelo wrote:
> 2012/2/6 Felix Geyer <debfx-pkg at fobos.de>:
>> It sets the minimal version of sdl-image1.2 that other package depend on.
>> So if you have another package that links against libsdl-image1.2 it will depend
>> on libsdl-image1.2 (>= 1.2.8).
>> This is necessary when the library adds new interfaces/functions at some point.
>> If you leave it out the dependency is versionless.
>> Most SDL libraries specify an INTERFACE_AGE in confiugre.in. It provides the number
>> of releases where no new interfaces have been added.
>> So MICRO_VERSION - INTERFACE_AGE is the number you need to pass to dh_makeshlibs.
>> For sdl-image that's 11 - 3 = 8.
> So if I understood it correctly, is it a way to manually especify the
> SO versions?

No, the SOVERSION is about binary incompatible changes. If that is bumped we need
to bump the package name.

> If this is the case, several related questions come to mind:
> - If the numbers that they provide can be relied upon, should we try
> to use it for the other SDL libraries?
> - Furthermore, should we devise an automatic way to check/generate
> that (e.g. a script that we can share across our packages)?

I don't know how reliable the numbers are (but I hope they are).

Maybe we should just switch to using symbols files. Basically they contain a list of
exported functions and the version they were introduced. When packaging a new
upstream version you need to watch the build log (dpkg-gensymbols output; lintian
also emits a tag) for new exported functions and add them to the symbols file.


More information about the Pkg-sdl-maintainers mailing list