> Anyway compiling a static Wine binary should be no problem? Given the way Wine uses some of the requisite libraries, providing static binaries isn't a solution. There are many moving parts to Wine on OS X, and providing Wine only without any of the other reqs will result in a half-usable Wine lacking many features. I use a script to build and install Wine and a number of the recommended prerequisite software packages from source: http://code.google.com/p/osxwinebuilder/ Binary install directories are 200+MB. An OS X binary distribution of Wine would be rather large and would likely present licensing issues as well, as not all required packages are LGPL. In short, use a source build, build script, MacPorts/Fink, WineBottler or Wineskin. A winehq.org-supported binary package isn't likely going to happen soon.
