https://bugs.winehq.org/show_bug.cgi?id=42037
--- Comment #3 from Michael Müller michael@fds-team.de --- The idea behind the official Wine packages is to ship a mostly unmodified version, to make sure that no problems are introduced by third party patches or software. On macOS this does not completely work out though as Wine is not installed to /usr/bin/wine. In order to start Wine it is therefore necessary to correctly set the PATH environment variable or specify the full path. This might be a bit difficult for some users, so the packaging files for macOS contain some scripts and an executable to launch a preconfigured Wine Terminal through Launchpad.
I don't mind accepting patches which improve those scripts and make it easier for people to use Wine (maybe even a minimal GUI), but shipping or installing Winetricks is not an option. Winetricks is not part of WineHQ and most probably never will be, due to legal reasons (some winetricks recipes install software that require the user to own a windows license). If you have any other ideas or improvements, you can take a look at the existing scripts [1] (mostly wrapper.m and payload-wine/Contents/Resources/start/bin/) and open a new bug report or a pull request at github.
[1] https://github.com/wine-compholio/wine-packaging/tree/master/macosx/wine/osx...