qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] ui/cocoa: Drop workarounds for pre-10.12 OSX


From: Christian Schoenebeck
Subject: Re: [PATCH] ui/cocoa: Drop workarounds for pre-10.12 OSX
Date: Tue, 04 Feb 2020 16:56:29 +0100

On Dienstag, 4. Februar 2020 14:13:35 CET Peter Maydell wrote:
> > 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.
> 
> But is anybody actually going to fix pre-10.12 support? They've
> had six months so far... If we had a good sized body of developers
> taking active care of how well QEMU on OSX works, I would be
> entirely happy for them to decide amongst themselves what they
> thought was a reasonable version support policy for OSX. But
> we just don't.

No idea of course whether somebody will fix it. It's just that young people 
tend to have fairly old Macbooks (i.e. >= 10 years) since younger models in 
that universe are often outside of their budget.

> I wouldn't object to a configure check if anybody wanted to write
> a patch to add one.

Like I said, I don't care much, but if you want I can send a small configure 
script patch of course. That's not a big deal. So roughly you want a warning 
for pre-10.14 and error out on pre-10.12, right?

G3, if you want to take care about sending this patch instead, very much 
appreciated of course. :)

> > > "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
> 
> Indeed, and none of those is the 10.11-and-earlier that this patch
> drops attempts to cater for. The patch does still keep 10.12 and
> 10.13 support alive, even though it's not strictly required by
> our support policy, because building for those host versions does
> in practice still work.

Sure, I just wanted to bring that to your attention. In fact security support 
policy by Apple is somewhat unpredictable. There is no official statement 
which branches are covered by security fixes. They simply decide on a case-to-
case basis whether or not to release updates for certain old release branches.

Best regards,
Christian Schoenebeck





reply via email to

[Prev in Thread] Current Thread [Next in Thread]