[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Best practices on system users and groups

On Tue, Nov 01, 2005 at 11:14:59AM +0200, Lars Wirzenius wrote:
> Also, sticking all the tens of lines of boilerplate code into the
> postinst of every package that needs a system user is a good way to
> invite trouble. When the boilerplate has a bug (possibly because things
> change in the future), it will have to be fixed in dozes on of packages.
> It's oh so much more sensible to create a tool that postinsts can call:
> if boilerplate code is good enough, then it can easily be abstracted
> away.

I'm aware of that, but currently there's lot of packages that do it wrong in
any case, so having some boilerplate script they can be pointed to is
something good. Obviously, it would be best if this was provided as shell
functions that could be sourced by package's maintainer scripts. But that's
the second step, first lets document it properly, then implement it, and then
remove the code from the document and point to the implementation.



Attachment: signature.asc
Description: Digital signature

Reply to: