On 28.10.18 18:45, Alexandre Viau wrote: > On 2018-10-28 12:49 p.m., Jens Reyer wrote: >> great to see you working on wine-mono (although personally I never >> needed it). > > Is this because you use Microsoft's proprietary implementation?
I don't use Wine very often, and the apps that I use it for, just don't require it. Last time I needed it, it was for Adobe Digital Editions - back then I used the proprietary solution (iirc wine-mono didn't work for it, not sure). >> On 28.10.18 01:22, Alexandre Viau wrote: >>> Also, I notice that C:\\windows\mono exists in prefixes by default, even >>> when wine-mono is not installed. That is expected? >> >> I've seen empty gecko/mono folders before, but didn't worry/investigate. > > Mono's folder is full, however. It contains many .exes and .dlls. > > Can you reproduce this? > > - rm -rf ~/wine > - wine explorer > - browse c:\\windows\mono Tested: No, no mono folder at all. > It could be that wine picks-up wine-mono from an unknown location on my > system without me noticing... Check for ~/.cache/wine/wine-mono-4.7.1.msi. That will be installed automatically and result in a full c:\\windows\mono folder. You might have downloaded it accidentally if you used another Wine (not from Debian, where we removed the installer download). All search paths (see the gecko and mono entries in our Debian.readme): - /usr/share/wine-mono/ - /usr/share/wine-development/mono/ (only if you are using wine-development) - /usr/share/wine/mono - $XDG_CACHE_HOME/wine/ - $HOME/.cache/wine/ (if XDG_CACHE_HOME is not set) >>> On a side note, Wine has a feature that installs mono automatically when >>> it is in /usr/share/wine-development/mono. However it checks for shasums >>> and exact filenames so we will probably have to patch it in Debian. >>> (dlls/appwiz.cpl/addons.c). That said, it shouldn't prevent us from >>> installing it manually with ``wine64 msiexec /i winemono.msi``. >> >> When I worked on disable/addons-download.patch I figured that the >> checksums are only checked if the wine-gecko/mono installer is loaded >> from home, but not when loaded from /usr/share. That's what I put into >> README.debian. Please verify. > > I'll verify when I get to that. I read it quickly and never really > managed to get it installed from /usr/share, but before I jump to the > conclusion that it didn't work, I want to find a reliable way to test > whether or not wine-mono is installed. > > Looking at wine uninstaller isn't enough as it produces results that are > hard to explain, like mono/gecko showing as present even when they were > not installed. Ok, I haven't looked into this more deeply. Make sure you don't have mono/gecko installed accidentally, see above. Which Wine are you using? >> btw, the command is always "wine" (not wine64 or wine32), e.g. "wine >> msiexec /i winemono.msi". Wine will then figure out internally which >> Wine loader to use. This is true both upstream and in Debian. > > Sure, I specified wine64 because this is what WineHQ's wiki specifically > says so, for 64bit prefixes: > - https://wiki.winehq.org/Mono > > It also yields totally different results, if we trust wine uninstaller. > Note that the .msi is supposed to install both 32 and 64bit versions of > mono. It could be that installing it with just wine will install only > the 32bit version and skip the 64bit version. Ok, that's new to me. I'd need to look into that more deeply (no promise, tell me if you need more help). Greets jre
