qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "berrange@redhat.com" <berrange@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [QUESTION] SDL 1.2 support
Date: Tue, 16 Jul 2019 12:41:26 +0100	[thread overview]
Message-ID: <CAFEAcA9D9-LmOxoSHyibqprKofAWAvthCYYRe==e=F_ZjjpZ5w@mail.gmail.com> (raw)
In-Reply-To: <CAL1e-=jiySpoypabXMkUsO=2pqgUrRxUhac=JM_V=2sn2LPhWA@mail.gmail.com>

On Tue, 16 Jul 2019 at 12:17, Aleksandar Markovic
<aleksandar.m.mail@gmail.com> wrote:
>
> Hello, Gerd, Daniel, and others involved.
>
> I have multiple reports from end users that say that transition from
> SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
> In that light, they don't appreciate removing SDL 1.2 support from
> QEMU. The most notable example is Ubutnu 16.04, where it looks there
> is no way of installing SDL 2.0 that does not involve complete OS
> upgrade, which, for various reasons, many are not willing to do.

One of my build test machines is an Ubuntu 16.04 system
(specifically 16.04.6 LTS), and it has SDL2 installed
and the built test includes compiling the SDL2 UI. So I'm
not sure what's happening with your end users -- do you have
more detail on what their setup is and what isn't working for them ?

> It looks to me that depreciation of SDL 1.2 was a little premature. My
> humble opinion is that we should not look at release dates of
> libraries when we deprecate them, but release dates and end-of-support
> dates of major Linux distribution that include them.

That is indeed the way our deprecation policy is supposed to
work -- we care about the versions of libraries that distros
have shipped in their LTS, not what the upstream library
release schedule is.

thanks
-- PMM


  reply	other threads:[~2019-07-16 11:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 11:17 [Qemu-devel] [QUESTION] SDL 1.2 support Aleksandar Markovic
2019-07-16 11:41 ` Peter Maydell [this message]
2019-07-16 17:48   ` Aleksandar Markovic
2019-07-16 18:30     ` Peter Maydell
2019-07-16 11:50 ` Daniel P. Berrangé
2019-07-16 11:54 ` Thomas Huth
2019-07-16 17:09   ` Aleksandar Markovic
2019-07-16 17:44     ` Daniel P. Berrangé
2019-07-16 18:06       ` Aleksandar Markovic
2019-07-16 18:16         ` Daniel P. Berrangé
2019-07-17 18:34       ` Aleksandar Markovic
2019-07-17 18:57         ` Eric Blake
2019-07-17 19:20           ` Aleksandar Markovic
2019-07-17 19:57             ` Eric Blake
2019-07-16 18:20     ` Philippe Mathieu-Daudé
2019-07-18  6:20       ` Philippe Mathieu-Daudé
2019-07-29 10:36         ` Philippe Mathieu-Daudé
2019-07-29 11:27           ` Aleksandar Markovic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFEAcA9D9-LmOxoSHyibqprKofAWAvthCYYRe==e=F_ZjjpZ5w@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).