Hi Zhenbo

The proposal does include me (Dean aka Gcenx), the proposal incorporates the current configuration/findings that are used for the packages I'm providing.

However the url you provided is for the homebrew tap now the packages for the actual location see [1]

[1]: https://github.com/Gcenx/macOS_Wine_builds

On Thu, Jul 29, 2021 at 12:39 PM Zhenbo Li <litimetal@gmail.com> wrote:
Hi,

How about using Gcenx's package[1]? If Gcenx's package is okay, I
think we may avoid some duplicate jobs.


[1]: https://github.com/Gcenx/homebrew-wine

On Thu, Jul 29, 2021 at 2:33 AM Gijs Vermeulen <gijsvrm@gmail.com> wrote:
>
> Hi everyone,
>
> Currently, official macOS packages haven't been released since wine-5.7. Thus I'm sending this email on behalf of myself and Dean Greer to officially nominate ourselves to take over the macOS packaging.
>
> There are, however, some specifics we'd like to discuss.
>
> The old packages were built with compatibility for macOS 10.8 and higher, but Apple stopped supporting 10.8 a very long time ago and it would be hard to keep supporting it for the packages.
>
> To get anything lower functional would mean needing to compile all the needed dylibs on the lowest supported version, as package managers don't have prebuilds for these versions.
>
> The ideal solution would be to raise the minimum macOS version to 10.13. This version has only recently lost support and would allow us to ship feature-complete packages.
>
> Metal also started maturing a lot from 10.13 onwards. [1]
>
> Is this something that you could agree too?
>
> Kind regards,
> Gijs & Dean
>
> [1] https://source.winehq.org/git/wine.git/commit/0d23ecd9ec8a0c24e5444e0fc9cf6933cc39c960



--

Sincerely,
Zhenbo Li