OK, filed http://code.google.com/p/winezeug/issues/detail?id=127 "want uninstall" and http://code.google.com/p/winezeug/issues/detail?id=128 "want status" - Dan
Thanks a lot.
Regarding your comment on id=127 "want uninstall":
Could this useage (use winetricks ONLY on a relatively empty .wine directory to troubleshoot) be documented on every place in the winetricks documentation directories ? This is not the way the documentation feels at: http://wiki.winehq.org/winetricks
e.g. a short point explaining this, and that there is NO way to remove winetricks will help here.
At this point, even the Ubuntu standard wine packaging includes winetricks. This leaves end-users with the impression that they are integral part of wine, and thus maintained.
Wine has been maturing. I now have a stable Windows environment, which required a few winetricks a year ago. This was then reasonable. I really will not anymore remove the .wine directory to delete all installed applications including keys & settings.
If I can help with starting an uninstaller, I am willing to put in some time: A helpful step for me as a user would be to begin with a few cases that can simply be implemented (e.g. cc580, which I could remove recently due to a bug fix).
I also see some application-like entries (7zip, firefox, gecko, python, vlc, wmp) where the package uninstaller may work.
Dan Kegel wrote:
OK, filed http://code.google.com/p/winezeug/issues/detail?id=127 "want uninstall" and http://code.google.com/p/winezeug/issues/detail?id=128 "want status"
- Dan
On Tue, Jun 8, 2010 at 11:09 PM, Jan Hoogenraad jan-winehq@h-i-s.nl wrote:
http://code.google.com/p/winezeug/issues/detail?id=127 "want uninstall"
Could this useage (use winetricks ONLY on a relatively empty .wine directory to troubleshoot) be documented on every place in the winetricks documentation directories ?
That's not quite true; it works perfectly fine on big .wine directories. It's just that they're not such a great idea, each additional thing you install has a chance to screw up the things already installed, and that has nothing to do with winetricks.
This is not the way the documentation feels at: http://wiki.winehq.org/winetricks
e.g. a short point explaining this, and that there is NO way to remove winetricks will help here.
OK, I added a note about it towards the bottom of the page.
At this point, even the Ubuntu standard wine packaging includes winetricks. This leaves end-users with the impression that they are integral part of wine, and thus maintained.
Winetricks is maintained; the lack of uninstall doesn't mean it's unmaintained.
Wine has been maturing. I now have a stable Windows environment, which required a few winetricks a year ago. This was then reasonable. I really will not anymore remove the .wine directory to delete all installed applications including keys & settings.
If I can help with starting an uninstaller, I am willing to put in some time: A helpful step for me as a user would be to begin with a few cases that can simply be implemented (e.g. cc580, which I could remove recently due to a bug fix).
I also see some application-like entries (7zip, firefox, gecko, python, vlc, wmp) where the package uninstaller may work.
If you or anyone else wants to submit patches to implement a way to uninstall things, please go ahead. The user interface would be a challenge, though. I'd rather not have an uninstall verb for each regular verb. - Dan
On Wed, Jun 9, 2010 at 2:35 PM, Dan Kegel dank@kegel.com wrote:
If you or anyone else wants to submit patches to implement a way to uninstall things, please go ahead. The user interface would be a challenge, though. I'd rather not have an uninstall verb for each regular verb.
- Dan
$ wine uninstaller ?
Everything wont be listed in the uninstaller, single dll's and font changes wont be listed. The unistaller could maybe be used for Firefox, Steam etc..
Tom
On Wed, Jun 9, 2010 at 12:41 AM, Tom Wickline twickline@gmail.com wrote:
$ wine uninstaller ?
Everything wont be listed in the uninstaller, single dll's and font changes wont be listed. The unistaller could maybe be used for Firefox, Steam etc..
I suppose winetricks could create uninstaller entries for even the little verbs... that would be the windows way of doing things.
On Wed, Jun 9, 2010 at 3:45 AM, Dan Kegel dank@kegel.com wrote:
I suppose winetricks could create uninstaller entries for even the little verbs... that would be the windows way of doing things.
+1 for this idea.
On Wed, Jun 9, 2010 at 9:35 AM, Dan Kegel dank@kegel.com wrote:
If you or anyone else wants to submit patches to implement a way to uninstall things, please go ahead. The user interface would be a challenge, though. I'd rather not have an uninstall verb for each regular verb.
If you implement a status feature for every trick, you can change the main UI into a list of checkboxes, with the installed tricks already ticked. Any change in tick state would result in the installation/uninstallation of that trick. After clicking ok, you would get a summary of the actions before proceeding: tricks to be installed and tricks to be uninstalled .
Octavian
On Wed, Jun 9, 2010 at 3:03 AM, Octavian Voicu octavian.voicu@gmail.com wrote:
If you implement a status feature for every trick, you can change the main UI into a list of checkboxes, with the installed tricks already ticked.
Right, of course. I had even realized that before. I guess I was just in 'no' mode... - Dan
Attached a simple script which at least removes those files that were installed by another application (possibly winetricks) and are now provided by wine.
On my computer, it removed the following files (of which I am unsure of its origins). 17680 1998-08-06 12:43 psapi.dll 131072 1999-01-15 04:37 mapi32.dll 348160 2008-10-06 23:30 msvcr71.dll 258352 2008-10-06 23:30 unicows.dll 65304 2010-06-08 16:58 winhlp32.exe
.. based on the date match, I suspect the files below as well. However, there are no files with the same name in the wine directory, and thus my simple script is unable to judge them as being superseded: 924432 2008-10-06 23:30 MFC40.DLL 499712 2008-10-06 23:30 msvcp71.dll 326656 2008-10-06 23:30 MSVCRT40.DLL 492304 2008-10-06 23:30 OLEAUT32.DLL 21936 2008-10-06 23:30 help.exe 995383 2008-10-06 23:30 MFC42.DLL 70656 2008-10-06 23:30 MSVCIRT.DLL
Dan: Can you attach this to http://code.google.com/p/winezeug/issues/detail?id=127 "want uninstall" as I have no access to the Google thing ?
Dan Kegel wrote:
On Wed, Jun 9, 2010 at 3:03 AM, Octavian Voicu octavian.voicu@gmail.com wrote:
If you implement a status feature for every trick, you can change the main UI into a list of checkboxes, with the installed tricks already ticked.
Right, of course. I had even realized that before. I guess I was just in 'no' mode...
- Dan
Jan Hoogenraad wrote:
Attached a simple script which at least removes those files that were installed by another application (possibly winetricks) and are now provided by wine.
On my computer, it removed the following files (of which I am unsure of its origins). 17680 1998-08-06 12:43 psapi.dll 131072 1999-01-15 04:37 mapi32.dll 348160 2008-10-06 23:30 msvcr71.dll 258352 2008-10-06 23:30 unicows.dll 65304 2010-06-08 16:58 winhlp32.exe
.. based on the date match, I suspect the files below as well. However, there are no files with the same name in the wine directory, and thus my simple script is unable to judge them as being superseded: 924432 2008-10-06 23:30 MFC40.DLL 499712 2008-10-06 23:30 msvcp71.dll 326656 2008-10-06 23:30 MSVCRT40.DLL 492304 2008-10-06 23:30 OLEAUT32.DLL 21936 2008-10-06 23:30 help.exe 995383 2008-10-06 23:30 MFC42.DLL 70656 2008-10-06 23:30 MSVCIRT.DLL
VB6, possibly?
James McKenzie
OK. New version of the script: it also finds uppercase filename matches. It also removed:
131072 1999-01-15 04:37 system32/MAPISTUB.DLL 70656 2008-10-06 23:30 system32/MSVCIRT.DLL 326656 2008-10-06 23:30 system32/MSVCRT40.DLL 492304 2008-10-06 23:30 system32/OLEAUT32.DLL
Now, is seems that the following files belong to that pack as well:
924432 2008-10-06 23:30 MFC40.DLL 499712 2008-10-06 23:30 msvcp71.dll 21936 2008-10-06 23:30 help.exe 995383 2008-10-06 23:30 MFC42.DLL
Are they in any way harmful if they stay in system32 ? Or do they contain additional functionality, not yet included in wine ?
James McKenzie wrote:
Jan Hoogenraad wrote:
Attached a simple script which at least removes those files that were installed by another application (possibly winetricks) and are now provided by wine.
On my computer, it removed the following files (of which I am unsure of its origins). 17680 1998-08-06 12:43 psapi.dll 131072 1999-01-15 04:37 mapi32.dll 348160 2008-10-06 23:30 msvcr71.dll 258352 2008-10-06 23:30 unicows.dll 65304 2010-06-08 16:58 winhlp32.exe
.. based on the date match, I suspect the files below as well. However, there are no files with the same name in the wine directory, and thus my simple script is unable to judge them as being superseded: 924432 2008-10-06 23:30 MFC40.DLL 499712 2008-10-06 23:30 msvcp71.dll 326656 2008-10-06 23:30 MSVCRT40.DLL 492304 2008-10-06 23:30 OLEAUT32.DLL 21936 2008-10-06 23:30 help.exe 995383 2008-10-06 23:30 MFC42.DLL 70656 2008-10-06 23:30 MSVCIRT.DLL
VB6, possibly?
James McKenzie
On Wed, Jun 9, 2010 at 6:03 AM, Dan Kegel dank@kegel.com wrote:
On Wed, Jun 9, 2010 at 3:03 AM, Octavian Voicu octavian.voicu@gmail.com wrote:
If you implement a status feature for every trick, you can change the main UI into a list of checkboxes, with the installed tricks already ticked.
Right, of course. I had even realized that before. I guess I was just in 'no' mode...
It took me a while, but I finally implemented this in winetricks-alpha today.
To get a list of installed verbs from the commandline, you can do winetricks-alpha list-installed In the GUI, the installed verbs now have their checkboxes already checked.
Unchecking them does nothing still, though.
Please test http://winetricks.googlecode.com/svn/trunk/src/winetricks-alpha and let me know what you think. - Dan