[Kolab-devel] [issue61] Document reasons for OpenPGK

[Buchan Milne]

On Tue, 20 Apr 2004, Bernhard Reiter wrote:

> 
> New submission from Bernhard Reiter <bernhard at intevation.de>:
> 
> The first section of the technical document is a start, but questions remain: 
> http://www.intevation.de/cgi-bin/viewcvs-kolab.cgi/server/doc/technical/openpkg.sgml?rev=1.9&content-type=text/vnd.viewcvs-markup 
>  
> Richard Bos  email 20040419 asked: 
>  why the executables from the distribution can't be used  
>  (if these are up to date enough, as is the case with mandrake 10 and soon  
>  with suse-9.1).  Is it not possible to obtain distribution independence via a  
>  configuration file instead of the openpkg overkill?
> 

For Richard's sake, it may be of interest to note that absolutely no 
3rd-party packages are required for deploying Kolab on Mandrake 10.0. The 
kolab-server package is available in "main" of Mandrake 10.0 (but, for 
marketing reasons it was left off the download ISOs, so it must be 
installed from the FTP mirrors on systems installed using the download 
ISOs), and works out-the-box, with GUI setup tools (ie replaces running 
the command-line bootstrap script).

For instance, this will get you a fully functional Kolab setup on Mandrake 
10.0:
# urpmi kolab-server
# kolab_bootstrap
(or use drakwizard instead if you have it installed).

The document claims:
"Unfortunately the major operating system distributions provide the 
needed server software in different and mostly elder releases - for rather 
good and understandable reasons. "
which is not entirely accurate (maybe the use of "many" or "some" is in 
order), all currently-supported versions of Mandrake Linux have new enough 
packages for kolab (unless OpenPKGs use of Openldap-2.2.5 implies that 
Kolab will need openldap-2.2.x in the near future).

Regards,
Buchan