From my understanding, a per-extension manifest file is intended to be shipped as part of the webext-* package for the extension, and not with the native helper. Compare with webext-browserpass:
``` $ dpkg -L webext-browserpass | grep native-messaging /etc/chromium/native-messaging-hosts /etc/chromium/native-messaging-hosts/com.github.browserpass.native.json /usr/lib/mozilla/native-messaging-hosts /usr/lib/mozilla/native-messaging-hosts/com.github.browserpass.native.json ```Confusion may have arisen because most webextensions (such as browserpass) ship the extension and the native helper app in the same package, making it unclear where the manifest belongs when the native helper is in a separate package (as gpgme must if it is to be shared between applications).
This would imply that the correct place for the manifests is in a notional `webext-mailvelope` package, where they SHOULD NOT be marked as config. Packaging mailvelope properly would greatly improve the user experience (see e.g. https://github.com/mailvelope/mailvelope/issues/628 , https://github.com/mailvelope/mailvelope/issues/699 ).
-- Andrew Gallagher
OpenPGP_signature
Description: OpenPGP digital signature
