[Federico 'Derfel' Stella] > In all my machine /usr is mounter read-only and remounted read-write by > Dpkg::Pre-Invoke in apt.conf. I use this kind of conf by years and I expect > a package to not touch /usr during re-configuration.
Well, dpkg-reconfigure runs the config and postinst scripts, if present, for any package. My system has 55 postinst scripts that call 'install-info', not to mention 66 postinst scripts that call 'update-alternatives' (which might well need write access to /usr). There could be several other reasons a read-only /usr might break that I haven't thought of. So on my system there are 106 packages that potentially have this behavior. Nobody special-cases dpkg-reconfigure. Thus it's clear to me that nobody expects dpkg-reconfigure to avoid touching the /usr filesystem. Feel free to take this to debian-devel, though, if you still disagree. I'm a reasonable person and I'll be happy to fix gpm if other people agree that this goal is worthwhile. Peter
signature.asc
Description: Digital signature
