June 2011 - syncevolution@synevolution.org

[SyncEvolution] --disable-mlite (was: Re: SE_2011-06-15-21-30_all: head-gcc-4.6-amd64)

by Patrick Ohly

On Mi, 2011-06-15 at 15:22 +0100, Zhu, Yongsheng wrote: > Preparation Results > prepare > Value > libsynthesis-fetch-config > okay > syncevolution-fetch-config > okay > compile > failed > dist > skipped > Total passed cases (all: 4) > 2 configure: error: required mlite package not found, use --disable-mlite to compile without mlite based notifications Salvatore, please change the configure logic so that mlite support is disabled by default. It should have to be enabled explicitly. When enabled explicitly, fail hard if it is not found. The rationale is that normal users shouldn't have to worry about adding --disable-mlite, a feature which will only be useful in MeeGo. -- 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.

10 years, 5 months

2
2
0 / 0

[SyncEvolution] question

by Laurent Emil

Hi all , i wanna ask if the major difference between syncevolution 0.8.1 and syncevolution 1.1.1 version is only replacing funambol by libsynthesis . is there any other raison for changing the code architecture? Regards

10 years, 5 months

2
1
0 / 0

[SyncEvolution] [PATCH] Replace "" with [] in call to PKG_CHECK_MODULES

by david＠tethera.net

From: David Bremner <bremner(a)unb.ca> If not, then autoconf 2.68 generates ""synthesis >= 3.4"" and the extra level of quoting causes the pkg-config call to fail. --- configure-pre.in | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configure-pre.in b/configure-pre.in index 1c9c8eb..a195903 100644 --- a/configure-pre.in +++ b/configure-pre.in @@ -686,7 +686,7 @@ elif test "$SYNTHESISSRC" != "none" && test -d $srcdir/src/synthesis; then esac elif test "$enable_shared" = "no"; then # link against engine - PKG_CHECK_MODULES(SYNTHESIS, "synthesis >= 3.4") + PKG_CHECK_MODULES(SYNTHESIS, [synthesis >= 3.4]) SYNTHESIS_ENGINE="$SYNTHESIS_LIBS -lsynthesis" else # link against SDK alone, except in client-test @@ -694,7 +694,7 @@ else #SYNTHESIS_ENGINE="`echo $SYNTHESIS_LIBS | sed -e 's/-lsynthesisstubs/-lsynthesis/'`" # can't use the SDK alone because of sysync::SySyncDebugPuts() - PKG_CHECK_MODULES(SYNTHESIS, "synthesis >= 3.4") + PKG_CHECK_MODULES(SYNTHESIS, [synthesis >= 3.4]) SYNTHESIS_ENGINE="$SYNTHESIS_LIBS" fi -- 1.7.4.4

10 years, 6 months

2
1
0 / 0

[SyncEvolution] [PATCHES] Webdav: in case of 404 when contacting server, assume 401

by Salvatore Iovene

If we're contacting a webdav server, trying to retrieve properties at an address like https://example.com/dav/username/events, a likely reason for a 404 error is that the username is invalid. We can't have a proper heuristic to determine that, so let's just assume an authentication error and inform the user accordingly.

10 years, 6 months

2
3
0 / 0

[SyncEvolution] new shared libraries

by David Bremner

I see 1.1.99.4 provides libsyncevolution and libsyncevo-dbus in /usr/lib. Are these intended to by publicly usable (i.e. by other software?). If so, is the API documented somewhere? d

10 years, 6 months

2
1
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

syncevolution June 2011