The road to SDL2 2.0.7

[Fabian Greffrath]

Am Samstag, den 04.11.2017, 15:00 +0100 schrieb Felix Geyer:
> Only in the sense that we have to manually apply SDL_INTERFACE_AGE
> from
> configure.in to SHLIBVER in debian/rules.

I see, but then even the packages not using any of the recently added
API get a dependency on the latest SDL.

> At least for libraries that is exactly the same set of flags.

How about bindnow?

> What's the benefit of that tracking?
> 
> That if a programA depends on SDL, and gets a new upstream version
> and
> compiles against (say) SDL 2.0.8 using new API functions, that then
> it
> fails to install in systems with <2.0.8  (or that it has to upgrade
> in
> lock-step)?

Yes, right. A program only using API that was already present in SDL
2.0.4 gets a dependency against that version, whereas a program that
uses some of the newer API will get a dependency against that newer
version of SDL.

> I thought that people would ask for it eventually, which
> surprisingly,
> didn't happen yet.
> 
> If it works sure, we can enable it.

Not sure if it works, but probably it compiles now (have not tested)?

 - Fabian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-sdl-maintainers/attachments/20171104/59902840/attachment.sig>