1338698 - Deprecate multi-package pages

Status: RESOLVED FIXED

(Developer Documentation Graveyard :: Add-ons, defect)

Description

[Andy McKay]

This page https://developer.mozilla.org/en-US/docs/Multiple_Item_Packaging and a few other pages linked off it should note that we no longer sign these on AMO and are effectively deprecated.

Comment 1

[Richard Bloor]

(In reply to Andy McKay [:andym] from comment #0)
> This page https://developer.mozilla.org/en-US/docs/Multiple_Item_Packaging
> and a few other pages linked off it should note that we no longer sign these
> on AMO and are effectively deprecated.

Hi Andy, I'm about to start on this. I notice the page already says:

Signing

All extensions now require signing by Mozilla. For multiple item packages, all internal add-ons need to be signed, but the container doesn't need to be signed. This means that the contained add-ons need to be submitted to AMO individually for signing. Additionally, the container add-on ID must not be the same as the ID of any of the contained add-ons.

Does this cover the changes already?

Or when you say "effectively deprecated" do you mean the "Multiple item extension packaging" or just the signing of them?

And to clarify "pages linked" you mean the 6 pages listed at the foot of the article?

Comment 2

[Andy McKay]

Sorry, in bug 1323128 which landed in 53 we removed the ability to load a multi-package XPI at all.

Comment 3

[Richard Bloor]

Hi Andy, I've updated https://developer.mozilla.org/en-US/docs/Multiple_Item_Packaging (with a warning, and marked as obsolete) and https://developer.mozilla.org/en-US/Add-ons/Extension_Packaging with a note where it mentions multiple item packages. Wasn't able to find other references on linked pages, nor from a search of MDN. All done?

Comment 4

[Andy McKay]

Looks good, thanks.