I just wanted to let you folks know about a current discussion going on between various Wine developers. Wine uses Gecko, the Mozilla rendering engine, as a replacement for whatever is in Windows. Currently at issue is how a user of Wine actually gets gecko on their system. It can be downloaded at wine startup, which is problematic for various reasons, or the distro can package it. But what's needed are the actual win32 gecko libraries, not a native Linux version, which sort of involves using mingw and cross-compiling.
The alternative of just sticking the cab in an rpm is obviously not acceptable for Fedora. The relevant thread starts at http://www.winehq.org/pipermail/wine-devel/2009-November/079744.html There's a wiki page http://wiki.winehq.org/Gecko which talks about distros which package Gecok "properly", where that seems to be just dropping a binary in the right place without any regard for how its built or how that conflicts with a distro's goals and requirements, although there is a complaint about this at http://www.winehq.org/pipermail/wine-devel/2009-November/079819.html There's also mention about mingw needing patching to handle building gecko at http://www.winehq.org/pipermail/wine-devel/2009-November/079851.html Feel free to ignore me entirely; I just wanted to bring this to the attention of folks who might understand things far better than I. - J< _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
