ports-using.html

FreeBSD安装说明概述 FreeBSD 提供了一个以文字为主

<samp class="PROMPT">#</samp>
</pre>

<p>Notice that once the compile is complete you are returned to your prompt. The next
step is to install the port. In order to install it, you simply need to tack one word
onto the <tt class="COMMAND">make</tt> command, and that word is <tt
class="COMMAND">install</tt>:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make install</kbd>
===&gt;  Installing for lsof-4.57
...
[installation output snipped]
...
===&gt;   Generating temporary packing list
===&gt;   Compressing manual pages for lsof-4.57
===&gt;   Registering installation for lsof-4.57
===&gt;  SECURITY NOTE: 
      This port has installed the following binaries which execute with
      increased privileges.
<samp class="PROMPT">#</samp>
</pre>

<p>Once you are returned to your prompt, you should be able to run the application you
just installed. Since <tt class="COMMAND">lsof</tt> is a program that runs with increased
privileges, a security warning is shown. During the building and installation of ports,
you should take heed of any other warnings that may appear.</p>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> You can save an extra step by just running <tt class="COMMAND">make
install</tt> instead of <tt class="COMMAND">make</tt> and <tt class="COMMAND">make
install</tt> as two separate steps.</p>
</blockquote>
</div>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Some shells keep a cache of the commands that are available in the
directories listed in the <tt class="ENVAR">PATH</tt> environment variable, to speed up
lookup operations for the executable file of these commands. If you are using one of
these shells, you might have to use the <tt class="COMMAND">rehash</tt> command after
installing a port, before the newly installed commands can be used. This is true for both
shells that are part of the base-system (such as <tt class="COMMAND">tcsh</tt>) and
shells that are available as ports (for instance, <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/shells/zsh/pkg-descr"><tt
class="FILENAME">shells/zsh</tt></a>).</p>
</blockquote>
</div>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Please be aware that the licenses of a few ports do not allow for
inclusion on the CD-ROM. This could be because a registration form needs to be filled out
before downloading or redistribution is not allowed, or for another reason. If you wish
to install a port not included on the CD-ROM, you will need to be online in order to do
so (see the <a href="ports-using.html#PORTS-INET">next section</a>).</p>
</blockquote>
</div>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="PORTS-INET" name="PORTS-INET">4.5.2.2. Installing Ports from the
Internet</a></h3>

<p>As with the last section, this section makes an assumption that you have a working
Internet connection. If you do not, you will need to perform the <a
href="ports-using.html#PORTS-CD">CD-ROM installation</a>, or put a copy of the distfile
into <tt class="FILENAME">/usr/ports/distfiles</tt> manually.</p>

<p>Installing a port from the Internet is done exactly the same way as it would be if you
were installing from a CD-ROM. The only difference between the two is that the distfile
is downloaded from the Internet instead of read from the CD-ROM.</p>

<p>The steps involved are identical:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make install</kbd>
&gt;&gt; lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
&gt;&gt; Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
439860 bytes transferred in 18.0 seconds (23.90 kBps)
===&gt;  Extracting for lsof-4.57
...
[extraction output snipped]
...
&gt;&gt; Checksum OK for lsof_4.57D.freebsd.tar.gz.
===&gt;  Patching for lsof-4.57
===&gt;  Applying FreeBSD patches for lsof-4.57
===&gt;  Configuring for lsof-4.57
...
[configure output snipped]
...
===&gt;  Building for lsof-4.57
...
[compilation output snipped]
...
===&gt;  Installing for lsof-4.57
...
[installation output snipped]
...
===&gt;   Generating temporary packing list
===&gt;   Compressing manual pages for lsof-4.57
===&gt;   Registering installation for lsof-4.57
===&gt;  SECURITY NOTE: 
      This port has installed the following binaries which execute with
      increased privileges.
<samp class="PROMPT">#</samp>
</pre>

<p>As you can see, the only difference is the line that tells you where the system is
fetching the port distfile from.</p>

<p>The ports system uses <span class="CITEREFENTRY"><span
class="REFENTRYTITLE">fetch</span>(1)</span> to download the files, which honors various
environment variables, including <tt class="ENVAR">FTP_PASSIVE_MODE</tt>, <tt
class="ENVAR">FTP_PROXY</tt>, and <tt class="ENVAR">FTP_PASSWORD</tt>. You may need to
set one or more of these if you are behind a firewall, or need to use an FTP/HTTP proxy.
See <span class="CITEREFENTRY"><span class="REFENTRYTITLE">fetch</span>(3)</span> for the
complete list.</p>

<p>For users which cannot be connected all the time, the <tt class="COMMAND">make <tt
class="MAKETARGET">fetch</tt></tt> option is provided. Just run this command at the top
level directory (<tt class="FILENAME">/usr/ports</tt>) and the required files will be
downloaded for you. This command will also work in the lower level categories, for
example: <tt class="FILENAME">/usr/ports/net</tt>. Note that if a port depends on
libraries or other ports this will <span class="emphasis"><i
class="EMPHASIS">not</i></span> fetch the distfiles of those ports too. Replace <tt
class="MAKETARGET">fetch</tt> with <tt class="MAKETARGET">fetch-recursive</tt> if you
want to fetch all the dependencies of a port too.</p>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> You can build all the ports in a category or as a whole by running <tt
class="COMMAND">make</tt> in the top level directory, just like the aforementioned <tt
class="COMMAND">make <tt class="MAKEVAR">fetch</tt></tt> method. This is dangerous,
however, as some ports cannot co-exist. In other cases, some ports can install two
different files with the same filename.</p>
</blockquote>
</div>

<p>In some rare cases, users may need to acquire the tarballs from a site other than the
<tt class="MAKEVAR">MASTER_SITES</tt> (the location where files are downloaded from). You
can override the <tt class="MAKEVAR">MASTER_SITES</tt> option with the following
command:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /usr/ports/<var
class="REPLACEABLE">directory</var></kbd>
</pre>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make MASTER_SITE_OVERRIDE= \
    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</kbd>
</pre>

<p>In this example we change the <tt class="MAKEVAR">MASTER_SITES</tt> option to <tt
class="HOSTID">ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/</tt>.</p>

<div class="NOTE">
<blockquote class="NOTE">
<p><b>Note:</b> Some ports allow (or even require) you to provide build options which can
enable/disable parts of the application which are unneeded, certain security options, and
other customizations. A few which come to mind are <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/www/mozilla/pkg-descr"><tt
class="FILENAME">www/mozilla</tt></a>, <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/security/gpgme/pkg-descr"><tt
class="FILENAME">security/gpgme</tt></a>, and <a
href="http://www.FreeBSD.org/cgi/url.cgi?ports/mail/sylpheed-claws/pkg-descr"><tt
class="FILENAME">mail/sylpheed-claws</tt></a>. A message will be displayed when options
such as these are available.</p>
</blockquote>
</div>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="AEN5670" name="AEN5670">4.5.2.3. Overriding the Default Ports
Directories</a></h3>

<p>Sometimes it is useful (or mandatory) to use a different distfiles and ports
directory. The <tt class="MAKEVAR">PORTSDIR</tt> and <tt class="MAKEVAR">PREFIX</tt>
variables can override the default directories. For example:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">make PORTSDIR=/usr/home/example/ports install</kbd>
</pre>

<p>will compile the port in <tt class="FILENAME">/usr/home/example/ports</tt> and install
everything under <tt class="FILENAME">/usr/local</tt>.</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">make PREFIX=/usr/home/example/local install</kbd>
</pre>

<p>will compile it in <tt class="FILENAME">/usr/ports</tt> and install it in <tt
class="FILENAME">/usr/home/example/local</tt>.</p>

<p>And of course,</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd
class="USERINPUT">make PORTSDIR=../ports PREFIX=../local install</kbd>
</pre>

<p>will combine the two (it is too long to completely write on this page, but it should
give you the general idea).</p>

<p>Alternatively, these variables can also be set as part of your environment. Read the
manual page for your shell for instructions on doing so.</p>
</div>

<div class="SECT3">
<h3 class="SECT3"><a id="AEN5693" name="AEN5693">4.5.2.4. Dealing with <tt
class="COMMAND">imake</tt></a></h3>

<p>Some ports that use <tt class="COMMAND">imake</tt> (a part of the X Windows System) do
not work well with <tt class="MAKEVAR">PREFIX</tt>, and will insist on installing under
<tt class="FILENAME">/usr/X11R6</tt>. Similarly, some Perl ports ignore <tt
class="MAKEVAR">PREFIX</tt> and install in the Perl tree. Making these ports respect <tt
class="MAKEVAR">PREFIX</tt> is a difficult or impossible job.</p>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="PORTS-REMOVING" name="PORTS-REMOVING">4.5.3. Removing Installed
Ports</a></h2>

<p>Now that you know how to install ports, you are probably wondering how to remove them,
just in case you install one and later on decide that you installed the wrong port. We
will remove our previous example (which was <tt class="COMMAND">lsof</tt> for those of
you not paying attention). As with installing ports, the first thing you must do is
change to the port directory, <tt class="FILENAME">/usr/ports/sysutils/lsof</tt>. After
you change directories, you are ready to uninstall <tt class="COMMAND">lsof</tt>. This is
done with the <tt class="COMMAND">make deinstall</tt> command:</p>

<pre class="SCREEN">
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">cd /usr/ports/sysutils/lsof</kbd>
<samp class="PROMPT">#</samp> <kbd class="USERINPUT">make deinstall</kbd>
===&gt;  Deinstalling for lsof-4.57
</pre>

<p>That was easy enough. You have removed <tt class="COMMAND">lsof</tt> from your system.
If you would like to reinstall it, you can do so by running <tt class="COMMAND">make
reinstall</tt> from the <tt class="FILENAME">/usr/ports/sysutils/lsof</tt> directory.</p>

<p>The <tt class="COMMAND">make deinstall</tt> and <tt class="COMMAND">make
reinstall</tt> sequence does not work once you have run <tt class="COMMAND">make
clean</tt>. If you want to deinstall a port after cleaning, use <span
class="CITEREFENTRY"><span class="REFENTRYTITLE">pkg_delete</span>(1)</span> as discussed
in the <a href="packages-using.html">Packages section of the Handbook</a>.</p>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="PORTS-DISK-SPACE" name="PORTS-DISK-SPACE">4.5.4. Ports and Disk
Space</a></h2>

<p>Using the ports collection can defiantly eat up your disk space. For this reason you
should always remember to clean up the work directories using the <tt
class="COMMAND">make <tt class="MAKEVAR">clean</tt></tt> option. This will remove the <tt
class="FILENAME">work</tt> directory after a port has been built, and installed. You can
also remove the tar files from the <tt class="FILENAME">distfiles</tt> directory, and
remove the installed ports when their use has delimited.</p>

<p>Some users choose to limit the port categories by placing an entry in the <tt
class="FILENAME">refuse</tt> file. This way when they run the <b
class="APPLICATION">CVSup</b> application, it will not download the files in that
category.</p>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="PORTS-UPGRADING" name="PORTS-UPGRADING">4.5.5. Upgrading
Ports</a></h2>

<p>Keeping your ports up to date can be a tedious job. For instance, to upgrade a port
you would go to the ports directory, build the port, deinstall the old port, install the
new port, and then clean up after the build. Imagine doing that for five ports, tedious
right? This was a large problem for system administrators to deal with, and now we have
utilities which do this for us. For instance the <tt
class="FILENAME">sysutils/portupgrade</tt> utility will do everything for you! Just
install it like you would any other port, using the <tt class="COMMAND">make <tt
class="MAKEVAR">install clean</tt></tt> command.</p>

<p>Now create a database with the <tt class="COMMAND">pkgdb -F</tt> command. This will
read the list of installed ports and create a database file in the <tt
class="FILENAME">/var/db/pkg</tt> directory. Now when you run <tt
class="COMMAND">portupgrade -a</tt>, it will read this and the ports <tt
class="FILENAME">INDEX</tt> file. Finally, <tt class="COMMAND">portupgrade</tt> will
begin to download, build, backup, install, and clean the ports which have been updated.
Other utilities exist which will do this, check out the <tt
class="FILENAME">ports/sysutils</tt> directory and see what you come up with.</p>
</div>
</div>

<div class="NAVFOOTER">
<hr align="LEFT" width="100%" />
<table summary="Footer navigation table" width="100%" border="0" cellpadding="0"
cellspacing="0">
<tr>
<td width="33%" align="left" valign="top"><a href="packages-using.html"
accesskey="P">Prev</a></td>
<td width="34%" align="center" valign="top"><a href="index.html"
accesskey="H">Home</a></td>
<td width="33%" align="right" valign="top"><a href="ports-nextsteps.html"
accesskey="N">Next</a></td>
</tr>

<tr>
<td width="33%" align="left" valign="top">使用package系统</td>
<td width="34%" align="center" valign="top"><a href="ports.html"
accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Post-installation Activities</td>
</tr>
</table>
</div>
</body>
</html>