Hi list, Every time before I post a problem or question, I try to upgrade my wine to the latest version (as I was told to do at the beginning). Well I'm going on to my 5th or 6th new version of wine. As an experienced Windows user (and a fairly new, but OK Linux user) I am concerned about the effect on my computer of simply installing wine after wine after wine. I seem to recall copying files all over the place and I'm sure by now it must be a mess. Alas my applications Dreamweaver and Fireworks still are not working. I have installed 1 Mandrake RPM version, all the rest from source tar.gz files. I have Mandrake 9.1 (2.4.22). Can someone please outline for me the CORRECT way of cleanly uninstalling one version of Wine before installing the next version? I'm pretty good at the command line but don't know everything yet. Thank you. -AB
On Tue, 2005-01-11 at 10:57 -0500, Angela Burrell wrote:> Hi list, > > Every time before I post a problem or question, I try to upgrade my wine to > the latest version (as I was told to do at the beginning). > > Well I'm going on to my 5th or 6th new version of wine. As an experienced > Windows user (and a fairly new, but OK Linux user) I am concerned about the > effect on my computer of simply installing wine after wine after wine. I > seem to recall copying files all over the place and I'm sure by now it must > be a mess. Alas my applications Dreamweaver and Fireworks still are not > working. > > I have installed 1 Mandrake RPM version, all the rest from source tar.gz > files. I have Mandrake 9.1 (2.4.22). > > Can someone please outline for me the CORRECT way of cleanly uninstalling > one version of Wine before installing the next version? I'm pretty good at > the command line but don't know everything yet. > > Thank you. > > -AB > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-usersYou're right, this is a bit complex at the moment. I'll be updating the documentation on it. Anyway I can summarize it here as "Uninstall packaged versions first, then uninstall source versions by going into the source directory and doing make uninstall" If you're going from old versions, you'll probably want a new config file as well. Back up the old one (or if you don't care about the fake windows drive, nuke ~/.wine entirely) and then follow the current instructions for new users, which at this point is to run winetools. This will soon be handled more automatically via the winecfg program, but in the meantime it doesn't hurt to use winetools. Thanks, Scott Ritchie
Angela Burrell wrote:> Hi list, > > Every time before I post a problem or question, I try to upgrade my wine to > the latest version (as I was told to do at the beginning). > > Well I'm going on to my 5th or 6th new version of wine. As an experienced > Windows user (and a fairly new, but OK Linux user) I am concerned about the > effect on my computer of simply installing wine after wine after wine. I > seem to recall copying files all over the place and I'm sure by now it must > be a mess. Alas my applications Dreamweaver and Fireworks still are not > working. >If you stick with always using packages from the same source, or always compiling, then there really is no reason to be concerned. Yes, you may end up with a few stray files, but it is mostly just a small amount of wasted disk space. If you switch from, say, a packaged version of Wine to compiling from source, then definitely uninstall the old version first. For what it is worth, I have been compiling and installing Wine from source (CVS) frequently for almost 5 years, and have never uninstalled it first.
Am Di, Jan 11, 2005 at 05:03:08 -0800 schrieb Richard W. Knight:> Joachim von Thadden wrote: > >Is there somebody out there who can tell my why it is so good to compile > >Wine yourself? There are binaries on winehq for almost every version,OK, thanks you all for the replies. Just for the archive the collected answers were: - have more than one installation of wine at a time for different windows programs - including special patches as the one for playing Snood ;-) - using a special distribution with no suitable packet at winehq - compile optimizations The reason I asked is that WineTools is not very good in coping with self compiled Wine if this does not create a suitable .wine directory during first call. If I have time I will fix it by providing a default if none is created. Regards Joachim -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"