It's just not going two work out every time, both the user and the upgrade program both trying to maintain wwwoffle.conf.
Proposal: most of the changes the upgrade makes are to the documentation. This should all be done to the wwwoffle.conf manpage, and the documentation can now be removed from wwwoffle.conf. Indeed, at least in the Debian model, I believe configuration files are not to be changed behind one's back. We are to be asked if we want to see a diff and whether to accept it or not. Some users create their wwwoffle.conf from scripts, so changes anybody else makes to it will get overwritten, dangnabbit. It would be best to convey anything important that needs to be done to wwwoffle.conf via other means: messages upon upgrade that require a RET to continue, email to root, README.upgrade, etc. Indeed, there should be no wwwoffle.conf supplied at all. Defaults are defaults, the rest is the exclusive domain of the user. Models and examples all should be on the man page, or a wwwoffle.conf.sample. Hmmm, for now on Debian perhaps I will do $ perl myscript /usr/share/wwwoffle/default/wwwoffle.conf>wwwoffle.conf after each upgrade.
