From casaxa@gmail.com Sun Sep 1 16:12:51 2013 Return-Path: X-Original-To: evolution-hackers@gnome.org Delivered-To: evolution-hackers@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by restaurant.gnome.org (Postfix) with ESMTP id D8528762EB for ; Sun, 1 Sep 2013 16:12:51 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from restaurant.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ok2QnWJa01gG for ; Sun, 1 Sep 2013 16:12:38 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by restaurant.gnome.org (Postfix) with ESMTP id E58AC762EF for ; Sun, 1 Sep 2013 16:12:27 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id ez12so461381wid.3 for ; Sun, 01 Sep 2013 09:12:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5QEHQKTZpYFIxAdgexqvzr7VDFZKc+tzzFLGDXKqaBk=; b=vMs0hJDUUdNk6QImg0tLEeGSvIuvhZ7V90KCLEog8fV1s6zRv32SQg/1tMmn5W035M J9e/A4WktVq4sVqYdxM735Vx16dIH3OJJHi4kDqtuLXBaTGcV2b9EFbDNJfrDh/C4rBR XxkOCPzIwxeq3dtlDQLDPsnwUgaQpjeQUvHr/fk37qzXlgPZ131jl5JofcWtEP3zBY6N Pt9uB1oLwqbWmmyaseOaymlVoUS00GZD6gFmp53FecVScYSxAz8CyPVmAsgB03EYNsSA NFQg/n8bsGw+hhAbISjEj/SHvRVNJEx/hTAwXz/Dw1mdvB+rVDmAFn/my8uGLomOKFb/ XYsQ== MIME-Version: 1.0 X-Received: by 10.180.210.231 with SMTP id mx7mr10282061wic.5.1378051945440; Sun, 01 Sep 2013 09:12:25 -0700 (PDT) Received: by 10.194.46.70 with HTTP; Sun, 1 Sep 2013 09:12:25 -0700 (PDT) Date: Sun, 1 Sep 2013 13:12:25 -0300 Message-ID: From: Sasa Ostrouska To: evolution-hackers@gnome.org Content-Type: multipart/alternative; boundary=001a11c25d32b0a9be04e554b8fa Subject: [Evolution-hackers] geocode-glib version X-BeenThere: evolution-hackers@gnome.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion about Evolution code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2013 16:12:51 -0000 --001a11c25d32b0a9be04e554b8fa Content-Type: text/plain; charset=ISO-8859-1 Hi I was just wondering if is there a special reason to use geocode-glib version 0.99.0 as there is already out a 0.99.2 so would be nice to have in configure.ac geocode-glib >= 0.99.0 instead of geocode-glib = 0.99.0 Rgds Saxa --001a11c25d32b0a9be04e554b8fa Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi I was just wondering if is there a speci= al reason to use geocode-glib version 0.99.0 as there is
already o= ut a 0.99.2 so would be nice to have in con= figure.ac geocode-glib >=3D 0.99.0 instead of geocode-glib =3D 0.99.= 0

Rgds
Saxa
--001a11c25d32b0a9be04e554b8fa-- From mbarnes@redhat.com Sun Sep 1 17:08:19 2013 Return-Path: X-Original-To: evolution-hackers@gnome.org Delivered-To: evolution-hackers@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by restaurant.gnome.org (Postfix) with ESMTP id 8B94C762EB for ; Sun, 1 Sep 2013 17:08:19 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -7.458 X-Spam-Level: X-Spam-Status: No, score=-7.458 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.556, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from restaurant.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iy2IY58tvod8 for ; Sun, 1 Sep 2013 17:08:05 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by restaurant.gnome.org (Postfix) with ESMTP id 94AFC762D1 for ; Sun, 1 Sep 2013 17:07:55 +0000 (UTC) Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r81H7qb7016595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 1 Sep 2013 13:07:52 -0400 Received: from [10.3.112.17] ([10.3.112.17]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r81H7obw019221; Sun, 1 Sep 2013 13:07:51 -0400 Message-ID: <1378055270.17861.6.camel@localhost.localdomain> From: Matthew Barnes To: Sasa Ostrouska Date: Sun, 01 Sep 2013 13:07:50 -0400 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 Cc: evolution-hackers@gnome.org Subject: Re: [Evolution-hackers] geocode-glib version X-BeenThere: evolution-hackers@gnome.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion about Evolution code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2013 17:08:19 -0000 On Sun, 2013-09-01 at 13:12 -0300, Sasa Ostrouska wrote: > Hi I was just wondering if is there a special reason to use > geocode-glib version 0.99.0 as there is > > already out a 0.99.2 so would be nice to have in configure.ac > geocode-glib >= 0.99.0 instead of geocode-glib = 0.99.0 There were substantial API changes on the master branch of geocode-glib that we don't yet support. I don't yet know if 0.99.2 includes those changes or if it's backward compatible with 0.99.0. If it's backward compatible then we can support it for Evolution 3.10, otherwise it has to wait for Evolution 3.11/3.12. Matthew Barnes From casaxa@gmail.com Sun Sep 1 21:40:50 2013 Return-Path: X-Original-To: evolution-hackers@gnome.org Delivered-To: evolution-hackers@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by restaurant.gnome.org (Postfix) with ESMTP id 747EC768D5 for ; Sun, 1 Sep 2013 21:40:50 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham Received: from restaurant.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpF9gWK8LXa8 for ; Sun, 1 Sep 2013 21:40:37 +0000 (UTC) Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) by restaurant.gnome.org (Postfix) with ESMTP id E3C8F7662F for ; Sun, 1 Sep 2013 21:40:26 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id p60so845646wes.28 for ; Sun, 01 Sep 2013 14:40:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ccaTiRA/GwI4v0ASchMySYCCRSJldr/+k8YX2zMMO3c=; b=rtevN0taSsZWnvp9LL5ZdGj8bJ4LDNQnJ8GV3P50jk78xTcm/8fwd+mu+epx/R7AmX 6GA521PReAdr4Ex0JS/pDP3guo2jvdG8cjBuHLnQTQ6enJsbhJk47sxzxgEk1ZHTdKOC BZCg6QttQBkcvlSGplVkZ9aECYl+SbGAytyZh6CRT1pzXay/+9FHmjlhlrwaEt8Sxjhc 2hv0TIiM61pSX5yxQ9Q4ZAra0iHwcuvI03Wf9kmPUZR9K9gviCC4KQUO6I7UkHJ0ucF0 jHpAcqiDVMX5xU0ILloJfFerAQpbOwoOYfhlzV5fOzXhjo30ApuSdFljyuyN0gT9MFyP aOaA== MIME-Version: 1.0 X-Received: by 10.180.229.103 with SMTP id sp7mr6264558wic.2.1378071623958; Sun, 01 Sep 2013 14:40:23 -0700 (PDT) Received: by 10.194.46.70 with HTTP; Sun, 1 Sep 2013 14:40:23 -0700 (PDT) In-Reply-To: References: <1378055270.17861.6.camel@localhost.localdomain> Date: Sun, 1 Sep 2013 18:40:23 -0300 Message-ID: From: Sasa Ostrouska To: evolution-hackers@gnome.org Content-Type: multipart/alternative; boundary=001a1135fafe9f075804e5594dd7 Subject: Re: [Evolution-hackers] geocode-glib version X-BeenThere: evolution-hackers@gnome.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Discussion about Evolution code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2013 21:40:50 -0000 --001a1135fafe9f075804e5594dd7 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Sep 1, 2013 at 2:07 PM, Matthew Barnes wrote: > On Sun, 2013-09-01 at 13:12 -0300, Sasa Ostrouska wrote: > > Hi I was just wondering if is there a special reason to use > > geocode-glib version 0.99.0 as there is > > > > already out a 0.99.2 so would be nice to have in configure.ac > > geocode-glib >= 0.99.0 instead of geocode-glib = 0.99.0 > > There were substantial API changes on the master branch of geocode-glib > that we don't yet support. > > Ok understood. > I don't yet know if 0.99.2 includes those changes or if it's backward > compatible with 0.99.0. > > The changes are listed here: http://ftp.acc.umu.se/pub/GNOME/sources/geocode-glib/0.99/geocode-glib-0.99.1.changes and http://ftp.acc.umu.se/pub/GNOME/sources/geocode-glib/0.99/geocode-glib-0.99.2.changes but i think the .news files are easier to read: http://ftp.acc.umu.se/pub/GNOME/sources/geocode-glib/0.99/geocode-glib-0.99.1.news http://ftp.acc.umu.se/pub/GNOME/sources/geocode-glib/0.99/geocode-glib-0.99.2.news If it's backward compatible then we can support it for Evolution 3.10, > otherwise it has to wait for Evolution 3.11/3.12. > > Matthew Barnes > > Ok thanks for the answer. Rgds Saxa --001a1135fafe9f075804e5594dd7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sun, Sep 1, 2013 at 2:07 PM, Matthew = Barnes <mbarnes@redhat.com> wrote:
On Sun, 2013-09= -01 at 13:12 -0300, Sasa Ostrouska wrote:
> Hi I was just wondering if is there a special reason to use
> geocode-glib version 0.99.0 as there is
>
> already out a 0.99.2 so would be nice to have in configure.ac
> geocode-glib >=3D 0.99.0 instead of geocode-glib =3D 0.99.0

There were substantial API changes on the master branch of geoc= ode-glib
that we don't yet support.

Ok understood.
=A0
I don't yet know if 0.99.2 includes those changes or if it's backwa= rd
compatible with 0.99.0.



If it's backward compatible then we can support it for Evolution 3.10,<= br> otherwise it has to wait for Evolution 3.11/3.12.

Matthew Barnes

Ok thanks for the answer.

=
Rgds
Saxa

=A0
--001a1135fafe9f075804e5594dd7-- From hilberg@kernelconcepts.de Thu Sep 12 11:53:11 2013 Return-Path: X-Original-To: evolution-hackers@gnome.org Delivered-To: evolution-hackers@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by restaurant.gnome.org (Postfix) with ESMTP id 37F7876D42 for ; Thu, 12 Sep 2013 11:53:11 +0000 (UTC) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.457 X-Spam-Level: X-Spam-Status: No, score=-2.457 tagged_above=-999 required=2 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.556, SPF_PASS=-0.001] autolearn=ham Received: from restaurant.gnome.org ([127.0.0.1]) by localhost (restaurant.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFfR4_25o9yC for ; Thu, 12 Sep 2013 11:53:06 +0000 (UTC) X-Greylist: delayed 2120 seconds by postgrey-1.34 at restaurant.gnome.org; Thu, 12 Sep 2013 11:53:06 UTC Received: from mail.kernelconcepts.de (mail.kernelconcepts.de [212.60.202.196]) by restaurant.gnome.org (Postfix) with ESMTP id 02A3B76A01 for ; Thu, 12 Sep 2013 11:52:55 +0000 (UTC) Received: from [192.168.2.47] (helo=falcon.localnet) by mail.kernelconcepts.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1VK4qr-0004dt-Q3 for evolution-hackers@gnome.org; Thu, 12 Sep 2013 13:14:22 +0200 From: Christian Hilberg Organization: kernel concepts To: evolution-hackers@gnome.org Date: Thu, 12 Sep 2013 13:17:25 +0200 User-Agent: KMail/1.13.7 (Linux/3.10-0.bpo.2-amd64; KDE/4.8.4; x86_64; ; ) References: <1376926398.5339.13.camel@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1431612.BFb0hDY1F9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201309121317.31320.hilberg@kernelconcepts.de> Subject: Re: [Evolution-hackers] Move IMAPX back to a module library for 3.12 X-BeenThere: evolution-hackers@gnome.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: hilberg@kernelconcepts.de List-Id: Discussion about Evolution code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 11:53:11 -0000 --nextPart1431612.BFb0hDY1F9 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Am Montag 19 August 2013, um 17:47:07 schrieb Srinivasa Ragavan: > On Mon, Aug 19, 2013 at 9:03 PM, Matthew Barnes wrot= e: > > The IMAPX classes were moved into Camel's public API to serve as base > > classes for evolution-kolab. But since Christian has parted ways with > > us it would appear the evolution-kolab project is no longer active. Sorry for being silent for so long. I was hoping to catch up on schedule with evolution-kolab again, but so far, I have not managed to do so because of being highly loaded with other projects (and evolution-kolab being a spare time project at present, with, alas, no more funding, and very low spare time anyway). As far as Kolab goes, the Kolab people have released a new major version 3, which has the XML storage format changed over the Kolab format version 2, which evolution-kolab currently supports. This would mean to implement a new storage format conversion library for evolution-kolab, which we had planned, but due to budget issues, were not able to implement. > > I'm planning a good deal of API changes to IMAPX over the next few > > months as I work toward completing IMAP NOTIFY support, and I would > > prefer these changes not be seen as breaking Camel's public API so I > > have sufficient freedom to change what needs changed. The IMAPX had been exposed so it could be subclassed and enhanced by evolution-kolab for IMAP-ANNOTATE (Kolab3 uses IMAP-METADATA). In 3.4 times, we had an IMAPX code copy within the evolution-kolab code base, which we got rid of by making IMAPX a Camel public API, so we could subclass it. > > Therefore I plan to move the IMAPX classes back to a runtime-loadable > > module library after the 3.10 release. If the evolution-kolab project > > is resurrected at some point in the future then we can renegotiate this. If by that time, upstream IMAPX can be extended with the aforementioned IMAP extensions, then no need to publicly expose IMAPX again, I guess. > > Any objections? *sigh* Honestly, I cannot really object here, since I do not know when (or even, if) I will be able to resurrect evolution-kolab. From what I can tell reading through the Kolab3 devel list posts, this version of this groupware server seems to catch on better than the previous version did, since they *finally* decided to drop the old OpenPKG distribution format alltogether with Kolab3 and started packaging for distributions. There is, also, still a great need for Kolab clients, although I have not been approa= ched in that regard after evolution-kolab went on a hiatus. > I still dont accept it under Camel. Since we are fixing it, Im fine. > -Srini. Srini, do I get you right in that you do not accept a certain IMAP implemen= tation (IMAPX in this case) being exposed by Camel? I do agree that it somewhat br= eaks the idea of Camel, that the actual IMAP implementation which gets used shou= ld be hidden. When it comes to IMAP extensions, then this concept is somewhat difficult in that it restricts what a certain IMAP implementation can expose feature-= wise, and there are some IMAP extensions (like ANNOTATION or, more recently, META= DATA), which may make sense to be implemented by, say, IMAPX, but maybe not in any= other IMAP code within Camel. evolution-kolab could always resort back to keeping around its own copy of IMAPX, although this would be a nightmare to keep up-to-date. Cheers! I hope to be around more often again in future. Christian =2D-=20 kernel concepts GmbH Tel: +49-271-771091-11 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ --nextPart1431612.BFb0hDY1F9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAlIxosYACgkQo3wgShzRDBE0FgCfTPzNQBcfRUGMV6PxAoaMYsON z7EAnjIp7eL2fxfQdXpCPfRyVgXSbpZX =WOp6 -----END PGP SIGNATURE----- --nextPart1431612.BFb0hDY1F9--