Sascha Wilde wrote: > /etc/chromium/native-messaging-hosts/gpgmejson.json > > Upstream recommends a slightly different file name schema[0]: > /etc/chromium/native-messaging-hosts/com.my_company.my_application.json > > As you can see, following this recommendation would mean adding a > domain. I'm not sure whether to follow this scheme, and if so, which > domain to add: org.debian, org.gnupg or ..?
I think the upstream org.gnupg.gpgme would be more fitting, but since this is a distro, just the package name would work imho. > > 2. The manifest for chromium is automatically marked configuration > file, > as it resides under /etc, which IMO is correct. A sysadmin might > want to edit the manifest, e.g. to add the IDs of further > extensions. > > However: the manifest for firefox is installed as > > /usr/lib/mozilla/native-messaging-hosts/gpgmejson.json > > (This is dictated by firefox searching for global manifests in that > place). So it is not automatically marked as configuration. And as > of compatibility level 12 of debhelper it seems to be no longer > possible to mark the file as configuration manually (dh_installdeb > simply ignores any debian/package.conffiles. > > Is there a way to work around this? For the reason given above I > think the manifest should be marked as a conffile for firefox, > too... Install the file in /etc/, e.g. /etc/mozilla/native-messaging- hosts/gpgmejson.json and make a symlink to that from /usr/lib/mozilla/native-messaging-hosts/ I'm not convinced this should be a conffile, though. Couldn't other externsions be added with a new file? So you could install webext-mailvelope-gpgme if you wanted mailvelope with GnuPG backend, and webext-foobar-gpgme if foobar extension should be enabled access to gpgme
