syncevolution

History

Patrick Ohly 50148ab580 scripting: prevent premature loop timeouts The more complex "avoid data loss during merging" scripting ran for longer than 5s limit under extreme conditions (full logging, busy system, running under valgrind), which resulted in aborting the script and a 10500 "local internal error" sync failure. The endless loop prevention should only be necessary to detect programming mistakes, so better disable it entirely.		2014-10-10 03:19:27 -07:00
..
datatypes	datatypes: raw text items with minimal conversion (FDO #52791 )	2014-09-12 11:38:40 +02:00
debug	XML config samples: split up into individual fragments	2010-02-02 15:34:22 +01:00
remoterules	datatypes: fix contact caching	2014-07-14 13:38:55 +02:00
scripting	scripting: prevent premature loop timeouts	2014-10-10 03:19:27 -07:00
README	XML config samples: split up into individual fragments	2010-02-02 15:34:22 +01:00
configs.am	Port build system to non-recursive Automake.	2011-08-30 16:38:34 +02:00
configs_xml.am	autotools: fixed "make dist[check]" in non-recursive Automake	2011-09-02 09:20:23 +00:00
syncevolution.xml	XML config: use configuration composed from fragments (MB #7712 )	2010-02-02 21:53:28 +01:00
update-samples.pl	XML config: use configuration composed from fragments (MB #7712 )	2010-02-02 21:53:28 +01:00

README

The sample configs contain common elements (datatypes, scripts, remote
rules, debug settings) which are maintained as separate files in the
corresponding directories. When modifying those common elements, run
"update-samples.pl" in this directory to update the sample configs.

The complete samples are under version control for several reasons:
1. avoid dependency on Perl unless common elements need to be updated
2. effect of changes on complete config show up in patches
3. the file layout and unshared parts (<client> and <server>) are
   determined by the sample configs

The naming of common elements determines the order in which they get
inserted. Files not ending in .xml are ignored. Elements that only
apply to a client or server are stored in the corresponding sub
directories, while the shared elements are in the
"debug/scripting/datatypes/remoterules".

It is a somewhat subjective choice which elements are stored in one
file and which ones are split up. The three elements of a datatype
definition (field list, profile, datatype) where split up because
there might be multiple different profiles using the same field list
and some users of these files might want to replace the default one.