Closed Bug 1132459 Opened 10 years ago Closed 10 years ago

Extensions installed from the distribution/extensions directory are not unpacked

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 633225

People

(Reporter: mkaply, Unassigned)

Details

Partner distributions place extensions in the distribution/extensions directory and then they are installed when a new profile is created. Currently that mechanism copies over the XPI file as is, regardless of the unpack attribute in the install.rdf. That is incorrect. If the install.rdf specifies unpack, the extension should be unpacked. This will especially be a problem with the new AMO signing mechanism, since it will be required that partner builds contain a signed XPI, yet sometimes the XPI needs to be unpacked.
Note that when the extension is updated, that version is unpacked.
(In reply to Mike Kaply [:mkaply] from comment #0) > This will especially be a problem with the new AMO signing mechanism, since > it will be required that partner builds contain a signed XPI, yet sometimes > the XPI needs to be unpacked. The new signing requirement won't make this any more of a problem since we will be able to verify the signatures on unpacked addons (bug 1038072)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
I really did search bugzilla for this before opening.
You need to log in before you can comment on or make changes to this bug.