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