[Kolab-devel] Packaging of the Kolab web client (Horde)

[Richard Bos]

Op Tuesday 16 September 2008 05:29:53 schreef Gunnar Wrobel:
> Quoting Richard Bos <ml at radoeka.nl>:
> > Hi Gunnar,
> >
> > Op Monday 15 September 2008 20:58:01 schreef cvs at kolab.org:
> >> Added Files:
> >>         horde-webmail-1.2_rc1_kolab_openpkg.patch
> >> Log Message:
> >> Added the patch for the new webmail release candidate. Horde was quick
> >> this time and we now have the release available that will be the basis
> >> for the next few Kolab server years. All native ports are encouraged to
> >> switch to horde-webmail-1.2.* as soon as possible.
> >
> > Instead of all the seperate modules do you mean?
>
> Yes.
>
> > What is the advantage, less packaging?
>
> Yes that is one part.
>
> In addition the patch handling is way easier. One Kolab specific patch
> for Horde and that's it.
>
> This is strongly against my personal Gentoo nature :) but I believe it
> is a significantly easier approach for all parties involved.

Sounds good indeed.  I had a look at the patch, and there are some changes 
that you make against the horde lib/core/app code.  Are these changes 
provided upstream, or are they really kolab specific?  I'm not talking about 
the $conf[''] changes, but e.g. the lines between:
if ($GLOBALS['conf']['kolab']['enabled']) {
}
and the changes to Horde/iCalendar.php or lib/SyncML/Backend.php, etc.


[............]

> I made this comment a little bit more elaborate as I would like to see
> the native ports to switch over to horde-webmail so that we have a
> common base. The Gentoo users already have the kolabified
> horde-webmail available in the main distribution, Univention switched
> also, and OpenPKG will have it in the next release.

Having to apply one patch is convincing enough ;)

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.