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

[Thomas Arendsen Hein]

* Alain Spineux <aspineux at gmail.com> [20070616 11:00]:
> On 6/16/07, Thomas Arendsen Hein <thomas at intevation.de> wrote:
> >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)
> 
> 
> Are you expecting apache2 for next kolab ?

It already is, see the thread
"Kolab Server 2.2-beta1 based on OpenPKG-CURRENT"
on this list

> But if ".... kolab dont change the config ...." then you mean
> apache1 would still be there ?

No, OpenPKG-CURRENT's apache2 already includes apache2.d/*.conf, so
kolab could just place its specific bits there.

> 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
> 
> I'm just in "making package" this afternoon. Do you have a skeleton for
> openpkg package to customize.

Look in CVS, e.g. at the 'server/file' or 'server/clamav' directory.

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