svn commit: r44421 - head/en_US.ISO8859-1/books/handbook/ports
Dru Lavigne
dru at FreeBSD.org
Wed Apr 2 19:05:22 UTC 2014
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 @@
<para>Before installing any application, check <uri
xlink:href="http://vuxml.freebsd.org/">http://vuxml.freebsd.org/</uri>
for security issues related to the application or install
- <package>ports-mgmt/portaudit</package>. Once installed, type
+ <package>ports-mgmt/portaudit</package>. Once installed, type
<command>portaudit -F -a</command> to check all installed
applications for known vulnerabilities.</para>
</warning>
@@ -422,11 +422,12 @@ Info: Lists information about open fil
<para>Package files are distributed in the
<filename>.tbz</filename> format. Packages are available
- from <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/</uri>
+ from <uri
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/</uri>
or the <filename>/packages</filename> directory of the &os;
DVD distribution. The layout of the packages directory is
- similar to that of the <filename>/usr/ports</filename> tree. Each
- category has its own directory, and every package can be
+ similar to that of the <filename>/usr/ports</filename> tree.
+ Each category has its own directory, and every package can be
found within the <filename>All</filename> directory.</para>
</sect2>
@@ -880,18 +881,18 @@ Deinstalling ca_root_nss-3.15.1_1... don
<para>The Ports Collection is a set of
<filename>Makefiles</filename>, patches, and description files
- stored in <filename>/usr/ports</filename>.
- 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:</para>
+ stored in <filename>/usr/ports</filename>. 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:</para>
<procedure>
<title>Portsnap Method</title>
<para>The base system of &os; includes
- <application>Portsnap</application>. This is a fast and
+ <application>Portsnap</application>. 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
</step>
<step>
- <para>When running <application>Portsnap</application> for
- the first time, extract the snapshot into
+ <para>When running <application>Portsnap</application> for the
+ first time, extract the snapshot into
<filename>/usr/ports</filename>:</para>
<screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
@@ -934,20 +935,19 @@ Deinstalling ca_root_nss-3.15.1_1... don
<procedure>
<title>Subversion Method</title>
- <para>If more control over the ports tree is needed or if
- local changes need to be maintained,
- <application>Subversion</application> can be used to
- obtain the Ports Collection. Refer to <link
+ <para>If more control over the ports tree is needed or if local
+ changes need to be maintained,
+ <application>Subversion</application> can be used to obtain
+ the Ports Collection. Refer to <link
xlink:href="&url.articles.committers-guide;/subversion-primer.html">the
Subversion Primer</link> for a detailed description of
<application>Subversion</application>.</para>
<step>
- <para><application>Subversion</application> 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 <application>Subversion</application> like
- this:</para>
+ <para><application>Subversion</application> 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
+ <application>Subversion</application> like this:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/devel/subversion</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
@@ -996,9 +996,9 @@ Deinstalling ca_root_nss-3.15.1_1... don
</listitem>
<listitem>
- <para><filename>distinfo</filename>: contains the names
- and checksums of the files that must be downloaded to
- build the port.</para>
+ <para><filename>distinfo</filename>: contains the names and
+ checksums of the files that must be downloaded to build the
+ port.</para>
</listitem>
<listitem>
@@ -1147,8 +1147,7 @@ Deinstalling ca_root_nss-3.15.1_1... don
<note>
<para>To save this extra step, instead use <command>make
- install clean</command> when
- compiling the port.</para>
+ install clean</command> when compiling the port.</para>
</note>
<sect3>
@@ -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 <command>make
- config-recursive</command>
- within the port skeleton to do this configuration in one
- batch. Then, run <command>make
- install [clean]</command> to
- compile and install the port.</para>
+ config-recursive</command> within the port skeleton to do
+ this configuration in one batch. Then, run <command>make
+ install [clean]</command> to compile and install the
+ port.</para>
<tip>
<para>When using
@@ -1176,10 +1174,10 @@ Deinstalling ca_root_nss-3.15.1_1... don
ports to configure are gathered by the
<buildtarget>all-depends-list</buildtarget> target. It is
recommended to run <command>make
- config-recursive</command>
- 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.</para>
+ config-recursive</command> 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.</para>
</tip>
<para>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 <command>make config</command>. Another
option is to use <command>make showconfig</command>.
Another option is to execute <command>make
- rmconfig</command> 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;.</para>
+ rmconfig</command> 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;.</para>
<para>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.</para>
<para>For users who cannot be connected to the Internet all
- the time, <command>make fetch</command> can be run
- within <filename>/usr/ports</filename>, to fetch all
- distfiles, or within a category, such as
+ the time, <command>make fetch</command> can be run within
+ <filename>/usr/ports</filename>, to fetch all distfiles, or
+ within a category, such as
<filename>/usr/ports/net</filename>, or within the specific
port skeleton. Note that if a port has any dependencies,
running this command in a category or ports skeleton will
<emphasis>not</emphasis> fetch the distfiles of ports from
another category. Instead, use <command>make
- fetch-recursive</command> to
- also fetch the distfiles for all the dependencies of a
- port.</para>
+ fetch-recursive</command> to also fetch the distfiles for
+ all the dependencies of a port.</para>
<para>In rare cases, such as when an organization has a local
distfiles repository, the <varname>MASTER_SITES</varname>
@@ -1245,10 +1242,9 @@ Deinstalling ca_root_nss-3.15.1_1... don
<para>will combine the two.</para>
- <para>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.</para>
-
+ <para>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.</para>
</sect3>
</sect2>
@@ -1313,15 +1309,14 @@ The deinstallation will free 229 kB
attempting an upgrade, read
<filename>/usr/ports/UPDATING</filename> 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.</para>
+ 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.</para>
</important>
<para>To perform the actual upgrade, use either
@@ -1462,9 +1457,9 @@ The deinstallation will free 229 kB
<para>To upgrade only a specified application instead of all
available ports, use <command>portupgrade
- <replaceable>pkgname</replaceable></command>. It is very important to include
- <option>-R</option> to first upgrade all the ports required
- by the given application:</para>
+ <replaceable>pkgname</replaceable></command>. It is very
+ important to include <option>-R</option> to first upgrade
+ all the ports required by the given application:</para>
<screen>&prompt.root; <userinput>portupgrade -R firefox</userinput></screen>
@@ -1472,9 +1467,9 @@ The deinstallation will free 229 kB
<option>-P</option> is included,
<application>Portupgrade</application> searches for
available packages in the local directories listed in
- <envar>PKG_PATH</envar>. If none are available locally,
- it then fetches packages from a remote site. If
- packages can not be found locally or fetched remotely,
+ <envar>PKG_PATH</envar>. If none are available locally, it
+ then fetches packages from a remote site. If packages can
+ not be found locally or fetched remotely,
<application>Portupgrade</application> will use ports. To
avoid using ports entirely, specify <option>-PP</option>.
This last set of options tells
@@ -1545,62 +1540,58 @@ The deinstallation will free 229 kB
<title>Building Packages with
<application>Poudriere</application></title>
- <para><application>Poudriere</application> is a
+ <para><application>Poudriere</application> is a
<acronym>BSD</acronym>-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.</para>
-
- <para><application>Poudriere</application> can be installed
- using the
- <package role="port">ports-mgmt/poudriere</package> package or
- port. The installation will include a sample configuration file
- <filename>/usr/local/etc/poudriere.conf.sample</filename>.
- This file should be copied to
- <filename>/usr/local/etc/poudriere.conf</filename> which can
- then be edited to suit the local configuration.</para>
-
- <para>While <acronym>ZFS</acronym> is not required on the
- system running <application>poudriere</application>,
- it is beneficial. When <acronym>ZFS</acronym> is used, the
- <varname>ZPOOL</varname> must be
- specified in
- <filename>/usr/local/etc/poudriere.conf</filename> and
- <varname>FREEBSD_HOST</varname> should be set to a nearby
- mirror. Defining
- <varname>CCACHE_DIR</varname> enables the use of
- <package role="port">devel/ccache</package> to cache
- compilation and reduce build times for
- frequently-compiled code. It may be convenient to put
- <application>poudriere</application> datasets in an isolated
- tree mounted at
- <filename class="directory">/poudriere</filename>. Defaults
- for the other configuration values are adequate.</para>
-
- <para>The number of processor cores detected is used to define
- how many builds should run in parallel. Supply enough virtual
- memory, either with <acronym>RAM</acronym> or swap space. If
- virtual memory runs out, compiling jails will stop and be torn
- down, resulting in weird error messages.</para>
+ &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.</para>
+
+ <para><application>Poudriere</application> can be installed using
+ the <package role="port">ports-mgmt/poudriere</package> package
+ or port. The installation will include a sample configuration
+ file <filename>/usr/local/etc/poudriere.conf.sample</filename>.
+ This file should be copied to
+ <filename>/usr/local/etc/poudriere.conf</filename> which can
+ then be edited to suit the local configuration.</para>
+
+ <para>While <acronym>ZFS</acronym> is not required on the system
+ running <application>poudriere</application>, it is beneficial.
+ When <acronym>ZFS</acronym> is used, the
+ <varname>ZPOOL</varname> must be specified in
+ <filename>/usr/local/etc/poudriere.conf</filename> and
+ <varname>FREEBSD_HOST</varname> should be set to a nearby
+ mirror. Defining <varname>CCACHE_DIR</varname> enables the use
+ of <package role="port">devel/ccache</package> to cache
+ compilation and reduce build times for frequently-compiled code.
+ It may be convenient to put
+ <application>poudriere</application> datasets in an isolated
+ tree mounted at <filename
+ class="directory">/poudriere</filename>. Defaults for the
+ other configuration values are adequate.</para>
+
+ <para>The number of processor cores detected is used to define how
+ many builds should run in parallel. Supply enough virtual
+ memory, either with <acronym>RAM</acronym> or swap space. If
+ virtual memory runs out, compiling jails will stop and be torn
+ down, resulting in weird error messages.</para>
<sect2 xml:id="poudriere-initialization">
<title>Initialize Jails and Port Trees</title>
<para>Once configured, initialize
<application>poudriere</application> so that it installs a
- jail with the required &os; tree and a
- ports tree. Specify a name for the jail using
- <option>-j</option> and the &os; version with
- <option>-v</option>. On systems running &os;/&arch.amd64;,
- the architecture can be set with <option>-a</option> to
- either <literal>i386</literal> or <literal>amd64</literal>.
- The default is to use the architecture shown by
- <command>uname</command>.</para>
+ jail with the required &os; tree and a ports tree. Specify a
+ name for the jail using <option>-j</option> and the &os;
+ version with <option>-v</option>. On systems running
+ &os;/&arch.amd64;, the architecture can be set with
+ <option>-a</option> to either <literal>i386</literal> or
+ <literal>amd64</literal>. The default is to use the
+ architecture shown by <command>uname</command>.</para>
<screen>&prompt.root; <userinput>poudriere jail -c -j <replaceable>10amd64</replaceable> -v <replaceable>10.0-RELEASE</replaceable></userinput>
====>> Creating 10amd64 fs... done
@@ -1693,8 +1684,9 @@ ports-mgmt/pkg
that can be used with a web server to display build
information.</para>
- <para>Once the build is complete, packages are now available for installation from the
- <application>poudriere</application> repository.</para>
+ <para>Once the build is complete, packages are now available for
+ installation from the <application>poudriere</application>
+ repository.</para>
<para>For more information on using
<application>poudriere</application>, see &man.poudriere.8;
More information about the svn-doc-all
mailing list