On 12/12/2015 11:57 PM, Michael Gilbert wrote: > On Sat, Dec 12, 2015 at 5:29 PM, Jens Reyer wrote: >> approach, I'd say this approach is a dead-end. > > Agreed. > >> try not to install wine64 automatically), > > That seems tricky given multiarch weirdness, but I guess may be possible.
To start with, we can change wine Depends to wine32|wine64 and maybe add a small hint in the package description. >> and make it as easy as possible to choose WoW64. > > That is more about doing 32 and 64 bit builds back to back, which is > sort of inefficient, but does avoid some problems with the current > multiarch setup, so it is worth looking at. I'd like to know the difference between doing it this way (a shared WoW64 built with --with-wine64=...), and what we now have if the packages wine, wine32 and wine64 are installed and you set WINEARCH=win64 WINEPREFIX="~/.wine". I didn't run any longtime tests, but I noticed that installing and running 32-bit and 64-bit apps in the *same* arch win64 wineprefix works. Can you call that WoW64 or is it a broken error-prone setup? Greets jre _______________________________________________ pkg-wine-party mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party
