From owner-cvs-all@FreeBSD.ORG Mon Feb 23 16:51:18 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1460F16A4CE for ; Mon, 23 Feb 2004 16:51:18 -0800 (PST) Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6DD043D1D for ; Mon, 23 Feb 2004 16:51:17 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (a4191dba2c7a0119418a9dda0e9cf671@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203])i1O0pGQ0029247; Mon, 23 Feb 2004 16:51:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2546B66CAF; Mon, 23 Feb 2004 16:51:16 -0800 (PST) Date: Mon, 23 Feb 2004 16:51:16 -0800 From: Kris Kennaway To: Thomas-Martin Seck Message-ID: <20040224005115.GA35980@xor.obsecurity.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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <20040223234111.GD1605@laurel.tmseck.homedns.org> User-Agent: Mutt/1.4.1i cc: cvs-all@freebsd.org cc: Kris Kennaway Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 00:51:18 -0000 --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--