Hi,
On Samstag, 19. Mai 2012, Bertrand Marc wrote:
> Thank you very much for uploading the GNUnet stack to unstable. Are you
> willing to sponsor these uploads on regular bases ?
we'll see :)
> I have to say I hesitated about using dpkg-statoverride. In my first
> uploaded to mentors, chmod and chown were used in postinst, but one of
> the reviews mentionned dpkg-statoverride. I looked a bit into it and I
> found this usage in the Debian policy (10.9.1) [1]. It seems to me
> gnunet falls into the case of dynamically allocated user or group ids,
> where dpkg-statoverride can be helpful.
also with dynamically allocated user or group ids you can use chown :)
> The main benefit would be the ability for a sysadmin to override the
> gnunet permissions easily.
this is also given when you use chown only on the first install of the
package.
> Could you explain me why you reverted this
> use of dpkg-statoverride in munin ?
because it's useless and it makes the list of "dpkg-statoverride --list"
longer.
as I see it, dpkg-statoverride is for users to overwrite the package. Not for
the package, eh, overriding itself ;)
cheers,
Holger
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
