svn commit: r42919 - head/en_US.ISO8859-1/books/handbook/ports

Dru Lavigne dru at FreeBSD.org
Wed Oct 9 19:25:45 UTC 2013


Author: dru
Date: Wed Oct  9 19:25:44 2013
New Revision: 42919
URL: http://svnweb.freebsd.org/changeset/doc/42919

Log:
  White space fix only. Translators can ignore.

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  9 19:08:10 2013	(r42918)
+++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml	Wed Oct  9 19:25:44 2013	(r42919)
@@ -1172,20 +1172,21 @@ Deinstalling ca_root_nss-3.15.1_1... don
 	  include <filename role="package">www/firefox</filename>,
 	  <filename role="package">security/gpgme</filename>, and
 	  <filename role="package">mail/sylpheed-claws</filename>.
-	  If the port depends upon other ports which have configurable 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
-	    <maketarget>config-recursive</maketarget></command> within the port skeleton to do
-	  this configuration in one batch.  Then, run <command>make
+	  If the port depends upon other ports which have configurable
+	  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
+	    <maketarget>config-recursive</maketarget></command>
+	  within the port skeleton to do this configuration in one
+	  batch.  Then, run <command>make
 	    <maketarget>install [clean]</maketarget></command> to
 	  compile and install the port.</para>
 
 	<tip>
 	  <para>When using <maketarget>config-recursive</maketarget>,
 	    the list of ports to configure are gathered by the
-	    <maketarget>all-depends-list</maketarget>
-	    target.  It is recommended to run <command>make
+	    <maketarget>all-depends-list</maketarget> target.  It is
+	    recommended to run <command>make
 	      <maketarget>config-recursive</maketarget></command>
 	    until all dependent ports options have been defined, and
 	    ports options screens no longer appear, to be certain
@@ -1345,9 +1346,9 @@ The deinstallation will free 229 kB
 	  the upgrade.</para>
       </important>
 
-	<para>To perform the actual upgrade, use either
-	  <application>Portmaster</application> or
-	  <application>Portupgrade</application>.</para>
+      <para>To perform the actual upgrade, use either
+	<application>Portmaster</application> or
+	<application>Portupgrade</application>.</para>
 
       <sect3 id="portmaster">
 	<title>Upgrading Ports Using
@@ -1359,39 +1360,39 @@ The deinstallation will free 229 kB
 
 	<para>The <filename
 	    role="package">ports-mgmt/portmaster</filename>
-	  package or port is the recommended tool for upgrading installed ports
-	  as it is designed to
-	  use the tools installed with &os;
-	  without depending upon other ports.  It uses the information
-	  in <filename class="directory">/var/db/pkg/</filename> to
-	  determine which ports to upgrade.  To install this utility
-	  as a port:</para>
+	  package or port is the recommended tool for upgrading
+	  installed ports as it is designed to use the tools installed
+	  with &os; without depending upon other ports.  It uses the
+	  information in <filename
+	    class="directory">/var/db/pkg/</filename> to determine
+	  which ports to upgrade.  To install this utility as a
+	  port:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/ports-mgmt/portmaster</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
-	<para><application>Portmaster</application> defines
-	  four categories of ports:</para>
+	<para><application>Portmaster</application> defines four
+	  categories of ports:</para>
 
 	<itemizedlist>
 	  <listitem>
-	    <para>Root port: has no dependencies and is not a dependency of
-	      any other ports.</para>
+	    <para>Root port: has no dependencies and is not a
+	      dependency of any other ports.</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>Trunk port: has no dependencies, but other ports depend
-	      upon it.</para>
+	    <para>Trunk port: has no dependencies, but other ports
+	      depend upon it.</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>Branch port: has dependencies and other ports depend
-	      upon it.</para>
+	    <para>Branch port: has dependencies and other ports
+	      depend upon it.</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>Leaf port: has dependencies but no other ports depend
-	      upon it.</para>
+	    <para>Leaf port: has dependencies but no other ports
+	      depend upon it.</para>
 	  </listitem>
 	</itemizedlist>
 
@@ -1419,7 +1420,8 @@ The deinstallation will free 229 kB
 ===>>> 137 total installed ports
         ===>>> 83 have new versions available</screen>
 
-	<para>This command is used to upgrade all outdated ports:</para>
+	<para>This command is used to upgrade all outdated
+	  ports:</para>
 
 	<screen>&prompt.root; <userinput>portmaster -a</userinput></screen>
 
@@ -1432,14 +1434,15 @@ The deinstallation will free 229 kB
 	    <application>Portmaster</application> not to automatically
 	    delete the backup.  Adding <option>-i</option> will start
 	    <application>Portmaster</application> in interactive mode,
-	    prompting for confirmation before upgrading each
-	    port.  Many other options are available.  Read through
-	    the manual page for portmaster(8) for details regarding
+	    prompting for confirmation before upgrading each port.
+	    Many other options are available.  Read through the
+	    manual page for portmaster(8) for details regarding
 	    their usage.</para>
 	</note>
 
-	<para>If errors are encountered during the upgrade process, add
-	  <option>-f</option> to upgrade and rebuild all ports:</para>
+	<para>If errors are encountered during the upgrade process,
+	  add <option>-f</option> to upgrade and rebuild all
+	  ports:</para>
 
 	<screen>&prompt.root; <userinput>portmaster -af</userinput></screen>
 
@@ -1450,9 +1453,9 @@ The deinstallation will free 229 kB
 	  port in the Ports Collection:</para>
 
 	<screen>&prompt.root; <userinput>portmaster <replaceable>shells/bash</replaceable></userinput></screen>
-	</sect3>
+      </sect3>
 
-	<sect3 id="portupgrade">
+      <sect3 id="portupgrade">
 	<title>Upgrading Ports Using Portupgrade</title>
 
 	<indexterm>
@@ -1461,46 +1464,48 @@ The deinstallation will free 229 kB
 
 	<para>Another utility that can be used to upgrade ports is
 	  <application>Portupgrade</application>, which is
-	  available
-	  as the <filename
-	    role="package">ports-mgmt/portupgrade</filename> package or port.
-	  This utility installs a suite of applications which can be
-	  used to manage ports.  However, it is dependent upon Ruby.
-	  To install the port:</para>
+	  available as the <filename
+	    role="package">ports-mgmt/portupgrade</filename> package
+	  or port.  This utility installs a suite of applications
+	  which can be used to manage ports.  However, it is dependent
+	  upon Ruby.  To install the port:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/ports-mgmt/portupgrade</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
 	<para>Before performing an upgrade using this utility, it is
 	  recommended to scan the list of installed ports using
-	  <command>pkgdb -F</command> and to fix all the inconsistencies
-	  it reports.</para>
+	  <command>pkgdb -F</command> and to fix all the
+	  inconsistencies it reports.</para>
 
-	<para>To upgrade all the
-	  outdated ports installed on the system, use <command>portupgrade -a</command>.  Alternately, include
-	  <option>-i</option> to be asked for confirmation of every
-	  individual upgrade:</para>
+	<para>To upgrade all the outdated ports installed on the
+	  system, use <command>portupgrade -a</command>.  Alternately,
+	  include <option>-i</option> to be asked for confirmation
+	  of every individual upgrade:</para>
 
 	<screen>&prompt.root; <userinput>portupgrade -ai</userinput></screen>
 
 	<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>
 
 	<para>If
 	  <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
+	  <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,
 	  <application>Portupgrade</application> will use ports.  To
 	  avoid using ports entirely, specify <option>-PP</option>.
-	  This last set of options tells <application>Portupgrade</application>
-	  to abort if no packages are available:</para>
+	  This last set of options tells
+	  <application>Portupgrade</application> to abort if no
+	  packages are available:</para>
 
 	<screen>&prompt.root; <userinput>portupgrade -PP gnome2</userinput></screen>
 
@@ -1510,7 +1515,7 @@ The deinstallation will free 229 kB
 	  information on all of the available switches, refer to the
 	  manual page for <command>portupgrade</command>.</para>
       </sect3>
-      </sect2>
+    </sect2>
 
     <sect2 id="ports-disk-space">
       <title>Ports and Disk Space</title>
@@ -1521,33 +1526,37 @@ The deinstallation will free 229 kB
       </indexterm>
 
       <para>Using the Ports Collection will use up disk space over
-	time.  After building and installing a port, running <command>make
-	<maketarget>clean</maketarget></command> within the ports skeleton will clean up the
-	temporary <filename class="directory">work</filename>
-	directory.  If <application>Portmaster</application> is used
-	to install a port, it will automatically remove this directory
-	unless <option>-K</option> is specified.  If
-	<application>Portupgrade</application> is installed, this command
-	will remove all <filename class="directory">work</filename>
-	directories found within the local copy of the Ports
-	Collection:</para>
+	time.  After building and installing a port, running
+	<command>make <maketarget>clean</maketarget></command>
+	within the ports skeleton will clean up the temporary
+	<filename class="directory">work</filename> directory.  If
+	<application>Portmaster</application> is used to install a
+	port, it will automatically remove this directory unless
+	<option>-K</option> is specified.  If
+	<application>Portupgrade</application> is installed, this
+	command will remove all <filename
+	  class="directory">work</filename> directories found within
+	the local copy of the Ports Collection:</para>
 
       <screen>&prompt.root; <userinput>portsclean -C</userinput></screen>
 
-      <para>In addition, a lot of out-dated source distribution files will collect
-	in <filename class="directory">/usr/ports/distfiles</filename> over time.
+      <para>In addition, a lot of out-dated source distribution files
+	will collect in <filename
+	  class="directory">/usr/ports/distfiles</filename> over time.
 	If <application>Portupgrade</application> is installed, this
-	command will delete all the distfiles that are
-	no longer referenced by any ports:</para>
+	command will delete all the distfiles that are no longer
+	referenced by any ports:</para>
 
       <screen>&prompt.root; <userinput>portsclean -D</userinput></screen>
 
-      <para>To use <application>Portupgrade</application> to remove all distfiles not referenced by any port
-	currently installed on the system:</para>
+      <para>To use <application>Portupgrade</application> to remove
+	all distfiles not referenced by any port currently installed
+	on the system:</para>
 
       <screen>&prompt.root; <userinput>portsclean -DD</userinput></screen>
 
-      <para>If <application>Portmaster</application> is installed, use:</para>
+      <para>If <application>Portmaster</application> is installed,
+	use:</para>
 
       <screen>&prompt.root; <userinput>portmaster --clean-distfiles</userinput></screen>
 
@@ -1555,9 +1564,9 @@ The deinstallation will free 229 kB
 	the user to confirm if a distfile should be deleted.</para>
 
       <para>In addition to these commands, the <filename
-	  role="package">ports-mgmt/pkg_cutleaves</filename> package or port automates
-	the task of removing installed ports that are no longer
-	needed.</para>
+	  role="package">ports-mgmt/pkg_cutleaves</filename> package
+	or port automates the task of removing installed ports that
+	are no longer needed.</para>
     </sect2>
   </sect1>
 
@@ -1623,15 +1632,16 @@ The deinstallation will free 229 kB
       <listitem>
 	<para>Search to see if there is a fix pending for the port in
 	  the <ulink url="&url.base;/support.html#gnats">Problem
-	    Report database</ulink>.  If so, implementing the proposed fix may
-	  fix the issue.</para>
+	    Report database</ulink>.  If so, implementing the proposed
+	  fix may fix the issue.</para>
       </listitem>
 
       <listitem>
 	<para>Ask the maintainer of the port for help.  Type
 	  <command>make <maketarget>maintainer</maketarget></command>
-	  in the ports skeleton or read the port's <filename>Makefile</filename> to find the
-	  maintainer's email address.  Remember to include the
+	  in the ports skeleton or read the port's
+	  <filename>Makefile</filename> to find the maintainer's
+	  email address.  Remember to include the
 	  <literal>$FreeBSD:</literal> line from the port's
 	  <filename>Makefile</filename> and the output leading up to
 	  the error in the email to the maintainer.</para>
@@ -1639,21 +1649,23 @@ The deinstallation will free 229 kB
 	<note>
 	  <para>Some ports are not maintained by an individual but
 	    instead by a <ulink
-	    url="&url.articles.mailing-list-faq;/article.html">mailing
-	    list</ulink>.  Many, but not all, of these addresses look
-	    like <email
+	      url="&url.articles.mailing-list-faq;/article.html">mailing
+	      list</ulink>.  Many, but not all, of these addresses
+	    look like <email
 	      role="nolink">freebsd-listname at FreeBSD.org</email>.
 	    Take this into account when sending an email.</para>
 
-	  <para>In particular, ports shown as maintained by
-	    <email role="nolink">ports at FreeBSD.org</email> are
-	    not maintained by a specific individual.  Instead, any fixes and support
-	    come from the general community who subscribe to that
-	    mailing list.  More volunteers are always needed!</para>
+	  <para>In particular, ports shown as maintained by <email
+	      role="nolink">ports at FreeBSD.org</email> are not
+	    maintained by a specific individual.  Instead, any fixes
+	    and support come from the general community who subscribe
+	    to that mailing list.  More volunteers are always
+	    needed!</para>
 	</note>
 
-	<para>If there is no response to the email, use &man.send-pr.1; to
-	  submit a bug report using the instructions in <ulink
+	<para>If there is no response to the email, use
+	  &man.send-pr.1; to submit a bug report using the
+	  instructions in <ulink
 	    url="&url.articles.problem-reports;/article.html">Writing
 	    &os; Problem Reports</ulink>.</para>
       </listitem>
@@ -1667,10 +1679,9 @@ The deinstallation will free 229 kB
       </listitem>
 
       <listitem>
-	<para>Install the package instead of the port using the instructions in
-	  <xref
-	  linkend="packages-using"/> or <xref
-	  linkend="pkgng-intro"/>.</para>
+	<para>Install the package instead of the port using the
+	  instructions in <xref linkend="packages-using"/> or <xref
+	    linkend="pkgng-intro"/>.</para>
       </listitem>
     </orderedlist>
   </sect1>


More information about the svn-doc-all mailing list