Am Mittwoch, den 10.03.2010, 00:16 -0500 schrieb Daniel Kahn Gillmor: > hey folks-- > > #558490 suggests that mozilla-devscripts should automatically put > extension-specific preferences files someplace in /etc, and link back to > them from the unpacked tree. > > I think this is a good idea, and i think it should be spelled out > specifically in https://wiki.debian.org/Mozilla/ExtensionsPolicy > > I've just modified the policy draft to include a new "Config Files" > section stating this idea, roughly. I'd appreciate feedback and edits > from any interested parties. > > In particular, i wonder if we should recommend particular placement of > the config files. at the moment, many extensions seem to use > /etc/mozilla-extensions/foo.js (which seems a little at odds to our > current xul-ext- naming scheme). Is there a better choice? > > As an admin, where would you look for the default configuration files of > your xul-ext packages?
I think that /etc/xul-ext/ is more consistent with our naming scheme. Every package needs only one config file. Therefore I suggest to put the file into /etc/xul-ext/PACKAGE.js, where PACKAGE is the package name with xul-ext- stripped away (for example adblock-plus). asac suggested [1] to put an empty file in /etc and link it from the preferences directory. This will give the admins the ability to reset to package defaults. [1] https://launchpad.net/bugs/535544 -- Benjamin Drung Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org)
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
