198584 - nsAppRunner should not depend on xpinstall

Status: RESOLVED WONTFIX

(SeaMonkey :: UI Design, defect)

Description

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

from bug 198296:
"sr=alecf but this is still really lame. xpfe/bootstrap should not have a
dependency on xpinstall! Who reviewed that?!"

Comment 1

[Daniel Veditz [:dveditz]]

Any solution should take into account the reason for the dependency:

If you are upgrading Mozilla itself then components or other libraries in-use at
the time of the install could not be replaced leading to a partial install
situation. We need to check for this situation at startup, and if we find it
then we need to kick off the cleanup utility and exit.

The mozilla application does this itself primarily to prevent having to load the
xpinstall component every startup, which is wasteful since XPInstall is rarely
needed. It also is best if the check is performed early before a potentially
mixed set of old and new components are used which might lead to crashes before
the cleanup utility could be kicked off, in turn leading to a loop that the user
couldn't get out of.

Comment 2

[Vidar Haarr (not reading bugmail)]

x-ref bug 320210

Comment 3

[Tony Mechelynck [:tonymec]]

Is this bug still relevant?

Comment 4

[Tony Mechelynck [:tonymec]]

no reply to comment #3

Comment 5

[Justin Wood (:Callek)]

we're not using xpfe/bootstrap anymore...