cckec / winetricks

Automatically exported from code.google.com/p/winetricks
0 stars 0 forks source link

winetricks does not install into explicitly specified WINEPREFIX #17

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. env WINEPREFIX=<bluh> winetricks firefox4
2. Watch new bottle "firefox4" be created.

Expect firefox4 or other app to install in <bluh> not new bottle.

Original issue reported on code.google.com by ToddM...@gmail.com on 29 Mar 2011 at 12:37

GoogleCodeExporter commented 8 years ago
Winetricks installs apps into their own bottles by default now.
If you want the old behavior, use the --noisolate option.

Original comment by daniel.r...@gmail.com on 29 Mar 2011 at 12:53

GoogleCodeExporter commented 8 years ago
A few more points I should mention:

The new behavior was explicitly requested by Vitaliy on wine-devel, see
http://www.winehq.org/pipermail/wine-devel/2011-January/088332.html

For dlls, settings, and fonts, winetricks defaults to the old behavior, 
since putting a dll in its own bottle doesn't make any sense.

Also, if you want to put a dll (say, flash) in an existing bottle (say, 
firefox), 
you can either do winetricks prefix=firefox flash, or 
WINEPREFIX=$HOME/.local/share/winetricks/firefox winetricks flash.

Original comment by daniel.r...@gmail.com on 29 Mar 2011 at 1:10

GoogleCodeExporter commented 8 years ago
Dan,
  I think it would be a good thing if we can just have
the old behavior, at least for people who know what they are doing. How about a
command line option?

Thanks,

-- todd --

Original comment by ToddM...@gmail.com on 29 Mar 2011 at 1:27

GoogleCodeExporter commented 8 years ago
Oh I see.  You can use --noisolate, but only to install things on the command 
line.
As soon as you use menus, it installs into individual bottles. 

Original comment by ToddM...@gmail.com on 29 Mar 2011 at 1:29

GoogleCodeExporter commented 8 years ago
Yeah, that was per Vitaliy's request to guide inexperienced users firmly 
towards isolating apps in bottles.  It does mean people who know what they're 
doing have to know a little more now, which is unfortunate, but it was the only 
way to prevent a flood of spurious wine problem reports.

Original comment by daniel.r...@gmail.com on 29 Mar 2011 at 1:32

GoogleCodeExporter commented 8 years ago
I grok.  Since I compile and run the git version of wine daily, 
I guess I know what category I fit into.

Original comment by ToddM...@gmail.com on 29 Mar 2011 at 1:36