[Kolab-devel] Packaging of the Kolab web client (Horde) (was: Re: gunnar: server/patches/horde-webmail/1.2_rc1 horde-webmail-1.2_rc1_kolab_openpkg.patch, NONE, 1.1)

[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.

Usually in packaging you would try to break the functionality down  
into the different existing pieces (like the PEAR packages in the  
Horde framework + horde + kronolith + imp + ...) and ensure the  
dependencies are correct. This is much less bloat for the user and  
allows for more flexibility.

In fact I'm using the splitted approach for the other sections of the  
Kolab Server. Kolab free/busy and the Kolab mail filters will be based  
on pure PEAR packages from upstream in the next Kolab Server release.  
That is what I commited into server/pear in CVS recently. Here I feel  
the splitted approach is better as it allows us to only install a  
third of the Horde framework instead of the whole thing which is  
actually also not distributed by upstream (there is only Horde base +  
framework).

But concerning the Kolab web client I believe it will be easier if we  
can tell people that there is this one horde-webmail package and you  
can just install it on your webserver, add the Kolab specific patch  
and configure it for your Kolab server. Instead of having seven or  
eight different applications with about fifteen patches.

The patches are of course still available in their separate form as I  
generate the combined patch from the sources at  
http://hg.pardus.de/cgi-bin/hg.cgi/horde/HORDE/. You have to know a  
little bit about Mercurial queues though in order to grasp how I  
manage the patches for the different Horde branches I'm working on.

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.

Cheers,

Gunnar


>
>
> --
> Richard Bos
> We are borrowing the world of our children,
> It is not inherited from our parents.
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                         Bundesstrasse 29
Fax    : +49 721 1513 52322                        D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.