it should, but i have developed a habit of copying everything to a .wine-working before i start screwing with stuff. also if time permits, start looking at what files wine is creating and where they are going. /usr/bin /usr/lib /usr/include or /usr/local/bin.... some times files are not removed completely and will confilct with the version you replace them with. use a file manager(i use mc) and sort by date and many times associated files will group together. this is especially true if you build your own. --- Robert Davis <rob@xxxxxxxxxxxxxxxxxxxx> wrote: > Thanks a bunch, good info. > If I remove wine with the package manager will it leave my directory > structures and config files in place? > > phrostie wrote: > > >DO NOT install one version of Wine on top of another. > >it will bite you every time. > > > >uninstall your currect version by what ever packaging system your dist' uses > >and then build and install wine. afterward do not delete the build > directory > >as this will have the uninstall. > > > >there should be a README file that says the prefered method for building. > >normally it is ./configure, make, make depend, make install, but check > anyway. > > > > > > ===== phrostie Oh I have slipped the surly bonds of DOS and danced the skies on Linux silvered wings. http://pfrostie.freeservers.com/cad-tastrafy/ //www.freelists.org/webpage/cad-linux __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com