Bug#568313: Suggestion: forbid the use of dpkg-statoverride in postinst scripts, except for --list
martin f krafft <firstname.lastname@example.org> writes:
> I tend to agree. With that in mind, though, why would one ever want/need
> to chmod/chown files under control by dpkg (which are the only ones for
> which dpkg-statoverride applies to) *from postinst*? I can perfectly
> understand admins wanting to override package defaults, but not why the
> package maintainer needs to use dpkg-statoverride.
It's for setting the ownership of files to dynamically allocated UIDs or
GIDs which are created in the postinst script. Since you don't know what
UID or GID they'll have, and since they don't exist during the package
unpack phase, there's no way to express that ownership in the *.deb file.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>