http://bugs.winehq.org/show_bug.cgi?id=17624
Summary: Add option to automatically install gecko when prompted Product: Wine Version: 1.1.16 Platform: PC URL: http://test.winehq.org/builds/winetest-latest.exe OS/Version: All Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com
Currently, winetest checks if gecko is installed, and if not, prompts the user to install it. While that's great, it makes it a bit hard to automate testing.
One can you 'winetricks gecko' to do this, but since it doesn't want to work for me on OpenSolaris, that's a bit of a pain as well.
I know I could install gecko in /usr/local/share/wine, but I've got my reasons for not doing so, and I'm sure others may have similar reasons against it. A simple -gecko switch shouldn't be too hard to add...
http://bugs.winehq.org/show_bug.cgi?id=17624
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com Status|NEW |RESOLVED Resolution| |WONTFIX
--- Comment #1 from Jacek Caban jacek@codeweavers.com 2009-03-05 14:53:33 ---
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.
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. The installer code is in mshtml.dll and all winetest does is it tries to create HTMLDocument object, so it's exactly the same scenario as any other app using MSHTML.
http://bugs.winehq.org/show_bug.cgi?id=17624
--- Comment #2 from Austin English austinenglish@gmail.com 2009-03-05 15:31:08 --- (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?
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.
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:)
http://bugs.winehq.org/show_bug.cgi?id=17624
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com 2009-03-05 17:00:00 --- (In reply to comment #3)
(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.
Sometimes it's helpful to test for some applications that only use gecko for minor features. Guess I'll just bite the bullet and install it globally...
http://bugs.winehq.org/show_bug.cgi?id=17624
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|All |other
--- Comment #5 from Austin English austinenglish@gmail.com 2012-02-23 15:21:19 CST --- Removing deprecated 'All' OS.