7feed6634a
The EDS backend in the syncevolution.org packages are compiled for the API in EDS <= 3.4. With some tricks (dynamically loading libs) it works across a range of libecal and libebook releases. Now the syncevolution-evolution meta package declares that it depends on one of these libecal/ebook libraries (was missing earlier), to ensure that the libs get installed on a system which did not have them already. The dynamic loading will no longer attempt to work with EDS 3.6. For EDS 3.6 it will be necessary to update the EClient variant of the EDS backend and compile the syncevolution.org binaries differently. |
||
|---|---|---|
| .. | ||
| 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.