On Wed, Nov 21, 2018 at 05:53:50AM -0500, Programmingkid wrote: > > > On 13 November 2018 at 12:12, Programmingkid <programmingk...@gmail.com> > > wrote: > >>> On Nov 11, 2018, at 4:35 PM, Berkus Decker wrote: > >>> These changes are ought to work on OSX 10.6, although I don?t have a > >>> machine handy to test it. > >> > >> I have Mac OS 10.6 available for testing. > > > > This is perhaps a good point to ask the question: is retaining > > support for 10.6 still worth the effort ? It was released 9 > > years ago and has been unsupported by Apple for nearly 5 years. > > > > qemu-doc.texi's "Supported build platforms" section says: > > # The project supports building with the two most recent versions > > # of macOS, with the current homebrew package set available. > > > > which would be High Sierra (10.13) and Mojave (10.14) only. If you > > widened that to "all versions still supported by Apple" it would add > > Sierra (10.13) to the list. > > > > Given how few upstream developers we have who care about OSX, > > I think it is not very useful to spend that effort on trying > > to retain support for ancient versions of it. > > > > thanks > > -- PMM > > Mac OS 10.6 is a very good operating system. I much rather we simplify > the patch rather than drop support for this excellent operation system > just because it is a few years old. I suspect rewriting the the patch > to use performSelectorOnMainThread:withObject:waitUntilDone: would be > a simpler and better patch.
Whether 10.6 is a good OS or not is not really relevant. There are a great many good operating systems that are no longer supported by either QEMU or their vendors. It isn't a sensible use of limited project resources to support an ever growing set of old OS versions. This is why we formalized our intentions wrt support for old operating systems to limit it to a reasonable number of versions that are currently supported by their respective vendors. We achieve a balance of keeping enough platforms supported to suit 90+% of our expected users, while keeping the set of platforms small enough that we can reasonably expect to test them well & be able to utilize new features in a timely manner. The goal of the support statement is further to stop endless debates about whether we can use new features that aren't available in certain old OS releases. The answer is now that we can use whatever features provide the best solution for the OS versions that we explicitly target. If that causes us to drop an old OS as a side-effect that is entirely fine. > I have tried the patch out already on Mac OS 10.12 and it did not work. > The firmware never runs and the Machine menu does not populate. I do > not believe this patch is worth dropping the support of many versions > of Mac OS X. Of course I'm not suggesting merging the patch if it doens't even work for modern macOS versions. We should clearly fix the patch to work as needed on our supported versions of macOS. 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 :|
