> On Jun 11, 2017, at 11:10, Mojca Miklavec <[email protected]> wrote: > > On 11 June 2017 at 10:32, Ryan Schmidt <[email protected]> wrote: >> >>> On Jun 10, 2017, at 23:29, Dave Horsfall wrote: >>> >>> I just did "port install wine", and it seeme to be (re)installing half the >>> known universe... Is this to be expected? Installinh it on Debian was >>> quite simple - just an "apt-get" or two. >> >> MacPorts Wine is 32-bit. Usually, your other ports will be installed 64-bit. >> So when you install wine, it will reinstall all of its dependencies with the >> universal variant, so that they contain both 32-bit and 64-bit code. >> >> On Debian and other Linux systems, wine may already be 64-bit, which might >> explain why you didn't have a similar problem there. There has been a >> platform-specific reason why wine must be 32-bit on macOS, but allegedly >> that reason no longer applies as of wine 2.0. Someone has worked on adding >> 64-bit support to the wine port: >> >> https://trac.macports.org/ticket/53651 >> >> I have not evaluated this. > > Would you be OK if some other MacPorts developer takes a look, tests > the ports and commits the changes from the following two PRs? > > https://github.com/macports/macports-ports/pull/374 > https://github.com/macports/macports-ports/pull/442 > > Mojca
Sure. 72-hour maintainer timeout rule.
