On Do, 2011-04-28 at 21:16 +0100, Frederik Elwert wrote:
thanks a lot! It works like charm with the new version.
Don't say that - it makes your emails drop in my priority list ;-)
If anyone else it interested in the setup, here are the commands I
$ syncevolution --configure backend=file \
databaseFormat=text/x-vcard @gigaset addressbook
$ syncevolution --configure syncURL=local://@gigaset peerIsClient=1 \
sync=one-way-from-server uri=addressbook --template default gigaset \
There is just one thing I don’t really get yet: Against the
sync=one-way-from-server setting, syncs are performed two-way. That
doesn’t really harm, I think, but it seems rather strange.
I can't reproduce that. For me, changes made in the directory (editing
files, adding files) are ignored during a sync and never make it back to
Evolution, as intended.
Just out of curiosity: If I wanted to make the phone sync even
I’d like to achieve to things: a) export only entries with a phone
number, and b) get rid of the PHOTO property for the items in the target
directory. Are there (rather) simple ways of doing this with
Such things are possible, but not easily. Basically you would have to:
* Define your own, specialized file backend (the existing one is
not configurable enough).
* Define your own Synthesis vCard profile which does not define
PHOTO. Use it instead of the default vCard profile.
* Add filtering scripts which only accept contacts on the
Evolution side which have at least one TEL.
I could also just write a quick python script to post-process the
but I was curious if there are built-in ways for this.
That's probably easier.
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.