Under the old system, some apps crashed waiting for gecko to install, and users were filing invalid bug reports. Having gecko installed at wineprefix creation avoids this problem.doh123 wrote: I'd rather leave it enabled and have the pop up only show if mshtml is accessed by the program running, like it used to do in older Wine versions, but that doesn't seem to be an option anymore.
Wine Gecko install notification
I think a better solution would be to error that it's missing, and just stop... Let people install, then start over... Expecting the program to wait is odd... Just a "Oops! you don't have gecko installed! See this link for more details. Until you have it installed, your program will not function. Click OK to exit now.
doh123 wrote
doh123 expecting users to be sane not wise. We have learnt better.
Currently vitamin I can cancel the install of gecko and not be asked again. Not going to cure the bad bug reporting problem current system. Reason why I gave the bypass. Ie solution does not work.
There are three possible valid solutions.
Solution 1)
A white list covering gecko missing. Anything not on whitelist before running must have gecko installed. Ie places up dialog to get gecko failure to install display message and fail out completely. Anything on the whitelist does not bother checking for gecko and goes ahead anyhow. Perfectly transparent to end users. Gecko white-listing could be placed in winecfg.
Solution 2)
The other solution also has a messy side. Get rid of gecko as a windows dll instead make it a normal dll.so of wine and a normal part of wine.
Solution 3)
A shared location for common windows dll's between wine and matching registry entries. Again advantage secuirty what reason does any program have to alter gecko files. Less windows parts alterable by rouge programs the better.
This would cure the bug reporting problem while keeping prefixs as small as able. Current solution does not work.
You missed what I was getting at. Wine does get regressions all the time. Even if rebuild works perfectly. ABI/API changes can break stuff.oiaohm wrote:
true, thats when I rebuild the prefix... if its messing up. Usually it seems to work ok though.Also wine versions changing can break applications from time to time.
doh123 expecting users to be sane not wise. We have learnt better.
Currently vitamin I can cancel the install of gecko and not be asked again. Not going to cure the bad bug reporting problem current system. Reason why I gave the bypass. Ie solution does not work.
There are three possible valid solutions.
Solution 1)
A white list covering gecko missing. Anything not on whitelist before running must have gecko installed. Ie places up dialog to get gecko failure to install display message and fail out completely. Anything on the whitelist does not bother checking for gecko and goes ahead anyhow. Perfectly transparent to end users. Gecko white-listing could be placed in winecfg.
Solution 2)
The other solution also has a messy side. Get rid of gecko as a windows dll instead make it a normal dll.so of wine and a normal part of wine.
Solution 3)
A shared location for common windows dll's between wine and matching registry entries. Again advantage secuirty what reason does any program have to alter gecko files. Less windows parts alterable by rouge programs the better.
This would cure the bug reporting problem while keeping prefixs as small as able. Current solution does not work.
