http://bugs.winehq.org/show_bug.cgi?id=19182
liquider liquiderz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |liquiderz@gmail.com
--- Comment #66 from liquider liquiderz@gmail.com --- xnitropl's patch gives a clue.
The most casual Wine user may WANT their XDG menu populated with launchers to newly installed software, but NOT WANT their host system's file associations modified. In this case, the FAQ-solution about disabling winemenubuilder.exe does not apply.
Instead, how about Wine upstream distribution, for the benefit of all, sets winemenubuilder.exe Service to run without -a switch by default?
winemenubuilder.exe with -a switch, as documented in the source, updates file associations. Should one, e.g. a popular distribution maintainer, wish their winemenubuilder to build freedesktop menus but not snatch mimeapps, the Services group in the systemwide wine.inf file can be amended to only ever run "winemenubuilder.exe -r".
Is this correct? Is "winemenubuilder.exe -a" ever run regardless of this setting (provided a user doen't have a already-tainted $WINEPREFIX/system.reg file)? If not, the majority of wine users strongly agrees there should be an option to build menus without changing mime associations.