[Pkg-giraffe-discuss] imported final release of zarafa-webapp and pushed latest changes to Alioth

Guido Günther agx at sigxcpu.org
Sat Oct 10 14:24:28 UTC 2015


Hi,
On Sat, Oct 10, 2015 at 09:56:43AM +0200, Carsten Schoenert wrote:
[..snip..]
> So the question is now, should we create a simple debconf dialog there
> the administrator can easily enable the http site with a big warning or
> doing nothing on this and the administrator is doing a "a2ensite
> zarafa-webapp" by himself if wanted.

See ssl-cert package. We don't need an extra debconf question for that.

> And depending on this I'm not verry happy with the current behavior via
> postinst and postrm there the website is disabled (postrm) and reenabled
> by default (postinst) by no really needs. We can control this mainly in
> the postinst and just reload the Apache configs if needed.

In any case the postinst/postrm must honor the admins decision. So if he
disabled once we must not reenable it in the postinst ever (except
when the package got purged).

Cheers,
 -- Guido



More information about the Pkg-giraffe-discuss mailing list