pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2002-06-27	Don't bother the admin to create a directory from MAKE_DIRS if it already	jlam	1	-1/+4
	exists on the system. We still make noise about directories in MAKE_DIRS_PERMS because those directories must have special permissions that the admin should check, even if they do exist.
2002-06-27	Don't bother the admin about the ${PKG_SYSCONFBASE} and ${RCD_SCRIPTS_DIR}	jlam	1	-4/+14
	directories if they still exist after we try to remove them.
2002-06-27	Put PKG_SYSCONFBASE and PKG_SYSCONFDIR in the header so that they may be	jlam	1	-1/+4
	used in the scripts.
2002-06-24	let mk.conf's PKG_CREATE_USERGROUP and PKG_CONFIG take advantage of	lukem	1	-9/+3
	the same case insensitive multiple choice that the equivalents from the environment support
2002-06-22	Change PKG_CREATE_USERGROUP and PKG_CONFIG so that their values are merely	jlam	1	-3/+3
	defaults for the INSTALL/DEINSTALL scripts. The environment variables of the same name take precedence during installation of a binary package.
2002-06-20	In order to solve the following problems:	jlam	3	-186/+349
	(1) Admins want to create users/groups on their own (pkg/17183). (2) Admins don't want packages to setup an initial configuration. The bsd.pkg.install.mk-generated INSTALL/DEINSTALL scripts have been modified to check certain PKG_* environment variables to tune their behaviour. This works whether installing from "make install" or from a binary package. PKG_CREATE_USERGROUP indicates whether the INSTALL script should automatically add any needed users/groups to the system using useradd/groupadd. It is either YES or NO, and defaults to YES. PKG_CONFIG indicates whether the INSTALL/DEINSTALL scripts should do automatic config file and directory handling, or if it should merely inform the admin of the list of required files and directories needed to use the package. It is either YES or NO, and defaults to YES. The make(1) variable INSTALL_RCD_SCRIPTS is removed. The package rc.d script is now handled like other config files for the package, and is copied into place if PKG_CONFIG=YES. The default values above reflect the current behaviour. Setting PKG_CREATE_USERGROUP=NO solves problem (1), and setting PKG_CONFIG=NO solves problem (2). To simply matters for users installing directly from pkgsrc, these variables may also be defined in /etc/mk.conf, but behaviour at deinstall time may be surprising. It is HIGHLY recommended that these values be set in the shell environment instead.
2002-01-23	Be more pervasive with previous change.	jlam	1	-4/+7

2002-01-23	When copying config files, if the destination file already exists, then	jlam	1	-2/+3
	tell user where the example file is located. Patch provided by Stoned Elipot <seb@netbsd.org> in private e-mail.
2002-01-10	bsd.pkg.install.mk lists many things in FILES_SUBST, and we should have	jlam	1	-1/+7
	something to replace for each of those things in the header.
2001-12-04	Fix of commands invoking {USER,GROUP}ADD so that '-{u,g}' and '{user,group}id'	seb	1	-5/+5
	are two distinct shell words. Reviewed by Johnny C. Lam.
2001-11-26	Replace PKG_{USER,GROUP} with PKG_USERS and PKG_GROUPS:	jlam	3	-80/+146
	PKG_USERS represents the users to create for the package. It is a space-separated list of elements of the form user:group[:[userid][:[descr][:[home][:shell]]]] Only the user and group are required; everything else is optional, but the colons must be in the right places when specifying optional bits. Note that if the description contains spaces, then spaces should be double backslash-escaped, e.g. foo:foogrp::The\\ Foomister PKG_GROUPS represents the groups to create for the package. It is a space-separated list of elements of the form group[:groupid] Only the group is required; the groupid is optional. This solves the problem of what to do when there is more than one user or group needed for a package, e.g. qmail. Also add a bit more error-checking to the INSTALL/DEINSTALL scripts.
2001-11-26	In fit of paranoia after reading about the iTunes installer and given we	jlam	2	-82/+99
	now work on Darwin, and then the discussion about allowing spaces in user/group names, make these scripts work even if the inputs contain spaces. Yes, this is overkill, but after doing all of the work, I didn't want to waste it.
2001-11-25	Fix pasto: PKG_GROUP -> PKG_USERID.	jlam	1	-2/+2

2001-11-25	Allow ALL_{DIRS,FILES,MAKE_DIRS} to be appended to by the extra templates	jlam	2	-5/+9
	so that the general INSTALL/DEINSTALL scripts can manage these extra files and directories.
2001-11-21	Change the way the RCD_SCRIPTS variable is used. It now just lists the	jlam	3	-6/+16
	names of the scripts and is no longer a MLINKS-type variable. The scripts are copied into ${RCD_SCRIPTS_DIR} which defaults to /etc/rc.d for now. It's unclear if Linux/Solaris would set RCD_SCRIPTS_DIR to something else.
2001-11-21	Forgot an EOF in the last commit.	jlam	1	-1/+2

2001-11-20	Remind the user that some rc.conf settings may need to be removed after	jlam	1	-1/+8
	the package has been deleted.
2001-11-19	For completeness, add a SUPPORT_FILES_PERMS that acts like CONF_FILES_PERMS	jlam	3	-21/+22
	but the user isn't prompted to customize the files at post-install time.
2001-11-19	Common INSTALL/DEINSTALL scripts and Makefile magic to automatically perform	jlam	4	-0/+388
	many of the tasks that need to be done when package is installed or deinstalled: * creating user/group for the package, * creating and removing directories with special permissions and ownership, * copying config files to their final locations, and removing them at deinstall time if they don't differ from the example ones, * reminding the package admin of files he may want to customize or of files/directories he may want to remove.