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