diff options
author | jlam <jlam@pkgsrc.org> | 2002-06-20 20:15:46 +0000 |
---|---|---|
committer | jlam <jlam@pkgsrc.org> | 2002-06-20 20:15:46 +0000 |
commit | f28a0a731b72309c8ff27be7b00234137436dac9 (patch) | |
tree | 15d25b0a8c8441b4d22c4a75ae86412dc8954ee3 /Packages.txt | |
parent | 8f6dfa65701404f02621a8ea92417701c1b655a7 (diff) | |
download | pkgsrc-f28a0a731b72309c8ff27be7b00234137436dac9.tar.gz |
In order to solve the following problems:
(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.
Diffstat (limited to 'Packages.txt')
-rw-r--r-- | Packages.txt | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/Packages.txt b/Packages.txt index 978aba4d55c..2c5554f298c 100644 --- a/Packages.txt +++ b/Packages.txt @@ -1,4 +1,4 @@ -# $NetBSD: Packages.txt,v 1.250 2002/06/18 16:14:54 agc Exp $ +# $NetBSD: Packages.txt,v 1.251 2002/06/20 20:15:46 jlam Exp $ ########################################################################### ========================== @@ -2223,7 +2223,9 @@ By default, a new user will have home directory /nonexistent, and login shell The package Makefile must also include "../../mk/bsd.pkg.install.mk" prior to the inclusion of bsd.pkg.mk. This will cause the users and groups to be created at pre-install time, and the admin will be prompted to remove them at -post-deinstall time. +post-deinstall time. Automatic creation of the users and groups can be +toggled on and off by setting the environment variable PKG_CREATE_USERGROUP +prior to package installation. 10.23 How to handle compiler bugs @@ -2363,8 +2365,12 @@ them into PKG_SYSCONFDIR. The contents of this variable is formed by pairs of filenames; the first element of the pair specifies the file inside the examples directory (registered by PLIST) and the second element specifies the target file. This is done this way to allow binary packages to place -files in the right directory (using INSTALL/DEINSTALL scripts which are -created automatically). +files in the right directory using INSTALL/DEINSTALL scripts which are +created automatically. The package Makefile must also include +"../../mk/bsd.pkg.install.mk" prior to the inclusion of bsd.pkg.mk to use +these automatically generated scripts. The automatic copying of config +files can be toggled by setting the environment variable PKG_CONFIG prior +to package installation. Here is an example, taken from mail/mutt/Makefile: |