[Kolab-devel] Moving Kolab to the current Horde version
suse-tux at gmx.de
Thu Jan 11 17:59:40 CET 2007
On 2007-01-11 17:05:19 +0100, Gunnar Wrobel wrote:
> Marcus Hüwe <suse-tux at gmx.de> writes:
> >> So I think I could either create a new branch within kolab-cvs or I
> >> create two new experimental packages horde-framework and horde-fbview
> >> (or horde-kronolith) and modify my patches for the
> >> kolab-resource-handlers and kolab-webadmin so that they will work with
> >> both the new and the old horde code base.
> > I would vote for a new branch because then we can be sure that the new patches
> > won't harm anything in the current main branch. After the release of 2.1 the
> > changes can be moved to normal kolab tree. That's the easiest solution IMHO.
> > Btw. are these patches already available?:)
> Sure, I am constantly sending patches to Horde and most of them got
> integrated. The biggest part, the new Share driver for Kolab, has been
> integrated two weeks ago. This switch created a few new, but minor
> bugs and I am currently going through them and fixing them. So far
> mnemo, nag and kronolith seem to work fine. Some problems with turba
> and free/busy still exist.
> But I believe it is definitely ready for testing. So if you are using
> Horde CVS, just update and select the kolab share driver - and throw
> your mysql db away ;).
That sounds great! I'll have a look at the horde cvs stuff. Installing horde
from cvs isn't as simple as installing a normal horde release iirc (at least it
was a bit difficult when i tried it some time ago).
More information about the devel