qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	G 3 <programmingkidx@gmail.com>
Subject: Re: [PATCH] ui/cocoa: Drop workarounds for pre-10.12 OSX
Date: Tue, 04 Feb 2020 14:03:27 +0100	[thread overview]
Message-ID: <15653420.4VsaQd57cB@silver> (raw)
In-Reply-To: <CAFEAcA8c6_ESiGCY5somH7LiDYGhW37QCAJDAUZ545b+VDoJSQ@mail.gmail.com>

On Dienstag, 4. Februar 2020 11:15:36 CET Peter Maydell wrote:
> On Mon, 3 Feb 2020 at 19:59, G 3 <programmingkidx@gmail.com> wrote:
> >> Our official OSX support policy covers the last two released versions.
> >> Currently that is 10.14 and 10.15.  We also may work on older versions,
> >> but
> >> don't guarantee it.
> >> 
> >> In commit 50290c002c045280f8d in mid-2019 we introduced some uses of
> >> CLOCK_MONOTONIC which incidentally broke compilation for pre-10.12 OSX
> >> versions (see LP:1861551). We don't intend to fix that, so we might
> >> as well drop the code in ui/cocoa.m which caters for pre-10.12
> >> versions as well. (For reference, 10.11 fell out of Apple extended
> >> security support in September 2018.)
> >> 
> >> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> >> ---
> >> The bug report is recent, but this was also pointed out on
> >> the mailing list back in June 2019. Since nobody has cared
> >> to try to fix it, we clearly don't care about 10.11 in
> >> practice as well as in theory.]
> > 
> > Why would you want to inconvenience the Mac users? This is unacceptable.
> > I and many other Mac users would not be able to use the newer versions of
> > QEMU anymore. Keeping Mac OS 10.10 and up support doesn't seem like a
> > burden. This patch should not be applied.

Not that I really care, but I also wonder whether that would be an appropriate 
action to remove this code, as it does not seem to impose anything negative to 
retain it.

> The rationale is in the commit message -- QEMU *already* does not
> build on 10.11, and it has not done so for more than six months, and
> none of these Mac users has submitted a patch to try to fix it.

How about handling this with an error message at configure stage instead? 
Removing this code does not increase the chance for somebody going to fix 
pre-10.12 support.

> "Last two versions only" is our support policy for OSX for a reason,
> and the reason is that there just aren't very many people running
> OSX and actively working on QEMU. Of those, even fewer will
> be still running OSX versions that are no longer being supported
> for security fixes by Apple.

Apple currently seems to maintain 4 macOS release branches with security fixes 
(10.15.x, 10.14.x, 10.13.x, 10.12.x):
https://en.wikipedia.org/wiki/MacOS_Sierra#Release_history

Best regards,
Christian Schoenebeck




  reply	other threads:[~2020-02-04 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.343.1580584897.2411.qemu-devel@nongnu.org>
2020-02-03 19:59 ` [PATCH] ui/cocoa: Drop workarounds for pre-10.12 OSX G 3
2020-02-04 10:15   ` Peter Maydell
2020-02-04 13:03     ` Christian Schoenebeck [this message]
2020-02-04 13:13       ` Peter Maydell
2020-02-04 15:56         ` Christian Schoenebeck
2020-02-01 17:05 Peter Maydell
2020-02-12 12:26 ` Gerd Hoffmann

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=15653420.4VsaQd57cB@silver \
    --to=qemu_oss@crudebyte.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.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).