-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15.07.13 23:14, Daniel Kahn Gillmor wrote: > 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 :(
That's correct. Enigmail v1.4.x won't work with Thunderbird 17, and Enigmail v1.5.x won't work with SeaMonkey 2.7. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQEVAwUBUeTqnsk25cDiHiw+AQidAAf/VcWhw1B8F8Aa3eqwqr9PYMa5s7EC80NP KSkAa2OMCRcets5TKKQqBXKG7poVKM8R5amWIXIdhQMAYGIeYBRskYw5UNJc36hm 3NePVflZvokZpvxuUDMF7T/fHkBPvklMaKy09uorVWEkCUZgo7VZeaZOKaREyiuB K5K7D46NPJeE9hEkVKoyXrEHU7hNogaoI0tDFkjBz+VdEJWR5h8CTTgmsTpry/+b SBpB3nwoufpSJWDfkvmfT/4Z+i0tEaMviKv8tS3BFG9nE/+UBaPMJvvIi5Ejf3Xf 3XZTZSP5m4ouNulAWj2gH855RqNpT9COJeOmU9vKdau1tEmTyoMXSQ== =DeZ6 -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
