On Mon, 2010-05-10 at 21:38 +0100, Alec Leamas wrote: > On 05/10/2010 08:33 PM, Patrick Ohly wrote: > > On Mon, 2010-05-10 at 18:32 +0100, Alec Leamas wrote: > > > >> On 05/10/2010 04:25 PM, Patrick Ohly wrote: > > To fix this, remove the client config. Then create it anew with > > --configure --template SyncEvolution my-client-con...@evolution > > and the other sync properties set so that it works with the local > > server. That should fix the problem. > > > > > Indeed. Works. Thanks! > > Final thoughts: it would be nice with some support for using the local > server, I doubt I'm the last one to run into this (?). A wiki page?
Would it fit into an additional section of the server HOWTO? > "Localhost" predefined in the same way as the other available servers? I > wish I could do this myself, but this is still to shaky for me. I'm not entirely sure how many people will really need this. It all depends on actually having multiple local data sources. In your case I still think that you could skip the plain file storage entirely and use EDS directly. Long term we want to simplify this "local sync", but it is uncertain how. -- 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
