[Pkg-mozext-maintainers] Chromium extensions and policy

Michael Meskes meskes at debian.org
Tue Feb 13 20:33:13 UTC 2018


Hi all,

I've been playing around with browser extensions and making them work on
chromium and firefox aka web extension. In the process I noticed that there are
two different way of getting chromium extension enabled already in use. One is
to set the extension as managed by putting a policy file into
/etc/chromium/policies/managed, the other is a load-extension flag via
/etc/chromium.d.

First of all I think we should come to an agreement which way to use and not
have different packages use different way. Unless of course there is a reason
for that that I failed to see so far.

And second, the policy file seems to be tricky. The package I am working on
also comes with one and as soon as I drop that into the directory the
chrome-gnome-shell is no longer loaded, meaning the way these files are, they
seem to be exclusive. Adding the information from both files into one makes
both extensions fly, but I don't see any currenty mechanism to establish that
making installing more packages rather difficult.

Comments?

Michael 
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



More information about the Pkg-mozext-maintainers mailing list