From Debian libSDL maintainers, any plans for bugfix release?

[Ryan C. Gordon]

Some structs have grown, but should remain binary compatible with any prior 2.0.x release.

Is there a specific crash? We need to examine this right away. One should not need to recompile apps to move from 2.0.3 to 2.0.4.

--ryan.


> On Jan 14, 2016, at 5:15 PM, Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com> wrote:
> 
> 2015-12-24 17:17 GMT+00:00 Manuel A. Fernandez Montecelo
> <manuel.montezelo at gmail.com>:
>> 2015-12-24 14:49 GMT+00:00 Sam Lantinga <slouken at libsdl.org>:
>>> We do, we were just talking about making an early release for the New Year.
>> 
>> That's great news, thanks!
> 
> Thanks for the new release, we are working on packaging it for Debian.
> 
> We found out that perhaps the ABI is incompatible (changes to structs)
> or even API incompatible, since some variable/macro names seem to have
> changed.
> 
> In this case, if we upload the new version, packages compiled against
> previous versions which were not recompiled can crash.  Packages
> within Debian we can manage to rebuild against the new version, but
> imagine people installing 3rd party applications/games, e.g. from,
> Steam and using Debian.  (Did you receive any complaints about that?)
> 
> 
> So in principle we would be forced to bump to SOVERSION/NAME ourselves
> ahead of upstream, but it would be nicer to stay in sync.  Would you
> mind to release 2.0.5 soon, with a bumped SOVERSION/NAME?
> 
> 
> Cheers and thanks in advance.
> -- 
> Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>