[Kolab-devel] What about squirrelmail standard in 2.2 ?

[Thomas Arendsen Hein]

* Alain Spineux <aspineux at gmail.com> [20070615 19:49]:
> # /kolab/bin/openpkg rpm --rebuild --nodeps /s0/linux/openpkg/squirrelmail-
> 1.4.9a-20070315.src.rpm --define "with_plugins no"
> # /kolab/bin/openpkg rpm -Uvh /kolab/RPM/PKG/squirrelmail-
> 1.4.9a-20070315.ix86-fedora6-kolab.rpm
> 
> === Squirrelmail configuration ===
> {{{
> # cd /kolab/share/squirrelmail
> # ln -sf ../../etc/squirrelmail/config_local.php config_local.php
> # cat /kolab/etc/squirrelmail/config_local.php
>...
> 
> == Apache integration ==
> # grep Include /kolab/etc/kolab/templates/httpd.conf.template
> Include "/kolab/etc/apache/apache.d/*.conf"

My dream would be:

apache2's config would not be changed by Kolab, but the
kolab/templates file would create
/kolab/etc/apache2/apache2.d/kolab.conf (or something like that)

For squirrelmail integration there would be a "kolab-squirrelmail"
package which depends on squirrelmail (and
"squirrelmail::with_plugins = no" if that is needed) and provides
a kolab/templates files for the configuration for squirrelmail and
for /kolab/etc/apache2/apache2.d/squirrelmail.conf

There could be a "kolab-horde" package which does similar things for
horde.

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner