[Evolution] Camel is now in eds.

[Not Zed <notzed ximian com>]

Ok so i've finished the camel move to evolution-data-server module.

Essentially it is just moving a private library from evolution to be a private library in e-d-s, at least more or less, for now.

Some things have moved a little, and some other things need changing, here is a summary of some of the changes.

• libcamel has been split into two parts, libcamel-provider, and libcamel.  None of the headers have moved though.  libcamel does MIME handling and message processing.  provider does all the backend related things, ssl streams, sasl authentication, stores, folders, etc.
• none of the provider implementation headers are installed anymore, i think that was just a bug originally.
• it is now installed into ${prefix}/lib, and versioned as with libedataserver, etc.  i.e libcamel-1.2.so.0.0.0 to start with.
• there are now two package-config packages.  camel-1.2 and camel-provider-1.2, you can't get the camel providerdir variable from the camel one, etc.
• the providers have moved from ${prefix}/lib/evolution/2.x/camel-providers/ to ${prefix}/lib/evolution-data-server-1.2/camel-providers
• the camel headers are installed in ${prefix}/include/evolution-data-server-1.2/camel
• a bunch of stuff that was in e-util has been moved to libedataserver and/or updated and/or then removed from e-util so there isn't duplication.  a couple more things may end up doing the same.
• probably other things i've forgotten ...

There are still a couple of little things to be done: the translations all need to be moved to eds.  I don't know if there's a tool that i can use to extract and merge the relevent evolution strings into evolution-data-server's po files?  Camel's makefiles would need to setup its own translation domain too.  Perhaps it should all be setup in a camel domain?  Thoughts, ideas?  This should be the most important thing to fix first.

I will cvs remove the evolution/camel soon too.  For now it is just sitting there dead in head.

Note that any work done to evolution/camel in cvs after yesterday will not be present in the cvs tree in evolution-data-server, so some manual patching work may be required (e.g. for the groupwise soap provider).

I think that is about all.  I may have forgotten some minor things; i did many rebuilds and ldd checks to make sure everything is using the proper new locations for all the libraries, so i'm fairly confident it should at least run.

Hopefully I haven't added any unacceptable dependencies or messed up the configure script too much, I just did a lot of cut and pasting.

 Michael

--

Michael Zucchi <notzed ximian com> "Ride, Work, Sleep. Beer." Novell's Evolution and Free Software Developer