http://bugzilla.moblin.org/show_bug.cgi?id=7712 --- Comment #1 from pohly <patrick.ohly(a)intel.com&gt; 2009-12-15 04:49:01 PST --- Currently, the config template contains the following entry: <client type="plugin"> <remoterule name="ZYB"> <manufacturer>ZYB</manufacturer> <model>ZYB</model> <!-- information to disable anchors checking --> <lenientmode>yes</lenientmode> </remoterule> </client> This happens to work because the Synthesis parser accepts multiple <client> tags, but it triggers a "<client> not supported" error when the config is used in server mode. This rule needs to be added dynamically to the config if and only if running as client. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.

http://bugzilla.moblin.org/show_bug.cgi?id=7712 --- Comment #3 from pohly <patrick.ohly(a)intel.com&gt; 2010-02-02 13:06:37 PST --- Just pushed a patch for this into mb7712. I took extra care to preserve the history of all changes we ever made to syncclient_sample_config.xml, so don't be surprised to see old commit messages attached to new files. commit a3574c27e22f18f871de2b262e3284b9ad4df17d Author: Patrick Ohly <patrick.ohly(a)intel.com&gt; Date: Tue Feb 2 21:29:53 2010 +0100 XML config: use configuration composed from fragments (MB #7712) This patch replaces src/syncclient_sample_config.xml with a combination of src/syncevo/configs/syncevolution.xml and the config fragments that are shared with Synthesis upstream. These fragments are installed in /usr/share/syncevolution/xml (or the corresponding data path). From there they are read at runtime to compose the final XML configuration. Users can copy individual files into the corresponding directory hierarchy rooted at $XDG_CONFIG_HOME/syncevolution-xml to replace individual fragments. New fragments can be added there or in /usr/share. For testing, these two directories can be overridden with the SYNCEVOLUTION_XML_CONFIG_DIR env variable. No tests have been added for this yet. There's also no documentation about it except this commit message - add something to the HACKING guide once this new concept stabilizes. Developers can add new fragments in the source tree, invoke make and run the resulting binary in client mode. As before, a complete config is included in the binary. However, it is only sufficient for SyncML client mode. For server mode, the files are expected to be installed (no need to maintain a list of files in a Makefile for that) or SYNCEVOLUTION_XML_CONFIG_DIR must be set. At the moment, the following sub-directories are scanned for .xml files: - the root directory to find syncevolution.xml - datatypes, datatypes/client, datatypes/server - scripting, scripting/client, scripting/server - remoterules, remoterules/client, remoterules/server Files inside "client" or "server" sub-directories are only used when assembling a config for the corresponding mode of operation. The goal of this patch is to simplify config sharing with Synthesis (individual files are easier to manage than the monolitithic one), to share files between client and server with the possibility to add mode-specific files, and to allow users to extend the XML configuration. The most likely use case for the latter is support for more devices. Previously, remote rules for the different devices listed in syncserv_sample_config.xml were not used by SyncEvolution. This patch moves the ZYB remote rule into a client-specific remote rule, thus removing a complaint from libsynthesis about the unknown <client> element when running as server. Because we are using the unified upstream config, some parts of the config have changed: - There is a SYNCLVL field in all field list. This is currently unused by SyncEvolution, but doesn't hurt either. - A new iCalendar 2.0 all-day sanity check was added (for older Oracle servers?). - The CATEGORIES defition in vBookmark was extended. - some comment and white space changes Because this is such fundamental change, extra care was taken to minimize and verify the config changes. Here's the command which compares old and new config for clients plus its output: [...] Congwu, can you review this? Your server work is related to this. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.

http://bugzilla.moblin.org/show_bug.cgi?id=7712 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |9417 -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.

http://bugzilla.moblin.org/show_bug.cgi?id=7712 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INTEGRATED --- Comment #6 from pohly <patrick.ohly(a)intel.com&gt; 2010-02-04 01:16:03 PST --- For QA, to verify this, consider two use cases: - add a new device rule in ~/.config/syncevolution-xml - modify an existing one, like 00zyb.xml, again in your home directory This is in 0.99.5. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.