Patrick Ohly <patrick.ohly@...> writes: > > On Sun, 2011-10-16 at 23:11 +0200, stephan0h@... wrote: > > Am 2011-10-16 21:36, schrieb Patrick Ohly: > > > > So examples or hints to adequate documentation would be very appreciated! > > How about "man syncevolution", online at > http://syncevolution.org/documentation/syncevolution-usage ? > > The question is meant seriously. If that isn't written well enough, how > could it be improved? > > There is no explicit example for setting "database", but there is one > for setting "sync": > > syncevolution --configure \ > sync=two-way \ > memotoo <at> other addressbook > > Substitute "sync" with "database", "two-way" with your database name and > replace the config/source name with the ones matching your existing > config and you are done. >
man syncevolution was my first bet - but maybe you need to have some background knowledge to fully understand it. Some definition of concepts would be helpful. What exacatly is a peer, source, database, context, template in syncevolution's context. And I didn't quite get the relation between configuration files and the "syncevolution --configure" statement. Can I do my changes either way? Can I create a configuration file for a specific source/database? And I missed some more examples and a list of options/properties. Can I do a: syncevolution --configure databaseuser=<user> password=<pwd> \ funambol@webcal://something calendar Hope this helps a little and if I can contribute anything please tell me. thanks and kind regards, stephan _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
