[Kolab-devel] kolab2 dependencies/integration
corey_s at qwest.net
Tue Jun 21 21:03:48 CEST 2005
How much of the Kolab2 distribution/package consists of actual sourcecode
patches to the various existing components ( openldap, cyrus, postfix, etc )
it uses, and how much of the distribution/package is simply configuration
files, installation scripts, and whatnot?
Is the Kolab project bound and determined to keep it's source packages as
openpkg only? There really should be a way for distributions/platforms to
provide their own native packages for Kolab, for better/natural integration
with existing software/services.
So, although openpkg works, as you say - "to provide a supportable base on a
wide variety of platforms" - it _also_ works to "provide a completely foreign
step-child sort of integration on every platform that it's installed onto".
How difficult would it be, now that Kolab2 has been released, to extract only
the Kolab specific changes/patches ( if any ), and provide a non-openpkg
distribution? OpenXchange does this to good effect, I don't see why Kolab do
the same. Of course installation and configuration of Kolab without using
the openpkg tools may be difficult, but it really should be an option.
More information about the Kolab-devel