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

[Ximin Luo]

On 15/07/13 19:50, Daniel Kahn Gillmor wrote:
> On 07/15/2013 02:37 PM, Klearchos-Angelos Gkountras wrote:
> 
>> I am using Debian Sid and icedove as my personal email programm and I
>> didn't install enigmail via repos but with icedove's add-ons manager .
>> Please describe in which branch of debian is the problem ;)
> 
> This goes against the general recommendations of the enigmail team --
> their suggestion is that you install icedove/thunderbird and enigmail
> from the same source; if you use your distro's version of the MUA, use
> your distro's version of the plugin; if you use the "upstream" binary
> distribution of the MUA, use the "upstream" binary distribution of the
> plugin.
> 
>> don't forget that debian has three branches
>> branch 	    code name
>> ------------------------
>> stable    |  wheezy
>> testing   |  jessie
>> unstable  |  sid
>> ------------------------
> 
> Andy's concern is about iceape (seamonkey) which is version 2.7.12-1 in
> all three active suites of debian (wheezy, jessie, and sid).
> 
> icedove is now at version 17.0.7 in wheezy (thanks to a security
> update), and enigmail was updated to match the icedove version. However,
> iceape has not been similarly updated.  There appears to be less
> developer time spent on iceape than on the other mozilla variants :(
> 
> So Andy is right that there are versioning issues with enigmail in
> wheezy if you try to use it with iceape.
> 
> As one of the members of the debian project who is trying to keep
> enigmail functional in debian, i'm not sure what the answer is.  We
> would love to continue to support enigmail for iceape as well as
> icedove, but i'm not sure what the right thing to do is.  if we're using
> the system-installed locations, i don't see how we can have the two
> versions of enigmail co-installable.
> 
> I'm cc'ing the mozilla extension packaging team on the e-mail to see if
> anyone has any suggestions for resolving this conflict in a healthy way.
> 

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

> Sorry to not have any more productive answers myself,
> 
> 	--dkg
> 
> 
> 
> _______________________________________________
> Pkg-mozext-maintainers mailing list
> Pkg-mozext-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mozext-maintainers
> 


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