125119 - Installer should delete all .DLL files in known mozilla directorys

Status: VERIFIED WONTFIX

(SeaMonkey :: Installer, enhancement)

Description

[Matthias Versen [:Matti]]

Currently the installer deletes only known Mozilla files.
This is a problem on win32 if the installer isn't up-to-date.
We get many Bugs with this problem. (not only entry-Point bugs.., 
see bug 124144)

I understand why the installer doesn't delete all files in the mozilla folder if 
you install over an older build but I think the main problems on win32 should be 
solved if the installer deletes all .DLL files in known mozilla directorys
(mozilla\, Mozilla\Components\,....)

You may say that this bug is a wontfix but you would agree if you work on 
Unconfirmed bugzilla Bugs.
(I saw ~30 and more Bugs about this problem in the last 4 months)

Comment 1

[Henrik Gemal]

since there's no current bug about leftovers dll's I wontfix this one. No need 
to delete all DLL files.

Comment 2

[Matthias Versen [:Matti]]

reopening since there is a valid open bug "entry point not found" bug

BTW: Have you tested all combinations ?

Install with Mailnews and install without.....

Comment 3

[Henrik Gemal]

it should not delete all .dll files. The installer already does some cleanup. If
we get any entry point missing bugs, lets fix those in the bug reports.

Comment 4

[Daniel Veditz [:dveditz]]

I concur with Henrik's WONTFIX, the installer will not blindly delete 
everything it finds. We currently do that on Mac and Linux and get complaints 
that we've zapped the plugins and the like that people then have to re-install 
each upgrade. Particularly annoying for testers who upgrade every day.

components don't come and go every day, it's easy enough to zap them as they 
come up.

Comment 5

[Matthias Versen [:Matti]]

dveditz: 
I know that you can easy fix the installer if get get a bug report but a
permanent solution would be better. (You can change a already released build...)

How about this:
1. installation into new directory: The installer creates a list of files which
are installed/extracted from the XPIs and saves this file list in the mozilla
directory. (install.lst)

2: user installs a new build over this old version:
Installer creates again a list of installed files in the memory, compares this
file list with the already installed files (install.st), delete all files that
are now unused from the older build and saves the new "install.lst"

- you can add an internal execption list for some files/directory (mozilla/plugins)

This would be a permanent solution for all "install over old build" problems.
There are not only "Entry point" bugs, we had also "Save as" (6 bugs in a M0.9.6
(?)) and other problems and this would be a permanent solution for the installer.

Comment 6

[Grace Bush]

verified