From owner-svn-doc-all@FreeBSD.ORG Wed Apr 2 19:05:22 2014 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 ESMTPS id DE6B1A31; Wed, 2 Apr 2014 19:05:22 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C747BCC6; Wed, 2 Apr 2014 19:05:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s32J5M10026720; Wed, 2 Apr 2014 19:05:22 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s32J5MXr026719; Wed, 2 Apr 2014 19:05:22 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404021905.s32J5MXr026719@svn.freebsd.org> From: Dru Lavigne Date: Wed, 2 Apr 2014 19:05:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44421 - 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.17 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 Apr 2014 19:05:22 -0000 Author: dru Date: Wed Apr 2 19:05:22 2014 New Revision: 44421 URL: http://svnweb.freebsd.org/changeset/doc/44421 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems 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 Apr 2 18:12:18 2014 (r44420) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Apr 2 19:05:22 2014 (r44421) @@ -197,7 +197,7 @@ Before installing any application, check http://vuxml.freebsd.org/ for security issues related to the application or install - ports-mgmt/portaudit. Once installed, type + ports-mgmt/portaudit. Once installed, type portaudit -F -a to check all installed applications for known vulnerabilities. @@ -422,11 +422,12 @@ Info: Lists information about open fil Package files are distributed in the .tbz format. Packages are available - from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/ + from 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 - category has its own directory, and every package can be + similar to that of the /usr/ports tree. + Each category has its own directory, and every package can be found within the All directory. @@ -880,18 +881,18 @@ Deinstalling ca_root_nss-3.15.1_1... don The Ports Collection is a set of Makefiles, patches, and description files - stored in /usr/ports. - This set of files is used to compile and install applications - on &os;. Before an application can be compiled using a port, - the Ports Collection must first be installed. If it was not - installed during the installation of &os;, use one of the - following methods to install it: + stored in /usr/ports. This set of files is + used to compile and install applications on &os;. Before an + application can be compiled using a port, the Ports Collection + must first be installed. If it was not installed during the + installation of &os;, use one of the following methods to + install it: Portsnap Method The base system of &os; includes - Portsnap. This is a fast and + Portsnap. This is a fast and user-friendly tool for retrieving the Ports Collection and is the recommended choice for most users. This utility connects to a &os; site, verifies the secure key, and @@ -907,8 +908,8 @@ Deinstalling ca_root_nss-3.15.1_1... don - When running Portsnap for - the first time, extract the snapshot into + When running Portsnap for the + first time, extract the snapshot into /usr/ports: &prompt.root; portsnap extract @@ -934,20 +935,19 @@ Deinstalling ca_root_nss-3.15.1_1... don Subversion Method - If more control over the ports tree is needed or if - local changes need to be maintained, - Subversion can be used to - obtain the Ports Collection. Refer to If more control over the ports tree is needed or if local + changes need to be maintained, + Subversion can be used to obtain + the Ports Collection. Refer to the Subversion Primer for a detailed description of Subversion. - Subversion must be - installed before it can be used to check out the ports - tree. If a copy of the ports tree is already present, - install Subversion like - this: + Subversion must be installed + before it can be used to check out the ports tree. If a + copy of the ports tree is already present, install + Subversion like this: &prompt.root; cd /usr/ports/devel/subversion &prompt.root; make install clean @@ -996,9 +996,9 @@ Deinstalling ca_root_nss-3.15.1_1... don - distinfo: contains the names - and checksums of the files that must be downloaded to - build the port. + distinfo: contains the names and + checksums of the files that must be downloaded to build the + port. @@ -1147,8 +1147,7 @@ Deinstalling ca_root_nss-3.15.1_1... don To save this extra step, instead use make - install clean when - compiling the port. + install clean when compiling the port. @@ -1164,11 +1163,10 @@ Deinstalling ca_root_nss-3.15.1_1... don options, it may pause several times for user interaction as the default behavior is to prompt the user to select options from a menu. To avoid this, run make - config-recursive - within the port skeleton to do this configuration in one - batch. Then, run make - install [clean] to - compile and install the port. + config-recursive within the port skeleton to do + this configuration in one batch. Then, run make + install [clean] to compile and install the + port. When using @@ -1176,10 +1174,10 @@ Deinstalling ca_root_nss-3.15.1_1... don ports to configure are gathered by the all-depends-list target. It is recommended to run make - config-recursive - until all dependent ports options have been defined, and - ports options screens no longer appear, to be certain - that all dependency options have been configured. + config-recursive until all dependent ports + options have been defined, and ports options screens no + longer appear, to be certain that all dependency options + have been configured. There are several ways to revisit a port's build options @@ -1189,10 +1187,10 @@ Deinstalling ca_root_nss-3.15.1_1... don port and type make config. Another option is to use make showconfig. Another option is to execute make - rmconfig which will - remove all selected options and allow you to start over. - All of these options, and others, are explained in great - detail in &man.ports.7;. + rmconfig which will remove all selected options + and allow you to start over. All of these options, and + others, are explained in great detail in + &man.ports.7;. The ports system uses &man.fetch.1; to download the source files, which supports various environment variables. @@ -1203,17 +1201,16 @@ Deinstalling ca_root_nss-3.15.1_1... don complete list of supported variables. For users who cannot be connected to the Internet all - the time, make fetch can be run - within /usr/ports, to fetch all - distfiles, or within a category, such as + the time, make fetch can be run within + /usr/ports, to fetch all distfiles, or + within a category, such as /usr/ports/net, or within the specific port skeleton. Note that if a port has any dependencies, running this command in a category or ports skeleton will not fetch the distfiles of ports from another category. Instead, use make - fetch-recursive to - also fetch the distfiles for all the dependencies of a - port. + fetch-recursive to also fetch the distfiles for + all the dependencies of a port. In rare cases, such as when an organization has a local distfiles repository, the MASTER_SITES @@ -1245,10 +1242,9 @@ Deinstalling ca_root_nss-3.15.1_1... don will combine the two. - These can also be set as environmental variables. - Refer to the manual page for your shell for instructions - on how to set an environmental variable. - + These can also be set as environmental variables. Refer + to the manual page for your shell for instructions on how to + set an environmental variable. @@ -1313,15 +1309,14 @@ The deinstallation will free 229 kB attempting an upgrade, read /usr/ports/UPDATING from the top of the file to the date closest to the last time ports were - upgraded or the system was installed. This file - describes various issues and additional steps users may - encounter and need to perform when updating a port, - including such things as file format changes, changes in - locations of configuration files, or any - incompatibilities with previous versions. Make note of - any instructions which match any of the ports that need - upgrading and follow these instructions when performing - the upgrade. + upgraded or the system was installed. This file describes + various issues and additional steps users may encounter and + need to perform when updating a port, including such things + as file format changes, changes in locations of + configuration files, or any incompatibilities with previous + versions. Make note of any instructions which match any of + the ports that need upgrading and follow these instructions + when performing the upgrade. To perform the actual upgrade, use either @@ -1462,9 +1457,9 @@ The deinstallation will free 229 kB To upgrade only a specified application instead of all available ports, use portupgrade - pkgname. It is very important to include - to first upgrade all the ports required - by the given application: + pkgname. It is very + important to include to first upgrade + all the ports required by the given application: &prompt.root; portupgrade -R firefox @@ -1472,9 +1467,9 @@ The deinstallation will free 229 kB is included, Portupgrade searches for available packages in the local directories listed in - PKG_PATH. If none are available locally, - it then fetches packages from a remote site. If - packages can not be found locally or fetched remotely, + PKG_PATH. If none are available locally, it + then fetches packages from a remote site. If packages can + not be found locally or fetched remotely, Portupgrade will use ports. To avoid using ports entirely, specify . This last set of options tells @@ -1545,62 +1540,58 @@ The deinstallation will free 229 kB Building Packages with <application>Poudriere</application> - Poudriere is a + Poudriere is a BSD-licensed utility for creating and testing - &os; packages. It uses &os; jails to set - up isolated compilation environments which can be used to build - packages for versions of &os; that are different from the box - on which it is installed, and also to build packages for i386 if - the host is an &arch.amd64; system. Once the packages are built, they - will be in a layout identical to the official mirrors and are - therefore useable by - &man.pkg.8; and other package management tools. - - Poudriere can be installed - using the - ports-mgmt/poudriere package or - port. The installation will include a sample configuration file - /usr/local/etc/poudriere.conf.sample. - This file should be copied to - /usr/local/etc/poudriere.conf which can - then be edited to suit the local configuration. - - While ZFS is not required on the - system running poudriere, - it is beneficial. When ZFS is used, the - ZPOOL must be - specified in - /usr/local/etc/poudriere.conf and - FREEBSD_HOST should be set to a nearby - mirror. Defining - CCACHE_DIR enables the use of - devel/ccache to cache - compilation and reduce build times for - frequently-compiled code. It may be convenient to put - poudriere datasets in an isolated - tree mounted at - /poudriere. Defaults - for the other configuration values are adequate. - - The number of processor cores detected is used to define - how many builds should run in parallel. Supply enough virtual - memory, either with RAM or swap space. If - virtual memory runs out, compiling jails will stop and be torn - down, resulting in weird error messages. + &os; packages. It uses &os; jails to set up isolated + compilation environments which can be used to build packages for + versions of &os; that are different from the box on which it is + installed, and also to build packages for i386 if the host is an + &arch.amd64; system. Once the packages are built, they will be + in a layout identical to the official mirrors and are therefore + useable by &man.pkg.8; and other package management + tools. + + Poudriere can be installed using + the ports-mgmt/poudriere package + or port. The installation will include a sample configuration + file /usr/local/etc/poudriere.conf.sample. + This file should be copied to + /usr/local/etc/poudriere.conf which can + then be edited to suit the local configuration. + + While ZFS is not required on the system + running poudriere, it is beneficial. + When ZFS is used, the + ZPOOL must be specified in + /usr/local/etc/poudriere.conf and + FREEBSD_HOST should be set to a nearby + mirror. Defining CCACHE_DIR enables the use + of devel/ccache to cache + compilation and reduce build times for frequently-compiled code. + It may be convenient to put + poudriere datasets in an isolated + tree mounted at /poudriere. Defaults for the + other configuration values are adequate. + + The number of processor cores detected is used to define how + many builds should run in parallel. Supply enough virtual + memory, either with RAM or swap space. If + virtual memory runs out, compiling jails will stop and be torn + down, resulting in weird error messages. Initialize Jails and Port Trees Once configured, initialize poudriere so that it installs a - jail with the required &os; tree and a - ports tree. Specify a name for the jail using - and the &os; version with - . On systems running &os;/&arch.amd64;, - the architecture can be set with to - either i386 or amd64. - The default is to use the architecture shown by - uname. + jail with the required &os; tree and a ports tree. Specify a + name for the jail using and the &os; + version with . On systems running + &os;/&arch.amd64;, the architecture can be set with + to either i386 or + amd64. The default is to use the + architecture shown by uname. &prompt.root; poudriere jail -c -j 10amd64 -v 10.0-RELEASE ====>> Creating 10amd64 fs... done @@ -1693,8 +1684,9 @@ ports-mgmt/pkg that can be used with a web server to display build information. - Once the build is complete, packages are now available for installation from the - poudriere repository. + Once the build is complete, packages are now available for + installation from the poudriere + repository. For more information on using poudriere, see &man.poudriere.8;