Differences between revisions 6 and 7
Revision 6 as of 2009-06-29 20:01:09
Size: 3261
Comment: typos
Revision 7 as of 2009-06-29 20:54:15
Size: 3260
Editor: XTaran
Comment: fixed typo: linb -> lib
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
Packages shipping extensions for XUL based applications like iceweasel or icedove should put them in ''/usr/share/xul-extensions'' or ''/usr/linb/xul-extensions''. Using the former if there's only architecture independent data or the later with architecture dependent data. Packages shipping extensions for XUL based applications like iceweasel or icedove should put them in ''/usr/share/xul-extensions'' or ''/usr/lib/xul-extensions''. Using the former if there's only architecture independent data or the later with architecture dependent data.

Mozilla Extension Packaging Team

Infrastructure

Interacting with the team

Task description

Packaging of extensions for Icedove, Iceweasel, Iceape and Iceowl (aka Thunderbird, Firefox, Seamonkey and Sunbird).

Joining

Simply request to join the project via Alioth.

TODO

  • cdbs class to ease packaging
  • ice*-extensions-config: lets the adminstrator decide which of the installed extensions is enabled by default (similar to ca-certificates)

  • Finish extension policy

Policy for packaging XUL based applications

This is a draft and up for discussion on pkg-mozext-maintainers@lists.alioth.debian.org:

Packages shipping extensions for XUL based applications like iceweasel or icedove should put them in /usr/share/xul-extensions or /usr/lib/xul-extensions. Using the former if there's only architecture independent data or the later with architecture dependent data.

The extensions should then be symlinked into the applications directory (e.g. /usr/lib/iceweasel/extensions) for all supported XUL applications.

The binary package's name should be xul-ext-<ext> with <ext> being the exteonsions name. E.g. xul-ext-nostalgy for Icedove's nostalgy extension.

In order to ease finding extensions for a given application the packages should

Provides: <xul-based-app1>-<extension>, <xul-based-app2>-<extension>, ...

and

Enhances: <xul-based-app1>, <xul-based-app2>, ...

where xul-based-app1 and xul-based-app2 are e.g. iceweasel and iceape.

Rationale:

  • canonical place to look for extensions instead of having them spread across several directories (iceape, iceowl, icedove, iceweasel, ...)
  • consistent naming (visual grouping) for all extensions (no mozilla-<ext> vs. iceweasel-<ext> for extensions supporting more than one XUL based application)

  • eases automatic packaging of extensions
  • ease work for downstream distributions

Packages

Use the following snippet for your sources.list:

deb http://pkg-mozext.alioth.debian.org/packages lenny/i386/
deb http://pkg-mozext.alioth.debian.org/packages lenny/all/
deb-src http://pkg-mozext.alioth.debian.org/packages lenny/source/

deb http://pkg-mozext.alioth.debian.org/packages sid/i386/
deb http://pkg-mozext.alioth.debian.org/packages sid/all/
deb-src http://pkg-mozext.alioth.debian.org/packages sid/source/

To install an extension run

apt-get install <EXTENSION>

If you are member of the group pkg-mozext you can upload with the following dput configuration:

[pkg-mozext]
method = scp
fqdn = alioth.debian.org
incoming = /home/groups/pkg-mozext/htdocs/packages/mini-dinstall/incoming/
post_upload_command = ssh alioth.debian.org /home/groups/pkg-mozext/mini-dinstall.sh