[SOLVED] how to uninstall wine

darksaurian · 06-08-2010, 02:56 AM

I install wine with this as regular user:
darksaurian@inferno:/usr/local/wine-1.1.40$ ./tools/wineinstall

Then to uninstall I do this as root:
root@inferno:/usr/local/wine-1.1.40# make uninstall

Now if I try to install again it say this:

Code:

darksaurian@inferno:/usr/local/wine-1.1.40$ ./tools/wineinstall
Wine Installer v1.0

Warning !! wine binary (still) found, which may indicate
a (conflicting) previous installation.
You might want to abort and uninstall Wine first.
(If you previously tried to install from source manually, 
run 'make uninstall' from the wine root directory)

We need to install Wine as the root user. Do you want us to build Wine,
'su root' and install Wine?  Enter 'no' to build Wine without installing:
(yes/no)

Why it say conflicting previous installation? "make uninstall" not work?

dive · 06-08-2010, 03:26 AM

Seems like it isn't uninstalling. You may have to delete files manually I think.

Daedra · 06-08-2010, 03:27 AM

What Dive said, also...

Your better off making your own slackware packages. You can use Alien Bob's wine slackbuild or just use his precompiled packages available here.
install fontforge first
http://connie.slackware.com/~alien/s...lds/fontforge/

then wine
http://connie.slackware.com/~alien/slackbuilds/wine/

darksaurian · 06-08-2010, 05:48 AM

"make uninstall" work for everyone else? Why it not work? How I know what files to delete manually? I not know where it put everything.

dive · 06-08-2010, 09:13 AM

I usually install wine (and other software) using the slackbuild: http://slackbuilds.org/repository/13.0/system/wine/

This builds a package which you can install and uninstall very easily. Update for 13.1 coming soon...

darksaurian · 06-08-2010, 10:29 AM

Yeah that's what I want to do next time is Slackbuild but I think I need to get previous wine off my system or maybe mess up Slackbuild. But I not know where all wine files are and it look like "make uninstall" not work.

dive · 06-08-2010, 11:00 AM

I would hazard a guess and say:

/usr/local/share/wine
/usr/local/lib/wine
/usr/local/include/wine
/usr/local/doc/wine-x.x.x
/usr/local/bin/wine*

But this is only a guess.

Have you tried doing './configure' in the source directory before 'make uninstall'?

bgeddy · 06-08-2010, 11:10 AM

Copy this to a file called delwine and, as root, run "source delwine"

Code:

cd /usr/local/bin
rm function_grep.pl
rm msiexec
rm notepad
rm regedit
rm regsvr32
rm widl
rm wine
rm wine-preloader
rm wineboot
rm winebuild
rm winecfg
rm wineconsole
rm winecpp
rm winedbg
rm winedump
rm winefile
rm wineg++
rm winegcc
rm winemaker
rm winemine
rm winepath
rm wineprefixcreate
rm wineserver
rm wmc
rm wrc
rm -rf /usr/local/include/wine
rm -rf /usr/local/lib/wine
rm /usr/local/lib/libwine*
rm -rf /usr/local/share/wine
rm  /usr/local/share/man/man1/wine*
rm  /usr/local/share/man/man1/wmc.1
rm  /usr/local/share/man/man1/wrc.1
rm  /usr/local/share/man/man1/widl.1
rm /usr/local/share/applications/wine.desktop

That should get rid of all traces of wine if installed to the default places.

darksaurian · 06-09-2010, 12:11 AM

No, none of those directories from dive's post exist and all I have in /usr/local/bin is:
pwgen timidity

"make uninstall" must have got rid of those things. But still have "previous installation" it say. I not understand.

Why run ./configure? When I run /tools/wineinstall it not do that already? I try it but I not understand.

darksaurian · 06-09-2010, 12:17 AM

./configure not help. Where this wine binary or previous installation that it talking about? It seem like it all cleaned out to me.

I do this:

Code:

root@inferno:~# find / -name wine
/home/darksaurian/.local/share/applications/wine
/home/darksaurian/.local/share/Trash/files/usr/include/wine
/home/darksaurian/.local/share/Trash/files/usr/bin/wine
/home/darksaurian/.local/share/Trash/files/usr/lib/wine
/home/darksaurian/.local/share/Trash/files/usr/share/wine
/usr/local/wine-1.1.40/libs/wine
/usr/local/wine-1.1.40/wine
/usr/local/wine-1.1.40/include/wine
/usr/local/wine-1.1.40/loader/wine
root@inferno:~#

darksaurian · 06-09-2010, 01:32 AM

Here part in wineinstall script that tell me I have previously installed binary:

Code:

# check whether wine binary still available
 99 if [ -x `which wine 2>/dev/null` ] && [ -n "`wine --version 2>/dev/null`" ]
100 then
101     echo "Warning !! wine binary (still) found, which may indicate"
102     echo "a (conflicting) previous installation."
103     echo "You might want to abort and uninstall Wine first."
104     echo "(If you previously tried to install from source manually, "
105     echo "run 'make uninstall' from the wine root directory)"
106     std_sleep
107 fi

I not know how to read this. It look like if statement succeed but why? Something in /dev/null?

darksaurian · 06-09-2010, 01:39 AM

I think it the "which" command. I try this at command prompt:
`which wine 2>/dev/null`

And nothing happen. I think it return true. I think I try to figure out what "which" command does and maybe figure out where it finding previous wine installation?

darksaurian · 06-09-2010, 01:47 AM

What? So command is "wine 2" and then standard output redirected to /dev/null?

This make no sense. I have no wine anymore. I type "wine" or "wine 2" and computer say no such thing as wine. But ./tools/wineinstall script try that and it return true and it say I have previously installed wine.

I not understand at all.

bgeddy · 06-09-2010, 05:08 AM

The command is redirecting stderr (device 2) to the bit bucket (/dev/null). You can try just running "which wine" to see what which finds. It then checks if anything is returned from "wine --version". You can try running :

Code:

if [ -x `which wine 2>/dev/null` ] && [ -n "`wine --version 2>/dev/null`" ]; then echo Wine Installed;fi

to prove to yourself what's happening.

If you want to delve into this look up redirection. Here's a quick reference - just the first one I found.

If you are determined to run this script - why not just comment out the test and run it anyway? Just insert # at the start of each line between if and fi, This will force wine to build every time.

darksaurian · 06-13-2010, 09:35 AM

No, I don't want to run the script. I want to install the new wine slackbuild. But I want to completely remove old wine from my system. I don't understand why that script thinks I still have wine.

Apparently this tells the script that I have previous version of wine on my system:
if [ -x `which wine 2>/dev/null` ] && [ -n "`wine --version 2>/dev/null`" ];

But I don't understand that line so I don't know what to delete.