[Pkg-mozext-maintainers] [Enigmail] Enigmail in Debian

[Daniel Kahn Gillmor]

On 07/15/2013 04:34 PM, Ximin Luo wrote:
> For xul-ext-gnome-keyring, I am building the extension twice, against both xulrunner-dev *and* icedove-dev, then packaging both binaries into the same XUL extension and using the appId to tell XPCOM to conditionally load the correct one. Have a look at debian/rules for source, although I don't know if the same strategy would be applicable to enigmail. I'm also not sure which version of the xulrunner lib the Debian iceape uses.
> 
> http://packages.debian.org/sid/xul-ext-gnome-keyring
> https://github.com/infinity0/mozilla-gnome-keyring/tree/debian

This is a neat approach, but my understanding of enigmail is that the
the issue is not just building against different -dev environments;
there are actually changes in enigmail source between the different
versions that are aligned to the behavior of the corresponding MUA versions.

So i don't think just building the same source package twice against
different dev environments will do the trick :(

	--dkg

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