qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Thomas Huth <thuth@redhat.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 19:09:37 +0200	[thread overview]
Message-ID: <CAL1e-=ikCpJO1bn=AKYSLWb8QNYkf6062ojxn+UN3svXCEQvFA@mail.gmail.com> (raw)
In-Reply-To: <054d5b29-6482-1d71-3866-057dd00cb021@redhat.com>

On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth <thuth@redhat.com> wrote:
>
> On 16/07/2019 13.17, Aleksandar Markovic 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.
>
> What's the problem here? According to
> https://packages.ubuntu.com/xenial/libsdl2-2.0-0 the library should be
> available there.
>

Yes, we, as developers, are good at upgrading, we like flexibility in
our development systems, and naturally want to try latest and greatest
tools and libraries.

However, in QA / build / test environments, the things seem to look
different. Their main concern is stability and repeatibility of their
systems. They don't like updates and upgrades. If a new of library
is available for an OS, this does not mean it will be installed, or it
will be desired to be installed.

It appears that Ubuntu 16.04 came originally with SDL 1.2, and
SDL 2.0 was made available later on.

That is the problem: We make, in my opinion, an incorrect logical
leap here: we assume that if a package is available for an OS, it is
installed (or should be installed) on any instance of an OS.

Yours,
Aleksandar


  reply	other threads:[~2019-07-16 17:10 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
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 [this message]
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='CAL1e-=ikCpJO1bn=AKYSLWb8QNYkf6062ojxn+UN3svXCEQvFA@mail.gmail.com' \
    --to=aleksandar.m.mail@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).