[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bits from the Apache Maintainers / Upcoming apache2 2.4 transition



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Vincent,

On 23.03.2012 10:22, Vincent Danjean wrote:
> just looking at the wiki, I see: ==== Likewise, in postrm do upon
> purge: if [ -e /usr/share/apache2/apache2-maintscript-helper ] ;
> then /usr/share/apache2/apache2-maintscript-helper apache2_invoke
> disconf yourapplication.conf fi ==== Should not this be done on
> remove (and not purge)? Usually, when a webapp package is removed,
> its configuration should be desactivated, no?

sorry our answer took so long, but we needed to discuss questions like
this. We came up with this proposal:

If the web application can be run with a feasible out-of-box
configuration call apache2_invoke enconf unconditionally on every
"postinst configure" run.

Likewise, the configuration should be disabled on any removal (and
purge anyway), because important files may be missing (and that's the
point of package removal, anyway). Thus, you need to call
"apache2_invoke disconf" on both on removal and on purge.


In future apache2_invoke will remember stuff it removed during removal
and will reenable it during reinstall (i.e. in contrast to web
application configurations disabled by the site administrator).


n.b. the behavior on the /usr/share/apache2/apache2-maintscript-helper
 edge is not fully functional yet. This will be changed soon.



- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPbvjVAAoJEMcrUe6dgPNtR6wQAMD7qS13nQKAcdQJKVqQ+M82
+GKq+M4HOlHJkBLL41+FuCxyKAATEmJcumBwsU2PM2WTcm5x5T3B+1Ygv+aTC1zo
8kMg5jaBhNX2vuHYnA5tDBz0HjyP900aFuUM/qq0Af083oPusyXXGygOdT6rJr5r
c1HP84uyEss2jExFe3/uMsL1t7kw7TEwo9d2d0BKm/FgAsks4NQwRMava0FjNv4Z
zb54Qr05d6OO7Ywvj6V2jeR0AnnUFpXbuhXM5ua4Yqqaeg7nJ9p7mohaXB9hH52g
ff5JHjrwUOw4FUGcbae0vBVDY49eqJoCph0SlAbPLQb0BEEAppTOU9jzukeHnM0D
h+ycVNLlsHuo61TitDtxN0ksBPa/08TEuY5Ql7lHFudQv3OFDSzCQj7AY/R2d2ev
xmZeQbEBaZeeZ3DWj9w8syxDrh4PQhyb5QYjDEhKylK9e6leJZnBmeO3EF2CZr4c
n7K5A+fHJXofPCln51T1s6EU09ybnqCwrfcykWNQ0tZ+jf4EEorHgxgcKgdLkfoB
2vSEaJrCoiyjr9IbjrX6JAPw+RAfYFKlMorTad2dzj8/APZbSVQ4XTPLet0CZjYv
K6kAjzizskect9kMDkYFdCqazUQLpg/7E6jmmjyV8lGySGbWIdjUBr8jPLnqdeZ+
d/ysjA8UlxaN+u+0NRaa
=UFFM
-----END PGP SIGNATURE-----


Reply to: