Annotation of htdocs/docs/pkgsrc/using.html, revision 1.35

1.25      sevan       1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
1.1       dsieger     2: <html>
                      3: <head>
                      4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.33      rillig      5: <title>Chapter 5. Using pkgsrc</title>
1.12      spz         6: <link rel="stylesheet" type="text/css" href="/global.css">
1.1       dsieger     7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
1.9       rillig      8: <link rel="home" href="index.html" title="The pkgsrc guide">
1.1       dsieger     9: <link rel="up" href="users-guide.html" title="Part I. The pkgsrc user's guide">
1.33      rillig     10: <link rel="prev" href="platforms.html" title="Chapter 4. Using pkgsrc on systems other than NetBSD">
                     11: <link rel="next" href="configuring.html" title="Chapter 6. Configuring pkgsrc">
1.1       dsieger    12: </head>
                     13: <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
                     14: <div class="navheader">
                     15: <table width="100%" summary="Navigation header">
1.33      rillig     16: <tr><th colspan="3" align="center">Chapter 5. Using pkgsrc</th></tr>
1.1       dsieger    17: <tr>
                     18: <td width="20%" align="left">
                     19: <a accesskey="p" href="platforms.html">Prev</a> </td>
                     20: <th width="60%" align="center">Part I. The pkgsrc user's guide</th>
                     21: <td width="20%" align="right"> <a accesskey="n" href="configuring.html">Next</a>
                     22: </td>
                     23: </tr>
                     24: </table>
                     25: <hr>
                     26: </div>
1.14      asau       27: <div class="chapter">
1.1       dsieger    28: <div class="titlepage"><div><div><h2 class="title">
1.33      rillig     29: <a name="using"></a>Chapter 5. Using pkgsrc</h2></div></div></div>
1.1       dsieger    30: <div class="toc">
                     31: <p><b>Table of Contents</b></p>
1.22      leot       32: <dl class="toc">
1.33      rillig     33: <dt><span class="sect1"><a href="using.html#using-pkg">5.1. Using binary packages</a></span></dt>
1.1       dsieger    34: <dd><dl>
1.33      rillig     35: <dt><span class="sect2"><a href="using.html#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
                     36: <dt><span class="sect2"><a href="using.html#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
                     37: <dt><span class="sect2"><a href="using.html#using.pkg_delete">5.1.3. Deinstalling packages</a></span></dt>
                     38: <dt><span class="sect2"><a href="using.html#using.pkg_info">5.1.4. Getting information about installed packages</a></span></dt>
                     39: <dt><span class="sect2"><a href="using.html#vulnerabilities">5.1.5. Checking for security vulnerabilities in installed packages</a></span></dt>
                     40: <dt><span class="sect2"><a href="using.html#pkg_versions">5.1.6. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
                     41: <dt><span class="sect2"><a href="using.html#using.pkg_admin">5.1.7. Other administrative functions</a></span></dt>
1.1       dsieger    42: </dl></dd>
1.33      rillig     43: <dt><span class="sect1"><a href="using.html#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.1       dsieger    44: <dd><dl>
1.33      rillig     45: <dt><span class="sect2"><a href="using.html#requirements">5.2.1. Requirements</a></span></dt>
                     46: <dt><span class="sect2"><a href="using.html#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
                     47: <dt><span class="sect2"><a href="using.html#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.1       dsieger    48: </dl></dd>
                     49: </dl>
                     50: </div>
                     51: <p>Basically, there are two ways of using pkgsrc. The first
                     52: is to only install the package tools and to use binary packages
1.11      wiz        53: that someone else has prepared. This is the <span class="quote">&#8220;<span class="quote">pkg</span>&#8221;</span>
                     54: in pkgsrc. The second way is to install the <span class="quote">&#8220;<span class="quote">src</span>&#8221;</span>
1.1       dsieger    55: of pkgsrc, too. Then you are able to build your own packages,
                     56: and you can still use binary packages from someone else.</p>
1.14      asau       57: <div class="sect1">
1.1       dsieger    58: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.33      rillig     59: <a name="using-pkg"></a>5.1. Using binary packages</h2></div></div></div>
1.32      sevan      60: <p>On the <a class="ulink" href="https://cdn.NetBSD.org/" target="_top">cdn.NetBSD.org</a>
                     61:   site and mirrors, there are collections of binary packages,
1.5       rillig     62:   ready to be installed. These binary packages have been built using the
                     63:   default settings for the directories, that is:</p>
1.14      asau       64: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.11      wiz        65: <li class="listitem"><p><code class="filename">/usr/pkg</code> for <code class="varname">LOCALBASE</code>, where most of the files are installed,</p></li>
                     66: <li class="listitem"><p><code class="filename">/usr/pkg/etc</code> for configuration files,</p></li>
                     67: <li class="listitem"><p><code class="filename">/var</code> for <code class="varname">VARBASE</code>, where those files are installed that may change after installation.</p></li>
1.5       rillig     68: </ul></div>
                     69: <p>If you cannot use these directories for whatever reasons (maybe
                     70:   because you're not root), you cannot use these binary packages, but
1.33      rillig     71:   have to build the packages yourself, which is explained in <a class="xref" href="platforms.html#bootstrapping-pkgsrc" title="4.2. Bootstrapping pkgsrc">Section 4.2, &#8220;Bootstrapping pkgsrc&#8221;</a>.</p>
1.14      asau       72: <div class="sect2">
1.1       dsieger    73: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig     74: <a name="finding-binary-packages"></a>5.1.1. Finding binary packages</h3></div></div></div>
1.4       weinem     75: <p>To install binary packages, you first need to know from where
                     76:     to get them. The first place where you should look is on the main
1.32      sevan      77:     pkgsrc FTP server in the directory <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/" target="_top"><code class="filename">/pub/pkgsrc/packages</code></a>.</p>
1.4       weinem     78: <p>This directory contains binary packages for multiple
                     79:     platforms. First, select your operating system. (Ignore the
                     80:     directories with version numbers attached to it, they just exist for
                     81:     legacy reasons.) Then, select your hardware architecture, and in the
1.11      wiz        82:     third step, the OS version and the <span class="quote">&#8220;<span class="quote">version</span>&#8221;</span> of pkgsrc.</p>
1.5       rillig     83: <p>In this directory, you often find a file called
                     84:     <code class="filename">bootstrap.tar.gz</code> which contains the package
                     85:     management tools. If the file is missing, it is likely that your
                     86:     operating system already provides those tools. Download the file and
                     87:     extract it in the <code class="filename">/</code> directory. It will create
                     88:     the directories <code class="filename">/usr/pkg</code> (containing the tools
1.24      sevan      89:     for managing binary packages and the database of installed packages).</p>
1.1       dsieger    90: </div>
1.14      asau       91: <div class="sect2">
1.1       dsieger    92: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig     93: <a name="installing-binary-packages"></a>5.1.2. Installing binary packages</h3></div></div></div>
1.5       rillig     94: <p>In the directory from the last section, there is a
1.16      wiz        95:     subdirectory called <code class="filename">All/</code>, which contains all the
1.5       rillig     96:     binary packages that are available for the platform, excluding those
                     97:     that may not be distributed via FTP or CDROM (depending on which
1.11      wiz        98:     medium you are using).</p>
1.5       rillig     99: <p>To install packages directly from an FTP or HTTP server, run
                    100:     the following commands in a Bourne-compatible shell (be sure to
1.6       hubertf   101:     <span class="command"><strong>su</strong></span> to root first):</p>
1.5       rillig    102: <pre class="screen">
                    103: <code class="prompt">#</code> <strong class="userinput"><code>PATH="/usr/pkg/sbin:$PATH"</code></strong>
1.32      sevan     104: <code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/<em class="replaceable"><code>OPSYS</code></em>/<em class="replaceable"><code>ARCH</code></em>/<em class="replaceable"><code>VERSIONS</code></em>/All/"</code></strong>
1.5       rillig    105: <code class="prompt">#</code> <strong class="userinput"><code>export PATH PKG_PATH</code></strong>
                    106: </pre>
                    107: <p>Instead of URLs, you can also use local paths, for example if
                    108:     you are installing from a set of CDROMs, DVDs or an NFS-mounted
                    109:     repository. If you want to install packages from multiple sources,
                    110:     you can separate them by a semicolon in
                    111:     <code class="varname">PKG_PATH</code>.</p>
                    112: <p>After these preparations, installing a package is very
                    113:     easy:</p>
                    114: <pre class="screen">
1.24      sevan     115: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add libreoffice</code></strong>
                    116: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add ap24-php71-*</code></strong>
1.5       rillig    117: </pre>
1.1       dsieger   118: <p>Note that any prerequisite packages needed to run the
                    119:     package in question will be installed, too, assuming they are
                    120:     present where you install from.</p>
1.11      wiz       121: <p>Adding packages might install vulnerable packages.
                    122:     Thus you should run <span class="command"><strong>pkg_admin audit</strong></span>
1.8       jmcneill  123:     regularly, especially after installing new packages, and verify
                    124:     that the vulnerabilities are acceptable for your configuration.</p>
1.1       dsieger   125: <p>After you've installed packages, be sure to have
                    126:     <code class="filename">/usr/pkg/bin</code> and <code class="filename">/usr/pkg/sbin</code> in your
                    127:     <code class="varname">PATH</code> so you can actually start the just
                    128:     installed program.</p>
                    129: </div>
1.14      asau      130: <div class="sect2">
1.1       dsieger   131: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    132: <a name="using.pkg_delete"></a>5.1.3. Deinstalling packages</h3></div></div></div>
1.1       dsieger   133: <p>To deinstall a package, it does not matter whether it was
                    134:     installed from source code or from a binary package. The
1.6       hubertf   135:     <span class="command"><strong>pkg_delete</strong></span> command does not know it anyway.
                    136:     To delete a package, you can just run <span class="command"><strong>pkg_delete
1.1       dsieger   137:     <em class="replaceable"><code>package-name</code></em></strong></span>. The package
                    138:     name can be given with or without version number. Wildcards can
                    139:     also be used to deinstall a set of packages, for example
                    140:     <code class="literal">*emacs*</code>. Be sure to include them in quotes,
                    141:     so that the shell does not expand them before
                    142:     <code class="literal">pkg_delete</code> sees them.</p>
                    143: <p>The <code class="option">-r</code> option is very powerful: it
                    144:     removes all the packages that require the package in question
                    145:     and then removes the package itself. For example:
                    146: 
                    147:     </p>
                    148: <pre class="screen">
                    149: <code class="prompt">#</code> <strong class="userinput"><code>pkg_delete -r jpeg</code></strong>
                    150:     </pre>
                    151: <p>
                    152: 
                    153:     will remove jpeg and all the packages that used it; this allows
                    154:     upgrading the jpeg package.</p>
                    155: </div>
1.14      asau      156: <div class="sect2">
1.1       dsieger   157: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    158: <a name="using.pkg_info"></a>5.1.4. Getting information about installed packages</h3></div></div></div>
1.6       hubertf   159: <p>The <span class="command"><strong>pkg_info</strong></span> shows information about
1.1       dsieger   160:     installed packages or binary package files.</p>
                    161: </div>
1.14      asau      162: <div class="sect2">
1.1       dsieger   163: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    164: <a name="vulnerabilities"></a>5.1.5. Checking for security vulnerabilities in installed packages</h3></div></div></div>
1.1       dsieger   165: <p>
1.35    ! leot      166:       The pkgsrc Security Team and Packages Groups maintain a list of
1.1       dsieger   167:       known security vulnerabilities to packages which are (or have been)
                    168:       included in pkgsrc.  The list is available from the NetBSD
1.35    ! leot      169:       FTP site at <a class="ulink" href="http://ftp.netbsd.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities" target="_top">http://ftp.netbsd.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities</a>.
1.1       dsieger   170:     </p>
                    171: <p>
1.10      jakllsch  172:       Through <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1.1       dsieger   173:       this list can be downloaded
                    174:       automatically, and a security audit of all packages installed on a system
                    175:       can take place.
                    176:     </p>
                    177: <p>
1.10      jakllsch  178:       There are two components to auditing.  The first
                    179:       step, <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
                    180:       is for downloading
1.1       dsieger   181:       the list of vulnerabilities from the NetBSD FTP site.  The second
1.10      jakllsch  182:       step, <span class="command"><strong>pkg_admin audit</strong></span>, checks to see if any of your
1.1       dsieger   183:       installed packages are vulnerable.  If a package is vulnerable, you
                    184:       will see output similar to the following:
                    185:     </p>
                    186: <pre class="screen">Package samba-2.0.9 has a local-root-shell vulnerability, see
                    187:     http://www.samba.org/samba/whatsnew/macroexploit.html</pre>
                    188: <p>
1.10      jakllsch  189:       You may wish to have the
1.32      sevan     190:       <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities" target="_top">vulnerabilities</a>
1.10      jakllsch  191:       file downloaded daily so that
                    192:       it remains current.  This may be done by adding an appropriate entry
1.34      leot      193:       to the root users <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?crontab+5.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">crontab</span>(5)</span></a> entry.  For example the entry
1.10      jakllsch  194:       </p>
                    195: <pre class="screen">
1.26      sevan     196: # Download vulnerabilities file
1.24      sevan     197: 0 3 * * * /usr/pkg/sbin/pkg_admin fetch-pkg-vulnerabilities &gt;/dev/null 2&gt;&amp;1
1.26      sevan     198: # Audit the installed packages and email results to root
                    199: 9 3 * * * /usr/pkg/sbin/pkg_admin audit |mail -s "Installed package audit result" \
                    200:            root &gt;/dev/null 2&gt;&amp;1
1.10      jakllsch  201:       </pre>
                    202: <p>
1.24      sevan     203:       will update the vulnerability list every day at 3AM, followed by an audit
                    204:       at 3:09AM. The result of the audit are then emailed to root.
1.10      jakllsch  205: 
1.24      sevan     206:       On NetBSD this may be accomplished instead by adding the following
                    207:       line to <code class="filename">/etc/daily.conf</code>:
1.10      jakllsch  208:       </p>
                    209: <pre class="screen">
1.24      sevan     210: fetch_pkg_vulnerabilities=YES
1.10      jakllsch  211:       </pre>
                    212: <p>
1.24      sevan     213:       to fetch the vulnerability list from the daily security script. The system
                    214:       is set to audit the packages by default but can be set explicitly, if
1.27      wiz       215:       desired (not required), by adding the following line to
1.24      sevan     216: <code class="filename">/etc/security.conf</code>:
                    217:       </p>
                    218: <pre class="screen">
                    219: check_pkg_vulnerabilities=YES
                    220:       </pre>
                    221: <p>
1.34      leot      222:       see <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?daily.conf+5.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a> and <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?security.conf+5.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for more details.
1.1       dsieger   223:     </p>
                    224: </div>
1.14      asau      225: <div class="sect2">
1.1       dsieger   226: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    227: <a name="pkg_versions"></a>5.1.6. Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div>
1.1       dsieger   228: <p>
1.30      leot      229:       Install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html" target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
1.11      wiz       230:       <span class="command"><strong>lintpkgsrc</strong></span> with the <span class="quote">&#8220;<span class="quote">-i</span>&#8221;</span>
1.1       dsieger   231:       argument to check if your packages are up-to-date, e.g.
                    232:     </p>
                    233: <pre class="screen">
                    234: <code class="prompt">%</code> <strong class="userinput"><code>lintpkgsrc -i</code></strong>
                    235: ...
                    236: Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
                    237:     </pre>
1.6       hubertf   238: <p>You can then use <span class="command"><strong>make update</strong></span> to update the
1.1       dsieger   239:     package on your system and rebuild any dependencies.
                    240:     </p>
                    241: </div>
1.14      asau      242: <div class="sect2">
1.1       dsieger   243: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    244: <a name="using.pkg_admin"></a>5.1.7. Other administrative functions</h3></div></div></div>
1.6       hubertf   245: <p>The <span class="command"><strong>pkg_admin</strong></span> executes various
1.1       dsieger   246:     administrative functions on the package system.</p>
                    247: </div>
                    248: </div>
1.14      asau      249: <div class="sect1">
1.1       dsieger   250: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.33      rillig    251: <a name="building-packages-from-source"></a>5.2. Building packages from source</h2></div></div></div>
1.1       dsieger   252: <p>After obtaining pkgsrc, the <code class="filename">pkgsrc</code>
                    253:   directory now contains a set of packages, organized into
                    254:   categories. You can browse the online index of packages, or run
1.6       hubertf   255:   <span class="command"><strong>make readme</strong></span> from the <code class="filename">pkgsrc</code>
1.1       dsieger   256:   directory to build local <code class="filename">README.html</code> files for
1.30      leot      257:   all packages, viewable with any web browser such as <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html" target="_top"><code class="filename">www/lynx</code></a> or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html" target="_top"><code class="filename">www/firefox</code></a>.</p>
1.1       dsieger   258: <p>The default <span class="emphasis"><em>prefix</em></span> for installed packages
                    259:   is <code class="filename">/usr/pkg</code>. If you wish to change this, you
                    260:   should do so by setting <code class="varname">LOCALBASE</code> in
1.6       hubertf   261:   <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>. You should not try to use multiple
1.1       dsieger   262:   different <code class="varname">LOCALBASE</code> definitions on the same
                    263:   system (inside a chroot is an exception). </p>
                    264: <p>The rest of this chapter assumes that the package is already
1.6       hubertf   265:   in pkgsrc. If it is not, see <a class="xref" href="developers-guide.html" title="Part II. The pkgsrc developer's guide">Part II, &#8220;The pkgsrc developer's guide&#8221;</a> for
1.1       dsieger   266:   instructions how to create your own packages.</p>
1.14      asau      267: <div class="sect2">
1.1       dsieger   268: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    269: <a name="requirements"></a>5.2.1. Requirements</h3></div></div></div>
1.1       dsieger   270: <p>To build packages from source, you need a working C
                    271:     compiler. On NetBSD, you need to install the
1.11      wiz       272:     <span class="quote">&#8220;<span class="quote">comp</span>&#8221;</span> and the <span class="quote">&#8220;<span class="quote">text</span>&#8221;</span> distribution
1.1       dsieger   273:     sets. If you want to build X11-related packages, the
1.11      wiz       274:     <span class="quote">&#8220;<span class="quote">xbase</span>&#8221;</span> and <span class="quote">&#8220;<span class="quote">xcomp</span>&#8221;</span> distribution
1.1       dsieger   275:     sets are required, too.</p>
                    276: </div>
1.14      asau      277: <div class="sect2">
1.1       dsieger   278: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    279: <a name="fetching-distfiles"></a>5.2.2. Fetching distfiles</h3></div></div></div>
1.1       dsieger   280: <p>The first step for building a package is downloading the
                    281:     distfiles (i.e. the unmodified source). If they have not yet been
                    282:     downloaded, pkgsrc will fetch them automatically.</p>
                    283: <p>If you have all files that you need in the
                    284:     <code class="filename">distfiles</code> directory,
                    285:     you don't need to connect. If the distfiles are on CD-ROM, you can
                    286:     mount the CD-ROM on <code class="filename">/cdrom</code> and add:
                    287:     </p>
                    288: <pre class="screen">DISTDIR=/cdrom/pkgsrc/distfiles</pre>
                    289: <p>
1.6       hubertf   290:     to your <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1       dsieger   291: <p>By default a list of distribution sites will be randomly
                    292:     intermixed to prevent huge load on servers which holding popular
                    293:     packages (for example, SourceForge.net mirrors). Thus, every
                    294:     time when you need to fetch yet another distfile all the mirrors
                    295:     will be tried in new (random) order. You can turn this feature
                    296:     off by setting <code class="varname">MASTER_SORT_RANDOM=NO</code> (for
                    297:     <code class="varname">PKG_DEVELOPER</code>s it's already disabled).</p>
                    298: <p>You can overwrite some of the major distribution sites to
                    299:     fit to sites that are close to your own.  By setting one or two
                    300:     variables you can modify the order in which the master sites are
                    301:     accessed.  <code class="varname">MASTER_SORT</code> contains a whitespace
                    302:     delimited list of domain suffixes.
                    303:     <code class="varname">MASTER_SORT_REGEX</code> is even more flexible, it
                    304:     contains a whitespace delimited list of regular expressions.  It
                    305:     has higher priority than <code class="varname">MASTER_SORT</code>.  Have a
                    306:     look at <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to find
                    307:     some examples.  This may save some of your bandwidth and
                    308:     time.</p>
                    309: <p>You can change these settings either in your shell's environment, or,
                    310:     if you want to keep the settings, by editing the
1.6       hubertf   311:     <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file,
1.1       dsieger   312:     and adding the definitions there.</p>
                    313: <p>
                    314:       If a package depends on many other packages (such as
1.30      leot      315:       <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/README.html" target="_top"><code class="filename">meta-pkgs/kde4</code></a>), the build process may
1.1       dsieger   316:       alternate between periods of
                    317:       downloading source, and compiling. To ensure you have all the source
                    318:       downloaded initially you can run the command:
                    319:       </p>
                    320: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch-list | sh</code></strong></pre>
                    321: <p>
                    322:       which will output and run a set of shell commands to fetch the
                    323:       necessary files into the <code class="filename">distfiles</code> directory.  You can
                    324:       also choose to download the files manually.
                    325:     </p>
                    326: </div>
1.14      asau      327: <div class="sect2">
1.1       dsieger   328: <div class="titlepage"><div><div><h3 class="title">
1.33      rillig    329: <a name="how-to-build-and-install"></a>5.2.3. How to build and install</h3></div></div></div>
1.1       dsieger   330: <p>
                    331:       Once the software has downloaded, any patches will be applied, then it
                    332:       will be compiled for you. This may take some time depending on your
                    333:       computer, and how many other packages the software depends on and their
                    334:       compile time.
                    335:     </p>
1.14      asau      336: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1       dsieger   337: <h3 class="title">Note</h3>
                    338: <p>If using bootstrap or pkgsrc on a non-NetBSD system,
1.6       hubertf   339:     use the pkgsrc <span class="command"><strong>bmake</strong></span> command instead of
1.11      wiz       340:     <span class="quote">&#8220;<span class="quote">make</span>&#8221;</span> in the examples in this guide.</p>
1.1       dsieger   341: </div>
                    342: <p>For example, type</p>
                    343: <pre class="screen">
                    344: <code class="prompt">%</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
                    345: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
                    346:     </pre>
                    347: <p>at the shell prompt to build the various components of the
                    348:     package.</p>
                    349: <p>The next stage is to actually install the newly compiled
                    350:     program onto your system. Do this by entering:
                    351: 
                    352:     </p>
                    353: <pre class="screen">
                    354: <code class="prompt">%</code> <strong class="userinput"><code>make install</code></strong>
                    355:     </pre>
                    356: <p>
                    357: 
                    358:     while you are still in the directory for whatever package you
                    359:     are installing.</p>
                    360: <p>Installing the package on your system may require you to
                    361:     be root.  However, pkgsrc has a
                    362:     <span class="emphasis"><em>just-in-time-su</em></span> feature, which allows you
                    363:     to only become root for the actual installation step.</p>
                    364: <p>That's it, the software should now be installed and setup for use.
                    365:     You can now enter:
                    366: 
                    367:     </p>
                    368: <pre class="screen">
                    369: <code class="prompt">%</code> <strong class="userinput"><code>make clean</code></strong>
                    370:     </pre>
                    371: <p>
                    372: 
                    373:     to remove the compiled files in the work directory, as you shouldn't need
                    374:     them any more. If other packages were also added to your system
                    375:     (dependencies) to allow your program to compile, you can tidy these up
                    376:     also with the command:</p>
                    377: <pre class="screen">
                    378: <code class="prompt">%</code> <strong class="userinput"><code>make clean-depends</code></strong>
                    379:     </pre>
                    380: <p>Taking the figlet utility as an example, we can install it on our
1.6       hubertf   381:     system by building as shown in <a class="xref" href="logs.html" title="Appendix B. Build logs">Appendix B, <i>Build logs</i></a>.</p>
1.1       dsieger   382: <p>The program is installed under the default root of the
                    383:     packages tree - <code class="filename">/usr/pkg</code>. Should this not
                    384:     conform to your tastes, set the <code class="varname">LOCALBASE</code>
                    385:     variable in your environment, and it will use that value as the
                    386:     root of your packages tree. So, to use
                    387:     <code class="filename">/usr/local</code>, set
                    388:     <code class="varname">LOCALBASE=/usr/local</code> in your environment.
                    389:     Please note that you should use a directory which is dedicated to
                    390:     packages and not shared with other programs (i.e., do not try and
                    391:     use <code class="varname">LOCALBASE=/usr</code>).  Also, you should not try
                    392:     to add any of your own files or directories (such as
                    393:     <code class="filename">src/</code>, <code class="filename">obj/</code>, or
                    394:     <code class="filename">pkgsrc/</code>) below the
                    395:     <code class="varname">LOCALBASE</code> tree.  This is to prevent possible
                    396:     conflicts between programs and other files installed by the
                    397:     package system and whatever else may have been installed
                    398:     there.</p>
1.6       hubertf   399: <p>Some packages look in <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> to
1.1       dsieger   400:     alter some configuration options at build time.  Have a look at
                    401:     <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to get an overview
                    402:     of what will be set there by default.  Environment variables such
                    403:     as <code class="varname">LOCALBASE</code> can be set in
1.6       hubertf   404:     <a class="link" href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> to save having to remember to
1.1       dsieger   405:     set them each time you want to use pkgsrc.</p>
1.11      wiz       406: <p>Occasionally, people want to <span class="quote">&#8220;<span class="quote">look under the
                    407:     covers</span>&#8221;</span> to see what is going on when a package is building
1.1       dsieger   408:     or being installed. This may be for debugging purposes, or out of
                    409:     simple curiosity. A number of utility values have been added to
                    410:     help with this.</p>
1.11      wiz       411: <div class="orderedlist"><ol class="orderedlist" type="1">
                    412: <li class="listitem">
1.34      leot      413: <p>If you invoke the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> command with
1.1       dsieger   414:        <code class="varname">PKG_DEBUG_LEVEL=2</code>, then a huge amount of
                    415:        information will be displayed. For example,</p>
                    416: <pre class="screen"><strong class="userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong></pre>
                    417: <p>will show all the commands that are invoked, up to and
1.11      wiz       418:        including the <span class="quote">&#8220;<span class="quote">patch</span>&#8221;</span> stage.</p>
1.1       dsieger   419: </li>
1.11      wiz       420: <li class="listitem">
1.34      leot      421: <p>If you want to know the value of a certain <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1       dsieger   422:        definition, then the <code class="varname">VARNAME</code> definition
                    423:        should be used, in conjunction with the show-var
1.34      leot      424:        target. e.g. to show the expansion of the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1       dsieger   425:        variable <code class="varname">LOCALBASE</code>:</p>
                    426: <pre class="screen">
                    427: <code class="prompt">%</code> <strong class="userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
                    428: /usr/pkg
                    429: <code class="prompt">%</code>
                    430:        </pre>
                    431: </li>
                    432: </ol></div>
                    433: <p>If you want to install a binary package that you've either
                    434:     created yourself (see next section), that you put into
                    435:     pkgsrc/packages manually or that is located on a remote FTP
                    436:     server, you can use the "bin-install" target. This target will
1.34      leot      437:     install a binary package - if available - via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>,
1.6       hubertf   438:     else do a <span class="command"><strong>make package</strong></span>.  The list of remote FTP
1.1       dsieger   439:     sites searched is kept in the variable
                    440:     <code class="varname">BINPKG_SITES</code>, which defaults to
1.34      leot      441:     ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-8.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>
1.1       dsieger   442:     can be put into <code class="varname">BIN_INSTALL_FLAGS</code>.  See
                    443:     <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more
                    444:     details.</p>
                    445: <p>A final word of warning: If you set up a system that has a
                    446:     non-standard setting for <code class="varname">LOCALBASE</code>, be sure to
                    447:     set that before any packages are installed, as you cannot use
                    448:     several directories for the same purpose. Doing so will result in
                    449:     pkgsrc not being able to properly detect your installed packages,
                    450:     and fail miserably. Note also that precompiled binary packages are
                    451:     usually built with the default <code class="varname">LOCALBASE</code> of
                    452:     <code class="filename">/usr/pkg</code>, and that you should
                    453:     <span class="emphasis"><em>not</em></span> install any if you use a non-standard
                    454:     <code class="varname">LOCALBASE</code>.</p>
                    455: </div>
                    456: </div>
                    457: </div>
                    458: <div class="navfooter">
                    459: <hr>
                    460: <table width="100%" summary="Navigation footer">
                    461: <tr>
                    462: <td width="40%" align="left">
                    463: <a accesskey="p" href="platforms.html">Prev</a> </td>
                    464: <td width="20%" align="center"><a accesskey="u" href="users-guide.html">Up</a></td>
                    465: <td width="40%" align="right"> <a accesskey="n" href="configuring.html">Next</a>
                    466: </td>
                    467: </tr>
                    468: <tr>
1.33      rillig    469: <td width="40%" align="left" valign="top">Chapter 4. Using pkgsrc on systems other than NetBSD </td>
1.1       dsieger   470: <td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
1.33      rillig    471: <td width="40%" align="right" valign="top"> Chapter 6. Configuring pkgsrc</td>
1.1       dsieger   472: </tr>
                    473: </table>
                    474: </div>
                    475: </body>
                    476: </html>

CVSweb <webmaster@jp.NetBSD.org>