So, we could use some packaging guidelines for webextensions, since Firefox switched and we now have Chromuim and some "official" endorsement of Chrome itself. Plus we just touched on this issue with the /opt/etc/chrome thing, so we might as well finish it.
I will work on an initial draft, since it should be pretty simple. However, there are some open questions I'll need to figure out.
More to come as I work through this.
So, yeah, it turns out that for chrome (and probably chromium without patching) the best you can do is give it a pointer to a google server unless things are specifically set to developer mode. The browser will then pull the extension into the per-user configuration for each user when they start the browser.
At this point I have no idea if it will then auto-update the extension or if it is bound to a specific version.
Still, as distasteful as this is, FESCo and particularly the council appear to have embraced chrome and so we will see packaged extensions (and already have two or three of them) and should still provide some guidance. Fortunately firefox isn't broken in this way.
to comment on this ticket.