cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml

[Joseph Scott]

On Mon, 23 Feb 2004, Kris Kennaway wrote:

-> On Tue, Feb 24, 2004 at 12:41:11AM +0100, Thomas-Martin Seck wrote:
->
-> > > > btw: Is implementing something like WANT_UID/WANT_USER in bsd.port.mk
-> > > > something worth pursuing? There are a lot of hand-made solutions of
-> > > > varying quality in the ports system for this problem now.
-> > >
-> > > What would that do?
-> >
-> > It should create a pseudo-user with name=WANT_USER with uid=WANT_UID in
-> > a unified way to reduce the chance of a maintainer doing something silly
-> > in Makefile or pkg-install when hand-rolling this. The problem I see
-> > with this proposal is that this is hard to implement this with make(1)
-> > since ideally this should be something like 'makeuser(username, uid,
-> > gid, homedir[, loginshell if we want to make this customizable])'. An
-> > added bonus would be that the user/uid demand is clearly visible in the
-> > Makefile (if that is of any value).
-> >
-> > If implementing this in bsd.port.mk is not feasible, we should have at
-> > least a known working reference for cut-and-pasting in the porters
-> > handbook since there are at least three different implementations for
-> > the problem of creating a user/group on the fly in the ports tree.
->
-> I don't think it's feasible to do this in bsd.port.mk, because the
-> user and group need to also be created at pkg_install time, using an
-> appropriate shell script.
->
-> Your suggestion of providing a standard template for doing this (in
-> the porter's handbook?) is a good one though.

	I think that mail/mailman does something along the lines of what
you are looking for.  It would be nice have a generic 'template' of this
to use for new ports.

--
Joseph Scott
http://www.randomnetworks.com/joseph/blog/contact.php