Closed Bug 435088 Opened 17 years ago Closed 17 years ago

Check .autoreg in the GRE directory, too

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.1b2

People

(Reporter: glandium, Assigned: glandium)

Details

Attachments

(1 file)

Attached patch patchSplinter Review
When using xulrunner applications, xpcom current process directory and GRE directory are different, and may contain things that are not updated synchronously, and one may need to trigger autoregistration of components on update of one or the other. The attached patch implements checking in both GRE_DIR and XPCOM_CURRENT_PROCESS_DIR (skipping second check when it is the same directory).
Attachment #321999 - Flags: review?(benjamin)
What failure case are you trying to solve? XR apps should be blowing away all component registration whenever the buildid of the toolkit or the application changes, see http://mxr.mozilla.org/mozilla/source/toolkit/xre/nsAppRunner.cpp#2135
In debian, and maybe in other linux distributions, we separate some components and put them in different packages (such as pyxpcom or mozgnome) to avoid spurious dependencies. When installing these extra components (that can't really be put as extensions, because not all applications enable the extensions manager, but we want all applications to have these components available, and for pyxpcom, it's actually mandatory), we trigger components autoregistration by touching .autoreg. The buildid doesn't change since we install new components on the same build.
Attachment #321999 - Flags: review?(benjamin) → review+
Component: XPCOM Registry → XPCOM
Assignee: nobody → mh+mozilla
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.1b2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: