I’ve been fixing bugs and implementing the provider specifics for summary files in all default Camel providers. On my Evolution, this version of the patch actually worked without any strange crashes.
You simply apply the patch to evolution-data-server/camel, you build e-d-s in /opt/camel and you set LD_LIBRARY_PATH to /opt/camel/lib before launching evolution –force-shutdown followed by evolution. You can of course also use tinymail after setting the library path. Tinymail is the real reason why I did this patch.
As I warned in my previous blog, it will rewrite all summary files (which takes some time). If you restart evolution without setting the library path, Evolution will again rewrite all summary files using the old format. So nothing really dangerous happens. But still make a backup of your evolution data directory.
If you are online, Evolution still consumes a lot memory. That’s because of memory problems in the Camel provider implementations that scan for new messages. I hope I (finally) inspired people to take a look at these problems. If these are also fixed, Evolution will on average (I think) consume less then 50MB. Try Evolution (with the patch) in offline mode and measure it with valgrind. You’ll see.
In general, visit my files and check for a new version of the patch before applying anything. The filename is appended with fixesXX.diff