================================================= ==> gobby.debian.org / debconf16 / bof / wine <== ================================================= - #827770: wine-development: FTBFS in Ubuntu -> generic issue with using dlopen instead of loading by ld.so what's the appropriate approach in Debian? perhaps discuss on -devel? speak with dpkg / debhelper maintainers? etc? -> debhelper maintainer thinks dpkg is the right place. Existing bugreports: #596715 (dpkg-shlibdeps: Please allow to manually add library dependencies via shlibdeps) #548463 (dpkg-shlibdeps: Please provide a method to compute dependencies for non-elf) - System integration useful: being able to automatically start .exe (under risk consideration so perhaps not enabled by default) not useful: registering files like .txt to be served by a windows program unless user explicitly asks for it - prevent surprising integration effects like notepad opening txt files in the minimal default installation - binfmt wine-binfmt/README.Debian: [...] To configure backend support for that, you'll need to install the wine-binfmt package first and then execute: $ sudo update-binfmts --import wine This change increases the risk of inadvertently launching Windows malware, so please make sure that you understand the security risks before blindly setting this up. - desktop file - Wine menubuilder - Debian alternatives system for the 2 source packages - breaks/replaces - priorities - master wine (in package wine) is not necessarily installed slave wine64 can be handled with file triggers how to handle the binaries in the -tools packages? - alternative dummy package with no-op master wine - or: separate master winegcc/winemaker --> ok to have solution which works for most/has no severe drawbacks, but is easiest to maintain --> Keep alternatives system in wineVERSION, and recommend that package from others with slaves - Is Ubuntu dropping i386? Everyone will at one point https://www.winehq.org/pipermail/wine-devel/2016-July/113784.html https://lists.ubuntu.com/archives/ubuntu-devel/2016-June/039420.html -> open source community is not sure why we still need i386 in long run -> old windows exes might be one reason to keep certain 32bit parts - Ubuntu has an epoch (1:1.6) - winetricks might be useful to use debian packages instead of downloads if the code is available in debian (even if it would need to be additionally compiled for windows) --> huge workload, already discussed a few years ago we already struggle with libwine-gecko