From owner-svn-doc-head@FreeBSD.ORG Wed Oct 2 12:38:20 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D32339A3; Wed, 2 Oct 2013 12:38:20 +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 B121826C8; Wed, 2 Oct 2013 12:38:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r92CcKY4047995; Wed, 2 Oct 2013 12:38:20 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r92CcKjB047993; Wed, 2 Oct 2013 12:38:20 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310021238.r92CcKjB047993@svn.freebsd.org> From: Dru Lavigne Date: Wed, 2 Oct 2013 12:38:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42802 - 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-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 12:38:20 -0000 Author: dru Date: Wed Oct 2 12:38:20 2013 New Revision: 42802 URL: http://svnweb.freebsd.org/changeset/doc/42802 Log: Minor word-smith patch which also: - introduces the term porting - adds mention of traditional and pkgng formats 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 11:47:11 2013 (r42801) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Oct 2 12:38:20 2013 (r42802) @@ -67,14 +67,14 @@ - Download the software, which might be distributed in - source code format, or as a binary. + Find and download the software, which might be distributed in + source code format or as a binary. - Unpack the software from its distribution format - (typically a tarball compressed with &man.compress.1;, - &man.gzip.1;, or &man.bzip2.1;). + Unpack the software from its distribution format. This + is typically a tarball compressed with &man.compress.1;, + &man.gzip.1;, or &man.bzip2.1;. @@ -87,8 +87,8 @@ If the software was distributed in source format, compile it. This may involve editing a - Makefile, or running a - configure script, and other work. + Makefile or running a + configure script. @@ -96,19 +96,20 @@ - If you are installing a software package that was not - deliberately ported to &os; you may even have to go in and edit - the code to make it work properly. - - &os; provides two technologies which perform these steps for - you. At the time of writing, over &os.numports; third-party - applications are available. + If the software package was not + deliberately ported, or tested to work, on &os;, the source code may need editing + in order for it to install and run properly. At the time of + this writing, over &os.numports; third-party + applications have been ported to &os;. + + &os; provides two technologies which automate these steps. 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 &os; - package management commands, such as &man.pkg.add.1;, - &man.pkg.delete.1;, and &man.pkg.info.1;. + and documentation. A package can be manipulated with the traditional &os; + package management commands, such as &man.pkg.add.1;, or using + the newer pkgng commands, such as + pkg install. A &os; port is a collection of files designed to automate the process of compiling an application from source code. The @@ -121,12 +122,12 @@ commands. Both packages and ports understand - dependencies. If &man.pkg.add.1; or the - Ports Collection is used to install an application and a + dependencies. If a package or port + is used to install an application and a dependent library is not already installed, the library will automatically be installed first. - While the two technologies are quite similar, packages and + While the two technologies are similar, packages and ports each have their own strengths. Select the technology that meets your requirements for installing a particular application. @@ -145,7 +146,7 @@ applications, such as Mozilla, KDE, or - GNOME this can be important, + GNOME, this can be important on a slow system. @@ -156,7 +157,7 @@ - Ports Benefits + Port Benefits Packages are normally compiled with conservative @@ -184,7 +185,7 @@ The licensing conditions of some software forbid binary - distribution. These must be distributed as source code + distribution. Such software must be distributed as source code which must be compiled by the end-user. @@ -195,8 +196,8 @@ - If you have local patches, you will need the source in - order to apply them. + Source code is needed in + order to apply custom patches.