Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #6775 > unrolled thread
| Started by | Wally W. <ww84wa@aim.com> |
|---|---|
| First post | 2016-07-23 18:13 -0400 |
| Last post | 2016-07-31 03:19 -0700 |
| Articles | 5 on this page of 45 — 9 participants |
Back to article view | Back to comp.programming
To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-23 18:13 -0400
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-24 06:44 +0000
Re: To all who write uninstallation programs for software you distribute Julio Di Egidio <julio@diegidio.name> - 2016-07-24 04:53 -0700
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-25 04:13 +0000
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-25 08:28 +0100
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 09:40 +0100
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-24 10:00 -0500
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 16:18 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 11:34 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 16:46 +0100
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-24 10:55 -0500
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 17:08 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 12:24 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 17:37 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 13:16 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 18:53 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 15:11 -0400
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-24 14:45 -0500
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 21:31 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 18:06 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 23:53 +0100
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 18:04 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 23:47 +0100
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 19:34 -0400
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 14:03 -0400
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 12:10 -0400
Re: To all who write uninstallation programs for software you distribute Richard Heathfield <rjh@cpax.org.uk> - 2016-07-24 17:36 +0100
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-24 11:37 -0500
Re: To all who write uninstallation programs for software you distribute "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-24 13:24 -0400
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-24 18:29 -0500
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 20:34 -0400
Re: To all who write uninstallation programs for software you distribute Mark Storkamp <mstorkamp@yahoo.com> - 2016-07-25 10:00 -0500
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-25 11:22 -0500
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-25 18:55 +0000
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-26 00:19 -0400
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-26 04:24 +0000
Re: To all who write uninstallation programs for software you distribute "Osmium" <r124c4u102@comcast.net> - 2016-07-26 09:13 -0500
Re: To all who write uninstallation programs for software you distribute Öö Tiib <ootiib@hot.ee> - 2016-07-26 14:11 -0700
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-27 02:58 -0400
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-27 13:47 +0000
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 13:24 -0400
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 13:40 -0400
Re: To all who write uninstallation programs for software you distribute Wally W. <ww84wa@aim.com> - 2016-07-24 13:42 -0400
Re: To all who write uninstallation programs for software you distribute Kaz Kylheku <349-534-5780@kylheku.com> - 2016-07-24 18:29 +0000
Re: To all who write uninstallation programs for software you distribute SIKDER EMRAN <sikderemran4321@gmail.com> - 2016-07-31 03:19 -0700
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Wally W. <ww84wa@aim.com> |
|---|---|
| Date | 2016-07-24 13:24 -0400 |
| Message-ID | <btt9pbd5hqm8a688as6eqeiqhb9mmhodn0@4ax.com> |
| In reply to | #6781 |
On Sun, 24 Jul 2016 11:34:16 -0400, J. Clarke wrote: >In article <nn2m7t$o38$2@dont-email.me>, rjh@cpax.org.uk says... >> >> On 24/07/16 16:00, Osmium wrote: >> > "Richard Heathfield" wrote: >> > >> >> On 23/07/16 23:13, Wally W. wrote: >> >>> To all who write uninstallation programs for software you distribute: >> >> >> >> Whenever possible, I prefer not to do this. To delete my software, you >> >> just delete it, and you're done. Either >> >> >> >> cd where/did/you/put/it >> >> rm * >> >> >> >> or maybe, just maybe, there are sub-directories, so: >> >> >> >> cd where/did/you/put/it >> >> rm -rf * >> >> >> >> (careful!) >> >> >> >> or, if you're on Windows, one of the many Windows equivalents of doing >> >> the same thing (such as dragging a pretty yellow box onto a picture of >> >> a dustbin - alas, I can't promise sweeties to those who get this right). >> >> >> >>> If your uninstallation program can't leave the machine in the >> >>> condition you found it, then tell the user what is different. >> >> >> >> Hear, hear! But if your program /needs/ an uninstallation program, >> >> there had better be an extraordinarily good reason. (And sometimes >> >> there is. But it's rarer than many people think.) >> > >> > I long for the good old days too. >> > >> > But doesn't your approach fail in one of the most elementary cases on >> > Windows? A new program with a new data file. You want to click on the >> > data file and invoke the program. How can you do that without changing >> > the data used by the OS? To me, that is SOP and not rare at all. >> >> But the /user/ is responsible for setting up that association. The user >> double-clicks on "foo.bar", and Windows says "huh? You'd better choose a >> program for that", and the user chooses my program, and that's the >> user's choice, so it's the user's problem. > >And the tech support guys think badly of you when they have to remote- >access 10,000 machines and set up that association that _should_ have >been set up by the installer. Why must the association *always* be changed to launch the last-installed program? Why should every new text editor assume the user wants the new program to be the default text file editor? What if I am testing a series of programs that use the .foo extension? I install three programs for this purpose: A, B, and C. When I install C, it may or may not keep track that 'B' had the .foo association before it. It turns out I like program 'A' best. So I uninstall 'B' then uninstall 'C'. If 'C' tries to revert the association to 'B', it will fail or be useless because 'B' is gone. 'A' is left without the association and the uninstaller for 'C' may complain about things not going well during the uninstallation. ... if the uninstaller even tries to make the effort to restore previous associations.
[toc] | [prev] | [next] | [standalone]
| From | Wally W. <ww84wa@aim.com> |
|---|---|
| Date | 2016-07-24 13:40 -0400 |
| Message-ID | <kiu9pbthh2rqp7818qrof6qqppdq4aqoje@4ax.com> |
| In reply to | #6777 |
On Sun, 24 Jul 2016 09:40:59 +0100, Richard Heathfield wrote: >On 23/07/16 23:13, Wally W. wrote: >> To all who write uninstallation programs for software you distribute: > >Whenever possible, I prefer not to do this. To delete my software, you >just delete it, and you're done. May your tribe increase. Wisdom from 20 years ago: "Place ... DLL files only in the same directory as the application that needs them. This allows the application to "see" the DLLs but hides them from the rest of the system." ... and stay away from my registry: <http://stackoverflow.com/questions/268424/when-and-why-should-you-store-data-in-the-windows-registry> "I would have to say there really isn't a good excuse to put something in the registry unless it is something like file associations, or machine specific settings. I come from the school of thought that says that a program should be runnable from wherever it is installed, that the installation should be completely movable within a machine, or even to another machine and not affect the running of it." ... but that is contrary to the interest of software vendors, who don't want their programs copied and getting legs. So all honest users are penalized and inconvenienced. Remember when LOTUS 123 came on a copy-protected disk? It was a PITA for users, and it stopped. The "installation" of programs that intertwine with the operating system and may not uninstall cleanly should likewise be stopped.
[toc] | [prev] | [next] | [standalone]
| From | Wally W. <ww84wa@aim.com> |
|---|---|
| Date | 2016-07-24 13:42 -0400 |
| Message-ID | <nfv9pbpkat09t6g2poa72qtmm2jbl9h1jk@4ax.com> |
| In reply to | #6793 |
On Sun, 24 Jul 2016 13:40:41 -0400, Wally W. wrote: >On Sun, 24 Jul 2016 09:40:59 +0100, Richard Heathfield wrote: > >>On 23/07/16 23:13, Wally W. wrote: >>> To all who write uninstallation programs for software you distribute: >> >>Whenever possible, I prefer not to do this. To delete my software, you >>just delete it, and you're done. > >May your tribe increase. > >Wisdom from 20 years ago: >"Place ... DLL files only in the same directory as the application >that needs them. This allows the application to "see" the DLLs but >hides them from the rest of the system." > >... and stay away from my registry: ><http://stackoverflow.com/questions/268424/when-and-why-should-you-store-data-in-the-windows-registry> >"I would have to say there really isn't a good excuse to put something >in the registry unless it is something like file associations, or >machine specific settings. > >I come from the school of thought that says that a program should be >runnable from wherever it is installed, that the installation should >be completely movable within a machine, or even to another machine and >not affect the running of it." > >... but that is contrary to the interest of software vendors, who >don't want their programs copied and getting legs. > >So all honest users are penalized and inconvenienced. > >Remember when LOTUS 123 came on a copy-protected disk? It was a PITA >for users, and it stopped. > >The "installation" of programs that intertwine with the operating >system and may not uninstall cleanly should likewise be stopped. ... without requiring software to run in the cloud.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <349-534-5780@kylheku.com> |
|---|---|
| Date | 2016-07-24 18:29 +0000 |
| Message-ID | <20160724111254.447@kylheku.com> |
| In reply to | #6777 |
On 2016-07-24, Richard Heathfield <rjh@cpax.org.uk> wrote: > On 23/07/16 23:13, Wally W. wrote: >> To all who write uninstallation programs for software you distribute: > > Whenever possible, I prefer not to do this. To delete my software, you > just delete it, and you're done. Either > > cd where/did/you/put/it > rm * Unfortunately, this happy "whenever possible" tends to fall apart. Stuff lives in multiple places. E.g. on Windows you have shortcuts in the start menu and desktop, data in some "application data" directory, registry settings, and perhaps environment variables (like PATH for all users). The user might want to uninstall all of it, or might want to keep the settings and data (perhaps they are switching to a different version). The program might have components running in the background that the uninstaller knows about and can report about and stop. >> If your uninstallation program can't leave the machine in the >> condition you found it, then tell the user what is different. > > Hear, hear! But if your program /needs/ an uninstallation program, there > had better be an extraordinarily good reason. (And sometimes there is. > But it's rarer than many people think.) Even if uninstallation is that simple, it may help the user to see that uninstall executable. The absence of that little program (by itself) fails to assure the user that deletion of the directory is sufficient.
[toc] | [prev] | [next] | [standalone]
| From | SIKDER EMRAN <sikderemran4321@gmail.com> |
|---|---|
| Date | 2016-07-31 03:19 -0700 |
| Message-ID | <188d6fd8-48b6-4b27-948c-d612e7a8ed19@googlegroups.com> |
| In reply to | #6775 |
http://www.computerprogrammingtutorial.com
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.programming
csiph-web