[Kolab-devel] Re: steffen: server/kolab-resource-handlers/kolab-resource-handlers/fbview/fbview/framework/Net_IMAP IMAP.php, NONE, 1.1 IMAPProtocol.php, NONE, 1.1 package.xml, NONE, 1.1

Stuart K. Bingë omicron-list at mighty.co.za
Tue Sep 21 17:30:16 CEST 2004


Hi Steffen,

On Tuesday, 21 September 2004 16:33, cvs at intevation.de wrote:
> Author: steffen
>
> Update of
> /kolabrepository/server/kolab-resource-handlers/kolab-resource-handlers/fbv
>iew/fbview/framework/Net_IMAP In directory doto:/tmp/cvs-serv20540/Net_IMAP
>
> Added Files:
>  IMAP.php IMAPProtocol.php package.xml
> Log Message:
> imported Net_IMAP
>
> [...]

Is this really necessary? Wouldn't it make more sense to just pull in the 
tarball from PEAR in the kolab-resource-handlers RPM spec?

The problem I have with this is that the webclient also depends on Net_IMAP, 
and I can see it's going to get messy when trying to install the webclient 
through an RPM if a copy of Net_IMAP is already installed.

I've already uncovered some bugs in Net_IMAP that need fixing for the 
webclient to function correctly (they don't affect the resmgr code) and now 
we're going to have to fix these bugs in two separate places. Either that, or 
we'll need to maintain two separate copies of Net_IMAP under the /kolab 
hierarchy; one for the resmgr and one for the webclient.

To me it just seems to be a very messy solution to include it here :-/

-- 
Stuart K. Bingë
Code Fusion cc.

Office: +27 11 673 0411
Mobile: +27 83 298 9727
Email: s.binge at codefusion.co.za

Tailored email solutions; Kolab specialists.
http://www.codefusion.co.za/




More information about the devel mailing list