[Pkg-mozext-maintainers] Policy update

[Alexander Sack]

On Mon, Apr 19, 2010 at 01:06:14PM +0200, Benjamin Drung wrote:
> Hi,
> 
> I request some policy updates:
> 
> Filesystem Placement and Linking
> ================================
> 
> I think we should not specify a install location and drop this
> paragraph:
> 
> Packages shipping extensions for XUL-based applications like iceweasel
> or icedove should put unpack the contents of the extension in a folder
> in /usr/share/mozilla/extensions/common. Packages that also contain
> architecture-dependent material should place the architecture-dependent
> material in a folder in /usr/lib/mozilla/extensions/common and symlink
> to it from the folder under /usr/share/mozilla/extensions/common 
> 
> The second paragraph
> 
> The unpacked extension directory should then be symlinked into the
> applications directory of every XUL application that can use the
> extension. For example, the package for an extension "fubar" which works
> with iceape (app-id {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}) and
> iceweasel (app-id {ec8030f7-c20a-464f-9b0e-13a3a9e97384}) should drop
> links into
> both /usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/fubar and /usr/share/mozilla/extensions/{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}/fubar, each pointing to /usr/share/mozilla/extensions/common/fubar. 
> 
> should be changed to
> 
> The unpacked extension directory must be symbolic linked into the
> applications directory of every XUL application that can use the
> extension. For example, the package for an extension "fubar" which works
> with iceape (app-id {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}) and
> iceweasel (app-id {ec8030f7-c20a-464f-9b0e-13a3a9e97384}) must drop
> links into
> both /usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/fubar and /usr/share/mozilla/extensions/{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}/fubar, each pointing to the unpacked extension directory. You can install the extension directly into the applications directory instead of symbolic linking, if the extension supports only one XUL application.


i think the extensions/common directory is supposed to be equivalent to targetapp:
toolkit at mozilla.org

so i agree that first paragraph is wrong and should be skipped. In second paragraph just
mention that extensiosn that have "toolkit at mozilla.org" as targetApp should be linked
into the common directory.


> 
> Config Files
> ============
> 
> This section should contain these rules:
> 
>       * config files must be put into /etc/xul-ext/fubar.js
>         or /etc/xul-ext/fubar/ if more than one file is required

why do we need more than one config for an extension? I would like to avoid
that folks push all the defaults/preferences there as those should be
package defaults that can only be overloed in /etc/ dir. Of course, that
matches what you say below. Just wonder what use-cases we could have for more
than one config file?

>       * config files must be empty or contain only comments
>       * place a link in defaults/preferences/ pointing to the each
>         config file
>       * the symlink names must be the first config file in
>         defaults/preferences/ sorted alphabetical

maybe give example what mozilla-devscript does to automagically achieve
this.

 - Alexander