Last Comment Bug 526202 - Installing SeaMonkey 2.0 directly over 1.x will result in a non-working installation.
: Installing SeaMonkey 2.0 directly over 1.x will result in a non-working insta...
Status: RESOLVED WONTFIX
:
Product: SeaMonkey
Classification: Client Software
Component: Installer (show other bugs)
: Trunk
: x86 Windows XP
: -- normal (vote)
: ---
Assigned To: installer
:
Mentors:
http://forums.mozillazine.org/viewtop...
Depends on: compdir-lockdown
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-03 05:49 PST by Philip Chee
Modified: 2010-12-08 16:41 PST (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Philip Chee 2009-11-03 05:49:36 PST
+++ This bug was initially created as a clone of Bug #525488 +++

Can we do something with removed-files? Components dumped by extensions into the application/components/ directory are definitely a problem. For the default 1.1 location we could just delete everything in that location but we would have to be careful with dictionaries and search plugins. We could probably get away with not deleting the dictionaries/, plugins/, and searchplugins/ directories.
Comment 1 Robert Kaiser 2009-11-03 10:24:21 PST
Of course, when installing over 1.x, we also could require the 1.x uninstaller to be run before we install into the same directory.
Comment 2 Serge Gautherie (:sgautherie) 2009-11-05 10:04:12 PST
It looks like bug 519357 will (help to) fix this from Core :-)
Comment 3 Robert Kaiser 2009-11-05 10:50:44 PST
(In reply to comment #2)
> It looks like bug 519357 will (help to) fix this from Core :-)

Well, it won't go into 1.9.1, and what we want here is something that helps us with SeaMonkey 2.0.1 installing over 1.x
Comment 4 Serge Gautherie (:sgautherie) 2009-11-05 19:33:34 PST
(In reply to comment #3)
> it won't go into 1.9.1

Won't it ? It's flagged as wanted+needed...
Comment 5 Robert Kaiser 2009-11-06 02:50:26 PST
(In reply to comment #4)
> (In reply to comment #3)
> > it won't go into 1.9.1
> 
> Won't it ? It's flagged as wanted+needed...

Interesting, I wouldn't think it's good to land such a major change in how things work on a stability/security branch. But it's not my decision, of course.

In any case, that one only covers some part of the problem. For one thing, it's bad to leave our app directory cluttered, and I'm pretty sure that we don't remove some files that even a standard 1.1.x without extensions has installed - for the other, there might be other files than those components giving us headaches as well.
Comment 6 Frank Wein [:mcsmurf] 2009-11-08 15:32:49 PST
I tried a bit around and noticed something interesting (but can probably be explained ;): After installing 2.0 on top of 1.1.18 it does not launch, after deleting all obsolete components in the components/ directory and the .autoreg file in the program folder it still does not launch. After launching another clean SeaMonkey 2.0 installation, the 2.0 installation in the 1.1.18 folder does launch fine.
Comment 7 Philip Chee 2009-11-08 17:03:37 PST
Try deleting the *.mfl files in the 2.0 profile as well (I think you need to delete only the XPC.mfl but lets be through)

If this works then I think all that needs to be done in the installer is to empty the components/ directory during the initial stages of installation. Why empty instead of checking for a list of removed-files?

In 1.x extensions need to put their components in the application components directory but not in 2.0 and we don't migrate extensions anyway so we need to clear a lot of cruft out.

Other directories to consider clearing out.
defaults/ obsolete prefs left behind by 1.x extensions
greprefs/
res/
Comment 8 Philip Chee 2009-11-17 05:19:47 PST
mcsmurf, do you have the cycles to work on this bug?
Comment 9 Robert Kaiser 2010-12-08 16:41:33 PST
Let's be realistic and admit that we'll not work on this any more. Please reopen if you are actually working on solving this.

Note You need to log in before you can comment on or make changes to this bug.