[Evolution-hackers] camel eds work progress
- From: Not Zed <notzed ximian com>
- To: evolution-hackers lists ximian com
- Subject: [Evolution-hackers] camel eds work progress
- Date: Mon, 15 Nov 2004 17:55:34 +0800
Hi,
Just giving a short progress report on the camel in eds thing. I've had to make a few decisions along the way and i'm bringing them up here since nobody is ever around on irc when I am.
The story so far:
- I've branched evolution and eds with notzed-camel-eds-branch.
- I've split camel into two parts, libcamel, containing the core object, stream, mime processing and message system, and libcamel-provider, containing all the store, vfolder, remote streams, etc.
- I've moved fully things from e-util to libedataserver, removing them from e-util. e-memory.c, e-msgport.c, e-sexp.c, e-trie.c, some i updated from the core, some are new. Some other things should probably follow, like e-account/e-account-list, which are surely out of date. The current duplication is very very bad.
- I've removed the no longer used e-path.c from e-util.
- I've moved e-iconv from gal/util to libedataserver, camel is completely gal-independent now.
- I've added a bunch of fugly stuff to eds's configure.in, some of this is now duplicated in eds, so some of the conditional stuff should be based on eds's tests not duplicated, not sure what to do with it yet.
- I've made camel in it 2 calls, camel_init and camel_provider_init.
- I've fixed all the code in all the modules to use libedataserver's version of various things that were in e-util.
- I fixed a bunch of linking errors - libraries not on link lines or function names mistyped, so unless its really necessary and people running dumbly-setup distros whine too much, the fixes should wait till I merge back.
So the main changes outside of camel itself are just e-util->libedataserver moves, i think everything except mail was already linking to it anyway.
Wow, this sucked. But it should be nearly there already. I'm thinking to actually move libcamel to eds, it should be copied on the cvs server, then do everything on the new version only from that point on. This reqiures some syncing with Jeff, JP, and I most probably - the other modules aren't important.
Z
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]