[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    today's git broke winetricks gecko :-(
From:       <Joerg-Cyril.Hoehle () t-systems ! com>
Date:       2009-11-30 15:57:10
Message-ID: 47CC5ABB01651443A88DB8EC5B4D657B037AE910 () S4DE8PSAANK ! mitte ! t-com ! de
[Download RAW message or body]

Jacek Caban wrote:
>You should understand, that we don't want users to have problems due to 
>*lack* of Gecko.
Fair enough.

> Instead you just said that 
>you pollute winetest results with your bad configuration.
Are you being rude or what?
I've not been polluting anything.  I've -- quite simply -- used for
years a (seemingly) perfectly reasonable and supported[*] configuration,
namely a Wine without Gecko.  Austin English too has provided
"ae-nogecko" test data for ages.

[*] "you can avoid problems" in WineGecko is not at all
the same as "It is highly recommended that you install Gecko in order
to avoid mysterious failures even with applications that do not seem to
have anything to do at all with HTML.  That's not how Windows works."

Well, as I said  earlier, my next Mac testdata will use Gecko.

I'd appreciate if the WineGecko page could be augmented with a recommendation
about how to add Gecko to an existing .wine.  I'm used to
rm .wine/.update-timestamp
wine winecfg
Is that fine?

Regards,
	Jörg Höhle.



[prev in list] [next in list] [prev in thread] [next in thread]