Why OpenPKG

[Richard Bos]

Op woensdag 21 april 2004 10:09, schreef Bernhard Reiter:
> > This is my first email to this list and let me start with saying that
> > it's hard to imagine how much knowledge is needed of all the
> > applications, that make up kolab, to get them integrated and working
> > toghether nicely.  And this includes of course openpkg, I have read the
> > document that Bernhard refers to above (even in paper format) several
> > times but the questions remain :(
>
> I have created an issue in our tracker so that we do not forget to explain
> the reasons better.

If you include the information that you provided below, it will shut up a lot 
of people :)  I can very much agree with your explanation below!

> > I have the question, 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?
>
> In principle every distributor can integrate the configuration files
> and the kolab-engine and web-admin interface to gain a Kolab compatible
> server. For the project this was not the best path because of the target
> group and the quality assurance.
>
> Anyone setting up a serious groupware server for a larger company
> or institution will dedicate a whole server machine to it.
> Also the platform decision will be already made.
> The design of Kolab1 was geared towards this.
> With OpenPGK you can supported Kolab controlled in several deployments
> running on top of different operating systems.
>
> A second point is the quality control. To get the system stable in a set
> time we expected to control every little detail about the used components.
> This means every configuration option, place in the directory and linked
> libraries and compiler versions. OpenPGK made that feasable.

-- 
Richard Bos
Without a home the journey is endless