On Sun, 2011-01-02 at 15:00 +0100, Patrick Ohly wrote: > Here's how you can synchronize multiple databases per peer (using a > second calendar as example): > * on the server side, configure a second calendar in the default > context: > syncevolution --configure \ > --source-property evolutionsource=<name of second > calendar on server> \ > --source-property "type=Evolution Calendar" \ > @default calendar2 > * on the client, enable the second calendar: > syncevolution --configure \ > --source-property evolutionsource=<name of second > calendar on client> \ > --source-property "type=Evolution Calendar" \ > --source-property sync=two-way \ > <config name> calendar2 > * Now synchronize using the <config name> client config.
I've had no luck installing SE 1.1 on my work desktop machine, which is a SLES 11 box that I don't have root on. There are just too many missing libraries. Is there a way to get SE 0.9.1 to use more than the four canonical sources, so that it can work as a client accessing the server configured as above? So far, I haven't been able to figure it out. -- John _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
