On Tue, 2008-05-20 at 10:54 +0100, Mark Ellis wrote:
> clarify something first. John, is there any problem with using opensync
> 0.2x to do a sync, replace opensync and the plugin with 0.3x, and then
> do another sync ? If this works, then I think opensync versions in /etc
> would be a good thing for distros. Of course it would be better worked
> out programmatically, but I don't know if that is possible.
>
I strongly suspect this might not work, though I haven't delved into
Opensync internals enough to be 100% sure. I think that Opensync's sync
database is different between OS0.2x and OS0.3x - meaning that the files
and Opensync sync partnership generated by OS0.2x would not be
compatible with OS0.3x (all in the ~/.opensync directory). So we can not
use old 0.2x sync data with 0.3x.
I can see the point now of putting a systemwide file in /etc, and this
would not be difficult to implement. Not only would AuthMethod and
OpensyncXMLFormat benefit from this, but some of the file sync config
settings could be hardware (i.e. system) dependent rather than user
dependent.
I would be happy to take the approach of scanning /etc, then ~/.synce,
and if unset use the app defaults.
Alternatively, packagers could put the template file in somewhere
sensible, such as /usr/share/synce/examples or similar, where it could
be found by users who want to customize their configuration.
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
