Enhancement: disable winemenubuilder and desktop integration

[GoogleCodeExporter]

It would be nice to be able to disable winemenubuilder and desktop
integration in one step instead of having to do it in winecfg every time I
test an app just to help out someone on the forum.

Original issue reported on code.google.com by dime...@gmail.com on 27 Oct 2009 at 4:41

[GoogleCodeExporter]

OK.  Why do you disable them -- does it make things faster, or what?

Original comment by daniel.r...@gmail.com on 29 Oct 2009 at 4:09

[GoogleCodeExporter]

Actually, it doesn't completely work. I need to file a wine bug once I've 
verified on
a clean system, but mime type integrations are still made if it's disabled.

Dan, it gets really annoying to have tons of shortcuts installed in your app 
menu,
along with mime-types added for tons of random programs.

Original comment by austinenglish@gmail.com on 29 Oct 2009 at 4:31

• Changed state: Started
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Dan: Most of the time when I run an installer these days it's just to test 
something,
either to help someone on the forum with some random app or to retest the apps I
maintain in a new version of Wine. I don't want menu entries and mimetypes 
added for
apps I'm not going to keep, and in the case of mimetypes, well, I'd really 
rather
Wine not mess with them at all, but even if I did want entries for the apps I 
do use,
I wouldn't want multiple entries for the same filetypes (Wine just keeps adding 
more,
even if they're already there).

Desktop integration is really a separate issue, and perhaps should be a separate
winetrick. I'm talking about the links that are checked by default on the 
desktop
integration tab in winecfg. The problem is that with those links enabled, some 
apps
create directories for their data outside of the wineprefix, and I have to find 
and
delete those in addition to the test wineprefix after I'm done testing. It 
would be
nice to be able to disable them all in one step rather than having to uncheck 
them
one by one. 

Austin: you're right about mimetype integrations still being made even with
winemenubuilder disabled. I recently had to delete multiple entries from KDE
associating WMV/WMA files with WMP9, and I did have winemenubuilder disabled 
when I
installed it. 

Original comment by dime...@gmail.com on 29 Oct 2009 at 5:13

[GoogleCodeExporter]

dimesio, those desktop integration links are disabled by "winetricks sandbox" in
recent versions.

As for the mimetype integrations, I feel your pain.

Original comment by eibol...@gmail.com on 29 Oct 2009 at 6:21

[GoogleCodeExporter]

I noticed the new sandbox option, but it's overkill for my purposes. I have a
separate /data partition, and I want Windows apps to be able to access it, even 
apps
I'm just testing. I just don't want them thinking that my home directory is My
Documents, My Pictures, etc. and installing stuff there by default.

Original comment by dime...@gmail.com on 29 Oct 2009 at 8:08

[GoogleCodeExporter]

You sure? Heh, removing the symlinks is the only thing the sandbox option does, 
the
current help text is a bit optimistic. You still have access via the Z: drive 
as usual.

Original comment by eibol...@gmail.com on 29 Oct 2009 at 10:34

[GoogleCodeExporter]

You're right; I hadn't realized that. The help text, and the "sandbox" 
designation,
are *very* misleading. You might want to consider toning it down so users don't 
get a
false sense of security.

Original comment by dime...@gmail.com on 30 Oct 2009 at 4:04

[GoogleCodeExporter]

The plan is rather to extend it over time, with things like disabling 
winemenubuilder
and mimetype integration, and perhaps remove the Z: drive. How are you doing 
this at
present?

Original comment by eibol...@gmail.com on 30 Oct 2009 at 7:00

[GoogleCodeExporter]

I've been setting winemenubuilder.exe to disabled in winecfg. That takes care 
of the
menu items, but currently doesn't stop mimetypes from being added. Those I just
periodically clean out. 

Original comment by dime...@gmail.com on 30 Oct 2009 at 8:06

[GoogleCodeExporter]

Dimesio, it's a bit easier to set:
export WINEDLLOVERRIDES="winemenubuilder.exe=d"

in $HOME/.bashrc (or whatever shell you're using)

Original comment by austinenglish@gmail.com on 12 Dec 2009 at 7:07

[GoogleCodeExporter]

Setting it in .bashrc works for things I run directly, but winetricks doesn't 
respect it. 

Original comment by dime...@gmail.com on 4 Jan 2011 at 7:20

[GoogleCodeExporter]

Try overriding XDG_CONFIG_HOME and XDG_DATA_HOME.  That ought to do it!

Original comment by daniel.r...@gmail.com on 6 Mar 2011 at 3:01