I already told about Lightning in this blog. Since version 0.5 is out to replace version 0.3.1, I recompiled quickly the extension on a clean install of Icedove 2.0.0.4.dfsg1 (but it will work with icedove 2.0.0.3, since I kept a copy around and there is no obvious bug). I recompile because people told me that the pristine binary Lightning 0.5 does not work.

[Update 16/07/2007] I added a small description of how to include the localisation data.

I will hereby give a few details about the recompilation (I assume that pbuilder is installed, tracks unstable and works ok):

• pbuilder update; pbuilder login
• Modify /etc/apt/sources.list to make the source repository available
• apt-get update; apt-get install wget; apt-get build-dep icedove; apt-get source icedove
• cd icedove-2.0.0.4dfsg1; tar xjf icedove-2.0.0.4.dfsg1-source.tar.bz2
• wget http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.5/source/lightning-sunbird-0.5-source.tar.bz2
• tar xjf lightning-sunbird-0.5-source.tar.bz2 mozilla/calendar
• rm icedove-2.0.0.4.dfsg1-source.tar.bz2;tar cjf icedove-2.0.0.4.dfsg1-source.tar.bz2
• Modify debian/rules to replace (line 65) --enable-extensions=default \ by --enable-extensions=default,lightning \
• debian/rules binary
• Go grow a coffee tree, wait for coffee grains to appear, make coffee.
• When the compilation is finished (from the outside of the chroot created by pbuilder) the file in .../icedove-2.0.0.4.dfsg1/build-tree/mozilla/dist/xpi-stage/lightning.xpi. Install in Icedove (Tools → Add-ons → Install). Drink coffee.

[Update 16/07/2007] The localisation data (everything that is needed to have Lightning user interface in different languages) is a bit more complicated to get, because it looks like it is not included in the source download. Thomas Wassong
did the trick — viele danken, Thomas. The method is to download one of the already localised packages (on the official Mozilla website), such as lightning-0.5.linux-i686.xpi, unzip it (a .xpi is just a zip file, unzip the .xpi that you just did build, and stuff all the chrome/calendar-xx.jar and chrome/lightning-xx.jar from the official build into your own build. Yes, this is not a clean work, but since the localization data is not inside the source...