On Fri, Aug 7, 2015 at 5:08 PM, Fabrice Desré <[email protected]> wrote:
> With the current patch, no... because that would mean that a package > with both .webapp and .json would always be an addon, and that would > prevent regualar apps from including a file named manifest.json. I guess > we could refine by checking the content of the various manifests... but > seriously, for 25 existing add-ons? > It sounds like the way gecko will distinguish between the add-on and the app install path is whether the package zip contains `manifest.webapp` or `manifest.json`. Is that correct? Will Settings->Add-ons need to be modified to display the new add-on type? If so, this needs to land soon after the Gecko parts, otherwise users won't be able to enable/disable/uninstall add-ons. If not though, this means this new add-ons will still be fetch-able using mgmt.getAll and will have role=addon. In this case, what happens to the deprecated add-ons? Do they get returned with mgmt.getAll? Will we have a way Gaia side to distinguish between them? The Hackerplace migration plan is as follows: - reach out to each add-on developer and give them a step by step guide to migrating to the new format (seems straightforward) - have them host the new package at a different manifestURL - update Hackerplace to have a new add-on list with manifestURLs that point to the new packages (as we get them) - include the new Hackerplace with the Gecko/Gaia change - host the new apps.json file at a different location than http://directory.fxosapps.org/apps.json This way, current foxfooders will only see the old Hackerplace until they get the update. The only weirdness will be that they will have to re-instal their add-ons after the switch over, and they will have a bunch of old add-ons in their app registry.
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
