-----BEGIN PGP SIGNED MESSAGE-----
On 15/05/12 20:00, Patrick Ohly wrote:
On Thu, 2012-02-16 at 21:27 +0100, Patrick Ohly wrote:
> On Fri, 2012-02-17 at 09:11 +1300, Jane Atkinson wrote:
>> On 17/02/12 08:51, Patrick Ohly wrote:
>>> On Fri, 2012-02-17 at 07:24 +1300, Jane Atkinson wrote:
>>>> Good question. There are two things that have held me back
>>>> here. One is figuring out the config necessary (laziness on
>>>> my part?). The other is that I've been using bluetooth, and
>>>> it sounds as though direct CalDAV sync involves setting up
>>>> other servers as well.
>>> No, just a CalDAV server, SyncEvolution (not running as
>>> server) and a SyncML capable phone should be enough. But
>>> there's still a bit code missing (reading credentials for
>>> CalDAV without the usual target-config config), so you cannot
>>> try it at the moment.
>> Just to make sure that I've got it right, this is via
> Whatever you currently use SyncEvolution for. The goal is to make
> the SyncEvolution CalDAV backend usable instead of the
> SyncEvolution EDS backend which calls the EDS CalDAV backend, for
> both syncing via Bluetooth and SyncML over HTTP.
This hasn't been forgotten
), it just didn't have
high priority. I've now added the necessary changes. Nightly
testing includes setups where CalDAV/CardDAV are used in a SyncML
server and in a SyncML client.
Jane, are you still interested? I can make binaries available, if
necessary. Otherwise just compile the "master" branches of
libsynthesis and SyncEvolution.
This is for syncing direct with CalDAV/CardDAV via Bluetooth?
Then I'm still interested. Syncing via Evolution has improved somewhat
since I started this thread, but it still misbehaves from time to time.
It's been a while since I compiled anything, so binaries would be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----