diff options
| author | asau <asau> | 2013-02-20 17:06:03 +0000 |
|---|---|---|
| committer | asau <asau> | 2013-02-20 17:06:03 +0000 |
| commit | 4a5c40e45824976487242ad55fa62a359927eca1 (patch) | |
| tree | 35a621ffdc1d9b14274cee40afe0b274c4f63f40 /doc/pkgsrc.html | |
| parent | e29b1b5427e331c46dd737ba95b8c79a619239c0 (diff) | |
| download | pkgsrc-4a5c40e45824976487242ad55fa62a359927eca1.tar.gz | |
regen
Diffstat (limited to 'doc/pkgsrc.html')
| -rw-r--r-- | doc/pkgsrc.html | 1047 |
1 files changed, 527 insertions, 520 deletions
diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 9d8dc5738b3..1635d56242f 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -7,7 +7,7 @@ <meta name="generator" content="DocBook XSL Stylesheets VX.X.X"> <meta name="description" content="pkgsrc is a centralized package management system for Unix-like operating systems. This guide provides information for users and developers of pkgsrc. It covers installation of binary and source packages, creation of binary and source packages and a high-level overview about the infrastructure."> </head> -<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="The pkgsrc guide"> +<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"> <div class="titlepage"> <div> <div><h1 class="title"> @@ -32,7 +32,7 @@ </div></div> <div><p class="copyright">Copyright © 1994-2007 The NetBSD Foundation, Inc</p></div> <div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.26 2007/09/18 08:17:21 rillig Exp $</p></div> -<div><div class="abstract" title="Abstract"> +<div><div class="abstract"> <p class="title"><b>Abstract</b></p> <p>pkgsrc is a centralized package management system for Unix-like operating systems. This guide provides information for @@ -488,9 +488,9 @@ source packages</a></span></dt> </dt> </dl> </div> -<div class="chapter" title="Chapter 1. What is pkgsrc?"> -<div class="titlepage"><div><div><h2 class="title"> -<a name="introduction"></a>Chapter 1. What is pkgsrc?</h2></div></div></div> +<div class="chapter"> +<div class="titlepage"><div><div><h1 class="title"> +<a name="introduction"></a>Chapter 1. What is pkgsrc?</h1></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> @@ -505,7 +505,7 @@ source packages</a></span></dt> <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt> </dl> </div> -<div class="sect1" title="1.1. Introduction"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="introduction-section"></a>1.1. Introduction</h2></div></div></div> <p>There is a lot of software freely available for Unix-based @@ -517,7 +517,7 @@ to handle binary packages, so that not every user has to build the packages for himself, which is a time-costly task.</p> <p>pkgsrc currently contains several thousand packages, including:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache/README.html" target="_top"><code class="filename">www/apache</code></a> - The Apache web server</p></li> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html" target="_top"><code class="filename">www/firefox</code></a> - The Firefox @@ -531,13 +531,13 @@ packages for himself, which is a time-costly task.</p> <p>pkgsrc has built-in support for handling varying dependencies, such as pthreads and X11, and extended features such as IPv6 support on a range of platforms.</p> -<div class="sect2" title="1.1.1. Why pkgsrc?"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="why-pkgsrc"></a>1.1.1. Why pkgsrc?</h3></div></div></div> <p> pkgsrc provides the following key features: </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Easy building of software from source as well as the creation and installation of binary packages. The source and latest patches are retrieved from a master or mirror download site, checksum @@ -567,7 +567,7 @@ pkgsrc provides the following key features: for your environment.</p></li> </ul></div> <p>The following principles are basic to pkgsrc:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><span class="quote">“<span class="quote">It should only work if it's right.</span>”</span> — That means, if a package contains bugs, it's better to find them and to complain about them rather than to just install the package @@ -581,7 +581,7 @@ pkgsrc has been ported to many operating systems. Care is taken that packages behave the same on all platforms.</p></li> </ul></div> </div> -<div class="sect2" title="1.1.2. Supported platforms"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="intro.platforms"></a>1.1.2. Supported platforms</h3></div></div></div> <p>pkgsrc consists of both a source distribution and a binary @@ -671,7 +671,7 @@ minutes!</p> <br class="table-break"> </div> </div> -<div class="sect1" title="1.2. Overview"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="overview"></a>1.2. Overview</h2></div></div></div> <p>This document is divided into three parts. The first, @@ -688,13 +688,13 @@ minutes!</p> <p>This document is available in various formats: <span class="simplelist"><a class="ulink" href="index.html" target="_top">HTML</a>, <a class="ulink" href="pkgsrc.pdf" target="_top">PDF</a>, <a class="ulink" href="pkgsrc.ps" target="_top">PS</a>, <a class="ulink" href="pkgsrc.txt" target="_top">TXT</a></span>.</p> </div> -<div class="sect1" title="1.3. Terminology"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="terminology"></a>1.3. Terminology</h2></div></div></div> <p>There has been a lot of talk about <span class="quote">“<span class="quote">ports</span>”</span>, <span class="quote">“<span class="quote">packages</span>”</span>, etc. so far. Here is a description of all the terminology used within this document.</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term">Package</span></dt> <dd><p>A set of files and building instructions that describe what's necessary @@ -738,10 +738,10 @@ minutes!</p> constructed from all the files in the distfile by the actions defined in the corresponding package.</p></dd> </dl></div> -<div class="sect2" title="1.3.1. Roles involved in pkgsrc"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="term.roles"></a>1.3.1. Roles involved in pkgsrc</h3></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term">pkgsrc users</span></dt> <dd> <p>The @@ -766,7 +766,7 @@ minutes!</p> </dl></div> </div> </div> -<div class="sect1" title="1.4. Typography"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="typography"></a>1.4. Typography</h2></div></div></div> <p>When giving examples for commands, shell prompts are used to @@ -776,7 +776,7 @@ minutes!</p> shell prompt, assuming they use the C-shell or tcsh.</p> </div> </div> -<div class="part" title="Part I. The pkgsrc user's guide"> +<div class="part"> <div class="titlepage"><div><div><h1 class="title"> <a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div> <div class="toc"> @@ -901,7 +901,7 @@ builds)</a></span></dt> </dl></dd> </dl> </div> -<div class="chapter" title="Chapter 2. Where to get pkgsrc and how to keep it up-to-date"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="getting"></a>Chapter 2. Where to get pkgsrc and how to keep it up-to-date</h2></div></div></div> <div class="toc"> @@ -927,7 +927,7 @@ your filesystem, provided that the pathname does not contain white-space or other characters that are interpreted specially by the shell and some other programs. A safe bet is to use only letters, digits, underscores and dashes.</p> -<div class="sect1" title="2.1. Getting pkgsrc for the first time"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div> <p>Before you download any pkgsrc files, you should decide @@ -940,7 +940,7 @@ and dashes.</p> <p>The second step is to decide <span class="emphasis"><em>how</em></span> you want to download pkgsrc. You can get it as a tar file or via CVS. Both ways are described here.</p> -<div class="sect2" title="2.1.1. As tar file"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="getting-via-tar"></a>2.1.1. As tar file</h3></div></div></div> <p>The primary download location for all pkgsrc files is @@ -966,7 +966,7 @@ and dashes.</p> <p>To download pkgsrc-current, run:</p> <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</code></strong></pre> </div> -<div class="sect2" title="2.1.2. Via anonymous CVS"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div> <p>To fetch a specific pkgsrc stable branch, run:</p> @@ -1008,17 +1008,17 @@ release -d </pre> </div> </div> -<div class="sect1" title="2.2. Keeping pkgsrc up-to-date"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="uptodate"></a>2.2. Keeping pkgsrc up-to-date</h2></div></div></div> <p>The preferred way to keep pkgsrc up-to-date is via CVS (which also works if you have first installed it via a tar file). It saves bandwidth and hard disk activity, compared to downloading the tar file again.</p> -<div class="sect2" title="2.2.1. Via tar files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="uptodate-tar"></a>2.2.1. Via tar files</h3></div></div></div> -<div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Warning</h3> <p>When updating from a tar file, you first need to completely remove the old pkgsrc directory. Otherwise those @@ -1039,7 +1039,7 @@ release -d changes to the files in the pkgsrc directory. Remove the pkgsrc directory and extract the new tar file. Done.</p> </div> -<div class="sect2" title="2.2.2. Via CVS"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="uptodate-cvs"></a>2.2.2. Via CVS</h3></div></div></div> <p>To update pkgsrc via CVS, change to the <code class="filename">pkgsrc</code> directory and run cvs:</p> @@ -1048,7 +1048,7 @@ release -d <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable as described above. E.g.:</p> <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP</code></strong> </pre> -<div class="sect3" title="2.2.2.1. Switching between different pkgsrc branches"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="uptodate-cvs-switch"></a>2.2.2.1. Switching between different pkgsrc branches</h4></div></div></div> <p>When updating pkgsrc, the CVS program keeps track of the @@ -1059,7 +1059,7 @@ release -d back to the stable branch, add the <span class="quote">“<span class="quote">-rpkgsrc-2009Q3</span>”</span> option.</p> </div> -<div class="sect3" title="2.2.2.2. What happens to my changes when updating?"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="uptodate-cvs-changes"></a>2.2.2.2. What happens to my changes when updating?</h4></div></div></div> <p>When you update pkgsrc, the CVS program will only touch @@ -1073,7 +1073,7 @@ release -d </div> </div> </div> -<div class="chapter" title="Chapter 3. Using pkgsrc on systems other than NetBSD"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="platforms"></a>Chapter 3. Using pkgsrc on systems other than NetBSD</h2></div></div></div> <div class="toc"> @@ -1093,12 +1093,12 @@ release -d </dl></dd> </dl> </div> -<div class="sect1" title="3.1. Binary distribution"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="binarydist"></a>3.1. Binary distribution</h2></div></div></div> <p>See <a class="xref" href="#using-pkg" title="4.1. Using binary packages">Section 4.1, “Using binary packages”</a>.</p> </div> -<div class="sect1" title="3.2. Bootstrapping pkgsrc"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bootstrapping-pkgsrc"></a>3.2. Bootstrapping pkgsrc</h2></div></div></div> <p>Installing the bootstrap kit from source should be as simple as:</p> @@ -1116,7 +1116,7 @@ release -d directory where pkgsrc will do its internal bookkeeping. However, these can also be set using command-line arguments.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>The bootstrap installs a <span class="command"><strong>bmake</strong></span> tool. Use this <span class="command"><strong>bmake</strong></span> when building via pkgsrc. @@ -1124,22 +1124,25 @@ release -d instead of <span class="quote">“<span class="quote">make</span>”</span>.</p> </div> </div> -<div class="sect1" title="3.3. Platform-specific notes"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="platform-specific-notes"></a>3.3. Platform-specific notes</h2></div></div></div> <p>Here are some platform-specific notes you should be aware of.</p> -<div class="sect2" title="3.3.1. Darwin (Mac OS X)"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="darwin"></a>3.3.1. Darwin (Mac OS X)</h3></div></div></div> -<p>Darwin 5.x and up are supported. Before you start, you - will need to download and install the Mac OS X Developer Tools - from Apple's Developer Connection. See +<p>Darwin 5.x and up are supported.</p> +<p>Before you start, you need to download and install + the Mac OS X Developer Tools from Apple's Developer Connection. + This requires (free) membership. See <a class="ulink" href="http://developer.apple.com/macosx/" target="_top">http://developer.apple.com/macosx/</a> - for details. Also, make sure you install X11 (an optional - package included with the Developer Tools) if you intend to - build packages that use the X11 Window System.</p> + for details. Also, make sure you install X11 (an optional + package included with the Developer Tools) if you intend + to build packages that use the X11 Window System. + (If you don't want or need the full Xcode GUI, + download and install Command Line Tools for Xcode.)</p> </div> -<div class="sect2" title="3.3.2. FreeBSD"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="freebsd"></a>3.3.2. FreeBSD</h3></div></div></div> <p>FreeBSD 8.3 and 9.0 have been tested and are supported, @@ -1168,7 +1171,7 @@ release -d when you use the bootstrap script.</p></li> </ol></div> </div> -<div class="sect2" title="3.3.3. Interix"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="interix"></a>3.3.3. Interix</h3></div></div></div> <p>Interix is a POSIX-compatible subsystem for the Windows NT kernel, @@ -1186,12 +1189,12 @@ release -d 6.1 (64bit) subsystems have been tested. Other versions may work as well. The Interix 5.x subsystem has not yet been tested with pkgsrc.</p> -<div class="sect3" title="3.3.3.1. When installing Interix/SFU"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.interix-sfu-install"></a>3.3.3.1. When installing Interix/SFU</h4></div></div></div> <p>At an absolute minimum, the following packages must be installed from the Windows Services for Unix 3.5 distribution in order to use pkgsrc:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Utilities -> Base Utilities</p></li> <li class="listitem"><p>Interix GNU Components -> (all)</p></li> <li class="listitem"><p>Remote Connectivity</p></li> @@ -1227,12 +1230,12 @@ release -d risk if applications are often run as a user in the Administrators group!)</p> </div> -<div class="sect3" title="3.3.3.2. What to do if Interix/SFU is already installed"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.interix-sfu-postinstall"></a>3.3.3.2. What to do if Interix/SFU is already installed</h4></div></div></div> <p>If SFU is already installed and you wish to alter these settings to work with pkgsrc, note the following things.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>To uninstall UNIX Perl, use Add/Remove Programs, select Microsoft Windows Services for UNIX, then click Change. In the installer, choose Add or Remove, then uncheck Utilities->UNIX Perl.</p></li> @@ -1250,7 +1253,7 @@ release -d </li> </ul></div> </div> -<div class="sect3" title="3.3.3.3. Important notes for using pkgsrc"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.interix-notes"></a>3.3.3.3. Important notes for using pkgsrc</h4></div></div></div> <p>The package manager (either the pkgsrc "su" user, or the user @@ -1273,13 +1276,13 @@ release -d interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi: </pre> </div> -<div class="sect3" title="3.3.3.4. Limitations of the Interix platform"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.interix-limits"></a>3.3.3.4. Limitations of the Interix platform</h4></div></div></div> <p>Though Interix suffices as a familiar and flexible substitute for a full Unix-like platform, it has some drawbacks that should be noted for those desiring to make the most of Interix.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p><span class="strong"><strong>X11:</strong></span></p> <p>Interix comes with the standard set of X11R6 client libraries, @@ -1330,7 +1333,7 @@ interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi: </li> </ul></div> </div> -<div class="sect3" title="3.3.3.5. Known issues for pkgsrc on Interix"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.interix-knownissues"></a>3.3.3.5. Known issues for pkgsrc on Interix</h4></div></div></div> <p>It is not necessary, in general, to have a "root" user on the @@ -1349,7 +1352,7 @@ interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi: </pre> </div> </div> -<div class="sect2" title="3.3.4. IRIX"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="irix"></a>3.3.4. IRIX</h3></div></div></div> <p>You will need a working C compiler, either gcc or SGI's MIPS and MIPSpro @@ -1394,7 +1397,7 @@ PKGSRC_COMPILER= mipspro <code class="filename">/usr/freeware/bin</code>), and (important) pass the '--preserve-path' flag.</p> </div> -<div class="sect2" title="3.3.5. Linux"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="linux"></a>3.3.5. Linux</h3></div></div></div> <p>Some versions of Linux (for example Debian GNU/Linux) need @@ -1409,7 +1412,7 @@ PKGSRC_COMPILER= mipspro <pre class="programlisting"> env ICCBASE=/opt/intel/cc/10.1.008 ./bootstrap --compiler=icc </pre> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>For icc 8.0 you must add `LDFLAGS=-static-libcxa' to this.</p> <p>For icc 8.1 you must add `LDFLAGS=-i-static' instead.</p> @@ -1437,7 +1440,7 @@ ICCBASE= /opt/intel/cc/10.1.008 dependency on the icc libraries until this is fixed in libtool.</p> </div> -<div class="sect2" title="3.3.6. OpenBSD"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="openbsd"></a>3.3.6. OpenBSD</h3></div></div></div> <p>OpenBSD 5.1 has been tested and supported, @@ -1478,7 +1481,7 @@ ICCBASE= /opt/intel/cc/10.1.008 </li> </ol></div> </div> -<div class="sect2" title="3.3.7. Solaris"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="solaris"></a>3.3.7. Solaris</h3></div></div></div> <p>Solaris 2.6 through 10 are supported on both x86 and sparc. @@ -1486,7 +1489,7 @@ ICCBASE= /opt/intel/cc/10.1.008 Sun WorkShop 5 have been tested.</p> <p>The following packages are required on Solaris 8 for the bootstrap process and to build packages.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>SUNWsprot</p></li> <li class="listitem"><p>SUNWarc</p></li> <li class="listitem"><p>SUNWbtool</p></li> @@ -1499,7 +1502,7 @@ ICCBASE= /opt/intel/cc/10.1.008 your $prefix are in your <code class="varname">PATH</code>. This includes <code class="filename">/usr/ccs/{bin,lib}</code> and e.g. <code class="filename">/usr/pkg/{bin,sbin}</code>.</p> -<div class="sect3" title="3.3.7.1. If you are using gcc"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="solaris-gcc-note"></a>3.3.7.1. If you are using gcc</h4></div></div></div> <p>It makes life much simpler if you only use the same gcc consistently @@ -1510,12 +1513,12 @@ ICCBASE= /opt/intel/cc/10.1.008 package, then remove gcc used during bootstrapping.</p> <p>Binary packages of gcc can be found through <a class="ulink" href="http://www.sunfreeware.com/" target="_top">http://www.sunfreeware.com/</a>.</p> </div> -<div class="sect3" title="3.3.7.2. If you are using Sun WorkShop"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="solaris-sun-workshop-note"></a>3.3.7.2. If you are using Sun WorkShop</h4></div></div></div> <p>You will need at least the following packages installed (from WorkShop 5.0)</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>SPROcc - Sun WorkShop Compiler C 5.0</p></li> <li class="listitem"><p>SPROcpl @@ -1533,14 +1536,14 @@ CXX= CC CPP= cc -E CXXCPP= CC -E </pre> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>The <code class="varname">CPP</code> setting might break some packages that use the C preprocessor for processing things other than C source code.</p> </div> </div> -<div class="sect3" title="3.3.7.3. Building 64-bit binaries with SunPro"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="solaris-sunpro-64"></a>3.3.7.3. Building 64-bit binaries with SunPro</h4></div></div></div> <p>To build 64-bit packages, you just need to have the @@ -1549,14 +1552,14 @@ CXXCPP= CC -E PKGSRC_COMPILER= sunpro ABI= 64 </pre> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>This setting has been tested for the SPARC architecture. Intel and AMD machines need some more work.</p> </div> </div> -<div class="sect3" title="3.3.7.4. Common problems"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="plat.sunos.problems"></a>3.3.7.4. Common problems</h4></div></div></div> <p>Sometimes, when using <span class="command"><strong>libtool</strong></span>, @@ -1573,7 +1576,7 @@ WRAPPER_SHELL= ${LOCALBASE}/bin/bash </div> </div> </div> -<div class="chapter" title="Chapter 4. Using pkgsrc"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="using"></a>Chapter 4. Using pkgsrc</h2></div></div></div> <div class="toc"> @@ -1604,14 +1607,14 @@ that someone else has prepared. This is the <span class="quote">“<span cla in pkgsrc. The second way is to install the <span class="quote">“<span class="quote">src</span>”</span> of pkgsrc, too. Then you are able to build your own packages, and you can still use binary packages from someone else.</p> -<div class="sect1" title="4.1. Using binary packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="using-pkg"></a>4.1. Using binary packages</h2></div></div></div> <p>On the <a class="ulink" href="ftp://ftp.NetBSD.org/" target="_top">ftp.NetBSD.org</a> server and its mirrors, there are collections of binary packages, ready to be installed. These binary packages have been built using the default settings for the directories, that is:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <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> <li class="listitem"><p><code class="filename">/usr/pkg/etc</code> for configuration files,</p></li> <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> @@ -1619,7 +1622,7 @@ and you can still use binary packages from someone else.</p> <p>If you cannot use these directories for whatever reasons (maybe because you're not root), you cannot use these binary packages, but have to build the packages yourself, which is explained in <a class="xref" href="#bootstrapping-pkgsrc" title="3.2. Bootstrapping pkgsrc">Section 3.2, “Bootstrapping pkgsrc”</a>.</p> -<div class="sect2" title="4.1.1. Finding binary packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="finding-binary-packages"></a>4.1.1. Finding binary packages</h3></div></div></div> <p>To install binary packages, you first need to know from where @@ -1639,7 +1642,7 @@ and you can still use binary packages from someone else.</p> for managing binary packages) and <code class="filename">/var/db/pkg</code> (the database of installed packages).</p> </div> -<div class="sect2" title="4.1.2. Installing binary packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="installing-binary-packages"></a>4.1.2. Installing binary packages</h3></div></div></div> <p>In the directory from the last section, there is a @@ -1679,7 +1682,7 @@ and you can still use binary packages from someone else.</p> <code class="varname">PATH</code> so you can actually start the just installed program.</p> </div> -<div class="sect2" title="4.1.3. Deinstalling packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="using.pkg_delete"></a>4.1.3. Deinstalling packages</h3></div></div></div> <p>To deinstall a package, it does not matter whether it was @@ -1705,13 +1708,13 @@ and you can still use binary packages from someone else.</p> will remove jpeg and all the packages that used it; this allows upgrading the jpeg package.</p> </div> -<div class="sect2" title="4.1.4. Getting information about installed packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="using.pkg_info"></a>4.1.4. Getting information about installed packages</h3></div></div></div> <p>The <span class="command"><strong>pkg_info</strong></span> shows information about installed packages or binary package files.</p> </div> -<div class="sect2" title="4.1.5. Checking for security vulnerabilities in installed packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="vulnerabilities"></a>4.1.5. Checking for security vulnerabilities in installed packages</h3></div></div></div> <p> @@ -1762,7 +1765,7 @@ and you can still use binary packages from someone else.</p> <p> </p> </div> -<div class="sect2" title="4.1.6. Finding if newer versions of your installed packages are in pkgsrc"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="pkg_versions"></a>4.1.6. Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div> <p> @@ -1779,13 +1782,13 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 package on your system and rebuild any dependencies. </p> </div> -<div class="sect2" title="4.1.7. Other administrative functions"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="using.pkg_admin"></a>4.1.7. Other administrative functions</h3></div></div></div> <p>The <span class="command"><strong>pkg_admin</strong></span> executes various administrative functions on the package system.</p> </div> -<div class="sect2" title="4.1.8. A word of warning"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="a-word-of-warning"></a>4.1.8. A word of warning</h3></div></div></div> <p>Please pay very careful attention to the warnings @@ -1801,7 +1804,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 involved.</p> </div> </div> -<div class="sect1" title="4.2. Building packages from source"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="building-packages-from-source"></a>4.2. Building packages from source</h2></div></div></div> <p>After obtaining pkgsrc, the <code class="filename">pkgsrc</code> @@ -1819,7 +1822,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 <p>The rest of this chapter assumes that the package is already in pkgsrc. If it is not, see <a class="xref" href="#developers-guide" title="Part II. The pkgsrc developer's guide">Part II, “The pkgsrc developer's guide”</a> for instructions how to create your own packages.</p> -<div class="sect2" title="4.2.1. Requirements"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="requirements"></a>4.2.1. Requirements</h3></div></div></div> <p>To build packages from source, you need a working C @@ -1829,7 +1832,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 <span class="quote">“<span class="quote">xbase</span>”</span> and <span class="quote">“<span class="quote">xcomp</span>”</span> distribution sets are required, too.</p> </div> -<div class="sect2" title="4.2.2. Fetching distfiles"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="fetching-distfiles"></a>4.2.2. Fetching distfiles</h3></div></div></div> <p>The first step for building a package is downloading the @@ -1879,7 +1882,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 also choose to download the files manually. </p> </div> -<div class="sect2" title="4.2.3. How to build and install"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="how-to-build-and-install"></a>4.2.3. How to build and install</h3></div></div></div> <p> @@ -1888,7 +1891,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 computer, and how many other packages the software depends on and their compile time. </p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>If using bootstrap or pkgsrc on a non-NetBSD system, use the pkgsrc <span class="command"><strong>bmake</strong></span> command instead of @@ -2010,7 +2013,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00 </div> </div> </div> -<div class="chapter" title="Chapter 5. Configuring pkgsrc"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="configuring"></a>Chapter 5. Configuring pkgsrc</h2></div></div></div> <div class="toc"> @@ -2046,7 +2049,7 @@ is done by setting variables in this file. Note that you can define all kinds of variables, and no special error checking (for example for spelling mistakes) takes place, so you have to try it out to see if it works.</p> -<div class="sect1" title="5.1. General configuration"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="general-configuration"></a>5.1. General configuration</h2></div></div></div> <p>In this section, you can find some variables that apply to all @@ -2054,7 +2057,7 @@ works.</p> configured by the user is available in <code class="filename">mk/defaults/mk.conf</code>, together with some comments that describe each variable's intent.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">LOCALBASE</code>: Where packages will be installed. The default is <code class="filename">/usr/pkg</code>. Do not mix binary packages @@ -2098,12 +2101,12 @@ works.</p> instructions on how to change this variable.</p></li> </ul></div> </div> -<div class="sect1" title="5.2. Variables affecting the build process"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="variables-affecting-build"></a>5.2. Variables affecting the build process</h2></div></div></div> <p>XXX </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">PACKAGES</code>: The top level directory for the binary packages. The default is <code class="filename">${PKGSRCDIR}/packages</code>.</p></li> @@ -2136,14 +2139,14 @@ works.</p> packages after installing dependencies.</p></li> </ul></div> </div> -<div class="sect1" title="5.3. Variables affecting the installation process"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="variables-affecting-installation"></a>5.3. Variables affecting the installation process</h2></div></div></div> <p>Most packages support installation into a subdirectory of <code class="varname">WRKDIR</code>. This allows a package to be built, before the actual filesystem is touched. DESTDIR support exists in two variations:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Basic DESTDIR support means that the package installation and packaging is still run as root.</p></li> <li class="listitem"><p>Full DESTDIR support can run the complete @@ -2212,21 +2215,21 @@ uid=1000(myusername) gid=100(users) groups=100(users),0(wheel) </p> </div> -<div class="sect1" title="5.4. Selecting and configuring the compiler"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="conf.compiler"></a>5.4. Selecting and configuring the compiler</h2></div></div></div> -<div class="sect2" title="5.4.1. Selecting the compiler"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="selecting-the-compiler"></a>5.4.1. Selecting the compiler</h3></div></div></div> <p>By default, pkgsrc will use GCC to build packages. This may be overridden by setting the following variables in /etc/mk.conf:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt> <dd> <p>This is a list of values specifying the chain of compilers to invoke when building packages. Valid values are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">distcc</code>: distributed C/C++ (chainable)</p></li> <li class="listitem"><p><code class="varname">ccache</code>: @@ -2258,7 +2261,7 @@ uid=1000(myusername) gid=100(users) groups=100(users),0(wheel) install one of the GCC packages to use instead.</p></dd> </dl></div> </div> -<div class="sect2" title="5.4.2. Additional flags to the compiler (CFLAGS)"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf.cflags"></a>5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div> <p>If you wish to set the <code class="varname">CFLAGS</code> variable, @@ -2274,7 +2277,7 @@ CFLAGS+= -your -flags package if you're interested in optimization specifically for the current CPU. </p> </div> -<div class="sect2" title="5.4.3. Additional flags to the linker (LDFLAGS)"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf.ldflags"></a>5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div> <p>If you want to pass flags to the linker, both in the configure @@ -2292,17 +2295,17 @@ LDFLAGS+= -your -linkerflags </pre> </div> </div> -<div class="sect1" title="5.5. Developer/advanced settings"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="developer-advanced-settings"></a>5.5. Developer/advanced settings</h2></div></div></div> <p>XXX </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p><code class="varname">PKG_DEVELOPER</code>: Run some sanity checks that package developers want: </p> -<div class="itemizedlist"><ul class="itemizedlist" type="circle"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "> <li class="listitem"><p>make sure patches apply with zero fuzz</p></li> <li class="listitem"><p>run check-shlibs to see that all @@ -2324,7 +2327,7 @@ LDFLAGS+= -your -linkerflags <p> </p> </div> -<div class="sect1" title="5.6. Selecting Build Options"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="selecting-build-options"></a>5.6. Selecting Build Options</h2></div></div></div> <p>Some packages have build time options, usually to select @@ -2395,7 +2398,7 @@ PKG_OPTIONS.apache= suexec </pre> eventually.</p> </div> </div> -<div class="chapter" title="Chapter 6. Creating binary packages"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="binary"></a>Chapter 6. Creating binary packages</h2></div></div></div> <div class="toc"> @@ -2405,7 +2408,7 @@ PKG_OPTIONS.apache= suexec </pre> <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">6.2. Settings for creation of binary packages</a></span></dt> </dl> </div> -<div class="sect1" title="6.1. Building a single binary package"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="building-a-single-binary-package"></a>6.1. Building a single binary package</h2></div></div></div> <p>Once you have built and installed a package, you can create @@ -2431,13 +2434,13 @@ PKG_OPTIONS.apache= suexec </pre> <p>See <a class="xref" href="#submit" title="Chapter 21. Submitting and Committing">Chapter 21, <i>Submitting and Committing</i></a> for information on how to submit such a binary package.</p> </div> -<div class="sect1" title="6.2. Settings for creation of binary packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="settings-for-creationg-of-binary-packages"></a>6.2. Settings for creation of binary packages</h2></div></div></div> <p>See <a class="xref" href="#build.helpful-targets" title="17.17. Other helpful targets">Section 17.17, “Other helpful targets”</a>.</p> </div> </div> -<div class="chapter" title="Chapter 7. Creating binary packages for everything in pkgsrc (bulk builds)"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="bulk"></a>Chapter 7. Creating binary packages for everything in pkgsrc (bulk builds)</h2></div></div></div> @@ -2472,18 +2475,18 @@ source. There are two ways of getting a set of binary packages: The old bulk build system, or the new (as of 2007) parallel bulk build (pbulk) system. This chapter describes how to set them up so that the packages are most likely to be usable later.</p> -<div class="sect1" title="7.1. Think first, build later"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bulk.pre"></a>7.1. Think first, build later</h2></div></div></div> <p>Since a bulk build takes several days or even weeks to finish, you should think about the setup before you start everything. Pay attention to at least the following points:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p>If you want to upload the binary packages to ftp.NetBSD.org, make sure the setup complies to the requirements for binary packages:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="circle"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "> <li class="listitem"><p>To end up on ftp.NetBSD.org, the packages must be built by a NetBSD developer on a trusted machine (that is, where you and only you have root access).</p></li> @@ -2508,14 +2511,14 @@ deinstall packages in <code class="filename">/usr/pkg</code> (or whatever that you don't need any package during the build.</p></li> </ul></div> </div> -<div class="sect1" title="7.2. Requirements of a bulk build"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bulk.req"></a>7.2. Requirements of a bulk build</h2></div></div></div> <p>A complete bulk build requires lots of disk space. Some of the disk space can be read-only, some other must be writable. Some can be on remote filesystems (such as NFS) and some should be local. Some can be temporary filesystems, others must survive a sudden reboot.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>10 GB for the distfiles (read-write, remote, temporary)</p></li> <li class="listitem"><p>10 GB for the binary packages (read-write, remote, permanent)</p></li> <li class="listitem"><p>400 MB for the pkgsrc tree (read-only, remote, permanent)</p></li> @@ -2524,19 +2527,19 @@ temporary filesystems, others must survive a sudden reboot.</p> <li class="listitem"><p>5 GB for temporary files (read-write, local, temporary)</p></li> </ul></div> </div> -<div class="sect1" title="7.3. Running an old-style bulk build"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bulk.old"></a>7.3. Running an old-style bulk build</h2></div></div></div> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>There are two ways of doing a bulk build. The old-style one and the new-style <span class="quote">“<span class="quote">pbulk</span>”</span>. The latter is the recommended way.</p> </div> -<div class="sect2" title="7.3.1. Configuration"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="binary.configuration"></a>7.3.1. Configuration</h3></div></div></div> -<div class="sect3" title="7.3.1.1. build.conf"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="binary.bulk.build.conf"></a>7.3.1.1. <code class="filename">build.conf</code> </h4></div></div></div> @@ -2550,7 +2553,7 @@ way.</p> <code class="filename">build.conf</code> and edit it, following the comments in that file.</p> </div> -<div class="sect3" title="7.3.1.2. mk.conf"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="binary.mk.conf"></a>7.3.1.2. <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> </h4></div></div></div> @@ -2574,7 +2577,7 @@ SKIP_LICENSE_CHECK= yes can be found at the top lines of the file <code class="filename">mk/bulk/bsd.bulk-pkg.mk</code>. The most useful options of these are briefly described here.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>If you are on a slow machine, you may want to set <code class="varname">USE_BULK_BROKEN_CHECK</code> to <span class="quote">“<span class="quote">no</span>”</span>.</p></li> @@ -2589,7 +2592,7 @@ SKIP_LICENSE_CHECK= yes </ul></div> <p>Some other options are scattered in the pkgsrc infrastructure:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">ALLOW_VULNERABLE_PACKAGES</code> should be set to <code class="literal">yes</code>. The purpose of the bulk builds is creating binary packages, no matter if they @@ -2617,7 +2620,7 @@ SKIP_LICENSE_CHECK= yes available.</p></li> </ul></div> </div> -<div class="sect3" title="7.3.1.3. pre-build.local"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="pre-build.local"></a>7.3.1.3. <code class="filename">pre-build.local</code> </h4></div></div></div> @@ -2635,7 +2638,7 @@ SKIP_LICENSE_CHECK= yes which requires nearly 3 GB of disk space.</p> </div> </div> -<div class="sect2" title="7.3.2. Other environmental considerations"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="other-environmental-considerations"></a>7.3.2. Other environmental considerations</h3></div></div></div> <p>As <code class="filename">/usr/pkg</code> will be completely @@ -2660,12 +2663,12 @@ fi via ssh after the bulk build is finished or if the machine gets rebooted or crashes. You have been warned! :)</p> </div> -<div class="sect2" title="7.3.3. Operation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="operation"></a>7.3.3. Operation</h3></div></div></div> <p>Make sure you don't need any of the packages still installed.</p> -<div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Warning</h3> <p>During the bulk build, <span class="emphasis"><em>all packages, their configuration files and some more files from @@ -2690,11 +2693,11 @@ fi <code class="varname">FTP</code> in the <code class="filename">build.conf</code> file.</p> </div> -<div class="sect2" title="7.3.4. What it does"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="what-it-does"></a>7.3.4. What it does</h3></div></div></div> <p>The bulk builds consist of three steps:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term">1. pre-build</span></dt> <dd><p>The script updates your pkgsrc tree via (anon)cvs, then cleans out any broken distfiles, and removes all @@ -2722,12 +2725,12 @@ fi they can be used to debug these broken package builds later.</p> </div> -<div class="sect2" title="7.3.5. Disk space requirements"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="disk-space-requirements"></a>7.3.5. Disk space requirements</h3></div></div></div> <p>Currently, roughly the following requirements are valid for NetBSD 2.0/i386:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>10 GB - distfiles (NFS ok)</p></li> <li class="listitem"><p>8 GB - full set of all binaries (NFS ok)</p></li> <li class="listitem"><p>5 GB - temp space for compiling (local disk recommended)</p></li> @@ -2739,7 +2742,7 @@ fi be installed 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> instead of building again, so there are no cycles wasted by recompiling.</p> </div> -<div class="sect2" title="7.3.6. Setting up a sandbox for chrooted builds"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="setting-up-a-sandbox"></a>7.3.6. Setting up a sandbox for chrooted builds</h3></div></div></div> <p>If you don't want all the packages nuked from a machine @@ -2763,41 +2766,41 @@ fi <code class="filename">/usr/src/etc</code>, be sure the following items are present and properly configured:</p> <div class="procedure"><ol class="procedure" type="1"> -<li class="step" title="Step 1"> +<li class="step"> <p>Kernel</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cp /netbsd /usr/sandbox</code></strong></pre> </li> -<li class="step" title="Step 2"> +<li class="step"> <p><code class="filename">/dev/*</code></p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sandbox/dev ; sh MAKEDEV all</code></strong></pre> </li> -<li class="step" title="Step 3"> +<li class="step"> <p><code class="filename">/etc/resolv.conf</code> (for <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/smtpd/README.html" target="_top"><code class="filename">security/smtpd</code></a> and mail):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cp /etc/resolv.conf /usr/sandbox/etc</code></strong></pre> </li> -<li class="step" title="Step 4"> +<li class="step"> <p>Working(!) mail config (hostname, sendmail.cf):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cp /etc/mail/sendmail.cf /usr/sandbox/etc/mail</code></strong></pre> </li> -<li class="step" title="Step 5"> +<li class="step"> <p><code class="filename">/etc/localtime</code> (for <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/smtpd/README.html" target="_top"><code class="filename">security/smtpd</code></a>):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>ln -sf /usr/share/zoneinfo/UTC /usr/sandbox/etc/localtime</code></strong></pre> </li> -<li class="step" title="Step 6"> +<li class="step"> <p><code class="filename">/usr/src</code> (system sources, e. g. for <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/aperture/README.html" target="_top"><code class="filename">sysutils/aperture</code></a>):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>ln -s ../disk1/cvs .</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>ln -s cvs/src-2.0 src</code></strong></pre> </li> -<li class="step" title="Step 7"> +<li class="step"> <p>Create <code class="filename">/var/db/pkg</code> (not part of default install):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>mkdir /usr/sandbox/var/db/pkg</code></strong></pre> </li> -<li class="step" title="Step 8"> +<li class="step"> <p>Create <code class="filename">/usr/pkg</code> (not part of default install):</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>mkdir /usr/sandbox/usr/pkg</code></strong></pre> </li> -<li class="step" title="Step 9"> +<li class="step"> <p>Checkout pkgsrc via cvs into <code class="filename">/usr/sandbox/usr/pkgsrc</code>:</p> <pre class="screen"> @@ -2807,12 +2810,12 @@ fi <p>Do not mount/link this to the copy of your pkgsrc tree you do development in, as this will likely cause problems!</p> </li> -<li class="step" title="Step 10"><p>Make +<li class="step"><p>Make <code class="filename">/usr/sandbox/usr/pkgsrc/packages</code> and <code class="filename">.../distfiles</code> point somewhere appropriate. NFS- and/or nullfs-mounts may come in handy!</p></li> -<li class="step" title="Step 11"><p>Edit <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, see <a class="xref" href="#binary.mk.conf" title="7.3.1.2. mk.conf">Section 7.3.1.2, “<code class="filename">mk.conf</code>”</a>.</p></li> -<li class="step" title="Step 12"><p>Adjust <code class="filename">mk/bulk/build.conf</code> to suit your needs.</p></li> +<li class="step"><p>Edit <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, see <a class="xref" href="#binary.mk.conf" title="7.3.1.2. mk.conf">Section 7.3.1.2, “<code class="filename">mk.conf</code>”</a>.</p></li> +<li class="step"><p>Adjust <code class="filename">mk/bulk/build.conf</code> to suit your needs.</p></li> </ol></div> <p>When the chroot sandbox is set up, you can start the build with the following steps:</p> @@ -2826,7 +2829,7 @@ fi <code class="filename">/usr/sandbox/usr/pkgsrc/packages</code> (wherever that points/mounts to/from).</p> </div> -<div class="sect2" title="7.3.7. Building a partial set of packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="building-a-partial-set"></a>7.3.7. Building a partial set of packages</h3></div></div></div> <p>In addition to building a complete set of all packages in @@ -2834,7 +2837,7 @@ fi may be used to build a subset of the packages contained in pkgsrc. By setting <code class="varname">SPECIFIC_PKGS</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the variables</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>SITE_SPECIFIC_PKGS</p></li> <li class="listitem"><p>HOST_SPECIFIC_PKGS</p></li> <li class="listitem"><p>GROUP_SPECIFIC_PKGS</p></li> @@ -2849,7 +2852,7 @@ fi needed for your site available without the overhead of building extra packages that are not needed.</p> </div> -<div class="sect2" title="7.3.8. Uploading results of a bulk build"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="bulk-upload"></a>7.3.8. Uploading results of a bulk build</h3></div></div></div> <p>This section describes how pkgsrc developers can upload binary @@ -2921,15 +2924,15 @@ nbftp% <strong class="userinput"><code>find . -type d | xargs chmod 775</code></ </pre> </div> </div> -<div class="sect1" title="7.4. Running a pbulk-style bulk build"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bulk.pbulk"></a>7.4. Running a pbulk-style bulk build</h2></div></div></div> <p>Running a pbulk-style bulk build works roughly as follows:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>First, build the pbulk infrastructure in a fresh pkgsrc location.</p></li> <li class="listitem"><p>Then, build each of the packages from a clean installation directory using the infrastructure.</p></li> </ul></div> -<div class="sect2" title="7.4.1. Preparation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="bulk.pbulk.prepare"></a>7.4.1. Preparation</h3></div></div></div> <p>First, you need to create a pkgsrc installation for the pbulk infrastructure. No matter on which platform you are (even on NetBSD), you should bootstrap into its own directory. Let's take the directory <code class="filename">/usr/pbulk</code> or <code class="filename">$HOME/pbulk</code> for it. This installation will be bootstrapped and all the tools that are required for the bulk build will be installed there.</p> @@ -2939,7 +2942,7 @@ $ <strong class="userinput"><code>./bootstrap/bootstrap --prefix=/usr/pbulk --va $ <strong class="userinput"><code>rm -rf /tmp/pbulk-bootstrap</code></strong> </pre> <p>Now the basic environment for the pbulk infrastructure is installed. The specific tools are still missing. This is a good time to edit the pkgsrc configuration file <code class="filename">/usr/pbulk/etc/mk.conf</code> to fit your needs. Typical things you might set now are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="literal"><code class="varname">PKG_DEVELOPER</code>=yes</code>, to enable many consistency checks,</p></li> <li class="listitem"><p><code class="literal"><code class="varname">WRKOBJDIR</code>=/tmp/pbulk-outer</code>, to keep <code class="filename">/usr/pkgsrc</code> free from any modifications,</p></li> <li class="listitem"><p><code class="literal"><code class="varname">DISTDIR</code>=/distfiles</code>, to have only one directory in which all distfiles (for the infrastructure and for the actual packages) are downloaded,</p></li> @@ -2954,14 +2957,14 @@ $ <strong class="userinput"><code>rm -rf /tmp/pbulk-outer</code></strong> </pre> <p>Now the pbulk infrastructure is built and installed. It still needs to be configured, and after some more preparation, we will be able to start the real bulk build.</p> </div> -<div class="sect2" title="7.4.2. Configuration"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="bulk.pbulk.conf"></a>7.4.2. Configuration</h3></div></div></div> <p>TODO; see pkgsrc/doc/HOWTO-pbulk for more information.</p> <p>TODO: continue writing</p> </div> </div> -<div class="sect1" title="7.5. Creating a multiple CD-ROM packages collection"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="creating-cdroms"></a>7.5. Creating a multiple CD-ROM packages collection</h2></div></div></div> <p>After your pkgsrc bulk-build has completed, you may wish to @@ -2972,7 +2975,7 @@ $ <strong class="userinput"><code>rm -rf /tmp/pbulk-outer</code></strong> <span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a way that keeps all the dependencies for a given package on the same CD as that package.</p> -<div class="sect2" title="7.5.1. Example of cdpack"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="cdpack-example"></a>7.5.1. Example of cdpack</h3></div></div></div> <p>Complete documentation for cdpack is found in the cdpack(1) @@ -3007,7 +3010,7 @@ $ <strong class="userinput"><code>rm -rf /tmp/pbulk-outer</code></strong> </div> </div> </div> -<div class="chapter" title="Chapter 8. Directory layout of the installed files"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="files"></a>Chapter 8. Directory layout of the installed files</h2></div></div></div> <div class="toc"> @@ -3044,7 +3047,7 @@ PKG_DBDIR= ${HOME}/pkg/var/db/pkg </pre> <p>What these four directories are for, and what they look like is explained below.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">LOCALBASE</code> corresponds to the <code class="filename">/usr</code> directory in the base system. It is the <span class="quote">“<span class="quote">main</span>”</span> directory where the files are installed and contains @@ -3061,13 +3064,13 @@ operation.</p></li> files of the packages, as well as pkgsrc's <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> itself.</p></li> </ul></div> -<div class="sect1" title="8.1. File system layout in ${LOCALBASE}"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="files.localbase"></a>8.1. File system layout in <code class="literal">${LOCALBASE}</code> </h2></div></div></div> <p>The following directories exist in a typical pkgsrc installation in <code class="filename">${LOCALBASE}</code>.</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">bin</code></span></dt> <dd><p>Contains executable programs that are intended to be directly used by the end user.</p></dd> @@ -3127,11 +3130,11 @@ that may be modified after installation.</p></dd> </dl></div> </div> -<div class="sect1" title="8.2. File system layout in ${VARBASE}"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="files.varbase"></a>8.2. File system layout in <code class="literal">${VARBASE}</code> </h2></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">db/pkg</code> (the usual location of <code class="filename">${PKG_DBDIR}</code>)</span></dt> <dd><p>Contains @@ -3148,7 +3151,7 @@ currently running.</p></dd> </dl></div> </div> </div> -<div class="chapter" title="Chapter 9. Frequently Asked Questions"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="faq"></a>Chapter 9. Frequently Asked Questions</h2></div></div></div> <div class="toc"> @@ -3177,11 +3180,11 @@ currently running.</p></dd> <p>This section contains hints, tips & tricks on special things in pkgsrc that we didn't find a better place for in the previous chapters, and it contains items for both pkgsrc users and developers.</p> -<div class="sect1" title="9.1. Are there any mailing lists for pkg-related discussion?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="mailing-list-pointers"></a>9.1. Are there any mailing lists for pkg-related discussion?</h2></div></div></div> <p>The following mailing lists may be of interest to pkgsrc users:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-users" target="_top">pkgsrc-users</a>: This is a general purpose list for most issues regarding pkgsrc, regardless of platform, e.g. soliciting user help @@ -3208,14 +3211,14 @@ it contains items for both pkgsrc users and developers.</p> <p>Archives for all these mailing lists are available from <a class="ulink" href="http://mail-index.NetBSD.org/" target="_top">http://mail-index.NetBSD.org/</a>.</p> </div> -<div class="sect1" title="9.2. Where's the pkgviews documentation?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="pkgviews-docs"></a>9.2. Where's the pkgviews documentation?</h2></div></div></div> <p>Pkgviews is tightly integrated with buildlink. You can find a pkgviews User's guide in <code class="filename">pkgsrc/mk/buildlink3/PKGVIEWS_UG</code>.</p> </div> -<div class="sect1" title="9.3. Utilities for package management (pkgtools)"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="faq-pkgtools"></a>9.3. Utilities for package management (pkgtools)</h2></div></div></div> <p>The directory <code class="filename">pkgsrc/pkgtools</code> contains @@ -3224,10 +3227,10 @@ section attempts only to make the reader aware of the utilities and when they might be useful, and not to duplicate the documentation that comes with each package.</p> <p>Utilities used by pkgsrc (automatically installed when needed):</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/README.html" target="_top"><code class="filename">pkgtools/x11-links</code></a>: +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/README.html" target="_top"><code class="filename">pkgtools/x11-links</code></a>: Symlinks for use by buildlink.</p></li></ul></div> <p>OS tool augmentation (automatically installed when needed):</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/digest/README.html" target="_top"><code class="filename">pkgtools/digest</code></a>: Calculates various kinds of checksums (including SHA1).</p></li> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libnbcompat/README.html" target="_top"><code class="filename">pkgtools/libnbcompat</code></a>: @@ -3240,7 +3243,7 @@ with each package.</p> systems where pkg_install is not present.</p></li> </ul></div> <p>Utilities used by pkgsrc (not automatically installed):</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html" target="_top"><code class="filename">pkgtools/pkg_tarup</code></a>: Create a binary package from an already-installed package. Used by <span class="command"><strong>make replace</strong></span> to @@ -3257,7 +3260,7 @@ with each package.</p> </ul></div> <p>Utilities for keeping track of installed packages, being up to date, etc:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a>: Reports on packages whose installed versions do not match the latest pkgsrc entries.</p></li> @@ -3274,7 +3277,7 @@ etc:</p> packages you have installed.</p></li> </ul></div> <p>Utilities for people maintaining or creating individual packages:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a>: Automate making and maintaining patches for a package (includes pkgdiff, pkgvi, mkpatches, etc.).</p></li> @@ -3286,14 +3289,14 @@ etc:</p> </ul></div> <p>Utilities for people maintaining pkgsrc (or: more obscure pkg utilities)</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_comp/README.html" target="_top"><code class="filename">pkgtools/pkg_comp</code></a>: Build packages in a chrooted area.</p></li> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libkver/README.html" target="_top"><code class="filename">pkgtools/libkver</code></a>: Spoof kernel version for chrooted cross builds.</p></li> </ul></div> </div> -<div class="sect1" title="9.4. How to use pkgsrc as non-root"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="non-root-pkgsrc"></a>9.4. How to use pkgsrc as non-root</h2></div></div></div> <p>If you want to use pkgsrc as non-root user, you can set some @@ -3314,7 +3317,7 @@ installation targets. These directories can be overridden by the <span class="quote">“<span class="quote">--prefix</span>”</span> flag provided by the script, as well as some others that allow finer tuning of the tree layout.</p> </div> -<div class="sect1" title="9.5. How to resume transfers when fetching distfiles?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="resume-transfers"></a>9.5. How to resume transfers when fetching distfiles?</h2></div></div></div> <p>By default, resuming transfers in pkgsrc is disabled, but you can @@ -3338,7 +3341,7 @@ like:</p> FETCH_USING= wget </pre> </div> -<div class="sect1" title="9.6. How can I install/use modular X.org from pkgsrc?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="x.org-from-pkgsrc"></a>9.6. How can I install/use modular X.org from pkgsrc?</h2></div></div></div> <p>If you want to use modular X.org from pkgsrc instead of your system's own X11 @@ -3348,13 +3351,13 @@ you will have to add the following line into <pre class="programlisting"> X11_TYPE=modular </pre> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>The DragonFly operating system defaults to using modular X.org from pkgsrc. </p> </div> </div> -<div class="sect1" title="9.7. How to fetch files from behind a firewall"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fetch-behind-firewall"></a>9.7. How to fetch files from behind a firewall</h2></div></div></div> <p>If you are sitting behind a firewall which does not allow direct @@ -3369,13 +3372,13 @@ ftp_proxy=ftp://orpheus.amdahl.com:80/ http_proxy=http://orpheus.amdahl.com:80/ </pre> </div> -<div class="sect1" title="9.8. How do I tell make fetch to do passive FTP?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="passive-ftp"></a>9.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</h2></div></div></div> <p>This depends on which utility is used to retrieve distfiles. From <code class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned the first available command from the following list:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li> <li class="listitem"><p><code class="filename">/usr/bin/ftp</code></p></li> </ul></div> @@ -3389,7 +3392,7 @@ refuses to do passive. For the other tools, add the following to your <code class="filename">/usr/bin/ftp</code> from falling back to active transfers.</p> </div> -<div class="sect1" title="9.9. How to fetch all distfiles at once"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fetching-all-distfiles"></a>9.9. How to fetch all distfiles at once</h2></div></div></div> <p>You would like to download all the distfiles in a single batch @@ -3421,7 +3424,7 @@ directly by running:</p> by running:</p> <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch NO_SKIP=yes</code></strong></pre> </div> -<div class="sect1" title="9.10. What does “Don't know how to make /usr/share/tmac/tmac.andoc” mean?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="tmac.andoc-missing"></a>9.10. What does <span class="quote">“<span class="quote">Don't know how to make /usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div> @@ -3435,7 +3438,7 @@ that to format man pages.</p> can get away with setting <code class="varname">NOMAN=YES</code> either in the environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p> </div> -<div class="sect1" title="9.11. What does “Could not find bsd.own.mk” mean?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bsd.own.mk-missing"></a>9.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</h2></div></div></div> <p>You didn't install the compiler set, <code class="filename">comp.tgz</code>, @@ -3447,7 +3450,7 @@ extracting it in <code class="filename">/</code>:</p> the one that corresponds to your release (determine via <span class="command"><strong>uname -r</strong></span>).</p> </div> -<div class="sect1" title="9.12. Using 'sudo' with pkgsrc"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="using-sudo-with-pkgsrc"></a>9.12. Using 'sudo' with pkgsrc</h2></div></div></div> <p>When installing packages as non-root user and using the just-in-time @@ -3465,7 +3468,7 @@ SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c .endif </pre> </div> -<div class="sect1" title="9.13. How do I change the location of configuration files?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="faq.conf"></a>9.13. How do I change the location of configuration files?</h2></div></div></div> <p>As the system administrator, you can choose where configuration files @@ -3487,7 +3490,7 @@ package you would like to modify, that is, the contents of <p>Note that after changing these settings, you must rebuild and reinstall any affected packages.</p> </div> -<div class="sect1" title="9.14. Automated security checks"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="audit-packages"></a>9.14. Automated security checks</h2></div></div></div> <p>Please be aware that there can often be bugs in third-party software, @@ -3520,7 +3523,7 @@ pkg_install</code></strong>.</p> perform a security check before building any package. See <a class="xref" href="#variables-affecting-build" title="5.2. Variables affecting the build process">Section 5.2, “Variables affecting the build process”</a> for ways to control this check.</p> </div> -<div class="sect1" title="9.15. Why do some packages ignore my CFLAGS?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ufaq-cflags"></a>9.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</h2></div></div></div> <p>When you add your own preferences to the @@ -3542,28 +3545,28 @@ check.</p> specific combination of <code class="varname">CFLAGS</code> they have chosen.</p> </div> -<div class="sect1" title="9.16. A package does not build. What shall I do?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ufaq-fail"></a>9.16. A package does not build. What shall I do?</h2></div></div></div> <div class="procedure"><ol class="procedure" type="1"> -<li class="step" title="Step 1"><p>Make sure that your copy of pkgsrc is consistent. A +<li class="step"><p>Make sure that your copy of pkgsrc is consistent. A case that occurs often is that people only update pkgsrc in parts, because of performance reasons. Since pkgsrc is one large system, not a collection of many small systems, there are sometimes changes that only work when the whole pkgsrc tree is updated.</p></li> -<li class="step" title="Step 2"><p>Make sure that you don't have any CVS conflicts. +<li class="step"><p>Make sure that you don't have any CVS conflicts. Search for <span class="quote">“<span class="quote"><<<<<<</span>”</span> or <span class="quote">“<span class="quote">>>>>>></span>”</span> in all your pkgsrc files.</p></li> -<li class="step" title="Step 3"><p>Make sure that you don't have old copies of the packages +<li class="step"><p>Make sure that you don't have old copies of the packages extracted. Run <span class="command"><strong>make clean clean-depends</strong></span> to verify this.</p></li> -<li class="step" title="Step 4"><p>If the problem still exists, write a mail to the +<li class="step"><p>If the problem still exists, write a mail to the <code class="literal">pkgsrc-users</code> mailing list.</p></li> </ol></div> </div> -<div class="sect1" title="9.17. What does “Makefile appears to contain unresolved cvs/rcs/??? merge conflicts” mean?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="faq.rcs-conflicts"></a>9.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</h2></div></div></div> <p>You have modified a file from pkgsrc, and someone else has @@ -3578,10 +3581,10 @@ anymore, you can remove that file and run <span class="command"><strong>cvs -q u </div> </div> </div> -<div class="part" title="Part II. The pkgsrc developer's guide"> +<div class="part"> <div class="titlepage"><div><div><h1 class="title"> <a name="developers-guide"></a>Part II. The pkgsrc developer's guide</h1></div></div></div> -<div class="partintro" title="The pkgsrc developer's guide"> +<div class="partintro"> <div></div> <p>This part of the book deals with creating and modifying packages. It starts with a <span class="quote">“<span class="quote">HOWTO</span>”</span>-like @@ -3817,7 +3820,7 @@ anymore, you can remove that file and run <span class="command"><strong>cvs -q u </dl> </div> </div> -<div class="chapter" title="Chapter 10. Creating a new pkgsrc package from scratch"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="creating"></a>Chapter 10. Creating a new pkgsrc package from scratch</h2></div></div></div> <div class="toc"> @@ -3838,20 +3841,20 @@ most likely have a URL from where you can download the source code. Starting with this URL, creating a package involves only a few steps.</p> <div class="procedure"><ol class="procedure" type="1"> -<li class="step" title="Step 1"><p>First, install the packages <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a> and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>.</p></li> -<li class="step" title="Step 2"><p>Then, choose one of the top-level directories as the +<li class="step"><p>First, install the packages <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a> and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>.</p></li> +<li class="step"><p>Then, choose one of the top-level directories as the category in which you want to place your package. You can also create a directory of your own (maybe called <code class="filename">local</code>). In that category directory, create another directory for your package and change into it.</p></li> -<li class="step" title="Step 3"><p>Run the program <span class="command"><strong>url2pkg</strong></span>, which will ask +<li class="step"><p>Run the program <span class="command"><strong>url2pkg</strong></span>, which will ask you for a URL. Enter the URL of the distribution file (in most cases a <code class="filename">.tar.gz</code> file) and watch how the basic ingredients of your package are created automatically. The distribution file is extracted automatically to fill in some details in the <code class="filename">Makefile</code> that would otherwise have to be done manually.</p></li> -<li class="step" title="Step 4"> +<li class="step"> <p>Examine the extracted files to determine the dependencies of your package. Ideally, this is mentioned in some <code class="filename">README</code> file, but things may differ. For each of @@ -3882,59 +3885,59 @@ DEPENDS+= screen>=4.0:../../misc/screen .include "../../mk/bsd.pkg.mk" </pre> </li> -<li class="step" title="Step 5"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need +<li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint --explain</strong></span> or <span class="command"><strong>pkglint -e</strong></span>, which outputs additional explanations.</p></li> -<li class="step" title="Step 6"><p>In many cases the package is not yet ready to build. You can +<li class="step"><p>In many cases the package is not yet ready to build. You can find instructions for the most common cases in the next section, <a class="xref" href="#creating.common" title="10.1. Common types of packages">Section 10.1, “Common types of packages”</a>. After you have followed the instructions over there, you can hopefully continue here.</p></li> -<li class="step" title="Step 7"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working +<li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working directory from the extracted files. Besides these files, a lot of cache files and other system information has been saved in the working directory, which may become wrong after you edited the <code class="filename">Makefile</code>.</p></li> -<li class="step" title="Step 8"><p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For +<li class="step"><p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For the various things that can go wrong in this phase, consult <a class="xref" href="#fixes" title="Chapter 19. Making your package work">Chapter 19, <i>Making your package work</i></a>.</p></li> -<li class="step" title="Step 9"><p>When the package builds fine, the next step is to install +<li class="step"><p>When the package builds fine, the next step is to install the package. Run <span class="command"><strong>bmake install</strong></span> and hope that everything works.</p></li> -<li class="step" title="Step 10"><p>Up to now, the file <code class="filename">PLIST</code>, which +<li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which contains a list of the files that are installed by the package, is nearly empty. Run <span class="command"><strong>bmake print-PLIST >PLIST</strong></span> to generate a probably correct list. Check the file using your preferred text editor to see if the list of files looks plausible.</p></li> -<li class="step" title="Step 11"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated +<li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated <code class="filename">PLIST</code> contains garbage or not.</p></li> -<li class="step" title="Step 12"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package +<li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package has been registered in the database of installed files, but with an empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span> and <span class="command"><strong>bmake install</strong></span> again. Now the package is registered with the list of files from <code class="filename">PLIST</code>.</p></li> -<li class="step" title="Step 13"><p>Run <span class="command"><strong>bmake package</strong></span> to create a binary +<li class="step"><p>Run <span class="command"><strong>bmake package</strong></span> to create a binary package from the set of installed files.</p></li> </ol></div> -<div class="sect1" title="10.1. Common types of packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="creating.common"></a>10.1. Common types of packages</h2></div></div></div> -<div class="sect2" title="10.1.1. Perl modules"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="creating.perl-module"></a>10.1.1. Perl modules</h3></div></div></div> <p>Simple Perl modules are handled automatically by <span class="command"><strong>url2pkg</strong></span>, including dependencies.</p> </div> -<div class="sect2" title="10.1.2. KDE applications"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="creating.kde-app"></a>10.1.2. KDE applications</h3></div></div></div> <p>KDE applications should always include <code class="filename">meta-pkgs/kde3/kde3.mk</code>, which contains numerous settings that are typical of KDE packages.</p> </div> -<div class="sect2" title="10.1.3. Python modules and programs"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="creating.python-module"></a>10.1.3. Python modules and programs</h3></div></div></div> <p>Python modules and programs packages are easily created using a @@ -3984,13 +3987,13 @@ REPLACE_PYTHON= *.py </pre> </div> </div> -<div class="sect1" title="10.2. Examples"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="creating.examples"></a>10.2. Examples</h2></div></div></div> -<div class="sect2" title="10.2.1. How the www/nvu package came into pkgsrc"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="creating.nvu"></a>10.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div> -<div class="sect3" title="10.2.1.1. The initial package"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="creating.nvu.init"></a>10.2.1.1. The initial package</h4></div></div></div> <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw @@ -4053,7 +4056,7 @@ Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done! Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-) </pre> </div> -<div class="sect3" title="10.2.1.2. Fixing all kinds of problems to make the package work"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="creating.nvu.problems"></a>10.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div> <p>Now that the package has been extracted, let's see what's inside @@ -4189,7 +4192,7 @@ which patch files were relevant for this issue and copied them to the patches so that they applied cleanly and retried again. This time, everything worked.</p> </div> -<div class="sect3" title="10.2.1.3. Installing the package"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="creating.nvu.inst"></a>10.2.1.3. Installing the package</h4></div></div></div> <pre class="programlisting"> @@ -4203,7 +4206,7 @@ everything worked.</p> </div> </div> </div> -<div class="chapter" title="Chapter 11. Package components - files, directories and contents"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="components"></a>Chapter 11. Package components - files, directories and contents</h2></div></div></div> <div class="toc"> @@ -4233,7 +4236,7 @@ everything worked.</p> <p>Whenever you're preparing a package, there are a number of files involved which are described in the following sections.</p> -<div class="sect1" title="11.1. Makefile"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="components.Makefile"></a>11.1. <code class="filename">Makefile</code> </h2></div></div></div> @@ -4248,7 +4251,7 @@ sections.</p> should appear exactly in the order given here. The order and grouping of the variables is mostly historical and has no further meaning.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">DISTNAME</code> is the basename of the distribution file to be downloaded from the package's website.</p></li> @@ -4297,7 +4300,7 @@ converters games mbone print x11 <p>The second section contains information about separately downloaded patches, if any. </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">PATCHFILES:</code> Name(s) of additional files that contain distribution patches. There is no default. pkgsrc will look for them at @@ -4311,7 +4314,7 @@ converters games mbone print x11 </ul></div> <p>The third section contains the following variables. </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">MAINTAINER</code> is the email address of the person who feels responsible for this package, and who is most likely to look at problems or questions regarding @@ -4336,7 +4339,7 @@ converters games mbone print x11 </ul></div> <p>Other variables that affect the build: </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> <p><code class="varname">WRKSRC</code>: The directory where the interesting distribution files of the package are found. The default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which @@ -4368,7 +4371,7 @@ converters games mbone print x11 <code class="filename">work.sparc</code>.</p> </li></ul></div> <p>Please pay attention to the following gotchas:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are installed in compressed form by the package. For packages using BSD-style makefiles which honor MANZ, there is @@ -4379,7 +4382,7 @@ converters games mbone print x11 <li class="listitem"><p>If the package installs any info files, see <a class="xref" href="#faq.info-files" title="19.6.7. Packages installing info files">Section 19.6.7, “Packages installing info files”</a>.</p></li> </ul></div> </div> -<div class="sect1" title="11.2. distinfo"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="components.distinfo"></a>11.2. <code class="filename">distinfo</code> </h2></div></div></div> @@ -4402,7 +4405,7 @@ converters games mbone print x11 upgrading such a package to ensure distfile information is not lost.</p> </div> -<div class="sect1" title="11.3. patches/*"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="components.patches"></a>11.3. patches/*</h2></div></div></div> <p>Many packages still don't work out-of-the box on the various @@ -4413,7 +4416,7 @@ converters games mbone print x11 applied to the files in <code class="varname">WRKSRC</code> directory after extracting them, in <a class="ulink" href="http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13_03" target="_top">alphabetic order</a>.</p> -<div class="sect2" title="11.3.1. Structure of a single patch file"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.patch.structure"></a>11.3.1. Structure of a single patch file</h3></div></div></div> <p>The <code class="filename">patch-*</code> files should be in @@ -4428,7 +4431,7 @@ converters games mbone print x11 empty for aesthetic reasons. After that, there should be a comment for each change that the patch does. There are a number of standard cases:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Patches for commonly known vulnerabilities should mention the vulnerability ID (CAN, CVE).</p></li> <li class="listitem"><p>Patches that change source code should mention the @@ -4441,7 +4444,7 @@ converters games mbone print x11 since we generally want that they accept our patches, so we have less work in the future.</p> </div> -<div class="sect2" title="11.3.2. Creating patch files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.patches.caveats"></a>11.3.2. Creating patch files</h3></div></div></div> <p>One important thing to mention is to pay attention that no RCS @@ -4477,7 +4480,7 @@ converters games mbone print x11 <span class="command"><strong>mkpatches</strong></span> included in <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> takes care of the name automatically.</p> </div> -<div class="sect2" title="11.3.3. Sources where the patch files come from"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.patches.sources"></a>11.3.3. Sources where the patch files come from</h3></div></div></div> <p>If you want to share patches between multiple packages @@ -4504,7 +4507,7 @@ PATCHDIR= ${.CURDIR}/../xemacs/patches and <span class="emphasis"><em>they are applied after pkgsrc patches are applied</em></span>.</p> </div> -<div class="sect2" title="11.3.4. Patching guidelines"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.patches.guidelines"></a>11.3.4. Patching guidelines</h3></div></div></div> <p>When fixing a portability issue in the code do not use @@ -4618,7 +4621,7 @@ monitor_file(...) collected from our experience in pkgsrc work, so they are possibly helpful when creating patches too.</p> </div> -<div class="sect2" title="11.3.5. Feedback to the author"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.patches.feedback"></a>11.3.5. Feedback to the author</h3></div></div></div> <p>Always, always, <span class="strong"><strong>always</strong></span> @@ -4641,10 +4644,10 @@ monitor_file(...) <p>Support the idea of free software!</p> </div> </div> -<div class="sect1" title="11.4. Other mandatory files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="other-mandatory-files"></a>11.4. Other mandatory files</h2></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">DESCR</code></span></dt> <dd><p>A multi-line description of the piece of software. This should include any credits where they are due. Please bear in mind that others do not @@ -4659,13 +4662,13 @@ monitor_file(...) information.</p></dd> </dl></div> </div> -<div class="sect1" title="11.5. Optional files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="components.optional"></a>11.5. Optional files</h2></div></div></div> -<div class="sect2" title="11.5.1. Files affecting the binary package"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.optional.bin"></a>11.5.1. Files affecting the binary package</h3></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">INSTALL</code></span></dt> <dd> <p>This shell script is invoked twice by <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>. @@ -4729,10 +4732,10 @@ MESSAGE_SUBST+= SOMEVAR="somevalue" alternatives framework.</p></dd> </dl></div> </div> -<div class="sect2" title="11.5.2. Files affecting the build process"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.optional.build"></a>11.5.2. Files affecting the build process</h3></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">Makefile.common</code></span></dt> <dd><p>This file contains arbitrary things that could also go into a <code class="filename">Makefile</code>, but its purpose is @@ -4758,10 +4761,10 @@ MESSAGE_SUBST+= SOMEVAR="somevalue" <code class="filename">Makefile</code>.</p></dd> </dl></div> </div> -<div class="sect2" title="11.5.3. Files affecting nothing at all"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="components.optional.none"></a>11.5.3. Files affecting nothing at all</h3></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">README*</code></span></dt> <dd><p>These files do not take place in the creation of a package and thus are purely informative to the package @@ -4773,7 +4776,7 @@ MESSAGE_SUBST+= SOMEVAR="somevalue" </dl></div> </div> </div> -<div class="sect1" title="11.6. work*"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="work-dir"></a>11.6. <code class="filename">work*</code> </h2></div></div></div> @@ -4787,7 +4790,7 @@ MESSAGE_SUBST+= SOMEVAR="somevalue" or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code> if <code class="varname">OBJMACHINE</code> is set.</p> </div> -<div class="sect1" title="11.7. files/*"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="files-dir"></a>11.7. <code class="filename">files/*</code> </h2></div></div></div> @@ -4807,7 +4810,7 @@ FILESDIR=${.CURDIR}/../xemacs/files </pre> </div> </div> -<div class="chapter" title="Chapter 12. Programming in Makefiles"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="makefile"></a>Chapter 12. Programming in <code class="filename">Makefile</code>s</h2></div></div></div> <div class="toc"> @@ -4840,10 +4843,10 @@ FILESDIR=${.CURDIR}/../xemacs/files <p>This chapter describes some patterns, that appear quite often in <code class="filename">Makefile</code>s, including the pitfalls that come along with them.</p> -<div class="sect1" title="12.1. Caveats"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="makefile.style"></a>12.1. Caveats</h2></div></div></div> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> <p>When you are creating a file as a target of a rule, always write the data to a temporary file first and finally rename that file. Otherwise there might occur an error @@ -4873,7 +4876,7 @@ correct: when one of the commands fails (like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?false+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">false</span>(1)</span></a> above).</p> </li></ul></div> </div> -<div class="sect1" title="12.2. Makefile variables"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="makefile.variables"></a>12.2. <code class="filename">Makefile</code> variables</h2></div></div></div> <p><code class="filename">Makefile</code> variables contain strings that @@ -4911,7 +4914,7 @@ correct: of whitespace.</p> <p>There are several types of variables that should be handled differently. Strings and two types of lists.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><span class="emphasis"><em>Strings</em></span> can contain arbitrary characters. Nevertheless, you should restrict yourself to only using printable characters. Examples are @@ -4931,10 +4934,10 @@ correct: <code class="varname">DISTFILES</code> and <code class="varname">MASTER_SITES</code>.</p></li> </ul></div> -<div class="sect2" title="12.2.1. Naming conventions"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="makefile.variables.names"></a>12.2.1. Naming conventions</h3></div></div></div> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>All variable names starting with an underscore are reserved for use by the pkgsrc infrastructure. They shall not be used by package @@ -4948,13 +4951,13 @@ correct: </ul></div> </div> </div> -<div class="sect1" title="12.3. Code snippets"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="makefile.code"></a>12.3. Code snippets</h2></div></div></div> <p>This section presents you with some code snippets you should use in your own code. If you don't find anything appropriate here, you should test your code and add it here.</p> -<div class="sect2" title="12.3.1. Adding things to a list"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="adding-to-list"></a>12.3.1. Adding things to a list</h3></div></div></div> <pre class="programlisting"> @@ -4975,7 +4978,7 @@ EXT_LIST+= ${ANOTHER_EXT_LIST} # 4 are sure that all entries are correctly interpreted in both lists.</p> </div> -<div class="sect2" title="12.3.2. Converting an internal list into an external list"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="converting-internal-to-external"></a>12.3.2. Converting an internal list into an external list</h3></div></div></div> <pre class="programlisting"> @@ -4990,7 +4993,7 @@ EXT_LIST+= ${i:Q}"" are unquoted they must be quoted here. The reason for appending <code class="varname">""</code> is explained below.</p> </div> -<div class="sect2" title="12.3.3. Passing variables to a shell command"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="passing-variable-to-shell"></a>12.3.3. Passing variables to a shell command</h3></div></div></div> <p>Sometimes you may want to print an arbitrary string. There @@ -5034,12 +5037,12 @@ all: <p>As internal lists shall not be passed to the shell, there is no example for it.</p> </div> -<div class="sect2" title="12.3.4. Quoting guideline"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="quoting-guideline"></a>12.3.4. Quoting guideline</h3></div></div></div> <p>There are many possible sources of wrongly quoted variables. This section lists some of the commonly known ones.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p>Whenever you use the value of a list, think about what happens to leading or trailing whitespace. If the @@ -5117,7 +5120,7 @@ for_test: </li> </ul></div> </div> -<div class="sect2" title="12.3.5. Workaround for a bug in BSD Make"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="bsd-make-bug-workaround"></a>12.3.5. Workaround for a bug in BSD Make</h3></div></div></div> <p>The pkgsrc bmake program does not handle the following @@ -5133,7 +5136,7 @@ VAR:= ${VAR:N${_othervar_:C/-//}} </div> </div> </div> -<div class="chapter" title="Chapter 13. PLIST issues"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="plist"></a>Chapter 13. PLIST issues</h2></div></div></div> <div class="toc"> @@ -5157,7 +5160,7 @@ VAR:= ${VAR:N${_othervar_:C/-//}} This chapter addresses some issues that need attention when dealing with the <code class="filename">PLIST</code> file (or files, see below!).</p> -<div class="sect1" title="13.1. RCS ID"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="rcs-id"></a>13.1. RCS ID</h2></div></div></div> <p>Be sure to add a RCS ID line as the first thing in any @@ -5166,7 +5169,7 @@ VAR:= ${VAR:N${_othervar_:C/-//}} @comment $NetBSD$ </pre> </div> -<div class="sect1" title="13.2. Semi-automatic PLIST generation"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="automatic-plist-generation"></a>13.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div> <p>You can use the <span class="command"><strong>make print-PLIST</strong></span> command @@ -5174,7 +5177,7 @@ VAR:= ${VAR:N${_othervar_:C/-//}} was extracted. See <a class="xref" href="#build.helpful-targets" title="17.17. Other helpful targets">Section 17.17, “Other helpful targets”</a> for more information on this target.</p> </div> -<div class="sect1" title="13.3. Tweaking output of make print-PLIST"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="print-PLIST"></a>13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span> </h2></div></div></div> @@ -5203,13 +5206,13 @@ PRINT_PLIST_AWK+= /^libdata\/foo/ { next; } PRINT_PLIST_AWK+= /^@dirrm share\/specific/ { print "@comment " $$0; next; } </pre> </div> -<div class="sect1" title="13.4. Variable substitution in PLIST"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="plist.misc"></a>13.4. Variable substitution in PLIST</h2></div></div></div> <p>A number of variables are substituted automatically in PLISTs when a package is installed on a system. This includes the following variables:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">${MACHINE_ARCH}</code>, <code class="varname">${MACHINE_GNU_ARCH}</code></span></dt> <dd> <p>Some packages like emacs and perl embed information @@ -5223,7 +5226,7 @@ PRINT_PLIST_AWK+= /^@dirrm share\/specific/ { print "@comment " $$0; next; <code class="varname">${MACHINE_GNU_ARCH}</code> is embedded in PLIST somewhere - use this on packages that have GNU autoconf-created configure scripts.</p> -<div class="note" title="Legacy note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Legacy note</h3> <p>There used to be a symbol <span class="quote">“<span class="quote"><code class="varname">$ARCH</code></span>”</span> that @@ -5238,7 +5241,7 @@ PRINT_PLIST_AWK+= /^@dirrm share\/specific/ { print "@comment " $$0; next; into some paths. To do this, use these variables in the <code class="filename">PLIST</code>: </p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">${OPSYS}</code> - output of <span class="quote">“<span class="quote"><span class="command"><strong>uname -s</strong></span></span>”</span></p></li> <li class="listitem"><p><code class="varname">${LOWER_OPSYS}</code> - lowercase common name (eg. <span class="quote">“<span class="quote">solaris</span>”</span>)</p></li> <li class="listitem"><p><code class="varname">${OS_VERSION}</code> - <span class="quote">“<span class="quote"><span class="command"><strong>uname -r</strong></span></span>”</span></p></li> @@ -5285,7 +5288,7 @@ ${PLIST.foo}share/bar/foo.data ${PLIST.foo}@dirrm share/bar </pre> </div> -<div class="sect1" title="13.5. Man page compression"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="manpage-compression"></a>13.5. Man page compression</h2></div></div></div> <p>Man pages should be installed in compressed form if @@ -5298,7 +5301,7 @@ ${PLIST.foo}@dirrm share/bar <code class="filename">PLIST</code> file is done on a copy of it, not <code class="filename">PLIST</code> itself.</p> </div> -<div class="sect1" title="13.6. Changing PLIST source with PLIST_SRC"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="using-PLIST_SRC"></a>13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code> </h2></div></div></div> @@ -5309,13 +5312,13 @@ ${PLIST.foo}@dirrm share/bar important. The default for <code class="varname">PLIST_SRC</code> is <code class="filename">${PKGDIR}/PLIST</code>.</p> </div> -<div class="sect1" title="13.7. Platform-specific and differing PLISTs"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="platform-specific-plist"></a>13.7. Platform-specific and differing PLISTs</h2></div></div></div> <p>Some packages decide to install a different set of files based on the operating system being used. These differences can be automatically handled by using the following files:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="filename">PLIST.common</code></p></li> <li class="listitem"><p><code class="filename">PLIST.${OPSYS}</code></p></li> <li class="listitem"><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li> @@ -5323,7 +5326,7 @@ ${PLIST.foo}@dirrm share/bar <li class="listitem"><p><code class="filename">PLIST.common_end</code></p></li> </ul></div> </div> -<div class="sect1" title="13.8. Sharing directories between packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="faq.common-dirs"></a>13.8. Sharing directories between packages</h2></div></div></div> <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where @@ -5346,7 +5349,7 @@ ${PLIST.foo}@dirrm share/bar </p> </div> </div> -<div class="chapter" title="Chapter 14. Buildlink methodology"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="buildlink"></a>Chapter 14. Buildlink methodology</h2></div></div></div> <div class="toc"> @@ -5391,7 +5394,7 @@ ${PLIST.foo}@dirrm share/bar <code class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is designed to insulate the package build from non-system-supplied software.</p> -<div class="sect1" title="14.1. Converting packages to use buildlink3"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="converting-to-buildlink3"></a>14.1. Converting packages to use buildlink3</h2></div></div></div> <p>The process of converting packages to use the buildlink3 @@ -5433,7 +5436,7 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0 <p>There are several <code class="filename">buildlink3.mk</code> files in <code class="filename">pkgsrc/mk</code> that handle special package issues:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="filename">bdb.buildlink3.mk</code> chooses either the native or a pkgsrc Berkeley DB implementation based on the values of <code class="varname">BDB_ACCEPTED</code> and @@ -5470,7 +5473,7 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0 files provide a more complete description of how to use them properly.</p> </div> -<div class="sect1" title="14.2. Writing buildlink3.mk files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="creating-buildlink3.mk"></a>14.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div> <a name="buildlink3.mk"></a><p>A package's <code class="filename">buildlink3.mk</code> file is @@ -5490,7 +5493,7 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0 <code class="prompt">%</code> <strong class="userinput"><code>cd pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>pkgdir</code></em> <code class="prompt">%</code> createbuildlink >buildlink3.mk</code></strong> </pre> -<div class="sect2" title="14.2.1. Anatomy of a buildlink3.mk file"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="anatomy-of-bl3"></a>14.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div> <p>The following real-life example @@ -5521,7 +5524,7 @@ BUILDLINK_TREE+= -tiff <p>The main section is protected from multiple inclusion and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is added. Several important variables are set in the section:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> is the actual dependency recorded in the installed package; this should always be set using @@ -5563,7 +5566,7 @@ BUILDLINK_TREE+= -tiff control which package files are symlinked into <code class="filename">${BUILDLINK_DIR}</code> and how their names are transformed during the symlinking:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code> (not shown above) is a shell glob pattern relative to <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> @@ -5609,7 +5612,7 @@ BUILDLINK_TREE+= -tiff file is included. Dependencies are only added for directly include <code class="filename">buildlink3.mk</code> files.</p> </div> -<div class="sect2" title="14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and BUILDLINK_ABI_DEPENDS.pkg in buildlink3.mk files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="updating-buildlink-depends"></a>14.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> @@ -5655,7 +5658,7 @@ BUILDLINK_TREE+= -tiff <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>. </p> </div> </div> -<div class="sect1" title="14.3. Writing builtin.mk files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="writing-builtin.mk"></a>14.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div> <p>Some packages in pkgsrc install headers and libraries that @@ -5680,7 +5683,7 @@ BUILDLINK_TREE+= -tiff is <span class="emphasis"><em>very</em></span> important and takes careful attention to <code class="filename">Makefile</code> coding.</p></li> </ol></div> -<div class="sect2" title="14.3.1. Anatomy of a builtin.mk file"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="anatomy-of-builtin.mk"></a>14.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</h3></div></div></div> <p>The following is the recommended template for builtin.mk @@ -5767,7 +5770,7 @@ CHECK_BUILTIN.foo?= no files to symlink into <code class="filename">${BUILDLINK_DIR}</code> (via <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>).</p> </div> -<div class="sect2" title="14.3.2. Global preferences for native or pkgsrc software"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="native-or-pkgsrc-preference"></a>14.3.2. Global preferences for native or pkgsrc software</h3></div></div></div> <p>When building packages, it's possible to choose whether to set @@ -5800,7 +5803,7 @@ PREFER_NATIVE= getopt skey tcp_wrappers </div> </div> </div> -<div class="chapter" title="Chapter 15. The pkginstall framework"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="pkginstall"></a>Chapter 15. The pkginstall framework</h2></div></div></div> <div class="toc"> @@ -5829,7 +5832,7 @@ PREFER_NATIVE= getopt skey tcp_wrappers </div> <p>This chapter describes the framework known as <code class="literal">pkginstall</code>, whose key features are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Generic installation and manipulation of directories and files outside the pkgsrc-handled tree, <code class="varname">LOCALBASE</code>.</p></li> <li class="listitem"><p>Automatic handling of configuration files during installation, @@ -5848,7 +5851,7 @@ using binary packages could not benefit from it at all (as the code itself could be unavailable). Therefore, the only way to achieve any of the items described above is by means of the installation scripts, which are automatically generated by pkginstall.</p> -<div class="sect1" title="15.1. Files and directories outside the installation prefix"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="files-and-dirs-outside-prefix"></a>15.1. Files and directories outside the installation prefix</h2></div></div></div> <p>As you already know, the <code class="filename">PLIST</code> file holds a list @@ -5881,12 +5884,12 @@ provides generic scripts to abstract the manipulation of such files and directories based on variables set in the package's <code class="filename">Makefile</code>. The rest of this section describes these variables.</p> -<div class="sect2" title="15.1.1. Directory manipulation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="dirs-outside-prefix"></a>15.1.1. Directory manipulation</h3></div></div></div> <p>The following variables can be set to request the creation of directories anywhere in the file system:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">MAKE_DIRS</code> and <code class="varname">OWN_DIRS</code> contain a list of directories that should be created and should attempt to be destroyed by the installation scripts. The difference between @@ -5908,7 +5911,7 @@ MAKE_DIRS_PERMS+= ${VARBASE}/foo/private ${ROOT_USER} ${ROOT_GROUP} 0700 </li> </ul></div> </div> -<div class="sect2" title="15.1.2. File manipulation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="files-outside-prefix"></a>15.1.2. File manipulation</h3></div></div></div> <p>Creating non-empty files outside the installation prefix is tricky @@ -5920,7 +5923,7 @@ generated by pkginstall). We will call the former the <span class="emphasis"><e file</em></span> in the following paragraphs, which describe the variables that can be used to automatically and consistently handle files outside the installation prefix:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p><code class="varname">CONF_FILES</code> and <code class="varname">REQD_FILES</code> are pairs of master and target files. @@ -5948,7 +5951,7 @@ REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile ${ROOT_USER} ${R </ul></div> </div> </div> -<div class="sect1" title="15.2. Configuration files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="conf-files"></a>15.2. Configuration files</h2></div></div></div> <p>Configuration files are special in the sense that they are installed @@ -5960,13 +5963,13 @@ inside <code class="varname">PKG_SYSCONFDIR</code>) during installation <span cl and only if</em></span> they didn't exist before. Similarly, they will not be removed if they have local modifications. This ensures that administrators never lose any custom changes they may have made.</p> -<div class="sect2" title="15.2.1. How PKG_SYSCONFDIR is set"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf-files-sysconfdir"></a>15.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</h3></div></div></div> <p>As said before, the <code class="varname">PKG_SYSCONFDIR</code> variable specifies where configuration files shall be installed. Its contents are set based upon the following variables:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root directory. Defaults to <code class="filename">${PREFIX}/etc</code> although it may be overridden by the user to point to his preferred location (e.g., @@ -6014,7 +6017,7 @@ automatically added to <code class="filename">OWN_DIRS</code>. See <a class="xr subdirectories of <code class="filename">${PKG_SYSCONFDIR}</code>, they still have to be created with OWN_DIRS or MAKE_DIRS.</p> </div> -<div class="sect2" title="15.2.2. Telling the software where configuration files are"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf-files-configure"></a>15.2.2. Telling the software where configuration files are</h3></div></div></div> <p>Given that pkgsrc (and users!) expect configuration files to be in a @@ -6031,7 +6034,7 @@ for</em></span> its configuration files, not where they will be originally installed (although the difference is never explicit, unfortunately).</p> </div> -<div class="sect2" title="15.2.3. Patching installations"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf-files-patching"></a>15.2.3. Patching installations</h3></div></div></div> <p>As said before, pkginstall automatically handles configuration files. @@ -6060,7 +6063,7 @@ CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc <p>Note that the <code class="varname">EGDIR</code> variable is specific to that package and has no meaning outside it.</p> </div> -<div class="sect2" title="15.2.4. Disabling handling of configuration files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conf-files-disable"></a>15.2.4. Disabling handling of configuration files</h3></div></div></div> <p>The automatic copying of config files can be toggled by setting the @@ -6068,7 +6071,7 @@ environment variable <code class="varname">PKG_CONFIG</code> prior to package installation.</p> </div> </div> -<div class="sect1" title="15.3. System startup scripts"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="rcd-scripts"></a>15.3. System startup scripts</h2></div></div></div> <p>System startup scripts are special files because they must be @@ -6106,7 +6109,7 @@ script in an automated fashion:</p> from the examples hierarchy into the system-wide startup scripts directory.</p></li> </ol></div> -<div class="sect2" title="15.3.1. Disabling handling of system startup scripts"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="rcd-scripts-disable"></a>15.3.1. Disabling handling of system startup scripts</h3></div></div></div> <p>The automatic copying of config files can be toggled by setting the @@ -6116,7 +6119,7 @@ examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code> matter what the value of this variable is.</p> </div> </div> -<div class="sect1" title="15.4. System users and groups"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="users-and-groups"></a>15.4. System users and groups</h2></div></div></div> <p>If a package needs to create special users and/or groups during @@ -6153,7 +6156,7 @@ indicate the phase before which the users and groups are created. In this case, the numeric UIDs and GIDs of the created users and groups are automatically hardcoded into the final installation scripts.</p> </div> -<div class="sect1" title="15.5. System shells"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="shells"></a>15.5. System shells</h2></div></div></div> <p>Packages that install system shells should register them in the shell @@ -6168,7 +6171,7 @@ following example, taken from <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/p <pre class="programlisting"> PKG_SHELL= ${PREFIX}/bin/zsh </pre> -<div class="sect2" title="15.5.1. Disabling shell registration"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="shells-disable"></a>15.5.1. Disabling shell registration</h3></div></div></div> <p>The automatic registration of shell interpreters can be disabled by @@ -6176,7 +6179,7 @@ the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</cod environment variable to <code class="literal">NO</code>.</p> </div> </div> -<div class="sect1" title="15.6. Fonts"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fonts"></a>15.6. Fonts</h2></div></div></div> <p>Packages that install X11 fonts should update the database files @@ -6194,7 +6197,7 @@ installation prefix. Consider the following example, taken from <a href="ftp:// <pre class="programlisting"> FONTS_DIRS.ttf= ${PREFIX}/lib/X11/fonts/TTF </pre> -<div class="sect2" title="15.6.1. Disabling automatic update of the fonts databases"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="fonts-disable"></a>15.6.1. Disabling automatic update of the fonts databases</h3></div></div></div> <p>The automatic update of fonts databases can be disabled by @@ -6203,7 +6206,7 @@ environment variable to <code class="literal">NO</code>.</p> </div> </div> </div> -<div class="chapter" title="Chapter 16. Options handling"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="options"></a>Chapter 16. Options handling</h2></div></div></div> <div class="toc"> @@ -6249,7 +6252,7 @@ included, and the amount of work.</p> <p>A further consideration is licensing. Non-free parts, or parts that depend on non-free dependencies (especially plugins) should almost always be split if feasible.</p> -<div class="sect1" title="16.1. Global default options"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="global-default-options"></a>16.1. Global default options</h2></div></div></div> <p>Global default options are listed in @@ -6257,7 +6260,7 @@ almost always be split if feasible.</p> that should be built into every package if that option is supported. This variable should be set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p> </div> -<div class="sect1" title="16.2. Converting packages to use bsd.options.mk"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="converting-to-options"></a>16.2. Converting packages to use <code class="filename">bsd.options.mk</code> </h2></div></div></div> @@ -6396,7 +6399,7 @@ whether it is listed in <code class="varname">PKG_OPTIONS</code>:</p> .if !empty(PKG_OPTIONS:M<em class="replaceable"><code>option</code></em>) </pre> </div> -<div class="sect1" title="16.3. Option Names"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="option-names"></a>16.3. Option Names</h2></div></div></div> <p>Options that enable similar features in different packages (like @@ -6420,7 +6423,7 @@ second its description. The description should be a whole sentence describes what enabling the option does. E. g. <span class="quote">“<span class="quote">Enable ispell support.</span>”</span> The file is sorted by option names.</p> </div> -<div class="sect1" title="16.4. Determining the options of dependencies"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="option-build"></a>16.4. Determining the options of dependencies</h2></div></div></div> <p>When writing <a class="link" href="#buildlink3.mk"><code class="filename">buildlink3.mk</code></a> files, it is often necessary to list @@ -6444,7 +6447,7 @@ file. See the file <code class="filename">pkg-build-options.mk</code> for more details.</p> </div> </div> -<div class="chapter" title="Chapter 17. The build process"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="build"></a>Chapter 17. The build process</h2></div></div></div> <div class="toc"> @@ -6473,7 +6476,7 @@ details.</p> <dt><span class="sect1"><a href="#build.helpful-targets">17.17. Other helpful targets</a></span></dt> </dl> </div> -<div class="sect1" title="17.1. Introduction"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.intro"></a>17.1. Introduction</h2></div></div></div> <p>This chapter gives a detailed description on how a package is @@ -6500,7 +6503,7 @@ details.</p> <code class="varname">PATCH_DEBUG</code> variable if you are just interested in more details about the <span class="emphasis"><em>patch</em></span> step.</p> </div> -<div class="sect1" title="17.2. Program location"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.prefix"></a>17.2. Program location</h2></div></div></div> <p>Before outlining the process performed by the NetBSD package system in @@ -6516,7 +6519,7 @@ details.</p> these files are encoded. See <a class="xref" href="#components.patches" title="11.3. patches/*">Section 11.3, “patches/*”</a> and <a class="xref" href="#fixes.libtool" title="19.3.1. Shared libraries - libtool">Section 19.3.1, “Shared libraries - libtool”</a> for more details.</p> <p>When choosing which of these variables to use, follow the following rules:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">PREFIX</code> always points to the location where the current pkg will be installed. When referring to a pkg's own installation path, use @@ -6601,7 +6604,7 @@ GTKDIR_DEFAULT= ${LOCALBASE} <code class="filename">${PREFIX}/share/man</code>.</p></li> </ul></div> </div> -<div class="sect1" title="17.3. Directories used during the build process"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.builddirs"></a>17.3. Directories used during the build process</h2></div></div></div> <p>When building a package, various directories are used to store @@ -6612,7 +6615,7 @@ GTKDIR_DEFAULT= ${LOCALBASE} <code class="varname">PKGSRCDIR/PKGPATH</code> is used for directories that are pkgsrc-specific. <code class="varname">WRKSRC</code> is used for directories inside the package itself.</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">PKGSRCDIR</code></span></dt> <dd><p>This is an absolute pathname that points to the pkgsrc root directory. Generally, you don't need @@ -6646,7 +6649,7 @@ GTKDIR_DEFAULT= ${LOCALBASE} <code class="varname">CREATE_WRKDIR_SYMLINK</code> should be set to <span class="emphasis"><em>no</em></span>.</p> </div> -<div class="sect1" title="17.4. Running a phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.running"></a>17.4. Running a phase</h2></div></div></div> <p>You can run a particular phase by typing <span class="command"><strong>make @@ -6656,14 +6659,14 @@ GTKDIR_DEFAULT= ${LOCALBASE} run <span class="command"><strong>make</strong></span> without parameters in a package directory, the package will be built, but not installed.</p> </div> -<div class="sect1" title="17.5. The fetch phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.fetch"></a>17.5. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div> <p>The first step in building a package is to fetch the distribution files (distfiles) from the sites that are providing them. This is the task of the <span class="emphasis"><em>fetch</em></span> phase.</p> -<div class="sect2" title="17.5.1. What to fetch and where to get it from"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="build.fetch.what"></a>17.5.1. What to fetch and where to get it from</h3></div></div></div> <p>In simple cases, <code class="varname">MASTER_SITES</code> @@ -6762,7 +6765,7 @@ MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/} <p>Note the trailing slash after the subdirectory name.</p> </div> -<div class="sect2" title="17.5.2. How are the files fetched?"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="build.fetch.how"></a>17.5.2. How are the files fetched?</h3></div></div></div> <p>The <span class="emphasis"><em>fetch</em></span> phase makes sure that @@ -6796,7 +6799,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} mirrored.</p> </div> </div> -<div class="sect1" title="17.6. The checksum phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.checksum"></a>17.6. The <span class="emphasis"><em>checksum</em></span> phase</h2></div></div></div> <p>After the distfile(s) are fetched, their checksum is @@ -6807,7 +6810,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} malign force, deliberately changed distfiles on the master distribution site or network lossage.</p> </div> -<div class="sect1" title="17.7. The extract phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.extract"></a>17.7. The <span class="emphasis"><em>extract</em></span> phase</h2></div></div></div> <p>When the distfiles are present on the local system, they @@ -6822,7 +6825,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} already knows how to extract various archive formats, so most likely you will not need to change anything here. But if you need, the following variables may help you:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}</code></span></dt> <dd><p>Use these variables to override the default options for an extract command, which are defined in @@ -6847,7 +6850,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <code class="varname">do-extract</code> target in the package Makefile.</p> </div> -<div class="sect1" title="17.8. The patch phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.patch"></a>17.8. The <span class="emphasis"><em>patch</em></span> phase</h2></div></div></div> <p>After extraction, all the patches named by the @@ -6868,19 +6871,19 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} may end up being applied in the wrong place, and cause severe harm there.</p> </div> -<div class="sect1" title="17.9. The tools phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.tools"></a>17.9. The <span class="emphasis"><em>tools</em></span> phase</h2></div></div></div> <p>This is covered in <a class="xref" href="#tools" title="Chapter 18. Tools needed for building or running">Chapter 18, <i>Tools needed for building or running</i></a>. </p> </div> -<div class="sect1" title="17.10. The wrapper phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.wrapper"></a>17.10. The <span class="emphasis"><em>wrapper</em></span> phase</h2></div></div></div> <p>This phase creates wrapper programs for the compilers and linkers. The following variables can be used to tweak the wrappers.</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">ECHO_WRAPPER_MSG</code></span></dt> <dd><p>The command used to print progress messages. Does nothing by default. Set to @@ -6912,7 +6915,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} investigate further]</p></dd> </dl></div> </div> -<div class="sect1" title="17.11. The configure phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.configure"></a>17.11. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div> <p>Most pieces of software need information on the header @@ -6972,7 +6975,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <p>If there is no configure step at all, set <code class="varname">NO_CONFIGURE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p> </div> -<div class="sect1" title="17.12. The build phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.build"></a>17.12. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div> <p>For building a package, a rough equivalent of the @@ -7007,12 +7010,12 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <p>If there is no build step at all, set <code class="varname">NO_BUILD</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p> </div> -<div class="sect1" title="17.13. The test phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.test"></a>17.13. The <span class="emphasis"><em>test</em></span> phase</h2></div></div></div> <p>[TODO]</p> </div> -<div class="sect1" title="17.14. The install phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.install"></a>17.14. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div> <p>Once the build stage has completed, the final step is to @@ -7046,7 +7049,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} permissions preset. <code class="varname">INSTALL</code> is the plain install command. The specialized variants, together with their intended use, are:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">INSTALL_PROGRAM_DIR</code></span></dt> <dd><p>directories that contain binaries</p></dd> @@ -7083,7 +7086,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <dd><p>man pages</p></dd> </dl></div> <p>Some other variables are:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">INSTALLATION_DIRS</code></span></dt> <dd><p>A list of directories relative to <code class="varname">PREFIX</code> that are created by pkgsrc at the @@ -7097,7 +7100,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} mostly relevant for packages in the <code class="filename">regress</code> category.</p> </div> -<div class="sect1" title="17.15. The package phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.package"></a>17.15. The <span class="emphasis"><em>package</em></span> phase</h2></div></div></div> <p>Once the install stage has completed, a binary package of @@ -7112,7 +7115,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} variable. <code class="varname">PACKAGES</code> defaults to <code class="filename">pkgsrc/packages</code>.</p> </div> -<div class="sect1" title="17.16. Cleaning up"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.clean"></a>17.16. Cleaning up</h2></div></div></div> <p>Once you're finished with a package, you can clean the work @@ -7120,10 +7123,10 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} to clean the work directories of all dependencies too, use <span class="command"><strong>make clean-depends</strong></span>.</p> </div> -<div class="sect1" title="17.17. Other helpful targets"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="build.helpful-targets"></a>17.17. Other helpful targets</h2></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term">pre/post-*</span></dt> <dd><p>For any of the main targets described in the previous section, two auxiliary targets exist with @@ -7161,7 +7164,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} current directory, effectively de-installing the package. The following variables can be used to tune the behaviour:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt> <dd><p>Add a "-v" to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd> <dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt> @@ -7216,7 +7219,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of <span class="command"><strong>make update</strong></span>:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt> <dd><p>Install target to recursively use for the updated package and the dependent packages. @@ -7287,7 +7290,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <p>The following variables can be used either on the command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of <span class="command"><strong>make clean-update</strong></span>:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt> <dd><p>After <span class="command"><strong>make clean</strong></span>, do not reconstruct the list of directories to update for @@ -7458,7 +7461,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} <p>A binary package is considered <span class="quote">“<span class="quote">up-to-date</span>”</span> to be installed 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> if:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>None of the package's files (<code class="filename">Makefile</code>, ...) were modified since it was built.</p></li> @@ -7471,7 +7474,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} </dl></div> </div> </div> -<div class="chapter" title="Chapter 18. Tools needed for building or running"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="tools"></a>Chapter 18. Tools needed for building or running</h2></div></div></div> <div class="toc"> @@ -7502,7 +7505,7 @@ For example, a package may need GNU awk, bison (instead of yacc) or a better sed.</p> <p>The tools used by a package can be listed by running <span class="command"><strong>make show-tools</strong></span>.</p> -<div class="sect1" title="18.1. Tools for pkgsrc builds"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="pkgsrc-tools"></a>18.1. Tools for pkgsrc builds</h2></div></div></div> <p>The default set of tools used by pkgsrc is defined in @@ -7515,7 +7518,7 @@ These can be seen by running: then the <code class="varname">USE_TOOLS</code> variable can be used to define the tools needed.</p> </div> -<div class="sect1" title="18.2. Tools needed by packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="package-tools"></a>18.2. Tools needed by packages</h2></div></div></div> <p>In the following examples, the :run means that it is needed at @@ -7535,7 +7538,7 @@ on Linux systems.</p> tool at run-time, then just use <code class="varname">DEPENDS</code> instead. </p> </div> -<div class="sect1" title="18.3. Tools provided by platforms"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="platform-tools"></a>18.3. Tools provided by platforms</h2></div></div></div> <p>When improving or porting pkgsrc to a new platform, have a look @@ -7552,11 +7555,11 @@ TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd TOOLS_PLATFORM.true?= true # shell builtin </pre> </div> -<div class="sect1" title="18.4. Questions regarding the tools"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div> -<div class="qandaset" title="Frequently Asked Questions"> -<a name="idm20025536"></a><dl> +<div class="qandaset"> +<a name="idm11867712"></a><dl> <dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a> </dt> <dt>18.4.2. <a href="#tools.listall">How do I get a list of all available @@ -7567,13 +7570,15 @@ TOOLS_PLATFORM.true?= true # shell builtin uses sed or not.</a> </dt> </dl> -<table border="0" width="100%" summary="Q and A Set"> +<table border="0" style="width: 100%;"> +<colgroup> <col align="left" width="1%"> <col> +</colgroup> <tbody> -<tr class="question" title="18.4.1."> +<tr class="question"> <td align="left" valign="top"> -<a name="tools.new"></a><a name="idm20025152"></a><p><b>18.4.1.</b></p> +<a name="tools.new"></a><a name="idm11867520"></a><p><b>18.4.1.</b></p> </td> <td align="left" valign="top"><p>How do I add a new tool?</p></td> </tr> @@ -7581,9 +7586,9 @@ TOOLS_PLATFORM.true?= true # shell builtin <td align="left" valign="top"></td> <td align="left" valign="top"><p>TODO</p></td> </tr> -<tr class="question" title="18.4.2."> +<tr class="question"> <td align="left" valign="top"> -<a name="tools.listall"></a><a name="idm20024128"></a><p><b>18.4.2.</b></p> +<a name="tools.listall"></a><a name="idm11867008"></a><p><b>18.4.2.</b></p> </td> <td align="left" valign="top"><p>How do I get a list of all available tools?</p></td> @@ -7592,9 +7597,9 @@ TOOLS_PLATFORM.true?= true # shell builtin <td align="left" valign="top"></td> <td align="left" valign="top"><p>TODO</p></td> </tr> -<tr class="question" title="18.4.3."> +<tr class="question"> <td align="left" valign="top"> -<a name="tools.used"></a><a name="idm20023104"></a><p><b>18.4.3.</b></p> +<a name="tools.used"></a><a name="idm11866496"></a><p><b>18.4.3.</b></p> </td> <td align="left" valign="top"><p>How can I get a list of all the tools that a package is using while being built? I want to know whether it @@ -7610,7 +7615,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </div> </div> </div> -<div class="chapter" title="Chapter 19. Making your package work"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="fixes"></a>Chapter 19. Making your package work</h2></div></div></div> <div class="toc"> @@ -7684,10 +7689,10 @@ TOOLS_PLATFORM.true?= true # shell builtin <dt><span class="sect1"><a href="#punting">19.7. Marking packages as having problems</a></span></dt> </dl> </div> -<div class="sect1" title="19.1. General operation"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="general-operation"></a>19.1. General operation</h2></div></div></div> -<div class="sect2" title="19.1.1. Portability of packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="portability-of-packages"></a>19.1.1. Portability of packages</h3></div></div></div> <p>One appealing feature of pkgsrc is that it runs on many @@ -7696,7 +7701,7 @@ TOOLS_PLATFORM.true?= true # shell builtin chapter mentions some particular details you should pay attention to while working on pkgsrc.</p> </div> -<div class="sect2" title="19.1.2. How to pull in user-settable variables from mk.conf"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="pulling-vars-from-etc-mk.conf"></a>19.1.2. How to pull in user-settable variables from <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> </h3></div></div></div> @@ -7717,19 +7722,19 @@ TOOLS_PLATFORM.true?= true # shell builtin in dependency lines (of the form <code class="literal">target: dependencies</code>) the variables are expanded at load time.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>Currently there is no exhaustive list of all variables that tells you whether they can be used at load time or only at run time, but it is in preparation.</p> </div> </div> -<div class="sect2" title="19.1.3. User interaction"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="user-interaction"></a>19.1.3. User interaction</h3></div></div></div> <p>Occasionally, packages require interaction from the user, and this can be in a number of ways:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>When fetching the distfiles, some packages require user interaction such as entering username/password or accepting a license on a web page.</p></li> @@ -7753,7 +7758,7 @@ INTERACTIVE_STAGE= configure install <p>The user can then decide to skip this package by setting the <code class="varname">BATCH</code> variable.</p> </div> -<div class="sect2" title="19.1.4. Handling licenses"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="handling-licenses"></a>19.1.4. Handling licenses</h3></div></div></div> <p>Authors of software can choose the licence under which @@ -7872,7 +7877,7 @@ ACCEPTABLE_LICENSES+=xv-license without also telling pkgsrc to proceed for all packages with that tag.</p> </div> -<div class="sect2" title="19.1.5. Restricted packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="restricted-packages"></a>19.1.5. Restricted packages</h3></div></div></div> <p>Some licenses restrict how software may be re-distributed. @@ -7895,7 +7900,7 @@ ACCEPTABLE_LICENSES+=xv-license <p>In order to encode these restrictions, the package system defines five make variables that can be set to note these restrictions:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p><code class="varname">RESTRICTED</code></p> <p>This variable should be set whenever a restriction @@ -7940,7 +7945,7 @@ ACCEPTABLE_LICENSES+=xv-license interactive fetch must have a maintainer and it is his/her responsibility to ensure this.</p> </div> -<div class="sect2" title="19.1.6. Handling dependencies"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="dependencies"></a>19.1.6. Handling dependencies</h3></div></div></div> <p>Your package may depend on some other package being present @@ -8035,7 +8040,7 @@ DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick (It relies on the jpeg sources being present in source form during the build.)</p> </div> -<div class="sect2" title="19.1.7. Handling conflicts with other packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="conflicts"></a>19.1.7. Handling conflicts with other packages</h3></div></div></div> <p>Your package may conflict with other packages a user might @@ -8061,7 +8066,7 @@ CONFLICTS= Xaw3d-[0-9]* string. <span class="quote">“<span class="quote">Xaw3d-1.5</span>”</span> e.g. will automatically conflict with the older version <span class="quote">“<span class="quote">Xaw3d-1.3</span>”</span>.</p> </div> -<div class="sect2" title="19.1.8. Packages that cannot or should not be built"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="not-building-packages"></a>19.1.8. Packages that cannot or should not be built</h3></div></div></div> <p>There are several reasons why a package might be @@ -8089,7 +8094,7 @@ CONFLICTS= Xaw3d-[0-9]* set <code class="varname">PKG_FAIL_REASON</code> to a descriptive message.</p> </div> -<div class="sect2" title="19.1.9. Packages which should not be deleted, once installed"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="undeletable-packages"></a>19.1.9. Packages which should not be deleted, once installed</h3></div></div></div> <p>To ensure that a package may not be deleted, once it has been @@ -8100,7 +8105,7 @@ CONFLICTS= Xaw3d-[0-9]* not be deleted using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> unless the <span class="quote">“<span class="quote">-f</span>”</span> option is used.</p> </div> -<div class="sect2" title="19.1.10. Handling packages with security problems"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="security-handling"></a>19.1.10. Handling packages with security problems</h3></div></div></div> <p>When a vulnerability is found, this should be noted in @@ -8117,7 +8122,7 @@ CONFLICTS= Xaw3d-[0-9]* <p>Binary packages already on ftp.NetBSD.org will be handled semi-automatically by a weekly cron job.</p> </div> -<div class="sect2" title="19.1.11. How to handle incrementing versions when fixing an existing package"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="bumping-pkgrevision"></a>19.1.11. How to handle incrementing versions when fixing an existing package</h3></div></div></div> <p>When making fixes to an existing package it can be useful @@ -8153,7 +8158,7 @@ DISTNAME= foo-17.43 <code class="varname">PKGREVISION</code> is appropriate. Examples of changes that do not merit increasing <code class="varname">PKGREVISION</code> are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>, <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>, or comments in Makefile.</p></li> @@ -8166,7 +8171,7 @@ DISTNAME= foo-17.43 </ul></div> <p>Examples of changes that do merit an increase to <code class="varname">PKGREVISION</code> include:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p> Security fixes</p></li> <li class="listitem"><p> @@ -8178,7 +8183,7 @@ DISTNAME= foo-17.43 <p>PKGREVISION must also be incremented when dependencies have ABI changes.</p> </div> -<div class="sect2" title="19.1.12. Substituting variable text in the package files (the SUBST framework)"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="fixes.subst"></a>19.1.12. Substituting variable text in the package files (the SUBST framework)</h3></div></div></div> <p>When you want to replace the same text in multiple files @@ -8238,10 +8243,10 @@ SUBST_SED.fix-paths+= -e 's,"/var/log,"${VARBASE}/log,g' <code class="filename">mk/subst.mk</code> file.</p> </div> </div> -<div class="sect1" title="19.2. Fixing problems in the fetch phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fixes.fetch"></a>19.2. Fixing problems in the <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div> -<div class="sect2" title="19.2.1. Packages whose distfiles aren't available for plain downloading"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="no-plain-download"></a>19.2.1. Packages whose distfiles aren't available for plain downloading</h3></div></div></div> <p>If you need to download from a dynamic URL you can set @@ -8262,7 +8267,7 @@ FETCH_MESSAGE+= " "${DISTFILES:Q} FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"." </pre> </div> -<div class="sect2" title="19.2.2. How to handle modified distfiles with the 'old' name"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="modified-distfiles-same-name"></a>19.2.2. How to handle modified distfiles with the 'old' name</h3></div></div></div> <p>Sometimes authors of a software package make some @@ -8295,10 +8300,10 @@ FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"." changing the file names is not good practice.</p> </div> </div> -<div class="sect1" title="19.3. Fixing problems in the configure phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fixes.configure"></a>19.3. Fixing problems in the <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div> -<div class="sect2" title="19.3.1. Shared libraries - libtool"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="fixes.libtool"></a>19.3.1. Shared libraries - libtool</h3></div></div></div> <p>pkgsrc supports many different machines, with different @@ -8423,7 +8428,7 @@ ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib file (this is a change from previous behaviour).</p></li> </ol></div> </div> -<div class="sect2" title="19.3.2. Using libtool on GNU packages that already support libtool"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="using-libtool"></a>19.3.2. Using libtool on GNU packages that already support libtool</h3></div></div></div> <p>Add <code class="varname">USE_LIBTOOL=yes</code> to the @@ -8446,7 +8451,7 @@ ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib <p>Some packages use libtool incorrectly so that the package may not work or build in some circumstances. Some of the more common errors are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p>The inclusion of a shared object (-module) as a dependent library in an executable or library. This in itself isn't a problem if one of two things @@ -8464,7 +8469,7 @@ ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib executables.</p></li> </ul></div> </div> -<div class="sect2" title="19.3.3. GNU Autoconf/Automake"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="autoconf-automake"></a>19.3.3. GNU Autoconf/Automake</h3></div></div></div> <p>If a package needs GNU autoconf or automake to be executed @@ -8505,10 +8510,10 @@ pre-configure: Makefile.</p> </div> </div> -<div class="sect1" title="19.4. Programming languages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="programming-languages"></a>19.4. Programming languages</h2></div></div></div> -<div class="sect2" title="19.4.1. C, C++, and Fortran"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="basic-programming-languages"></a>19.4.1. C, C++, and Fortran</h3></div></div></div> <p>Compilers for the C, C++, and Fortran languages comes with @@ -8523,14 +8528,14 @@ pre-configure: written in C++, usually need a C compiler for the configure phase.</p> </div> -<div class="sect2" title="19.4.2. Java"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="java-programming-language"></a>19.4.2. Java</h3></div></div></div> <p>If a program is written in Java, use the Java framework in pkgsrc. The package must include <code class="filename">../../mk/java-vm.mk</code>. This Makefile fragment provides the following variables:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">USE_JAVA</code> defines if a build dependency on the JDK is added. If <code class="varname">USE_JAVA</code> is set to <span class="quote">“<span class="quote">run</span>”</span>, then @@ -8552,7 +8557,7 @@ pre-configure: </p></li> </ul></div> </div> -<div class="sect2" title="19.4.3. Packages containing perl scripts"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="perl-scripts"></a>19.4.3. Packages containing perl scripts</h3></div></div></div> <p>If your package contains interpreted perl scripts, add @@ -8569,7 +8574,7 @@ pre-configure: <p>See <a class="xref" href="#perl-modules" title="19.6.6. Packages installing perl modules">Section 19.6.6, “Packages installing perl modules”</a> for information about handling perl modules.</p> </div> -<div class="sect2" title="19.4.4. Packages containing shell scripts"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="shell-scripts"></a>19.4.4. Packages containing shell scripts</h3></div></div></div> <p><code class="varname">REPLACE_SH</code>, @@ -8580,7 +8585,7 @@ pre-configure: When using <code class="varname">REPLACE_BASH</code>, don't forget to add <code class="filename">bash</code> to <code class="varname">USE_TOOLS</code>.</p> </div> -<div class="sect2" title="19.4.5. Other programming languages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="other-programming-languages"></a>19.4.5. Other programming languages</h3></div></div></div> <p>Currently, there is no special handling for other languages @@ -8590,7 +8595,7 @@ pre-configure: package.</p> </div> </div> -<div class="sect1" title="19.5. Fixing problems in the build phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fixes.build"></a>19.5. Fixing problems in the <span class="emphasis"><em>build</em></span> phase</h2></div></div></div> <p>The most common failures when building a package are that @@ -8599,7 +8604,7 @@ pre-configure: original package author didn't know. To work around this, you can rewrite the source code in most cases so that it does not use the missing functions or provides a replacement function.</p> -<div class="sect2" title="19.5.1. Compiling C and C++ code conditionally"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="fixes.build.cpp"></a>19.5.1. Compiling C and C++ code conditionally</h3></div></div></div> <p>If a package already comes with a GNU configure script, the @@ -8619,7 +8624,7 @@ pre-configure: example, if you want to conditionally compile code on Solaris, don't use <code class="varname">__sun__</code>, as the SunPro compiler does not define it. Use <code class="varname">__sun</code> instead.</p> -<div class="sect3" title="19.5.1.1. C preprocessor macros to identify the operating system"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="fixes.build.cpp.os"></a>19.5.1.1. C preprocessor macros to identify the operating system</h4></div></div></div> <p>To distinguish between 4.4 BSD-derived systems and the @@ -8645,7 +8650,7 @@ OpenBSD __OpenBSD__ Solaris sun, __sun </pre> </div> -<div class="sect3" title="19.5.1.2. C preprocessor macros to identify the hardware architecture"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="fixes.build.cpp.arch"></a>19.5.1.2. C preprocessor macros to identify the hardware architecture</h4></div></div></div> <pre class="programlisting"> @@ -8654,7 +8659,7 @@ MIPS __mips SPARC sparc, __sparc </pre> </div> -<div class="sect3" title="19.5.1.3. C preprocessor macros to identify the compiler"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="fixes.build.cpp.compiler"></a>19.5.1.3. C preprocessor macros to identify the compiler</h4></div></div></div> <pre class="programlisting"> @@ -8665,7 +8670,7 @@ SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8) </pre> </div> </div> -<div class="sect2" title="19.5.2. How to handle compiler bugs"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="compiler-bugs"></a>19.5.2. How to handle compiler bugs</h3></div></div></div> <p>Some source files trigger bugs in the compiler, based on @@ -8680,7 +8685,7 @@ SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8) in <code class="filename">pkgsrc/doc/HACKS</code>. See that file for a number of examples.</p> </div> -<div class="sect2" title="19.5.3. Undefined reference to “...”"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="undefined-reference"></a>19.5.3. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span> </h3></div></div></div> @@ -8743,7 +8748,7 @@ SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8) -l<em class="replaceable"><code>foo</code></em></code> to the package <code class="filename">Makefile</code> and then say <span class="command"><strong>bmake clean; bmake</strong></span>.</p> -<div class="sect3" title="19.5.3.1. Special issue: The SunPro compiler"> +<div class="sect3"> <div class="titlepage"><div><div><h4 class="title"> <a name="undefined-reference-sunpro"></a>19.5.3.1. Special issue: The SunPro compiler</h4></div></div></div> <p>When you are using the SunPro compiler, there is another @@ -8769,7 +8774,7 @@ solve this problem you can try to tell the package to disable inlining of functions.</p> </div> </div> -<div class="sect2" title="19.5.4. Running out of memory"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="out-of-memory"></a>19.5.4. Running out of memory</h3></div></div></div> <p>Sometimes packages fail to build because the compiler runs @@ -8783,10 +8788,10 @@ of functions.</p> their hard limits.</p> </div> </div> -<div class="sect1" title="19.6. Fixing problems in the install phase"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="fixes.install"></a>19.6. Fixing problems in the <span class="emphasis"><em>install</em></span> phase</h2></div></div></div> -<div class="sect2" title="19.6.1. Creating needed directories"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="install-scripts"></a>19.6.1. Creating needed directories</h3></div></div></div> <p>The BSD-compatible <span class="command"><strong>install</strong></span> supplied @@ -8802,7 +8807,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2 <code class="varname">INSTALLATION_DIRS</code> variable, which will automatically do the right thing.</p> </div> -<div class="sect2" title="19.6.2. Where to install documentation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="where-to-install-documentation"></a>19.6.2. Where to install documentation</h3></div></div></div> <p>In general, documentation should be installed into @@ -8831,7 +8836,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2 <code class="filename">${PREFIX}/share/gtk-doc</code> is preferred though.)</p> </div> -<div class="sect2" title="19.6.3. Installing highscore files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="installing-score-files"></a>19.6.3. Installing highscore files</h3></div></div></div> <p>Certain packages, most of them in the games category, install @@ -8850,7 +8855,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2 <code class="varname">INSTALL_GAME_DATA</code> to set these correctly.</p> </div> -<div class="sect2" title="19.6.4. Adding DESTDIR support to packages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="destdir-support"></a>19.6.4. Adding DESTDIR support to packages</h3></div></div></div> <p><code class="varname">DESTDIR</code> support means that a package @@ -8859,7 +8864,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2 installation as usual. There are two ways: Either the package must install as root (<span class="quote">“<span class="quote">destdir</span>”</span>) or the package can install as non-root user (<span class="quote">“<span class="quote">user-destdir</span>”</span>).</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be set to <span class="quote">“<span class="quote">none</span>”</span>, <span class="quote">“<span class="quote">destdir</span>”</span>, or <span class="quote">“<span class="quote">user-destdir</span>”</span>. By default <code class="varname">PKG_DESTDIR_SUPPORT</code> @@ -8879,7 +8884,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2 DESTDIR.</p></li> </ul></div> </div> -<div class="sect2" title="19.6.5. Packages with hardcoded paths to other interpreters"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="hardcoded-paths"></a>19.6.5. Packages with hardcoded paths to other interpreters</h3></div></div></div> <p>Your package may also contain scripts with hardcoded paths to @@ -8894,14 +8899,14 @@ REPLACE.tcl.new= ${PREFIX}/bin/tclsh REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed, # relative to ${WRKSRC}, just as in REPLACE_PERL </pre> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>Before March 2006, these variables were called <code class="varname">_REPLACE.*</code> and <code class="varname">_REPLACE_FILES.*</code>.</p> </div> </div> -<div class="sect2" title="19.6.6. Packages installing perl modules"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="perl-modules"></a>19.6.6. Packages installing perl modules</h3></div></div></div> <p>Makefiles of packages providing perl5 modules should include @@ -8930,7 +8935,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist variables are also substituted for in the <code class="filename">PLIST</code>.</p> </div> -<div class="sect2" title="19.6.7. Packages installing info files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="faq.info-files"></a>19.6.7. Packages installing info files</h3></div></div></div> <p>Some packages install info files or use the @@ -8977,7 +8982,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist value of <code class="varname">TEXINFO_REQD</code> either runs the appropriate <span class="command"><strong>makeinfo</strong></span> command or exit on error.</p> </div> -<div class="sect2" title="19.6.8. Packages installing man pages"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="manpages"></a>19.6.8. Packages installing man pages</h3></div></div></div> <p>All packages that install manual pages should install them @@ -8988,7 +8993,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist <code class="varname">PKGMANDIR</code> is <span class="quote">“<span class="quote"><code class="filename">man</code></span>”</span>. Another often-used value is <span class="quote">“<span class="quote"><code class="filename">share/man</code></span>”</span>.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>The support for a custom <code class="varname">PKGMANDIR</code> is far from complete.</p> @@ -9014,7 +9019,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist <p>See <a class="xref" href="#manpage-compression" title="13.5. Man page compression">Section 13.5, “Man page compression”</a> for information on installation of compressed manual pages.</p> </div> -<div class="sect2" title="19.6.9. Packages installing GConf data files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="gconf-data-files"></a>19.6.9. Packages installing GConf data files</h3></div></div></div> <p>If a package installs <code class="filename">.schemas</code> or @@ -9048,7 +9053,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist them.</p></li> </ol></div> </div> -<div class="sect2" title="19.6.10. Packages installing scrollkeeper/rarian data files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="scrollkeeper-data-files"></a>19.6.10. Packages installing scrollkeeper/rarian data files</h3></div></div></div> <p>If a package installs <code class="filename">.omf</code> files, used by @@ -9069,7 +9074,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist print-PLIST</strong></span> does this automatically.)</p></li> </ol></div> </div> -<div class="sect2" title="19.6.11. Packages installing X11 fonts"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="x11-fonts"></a>19.6.11. Packages installing X11 fonts</h3></div></div></div> <p>If a package installs font files, you will need to rebuild @@ -9086,7 +9091,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist instead use the standard ones to avoid that the user needs to manually configure his X server to find them.</p> </div> -<div class="sect2" title="19.6.12. Packages installing GTK2 modules"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="gtk2-modules"></a>19.6.12. Packages installing GTK2 modules</h3></div></div></div> <p>If a package installs GTK2 immodules or loaders, you need to @@ -9104,7 +9109,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist <li class="listitem"> <p>Patch the package to not touch any of the GTK2 databases directly. These are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="filename">libdata/gtk-2.0/gdk-pixbuf.loaders</code></p></li> <li class="listitem"><p><code class="filename">libdata/gtk-2.0/gtk.immodules</code></p></li> </ul></div> @@ -9114,7 +9119,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist directory, as they will be handled automatically.</p></li> </ol></div> </div> -<div class="sect2" title="19.6.13. Packages installing SGML or XML data"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="sgml-xml-data"></a>19.6.13. Packages installing SGML or XML data</h3></div></div></div> <p>If a package installs SGML or XML data files that need to be @@ -9142,7 +9147,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist normally not use this variable.</p></li> </ol></div> </div> -<div class="sect2" title="19.6.14. Packages installing extensions to the MIME database"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="mime-database"></a>19.6.14. Packages installing extensions to the MIME database</h3></div></div></div> <p>If a package provides extensions to the MIME database by @@ -9172,7 +9177,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist package.</p></li> </ol></div> </div> -<div class="sect2" title="19.6.15. Packages using intltool"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="intltool"></a>19.6.15. Packages using intltool</h3></div></div></div> <p>If a package uses intltool during its build, add @@ -9183,7 +9188,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist latest available version; this way, the package benefits of any bug fixes that may have appeared since it was released.</p> </div> -<div class="sect2" title="19.6.16. Packages installing startup scripts"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="startup-scripts"></a>19.6.16. Packages installing startup scripts</h3></div></div></div> <p>If a package contains a rc.d script, it won't be copied into @@ -9194,13 +9199,13 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist it will automatically remove the scripts when the package is deinstalled.</p> </div> -<div class="sect2" title="19.6.17. Packages installing TeX modules"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="tex-packages"></a>19.6.17. Packages installing TeX modules</h3></div></div></div> <p>If a package installs TeX packages into the texmf tree, the <code class="filename">ls-R</code> database of the tree needs to be updated.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>Except the main TeX packages such as kpathsea, packages should install files @@ -9233,7 +9238,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist they will be removed only by the kpathsea package.</p></li> </ol></div> </div> -<div class="sect2" title="19.6.18. Packages supporting running binaries in emulation"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="emulation-packages"></a>19.6.18. Packages supporting running binaries in emulation</h3></div></div></div> @@ -9250,7 +9255,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist this fails for emulation packages, because the libraries used by the emulation are not in the standard directories.</p> </div> -<div class="sect2" title="19.6.19. Packages installing hicolor theme icons"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="hicolor-theme"></a>19.6.19. Packages installing hicolor theme icons</h3></div></div></div> <p>If a package installs images under the @@ -9272,7 +9277,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist respect to the last two points is to regenerate it using <span class="command"><strong>make print-PLIST</strong></span>.</p> </div> -<div class="sect2" title="19.6.20. Packages installing desktop files"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="desktop-files"></a>19.6.20. Packages installing desktop files</h3></div></div></div> <p>If a package installs <code class="filename">.desktop</code> files @@ -9291,7 +9296,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist print-PLIST</strong></span>.</p> </div> </div> -<div class="sect1" title="19.7. Marking packages as having problems"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="punting"></a>19.7. Marking packages as having problems</h2></div></div></div> <p>In some cases one does not have the time to solve a problem @@ -9305,14 +9310,14 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist intervals.</p> </div> </div> -<div class="chapter" title="Chapter 20. Debugging"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="debug"></a>Chapter 20. Debugging</h2></div></div></div> <p>To check out all the gotchas when building a package, here are the steps that I do in order to get a package working. Please note this is basically the same as what was explained in the previous sections, only with some debugging aids.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Be sure to set <code class="varname">PKG_DEVELOPER=yes</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p></li> <li class="listitem"> <p>Install <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>, @@ -9387,7 +9392,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist <li class="listitem"><p>Submit (or commit, if you have cvs access); see <a class="xref" href="#submit" title="Chapter 21. Submitting and Committing">Chapter 21, <i>Submitting and Committing</i></a>.</p></li> </ul></div> </div> -<div class="chapter" title="Chapter 21. Submitting and Committing"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="submit"></a>Chapter 21. Submitting and Committing</h2></div></div></div> <div class="toc"> @@ -9402,7 +9407,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist <dt><span class="sect1"><a href="#moving-package">21.7. Moving a package in pkgsrc</a></span></dt> </dl> </div> -<div class="sect1" title="21.1. Submitting binary packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="submitting-binary-packages"></a>21.1. Submitting binary packages</h2></div></div></div> <p>Our policy is that we accept binaries only from pkgsrc @@ -9413,7 +9418,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist developers doing bulk builds and wanting to upload them please see <a class="xref" href="#bulk-upload" title="7.3.8. Uploading results of a bulk build">Section 7.3.8, “Uploading results of a bulk build”</a>.</p> </div> -<div class="sect1" title="21.2. Submitting source packages (for non-NetBSD-developers)"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="submitting-your-package"></a>21.2. Submitting source packages (for non-NetBSD-developers)</h2></div></div></div> <p>First, check that your package is complete, compiles and @@ -9443,7 +9448,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist homepage at <a class="ulink" href="http://pkgsrc-wip.sourceforge.net/" target="_top">http://pkgsrc-wip.sourceforge.net/</a> for details.</p> </div> -<div class="sect1" title="21.3. General notes when adding, updating, or removing packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="general-notes-for-changes"></a>21.3. General notes when adding, updating, or removing packages</h2></div></div></div> <p>Please note all package additions, updates, moves, and @@ -9482,7 +9487,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist makes the cvs commands use the main repository. </p> </div> -<div class="sect1" title="21.4. Committing: Adding a package to CVS"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="committing-importing"></a>21.4. Committing: Adding a package to CVS</h2></div></div></div> <p>This section is only of interest for pkgsrc developers with write @@ -9512,13 +9517,13 @@ you can check by running <span class="quote">“<span class="quote">cvs stat <p>Previously, <span class="quote">“<span class="quote">cvs import</span>”</span> was suggested, but it was much easier to get wrong than <span class="quote">“<span class="quote">cvs add</span>”</span>.</p> </div> -<div class="sect1" title="21.5. Updating a package to a newer version"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="updating-package"></a>21.5. Updating a package to a newer version</h2></div></div></div> <p>Please always put a concise, appropriate and relevant summary of the changes between old and new versions into the commit log when updating a package. There are various reasons for this:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>A URL is volatile, and can change over time. It may go away completely or its information may be overwritten by newer information.</p></li> <li class="listitem"><p>Having the change information between old and new versions in our CVS @@ -9536,7 +9541,7 @@ much easier to get wrong than <span class="quote">“<span class="quote">cvs judgement about what should go into pkgsrc, and bear in mind that stability is to be preferred above new and possibly untested features.</p> </div> -<div class="sect1" title="21.6. Renaming a package in pkgsrc"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="renaming-package"></a>21.6. Renaming a package in pkgsrc</h2></div></div></div> <p>Renaming packages is not recommended.</p> @@ -9554,7 +9559,7 @@ much easier to get wrong than <span class="quote">“<span class="quote">cvs not be an exact replacement but is a suggestion for the replaced functionality.</p> </div> -<div class="sect1" title="21.7. Moving a package in pkgsrc"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="moving-package"></a>21.7. Moving a package in pkgsrc</h2></div></div></div> <p>It is preferred that packages are not renamed or moved, but if needed @@ -9602,7 +9607,7 @@ place.</p></li> </ol></div> </div> </div> -<div class="chapter" title="Chapter 22. Frequently Asked Questions"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div> <p>This section contains the answers to questions that may @@ -9610,8 +9615,8 @@ place.</p></li> question answered here, first have a look in the other chapters, and if you still don't have the answer, ask on the <code class="literal">pkgsrc-users</code> mailing list.</p> -<div class="qandaset" title="Frequently Asked Questions"> -<a name="idm19487552"></a><dl> +<div class="qandaset"> +<a name="idm11525568"></a><dl> <dt>22.1. <a href="#devfaq.makeflags">What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?</a> @@ -9648,13 +9653,15 @@ place.</p></li> do?</a> </dt> </dl> -<table border="0" width="100%" summary="Q and A Set"> +<table border="0" style="width: 100%;"> +<colgroup> <col align="left" width="1%"> <col> +</colgroup> <tbody> -<tr class="question" title="22.1."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.makeflags"></a><a name="idm19487168"></a><p><b>22.1.</b></p> +<a name="devfaq.makeflags"></a><a name="idm11525376"></a><p><b>22.1.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and @@ -9668,9 +9675,9 @@ do?</a> the <code class="varname">MAKE_PROGRAM</code> when building the package. [FIXME: What is .MAKEFLAGS for?]</p></td> </tr> -<tr class="question" title="22.2."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.make"></a><a name="idm19483200"></a><p><b>22.2.</b></p> +<a name="devfaq.make"></a><a name="idm11523264"></a><p><b>22.2.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and @@ -9686,9 +9693,9 @@ do?</a> Make program that is used for building the package.</p></td> </tr> -<tr class="question" title="22.3."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.cc"></a><a name="idm19478720"></a><p><b>22.3.</b></p> +<a name="devfaq.cc"></a><a name="idm11520960"></a><p><b>22.3.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and @@ -9704,9 +9711,9 @@ do?</a> used. See <code class="filename">mk/compiler.mk</code> for more information about the latter variable.</p></td> </tr> -<tr class="question" title="22.4."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.bl3flags"></a><a name="idm19474624"></a><p><b>22.4.</b></p> +<a name="devfaq.bl3flags"></a><a name="idm11518848"></a><p><b>22.4.</b></p> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">BUILDLINK_LDFLAGS</code>, @@ -9717,9 +9724,9 @@ do?</a> <td align="left" valign="top"></td> <td align="left" valign="top"><p>[FIXME]</p></td> </tr> -<tr class="question" title="22.5."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.bl3prefix"></a><a name="idm19472320"></a><p><b>22.5.</b></p> +<a name="devfaq.bl3prefix"></a><a name="idm11517696"></a><p><b>22.5.</b></p> </td> <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> @@ -9733,9 +9740,9 @@ do?</a> <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above command.</p></td> </tr> -<tr class="question" title="22.6."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.master_sites"></a><a name="idm19469248"></a><p><b>22.6.</b></p> +<a name="devfaq.master_sites"></a><a name="idm11516160"></a><p><b>22.6.</b></p> </td> <td align="left" valign="top"><p>What does <code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I @@ -9757,16 +9764,16 @@ do?</a> <code class="literal">:</code> and the <code class="literal">=</code> fall together.</p></td> </tr> -<tr class="question" title="22.7."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.mailinglists"></a><a name="idm19452992"></a><p><b>22.7.</b></p> +<a name="devfaq.mailinglists"></a><a name="idm11512192"></a><p><b>22.7.</b></p> </td> <td align="left" valign="top"><p>Which mailing lists are there for package developers?</p></td> </tr> <tr class="answer"> <td align="left" valign="top"></td> -<td align="left" valign="top"><div class="variablelist"><dl> +<td align="left" valign="top"><div class="variablelist"><dl class="variablelist"> <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt> <dd><p>This is a list for technical discussions related to pkgsrc development, e.g. soliciting feedback for changes to @@ -9782,9 +9789,9 @@ do?</a> lists.</p></dd> </dl></div></td> </tr> -<tr class="question" title="22.8."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.documentation"></a><a name="idm19449280"></a><p><b>22.8.</b></p> +<a name="devfaq.documentation"></a><a name="idm11510144"></a><p><b>22.8.</b></p> </td> <td align="left" valign="top"><p>Where is the pkgsrc documentation?</p></td> @@ -9794,7 +9801,7 @@ do?</a> <td align="left" valign="top"> <p>There are many places where you can find documentation about pkgsrc:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>The pkgsrc guide (this document) is a collection of chapters that explain large parts of pkgsrc, but some chapters tend to be outdated. Which ones they are is hard to @@ -9830,9 +9837,9 @@ do?</a> </ul></div> </td> </tr> -<tr class="question" title="22.9."> +<tr class="question"> <td align="left" valign="top"> -<a name="devfaq.too-much-time"></a><a name="idm19442752"></a><p><b>22.9.</b></p> +<a name="devfaq.too-much-time"></a><a name="idm11498688"></a><p><b>22.9.</b></p> </td> <td align="left" valign="top"><p>I have a little time to kill. What shall I do?</p></td> @@ -9842,7 +9849,7 @@ do?</p></td> <td align="left" valign="top"> <p>This is not really an FAQ yet, but here's the answer anyway.</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It will tell you about newer versions of installed packages that are @@ -9861,7 +9868,7 @@ anyway.</p> </table> </div> </div> -<div class="chapter" title="Chapter 23. GNOME packaging and porting"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="gnome"></a>Chapter 23. GNOME packaging and porting</h2></div></div></div> <div class="toc"> @@ -9896,7 +9903,7 @@ portability fixes to make GNOME build and install under it.</p> interested in helping our GNOME porting and packaging efforts. It provides instructions on how to manage the existing packages and some important information regarding their internals.</p> -<div class="note" title="We need your help!" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">We need your help!</h3> <p>Should you have some spare cycles to devote to NetBSD, pkgsrc and GNOME and are willing to learn new exciting stuff, please jump @@ -9905,11 +9912,11 @@ important information regarding their internals.</p> fully-functional GNOME desktop under NetBSD and we need your help to achieve it!</p> </div> -<div class="sect1" title="23.1. Meta packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="meta-packages"></a>23.1. Meta packages</h2></div></div></div> <p>pkgsrc includes three GNOME-related meta packages:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html" target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>: Provides the core GNOME desktop environment. It only includes the necessary bits to get it to boot correctly, although it may lack important @@ -9939,14 +9946,14 @@ packages listed before it but not on any listed after it. It is very important to keep this order to ease updates so... <span class="emphasis"><em>do not change it to alphabetical sorting!</em></span></p> </div> -<div class="sect1" title="23.2. Packaging a GNOME application"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="new-package"></a>23.2. Packaging a GNOME application</h2></div></div></div> <p>Almost all GNOME applications are written in C and use a common set of tools as their build system. Things get different with the new bindings to other languages (such as Python), but the following will give you a general idea on the minimum required tools:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"> <p>Almost all GNOME applications use the GNU Autotools as their build system. As a general rule you will need to tell this to your @@ -10039,12 +10046,12 @@ solution is given. After applying the solution be sure to </div> <br class="table-break"> </div> -<div class="sect1" title="23.3. Updating GNOME to a newer version"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="full-update"></a>23.3. Updating GNOME to a newer version</h2></div></div></div> <p>When seeing GNOME as a whole, there are two kinds of updates:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term">Major update</span></dt> <dd> <p>Given that there is still a very long way for GNOME 3 (if it @@ -10128,7 +10135,7 @@ followed:</p> <a href="http://cvsweb.NetBSD.org/bsdweb.cgi/pkgsrc/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup" target="_top"><code class="filename">pkgsrc/doc/TODO</code></a> files.</p></li> </ol></div> </div> -<div class="sect1" title="23.4. Patching guidelines"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="patching"></a>23.4. Patching guidelines</h2></div></div></div> <p>GNOME is a very big component in pkgsrc which approaches 100 @@ -10156,10 +10163,10 @@ details.</p> </div> </div> </div> -<div class="part" title="Part III. The pkgsrc infrastructure internals"> +<div class="part"> <div class="titlepage"><div><div><h1 class="title"> <a name="infrastructure"></a>Part III. The pkgsrc infrastructure internals</h1></div></div></div> -<div class="partintro" title="The pkgsrc infrastructure internals"> +<div class="partintro"> <div></div> <p>This part of the guide deals with everything from the infrastructure that is behind the interfaces described @@ -10207,7 +10214,7 @@ details.</p> </dl> </div> </div> -<div class="chapter" title="Chapter 24. Design of the pkgsrc infrastructure"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="infr.design"></a>Chapter 24. Design of the pkgsrc infrastructure</h2></div></div></div> <div class="toc"> @@ -10237,7 +10244,7 @@ details.</p> fragments. Each such fragment needs a properly specified interface. This chapter explains how such an interface looks like.</p> -<div class="sect1" title="24.1. The meaning of variable definitions"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.vardef"></a>24.1. The meaning of variable definitions</h2></div></div></div> <p>Whenever a variable is defined in the pkgsrc @@ -10261,14 +10268,14 @@ details.</p> <p>Variables whose name starts with an underscore must not be accessed outside the pkgsrc infrastructure at all. They may change without further notice.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>These conventions are currently not applied consistently to the complete pkgsrc infrastructure.</p> </div> </div> -<div class="sect1" title="24.2. Avoiding problems before they arise"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.vardef.problems"></a>24.2. Avoiding problems before they arise</h2></div></div></div> <p>All variables that contain lists of things should default @@ -10292,16 +10299,16 @@ DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz doesn't stand out. Nevertheless it is mentioned in many files.</p> </div> -<div class="sect1" title="24.3. Variable evaluation"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.var"></a>24.3. Variable evaluation</h2></div></div></div> -<div class="sect2" title="24.3.1. At load time"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.var.load"></a>24.3.1. At load time</h3></div></div></div> <p>Variable evaluation takes place either at load time or at runtime, depending on the context in which they occur. The contexts where variables are evaluated at load time are:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p>The right hand side of the <code class="literal">:=</code> and <code class="literal">!=</code> operators,</p></li> <li class="listitem"><p>Make directives like <code class="literal">.if</code> or @@ -10337,7 +10344,7 @@ CFLAGS+= -Wall paragraphs from above typically occur in completely unrelated files.</p> </div> -<div class="sect2" title="24.3.2. At runtime"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.var.run"></a>24.3.2. At runtime</h3></div></div></div> <p>After all the files have been loaded, the values of the @@ -10345,7 +10352,7 @@ CFLAGS+= -Wall the shell commands are expanded at this point.</p> </div> </div> -<div class="sect1" title="24.4. How can variables be specified?"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.varspec"></a>24.4. How can variables be specified?</h2></div></div></div> <p>There are many ways in which the definition and use of a @@ -10354,14 +10361,14 @@ CFLAGS+= -Wall <code class="literal">pkglint</code> developer's documentation for further details.</p> </div> -<div class="sect1" title="24.5. Designing interfaces for Makefile fragments"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.design.intf"></a>24.5. Designing interfaces for Makefile fragments</h2></div></div></div> <p>Most of the <code class="filename">.mk</code> files fall into one of the following classes. Cases where a file falls into more than one class should be avoided as it often leads to subtle bugs.</p> -<div class="sect2" title="24.5.1. Procedures with parameters"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.design.intf.proc"></a>24.5.1. Procedures with parameters</h3></div></div></div> <p>In a traditional imperative programming language some of @@ -10395,7 +10402,7 @@ CFLAGS+= -Wall assigned using the <code class="literal">:=</code> operator, which should be used only for this purpose.</p> </div> -<div class="sect2" title="24.5.2. Actions taken on behalf of parameters"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.design.intf.action"></a>24.5.2. Actions taken on behalf of parameters</h3></div></div></div> <p>Action files take some input parameters and may define @@ -10407,7 +10414,7 @@ CFLAGS+= -Wall <code class="filename">mk/subst.mk</code>.</p> </div> </div> -<div class="sect1" title="24.6. The order in which files are loaded"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.order"></a>24.6. The order in which files are loaded</h2></div></div></div> <p>Package <code class="filename">Makefile</code>s usually consist of @@ -10422,7 +10429,7 @@ CFLAGS+= -Wall matters.</p> <p>This section describes at which point the various files are loaded and gives reasons for that order.</p> -<div class="sect2" title="24.6.1. The order in bsd.prefs.mk"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.order.prefs"></a>24.6.1. The order in <code class="filename">bsd.prefs.mk</code> </h3></div></div></div> @@ -10447,7 +10454,7 @@ CFLAGS+= -Wall variables that have been cached in earlier phases of a package build.</p> </div> -<div class="sect2" title="24.6.2. The order in bsd.pkg.mk"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.order.pkg"></a>24.6.2. The order in <code class="filename">bsd.pkg.mk</code> </h3></div></div></div> @@ -10480,7 +10487,7 @@ CFLAGS+= -Wall </div> </div> </div> -<div class="chapter" title="Chapter 25. Regression tests"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="regression"></a>Chapter 25. Regression tests</h2></div></div></div> <div class="toc"> @@ -10503,12 +10510,12 @@ CFLAGS+= -Wall along with every important part of the pkgsrc infrastructure. This chapter describes how regression tests work in pkgsrc and how you can add new tests.</p> -<div class="sect1" title="25.1. The regression tests framework"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="regression.descr"></a>25.1. The regression tests framework</h2></div></div></div> <p></p> </div> -<div class="sect1" title="25.2. Running the regression tests"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="regression.run"></a>25.2. Running the regression tests</h2></div></div></div> <p>You first need to install the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_regress/README.html" target="_top"><code class="filename">pkgtools/pkg_regress</code></a> package, which @@ -10516,7 +10523,7 @@ CFLAGS+= -Wall can simply run that command, which will run all tests in the <code class="filename">regress</code> category.</p> </div> -<div class="sect1" title="25.3. Adding a new regression test"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="regression.new"></a>25.3. Adding a new regression test</h2></div></div></div> <p>Every directory in the <code class="filename">regress</code> @@ -10525,14 +10532,14 @@ CFLAGS+= -Wall that is included by the <span class="command"><strong>pkg_regress</strong></span> command. The following functions can be overridden to suit your needs.</p> -<div class="sect2" title="25.3.1. Overridable functions"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="regression.fun.override"></a>25.3.1. Overridable functions</h3></div></div></div> <p>These functions do not take any parameters. They are all called in <span class="quote">“<span class="quote">set -e</span>”</span> mode, so you should be careful to check the exitcodes of any commands you run in the test.</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">do_setup()</code></span></dt> <dd><p>This function prepares the environment for the test. By default it does nothing.</p></dd> @@ -10552,10 +10559,10 @@ CFLAGS+= -Wall test has been run. By default it does nothing.</p></dd> </dl></div> </div> -<div class="sect2" title="25.3.2. Helper functions"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="regression.fun.helper"></a>25.3.2. Helper functions</h3></div></div></div> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="varname">exit_status(expected)</code></span></dt> <dd><p>This function compares the exitcode of the <span class="command"><strong>do_test()</strong></span> function with its first parameter. @@ -10575,7 +10582,7 @@ CFLAGS+= -Wall </div> </div> </div> -<div class="chapter" title="Chapter 26. Porting pkgsrc"> +<div class="chapter"> <div class="titlepage"><div><div><h2 class="title"> <a name="porting"></a>Chapter 26. Porting pkgsrc</h2></div></div></div> <div class="toc"> @@ -10589,13 +10596,13 @@ CFLAGS+= -Wall operating systems, hardware architectures and compilers. This chapter explains the necessary steps to make pkgsrc even more portable.</p> -<div class="sect1" title="26.1. Porting pkgsrc to a new operating system"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="porting.opsys"></a>26.1. Porting pkgsrc to a new operating system</h2></div></div></div> <p>To port pkgsrc to a new operating system (called <code class="literal">MyOS</code> in this example), you need to touch the following files:</p> -<div class="variablelist"><dl> +<div class="variablelist"><dl class="variablelist"> <dt><span class="term"><code class="filename">pkgtools/bootstrap-mk-files/files/mods/<em class="replaceable"><code>MyOS</code></em>.sys.mk</code></span></dt> <dd><p>This file contains some basic definitions, for example the name of the C @@ -10639,16 +10646,16 @@ CFLAGS+= -Wall <p>Now, you should be able to build some basic packages, like <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/perl5/README.html" target="_top"><code class="filename">lang/perl5</code></a>, <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a>.</p> </div> -<div class="sect1" title="26.2. Adding support for a new compiler"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="porting.compiler"></a>26.2. Adding support for a new compiler</h2></div></div></div> <p>TODO</p> </div> </div> </div> -<div class="appendix" title="Appendix A. A simple example package: bison"> -<div class="titlepage"><div><div><h2 class="title"> -<a name="examples"></a>Appendix A. A simple example package: bison</h2></div></div></div> +<div class="appendix"> +<div class="titlepage"><div><div><h1 class="title"> +<a name="examples"></a>Appendix A. A simple example package: bison</h1></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> @@ -10667,10 +10674,10 @@ CFLAGS+= -Wall <span class="command"><strong>bison</strong></span> when Berkeley <span class="command"><strong>yacc</strong></span> is already present in the tree is beyond us, but it's useful for the purposes of this exercise.</p> -<div class="sect1" title="A.1. files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="example-files"></a>A.1. files</h2></div></div></div> -<div class="sect2" title="A.1.1. Makefile"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="example-Makefile"></a>A.1.1. Makefile</h3></div></div></div> <pre class="programlisting"> @@ -10691,7 +10698,7 @@ INFO_FILES= bison.info .include "../../mk/bsd.pkg.mk" </pre> </div> -<div class="sect2" title="A.1.2. DESCR"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="example-descr"></a>A.1.2. DESCR</h3></div></div></div> <pre class="programlisting"> @@ -10700,7 +10707,7 @@ improvements. Why you would want this when Berkeley <a class="citerefentry" hre of the NetBSD source tree is beyond me. </pre> </div> -<div class="sect2" title="A.1.3. PLIST"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="example-plist"></a>A.1.3. PLIST</h3></div></div></div> <pre class="programlisting"> @@ -10711,7 +10718,7 @@ share/bison.simple share/bison.hairy </pre> </div> -<div class="sect2" title="A.1.4. Checking a package with pkglint"> +<div class="sect2"> <div class="titlepage"><div><div><h3 class="title"> <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with <span class="command"><strong>pkglint</strong></span> </h3></div></div></div> @@ -10728,7 +10735,7 @@ looks fine.</pre> -Wall</strong></span> for a very thorough check.</p> </div> </div> -<div class="sect1" title="A.2. Steps for building, installing, packaging"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="steps-for-b-i-p"></a>A.2. Steps for building, installing, packaging</h2></div></div></div> <p>Create the directory where the package lives, @@ -10837,9 +10844,9 @@ Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre> ===> Cleaning for bison-1.25</pre> </div> </div> -<div class="appendix" title="Appendix B. Build logs"> -<div class="titlepage"><div><div><h2 class="title"> -<a name="logs"></a>Appendix B. Build logs</h2></div></div></div> +<div class="appendix"> +<div class="titlepage"><div><div><h1 class="title"> +<a name="logs"></a>Appendix B. Build logs</h1></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> @@ -10847,7 +10854,7 @@ Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre> <dt><span class="sect1"><a href="#logs.package">B.2. Packaging figlet</a></span></dt> </dl> </div> -<div class="sect1" title="B.1. Building figlet"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="logs.building"></a>B.1. Building figlet</h2></div></div></div> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong> @@ -10939,7 +10946,7 @@ cp figlet.6 /usr/pkg/man/man6 ===> Registering installation for figlet-2.2.1nb2 <code class="prompt">#</code></pre> </div> -<div class="sect1" title="B.2. Packaging figlet"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="logs.package"></a>B.2. Packaging figlet</h2></div></div></div> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong> @@ -10952,9 +10959,9 @@ Registering depends:. <code class="prompt">#</code></pre> </div> </div> -<div class="appendix" title="Appendix C. Directory layout of the pkgsrc FTP server"> -<div class="titlepage"><div><div><h2 class="title"> -<a name="ftp-layout"></a>Appendix C. Directory layout of the pkgsrc FTP server</h2></div></div></div> +<div class="appendix"> +<div class="titlepage"><div><div><h1 class="title"> +<a name="ftp-layout"></a>Appendix C. Directory layout of the pkgsrc FTP server</h1></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> @@ -10975,7 +10982,7 @@ source packages</a></span></dt> everything should look the same, no matter on which server you are. This directory contains some subdirectories, which are explained below.</p> -<div class="sect1" title="C.1. distfiles: The distributed source files"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ftp-distfiles"></a>C.1. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div> <p>The directory <code class="filename">distfiles</code> contains lots @@ -10985,19 +10992,19 @@ source packages</a></span></dt> explicitly contain a version number or are otherwise too generic (for example <code class="filename">release.tar.gz</code>).</p> </div> -<div class="sect1" title="C.2. misc: Miscellaneous things"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ftp-misc"></a>C.2. <code class="filename">misc</code>: Miscellaneous things</h2></div></div></div> <p>This directory contains things that individual pkgsrc developers find worth publishing.</p> </div> -<div class="sect1" title="C.3. packages: Binary packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ftp-packages"></a>C.3. <code class="filename">packages</code>: Binary packages</h2></div></div></div> <p>This directory contains binary packages for the various platforms that are supported by pkgsrc. Each subdirectory is of the form <em class="replaceable"><code>OPSYS</code></em>/<em class="replaceable"><code>ARCH</code></em>/<em class="replaceable"><code>OSVERSION_TAG</code></em>. The meaning of these variables is:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="varname">OPSYS</code> is the name of the operating system for which the packages have been built. The name is taken from the output of the <span class="command"><strong>uname</strong></span> @@ -11035,14 +11042,14 @@ source packages</a></span></dt> Besides that, there are various category directories that contain symbolic links to the real binary packages.</p> </div> -<div class="sect1" title="C.4. reports: Bulk build reports"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ftp-reports"></a>C.4. <code class="filename">reports</code>: Bulk build reports</h2></div></div></div> <p>Here are the reports from bulk builds, for those who want to fix packages that didn't build on some of the platforms. The structure of subdirectories should look like the one in <a class="xref" href="#ftp-packages" title="C.3. packages: Binary packages">Section C.3, “<code class="filename">packages</code>: Binary packages”</a>.</p> </div> -<div class="sect1" title="C.5. current, pkgsrc-20xxQy: source packages"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="ftp-source"></a>C.5. <code class="filename">current</code>, <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>: @@ -11060,9 +11067,9 @@ source packages</h2></div></div></div> which contains the state of pkgsrc when it was branched.</p> </div> </div> -<div class="appendix" title="Appendix D. Editing guidelines for the pkgsrc guide"> -<div class="titlepage"><div><div><h2 class="title"> -<a name="editing"></a>Appendix D. Editing guidelines for the pkgsrc guide</h2></div></div></div> +<div class="appendix"> +<div class="titlepage"><div><div><h1 class="title"> +<a name="editing"></a>Appendix D. Editing guidelines for the pkgsrc guide</h1></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> @@ -11072,13 +11079,13 @@ source packages</h2></div></div></div> </div> <p>This section contains information on editing the pkgsrc guide itself.</p> -<div class="sect1" title="D.1. Make targets"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="targets"></a>D.1. Make targets</h2></div></div></div> <p>The pkgsrc guide's source code is stored in <code class="filename">pkgsrc/doc/guide/files</code>, and several files are created from it:</p> -<div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.txt</code></p></li> <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.html</code></p></li> <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/docs/pkgsrc/" target="_top">http://www.NetBSD.org/docs/pkgsrc/</a></p></li> @@ -11088,38 +11095,38 @@ source packages</h2></div></div></div> PostScript version of the pkgsrc guide.</p></li> </ul></div> </div> -<div class="sect1" title="D.2. Procedure"> +<div class="sect1"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="procedure"></a>D.2. Procedure</h2></div></div></div> <p>The procedure to edit the pkgsrc guide is:</p> <div class="procedure"><ol class="procedure" type="1"> -<li class="step" title="Step 1"><p>Make sure you have the packages needed to +<li class="step"><p>Make sure you have the packages needed to regenerate the pkgsrc guide (and other XML-based NetBSD documentation) installed. These are <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/netbsd-doc/README.html" target="_top"><code class="filename">meta-pkgs/netbsd-doc</code></a> for creating the ASCII and HTML versions, and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/netbsd-doc-print/README.html" target="_top"><code class="filename">meta-pkgs/netbsd-doc-print</code></a> for the PostScript and PDF versions. You will need both packages installed, to make sure documentation is consistent across all formats.</p></li> -<li class="step" title="Step 2"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the +<li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the right directory. All further steps will take place here.</p></li> -<li class="step" title="Step 3"><p>Edit the XML file(s) in +<li class="step"><p>Edit the XML file(s) in <code class="filename">files/</code>.</p></li> -<li class="step" title="Step 4"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc +<li class="step"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc guide for valid XML and to build the final output files. If you get any errors at this stage, you can just edit the files, as there are only symbolic links in the working directory, pointing to the files in <code class="filename">files/</code>.</p></li> -<li class="step" title="Step 5"><p><span class="command"><strong>(cd files && cvs +<li class="step"><p><span class="command"><strong>(cd files && cvs commit)</strong></span></p></li> -<li class="step" title="Step 6"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to +<li class="step"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to regenerate the output files with the proper RCS Ids.</p></li> -<li class="step" title="Step 7"> +<li class="step"> <p>Run <span class="command"><strong>bmake regen</strong></span> to install and commit the files in both <code class="filename">pkgsrc/doc</code> and <code class="filename">htdocs</code>.</p> -<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>If you have added, removed or renamed some chapters, you need to synchronize them using <span class="command"><strong>cvs add</strong></span> or |