From owner-svn-doc-all@FreeBSD.ORG Wed Oct 2 20:02:03 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 177CB834; Wed, 2 Oct 2013 20:02:03 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EA07124EE; Wed, 2 Oct 2013 20:02:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r92K22Qb086544; Wed, 2 Oct 2013 20:02:02 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r92K225k086542; Wed, 2 Oct 2013 20:02:02 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310022002.r92K225k086542@svn.freebsd.org> From: Dru Lavigne Date: Wed, 2 Oct 2013 20:02:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42809 - head/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 20:02:03 -0000 Author: dru Date: Wed Oct 2 20:02:02 2013 New Revision: 42809 URL: http://svnweb.freebsd.org/changeset/doc/42809 Log: This patch: - clarifies that this is an alternative to pkgng - updates the listing version numbers and removes the example for manually fetching a pkg - removes .tgz format - does some word-smithing to make what is demonstrated clearer and to refer the reader to man pages for further usage examples - comments out the author info so that it doesn't render in the print version Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Oct 2 18:00:46 2013 (r42808) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Oct 2 20:02:02 2013 (r42809) @@ -341,33 +341,40 @@ Info: Lists information about open fil + - + + --> Using Binary Packages At the present time, &os; is transitioning toward a new - method of package management. Users of the latest releases + method of package management. Users may wish to investigate the benefits of using - PKGng to manage third - party software on &os;. For those not yet migrated to the - pkgng tool, the tools discussed - here may be used for managing the package database. For - simplicity, the sysinstall utility is - also available post-install for package management. + PKGng 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. - All package installation files are stored in the + This method of package management uses a package database directory, - /var/db/pkg. + /var/db/pkg, to track + installed software versions and the files installed with each + application. Several utilities interact with the database + directory and are used to manage binary packages. These + commands begin with pkg_. This section + provides an overview of the commands which are used to install, + delete, and gather information about binary packages. Each + command provides many switches to customize its operation. + Refer to the listed man pages for more details and further usage + examples. Installing a Package @@ -380,43 +387,16 @@ Info: Lists information about open fil pkg_add - Use &man.pkg.add.1; to install a &os; binary package from - a local file or from a server on the network. - - - Downloading a Package Manually and Installing It - Locally - - &prompt.root; ftp -a ftp2.FreeBSD.org -Connected to ftp2.FreeBSD.org. -220 ftp2.FreeBSD.org FTP server (Version 6.00LS) ready. -331 Guest login ok, send your email address as password. -230- -230- This machine is in Vienna, VA, USA, hosted by Verio. -230- Questions? E-mail freebsd@vienna.verio.net. -230- -230- -230 Guest login ok, access restrictions apply. -Remote system type is UNIX. -Using binary mode to transfer files. -ftp> cd /pub/FreeBSD/ports/packages/sysutils/ -250 CWD command successful. -ftp> get lsof-4.56.4.tgz -local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz -200 PORT command successful. -150 Opening BINARY mode data connection for 'lsof-4.56.4.tgz' (92375 bytes). -100% |**************************************************| 92375 00:00 ETA -226 Transfer complete. -92375 bytes received in 5.60 seconds (16.11 KB/s) -ftp> exit -&prompt.root; pkg_add lsof-4.56.4.tgz - - - If you do not have a source of local packages, such as a - &os; CD-ROM set, include with + To install a binary package from + a local &os; media or a remote &os; package server, use &man.pkg.add.1;. + While a &os; media can provide a source of local packages + without requiring a network connection, it may not contain + the latest versions of binary packages as new versions are + always being rebuilt for the &os; package servers. To install + from a package server, always include (for remote) with &man.pkg.add.1;. This automatically determines the correct object format and release, and then fetches and installs the - package from an FTP site without any further user + package from a package server without any further user intervention. @@ -424,18 +404,16 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 &prompt.root; pkg_add -r lsof - To specify an alternative &os; FTP mirror, specify the + In this example, lsof is used without + specifying a version number as the version is not included when the remote + fetching feature is used. To specify an alternative &os; FTP mirror, specify the mirror in the PACKAGESITE environment variable. &man.pkg.add.1; uses &man.fetch.3; to download files, which uses various environment variables, including FTP_PASSIVE_MODE, FTP_PROXY, and FTP_PASSWORD. You may need to set one or more of these if you are behind a firewall, or need to use an - FTP/HTTP proxy. See &man.fetch.3; for the complete list of variables. - Note that in the example above lsof is used - instead of lsof-4.56.4. When the remote - fetching feature is used, the version number of the package - must be removed. + FTP/HTTP proxy. See &man.fetch.3; for the complete list of FTP-related variables. &man.pkg.add.1; will automatically download the latest @@ -444,23 +422,23 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 installs the version of the package that was built with that release. It is possible to change this behavior by overriding PACKAGESITE. For example, on a - &os; 8.1-RELEASE system, by default &man.pkg.add.1; + &os; 9.1-RELEASE system, by default &man.pkg.add.1; will try to fetch packages from - ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/. - To force &man.pkg.add.1; to download &os; 8-STABLE + ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.1-release/Latest/. + To force &man.pkg.add.1; to download &os; 9-STABLE packages, set PACKAGESITE to - ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/. + ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest/. - Package files are distributed in .tgz - and .tbz formats. Packages are + Package files are distributed in the + .tbz format. Packages are available from , + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"> or the /packages directory of the &os; DVD distribution. The layout of the packages directory is similar to - that of the /usr/ports tree. Each + that of the /usr/ports tree. Each category has its own directory, and every package can be found - within the All directory. + within the All directory. @@ -471,21 +449,21 @@ local: lsof-4.56.4.tgz remote: lsof-4.56 managing - &man.pkg.info.1; can be used to list and describe - installed packages: + To list and describe + installed packages, use &man.pkg.info.1;: pkg_info &prompt.root; pkg_info -colordiff-1.0.13 A tool to colorize diff output -docbook-1.2 Meta-port for the different versions of the DocBook DTD +colordiff-1.0.13 Tool to colorize diff output +docbook-1.4 Meta-port for the different versions of the DocBook DTD ... - &man.pkg.version.1; summarizes the versions of all - installed packages and compares the package version to the - current version found in the ports tree. + To receive a summary of the versions of all + installed packages and a comparison of the installed package versions to the + current versions found in the locally installed ports tree, use &man.pkg.version.1;: pkg_version @@ -546,7 +524,7 @@ docbook = ! The installed package exists in the index but for - some reason, pkg_version was unable + some reason pkg_version was unable to compare the version number of the installed package with the corresponding entry in the index. @@ -570,12 +548,12 @@ docbook = To remove a previously installed software package, use &man.pkg.delete.1;: - &prompt.root; pkg_delete xchat-1.7.1 + &prompt.root; pkg_delete xchat-2.8.8_1 Note that &man.pkg.delete.1; requires the full package - name and number; the above command would not work if + name and number and that the above command would not work if xchat was given instead of - xchat-1.7.1. Use + xchat-2.8.8_1. Use &man.pkg.version.1; to find the version of the installed package, or use a wildcard: