Hi > I was wondering if somebody is working on this
AFAIK noone on wine-gecko (but I'd be happy to be wrong). For wine-mono there was some work half a year ago, but I haven't seen any results. > In the > past the wine in Debian would at least try to download wine gecko from > official > binary files at winehq.org, and now even that is gone Downloading from a 3rd party (including upstream) is exactly what we want to prevent. Did I miss something, or are you confusing something here? > I know it is know (and documented in README.Debian.gz), but I couldn't find > exact > details what are the current blockers to build it in Debian using debian > libraries. Is it because it is somehow forked vesion of Gecko? It is fully > understandable tho, and can be considered a separate project, as it provides > completly different functionality than gecko. Is it a security support? > Or some other reasons? I guess the main reason is just time, or generally a person who is willing to work on this. One of the main blockers in the past afaik was handling the copyright. The good news is that upstream recently fixed the build with python3 and current gcc - so if these were blockers now is a good time to start again. In the mean time, if you can't help on packaging, the best option probably is to download the installers manually to your user's .cache/wine. Then Wine will check the correct version and checksum of the installer and install it automatically. For wine 4.0 this is: cd ~/.cache/wine wget http://dl.winehq.org/wine/wine-gecko/2.47/wine_gecko-2.47-x86.msi wget http://dl.winehq.org/wine/wine-gecko/2.47/wine_gecko-2.47-x86_64.msi wget http://dl.winehq.org/wine/wine-mono/4.7.5/wine-mono-4.7.5.msi Greets jre
