Super, thanks. I'll update the document over the weekend.
On Thu, May 22, 2014 at 4:19 PM, Patrick Ohly <[email protected]>wrote: > On Wed, 2014-04-23 at 13:10 +0200, Emiliano Heyns wrote: > > > I've pushed out a new version at > > http://reichenhack.github.io/syncevolution.html that now adds google > > sync; I'd love it if someone could go over it to see if there are > > mistakes left. > > | syncevolution --configure --template none backend=file > | database="file:///tmp/my-contacts-store" databaseformat=text/vcard > | @local local-contacts > > | I did not explicitly create the datastore or the contexts; both are > | created when first referenced, and updated if they already exist. I > | also did not explicitly tell SyncEvolution that we're setting up a > | datastore (rather than a sync-config, which we'll set up with a > | similar command); SyncEvolution knows that we're configuring a > | datastore because we are passing it properties that are relevant to > | datastores. > > This is not quite correct. SyncEvolution does not look at the properties > to determine what is meant to be changed. That is determined exclusively > by the sync config and source names (@local and local-contacts in the > example above). The configs corresponding to that will get updated with > the properties from the command line that match the entity that gets > updated (sync properties go into the sync config, source properties into > the source configs, foo/<source property> goes into the config of source > foo). > > I've only briefly scanned the rest of the document; looks good. > > -- > 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
