f919856f6b
Having to look for XDG config files in two different locations was confusing. The XDG_DATA_HOME=temp-testpim/local/cache was also wrong, because "cache" is for XDG_CACHE_HOME. Now XDG_CONFIG/CACHE/DATA_HOME must be set to temp-testpim/[config|cache|data], which is consistent with the usage of private XDG dirs in test-dbus.py, and the directories are shared by EDS and PIM Manager. EDS keeps running throughout all tests. This must be taken into account when cleaning temp-testpim. evolution-source-registry does not cope with removal of its "sources" directory, so we have to keep that, although we are removing its content. evolution-addressbook-factory may continue to have an ESource open although its client *and* the source are gone (should be fixed in EDS by tracking clients *and* source removals!). When that happens and we reuse a DB UUID, evolution-addressbook-factory continues to use the deleted instance, leading to IO errors. To avoid that inside a test run, we use different UID prefices for each test, by embedding the test name. To avoid it between test runs, kill evolution-addressbook-factory first. When killing evolution-source-registry, use -9, because otherwise it shuts down too slowly, which may lead to test failures when it talks to the closing instance. For the system address book we can't change the UID between tests, so we must not delete it. |
||
|---|---|---|
| .. | ||
| 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.