http://bugs.winehq.org/show_bug.cgi?id=19182
--- Comment #45 from Martin Misuth et.junk@ethome.sk 2012-08-01 08:20:50 CDT --- Excuse me I was not present to discuss this. I am coming from Bug 31194.
Well it's nice mine got closed, but issue really wasn't solved.
Seems like adding correct variable to profile and exceptions to libraries listbox fixes this issue, but it simply DOESN'T SOLVE the problem.
**User should have a clearly understandable choice to completely disable integration in the correct winecfg menu, if he/she wants!**
How many of not so advanced users (think ubuntu), who would still like to send wine integration to hell, are gonna mess with their shell profile or manually add exceptions to libraries listbox?
Really guys, don't come on me with windows crap a la: "on windows aps can't disable integration bla bla"
Let crappy wine explorer handle it's own verbs and associations, but don't push on normal users this mime db disturbance of the HOST shit.
More and more users are really unhappy with wine overtaking their native desktop, and just because they are not as vocal as me right now, doesn't make the problem go away.
Most of them were completely clueless that winemenubuilder is the culprit, and one of my acquintances even removed wine altogether to sort this shit out.
Please fix this by providing normal visible and sensible option and give users choice, not everybody wants wine to overake his computer Microsoft fashion.
What wine does with it's registry is it's problem but don't crap my mime acssociations please.
I tolerated this shit 2 years but now i am really fed up.