Patrick, Ok, I am able to create addressbooks in the same way I do for folks eds backend unit tests by copying an ini file. The last snag I'm hitting is that syncevo-local-sync is missing in our packages. Is there some configure line that builds that? I don't see it in /usr/local/lib/syncevolution in my build from git either.
thanks, Jeremy On Fri, Aug 31, 2012 at 12:58 PM, Patrick Ohly <[email protected]> wrote: > On Fri, 2012-08-31 at 10:24 -0600, Jeremy Whiting wrote: >> Patrick, >> >> Thanks for the fix. Now --print-items is working, though it's only >> printing a bunch of id numbers between 0 and 110 (probably how many >> contacts I have on my phone at the moment). When I attempt the next >> step from the README file I get an error because gnome-keyring is not >> running. What does syncevolution need the keyring for? > > The "password" property values are stored in it. You can control the > usage of the keyring with the "keyring" property (disable, use KWallet > instead, ...). Or compile SyncEvolution without GNOME keyring support in > the first place. > >> Our usecase is when a phone is paired with the device by bluetooth we >> would like to sync the contacts into an eds addressbook named by the >> mac address of the phone (or some other unique identifier, but mac >> address seems to be fine so far). The steps in the README seem to set >> up the sync to put contacts into addressbook, is there a way to >> specify which addressbook to sync into I hope? > > syncevolution --configure database=<name or UUID> @default addressbook > > Creating and deleting that address book is currently out of scope for > SyncEvolution. At some point it was possible to have it create an > address book by using a file:///<file name> URI as database value, but > accessing files like that was removed in EDS a while back. > > -- > 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. > > _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
