158346 - Need talkback builds to handle unzipping over existing build

Status: VERIFIED DUPLICATE of bug 167174

(SeaMonkey :: Installer, enhancement)

Description

[David Bradley]

We see a lot of crashes from people unzipping talkback builds into an existing
directory. While the docs explicitly state users not to do this, they continue.
This results in bugs that are often strange and take some time to track back to
this issue. This occurs because the xpcom type information doesn't get updated
in release builds, so these people have new components but old type info.

Comment 1

[Shiva Thirumazhusai]

This is not a talkback problem. It should be handled by Installer and/or
distribution. Talkback bits are very closely associated with specific
distribution. Having seperate installer will not solve the issue.

Comment 2

[David Bradley]

jband came up with an alternative for dealing with this problem in bug 156711.
http://bugzilla.mozilla.org/show_bug.cgi?id=156711#c12 Create an invalid
xpti.dat file for talkback builds, containing just a single \n. This would force
a new auto registering of components to occur. I'm going to change the summary
to more accurately reflect the problem being addressed rather than a specific
solution

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

per http://lxr.mozilla.org/seamonkey/source/xpcom/build/nsXPComInit.cpp#219 and
bug 167174 it seems like creating an empty .autoreg file would also suffice.

seems like bug 167174 is a duplicate of this one...

Comment 4

[David Bradley]

Agreed, since bug 167174 has gotten the most discussion, duping to that.

*** This bug has been marked as a duplicate of 167174 ***

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

VERIFIED