On Tue, Nov 15, 2011 at 10:03 AM, Matthew Barnes <mbar...@redhat.com> wrote:
> I have severed all of Camel's remaining dependencies on libedataserver,
> mostly by way of code duplication.  In particular, all of Camel's search
> and filtering code now uses CamelSExp, which is a clone of ESExp.
> libcamel now builds first in the evolution-data-server module, and its
> pkg-config file has shed its libedataserver-1.2 requirement.  You should
> consider it a base library for E-D-S, like libsoup or libgdata.
> There is no longer any _technical_ reason why Camel needs to be bundled
> in the evolution-data-server module.  I DO intend to split Camel off at
> some point, but not yet.  Parts of its API are still a complete mess and
> I'd like to give them some attention and also reach some semblance of
> API stability for the library as a whole.  We're not there yet.

When I complete my branch & merge mail to EDS, more of mail code is
gonna end up there (of course, its atleast one more release away). I
don't see a chance of camel being missed out there ;-)

evolution-hackers mailing list
To change your list options or unsubscribe, visit ...

Reply via email to