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

Mike Hommey mh at glandium.org
Wed Jul 1 17:59:51 UTC 2009

On Wed, Jul 01, 2009 at 09:54:09AM -0400, Daniel Kahn Gillmor wrote:
> 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
> /usr/lib/mozilla/extensions/common/<ext-name>
>  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?

I'd be more in favour of the option 2 (the last one). It has the
advantage of working without modifying xulrunner (which means backwards
compatibility) and not putting all the files in /usr/lib.


More information about the Pkg-mozext-maintainers mailing list