Closed Bug 12143 Opened 25 years ago Closed 25 years ago

[feature] need support relative path in component registry

Categories

(Core :: XPCOM, defect, P1)

Product:
Core
Component:
XPCOM
Platform:
x86
Other
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: cathleennscp, Assigned: dp)

References

Details

we need this functionality to work, so that we can pre-package a copy of registry for use during install time.
URL: need support relative path in compone... → [feature] need support relative path ...
Severity: normal → critical
Priority: P3 → P1
Assignee: dp → dougt
I need relative path handling from filespec to fix this. Over to dougt.
URL: [feature] need support relative path ...
Summary: [feature] need support relative path in component registry
setting summary.
Blocks: 11020
Doug? Can you see if this can be supported in M10?
Actually I dont know what I asking for. This might be as simple as some bug fixing in filespec. I will talk to you about this doug.
Component: XPInstall → XPCOM Registry
this is not a xpinstall bug, but rather a xpcom bug. setting to xpcom registry.
Assignee: dougt → dp
I believe that dp has been working on this. assigning to him...
Target Milestone: M10
Blocks: 12806
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Done. Test case would be run apprunner. zip the entire binary dir, extract it elsewhere. Things should run fine and autoreg shouldn't register any dlls at all.
Status: RESOLVED → VERIFIED
Build 9/14/99 All platforms verified. Dlls do not reregister to component.reg.
Component: XPCOM Registry → XPCOM
QA Contact: jimmykenlee → xpcom
You need to log in before you can comment on or make changes to this bug.