* Fabio Massimo Di Nitto (email@example.com) [040418 20:25]:
> The main problems are:
> 1) Packages changing user configuration files in a dangerous manner
> (RC bugs)
When do you consider that they do it in a dangerous manner? Is grep
dangerous? Is echo foo >> dangerous?
> Two important notes:
> a) The way in which packages use modules-config/apache-modconf.
> Most maintainers used our examples for postinst/prerm. We have
> now fixed some problems in the prerm phase, and therefore suggest that
> maintainers should check their scripts against the new examples we provide
> in README.modules, which ensures that apache-modconf exists before
> attempting to use it.
Well, I dislike this way. Reason is that user configuration could be
lost on remove in this way. (Example: User installs mod foo; foo is
enabled. Then user decides to disable foo by hand or not. Then user
removes, but not purges foo; here foo is disabled by script. After
a new install, the install enables foo again. So, the previous disable
So, if you change the script, then it would be good if you could
seperate interfaces, and provide a "install", "remove" and "purge"
interface for the maintainer script, that do the appropriate actions,
and not fiddle with users decisions (except on purge, where everything
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
- From: Fabio Massimo Di Nitto <firstname.lastname@example.org>