The road to SDL2 2.0.7
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Sat Nov 4 14:58:31 UTC 2017
Hi,
2017-11-04 14:42 GMT+01:00 Fabian Greffrath <fabian at debian.org>:
> Hi Manuel,
>
> Am Samstag, den 04.11.2017, 00:30 +0100 schrieb Manuel A. Fernandez
> Montecelo:
>> Finally, they are really commited to ABI stability in the last few
>> years, so they treat problematic ABI changes very seriously.
>
> symbols files aren't there to track ABI breaking changes (this would
> require a SONAME bump anyway) but API additions. And, as you have
> already correctly stated, SDL development was rather stangnant around
> the last decade but has recently gained more steam again. So, they
> might be adding more API between releases and we currently have to keep
> track of that manually.
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)?
> Another question: We do currently disable Vulkan support, which was the
> last SDL version this has been tested with?
I seem to remember that I tried to enable them when the support became
available, but that it didn't work (cannot remember the details).
I thought that people would ask for it eventually, which surprisingly,
didn't happen yet.
If it works sure, we can enable it.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Pkg-sdl-maintainers
mailing list