[SyncEvolution] testing ActiveSync SyncEvolution backend
Hello!
Beware if you are running Client::Source::eas_contact/event, I made a
change which will require config changes when compiling from source or
updating to the upcoming SyncEvolution 1.1.99.6.
From the activesyncd README update:
commit 6b1cf2b557e6eb3c9df9c454d0388932d10b631a
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Mon Aug 15 17:35:53 2011 +0200
SyncEvolution: use target-config@client-test-exchange for Client::Source
SyncEvolution has changed how it finds config in the commit quoted
below. Adapted README accordingly.
commit 24efbe11dbae9394d4befb2b91a25cd403907ec2
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Mon Aug 15 17:32:01 2011 +0200
testing: use target-config@client-test-$CLIENT_TEST_SERVER for Client::Source
For testing sources instantiated via SyncSource.cpp (for example, EDS)
and client-test-app.cpp (ActiveSync) append the name of the server set
via the CLIENT_TEST_SERVER env variable to target-config@client-test,
separated by a hyphen.
This allows configuring testing differently for different servers.
Was already done for CalDAV sources, inside WebDAVSourceRegister.cpp.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.