[Kolab-devel] Kolab with CentOS/ClarkConnect

[Richard Bos]

Hello Peter!

Op woensdag 29 maart 2006 18:44, schreef Peter Baldwin:
> Hello Kolab Developers!
>
> Quick introduction: I'm the project leader for the ClarkConnect Linux
> distribution.  It's an open source business server software package
> designed for 5 to 200-ish users (gory details are here:
> http://www.clarkconnect.com/).  

clarkconnect is a fine distribution indeed.  I have it running as a firewall 
and it does it job well :)

> We're in the process of integrating Kolab 
> into the ClarkConnect solution and we're at the stage where we can start
> contributing patches (we have to keep up with Gunnar!).  

That is a nice extenstion to clark connect!

> We'll have at 
> least one, and maybe two developers available to work on Kolab.
>
> The core ClarkConnect packages are based on CentOS 4.x, so we'll have 95%
> of the CentOS/Red Hat dist_conf sanity checked.  

If you like I can commit the dist_conf file to cvs.  What would be the name 
for the dist_conf file redhat, centos, perhaps fedora?  Or is the latter not 
similar to redhat anymore?

> We'll also have the 
> following RPMs and source RPMs completed for any interested CentOS/Red Hat
> users:
>
> 1) all of the required perl-XYZ packages (e.g. perl-Mail-IMAPClient)
> 2) patched versions of cyrus-imapd and postfix
> 3) a "sandboxed" Apache/PHP/Pear/PECL build
> 4) a "sandboxed" MySQL build (for Horde testing)

What do you mean with a sandboxed apache and mysql?  Does that mean that there 
will be 2 mysql's running, 1 regular and another one for horde testing?  Is 
that using another port than?

> 5) Dspam (as a delivery agent)
> 5) miscellaneous and fairly minor patches that will hopefully make their
> way into Kolab
>
> My question boils down to this -- should we be in a "code freeze" kind of
> mode, or still in a "take your time to fix it right" mode.  Here's a good
> example of what I'm trying to get at (and mentioned in Gunnar's earlier
> e-mail): issue #1176 https://intevation.de/roundup/kolab/issue1176 has a
> quick, dirty, and fairly safe solution (a 3-line patch and an extra PHP
> file).  The "take your time to fix it right" would be to add the required
> PHP 5 code.

I would say it depends on which php version you include.  Is it php4 or 5?  
Kolab on non-openpkg distributions with php4 is I think save till the point 
of just regular email delivery, sending (including spam and virus scanning).  
I'm able to succesfully schedule meetings and have those events sent to 
participants.

I'm not able to use the freebusy.php and pfb.php urls, like:
https://<fqdn>/kolab/freebusy/pfb.php or 
https://<fqdn>/kolab/freebusy/pfb.php?uid=test%40radoeka.nl
https://<fqdn>/kolab/freebusy/freebusy.php

Don't know what is wrong there, might be urls (I assume) and the scripts might 
not be configured correctly at the moment (on suse)....

Difficult question, code freeze or not....  Most the times it are just little 
changes that are made....  unlike today that saw a lot of big changes....
Further more the current kolab version, is somewhere in beta mode....  It is 
not released yet....  I can't answer the question :( sorry.

-- 
Richard Bos
Without a home the journey is endless