Hi Marc,

On 8/10/26 07:23, Marc Haber wrote:
Normally, we could just mark dokuwiki.php not being a conffile (all files in /etc automatically have the status of a conffile, unless dpkg is told otherwise; any other file outside of /etc is not a conffile by default). However, that would mean, that any local modifications are automatically discarded on upgrade, i.e. users loose their settings.

I think that would be a policy violation and also a bad example.

as I said later on, there's no point in making it a non-conffile, however, jftr being policy compliant is not a problem here. the usual way to do this is to move it to /usr/share and symlink it to /etc/.

How strong is the wording pointing people to local.php inside dokuwiki.php? Maybe that could be improved.

it's discouraged, but most howtos on the internet don't mention local.php and tell users to modify dokuwiki.php, so, this is a long shot anyway.

 * add a check in postinst so that after the package is installed
   (i.e. after the user has chosen to keep the old dokuwiki.php)
   we show a debconf warning message if the syntax option is missing
   and that that needs to be added, and advise the user to use
   local.php for modifications instead of dokuwiki.php.

Please don't.

I beg to differ. first, this is the first time in almost two decades where dokuwiki needs a certain option to be in dokuwiki.php and fails otherwise. second, a simple *single* check for that is fine (and I would drop it right after forky anyway).

third, I think this is a nice service to dokuwiki users, who often are not so admin-proficiant and, I think, will appreciate the helpful pointer.

That's going to explode in the face of all package maintainers wo will spend weeks of their lifetime writing manual checks for each and every incompatible change in packages during upgrades.

what has *one* check in *one* package (= dokuwiki) got to do with any other package or maintainer?

A package cannot ever touch a dpkg conffile in maintainer scripts.

again, not applicable here, however jftr, there are multiple policy-compliant ways to do that, e.g. ucf just to name one.

Regards,
Daniel

Reply via email to