os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Fix some long lines, which slept in in my previous commit. While here,

Browse source 
cut some other long lines and put a missing comma.
This commit is contained in:
Gabor Kovesdan 2008-04-27 12:19:23 +00:00
parent 6eb9277a95
commit d9c08023ec
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=31920
1 changed files with 49 additions and 40 deletions

89
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -341,8 +341,8 @@ R-deps: </screen>
will not be covered here.</para>
<para>For more in-depth searching you can also use <command>make
<maketarget>search</maketarget> key=<replaceable>string</replaceable></command> where
<replaceable>string</replaceable> is some text to search for.
<maketarget>search</maketarget> key=<replaceable>string</replaceable></command>
where <replaceable>string</replaceable> is some text to search for.
This searches port names, comments, descriptions and
dependencies and can be used to find ports which relate to a
particular subject if you do not know the name of the program
@ -622,16 +622,17 @@ docbook =
<title>CVSup Method</title>
<para>This is a quick method for getting and keeping your copy of the
Ports Collection up to date using <application>CVSup</application> protocol.
If you want to learn more about <application>CVSup</application>, see
<link linkend="cvsup">Using CVSup</link>.</para>
Ports Collection up to date using <application>CVSup</application>
protocol. If you want to learn more about
<application>CVSup</application>, see <link
linkend="cvsup">Using CVSup</link>.</para>
<note>
<para>The implementation of <application>CVSup</application> protocol
included with the &os; system is called <application>csup</application>.
It first appeared in &os; 6.2. Users of older &os; releases can install
it via the <filename role="package">net/csup</filename>
port/package.</para>
included with the &os; system is called
<application>csup</application>. It first appeared in &os; 6.2.
Users of older &os; releases can install it via the <filename
role="package">net/csup</filename> port/package.</para>
</note>
<para>Make sure <filename role="directory">/usr/ports</filename>
@ -691,8 +692,8 @@ docbook =
</step>
<step>
<para>Running the &man.csup.1; command later will download and apply all
the recent changes to your Ports Collection, except
<para>Running the &man.csup.1; command later will download and apply
all the recent changes to your Ports Collection, except
actually rebuilding the ports for your own system.</para>
</step>
</procedure>
@ -700,10 +701,10 @@ docbook =
<procedure>
<title>Portsnap Method</title>
<para><application>Portsnap</application> is an alternative system for distributing the
Ports Collection. It was first included in &os;&nbsp;6.0. On older
systems, you can install it from <filename
role="package">ports-mgmt/portsnap</filename> package:</para>
<para><application>Portsnap</application> is an alternative system for
distributing the Ports Collection. It was first included in
&os;&nbsp;6.0. On older systems, you can install it from <filename
role="package">ports-mgmt/portsnap</filename> package:</para>
<screen>&prompt.root; <userinput>pkg_add -r portsnap</userinput></screen>
@ -720,7 +721,8 @@ docbook =
With previous versions of
<application>Portsnap</application>, you will have to
create an empty directory <filename
role="directory">/usr/ports</filename> if it does not exists:</para>
role="directory">/usr/ports</filename> if it does not
exists:</para>
<screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
</step>
@ -981,8 +983,10 @@ docbook =
<note>
<para>You can save two extra steps by just running <command>make
<maketarget>install clean</maketarget></command> instead of <command>make</command>,
<command>make <maketarget>install</maketarget></command> and <command>make <maketarget>clean</maketarget></command>
<maketarget>install clean</maketarget></command> instead of
<command>make</command>,
<command>make <maketarget>install</maketarget></command> and
<command>make <maketarget>clean</maketarget></command>
as three separate steps.</para>
</note>
@ -1129,14 +1133,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
remove, or change these options after a port has been built. There
are many ways to do this. One option is to go into the directory
containing the port and type <command>make
<maketarget>config</maketarget></command>, which will simply present the menu
again with the same options selected. Another option is to use
<command>make <maketarget>showconfig</maketarget></command> which
will show you all the configuration options for the port. Yet
<maketarget>config</maketarget></command>, which will simply present
the menu again with the same options selected. Another option is to
use <command>make <maketarget>showconfig</maketarget></command>,
which will show you all the configuration options for the port. Yet
another option is to execute <command>make
<maketarget>rmconfig</maketarget></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 in the man page for
<maketarget>rmconfig</maketarget></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 in the man page for
&man.ports.7;.</para>
</sect3>
</sect2>
@ -1253,7 +1257,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<para><application>Portmanager</application> is another utility for
easy upgrading of installed ports. It is available from the
<filename role="package">ports-mgmt/portmanager</filename> port:</para>
<filename role="package">ports-mgmt/portmanager</filename>
port:</para>
<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/ports-mgmt/portmanager</filename></userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
@ -1267,9 +1272,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
confirmation of every step <application>Portmanager</application>
will perform. <application>Portmanager</application> can also be
used to install new ports on the system. Unlike the usual
<command>make <maketarget>install clean</maketarget></command> command, it will upgrade all
the dependencies prior to building and installing the
selected port.</para>
<command>make <maketarget>install clean</maketarget></command>
command, it will upgrade all the dependencies prior to building and
installing the selected port.</para>
<screen>&prompt.root; <userinput>portmanager <replaceable>x11/gnome2</replaceable></userinput></screen>
@ -1296,7 +1301,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
system (it does not depend upon other ports) and uses the
information in <filename class="directory">/var/db/pkg/</filename>
to determine which ports to upgrade. It is available from the
<filename role="package">ports-mgmt/portmaster</filename> port:</para>
<filename role="package">ports-mgmt/portmaster</filename>
port:</para>
<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/ports-mgmt/portmaster</filename></userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
@ -1385,9 +1391,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<para>Using the Ports Collection will use up disk
space over time. After building and installing software from the
ports, you should always remember to clean up
the temporary <filename class="directory">work</filename> directories using the <command>make
<maketarget>clean</maketarget></command> command. You can sweep the whole
Ports Collection with the following command:</para>
the temporary <filename class="directory">work</filename> directories
using the <command>make <maketarget>clean</maketarget></command>
command. You can sweep the whole Ports Collection with the following
command:</para>
<screen>&prompt.root; <userinput>portsclean -C</userinput></screen>
@ -1411,7 +1418,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<para>Do not forget to remove the installed ports once you no longer need
them. A nice tool to help automate this task is available from the
<filename role="package">ports-mgmt/pkg_cutleaves</filename> port.</para>
<filename role="package">ports-mgmt/pkg_cutleaves</filename>
port.</para>
</sect2>
</sect1>
@ -1503,8 +1511,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<listitem>
<para>Ask the maintainer of the port for help. Type
<command>make <maketarget>maintainer</maketarget></command> or read the
<filename>Makefile</filename> to find the maintainer's
<command>make <maketarget>maintainer</maketarget></command> or read
the <filename>Makefile</filename> to find the maintainer's
email address. Remember to include the name and version
of the port (send the <literal>&dollar;FreeBSD:</literal>
line from the <filename>Makefile</filename>) and the
@ -1516,8 +1524,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
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 role="nolink">freebsd-listname@FreeBSD.org</email>. Please
take this into account when phrasing your questions.</para>
<email role="nolink">freebsd-listname@FreeBSD.org</email>.
Please take this into account when phrasing your
questions.</para>
<para>In particular, ports shown as maintained by
<email role="nolink">freebsd-ports@FreeBSD.org</email> are
@ -1537,8 +1546,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<para>Fix it! The <ulink
url="&url.books.porters-handbook;/index.html">Porter's
Handbook</ulink> includes detailed information on the
<quote>Ports</quote> infrastructure so that you can fix the occasional
broken port or even submit your own!</para>
<quote>Ports</quote> infrastructure so that you can fix the
occasional broken port or even submit your own!</para>
</listitem>
<listitem>