diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.xml b/en_US.ISO8859-1/books/handbook/ports/chapter.xml index 663a4873da..a91c1598a0 100644 --- a/en_US.ISO8859-1/books/handbook/ports/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/ports/chapter.xml @@ -37,7 +37,7 @@ How to manage binary packages using - pkgng. + pkg. @@ -102,7 +102,7 @@ A &os; package contains pre-compiled copies of all the commands for an application, as well as any configuration files and documentation. A package can be manipulated with the - pkgng commands, such as + pkg commands, such as pkg install. A &os; port is a collection of files designed to automate @@ -407,11 +407,11 @@ Info: Lists information about open files (similar to fstat(1)) At the present time, &os; is transitioning toward a new method of package management. Users may wish to investigate the benefits of using - PKGng to manage third-party + pkg to manage third-party software on &os;. This section describes the traditional method for managing binary packages and only applies to those users who have not yet migrated to the - pkgng format. + pkg format. This method of package management uses a package database directory, /var/db/pkg, @@ -619,30 +619,30 @@ docbook = --> - Using <application>pkgng</application> for Binary Package + <title>Using <application>pkg</application> for Binary Package Management - pkgng is the next generation + pkg is the next generation replacement for the traditional &os; package management tools, offering many features that make dealing with binary packages faster and easier. - pkgng is not a replacement for + pkg is not a replacement for port management tools like ports-mgmt/portmaster or ports-mgmt/portupgrade. These tools can be used to install third-party software from both binary packages and the Ports Collection, while - pkgng installs only binary + pkg installs only binary packages. Getting Started with - <application>pkgng</application> + pkg &os; 8.4 and later includes a bootstrap utility which can be used to download and install - pkgng, along with its manual + pkg, along with its manual pages. To bootstrap the system, run: @@ -650,7 +650,7 @@ docbook = &prompt.root; /usr/sbin/pkg For earlier &os; versions, - pkgng must instead be installed + pkg must instead be installed from the Ports Collection or as a binary package. To install the port, run: @@ -659,24 +659,25 @@ docbook = &prompt.root; make &prompt.root; make install clean - To install the binary package, run: - - &prompt.root; pkg_add -r pkg - - Once pkgng is installed, the + When upgrading an existing system that originally used the + older package system, the database must be converted to the + new format, so that the new tools are aware of the already + installed packages. Once pkg has + been installed, the package database must be converted from the traditional format to the new format by running this command: &prompt.root; pkg2ng - This step is not required for new installations that do - not yet have any third-party software installed. + This step is not required for new installations that + do not yet have any third-party software + installed. This step is not reversible. Once the package database - has been converted to the pkgng + has been converted to the pkg format, the traditional pkg_* tools - should not be used. + should no longer be used. @@ -689,28 +690,28 @@ docbook = To ensure that the &os; Ports Collection registers - new software with pkgng, and not + new software with pkg, and not the traditional packages format, &os; versions earlier than 10.X require this line in /etc/make.conf: WITH_PKGNG= yes - The pkgng package management + The pkg package management system uses a package repository for most operations. The default package repository location is defined in /usr/local/etc/pkg.conf or by the PACKAGESITE environment variable, which overrides the configuration file. - Additional pkgng + Additional pkg configuration options are described in pkg.conf(5). - Usage information for pkgng is + Usage information for pkg is available in pkg(8) or by running pkg without additional arguments. - Each pkgng command argument is + Each pkg command argument is documented in a command-specific manual page. To read the manual page for pkg install, for example, run either of these commands: @@ -721,7 +722,7 @@ docbook = The rest of this section demonstrates common binary package management tasks which can be performed using - pkgng. Each demonstrated command + pkg. Each demonstrated command provides many switches to customize its use. Refer to a command's help or man page for details and more examples. @@ -737,7 +738,7 @@ docbook = package. For example, to see which version of - pkgng is installed, run: + pkg is installed, run: &prompt.root; pkg info pkg pkg-1.1.4_1 @@ -825,7 +826,7 @@ Proceed with deleting packages [y/N]: y Occasionally, software vulnerabilities may be discovered in third-party applications. To address this, - pkgng includes a built-in auditing + pkg includes a built-in auditing mechanism. To determine if there are any known vulnerabilities for the software installed on the system, run: @@ -855,7 +856,7 @@ Deinstalling ca_root_nss-3.15.1_1... done Backing Up the Package Database Unlike the traditional package management system, - pkgng includes its own package + pkg includes its own package database backup mechanism. To manually back up the contents of the package database, run the following command, replacing pkgng.db with a suitable file @@ -863,16 +864,15 @@ Deinstalling ca_root_nss-3.15.1_1... done &prompt.root; pkg backup -d pkgng.db - Additionally, pkgng includes + Additionally, pkg includes a &man.periodic.8; script to automatically perform a daily back up of the package database. This functionality is - enabled if daily_backup_pkgng_enable is + enabled if daily_backup_pkgdb_enable is set to YES in &man.periodic.conf.5;. To disable the periodic script from backing up the - package database, set daily_backup_pkgdb_ - enable to NO in + package database, set daily_backup_pkgdb_enable to NO in &man.periodic.conf.5;. @@ -885,7 +885,7 @@ Deinstalling ca_root_nss-3.15.1_1... done Removing Stale Packages - By default, pkgng stores + By default, pkg stores binary packages in a cache directory defined by PKG_CACHEDIR in pkg.conf(5). When upgrading packages with pkg upgrade, old versions @@ -901,7 +901,7 @@ Deinstalling ca_root_nss-3.15.1_1... done Software within the &os; Ports Collection can undergo major version number changes. To address this, - pkgng has a built-in command to + pkg has a built-in command to update package origins. This can be useful, for example, if lang/php5 is renamed to lang/php53 so that @@ -1014,7 +1014,7 @@ Deinstalling ca_root_nss-3.15.1_1... done &prompt.root; make install clean If the ports tree is not available, or - pkgng is being used to manage + pkg is being used to manage packages, Subversion can be installed as a package: @@ -1361,7 +1361,7 @@ The deinstallation will free 229 kB or . On &os; 10 and later, or if the system has been converted to - pkgng, the following command will + pkg, the following command will list the installed ports which are out of date: &prompt.root; pkg version -l "<"