pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2001-12-26	Include bsd.prefs.mk so that INSTALL_RCD_SCRIPTS may be defined before the	jlam	1	-1/+3
	relevant code in this file.
2001-12-19	D'oh! I had the logic reversed for the INSTALL_RCD_SCRIPTS check.	jlam	1	-3/+3

2001-12-19	Do previous without breaking package Makefiles that use RCD_SCRIPTS and	jlam	1	-5/+6
	expect it to contain the list of example rc.d scripts.
2001-12-18	By default, don't install the rc.d scripts into /etc/rc.d. Despite the	jlam	1	-1/+7
	fact that they don't do anything unless the appropriate variables are set in rc.conf, people really dislike the warning emitted at startup. For users that do want the pkg_* tools to handle automatically copying and removing the rc.d scripts, the mk.conf variable to set is INSTALL_RCD_SCRIPTS=YES.
2001-12-13	Substitute for GREP as well.	jlam	1	-1/+2

2001-12-10	Substitute for HEAD and GTAR.	jlam	1	-1/+3

2001-12-09	Subst. for PERL5 in INSTALL files.	jlam	1	-1/+2

2001-12-02	Support automatically calling the INSTALL script during installation. This	jlam	1	-3/+7
	currently only occurs for packages that use bsd.pkg.install.mk. There are two new targets, pre-install-script and post-install-script, that default to doing nothing. The order of targets called for a "make install" is: pre-install-script pre-install do-install post-install post-install-script The new targets are defined in bsd.pkg.install.mk to call the INSTALL script with the PRE-INSTALL and POST-INSTALL options.
2001-11-26	Replace PKG_{USER,GROUP} with PKG_USERS and PKG_GROUPS:	jlam	1	-33/+31
	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-25	PKG_SYSCONFDIR is where the configuration files for a package may be found.	jlam	1	-5/+5
	This value may be customized in various ways: PKG_SYSCONFBASE is the main config directory under which all package configuration files are to be found. PKG_SYSCONFSUBDIR is the subdirectory of PKG_SYSCONFBASE under which the configuration files for a particular package may be found. PKG_SYSCONFDIR.${PKGBASE} overrides the value of ${PKG_SYSCONFDIR} for a particular package. Users will typically want to set PKG_SYSCONFBASE to /etc, or accept the default location of ${PREFIX}/etc. This obsoletes the use of CONFDIR, which was active for only 6 days, so no need to have a workaround to still accept old CONFDIR settings.
2001-11-23	Add SU to FILES_SUBST	abs	1	-1/+2

2001-11-21	Refer to /etc/rc.d as ${RCD_SCRIPTS_DIR} more thoroughly.	jlam	1	-3/+3

2001-11-21	Change the way the RCD_SCRIPTS variable is used. It now just lists the	jlam	1	-3/+6
	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-19	For completeness, add a SUPPORT_FILES_PERMS that acts like CONF_FILES_PERMS	jlam	1	-3/+7
	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	1	-0/+189
	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.