f663c2716c
Only the "client-test" executable and its test data were installed so far, in /usr/bin resp. the doc dir. Now also test-dbus.py and testpim.py plus their data files get installed, using a new /usr/lib/syncevolution/test directory for all test files and commands. "runtests.py --prebuilt" can take one or more .deb files including these tests, will install them as the "compile" operation and then will use the installed SyncEvolution, without overriding any paths. This relies on having suitable rights for "dpkg" and /usr/lib/syncevolution/test; the way how that is done in the nightly testing is via chroots where the entire file system is writable by the normal test user. Normal users without such write access to /usr/lib/syncevolution/test need to copy that directory into their home directory first. |
||
|---|---|---|
| .. | ||
| 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.