> Dean, do you know if there are many users of your ports on 10.13/10.14?

The main Ports no longer support macOS Sonoma (wine-stable, wine-devel & wine-staging), I do provide alternative Portfiles that work for all legacy versions of macOS from 10.6.8 to 10.14.

It’s also a nightmare buiding on 10.14 thanks to some macports maintainers not believing that Xcode10 Command Line Tools provided a headers package that enabled the ability to build for i386 & x86_64.

> Your MacPorts packages still support those, right?

If your referring to the Winehq packages installable via brew cask system?, no those only support macOS Catalina or later, there’s really been no complaints.

Something else to keep in mind is these legacy versions of macOS also have expired certs.

On Mon, Apr 15, 2024 at 7:15 PM Brendan Shanks <bshanks@codeweavers.com> wrote:

> On Apr 11, 2024, at 11:14 AM, Tim Clem <tclem@codeweavers.com> wrote:
>
> I would prefer 10.15 in particular so we could drop support for native (i.e. macho) 32-bit binaries. That would allow us to use modern Obj-C runtime features (e.g. auto-synthesis) and eventually consider ARC. It's also worth noting that winehq's gitlab CI runs 10.15.

I’m totally on board with raising the minimum version to 10.13.
I’m slightly more hesitant to go to 10.15, just since there are a lot of Macs and software that can only run (on) 10.13 or 10.14. But Firefox, Chrome, and Steam have all raised their minimum versions to 10.15 in the last year (and they were among the last to do so). We can’t support them forever, and anyone who needs to run 10.13 or 10.14 can keep running Wine 9.0. Ultimately I think I’m good with 10.15, although I’m curious whether Dean has any more info.

Dean, do you know if there are many users of your ports on 10.13/10.14? Your MacPorts packages still support those, right?

(Also for those who aren’t aware, CrossOver requires 10.15 starting with this year’s version 24).

Brendan