On Wed, Aug 08, 2018 at 02:51:01PM +0100, Peter Maydell wrote:
On 8 August 2018 at 11:49, Daniel P. Berrangé
<berrange(a)redhat.com> wrote:
> SDL1.2 was deprecated in the 2.12.0 release with:
>
> commit e52c6ba34149b4f39c3fd60e59ee32b809db2bfa
> Author: Daniel P. Berrange <berrange(a)redhat.com>
> Date: Mon Jan 15 14:25:33 2018 +0000
>
> ui: deprecate use of SDL 1.2 in favour of 2.0 series
>
> The SDL 2.0 release was made in Aug, 2013:
>
>
https://www.libsdl.org/release/
>
> That will soon be 4 + 1/2 years ago, which is enough time to consider
> the 2.0 series widely supported.
>
> Thus we deprecate the SDL 1.2 support, which will allow us to delete it
> in the last release of 2018. By this time, SDL 2.0 will be more than 5
> years old.
>
> Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com>
> Reviewed-by: Marc-André Lureau <marcandre.lureau(a)redhat.com>
> Message-id: 20180115142533.24585-1-berrange(a)redhat.com
> Signed-off-by: Gerd Hoffmann <kraxel(a)redhat.com>
>
> It is thus able to be removed in the 3.1.0 release.
At least one of the BSD VMs in tests/vm/ is still using SDL1.2.
I think we should update that VM before we drop SDL1.2 support.
(This is probably just a matter of updating the VM image that
is currently stored on patchew somewhere. It would also be
nice if our test infra here had a mechanism for regenerating
that VM image from scratch rather than just being "here's a
disk image blob...")
Oh, I can no idea the images used SDL1, because they're totally opaque
to our git repo :-( Just an external blob with no info about how they
were built. Preferrably we'd at least have a manifest for their contents
in git, even better if there's something to automate building them.
According to
repology.org/metapackage/sdl2/versions all the *BSDs have
SDL2 available to use at least.
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|