Hello,
I sort of made a mess out of my ~/.wine folder and want to start over with a fresh one. If I delete the ~/.wine folder and run winecfg, will a new one be created?
TIA
Create a New .wine Directory
-
Dan Kegel
Create a New .wine Directory
On Fri, Feb 29, 2008 at 12:11 PM, Juan Largo <[email protected]> wrote:
running any wine app will do it. Even running 'wine foo' will do it
(and then complain that foo does not exist).
Yes. I do it all the time. You don't even need to run winecfg;I sort of made a mess out of my ~/.wine folder and want to start over with a fresh one. If I delete the ~/.wine folder and run winecfg, will a new one be created?
running any wine app will do it. Even running 'wine foo' will do it
(and then complain that foo does not exist).
Create a New .wine Directory
On Friday February 29 2008 20:11:28 Juan Largo wrote:
rm -rf ~/.wine
wineprefixcreate
...to create "clean" ~/.wine directory.
Just run:Hello,
I sort of made a mess out of my ~/.wine folder and want to start over with
a fresh one. If I delete the ~/.wine folder and run winecfg, will a new
one be created?
TIA
rm -rf ~/.wine
wineprefixcreate
...to create "clean" ~/.wine directory.
I have lots of .wine's Here is a typical scenario for me:
winecfg
mv .wine .wine-mycoolprogram
ln -s .wine-mycoolprogram .wine
wine mycoolprograminstaller.exe
rm .wine
winecfg
mv .wine .wine-someotherproggie
ln -s .wine-someotherproggie .wine
wine someotherinstaller.exe
rm .wine
winecfg
mv .wine .wine-default
ln -s .wine-default .wine
wine wellbahavedprograminstaller.exe
env WINEPREFIX="/home/bill/.wine-mycoolprogram" wine "C:\Program Files\CoolCompany\Cool.exe"
env WINEPREFIX="/home/bill/.wine-someotherproggie" wine "C:\Program Files\SomeCo\SomeOther.exe"
env WINEPREFIX="/home/bill/.wine-default" wine "C:\Program Files\NoBugsInc\WellBehaved.exe"
You can also make desktop launchers from the last three example command lines, as well as similar calls to each different winecfg. I also have a chell script called "setwine" that looks like this to set the symbolic link as needed:
#!/bin/bash
rm /home/bill/.wine
ln -s .wine-$1 .wine
Then I can say something like this:
setwine default
and .wine will now point to .wine-default
As you can imagine, I never have a "real" .wine unless it's temporary. There may be other ways to handle multiple wine bottles, including different local wine version runtimes, but I will leave that for others to describe. Have fun.
Bill
winecfg
mv .wine .wine-mycoolprogram
ln -s .wine-mycoolprogram .wine
wine mycoolprograminstaller.exe
rm .wine
winecfg
mv .wine .wine-someotherproggie
ln -s .wine-someotherproggie .wine
wine someotherinstaller.exe
rm .wine
winecfg
mv .wine .wine-default
ln -s .wine-default .wine
wine wellbahavedprograminstaller.exe
env WINEPREFIX="/home/bill/.wine-mycoolprogram" wine "C:\Program Files\CoolCompany\Cool.exe"
env WINEPREFIX="/home/bill/.wine-someotherproggie" wine "C:\Program Files\SomeCo\SomeOther.exe"
env WINEPREFIX="/home/bill/.wine-default" wine "C:\Program Files\NoBugsInc\WellBehaved.exe"
You can also make desktop launchers from the last three example command lines, as well as similar calls to each different winecfg. I also have a chell script called "setwine" that looks like this to set the symbolic link as needed:
#!/bin/bash
rm /home/bill/.wine
ln -s .wine-$1 .wine
Then I can say something like this:
setwine default
and .wine will now point to .wine-default
As you can imagine, I never have a "real" .wine unless it's temporary. There may be other ways to handle multiple wine bottles, including different local wine version runtimes, but I will leave that for others to describe. Have fun.
Bill
