>Number:         17183
>Category:       pkg
>Synopsis:       need control over how pkgsrc creates users & groups
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 06 17:22:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Luke Mewburn
>Release:        NetBSD 1.6_BETA1
>Organization:
Luke Mewburn  <lukem@wasabisystems.com>  http://www.wasabisystems.com
Luke Mewburn     <lukem@netbsd.org>      http://www.netbsd.org
Wasabi Systems - NetBSD hackers for hire
NetBSD - the world's most portable UNIX-like operating system
>Environment:
System: NetBSD argo.mewburn.net 1.6_BETA1 NetBSD 1.6_BETA1 (ARGO from GENERIC-$Revision: 1.491 $) #0: Thu May 23 23:22:19 EST 2002 lukem@argo.mewburn.net:/var/scratch/obj.i386/usr/src/sys/arch/i386/compile/ARGO i386
Architecture: i386
Machine: i386
>Description:
	It would be nice if (IWBNI) pkgsrc had an mk.conf variable
	to control whether required users or groups are created by
	the package install mechanism (from mk/install/install ?),
	or just checked for the existence and barf if they're missing.

	Some of us run systems where it's not appropriate to
	add new users or groups to the local system databases, or at
	least, not without manual intervention.

>How-To-Repeat:
	Install a package on a (client) machine.  Notice that it's
	polluted your passed(5) database with a new user, which will get
	lost the next time the database is built from your master
	repository.

>Fix:
	Add an mk.conf variable.  Johnny Lam suggests PREEXIST_USERGROUP
	(and then goes on say, "Of course, a better variable name
	would be good to have in the PR" :-)
>Release-Note:
>Audit-Trail:
>Unformatted: