From wine-devel mailing list (http://www.winehq.org/pipermail/wine-devel/2007-October/060058.html): <quote> As you probably have noticed, downloading Gecko on first use confuses users. Now, with last week patches, there is an other way to do it, transparent for users. MSHTML code looks for cab file in $data_dir/gecko (that is usually /usr/share/wine/gecko). Alternatively, if you run Wine from build dir, it looks for $build_dir/../gecko. Wine checks it both in wineprefixcreate and, if Gecko is not installed, on first usage. It means that if you download wine_gecko-0.1.0.cab from SourceForge and put it in the right place, you will no longer have to care about installing Gecko. Now, it's time to consider Linux packages to simplify its use. In Gentoo it may be a separate USE flag, but for other distributions that don't support such things, we'll need a separate package. Such package will need only one file placed in the right place, so it should be easy to do and maintain (I don't expect versions to change often). Are Wine packagers interested in creating Gecko packages? </quote> Reproducible: Always Steps to Reproduce:
i'm not familiar with "Gecko" at all ... could you describe it real quick or point me to some info about ? just wondering if it makes sense to force it on for everyone or to make a local USE flag ...
Gecko is the HTML rendering engine developed by Mozilla and used by Firefox and SeaMonkey. It is used in Wine to render Windows Help Files which are essentially HTML. http://en.wikipedia.org/wiki/Gecko_(layout_engine)
That's right, although it's not limited to help files (help files are just one component using it). Gecko is used to implement MSHTML, which is needed by many apps to render HTML. Wine also contains a very simple implementation of IE, which may be used for tests. Currently, if you run $ wine iexplore http://www.gentoo.org on the fresh Wine prefix, you will see a dialog offering downloading Wine Gecko (Gecko build packaged for Wine as a .cab file). With wine_gecko-0.1.0.cab file placed as I've described in the quoted mail, Wine will automatically use it.
i see a .cab and a .source.tar.bz2 ... could you expound on this a bit ? i'm wondering if making a "wine-gecko" package makes sense for wine to optionally depend on ...
.source.tar.bz2 is, as the name says, the source of the package. it is really Mozilla source with tiny changes. It needs MSVC in Windows to compile, so it's not useful for Gentoo. .cab file is the compiled package. It will be used by Wine as is - it just has to be placed in the right place. No extract nor configuration is needed. IMO it's best to add "gecko" USE flag, not a separate package. I'd vote to make it set by default.
0.9.52 should do it now, thanks for the report
