On Mon, 2012-11-26 at 13:47 +0100, [email protected] wrote: > I'm looking for the reason why syncevolution 1.3 requires libsynthesis > 3.4.0.16.8. I'm not shure what to look for. Could you point me to > specific commits in syncevolution? The dependency change in > configure.ac came in with a commit that also added a lot of stuff to > the NEWS file.
In that commit I was just cleaning up for the release. The actual changes were there before. Have a look at the commit messages in libsynthesis where I bump the version. That together with the libsynthesis patches gives an idea why the new version is needed for SyncEvolution: $ git log libsynthesis_3.4.0.16+syncevolution-1-2-99-1..libsynthesis_3.4.0.16+syncevolution-1-3-1 commit 99159e0991664f8c8319e634598ea6c9bd73fcc2 Author: Patrick Ohly <[email protected]> Date: Mon Sep 10 09:15:20 2012 +0200 autotools: bumped minor version Bumped minor version so that SyncEvolution can ensure that the version it is compiled against really fixes the VJOURNAL<->plain text conversion problem. ^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^ A fix required for 1.3.1. commit 0a4a64f976a0f1812c9011efe7d832e381889e97 Author: Patrick Ohly <[email protected]> Date: Thu Aug 16 18:59:22 2012 +0200 engine: allow text->VJOURNAL conversion SyncEvolution uses the Synthesis engine to convert a plain text memo to iCalendar 2.0 in the local storage. ... And here's the feature itself, added earlier. The other commits are about build issues (pthread) and memory handling (reading uninitialized memory). Those are not essential for SyncEvolution, but useful anyway. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
