SyncEvolution 188.8.131.52 "beyond SyncML" released
Release 184.108.40.206 is the first release candidate for 1.2. It has gone through a long stabilization period and thus is suitable for normal users.
The major new feature of the 1.2 release is support for non-SyncML protocols in general and CalDAV/CardDAV in particular. ActiveSync support is in development.
Changes 1.1.1 -> 220.127.116.11
The major new feature of the 1.2 release is support for non-SyncML protocols in general and CalDAV/CardDAV in particular. ActiveSync support is in development. These protocols are implemented as backends which are combined with other backends by SyncEvolution in a so called "local sync". The GTK sync-ui does not yet support configuring non-SyncML protocols. See the README and man page for more information on how to use the new feature via the command line.
Properties not supported by SyncML servers can now be preserved locally in two-way synchronization (BMC #15030). This depends on information about what properties a SyncML server supports ("CtCap"), which is typically not provided by servers. SyncEvolution contains a copy of that information for Google Contacts (BMC #15029).
Akonadi backend and KWallet support were merged. They are not included yet in syncevolution.org binaries. To use them compile from source.
The configuration format was updated to solve a conceptual problem inherited with the legacy property names: the "type" property had multiple, sometimes conflicting roles. For example, setting the preferred data format for sync with one peer might have changed the backend selection for some other peer (BMC #1023). Now "backend/databaseFormat/syncFormat/forceSyncFormat" replace "type". "type" is still accepted by the command line as alias.
Old configurations can still be read. But writing, as it happens during a sync, must migrate the configuration first. In contrast to earlier, more experimental releases in the 1.2 series, 18.104.22.168 and later automatically migrate configurations. The old configurations will still be available (see "syncevolution --print-configs") but must be renamed manually to use them again under their original names with older SyncEvolution releases.
- a problem with enabling release mode required replacing 22.214.171.124 with a fixed 126.96.36.199a release
- syncevo-http-server was enhanced considerably. See the HTTP server HOWTO
- support NetworkManager API >= 0.9 (BMC #19470)
- Sync mode is recorded when running in SyncML server mode (BMC #2786).
- syncevo-dbus-server automatically stops when some of its libraries are updated and restarts if auto-syncing is on (BMC #14955).
- Using the --sync-property and --source-property command line options is optional, just specifying the property assignment is enough.
- Added support for Buteo, mKCal and QtContacts in MeeGo. Buteo and mKCal were removed again from MeeGo, so the code is obsolete. The QtContacts backend may be still be useful to access items via that API, but for syncing on MeeGo the normal EDS backend is used since MeeGo reverted back to EDS as PIM storage.
- code cleanup and various minor fixes/improvements, see ChangeLog
Source, Installation, Further information
Source snapshots are in http://downloads.syncevolution.org/syncevolution/sources
i386, amd64 and lpia binaries for Debian-based distributions are available via the "unstable" syncevolution.org repository. Add the following entry to your /apt/source.list, then install "syncevolution-evolution":
deb http://downloads.syncevolution.org/apt unstable main
These binaries include the "sync-ui" GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).
The same binaries are also available as .tar.gz and .rpm archives in http://downloads.syncevolution.org/syncevolution/evolution. In contrast to 0.8.x archives, the 1.0 .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.
After installation, follow the getting started steps.