http://bugs.winehq.org/show_bug.cgi?id=17624
--- Comment #3 from Jacek Caban jacek@codeweavers.com 2009-03-05 15:47:13 --- (In reply to comment #2)
(In reply to comment #1)
I know I could install gecko in /usr/local/share/wine,
That's what you should do.
but I've got my reasons for not doing so, and I'm sure others may have similar reasons against it.
It's the only supported way to install Wine Gecko. I don't see any reason to not use it.
There's not a simple way then to test an application _without_ using gecko if it's installed that way. Or am I wrong on that?
You're right (unless you're using native mshtml.dll), but I don't see any reason to test that.
A simple -gecko switch shouldn't be too hard to add...
There is no way to do it with current way that we install the package.
That's why I labeled it as an enhancement ;-).
The current way is fine, IMHO, I'd just like to be able to, say, run $ wine winetest.exe -gecko -c -t $TAG
and not have to click the install button on the gecko prompt.
I still don't think we should do it. It would require changes both in mshtml.dll and winetest.exe for no good reason. I'd call the fact that gecko prompt may be annoying a good thing, as it convinces people to install it right:)