fe01bf0d87
"--status target-config@..." cannot really report on the status of the target side of the sync, because nothing in the command line identifies *which* sync is meant to be reported on: the same target config can be used in multiple sync configs, therefore the meta data which tracks changes is attached to the sync config, not the target config. It should not abort, though, which happened because the backend had not been properly initialized in this particular code path. Now it reports the total number of items and zero changes. Long term a dedicated error message would be better (see FDO #57145). |
||
|---|---|---|
| .. | ||
| backends | ||
| dbus | ||
| gdbus | ||
| gdbusxx | ||
| gnome-bluetooth | ||
| gtk-ui | ||
| gtk3-ui | ||
| syncevo | ||
| synthesis-includes | ||
| templates | ||
| README.h | ||
| README.templates | ||
| async.patch | ||
| client-test-app.cpp | ||
| shlibs.local | ||
| src.am | ||
| syncevo-local-sync.cpp | ||
| syncevolution.cpp | ||
| testcases.am | ||
| valgrind.supp | ||
README.templates
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.