dfd0bc29af
EDS 3.8 sets X-EVOLUTION-FILE-AS to "last, first" when a contact is created without it. This leads again to unnecessary DB updates because the incoming item that the engine works with doesn't have that field set. To mitigate that issue, set FILE_AS (renamed to make the field name valid in a script) like EDS would do during writing. The downside is that all incoming items now have FILE_AS set, which will overwrite a locally stored copy of that property even if the peer did not store X-EVOLUTION-FILE-AS. Previously, as tested by testExtension, the local value was preserved. There is no good solution that works for both use cases, so allow X-EVOLUTION-FILE-AS to get lost and relax the test. |
||
|---|---|---|
| .. | ||
| backends | ||
| dbus | ||
| gdbus | ||
| gdbusxx | ||
| gnome-bluetooth | ||
| gtk-ui | ||
| gtk3-ui | ||
| syncevo | ||
| synthesis-includes | ||
| templates | ||
| async.patch | ||
| client-test-app.cpp | ||
| README.h | ||
| README.templates | ||
| shlibs.local | ||
| src.am | ||
| syncevo-local-sync.cpp | ||
| syncevolution.cpp | ||
| testcases.am | ||
| valgrind.supp | ||
The configuration templates in "templates" get installed into $(datadir)/syncevolution/templates. When adding/changing a new server, then only enter the properties which need to be changed here so that the default values can be used for the remaining properties. An icon can be added here for servers. The file name must start with "icon". Server configurations must be kept in sync in three different places: - here (if a server is installed as files) - in SyncEvolutionConfig.cpp's EvolutionSyncConfig::createServerTemplate() - in SyncEvolutionCmdline.cpp's test server configs - in test/test-dbus.py testGetConfigsTemplates() Note that server icons must come with a suitable license that allows redistribution.