Date: Mon, 23 Feb 2004 16:51:16 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Thomas-Martin Seck <tmseck-lists@netcologne.de> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml Message-ID: <20040224005115.GA35980@xor.obsecurity.org> In-Reply-To: <20040223234111.GD1605@laurel.tmseck.homedns.org> References: <20040223214202.GA29948@xor.obsecurity.org> <20040223222705.1873.qmail@laurel.tmseck.homedns.org> <20040223223508.GB31276@xor.obsecurity.org> <20040223234111.GD1605@laurel.tmseck.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. > >=20 > > What would that do? >=20 > It should create a pseudo-user with name=3DWANT_USER with uid=3DWANT_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). >=20 > 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. Kris --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAOqADWry0BWjoQKURAhIhAKD8qRvYECj569n1peTnIpCM4xSEoQCgsBns b6ILuxRsRnNmgCHWYuwfY3A= =Xff/ -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040224005115.GA35980>