[Pkg-mozext-maintainers] Draft Mozilla extension packaging policy

Daniel Kahn Gillmor dkg at fifthhorseman.net
Wed Jul 1 13:54:09 UTC 2009

On 06/29/2009 04:41 PM, Mike Hommey wrote:
> Note that upstream supports
> /usr/share/mozilla/extensions/{application-uuid}/ directories, and there
> may be /usr/share/mozilla/extensions/common supported at some time in
> the future, out of the box.

It occurred to me today that this won't be policy-compliant for
extensions with architecture-dependent components, since /usr/share is
supposed to be architecture-independent.  If we go with this location,
what should we recommend arch-dependent extensions do?

I can see a few possible options:

 0) ship the whole extension in
/usr/lib/mozilla/extensions/common/<ext-name> , and provide a symlink to
there from  /usr/share/mozilla/extensions/common/<ext-name>

 1) encourage xulapps (via upstream?) to check both
/usr/share/mozilla/extensions *and* /usr/lib/mozilla/extensions, and
just ship arch-dep extensions in

 2)  put arch-dep material in /usr/lib/<ext-name>/, ship all the rest
(arch-independent material) of the extension in
/usr/share/mozilla/extensions/common/<ext-name>/,and symlink to the
arch-dep material from there.

any other options?  Any thoughts about which path presents a better plan
for the long term?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mozext-maintainers/attachments/20090701/b0578fbd/attachment.pgp>

More information about the Pkg-mozext-maintainers mailing list