Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49176 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88653 invoked from network); 29 Jul 2010 21:44:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jul 2010 21:44:56 -0000 X-Host-Fingerprint: 128.59.13.186 dhcp-13-186.cs.columbia.edu Received: from [128.59.13.186] ([128.59.13.186:7967] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E8/D3-03376-756F15C4 for ; Thu, 29 Jul 2010 17:44:55 -0400 Message-ID: To: internals@lists.php.net Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 29 Jul 2010 17:44:58 -0400 Content-Transfer-Encoding: 7Bit References: <1A7DEEA5-A4AA-40F5-A2E5-BD8AB8FD398A@ubuntu.com> Followup-To: php.internals Lines: 29 MIME-Version: 1.0 X-Posted-By: 128.59.13.186 Subject: Re: [PHP-DEV] IMAP patches from kolab -- can we get these merged? From: geissert@php.net (Raphael Geissert) Mikko Koppanen wrote: > I was looking at annotations patch and it seems that my c-client does > not support the functionality (2007b on Debian Lenny). Do the > annotations require a custom patch to c-client as well? The request to include the annotations patch at Debian is at: http://bugs.debian.org/456947 But as you can see, it is marked as blocked by http://bugs.debian.org/456591 (the request against uw-imap/libc-client to include the patch.) Therefore, the blocker at the php level is enabling the annotations code at configure time if the system supports it. Of course, support on libc-client is necessary for it to be of any use. I just talked to Jonas Smedegaard (the Debian maintainer of libc-client,) and apparently the reason for not merging it is that the code is dead upstream and unmaintainable. A dead end. While digging for alternatives, it appears that there was a discussion in 2004 for FC2 about the situation of libc-client, but besides that: nothing. As it seems, the best and maintainable solution is to switch to some other alternative library (sadly, there's no such candidate atm.) HTH -- Raphael Geissert