From a0f57683adfe8dba39b9fea4177e566f3a48b24f Mon Sep 17 00:00:00 2001 From: Warren Block Date: Sun, 9 Feb 2014 03:37:57 +0000 Subject: [PATCH] Whitespace-only fixes, translators please ignore. --- .../porters-handbook/pkg-files/chapter.xml | 331 +++++++++--------- 1 file changed, 163 insertions(+), 168 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/pkg-files/chapter.xml b/en_US.ISO8859-1/books/porters-handbook/pkg-files/chapter.xml index 18912f558c..70a2a7e0c2 100644 --- a/en_US.ISO8859-1/books/porters-handbook/pkg-files/chapter.xml +++ b/en_US.ISO8859-1/books/porters-handbook/pkg-files/chapter.xml @@ -5,211 +5,206 @@ $FreeBSD$ --> - + - The <filename>pkg-*</filename> - Files + The <filename>pkg-*</filename> Files - There are some tricks we have not mentioned yet about the - pkg-* files - that come in handy sometimes. + There are some tricks we have not mentioned yet about the + pkg-* files that come in handy + sometimes. - - <filename>pkg-message</filename> + + <filename>pkg-message</filename> - If you need to display a message to the installer, you may - place the message in pkg-message. This - capability is often useful to display additional installation - steps to be taken after a pkg install or to - display licensing information. + If you need to display a message to the installer, you may + place the message in pkg-message. This + capability is often useful to display additional installation + steps to be taken after a pkg install or to + display licensing information. - When some lines about the build-time knobs or warnings - have to be displayed, use ECHO_MSG. The - pkg-message file is only for - post-installation steps. Likewise, the distinction between - ECHO_MSG and ECHO_CMD - should be kept in mind. The former is for printing - informational text to the screen, while the latter is for - command pipelining: + When some lines about the build-time knobs or warnings + have to be displayed, use ECHO_MSG. The + pkg-message file is only for + post-installation steps. Likewise, the distinction between + ECHO_MSG and ECHO_CMD + should be kept in mind. The former is for printing + informational text to the screen, while the latter is for + command pipelining: - update-etc-shells: + update-etc-shells: @${ECHO_MSG} "updating /etc/shells" @${CP} /etc/shells /etc/shells.bak @( ${GREP} -v ${PREFIX}/bin/bash /etc/shells.bak; \ ${ECHO_CMD} ${PREFIX}/bin/bash) >/etc/shells @${RM} /etc/shells.bak - - The pkg-message file does not need - to be added to pkg-plist. - - + + The pkg-message file does not need + to be added to pkg-plist. + + - - <filename>pkg-install</filename> + + <filename>pkg-install</filename> - If your port needs to execute commands when the binary - package is installed with pkg add or - pkg install you can do this via the - pkg-install script. This script will - automatically be added to the package, and will be run twice - by pkg the first time as - ${SH} pkg-install ${PKGNAME} - PRE-INSTALL and the second time as - ${SH} pkg-install ${PKGNAME} - POST-INSTALL. $2 can be - tested to determine which mode the script is being run in. - The PKG_PREFIX environmental variable will be - set to the package installation directory. + If your port needs to execute commands when the binary + package is installed with pkg add or + pkg install you can do this via the + pkg-install script. This script will + automatically be added to the package, and will be run twice by + pkg the first time as - - This script is not run automatically if you install the - port with make install. If you are - depending on it being run, you will have to explicitly call - it from your port's Makefile, with a - line like PKG_PREFIX=${PREFIX} ${SH} - ${PKGINSTALL} ${PKGNAME} - PRE-INSTALL. - - + ${SH} pkg-install ${PKGNAME} + PRE-INSTALL and the second time as + ${SH} pkg-install ${PKGNAME} + POST-INSTALL. $2 can be + tested to determine which mode the script is being run in. + The PKG_PREFIX environmental variable will be + set to the package installation directory. - - <filename>pkg-deinstall</filename> + + This script is not run automatically if you install the + port with make install. If you are + depending on it being run, you will have to explicitly call + it from your port's Makefile, with a + line like PKG_PREFIX=${PREFIX} ${SH} + ${PKGINSTALL} ${PKGNAME} + PRE-INSTALL. + + - This script executes when a package is removed. + + <filename>pkg-deinstall</filename> - This script will be run twice by pkg - delete The first time as ${SH} - pkg-deinstall ${PKGNAME} DEINSTALL and the - second time as ${SH} pkg-deinstall - ${PKGNAME} POST-DEINSTALL. - + This script executes when a package is removed. - - Changing the Names of - <filename>pkg-*</filename> - Files + This script will be run twice by + pkg delete The first time as + ${SH} pkg-deinstall ${PKGNAME} + DEINSTALL and the second time as + ${SH} pkg-deinstall + ${PKGNAME} POST-DEINSTALL. + - All the names of - pkg-* files - are defined using variables so you can change them in your - Makefile if need be. This is especially - useful when you are sharing the same - pkg-* files - among several ports or have to write to one of the above files - (see writing to places other - than WRKDIR for why it is a bad - idea to write directly into the - pkg-* - subdirectory). + + Changing the Names of + <filename>pkg-*</filename> Files - Here is a list of variable names and their default values. - (PKGDIR defaults to - ${MASTERDIR}.) + All the names of pkg-* files are + defined using variables so you can change them in your + Makefile if need be. This is especially + useful when you are sharing the same pkg-* + files among several ports or have to write to one of the above + files (see writing to places + other than WRKDIR for why it is a + bad idea to write directly into the pkg-* + subdirectory). - - - - - Variable - Default value - - + Here is a list of variable names and their default values. + (PKGDIR defaults to + ${MASTERDIR}.) - - - DESCR - ${PKGDIR}/pkg-descr - + + + + + Variable + Default value + + - - PLIST - ${PKGDIR}/pkg-plist - + + + DESCR + ${PKGDIR}/pkg-descr + - - PKGINSTALL - ${PKGDIR}/pkg-install - + + PLIST + ${PKGDIR}/pkg-plist + - - PKGDEINSTALL - ${PKGDIR}/pkg-deinstall - + + PKGINSTALL + ${PKGDIR}/pkg-install + - - PKGMESSAGE - ${PKGDIR}/pkg-message - - - - + + PKGDEINSTALL + ${PKGDIR}/pkg-deinstall + - Please change these variables rather than overriding - PKG_ARGS. If you change - PKG_ARGS, those files will not correctly be - installed in /var/db/pkg upon install - from a port. - + + PKGMESSAGE + ${PKGDIR}/pkg-message + + + + - - Making Use of <varname>SUB_FILES</varname> and - <varname>SUB_LIST</varname> + Please change these variables rather than overriding + PKG_ARGS. If you change + PKG_ARGS, those files will not correctly be + installed in /var/db/pkg upon install + from a port. + - The SUB_FILES and - SUB_LIST variables are useful for dynamic - values in port files, such as the installation - PREFIX in - pkg-message. + + Making Use of <varname>SUB_FILES</varname> and + <varname>SUB_LIST</varname> - The SUB_FILES variable specifies a list - of files to be automatically modified. Each - file in the - SUB_FILES list must have a corresponding - file.in - present in FILESDIR. A modified version - will be created in WRKDIR. Files defined - as a value of USE_RC_SUBR (or the - deprecated USE_RCORDER) are automatically - added to the SUB_FILES. For the files - pkg-message, - pkg-install, - and - pkg-deinstall, - the corresponding Makefile - variable is automatically set to point to the processed - version. + The SUB_FILES and + SUB_LIST variables are useful for dynamic + values in port files, such as the installation + PREFIX in + pkg-message. - The SUB_LIST variable is a list of - VAR=VALUE pairs. For each pair - %%VAR%% will get replaced with - VALUE in each file listed in - SUB_FILES. Several common pairs are - automatically defined: PREFIX, - LOCALBASE, DATADIR, - DOCSDIR, EXAMPLESDIR, - WWWDIR, and ETCDIR. - Any line beginning with @comment will be - deleted from resulting files after a variable - substitution. + The SUB_FILES variable specifies a list + of files to be automatically modified. Each + file in the + SUB_FILES list must have a corresponding + file.in present in + FILESDIR. A modified version will be created + in WRKDIR. Files defined as a value of + USE_RC_SUBR (or the deprecated + USE_RCORDER) are automatically added to the + SUB_FILES. For the files + pkg-message, + pkg-install, and + pkg-deinstall, the corresponding Makefile + variable is automatically set to point to the processed + version. - The following example will replace - %%ARCH%% with the system architecture in a - pkg-message: + The SUB_LIST variable is a list of + VAR=VALUE pairs. For each pair + %%VAR%% will get replaced with + VALUE in each file listed in + SUB_FILES. Several common pairs are + automatically defined: PREFIX, + LOCALBASE, DATADIR, + DOCSDIR, EXAMPLESDIR, + WWWDIR, and ETCDIR. Any + line beginning with @comment will be deleted + from resulting files after a variable substitution. - SUB_FILES= pkg-message + The following example will replace + %%ARCH%% with the system architecture in a + pkg-message: + + SUB_FILES= pkg-message SUB_LIST= ARCH=${ARCH} - Note that for this example, the - pkg-message.in file must exist in - FILESDIR. + Note that for this example, the + pkg-message.in file must exist in + FILESDIR. - Example of a good - pkg-message.in: + Example of a good + pkg-message.in: - Now it is time to configure this package. + Now it is time to configure this package. Copy %%PREFIX%%/share/examples/putsy/%%ARCH%%.conf into your home directory as .putsy.conf and edit it. - - - + +