diff options
| author | rillig <rillig> | 2006-05-29 08:55:59 +0000 |
|---|---|---|
| committer | rillig <rillig> | 2006-05-29 08:55:59 +0000 |
| commit | d0a8b887d59e661353e7fefe43c1ceb297317f7b (patch) | |
| tree | f3717937c48105f05b821c6b4a3e465a66f1e81f /doc/pkgsrc.html | |
| parent | b3a113ef9577f01be6f0162a7f5fd98f024da082 (diff) | |
| download | pkgsrc-d0a8b887d59e661353e7fefe43c1ceb297317f7b.tar.gz | |
regen, this time with valid HTML.
Diffstat (limited to 'doc/pkgsrc.html')
| -rw-r--r-- | doc/pkgsrc.html | 1537 |
1 files changed, 778 insertions, 759 deletions
diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 14370e1ab02..b66c8fc8b8c 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -35,7 +35,8 @@ </h3> </div></div> <div><p class="copyright">Copyright © 1994-2006 The NetBSD Foundation, Inc</p></div> -<div xmlns="http://www.w3.org/TR/xhtml1/transitional"><p xmlns="" class="pubdate">$NetBSD: pkgsrc.xml,v 1.18 2006/05/19 22:05:09 rillig Exp $</p></div><div><div class="abstract"> +<div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.18 2006/05/19 22:05:09 rillig Exp $</p></div> +<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 @@ -153,17 +154,17 @@ <dd><dl> <dt><span class="chapter"><a href="#components">8. Package components - files, directories and contents</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="#components.Makefile">8.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code></a></span></dt> -<dt><span class="sect1"><a href="#components.distinfo">8.2. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code></a></span></dt> +<dt><span class="sect1"><a href="#components.Makefile">8.1. <code class="filename">Makefile</code></a></span></dt> +<dt><span class="sect1"><a href="#components.distinfo">8.2. <code class="filename">distinfo</code></a></span></dt> <dt><span class="sect1"><a href="#components.patches">8.3. patches/*</a></span></dt> <dt><span class="sect1"><a href="#other-mandatory-files">8.4. Other mandatory files</a></span></dt> <dt><span class="sect1"><a href="#components.optional">8.5. Optional files</a></span></dt> -<dt><span class="sect1"><a href="#work-dir">8.6. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work*</code></a></span></dt> -<dt><span class="sect1"><a href="#files-dir">8.7. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">files/*</code></a></span></dt> +<dt><span class="sect1"><a href="#work-dir">8.6. <code class="filename">work*</code></a></span></dt> +<dt><span class="sect1"><a href="#files-dir">8.7. <code class="filename">files/*</code></a></span></dt> </dl></dd> -<dt><span class="chapter"><a href="#makefile">9. Programming in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s</a></span></dt> +<dt><span class="chapter"><a href="#makefile">9. Programming in <code class="filename">Makefile</code>s</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="#makefile.variables">9.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> variables</a></span></dt> +<dt><span class="sect1"><a href="#makefile.variables">9.1. <code class="filename">Makefile</code> variables</a></span></dt> <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">9.1.1. Naming conventions</a></span></dt></dl></dd> <dt><span class="sect1"><a href="#makefile.code">9.2. Code snippets</a></span></dt> <dd><dl> @@ -177,7 +178,7 @@ <dt><span class="chapter"><a href="#plist">10. PLIST issues</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#rcs-id">10.1. RCS ID</a></span></dt> -<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> generation</a></span></dt> +<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt> <dt><span class="sect1"><a href="#print-PLIST">10.3. Tweaking output of <span><strong class="command">make print-PLIST</strong></span></a></span></dt> <dt><span class="sect1"><a href="#plist.misc">10.4. Variable substitution in PLIST</a></span></dt> <dt><span class="sect1"><a href="#manpage-compression">10.5. Man page compression</a></span></dt> @@ -188,14 +189,14 @@ <dt><span class="chapter"><a href="#buildlink">11. Buildlink methodology</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#converting-to-buildlink3">11.1. Converting packages to use buildlink3</a></span></dt> -<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="#anatomy-of-bl3">11.2.1. Anatomy of a buildlink3.mk file</a></span></dt> -<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code class="filename">buildlink3.mk</code> files</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file</a></span></dt> +<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt> <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">11.3.2. Global preferences for native or pkgsrc software</a></span></dt> </dl></dd> </dl></dd> @@ -224,7 +225,7 @@ <dt><span class="chapter"><a href="#options">13. Options handling</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#global-default-options">13.1. Global default options</a></span></dt> -<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code></a></span></dt> +<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt> <dt><span class="sect1"><a href="#option-names">13.3. Option Names</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="#build">14. The build process</a></span></dt> @@ -366,7 +367,17 @@ <dt><span class="sect1"><a href="#logs.building">B.1. Building figlet</a></span></dt> <dt><span class="sect1"><a href="#logs.package">B.2. Packaging figlet</a></span></dt> </dl></dd> -<dt><span class="appendix"><a href="#ftp-layout">C. Layout of the FTP server's package archive</a></span></dt> +<dt><span class="appendix"><a href="#ftp-layout">C. Directory layout of the pkgsrc FTP server</a></span></dt> +<dd><dl> +<dt><span class="sect1"><a href="#ftp-bootstrap">C.1. <code class="filename">bootstrap-pkgsrc</code>: Bootstrap kits</a></span></dt> +<dt><span class="sect1"><a href="#ftp-distfiles">C.2. <code class="filename">distfiles</code>: The distributed source files</a></span></dt> +<dt><span class="sect1"><a href="#ftp-iso">C.3. <code class="filename">iso</code>: Currently empty</a></span></dt> +<dt><span class="sect1"><a href="#ftp-misc">C.4. <code class="filename">misc</code>: Miscellaneous things</a></span></dt> +<dt><span class="sect1"><a href="#ftp-packages">C.5. <code class="filename">packages*</code>: Binary packages</a></span></dt> +<dt><span class="sect1"><a href="#ftp-source">C.6. <code class="filename">current</code>, +<code class="filename">200<em class="replaceable"><code>x</code></em>Q<em class="replaceable"><code>y</code></em></code>: +source packages</a></span></dt> +</dl></dd> <dt><span class="appendix"><a href="#editing">D. Editing guidelines for the pkgsrc guide</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#targets">D.1. Targets</a></span></dt> @@ -406,13 +417,13 @@ <p>pkgsrc currently contains several thousand packages, including:</p> <div class="itemizedlist"><ul type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/apache/README.html" target="_top"><code xmlns="" class="filename">www/apache</code></a> - The Apache +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/apache/README.html" target="_top"><code class="filename">www/apache</code></a> - The Apache web server</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html" target="_top"><code xmlns="" class="filename">www/mozilla</code></a> - The Mozilla +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html" target="_top"><code class="filename">www/mozilla</code></a> - The Mozilla web browser</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/gnome/README.html" target="_top"><code xmlns="" class="filename">meta-pkgs/gnome</code></a> - The GNOME +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/gnome/README.html" target="_top"><code class="filename">meta-pkgs/gnome</code></a> - The GNOME Desktop Environment</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/kde3/README.html" target="_top"><code xmlns="" class="filename">meta-pkgs/kde3</code></a> - The K +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/meta-pkgs/kde3/README.html" target="_top"><code class="filename">meta-pkgs/kde3</code></a> - The K Desktop Environment</p></li> </ul></div> <p>...just to name a few.</p> @@ -467,7 +478,7 @@ that describe what's necessary to build a certain piece of software using pkgsrc. Packages are traditionally stored under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc</code>.</p></dd> + <code class="filename">/usr/pkgsrc</code>.</p></dd> <dt><span class="term">The NetBSD package system</span></dt> <dd><p> This is the former name of “<span class="quote">pkgsrc</span>”. It is @@ -484,7 +495,7 @@ the distfile is in the form of a compressed tar-archive, but other types are possible, too. Distfiles are usually stored below - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/distfiles</code>.</p></dd> + <code class="filename">/usr/pkgsrc/distfiles</code>.</p></dd> <dt><span class="term">Port</span></dt> <dd><p>This is the term used by FreeBSD and OpenBSD people for what we call a package. @@ -493,11 +504,11 @@ <dt><span class="term">Precompiled/binary package</span></dt> <dd> <p>A set of binaries built with pkgsrc from a distfile - and stuffed together in a single <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.tgz</code> + and stuffed together in a single <code class="filename">.tgz</code> file so it can be installed on machines of the same machine architecture without the need to recompile. Packages are usually generated in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/packages</code>; there is also + <code class="filename">/usr/pkgsrc/packages</code>; there is also an archive on <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/" target="_top">ftp.NetBSD.org</a>.</p> <p>Sometimes, this is referred to by the term “<span class="quote">package</span>” too, especially in the context of precompiled packages.</p> @@ -529,7 +540,7 @@ package maintainer creates packages as described in <a href="#developers-guide" title="Part II. The pkgsrc developer's guide">Part II, “The pkgsrc developer's guide”</a>.</p></dd> <dt><span class="term">infrastructure developers</span></dt> <dd><p>These people are involved in all those files - that live in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/</code> directory and below. + that live in the <code class="filename">mk/</code> directory and below. Only these people should need to read through <a href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">Part III, “The pkgsrc infrastructure internals”</a>, though others might be curious, too.</p></dd> </dl></div> @@ -662,8 +673,8 @@ </dl> </div> <p>The most common location where pkgsrc is installed is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc</code> for the “<span class="quote">package - sources</span>” and <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> for the + <code class="filename">/usr/pkgsrc</code> for the “<span class="quote">package + sources</span>” and <code class="filename">/usr/pkg</code> for the installed binary packages. You are though free to install the sources and binary packages wherever you want in your filesystem, provided that both paths do not contain white-space @@ -689,15 +700,15 @@ <p>The primary download location for all pkgsrc files is <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a>. There are a number of subdirectories for different purposes, which are - described in detail in <a href="#ftp-layout" title="Appendix C. Layout of the FTP server's package archive">Appendix C, <i>Layout of the FTP server's package archive</i></a>.</p> + described in detail in <a href="#ftp-layout" title="Appendix C. Directory layout of the pkgsrc FTP server">Appendix C, <i>Directory layout of the pkgsrc FTP server</i></a>.</p> <p>The tar file for the current branch is in the directory - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">current</code> and is called <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc.tar.gz</code></a>. + <code class="filename">current</code> and is called <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>. It is autogenerated daily.</p> <p>The tar file for the stable branch 2006Q1 is in the - directory <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">2006Q1</code> and is also called <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/2006Q1/pkgsrc.tar.gz" target="_top"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc.tar.gz</code></a>.</p> + directory <code class="filename">2006Q1</code> and is also called <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/2006Q1/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p> <p>After downloading the tar file, change to the directory where you want to have pkgsrc. This is usually - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr</code>. Then, run <span><strong class="command">tar xfz + <code class="filename">/usr</code>. Then, run <span><strong class="command">tar xfz pkgsrc.tar.gz</strong></span> to extract the files.</p> </div> <div class="sect2" lang="en"> @@ -714,8 +725,8 @@ <p> in it, see the examples in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/share/examples/supfiles</code>, and that the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc</code> directory exists. Then, simply + <code class="filename">/usr/share/examples/supfiles</code>, and that the + <code class="filename">/usr/pkgsrc</code> directory exists. Then, simply run <span><strong class="command">sup -v <em class="replaceable"><code>/path/to/your/supfile</code></em></strong></span>.</p> </div> @@ -738,12 +749,12 @@ </pre> <p>Then, you change to the directory where you want to have your copy of pkgsrc. In most cases this is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr</code>. In that directory you run the + <code class="filename">/usr</code>. In that directory you run the checkout command, which is <span><strong class="command">cvs -q checkout -P pkgsrc</strong></span> for the current branch and <span><strong class="command">cvs -q checkout -rpkgsrc-2006Q1 -P pkgsrc</strong></span> for the stable branch. This command will create a directory called - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc</code> with all the pkgsrc files in + <code class="filename">pkgsrc</code> with all the pkgsrc files in it.</p> </div> </div> @@ -851,9 +862,9 @@ <p>See <a href="#getting" title="Chapter 2. Where to get pkgsrc and how to keep it up-to-date">Chapter 2, <i>Where to get pkgsrc and how to keep it up-to-date</i></a> for other ways to get pkgsrc before bootstrapping. The given <span><strong class="command">bootstrap</strong></span> command will use the defaults of - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> for the + <code class="filename">/usr/pkg</code> for the <span class="emphasis"><em>prefix</em></span> where programs will be installed in, - and <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/var/db/pkg</code> for the package database + and <code class="filename">/var/db/pkg</code> for the package database directory where pkgsrc will do its internal bookkeeping. However, these can also be set using command-line arguments.</p> @@ -861,7 +872,7 @@ available for supported platforms. An up-to-date list of these can be found on <a href="http://www.pkgsrc.org/" target="_top">www.pkgsrc.org</a>. Note that this only works for privileged builds that install - into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code>.</p> + into <code class="filename">/usr/pkg</code>.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p>The bootstrap installs a <span><strong class="command">bmake</strong></span> tool. @@ -908,17 +919,17 @@ <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="platform.osx-ufs"></a>3.2.1.2. Using a UFS partition</h4></div></div></div> -<p>By default, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr</code> will be on your root file +<p>By default, <code class="filename">/usr</code> will be on your root file system, normally HFS+. It is possible to use the default - <span class="emphasis"><em>prefix</em></span> of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> - by symlinking <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> to a directory on a UFS + <span class="emphasis"><em>prefix</em></span> of <code class="filename">/usr/pkg</code> + by symlinking <code class="filename">/usr/pkg</code> to a directory on a UFS file system. Obviously, another symlink is required if you want to place the package database directory outside the <span class="emphasis"><em>prefix</em></span>. e.g.</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>./bootstrap --pkgdbdir /usr/pkg/pkgdb</code></strong></pre> <p>If you created your partitions at the time of installing Mac OS X and formatted the target partition as UFS, it should automatically - mount on <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/Volumes/<volume name></code> when the + mount on <code class="filename">/Volumes/<volume name></code> when the machine boots. If you are (re)formatting a partition as UFS, you need to ensure that the partition map correctly reflects “<span class="quote">Apple_UFS</span>” and not “<span class="quote">Apple_HFS</span>”.</p> @@ -949,9 +960,9 @@ with the FreeBSD userland tools. There are several steps:</p> <div class="orderedlist"><ol type="1"> <li><p>FreeBSD stores its ports pkg database in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/var/db/pkg</code>. It is therefore + <code class="filename">/var/db/pkg</code>. It is therefore recommended that you choose a different location (e.g. - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgdb</code>) by + <code class="filename">/usr/pkgdb</code>) by using the --pkgdbdir option to the bootstrap script.</p></li> <li> <p>If you do not intend to use the FreeBSD ports tools, it's probably a @@ -962,8 +973,8 @@ <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_delete pkg_delete.orig</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong></pre> </li> -<li><p>An example <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> file will be placed in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf.example</code> file +<li><p>An example <code class="filename">/etc/mk.conf</code> file will be placed in + <code class="filename">/etc/mk.conf.example</code> file when you use the bootstrap script.</p></li> </ol></div> </div> @@ -1093,10 +1104,10 @@ <p>Interix has no native support for audio output. For audio support, pkgsrc uses the <span><strong class="command">esound</strong></span> client/server audio system on Interix. Unlike on most platforms, the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/audio/esound/README.html" target="_top"><code xmlns="" class="filename">audio/esound</code></a> package does + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/audio/esound/README.html" target="_top"><code class="filename">audio/esound</code></a> package does <span class="emphasis"><em>not</em></span> contain the <span><strong class="command">esd</strong></span> server component. To output audio via an Interix host, the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/emulators/cygwin_esound/README.html" target="_top"><code xmlns="" class="filename">emulators/cygwin_esound</code></a> package + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/emulators/cygwin_esound/README.html" target="_top"><code class="filename">emulators/cygwin_esound</code></a> package must also be installed.</p> </li> <li> @@ -1150,16 +1161,16 @@ with.</p> <p>Therefore, please make sure that you have no conflicting <code class="varname">CFLAGS</code> in your environment or the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. Particularly, make sure that you do not + <code class="filename">/etc/mk.conf</code>. Particularly, make sure that you do not try to link n32 object files with lib64 or vice versa. Check your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/compiler.defaults</code>!</p> + <code class="filename">/etc/compiler.defaults</code>!</p> <p>If you have the actual pkgsrc tree mounted via NFS from a different host, please make sure to set <code class="varname">WRKOBJDIR</code> to a local directory, as it appears that IRIX linker occasionally runs into issues when trying to link over a network-mounted file system.</p> <p>The bootstrapping process should set all the right options for programs such as imake(1), but you may want to set some options depending on your local - setup. Please see <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code> and, of + setup. Please see <code class="filename">pkgsrc/mk/defaults/mk.conf</code> and, of course, your compiler's man pages for details.</p> <p>If you are using SGI's MIPSPro compiler, please set @@ -1169,14 +1180,14 @@ </pre> <p> - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. Otherwise, pkgsrc will assume you + in <code class="filename">/etc/mk.conf</code>. Otherwise, pkgsrc will assume you are using gcc and may end up passing invalid flags to the compiler. Note that - bootstrap should create an appropriate <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf.example</code> by + bootstrap should create an appropriate <code class="filename">mk.conf.example</code> by default.</p> <p>If you have both the MIPSPro compiler chain installed as well as gcc, but want to make sure that MIPRPro is used, please set your <code class="varname">PATH</code> to <span class="emphasis"><em>not</em></span> include the location of gcc (often - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/freeware/bin</code>), and (important) pass the + <code class="filename">/usr/freeware/bin</code>), and (important) pass the '--preserve-path' flag.</p> </div> <div class="sect2" lang="en"> @@ -1207,15 +1218,15 @@ overridden so that __attribute__ is assumed supported by the compiler.</p> <p>After bootstrapping, you should set <code class="varname">PKGSRC_COMPILER</code> - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>:</p> + in <code class="filename">/etc/mk.conf</code>:</p> <pre class="programlisting"> PKGSRC_COMPILER= icc </pre> <p>The default installation directory for icc is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/opt/intel_cc_80</code>, which + <code class="filename">/opt/intel_cc_80</code>, which is also the pkgsrc default. If you have installed it into a different directory, set <code class="varname">ICCBASE</code> in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>:</p> + <code class="filename">/etc/mk.conf</code>:</p> <pre class="programlisting"> ICCBASE= /opt/icc </pre> @@ -1237,9 +1248,9 @@ with the OpenBSD userland tools. There are several steps:</p> <div class="orderedlist"><ol type="1"> <li><p>OpenBSD stores its ports pkg database in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/var/db/pkg</code>. It is therefore + <code class="filename">/var/db/pkg</code>. It is therefore recommended that you choose a different location (e.g. - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgdb</code>) by + <code class="filename">/usr/pkgdb</code>) by using the --pkgdbdir option to the bootstrap script.</p></li> <li> <p>If you do not intend to use the OpenBSD ports tools, it's probably a @@ -1251,10 +1262,10 @@ <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong></pre> </li> <li> -<p>An example <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> file will be placed in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf.example</code> file +<p>An example <code class="filename">/etc/mk.conf</code> file will be placed in + <code class="filename">/etc/mk.conf.example</code> file when you use the bootstrap script. OpenBSD's make program uses - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> + <code class="filename">/etc/mk.conf</code> as well. You can work around this by enclosing all the pkgsrc-specific parts of the file with:</p> <pre class="programlisting"> @@ -1286,8 +1297,8 @@ <span class="emphasis"><em>not</em></span> supported.</p> <p>Whichever compiler you use, please ensure the compiler tools and your $prefix are in your <code class="varname">PATH</code>. This includes - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/ccs/{bin,lib}</code> - and e.g. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg/{bin,sbin}</code>.</p> + <code class="filename">/usr/ccs/{bin,lib}</code> + and e.g. <code class="filename">/usr/pkg/{bin,sbin}</code>.</p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="solaris-gcc-note"></a>3.2.7.1. If you are using gcc</h4></div></div></div> @@ -1295,7 +1306,7 @@ for building all packages.</p> <p>It is recommended that an external gcc be used only for bootstrapping, then either build gcc from - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/gcc/README.html" target="_top"><code xmlns="" class="filename">lang/gcc</code></a> or install a binary gcc + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/gcc/README.html" target="_top"><code class="filename">lang/gcc</code></a> or install a binary gcc package, then remove gcc used during bootstrapping.</p> <p>Binary packages of gcc can be found through <a href="http://www.sun.com/bigadmin/common/freewareSearch.html" target="_top">http://www.sun.com/bigadmin/common/freewareSearch.html</a>.</p> </div> @@ -1315,7 +1326,7 @@ - Sun WorkShop Compilers common components</p></li> </ul></div> <p>You should set <code class="varname">CC</code>, <code class="varname">CXX</code> and - optionally, <code class="varname">CPP</code> in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, + optionally, <code class="varname">CPP</code> in <code class="filename">/etc/mk.conf</code>, e.g.:</p> <pre class="programlisting"> CC= cc @@ -1329,10 +1340,10 @@ <p>Building 64-bit binaries is a little trickier. First, you need to bootstrap pkgsrc in 64-bit mode. One problem here is that while building one of the programs in the bootstrap kit - (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bmake</code>), the <code class="varname">CFLAGS</code> + (<code class="filename">bmake</code>), the <code class="varname">CFLAGS</code> variable is not honored, even if it is set in the environment. To work around this bug, you can create a simple shell script - called <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">cc64</code> and put it somewhere in the + called <code class="filename">cc64</code> and put it somewhere in the <code class="varname">PATH</code>:</p> <pre class="programlisting"> #! /bin/sh @@ -1347,7 +1358,7 @@ <p>After bootstrapping, there are two alternative ways, depending on whether you want to find bugs in packages or get your system ready quickly. If you just want a running system, - add the following lines to your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf</code> + add the following lines to your <code class="filename">mk.conf</code> file:</p> <pre class="programlisting"> CC= cc64 @@ -1357,10 +1368,10 @@ <p>This way, all calls to the compiler will be intercepted by the above wrapper and therefore get the necessary ABI options automatically. (Don't forget to create the shell script - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">CC64</code>, too.)</p> + <code class="filename">CC64</code>, too.)</p> <p>To find packages that ignore the user-specified <code class="varname">CFLAGS</code> and <code class="varname">CXXFLAGS</code>, add - the following lines to your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf</code> + the following lines to your <code class="filename">mk.conf</code> file:</p> <pre class="programlisting"> CC= cc @@ -1380,15 +1391,15 @@ <div class="titlepage"><div><div><h4 class="title"> <a name="plat.sunos.problems"></a>3.2.7.4. Common problems</h4></div></div></div> <p>Sometimes, when using <span><strong class="command">libtool</strong></span>, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/bin/ksh</code> crashes with a segmentation fault. + <code class="filename">/bin/ksh</code> crashes with a segmentation fault. The workaround is to use another shell for the configure - scripts, for example by installing <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/bash/README.html" target="_top"><code xmlns="" class="filename">shells/bash</code></a> and adding the following lines - to your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf</code>:</p> + scripts, for example by installing <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a> and adding the following lines + to your <code class="filename">mk.conf</code>:</p> <pre class="programlisting"> CONFIG_SHELL= ${LOCALBASE}/bin/bash WRAPPER_SHELL= ${LOCALBASE}/bin/bash </pre> -<p>Then, rebuild the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/libtool-base/README.html" target="_top"><code xmlns="" class="filename">devel/libtool-base</code></a> package.</p> +<p>Then, rebuild the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/libtool-base/README.html" target="_top"><code class="filename">devel/libtool-base</code></a> package.</p> </div> </div> </div> @@ -1428,7 +1439,7 @@ operating systems, you need to install them first. For the following platforms, prebuilt versions of the package tools are available and can simply be downloaded and unpacked in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/</code> directory:</p> + <code class="filename">/</code> directory:</p> <div class="informaltable"> <a name="binary-bootstrap-kits"></a><table border="1"> <colgroup> @@ -1442,18 +1453,18 @@ <tbody> <tr> <td>Solaris 9</td> -<td><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/bootstrap-pkgsrc/</code></td> +<td><code class="filename">ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/bootstrap-pkgsrc/</code></td> </tr> <tr> <td>Solaris 10</td> -<td><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">http://public.enst.fr/pkgsrc/packages/bootstrap-pkgsrc/</code></td> +<td><code class="filename">http://public.enst.fr/pkgsrc/packages/bootstrap-pkgsrc/</code></td> </tr> </tbody> </table> </div> <p>These prebuilt package tools use - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> for the base directory, and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/var/db/pkg</code> for the database of installed + <code class="filename">/usr/pkg</code> for the base directory, and + <code class="filename">/var/db/pkg</code> for the database of installed packages. If you cannot use these directories for whatever reasons (maybe because you're not root), you have to build the package tools yourself, which is explained in <a href="#bootstrapping-pkgsrc" title="3.1. Bootstrapping pkgsrc">Section 3.1, “Bootstrapping pkgsrc”</a>.</p> @@ -1464,9 +1475,9 @@ where to get them. You can get them on CD-ROMs, DVDs, or via FTP or HTTP.</p> <p>For NetBSD, the binary packages are made available on - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp.NetBSD.org</code> and its mirrors, in the + <code class="filename">ftp.NetBSD.org</code> and its mirrors, in the directory - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/pub/NetBSD/packages/<em class="replaceable"><code>OSVERSION</code></em>/<em class="replaceable"><code>ARCH</code></em>/</code>. + <code class="filename">/pub/NetBSD/packages/<em class="replaceable"><code>OSVERSION</code></em>/<em class="replaceable"><code>ARCH</code></em>/</code>. For <em class="replaceable"><code>OSVERSION</code></em>, you should insert the output of <span><strong class="command">uname -r</strong></span>, and for <em class="replaceable"><code>ARCH</code></em> the output of <span><strong class="command">uname @@ -1486,11 +1497,11 @@ <tbody> <tr> <td>Solaris 9</td> -<td><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/</code></td> +<td><code class="filename">ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/</code></td> </tr> <tr> <td>Solaris 10</td> -<td><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">http://public.enst.fr/pkgsrc/packages/</code></td> +<td><code class="filename">http://public.enst.fr/pkgsrc/packages/</code></td> </tr> </tbody> </table> @@ -1498,11 +1509,11 @@ <p>Most of these directories contain the pkgsrc distribution for multiple platforms. Select the appropriate subdirectories, according to your machine architecture and operating system, - until you find a directory called <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">All</code>. This + until you find a directory called <code class="filename">All</code>. This directory contains all the binary packages. Further, there are subdirectories for categories that contain symbolic links that point to the actual binary package in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../All</code>. This directory layout is used for + <code class="filename">../All</code>. This directory layout is used for all package repositories, no matter if they are accessed via HTTP, FTP, NFS, CD-ROM, or the local filesystem.</p> </div> @@ -1525,21 +1536,21 @@ <code class="varname">PKG_PATH</code> environment variable to a semicolon-separated list of paths (including remote URLs); trailing slashes are not allowed. </p> -<p>Additionally to the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">All</code> directory - there exists a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">vulnerable</code> directory to +<p>Additionally to the <code class="filename">All</code> directory + there exists a <code class="filename">vulnerable</code> directory to which binary packages with known vulnerabilities are moved, since removing them could cause missing dependencies. To - use these packages, add the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">vulnerable</code> + use these packages, add the <code class="filename">vulnerable</code> directory to your <code class="varname">PKG_PATH</code>. However, you should run - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code xmlns="" class="filename">security/audit-packages</code></a> regularly, + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code class="filename">security/audit-packages</code></a> regularly, especially after installing new packages, and verify that the vulnerabilities are acceptable for your configuration. An example <code class="varname">PKG_PATH</code> would be: - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/vulnerable</code> + <code class="filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OSVERSION>/<ARCH>/vulnerable</code> Please note that semicolon (';') is a shell meta-character, so you'll probably have to quote it.</p> <p>After you've installed packages, be sure to have - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg/bin</code> and <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg/sbin</code> in your + <code class="filename">/usr/pkg/bin</code> and <code class="filename">/usr/pkg/sbin</code> in your <code class="varname">PATH</code> so you can actually start the just installed program. </p> </div> @@ -1582,19 +1593,19 @@ downloaded, pkgsrc will fetch them automatically.</p> <p>You can overwrite some of the major distribution sites to fit to sites that are close to your own. Have a look at - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code> to find some examples + <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to find some examples — in particular, look for the <code class="varname">MASTER_SORT</code>, <code class="varname">MASTER_SORT_REGEX</code> and <code class="varname">INET_COUNTRY</code> definitions. This may save some of your bandwidth and time.</p> <p>You can change these settings either in your shell's environment, or, if you want to keep the settings, by editing the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> file, + <code class="filename">/etc/mk.conf</code> file, and adding the definitions there.</p> <p>If you don't have a permanent Internet connection and you want to know which files to download, <span><strong class="command">make fetch-list</strong></span> will tell you what you'll need. Put these distfiles into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/distfiles</code>.</p> + <code class="filename">/usr/pkgsrc/distfiles</code>.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> @@ -1622,25 +1633,25 @@ <p>Taking the figlet utility as an example, we can install it on our system by building as shown in <a href="#logs" title="Appendix B. Build logs">Appendix B, <i>Build logs</i></a>.</p> <p>The program is installed under the default root of the packages tree - - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code>. Should this not conform to your tastes, + <code class="filename">/usr/pkg</code>. Should this not conform to your tastes, set the <code class="varname">LOCALBASE</code> variable in your environment, and it will use that value as the root of - your packages tree. So, to use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/local</code>, set + your packages tree. So, to use <code class="filename">/usr/local</code>, set <code class="varname">LOCALBASE=/usr/local</code> in your environment. Please note that you should use a directory which is dedicated to packages and not shared with other programs (i.e., do not try and use <code class="varname">LOCALBASE=/usr</code>). Also, you should not try to - add any of your own files or directories (such as <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">src/</code>, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">obj/</code>, or <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/</code>) below the + add any of your own files or directories (such as <code class="filename">src/</code>, + <code class="filename">obj/</code>, or <code class="filename">pkgsrc/</code>) below the <code class="varname">LOCALBASE</code> tree. This is to prevent possible conflicts between programs and other files installed by the package system and whatever else may have been installed there.</p> -<p>Some packages look in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to alter some +<p>Some packages look in <code class="filename">/etc/mk.conf</code> to alter some configuration options at build time. Have a look at - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code> to + <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to get an overview of what will be set there by default. Environment variables such as <code class="varname">LOCALBASE</code> - can be set in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to + can be set in <code class="filename">/etc/mk.conf</code> to save having to remember to set them each time you want to use pkgsrc.</p> <p>Occasionally, people want to “<span class="quote">look under the covers</span>” to see what is going on when a package is building or being installed. This may be @@ -1675,7 +1686,7 @@ <code class="varname">BINPKG_SITES</code>, which defaults to ftp.NetBSD.org. Any flags that should be added to <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> can be put into <code class="varname">BIN_INSTALL_FLAGS</code>. - See <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code> for more details.</p> + See <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more details.</p> <p>A final word of warning: If you set up a system that has a non-standard setting for <code class="varname">LOCALBASE</code>, be sure to set that before any packages are installed, as you can not use several directories @@ -1683,7 +1694,7 @@ properly detect your installed packages, and fail miserably. Note also that precompiled binary packages are usually built with the default <code class="varname">LOCALBASE</code> of - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code>, and that you should <span class="emphasis"><em>not</em></span> + <code class="filename">/usr/pkg</code>, and that you should <span class="emphasis"><em>not</em></span> install any if you use a non-standard <code class="varname">LOCALBASE</code>.</p> </div> <div class="sect2" lang="en"> @@ -1747,36 +1758,36 @@ <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 pkgsrc packages. The preferred method of setting these variables - is by setting them in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. + is by setting them in <code class="filename">/etc/mk.conf</code>. </p> <div class="itemizedlist"><ul type="disc"> <li><p><code class="varname">LOCALBASE</code>: Where packages will be installed. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code>. Do not mix binary packages + <code class="filename">/usr/pkg</code>. Do not mix binary packages with different <code class="varname">LOCALBASE</code>s!</p></li> <li><p><code class="varname">CROSSBASE</code>: Where “<span class="quote">cross</span>” category packages will be installed. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${LOCALBASE}/cross</code>.</p></li> + <code class="filename">${LOCALBASE}/cross</code>.</p></li> <li><p><code class="varname">X11BASE</code>: Where X11 is installed on the system. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/X11R6</code>.</p></li> + <code class="filename">/usr/X11R6</code>.</p></li> <li><p><code class="varname">DISTDIR</code>: Where to store the downloaded copies of the original source distributions used for building pkgsrc packages. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKGSRCDIR}/distfiles</code>.</p></li> + <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li> <li><p><code class="varname">MASTER_SITE_OVERRIDE</code>: If set, override the packages' <code class="varname">MASTER_SITES</code> with this value.</p></li> <li><p><code class="varname">MASTER_SITE_BACKUP</code>: Backup location(s) for distribution files and patch files if not found locally or in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${MASTER_SITES}</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PATCH_SITES}</code> respectively. + <code class="filename">${MASTER_SITES}</code> or + <code class="filename">${PATCH_SITES}</code> respectively. The defaults are - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}/</code> + <code class="filename">ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/${DIST_SUBDIR}/</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/</code>.</p></li> + <code class="filename">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/</code>.</p></li> <li><p><code class="varname">BINPKG_SITES</code>: List of sites carrying binary pkgs.</p></li> </ul></div> @@ -1791,14 +1802,14 @@ <div class="itemizedlist"><ul type="disc"> <li><p><code class="varname">PACKAGES</code>: The top level directory for the binary packages. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKGSRCDIR}/packages</code>.</p></li> + <code class="filename">${PKGSRCDIR}/packages</code>.</p></li> <li><p><code class="varname">WRKOBJDIR</code>: The top level directory where, if defined, the separate working directories will get created, and symbolically - linked to from <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKDIR}</code> (see below). + linked to from <code class="filename">${WRKDIR}</code> (see below). This is useful for building packages on several - architectures, then <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKGSRCDIR}</code> - can be NFS-mounted while <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKOBJDIR}</code> + architectures, then <code class="filename">${PKGSRCDIR}</code> + can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code> is local to every architecture. (It should be noted that <code class="varname">PKGSRCDIR</code> should not be set by the user — it is an internal definition which refers to the @@ -1812,11 +1823,11 @@ release (“<span class="quote">2.0</span>”, etc.) and architecture (“<span class="quote">mipsel</span>”, etc.).</p></li> <li><p><code class="varname">PKGMAKECONF</code>: Location of - the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf</code> file used by a package's + the <code class="filename">mk.conf</code> file used by a package's BSD-style Makefile. If this is not set, <code class="varname">MAKECONF</code> is set to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/dev/null</code> to avoid picking up - settings used by builds in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/src</code>.</p></li> + <code class="filename">/dev/null</code> to avoid picking up + settings used by builds in <code class="filename">/usr/src</code>.</p></li> </ul></div> <p> </p> @@ -1858,7 +1869,7 @@ </p></li> <li><p><code class="varname">SKIP_AUDIT_PACKAGES</code>: If this is set to “<span class="quote">yes</span>”, the automated security checks - (which use the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code xmlns="" class="filename">security/audit-packages</code></a> + (which use the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code class="filename">security/audit-packages</code></a> package) will be <span class="strong"><strong>entirely</strong></span> skipped for <span class="strong"><strong>all</strong></span> packages built. Normally you'll want to use ALLOW_VULNERABILITIES instead of this. @@ -1890,7 +1901,7 @@ These options are currently enabled: mozilla ssl </pre> <p>The following variables can be defined in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to select which options to enable + <code class="filename">/etc/mk.conf</code> to select which options to enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>, which can be used to select or disable options for all packages that support them, and <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>, @@ -1921,12 +1932,12 @@ PKG_OPTIONS.apache= suexec </pre> <p>Before the options framework was introduced, build options were selected by setting a variable (often named <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> for each option. To ease transition + <code class="filename">/etc/mk.conf</code> for each option. To ease transition to the options framework for the user, these legacy variables are converted to the appropriate options setting (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>) automatically. A warning is issued to prompt the user to - update <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to use the options framework + update <code class="filename">/etc/mk.conf</code> to use the options framework directly. Support for the legacy variables will be removed eventually.</p> </div> @@ -1977,9 +1988,9 @@ PKG_OPTIONS.apache= suexec </pre> and then build a binary package from what was installed. You can then use the <span><strong class="command">pkg_*</strong></span> tools to manipulate it. Binary packages are created by default in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/packages</code>, in the form of a + <code class="filename">/usr/pkgsrc/packages</code>, in the form of a gzipped tar file. See <a href="#logs.package" title="B.2. Packaging figlet">Section B.2, “Packaging figlet”</a> for a - continuation of the above <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/misc/figlet/README.html" target="_top"><code xmlns="" class="filename">misc/figlet</code></a> example.</p> + continuation of the above <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/misc/figlet/README.html" target="_top"><code class="filename">misc/figlet</code></a> example.</p> <p> See <a href="#submit" title="Chapter 18. Submitting and Committing">Chapter 18, <i>Submitting and Committing</i></a> for information on how to submit such a binary package.</p> @@ -2008,23 +2019,23 @@ PKG_OPTIONS.apache= suexec </pre> <a name="binary.configuration"></a>6.3.1. Configuration</h3></div></div></div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="binary.bulk.build.conf"></a>6.3.1.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf</code></h4></div></div></div> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf</code> file is the main +<a name="binary.bulk.build.conf"></a>6.3.1.1. <code class="filename">build.conf</code></h4></div></div></div> +<p>The <code class="filename">build.conf</code> file is the main configuration file for bulk builds. You can configure how your copy of pkgsrc is kept up to date, how the distfiles are downloaded, how the packages are built and how the report is generated. You can find an annotated example file in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bulk/build.conf-example</code>. To use - it, copy <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf-example</code> to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf</code> and edit it, following the + <code class="filename">pkgsrc/mk/bulk/build.conf-example</code>. To use + it, copy <code class="filename">build.conf-example</code> to + <code class="filename">build.conf</code> and edit it, following the comments in that file.</p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="binary.mk.conf"></a>6.3.1.2. /etc/mk.conf</h4></div></div></div> <p>You may want to set variables in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. - Look at <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code> for + <code class="filename">/etc/mk.conf</code>. + Look at <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for details of the default settings. You will want to ensure that <code class="varname">ACCEPTABLE_LICENSES</code> meet your local policy. As used in this example, <code class="varname">_ACCEPTABLE=yes</code> @@ -2041,7 +2052,7 @@ PKG_OPTIONS.apache= suexec </pre> </pre> <p>Some options that are especially useful for bulk builds can be found at the top lines of the file - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bulk/bsd.bulk-pkg.mk</code>. The most useful + <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 type="disc"> <li><p>If you are on a slow machine, you may want to @@ -2068,11 +2079,11 @@ PKG_OPTIONS.apache= suexec </pre> build system from even trying to build them, so possible building errors would not show up.</p></li> <li><p><code class="varname">CHECK_FILES</code> - (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bsd.pkg.check.mk</code>) can be set to + (<code class="filename">pkgsrc/mk/bsd.pkg.check.mk</code>) can be set to “<span class="quote">yes</span>” to check that the installed set of files - matches the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>.</p></li> + matches the <code class="filename">PLIST</code>.</p></li> <li><p><code class="varname">CHECK_INTERPRETER</code> - (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bsd.pkg.check.mk</code>) can be set to + (<code class="filename">pkgsrc/mk/bsd.pkg.check.mk</code>) can be set to “<span class="quote">yes</span>” to check that the installed “<span class="quote">#!</span>”-scripts will find their interpreter.</p></li> @@ -2080,15 +2091,15 @@ PKG_OPTIONS.apache= suexec </pre> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="pre-build.local"></a>6.3.1.3. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pre-build.local</code></h4></div></div></div> +<a name="pre-build.local"></a>6.3.1.3. <code class="filename">pre-build.local</code></h4></div></div></div> <p>It is possible to configure the bulk build to perform certain site-specific tasks at the end of the pre-build stage. If the file - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pre-build.local</code> exists in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/mk/bulk</code>, it will be executed + <code class="filename">pre-build.local</code> exists in + <code class="filename">/usr/pkgsrc/mk/bulk</code>, it will be executed (as a <a href="http://netbsd.gw.com/cgi-bin/man-cgi?sh+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span></a> script) at the end of the usual pre-build stage. An example use of - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pre-build.local</code> is to have the line:</p> + <code class="filename">pre-build.local</code> is to have the line:</p> <pre class="screen">echo "I do not have enough disk space to build this pig." \ > misc/openoffice/$BROKENF</pre> <p>to prevent the system from trying to build a particular package @@ -2098,18 +2109,18 @@ PKG_OPTIONS.apache= suexec </pre> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="other-environmental-considerations"></a>6.3.2. Other environmental considerations</h3></div></div></div> -<p>As <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> will be completely +<p>As <code class="filename">/usr/pkg</code> will be completely deleted at the start of bulk builds, make sure your login shell is placed somewhere else. Either drop it into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/local/bin</code> (and adjust your login + <code class="filename">/usr/local/bin</code> (and adjust your login shell in the passwd file), or (re-)install it via - <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> from <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/rc.local</code>, so + <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> from <code class="filename">/etc/rc.local</code>, so you can login after a reboot (remember that your current process won't die if the package is removed, you just can't start any new instances of the shell any more). Also, if you use NetBSD earlier than 1.5, or you still want to use the pkgsrc version of ssh for some reason, be sure to install ssh before - starting it from <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">rc.local</code>:</p> + starting it from <code class="filename">rc.local</code>:</p> <pre class="programlisting"> ( cd /usr/pkgsrc/security/ssh ; make bulk-install ) if [ -f /usr/pkg/etc/rc.d/sshd ]; then @@ -2133,7 +2144,7 @@ PKG_OPTIONS.apache= suexec </pre> </div> <p>Be sure to remove all other things that might interfere with builds, like some libs installed in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/local</code>, etc. then become root and type:</p> + <code class="filename">/usr/local</code>, etc. then become root and type:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>sh mk/bulk/build</code></strong></pre> <p>If for some reason your last build didn't complete (power @@ -2143,7 +2154,7 @@ PKG_OPTIONS.apache= suexec </pre> <p> At the end of the bulk build, you will get a summary via mail, and find build logs in the directory specified by - <code class="varname">FTP</code> in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf</code> + <code class="varname">FTP</code> in the <code class="filename">build.conf</code> file. </p> </div> @@ -2168,15 +2179,15 @@ PKG_OPTIONS.apache= suexec </pre> <dt><span class="term">3. post-build</span></dt> <dd><p> Generates a report that's placed in the directory - specified in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">build.conf</code> file - named <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">broken.html</code>, a short version + specified in the <code class="filename">build.conf</code> file + named <code class="filename">broken.html</code>, a short version of that report will also be mailed to the build's admin.</p></dd> </dl></div> <p> During the build, a list of broken packages will be compiled - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/.broken</code> (or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.../.broken.${MACHINE}</code> if + in <code class="filename">/usr/pkgsrc/.broken</code> (or + <code class="filename">.../.broken.${MACHINE}</code> if <code class="varname">OBJMACHINE</code> is set), individual build logs of broken builds can be found in the package's directory. These files are used by the bulk-targets to mark @@ -2221,14 +2232,14 @@ PKG_OPTIONS.apache= suexec </pre> </p> <p> The first step is to set up a chroot sandbox, - e.g. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/sandbox</code>. This can be done by + e.g. <code class="filename">/usr/sandbox</code>. This can be done by using null mounts, or manually. </p> <p> There is a shell script called - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bulk/mksandbox</code> which will set + <code class="filename">pkgsrc/mk/bulk/mksandbox</code> which will set up the sandbox environment using null mounts. It will also - create a script called <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">sandbox</code> in the + create a script called <code class="filename">sandbox</code> in the root of the sandbox environment, which will allow the null mounts to be activated using the <span><strong class="command">sandbox mount</strong></span> command and deactivated using the @@ -2238,7 +2249,7 @@ PKG_OPTIONS.apache= suexec </pre> To set up a sandbox environment by hand, after extracting all the sets from a NetBSD installation or doing a <span><strong class="command">make distribution DESTDIR=/usr/sandbox</strong></span> in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/src/etc</code>, be sure the following items + <code class="filename">/usr/src/etc</code>, be sure the following items are present and properly configured: </p> <div class="procedure"><ol type="1"> @@ -2247,11 +2258,11 @@ PKG_OPTIONS.apache= suexec </pre> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cp /netbsd /usr/sandbox</code></strong></pre> </li> <li> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/dev/*</code></p> +<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> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/resolv.conf</code> (for <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/smtpd/README.html" target="_top"><code xmlns="" class="filename">security/smtpd</code></a> and mail):</p> +<p><code class="filename">/etc/resolv.conf</code> (for <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> @@ -2259,26 +2270,26 @@ PKG_OPTIONS.apache= suexec </pre> <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> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/localtime</code> (for <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/smtpd/README.html" target="_top"><code xmlns="" class="filename">security/smtpd</code></a>):</p> +<p><code class="filename">/etc/localtime</code> (for <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/src</code> (system sources, - e. g. for <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/aperture/README.html" target="_top"><code xmlns="" class="filename">sysutils/aperture</code></a>):</p> +<p><code class="filename">/usr/src</code> (system sources, + e. g. for <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> -<p>Create <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/var/db/pkg</code> (not part of default install):</p> +<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> -<p>Create <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code> (not part of default install):</p> +<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> <p>Checkout pkgsrc via cvs into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/sandbox/usr/pkgsrc</code>:</p> + <code class="filename">/usr/sandbox/usr/pkgsrc</code>:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sandbox/usr</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -d -P pkgsrc</code></strong></pre> <p>Do not mount/link this to the copy of your pkgsrc tree @@ -2286,12 +2297,12 @@ PKG_OPTIONS.apache= suexec </pre> </p> </li> <li><p>Make - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/sandbox/usr/pkgsrc/packages</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.../distfiles</code> point somewhere + <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><p>Edit <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, see <a href="#binary.mk.conf" title="6.3.1.2. /etc/mk.conf">Section 6.3.1.2, “/etc/mk.conf”</a>.</p></li> -<li><p>Adjust <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bulk/build.conf</code> to suit your needs.</p></li> +<li><p>Edit <code class="filename">/etc/mk.conf</code>, see <a href="#binary.mk.conf" title="6.3.1.2. /etc/mk.conf">Section 6.3.1.2, “/etc/mk.conf”</a>.</p></li> +<li><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> @@ -2301,17 +2312,17 @@ PKG_OPTIONS.apache= suexec </pre> This will just jump inside the sandbox and start building. At the end of the build, mail will be sent with the results of the build. Created binary pkgs will be in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/sandbox/usr/pkgsrc/packages</code> + <code class="filename">/usr/sandbox/usr/pkgsrc/packages</code> (wherever that points/mounts to/from).</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="building-a-partial-set"></a>6.3.7. Building a partial set of packages</h3></div></div></div> <p> In addition to building a complete set of all packages in - pkgsrc, the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bulk/build</code> script + pkgsrc, the <code class="filename">pkgsrc/mk/bulk/build</code> script may be used to build a subset of the packages contained in pkgsrc. By setting <code class="varname">SPECIFIC_PKGS</code> - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, the variables</p> + in <code class="filename">/etc/mk.conf</code>, the variables</p> <div class="itemizedlist"><ul type="disc"> <li><p>SITE_SPECIFIC_PKGS</p></li> <li><p>HOST_SPECIFIC_PKGS</p></li> @@ -2339,18 +2350,18 @@ PKG_OPTIONS.apache= suexec </pre> If you would like to automatically create checksum files for the binary packages you intend to upload, remember to set <code class="varname">MKSUMS=yes</code> in your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bulk/build.conf</code>. + <code class="filename">mk/bulk/build.conf</code>. </p> <p> If you would like to PGP sign the checksum files (highly recommended!), remember to set <code class="varname">SIGN_AS=username@NetBSD.org</code> in your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bulk/build.conf</code>. This will prompt you for + <code class="filename">mk/bulk/build.conf</code>. This will prompt you for your GPG password to sign the files before uploading everything. </p> <p> Then, make sure that you have <code class="varname">RSYNC_DST</code> - set properly in your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bulk/build.conf</code> + set properly in your <code class="filename">mk/bulk/build.conf</code> file, i.e. adjust it to something like one of the following: </p> <pre class="screen">RSYNC_DST=ftp.NetBSD.org:/pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload </pre> @@ -2361,16 +2372,16 @@ PKG_OPTIONS.apache= suexec </pre> login "hubertf", I use:</p> <pre class="screen">RSYNC_DST=hubertf@ftp.NetBSD.org:/pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload </pre> <p> - A separate <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">upload</code> directory is used + A separate <code class="filename">upload</code> directory is used here to allow "closing" the directory during upload. To do so, run the following command on ftp.NetBSD.org next: </p> <pre class="screen">nbftp% <strong class="userinput"><code>mkdir -p -m 750 /pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch/upload</code></strong></pre> <p> - Please note that <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/pub/NetBSD/packages</code> is + Please note that <code class="filename">/pub/NetBSD/packages</code> is only appropriate for packages for the NetBSD operating system. Binary packages for other operating systems should go - into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/pub/pkgsrc</code>. + into <code class="filename">/pub/pkgsrc</code>. </p> <p> Before uploading the binary pkgs, ssh authentication needs to @@ -2383,8 +2394,8 @@ chroot-<code class="prompt">#</code> <strong class="userinput"><code>rm $HOME/.s chroot-<code class="prompt">#</code> <strong class="userinput"><code>ssh-keygen -t dsa</code></strong> chroot-<code class="prompt">#</code> <strong class="userinput"><code>cat $HOME/.ssh/id-dsa.pub</code></strong> </pre> <p> - Now take the output of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">id-dsa.pub</code> and - append it to your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">~/.ssh/authorized_keys</code> + Now take the output of <code class="filename">id-dsa.pub</code> and + append it to your <code class="filename">~/.ssh/authorized_keys</code> file on ftp.NetBSD.org. You can remove the key after the upload is done! </p> @@ -2407,7 +2418,7 @@ chroot-<code class="prompt">#</code> <strong class="userinput"><code>cat $HOME/. <a href="http://netbsd.gw.com/cgi-bin/man-cgi?du+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">du</span>(1)</span></a> on the FTP server to monitor progress of the upload. The upload script will take care of not uploading restricted packages and putting vulnerable packages into the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">vulnerable</code> subdirectory. + <code class="filename">vulnerable</code> subdirectory. </p> <p> After the upload has ended, first thing is to revoke ssh access: @@ -2417,7 +2428,7 @@ Gdd:x! </pre> <p> Use whatever is needed to remove the key you've entered before! Last, move the uploaded packages out of the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">upload</code> directory to have them accessible + <code class="filename">upload</code> directory to have them accessible to everyone: </p> <pre class="screen">nbftp% <strong class="userinput"><code>cd /pub/NetBSD/packages/pkgsrc-200xQy/NetBSD-a.b.c/arch</code></strong> @@ -2433,7 +2444,7 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong> </pre> After your pkgsrc bulk-build has completed, you may wish to create a CD-ROM set of the resulting binary packages to assist in installing packages on other machines. The - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/cdpack/README.html" target="_top"><code xmlns="" class="filename">pkgtools/cdpack</code></a> package provides + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/cdpack/README.html" target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides a simple tool for creating the ISO 9660 images. <span><strong class="command">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 @@ -2446,15 +2457,15 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong> </pre> Complete documentation for cdpack is found in the cdpack(1) man page. The following short example assumes that the binary packages are left in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/packages/All</code> and that - sufficient disk space exists in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/u2</code> to + <code class="filename">/usr/pkgsrc/packages/All</code> and that + sufficient disk space exists in <code class="filename">/u2</code> to hold the ISO 9660 images.</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>mkdir /u2/images</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong></pre> <p> If you wish to include a common set of files - (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">COPYRIGHT</code>, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README</code>, + (<code class="filename">COPYRIGHT</code>, <code class="filename">README</code>, etc.) on each CD in the collection, then you need to create a directory which contains these files. e.g. </p> @@ -2467,8 +2478,8 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong> </pre> <code class="prompt">#</code> <strong class="userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong></pre> <p>Now create the images:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong></pre> -<p>Each image will contain <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README</code>, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">COPYING</code>, and <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bin/myscript</code> +<p>Each image will contain <code class="filename">README</code>, + <code class="filename">COPYING</code>, and <code class="filename">bin/myscript</code> in their root directories.</p> </div> </div> @@ -2550,83 +2561,83 @@ it contains items for both pkgsrc users and developers.</p> <a name="pkgviews-docs"></a>7.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 xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/buildlink3/PKGVIEWS_UG</code>.</p> +<code class="filename">pkgsrc/mk/buildlink3/PKGVIEWS_UG</code>.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="faq-pkgtools"></a>7.3. Utilities for package management (pkgtools)</h2></div></div></div> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/pkgtools</code> directory pkgtools contains +<p>The <code class="filename">pkgsrc/pkgtools</code> directory pkgtools contains a number of useful utilities for both users and developers of pkgsrc. This 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 type="disc"><li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/x11-links/README.html" target="_top"><code xmlns="" class="filename">pkgtools/x11-links</code></a>: +<div class="itemizedlist"><ul type="disc"><li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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 type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/digest/README.html" target="_top"><code xmlns="" class="filename">pkgtools/digest</code></a>: +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/digest/README.html" target="_top"><code class="filename">pkgtools/digest</code></a>: Calculates various kinds of checksums (including SHA1).</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/libnbcompat/README.html" target="_top"><code xmlns="" class="filename">pkgtools/libnbcompat</code></a>: +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/libnbcompat/README.html" target="_top"><code class="filename">pkgtools/libnbcompat</code></a>: Compatibility library for pkgsrc tools.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/mtree/README.html" target="_top"><code xmlns="" class="filename">pkgtools/mtree</code></a>: Installed on +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/mtree/README.html" target="_top"><code class="filename">pkgtools/mtree</code></a>: Installed on non-BSD systems due to lack of native mtree. </p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_install</code></a>: +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a>: Up-to-date replacement for - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/sbin/pkg_install</code>, or for use on operating + <code class="filename">/usr/sbin/pkg_install</code>, or for use on operating systems where pkg_install is not present.</p></li> </ul></div> <p>Utilities used by pkgsrc (not automatically installed):</p> <div class="itemizedlist"><ul type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_tarup/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_tarup</code></a>: +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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><strong class="command">make replace</strong></span> to save the old package.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/dfdisk/README.html" target="_top"><code xmlns="" class="filename">pkgtools/dfdisk</code></a>: +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/dfdisk/README.html" target="_top"><code class="filename">pkgtools/dfdisk</code></a>: Adds extra functionality to pkgsrc, allowing it to fetch distfiles from multiple locations. It currently supports the following methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html" target="_top"><code xmlns="" class="filename">pkgtools/xpkgwedge</code></a>: Put X11 +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html" target="_top"><code class="filename">pkgtools/xpkgwedge</code></a>: Put X11 packages someplace else (enabled by default).</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html" target="_top"><code xmlns="" class="filename">devel/cpuflags</code></a>: Determine the +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html" target="_top"><code class="filename">devel/cpuflags</code></a>: Determine the best compiler flags to optimise code for your current CPU and compiler.</p></li> </ul></div> <p>Utilities for keeping track of installed packages, being up to date, etc:</p> <div class="itemizedlist"><ul type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_chk</code></a>: Reports on +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdep</code></a>: Makes +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a>: Makes dependency graphs of packages, to aid in choosing a strategy for updating.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdepgraph/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdepgraph</code></a>: Makes - graphs from the output of <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdep</code></a> (uses graphviz).</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkglint</code></a>: The +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdepgraph/README.html" target="_top"><code class="filename">pkgtools/pkgdepgraph</code></a>: Makes + graphs from the output of <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a> (uses graphviz).</p></li> +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>: The pkglint(1) program checks a pkgsrc entry for errors, lintpkgsrc(1) does various checks on the complete pkgsrc system.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgsurvey/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgsurvey</code></a>: Report what +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgsurvey/README.html" target="_top"><code class="filename">pkgtools/pkgsurvey</code></a>: Report what packages you have installed.</p></li> </ul></div> <p>Utilities for people maintaining or creating individual packages:</p> <div class="itemizedlist"><ul type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdiff</code></a>: Automate +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/rpm2pkg/README.html" target="_top"><code xmlns="" class="filename">pkgtools/rpm2pkg</code></a>, - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code xmlns="" class="filename">pkgtools/url2pkg</code></a>: Aids in +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/rpm2pkg/README.html" target="_top"><code class="filename">pkgtools/rpm2pkg</code></a>, + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>: Aids in converting to pkgsrc.</p></li> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/gensolpkg/README.html" target="_top"><code xmlns="" class="filename">pkgtools/gensolpkg</code></a>: Convert +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/gensolpkg/README.html" target="_top"><code class="filename">pkgtools/gensolpkg</code></a>: Convert pkgsrc to a Solaris package.</p></li> </ul></div> <p>Utilities for people maintaining pkgsrc (or: more obscure pkg utilities)</p> <div class="itemizedlist"><ul type="disc"> -<li><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_comp/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_comp</code></a>: Build +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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><p><a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/libkver/README.html" target="_top"><code xmlns="" class="filename">pkgtools/libkver</code></a>: Spoof +<li><p><a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/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> @@ -2646,7 +2657,7 @@ them by setting <code class="varname">UNPRIVILEGED_USER</code> and <p>As regards bootstrapping, please note that the <span><strong class="command">bootstrap</strong></span> script will ease non-root configuration when given the “<span class="quote">--ignore-user-check</span>” flag, as it will choose and -use multiple default directories under <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">~/pkg</code> as the +use multiple default directories under <code class="filename">~/pkg</code> as the installation targets. These directories can be overriden by the “<span class="quote">--prefix</span>” flag provided by the script, as well as some others that allow finer tuning of the tree layout.</p> @@ -2657,7 +2668,7 @@ that allow finer tuning of the tree layout.</p> <p>By default, resuming transfers in pkgsrc is disabled, but you can enable this feature by adding the option <code class="varname">PKG_RESUME_TRANSFERS=YES</code> into -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. If, during a fetch step, an incomplete +<code class="filename">/etc/mk.conf</code>. If, during a fetch step, an incomplete distfile is found, pkgsrc will try to resume it.</p> <p>You can also use a different program than the default <a href="http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> by changing the @@ -2666,7 +2677,7 @@ use a different program than the default <a href="http://netbsd.gw.com/cgi-bin/m <code class="varname">FETCH_OUTPUT_ARGS</code> if you are not using default values.</p> <p>For example, if you want to use -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">wget</code> to resume downloads, you'll have to use something +<code class="filename">wget</code> to resume downloads, you'll have to use something like:</p> <pre class="programlisting"> FETCH_CMD= wget @@ -2679,9 +2690,9 @@ like:</p> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="XFree86-from-pkgsrc"></a>7.6. How can I install/use XFree86 from pkgsrc?</h2></div></div></div> <p>If you want to use XFree86 from pkgsrc instead of your system's own -X11 (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/X11R6</code>, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/openwin</code>, +X11 (<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...), you will have to add the following line into -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>:</p> +<code class="filename">/etc/mk.conf</code>:</p> <pre class="programlisting"> X11_TYPE=XFree86 </pre> @@ -2690,9 +2701,9 @@ X11 (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/us <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="x.org-from-pkgsrc"></a>7.7. How can I install/use X.org from pkgsrc?</h2></div></div></div> <p>If you want to use X.org from pkgsrc instead of your system's own X11 -(<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/X11R6</code>, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/openwin</code>, ...) +(<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...) you will have to add the following line into -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>:</p> +<code class="filename">/etc/mk.conf</code>:</p> <pre class="programlisting"> X11_TYPE=xorg </pre> @@ -2722,20 +2733,20 @@ are:</p> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="passive-ftp"></a>7.9. How do I tell <span><strong class="command">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 xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned +<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 type="disc"> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${LOCALBASE}/bin/ftp</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/bin/ftp</code></p></li> +<li><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li> +<li><p><code class="filename">/usr/bin/ftp</code></p></li> </ul></div> <p>On a default NetBSD installation, this will be -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/bin/ftp</code>, which automatically tries passive +<code class="filename">/usr/bin/ftp</code>, which automatically tries passive connections first, and falls back to active connections if the server refuses to do passive. For the other tools, add the following to your -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> file: +<code class="filename">/etc/mk.conf</code> file: <code class="varname">PASSIVE_FETCH=1</code>.</p> <p>Having that option present will prevent -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/bin/ftp</code> from falling back to active +<code class="filename">/usr/bin/ftp</code> from falling back to active transfers.</p> </div> <div class="sect1" lang="en"> @@ -2746,7 +2757,7 @@ work or university, where you can't run a <span><strong class="command">make fet There is an archive of distfiles on <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/" target="_top">ftp.NetBSD.org</a>, but downloading the entire directory may not be appropriate.</p> <p>The answer here is to do a <span><strong class="command">make fetch-list</strong></span> in -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the +<code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the resulting list to your machine at work/school and use it there. If you don't have a NetBSD-compatible <a href="http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't forget to set <code class="varname">FETCH_CMD</code> to something that fetches a @@ -2757,7 +2768,7 @@ URL:</p> <code class="prompt">%</code> <strong class="userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong></pre> <p>At work:</p> <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>sh /tmp/fetch.sh</code></strong></pre> -<p>then tar up <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/tmp/distfiles</code> and take it +<p>then tar up <code class="filename">/tmp/distfiles</code> and take it home.</p> <p>If you have a machine running NetBSD, and you want to get <span class="emphasis"><em>all</em></span> distfiles (even ones that aren't for your machine @@ -2774,25 +2785,25 @@ by running:</p> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="tmac.andoc-missing"></a>7.11. What does “<span class="quote">Don't know how to make /usr/share/tmac/tmac.andoc</span>” mean?</h2></div></div></div> -<p>When compiling the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_install</code></a> +<p>When compiling the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you get the error from make that it doesn't know how to make -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that +<code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that you don't have installed the “<span class="quote">text</span>” set (nroff, ...) from the NetBSD base distribution on your machine. It is recommended to do that to format man pages.</p> -<p>In the case of the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_install</code></a> package, you +<p>In the case of the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you can get away with setting <code class="varname">NOMAN=YES</code> either in the -environment or in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>.</p> +environment or in <code class="filename">/etc/mk.conf</code>.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="bsd.own.mk-missing"></a>7.12. What does “<span class="quote">Could not find bsd.own.mk</span>” mean?</h2></div></div></div> -<p> You didn't install the compiler set, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">comp.tgz</code>, +<p> You didn't install the compiler set, <code class="filename">comp.tgz</code>, when you installed your NetBSD machine. Please get and install it, by -extracting it in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/</code>:</p> +extracting it in <code class="filename">/</code>:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong></pre> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">comp.tgz</code> is part of every NetBSD release. Get +<p><code class="filename">comp.tgz</code> is part of every NetBSD release. Get the one that corresponds to your release (determine via <span><strong class="command">uname -r</strong></span>).</p> </div> @@ -2804,8 +2815,8 @@ the one that corresponds to your release (determine via <span><strong class="com password for each required package installed. To avoid this, the sudo package can be used, which does password caching over a limited time. To use it, install sudo (either as binary package or from -<a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/sudo/README.html" target="_top"><code xmlns="" class="filename">security/sudo</code></a>) and then put the following -into your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>:</p> +<a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/sudo/README.html" target="_top"><code class="filename">security/sudo</code></a>) and then put the following +into your <code class="filename">/etc/mk.conf</code>:</p> <pre class="programlisting"> .if exists(${LOCALBASE}/bin/sudo) SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c @@ -2817,15 +2828,15 @@ into your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename <a name="faq.conf"></a>7.14. How do I change the location of configuration files?</h2></div></div></div> <p>As the system administrator, you can choose where configuration files are installed. The default settings make all these files go into -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may +<code class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may be suboptimal depending on your expectations (e.g., a read-only, NFS-exported <code class="varname">PREFIX</code> with a need of per-machine configuration of the provided packages).</p> <p>In order to change the defaults, you can modify the <code class="varname">PKG_SYSCONFBASE</code> variable (in -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>) to point to your preferred configuration -directory; some common examples include <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc</code> or -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/pkg</code>.</p> +<code class="filename">/etc/mk.conf</code>) to point to your preferred configuration +directory; some common examples include <code class="filename">/etc</code> or +<code class="filename">/etc/pkg</code>.</p> <p>Furthermore, you can change this value on a per-package basis by setting the <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> variable. <code class="varname">PKG_SYSCONFVAR</code>'s value usually matches the name of the @@ -2843,7 +2854,7 @@ attackers. In an effort to lessen the exposure, the NetBSD packages team maintains a database of known-exploits to packages which have at one time been included in pkgsrc. The database can be downloaded automatically, and a security audit of all packages installed on a system can take place. To -do this, install the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code xmlns="" class="filename">security/audit-packages</code></a> package. It has two +do this, install the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code class="filename">security/audit-packages</code></a> package. It has two components:</p> <div class="orderedlist"><ol type="1"> <li> @@ -2859,7 +2870,7 @@ components:</p> including a description of the type of vulnerability, and a URL containing more information.</p></li> </ol></div> -<p>Use of the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code xmlns="" class="filename">security/audit-packages</code></a> +<p>Use of the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/security/audit-packages/README.html" target="_top"><code class="filename">security/audit-packages</code></a> package is strongly recommended! After “<span class="quote">audit-packages</span>” is installed, please read the package's message, which you can get by running <strong class="userinput"><code>pkg_info -D @@ -2874,17 +2885,17 @@ a security check before building any package. See <a name="ufaq-cflags"></a>7.16. Why do some packages ignore my <code class="varname">CFLAGS</code>?</h2></div></div></div> <p>When you add your own preferences to the <code class="varname">CFLAGS</code> variable in your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk.conf</code>, these flags are passed in - environment variables to the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">./configure</code> + <code class="filename">mk.conf</code>, these flags are passed in + environment variables to the <code class="filename">./configure</code> scripts and to <a href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>. Some package authors ignore the <code class="varname">CFLAGS</code> from the environment variable by - overriding them in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s of their + overriding them in the <code class="filename">Makefile</code>s of their package.</p> <p>Currently there is no solution to this problem. If you really need the package to use your <code class="varname">CFLAGS</code> you should run <span><strong class="command">make patch</strong></span> in the package - directory and then inspect any <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile.in</code> for whether they define + directory and then inspect any <code class="filename">Makefile</code> and + <code class="filename">Makefile.in</code> for whether they define <code class="varname">CFLAGS</code> explicitly. Usually you can remove these lines. But be aware that some “<span class="quote">smart</span>” programmers write so bad code that it only works for the @@ -2901,17 +2912,17 @@ a security check before building any package. See <dl> <dt><span class="chapter"><a href="#components">8. Package components - files, directories and contents</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="#components.Makefile">8.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code></a></span></dt> -<dt><span class="sect1"><a href="#components.distinfo">8.2. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code></a></span></dt> +<dt><span class="sect1"><a href="#components.Makefile">8.1. <code class="filename">Makefile</code></a></span></dt> +<dt><span class="sect1"><a href="#components.distinfo">8.2. <code class="filename">distinfo</code></a></span></dt> <dt><span class="sect1"><a href="#components.patches">8.3. patches/*</a></span></dt> <dt><span class="sect1"><a href="#other-mandatory-files">8.4. Other mandatory files</a></span></dt> <dt><span class="sect1"><a href="#components.optional">8.5. Optional files</a></span></dt> -<dt><span class="sect1"><a href="#work-dir">8.6. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work*</code></a></span></dt> -<dt><span class="sect1"><a href="#files-dir">8.7. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">files/*</code></a></span></dt> +<dt><span class="sect1"><a href="#work-dir">8.6. <code class="filename">work*</code></a></span></dt> +<dt><span class="sect1"><a href="#files-dir">8.7. <code class="filename">files/*</code></a></span></dt> </dl></dd> -<dt><span class="chapter"><a href="#makefile">9. Programming in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s</a></span></dt> +<dt><span class="chapter"><a href="#makefile">9. Programming in <code class="filename">Makefile</code>s</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="#makefile.variables">9.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> variables</a></span></dt> +<dt><span class="sect1"><a href="#makefile.variables">9.1. <code class="filename">Makefile</code> variables</a></span></dt> <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">9.1.1. Naming conventions</a></span></dt></dl></dd> <dt><span class="sect1"><a href="#makefile.code">9.2. Code snippets</a></span></dt> <dd><dl> @@ -2925,7 +2936,7 @@ a security check before building any package. See <dt><span class="chapter"><a href="#plist">10. PLIST issues</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#rcs-id">10.1. RCS ID</a></span></dt> -<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> generation</a></span></dt> +<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt> <dt><span class="sect1"><a href="#print-PLIST">10.3. Tweaking output of <span><strong class="command">make print-PLIST</strong></span></a></span></dt> <dt><span class="sect1"><a href="#plist.misc">10.4. Variable substitution in PLIST</a></span></dt> <dt><span class="sect1"><a href="#manpage-compression">10.5. Man page compression</a></span></dt> @@ -2936,14 +2947,14 @@ a security check before building any package. See <dt><span class="chapter"><a href="#buildlink">11. Buildlink methodology</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#converting-to-buildlink3">11.1. Converting packages to use buildlink3</a></span></dt> -<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="#anatomy-of-bl3">11.2.1. Anatomy of a buildlink3.mk file</a></span></dt> -<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code class="filename">buildlink3.mk</code> files</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file</a></span></dt> +<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt> <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">11.3.2. Global preferences for native or pkgsrc software</a></span></dt> </dl></dd> </dl></dd> @@ -2972,7 +2983,7 @@ a security check before building any package. See <dt><span class="chapter"><a href="#options">13. Options handling</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="#global-default-options">13.1. Global default options</a></span></dt> -<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code></a></span></dt> +<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt> <dt><span class="sect1"><a href="#option-names">13.3. Option Names</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="#build">14. The build process</a></span></dt> @@ -3074,13 +3085,13 @@ a security check before building any package. See <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="#components.Makefile">8.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code></a></span></dt> -<dt><span class="sect1"><a href="#components.distinfo">8.2. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code></a></span></dt> +<dt><span class="sect1"><a href="#components.Makefile">8.1. <code class="filename">Makefile</code></a></span></dt> +<dt><span class="sect1"><a href="#components.distinfo">8.2. <code class="filename">distinfo</code></a></span></dt> <dt><span class="sect1"><a href="#components.patches">8.3. patches/*</a></span></dt> <dt><span class="sect1"><a href="#other-mandatory-files">8.4. Other mandatory files</a></span></dt> <dt><span class="sect1"><a href="#components.optional">8.5. Optional files</a></span></dt> -<dt><span class="sect1"><a href="#work-dir">8.6. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work*</code></a></span></dt> -<dt><span class="sect1"><a href="#files-dir">8.7. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">files/*</code></a></span></dt> +<dt><span class="sect1"><a href="#work-dir">8.6. <code class="filename">work*</code></a></span></dt> +<dt><span class="sect1"><a href="#files-dir">8.7. <code class="filename">files/*</code></a></span></dt> </dl> </div> <p> Whenever you're preparing a package, there are a number of @@ -3088,14 +3099,14 @@ a security check before building any package. See sections. </p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="components.Makefile"></a>8.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code></h2></div></div></div> +<a name="components.Makefile"></a>8.1. <code class="filename">Makefile</code></h2></div></div></div> <p>Building, installation and creation of a binary package are all - controlled by the package's <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>. - The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> describes various things about + controlled by the package's <code class="filename">Makefile</code>. + The <code class="filename">Makefile</code> describes various things about a package, for example from where to get it, how to configure, build, and install it. </p> -<p>A package <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> contains several +<p>A package <code class="filename">Makefile</code> contains several sections that describe the package.</p> <p>In the first section there are the following variables, which should appear exactly in the order given here. @@ -3184,7 +3195,7 @@ a security check before building any package. See <li> <p><code class="varname">DISTFILES</code>: Name(s) of archive file(s) containing distribution. The default is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${DISTNAME}${EXTRACT_SUFX}</code>. Should only + <code class="filename">${DISTNAME}${EXTRACT_SUFX}</code>. Should only be set if you have more than one distfile.</p> <p>Note that the normal default setting of <code class="varname">DISTFILES</code> must be made explicit if you @@ -3194,7 +3205,7 @@ a security check before building any package. See <li><p><code class="varname">EXTRACT_SUFX</code>: Suffix of the distribution file, will be appended to <code class="varname">DISTNAME</code>. Defaults to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.tar.gz</code>. + <code class="filename">.tar.gz</code>. </p></li> </ul></div> <p> @@ -3208,8 +3219,8 @@ a security check before building any package. See There is no default. pkgsrc will look for them at <code class="varname">PATCH_SITES</code>. They will automatically be uncompressed before patching if - the names end with <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.gz</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.Z</code>.</p></li> + the names end with <code class="filename">.gz</code> or + <code class="filename">.Z</code>.</p></li> <li><p><code class="varname">PATCH_SITES</code>: Primary location(s) for distribution patch files (see <code class="varname">PATCHFILES</code> below) if not found locally.</p></li> @@ -3241,7 +3252,7 @@ a security check before building any package. See <div class="itemizedlist"><ul type="disc"><li> <p><code class="varname">WRKSRC</code>: The directory where the interesting distribution files of the package are found. The - default is <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKDIR}/${DISTNAME}</code>, which + default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which works for most packages.</p> <p>If a package doesn't create a subdirectory for itself (most GNU software does, for instance), but extracts itself in @@ -3250,21 +3261,21 @@ a security check before building any package. See <p>If a package doesn't create a subdirectory with the name of <code class="varname">DISTNAME</code> but some different name, set <code class="varname">WRKSRC</code> to point to the proper name in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKDIR}</code>, for example <code class="varname">WRKSRC= - ${WRKDIR}/${DISTNAME}/unix</code>. See <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/tcl/README.html" target="_top"><code xmlns="" class="filename">lang/tcl</code></a> and <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/tk/README.html" target="_top"><code xmlns="" class="filename">x11/tk</code></a> for other examples.</p> + <code class="filename">${WRKDIR}</code>, for example <code class="varname">WRKSRC= + ${WRKDIR}/${DISTNAME}/unix</code>. See <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/tcl/README.html" target="_top"><code class="filename">lang/tcl</code></a> and <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/tk/README.html" target="_top"><code class="filename">x11/tk</code></a> for other examples.</p> <p>The name of the working directory created by pkgsrc is taken from the <code class="varname">WRKDIR_BASENAME</code> variable. By - default, its value is <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work</code>. If you want + default, its value is <code class="filename">work</code>. If you want to use the same pkgsrc tree for building different kinds of binary packages, you can change the variable according to your needs. Two other variables handle common cases of setting <code class="varname">WRKDIR_BASENAME</code> individually. If <code class="varname">OBJHOSTNAME</code> is defined in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, the first component of the + <code class="filename">/etc/mk.conf</code>, the first component of the host's name is attached to the directory name. If <code class="varname">OBJMACHINE</code> is defined, the platform name is - attached, which might look like <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work.i386</code> - or <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work.sparc</code>.</p> + attached, which might look like <code class="filename">work.i386</code> + or <code class="filename">work.sparc</code>.</p> </li></ul></div> <p> </p> @@ -3272,8 +3283,8 @@ a security check before building any package. See <div class="itemizedlist"><ul type="disc"> <li><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are installed in compressed form by the package; see comment in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.pkg.mk</code>.</p></li> -<li><p>Replace <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/local</code> with + <code class="filename">bsd.pkg.mk</code>.</p></li> +<li><p>Replace <code class="filename">/usr/local</code> with “<span class="quote">${PREFIX}</span>” in all files (see patches, below).</p></li> <li><p>If the package installs any info files, see <a href="#faq.info-files" title="16.5.7. Packages installing info files">Section 16.5.7, “Packages installing info files”</a>.</p></li> @@ -3281,23 +3292,23 @@ a security check before building any package. See </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="components.distinfo"></a>8.2. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code></h2></div></div></div> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code> file contains the message +<a name="components.distinfo"></a>8.2. <code class="filename">distinfo</code></h2></div></div></div> +<p>The <code class="filename">distinfo</code> file contains the message digest, or checksum, of each distfile needed for the package. This ensures that the distfiles retrieved from the Internet have not been corrupted during transfer or altered by a malign force to introduce a security hole. Due to recent rumor about weaknesses of digest algorithms, all distfiles are protected using both SHA1 and RMD160 message digests, as well as the file size.</p> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code> file also contains the +<p>The <code class="filename">distinfo</code> file also contains the checksums for all the patches found in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">patches</code> directory (see <a href="#components.patches" title="8.3. patches/*">Section 8.3, “patches/*”</a>).</p> -<p>To regenerate the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code> file, use the + <code class="filename">patches</code> directory (see <a href="#components.patches" title="8.3. patches/*">Section 8.3, “patches/*”</a>).</p> +<p>To regenerate the <code class="filename">distinfo</code> file, use the <span><strong class="command">make makedistinfo</strong></span> or <span><strong class="command">make mdi</strong></span> command.</p> <p>Some packages have different sets of distfiles depending on - the platform, for example <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/navigator/README.html" target="_top"><code xmlns="" class="filename">www/navigator</code></a>). These are kept in the same - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code> file and care should be taken when + the platform, for example <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/navigator/README.html" target="_top"><code class="filename">www/navigator</code></a>). These are kept in the same + <code class="filename">distinfo</code> file and care should be taken when upgrading such a package to ensure distfile information is not lost.</p> </div> @@ -3310,9 +3321,9 @@ a security check before building any package. See that will compile and run perfectly on NetBSD. The files are applied successively in alphabetic order (as returned by a shell “<span class="quote">patches/patch-*</span>” glob expansion), so - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">patch-aa</code> is applied before - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">patch-ab</code>, etc.</p> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">patch-*</code> files should be in + <code class="filename">patch-aa</code> is applied before + <code class="filename">patch-ab</code>, etc.</p> +<p>The <code class="filename">patch-*</code> files should be in <span><strong class="command">diff -bu</strong></span> format, and apply without a fuzz to avoid problems. (To force patches to apply with fuzz you can set <code class="varname">PATCH_FUZZ_FACTOR=-F2</code>). @@ -3325,18 +3336,18 @@ a security check before building any package. See get stored in the patch files, as these will cause problems when later checked into the NetBSD CVS tree. Use the <span><strong class="command">pkgdiff</strong></span> from the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdiff</code></a> package to avoid + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package to avoid these problems.</p> <p>For even more automation, we recommend using <span><strong class="command">mkpatches</strong></span> from the same package to make a whole set of patches. You just have to backup files - before you edit them to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">filename.orig</code>, e.g. with + before you edit them to <code class="filename">filename.orig</code>, e.g. with <span><strong class="command">cp -p filename filename.orig</strong></span> or, easier, by using <span><strong class="command">pkgvi</strong></span> again from the same package. If you upgrade a package this way, you can easily compare the new set of patches with the previously existing one with <span><strong class="command">patchdiff</strong></span>.</p> <p>When you have finished a package, remember to generate the checksums for the patch files by using the <span><strong class="command">make makepatchsum</strong></span> - command, see <a href="#components.distinfo" title="8.2. distinfo">Section 8.2, “<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code>”</a>.</p> + command, see <a href="#components.distinfo" title="8.2. distinfo">Section 8.2, “<code class="filename">distinfo</code>”</a>.</p> <p>When adding a patch that corrects a problem in the distfile (rather than e.g. enforcing pkgsrc's view of where man pages should go), send the patch as a bug report to the maintainer. This benefits @@ -3347,14 +3358,14 @@ a security check before building any package. See <code class="varname">$PATCHFILES</code>. </p> <p>If it is desired to store any patches that should not be committed into pkgsrc, they can be kept outside the pkgsrc tree in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">$LOCALPATCHES</code> + <code class="filename">$LOCALPATCHES</code> directory. The directory tree there is expected to have the same “<span class="quote">category/package</span>” structure as pkgsrc, and patches are expected to be stored inside these dirs (also known as - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">$LOCALPATCHES/$PKGPATH</code>). For + <code class="filename">$LOCALPATCHES/$PKGPATH</code>). For example, if you want to keep a private patch for - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/graphics/png</code>, keep - it in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All + <code class="filename">pkgsrc/graphics/png</code>, keep + it in <code class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All files in the named directory are expected to be patch files, and <span class="emphasis"><em>they are applied after pkgsrc patches are applied</em></span>.</p> </div> @@ -3362,12 +3373,12 @@ a security check before building any package. See <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="other-mandatory-files"></a>8.4. Other mandatory files</h2></div></div></div> <div class="variablelist"><dl> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DESCR</code></span></dt> +<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 share your sense of humour (or spelling idiosyncrasies), and that others will read everything that you write here.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code></span></dt> +<dt><span class="term"><code class="filename">PLIST</code></span></dt> <dd><p> This file governs the files that are installed on your system: all the binaries, manual pages, etc. There are other directives which may be @@ -3380,22 +3391,22 @@ a security check before building any package. See <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="components.optional"></a>8.5. Optional files</h2></div></div></div> <div class="variablelist"><dl> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">INSTALL</code></span></dt> +<dt><span class="term"><code class="filename">INSTALL</code></span></dt> <dd><p>This shell script is invoked twice by <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. First time after package extraction and before files are moved in place, the second time after the files to install are moved in place. This can be used to do any custom procedures not possible with @exec commands in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>. See + <code class="filename">PLIST</code>. See <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> and <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DEINSTALL</code></span></dt> +<dt><span class="term"><code class="filename">DEINSTALL</code></span></dt> <dd><p>This script is executed before and after any files are removed. It is this script's responsibility to clean up any additional messy details around the package's installation, since all pkg_delete knows is how to delete the files created in the original distribution. See <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> and <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">MESSAGE</code></span></dt> +<dt><span class="term"><code class="filename">MESSAGE</code></span></dt> <dd> <p>This file is displayed after installation of the package. Useful for things like legal notices on almost-free @@ -3403,47 +3414,47 @@ a security check before building any package. See installing modules for apache, PHP etc. Please note that you can modify variables in it easily by using <code class="varname">MESSAGE_SUBST</code> in the package's - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>:</p> + <code class="filename">Makefile</code>:</p> <pre class="programlisting"> MESSAGE_SUBST+= SOMEVAR="somevalue" </pre> <p>replaces "${SOMEVAR}" with “<span class="quote">somevalue</span>” in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">MESSAGE</code>.</p> + <code class="filename">MESSAGE</code>.</p> </dd> </dl></div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="work-dir"></a>8.6. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">work*</code></h2></div></div></div> +<a name="work-dir"></a>8.6. <code class="filename">work*</code></h2></div></div></div> <p>When you type <span><strong class="command">make</strong></span>, the distribution files are unpacked into the directory denoted by <code class="varname">WRKDIR</code>. It can be removed by running <span><strong class="command">make clean</strong></span>. Besides the sources, this directory is also used to keep various timestamp files. The directory gets <span class="emphasis"><em>removed completely</em></span> on clean. - The default is <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${.CURDIR}/work</code> - or <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code> + The default is <code class="filename">${.CURDIR}/work</code> + or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code> if <code class="varname">OBJMACHINE</code> is set.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="files-dir"></a>8.7. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">files/*</code></h2></div></div></div> +<a name="files-dir"></a>8.7. <code class="filename">files/*</code></h2></div></div></div> <p>If you have any files that you wish to be placed in the package prior to configuration or building, you could place these files here and use a “<span class="quote">${CP}</span>” command in the “<span class="quote">pre-configure</span>” target to achieve this. Alternatively, you could simply diff the file against - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/dev/null</code> and use the patch mechanism to manage + <code class="filename">/dev/null</code> and use the patch mechanism to manage the creation of this file.</p> </div> </div> <div class="chapter" lang="en"> <div class="titlepage"><div><div><h2 class="title"> -<a name="makefile"></a>Chapter 9. Programming in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s</h2></div></div></div> +<a name="makefile"></a>Chapter 9. Programming in <code class="filename">Makefile</code>s</h2></div></div></div> <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="#makefile.variables">9.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> variables</a></span></dt> +<dt><span class="sect1"><a href="#makefile.variables">9.1. <code class="filename">Makefile</code> variables</a></span></dt> <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">9.1.1. Naming conventions</a></span></dt></dl></dd> <dt><span class="sect1"><a href="#makefile.code">9.2. Code snippets</a></span></dt> <dd><dl> @@ -3455,29 +3466,29 @@ a security check before building any package. See </dl></dd> </dl> </div> -<p>Pkgsrc consists of many <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> fragments, +<p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments, each of which forms a well-defined part of the pkgsrc system. Using the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a programming language for a big system like pkgsrc requires some discipline to keep the code correct and understandable.</p> -<p>The basic ingredients for <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> +<p>The basic ingredients for <code class="filename">Makefile</code> programming are variables (which are actually macros) and shell commands. Among these shell commands may even be more complex ones like <a href="http://netbsd.gw.com/cgi-bin/man-cgi?awk+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make sure that every shell command runs as intended it is necessary to quote all variables correctly when they are used.</p> <p>This chapter describes some patterns, that appear quite often in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s, including the pitfalls that come along + <code class="filename">Makefile</code>s, including the pitfalls that come along with them.</p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="makefile.variables"></a>9.1. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> variables</h2></div></div></div> -<p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> variables contain strings that +<a name="makefile.variables"></a>9.1. <code class="filename">Makefile</code> variables</h2></div></div></div> +<p><code class="filename">Makefile</code> variables contain strings that can be processed using the five operators ``='', ``+='', ``?='', ``:='', and ``!='', which are described in the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page.</p> <p>When a variable's value is parsed from a - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, the hash character ``#'' and the + <code class="filename">Makefile</code>, the hash character ``#'' and the backslash character ``\'' are handled specially. If a backslash is followed by a newline, any whitespace immediately in front of the backslash, the backslash, the newline, and any whitespace @@ -3534,7 +3545,7 @@ a security check before building any package. See <li><p>All variable names starting with an underscore are reserved for use by the pkgsrc infrastructure. They shall not be used by package - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s.</p></li> + <code class="filename">Makefile</code>s.</p></li> <li><p>In <span><strong class="command">.for</strong></span> loops you should use lowercase variable names for the iteration variables.</p></li> @@ -3717,7 +3728,7 @@ a security check before building any package. See VAR:= ${VAR:N${_othervar_:C/-//}} </pre> <p>For a more complex code snippet and a workaround, see the - package <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/regress/make-quoting/README.html" target="_top"><code xmlns="" class="filename">regress/make-quoting</code></a>, testcase + package <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/regress/make-quoting/README.html" target="_top"><code class="filename">regress/make-quoting</code></a>, testcase <code class="varname">bug1</code>.</p> </div> </div> @@ -3729,7 +3740,7 @@ a security check before building any package. See <p><b>Table of Contents</b></p> <dl> <dt><span class="sect1"><a href="#rcs-id">10.1. RCS ID</a></span></dt> -<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> generation</a></span></dt> +<dt><span class="sect1"><a href="#automatic-plist-generation">10.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt> <dt><span class="sect1"><a href="#print-PLIST">10.3. Tweaking output of <span><strong class="command">make print-PLIST</strong></span></a></span></dt> <dt><span class="sect1"><a href="#plist.misc">10.4. Variable substitution in PLIST</a></span></dt> <dt><span class="sect1"><a href="#manpage-compression">10.5. Man page compression</a></span></dt> @@ -3738,20 +3749,20 @@ a security check before building any package. See <dt><span class="sect1"><a href="#faq.common-dirs">10.8. Sharing directories between packages</a></span></dt> </dl> </div> -<p> The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file contains a package's +<p> The <code class="filename">PLIST</code> file contains a package's “<span class="quote">packing list</span>”, i.e. a list of files that belong to - the package (relative to the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}</code> + the package (relative to the <code class="filename">${PREFIX}</code> directory it's been installed in) plus some additional statements - see the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> man page for a full list. This chapter addresses some issues that need attention when - dealing with the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file (or files, see + dealing with the <code class="filename">PLIST</code> file (or files, see below!).</p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="rcs-id"></a>10.1. RCS ID</h2></div></div></div> <p> Be sure to add a RCS ID line as the first thing in any - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file you write: + <code class="filename">PLIST</code> file you write: </p> <pre class="programlisting"> @comment $NetBSD$ @@ -3759,7 +3770,7 @@ a security check before building any package. See </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="automatic-plist-generation"></a>10.2. Semi-automatic <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> generation</h2></div></div></div> +<a name="automatic-plist-generation"></a>10.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div> <p>You can use the <span><strong class="command">make print-PLIST</strong></span> command to output a PLIST that matches any new files since the package was extracted. See <a href="#build.helpful-targets" title="14.16. Other helpful targets">Section 14.16, “Other helpful targets”</a> for @@ -3781,7 +3792,7 @@ a security check before building any package. See print-PLIST. You can <span class="emphasis"><em>append</em></span> any chunk of AWK scripting you like to it, but be careful with quoting. </p> <p> For example, to get all files inside the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libdata/foo</code> directory removed from the + <code class="filename">libdata/foo</code> directory removed from the resulting PLIST:</p> <pre class="programlisting"> PRINT_PLIST_AWK+= /^libdata\/foo/ { next; } @@ -3827,7 +3838,7 @@ a security check before building any package. See <dd> <p>Some packages want to embed the OS name and version into some paths. To do this, use these variables in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>: + <code class="filename">PLIST</code>: </p> <div class="itemizedlist"><ul type="disc"> <li><p><code class="varname">${OPSYS}</code> - output of “<span class="quote"><span><strong class="command">uname -s</strong></span></span>”</p></li> @@ -3837,7 +3848,7 @@ a security check before building any package. See </dd> </dl></div> <p> For a complete list of values which are replaced by - default, please look in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.pkg.mk</code> (and + default, please look in <code class="filename">bsd.pkg.mk</code> (and search for <span class="emphasis"><em>PLIST_SUBST</em></span>). </p> <p> If you want to change other variables not listed above, you can add variables and their expansions to this variable in the @@ -3852,19 +3863,19 @@ a security check before building any package. See <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="manpage-compression"></a>10.5. Man page compression</h2></div></div></div> <p>Man pages should be installed in compressed form if - <code class="varname">MANZ</code> is set (in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.own.mk</code>), + <code class="varname">MANZ</code> is set (in <code class="filename">bsd.own.mk</code>), and uncompressed otherwise. To handle this in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file, the suffix “<span class="quote">.gz</span>” is + <code class="filename">PLIST</code> file, the suffix “<span class="quote">.gz</span>” is appended/removed automatically for man pages according to <code class="varname">MANZ</code> and <code class="varname">MANCOMPRESSED</code> being set or not, see above for details. This modification of the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file is done on a copy of it, not - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> itself.</p> + <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" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="using-PLIST_SRC"></a>10.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></h2></div></div></div> -<p>To use one or more files as source for the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> used +<p>To use one or more files as source for the <code class="filename">PLIST</code> used in generating the binary package, set the variable <code class="varname">PLIST_SRC</code> to the names of that file(s). The files are later concatenated using <a href="http://netbsd.gw.com/cgi-bin/man-cgi?cat+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">cat</span>(1)</span></a>, and order of things is @@ -3877,11 +3888,11 @@ a security check before building any package. See the operating system being used. These differences can be automatically handled by using the following files:</p> <div class="itemizedlist"><ul type="disc"> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST.common</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST.${OPSYS}</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST.${MACHINE_ARCH}</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST.common_end</code></p></li> +<li><p><code class="filename">PLIST.common</code></p></li> +<li><p><code class="filename">PLIST.${OPSYS}</code></p></li> +<li><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li> +<li><p><code class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li> +<li><p><code class="filename">PLIST.common_end</code></p></li> </ul></div> </div> <div class="sect1" lang="en"> @@ -3906,9 +3917,9 @@ a security check before building any package. See <div class="orderedlist"><ol type="1"> <li><p> If the packages have a common dependency, the directory can be removed in that. For example, see - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/textproc/scrollkeeper/README.html" target="_top"><code xmlns="" class="filename">textproc/scrollkeeper</code></a>, which + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/textproc/scrollkeeper/README.html" target="_top"><code class="filename">textproc/scrollkeeper</code></a>, which removes the shared directory - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/omf</code>. </p></li> + <code class="filename">share/omf</code>. </p></li> <li><p> If the packages using the directory are not related at all (they have no common dependencies), a *-dirs package is used. </p></li> @@ -3925,7 +3936,7 @@ a security check before building any package. See version number (always pick the latest one when writing new packages). </p> <p> For example, if a package installs files under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/applications</code>, it should have the + <code class="filename">share/applications</code>, it should have the following line in it: </p> <pre class="programlisting"> @@ -3935,9 +3946,9 @@ a security check before building any package. See print-PLIST</strong></span>, you should get the right (commented out) lines. </p> <p> Note that even if your package is using - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">$X11BASE</code>, it must not depend on the + <code class="filename">$X11BASE</code>, it must not depend on the *-x11-dirs packages. Just specify the name without that part and - pkgsrc (in particular, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/dirs.mk</code>) will take + pkgsrc (in particular, <code class="filename">mk/dirs.mk</code>) will take care of it. </p> </div> </div> @@ -3948,14 +3959,14 @@ a security check before building any package. See <p><b>Table of Contents</b></p> <dl> <dt><span class="sect1"><a href="#converting-to-buildlink3">11.1. Converting packages to use buildlink3</a></span></dt> -<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#creating-buildlink3.mk">11.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="#anatomy-of-bl3">11.2.1. Anatomy of a buildlink3.mk file</a></span></dt> -<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</a></span></dt> +<dt><span class="sect2"><a href="#updating-buildlink-depends">11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code class="filename">buildlink3.mk</code> files</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> files</a></span></dt> +<dt><span class="sect1"><a href="#writing-builtin.mk">11.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file</a></span></dt> +<dt><span class="sect2"><a href="#anatomy-of-builtin.mk">11.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt> <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">11.3.2. Global preferences for native or pkgsrc software</a></span></dt> </dl></dd> </dl> @@ -3978,8 +3989,8 @@ a security check before building any package. See <p>This normalizes the environment in which a package is built so that the package may be built consistently despite what other software may be installed. Please note that the normal system header and library paths, - e.g. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/include</code>, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is + e.g. <code class="filename">/usr/include</code>, + <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" lang="en"> @@ -3992,16 +4003,16 @@ a security check before building any package. See <li><p> Ensure that the build always calls the wrapper scripts instead of the actual toolchain. Some packages are tricky, and the only way to know for sure is the check - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKDIR}/.work.log</code> to see if the + <code class="filename">${WRKDIR}/.work.log</code> to see if the wrappers are being invoked. </p></li> <li><p> Don't override <code class="varname">PREFIX</code> from within the package Makefile, e.g. Java VMs, standalone shells, etc., because the code to symlink files into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code> looks for files + <code class="filename">${BUILDLINK_DIR}</code> looks for files relative to “<span class="quote">pkg_info -qp <em class="replaceable"><code>pkgname</code></em></span>”. </p></li> <li><p> Remember that <span class="emphasis"><em>only</em></span> the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files that you list in a + <code class="filename">buildlink3.mk</code> files that you list in a package's Makefile are added as dependencies for that package. </p></li> </ol></div> @@ -4022,66 +4033,66 @@ a security check before building any package. See BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0 .include "../../category/foo/buildlink3.mk" </pre> -<p>There are several <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> - files in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk</code> +<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 type="disc"> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bdb.buildlink3.mk</code> chooses either +<li><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 <code class="varname">BDB_DEFAULT</code>.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">curses.buildlink3.mk</code>: If the system +<li><p><code class="filename">curses.buildlink3.mk</code>: If the system comes with neither Curses nor NCurses, this will take care - to install the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/ncurses/README.html" target="_top"><code xmlns="" class="filename">devel/ncurses</code></a> package.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">krb5.buildlink3.mk</code> uses the value + to install the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/ncurses/README.html" target="_top"><code class="filename">devel/ncurses</code></a> package.</p></li> +<li><p><code class="filename">krb5.buildlink3.mk</code> uses the value of <code class="varname">KRB5_ACCEPTED</code> to choose between adding a dependency on Heimdal or MIT-krb5 for packages that require a Kerberos 5 implementation.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">motif.buildlink3.mk</code> checks +<li><p><code class="filename">motif.buildlink3.mk</code> checks for a system-provided - Motif installation or adds a dependency on <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/lesstif/README.html" target="_top"><code xmlns="" class="filename">x11/lesstif</code></a> or - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/openmotif/README.html" target="_top"><code xmlns="" class="filename">x11/openmotif</code></a>.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">oss.buildlink3.mk</code> defines several + Motif installation or adds a dependency on <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/lesstif/README.html" target="_top"><code class="filename">x11/lesstif</code></a> or + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/openmotif/README.html" target="_top"><code class="filename">x11/openmotif</code></a>.</p></li> +<li><p><code class="filename">oss.buildlink3.mk</code> defines several variables that may be used by packages that use the Open Sound System (OSS) API.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pgsql.buildlink3.mk</code> will accept +<li><p><code class="filename">pgsql.buildlink3.mk</code> will accept either Postgres 7.3 or 7.4, whichever is found installed. See the file for more information. </p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pthread.buildlink3.mk</code> uses the value of +<li><p><code class="filename">pthread.buildlink3.mk</code> uses the value of <code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds - a dependency on <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/pth/README.html" target="_top"><code xmlns="" class="filename">devel/pth</code></a> as needed.</p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">xaw.buildlink3.mk</code> uses the value of + a dependency on <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/pth/README.html" target="_top"><code class="filename">devel/pth</code></a> as needed.</p></li> +<li><p><code class="filename">xaw.buildlink3.mk</code> uses the value of <code class="varname">XAW_TYPE</code> to choose a particular Athena widgets library.</p></li> </ul></div> -<p>The comments in those <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> +<p>The comments in those <code class="filename">buildlink3.mk</code> files provide a more complete description of how to use them properly.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="creating-buildlink3.mk"></a>11.2. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</h2></div></div></div> -<p> A package's <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file is +<a name="creating-buildlink3.mk"></a>11.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div> +<p> A package's <code class="filename">buildlink3.mk</code> file is included by Makefiles to indicate the need to compile and link against header files and libraries provided by the package. A - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file should always provide + <code class="filename">buildlink3.mk</code> file should always provide enough information to add the correct type of dependency relationship and include any other - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files that it needs to find + <code class="filename">buildlink3.mk</code> files that it needs to find headers and libraries that it needs in turn.</p> -<p> To generate an initial <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> - file for further editing, Rene Hexel's <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/createbuildlink/README.html" target="_top"><code xmlns="" class="filename">pkgtools/createbuildlink</code></a> +<p> To generate an initial <code class="filename">buildlink3.mk</code> + file for further editing, Rene Hexel's <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/createbuildlink/README.html" target="_top"><code class="filename">pkgtools/createbuildlink</code></a> package is highly recommended. For most packages, the following command will generate a good starting point for - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files:</p> + <code class="filename">buildlink3.mk</code> files:</p> <pre class="screen"><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" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="anatomy-of-bl3"></a>11.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div> <p>The following real-life example - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> is taken - from <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/graphics/tiff</code>:</p> + <code class="filename">buildlink3.mk</code> is taken + from <code class="filename">pkgsrc/graphics/tiff</code>:</p> <pre class="programlisting"> # $NetBSD: buildlink3.mk,v 1.7 2004/03/18 09:12:12 jlam Exp $ @@ -4107,21 +4118,21 @@ a security check before building any package. See </pre> <p> The header and footer manipulate <code class="varname">BUILDLINK_DEPTH</code>, which is common across all - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files and is used to track + <code class="filename">buildlink3.mk</code> files and is used to track at what depth we are including - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files.</p> + <code class="filename">buildlink3.mk</code> files.</p> <p> The first section controls if the dependency on <em class="replaceable"><code>pkg</code></em> is added. <code class="varname">BUILDLINK_DEPENDS</code> is the global list of packages for which dependencies are added by buildlink3.</p> <p> The second section advises pkgsrc that the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file for + <code class="filename">buildlink3.mk</code> file for <em class="replaceable"><code>pkg</code></em> has been included at some point. <code class="varname">BUILDLINK_PACKAGES</code> is the global list of - packages for which <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files + packages for which <code class="filename">buildlink3.mk</code> files have been included. It must <span class="emphasis"><em>always</em></span> be - appended to within a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> + appended to within a <code class="filename">buildlink3.mk</code> file. </p> <p> The third section is protected from multiple inclusion and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is @@ -4155,7 +4166,7 @@ a security check before building any package. See and <code class="varname">BUILDLINK_LIBDIRS.<em class="replaceable"><code>pkg</code></em></code> (not shown above) are lists of subdirectories of - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> + <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> to add to the header and library search paths. These default to “<span class="quote">include</span>” and “<span class="quote">lib</span>” respectively. </p></li> @@ -4171,40 +4182,40 @@ a security check before building any package. See <p> The following variables are all optionally defined within this second section (protected against multiple inclusion) and control which package files are symlinked into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code> and how their names are + <code class="filename">${BUILDLINK_DIR}</code> and how their names are transformed during the symlinking: </p> <div class="itemizedlist"><ul type="disc"> <li><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 xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> + <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> to be symlinked into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code>, - e.g. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">include/*.h</code>. </p></li> + <code class="filename">${BUILDLINK_DIR}</code>, + e.g. <code class="filename">include/*.h</code>. </p></li> <li><p> <code class="varname">BUILDLINK_FILES_CMD.<em class="replaceable"><code>pkg</code></em></code> (not shown above) is a shell pipeline that outputs to stdout a list of files relative to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>. + <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>. The resulting files are to be symlinked - into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code>. By default, - this takes the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">+CONTENTS</code> of a + into <code class="filename">${BUILDLINK_DIR}</code>. By default, + this takes the <code class="filename">+CONTENTS</code> of a <em class="replaceable"><code>pkg</code></em> and filters it through <code class="varname">${BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em>}</code>. </p></li> <li><p> <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code> (not shown above) is a filter command that filters - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">+CONTENTS</code> input into a list of files + <code class="filename">+CONTENTS</code> input into a list of files relative to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> + <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code> on stdout. By default for overwrite packages, <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code> - outputs the contents of the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">include</code> - and <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">lib</code> directories in the package - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">+CONTENTS</code>, and for pkgviews packages, + outputs the contents of the <code class="filename">include</code> + and <code class="filename">lib</code> directories in the package + <code class="filename">+CONTENTS</code>, and for pkgviews packages, it outputs any libtool archives in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">lib</code> directories. + <code class="filename">lib</code> directories. </p></li> <li><p> <code class="varname">BUILDLINK_TRANSFORM.<em class="replaceable"><code>pkg</code></em></code> @@ -4215,20 +4226,20 @@ a security check before building any package. See </p></li> </ul></div> <p> The last section includes any - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> needed for + <code class="filename">buildlink3.mk</code> needed for <em class="replaceable"><code>pkg</code></em>'s library dependencies. - Including these <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files + Including these <code class="filename">buildlink3.mk</code> files means that the headers and libraries for these dependencies are also symlinked into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code> + <code class="filename">${BUILDLINK_DIR}</code> whenever the <em class="replaceable"><code>pkg</code></em> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> + <code class="filename">buildlink3.mk</code> file is included. </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="updating-buildlink-depends"></a>11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files</h3></div></div></div> +<a name="updating-buildlink-depends"></a>11.2.2. Updating <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> in <code class="filename">buildlink3.mk</code> files</h3></div></div></div> <p> The situation that requires increasing the dependency listed in <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> @@ -4239,7 +4250,7 @@ a security check before building any package. See should be adjusted to require at least the new package version. In some cases, the packages that depend on this new version may need their <code class="varname">PKGREVISION</code>s - increased and, if they have <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> + increased and, if they have <code class="filename">buildlink3.mk</code> files, their <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code> adjusted, too. This is needed so pkgsrc will require the @@ -4274,12 +4285,12 @@ a security check before building any package. See </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="writing-builtin.mk"></a>11.3. Writing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> files</h2></div></div></div> +<a name="writing-builtin.mk"></a>11.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div> <p> Some packages in pkgsrc install headers and libraries that coincide with headers and libraries present in the base system. - Aside from a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file, these - packages should also include a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> + Aside from a <code class="filename">buildlink3.mk</code> file, these + packages should also include a <code class="filename">builtin.mk</code> file that includes the necessary checks to decide whether using the built-in software or the pkgsrc software is appropriate. </p> @@ -4295,16 +4306,16 @@ a security check before building any package. See <li><p> It should <span class="emphasis"><em>not</em></span> override any <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> which is already set before the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file is included. + <code class="filename">builtin.mk</code> file is included. </p></li> <li><p> It should be written to allow multiple inclusion. This is <span class="emphasis"><em>very</em></span> important and takes careful - attention to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> coding. + attention to <code class="filename">Makefile</code> coding. </p></li> </ol></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="anatomy-of-builtin.mk"></a>11.3.1. Anatomy of a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file</h3></div></div></div> +<a name="anatomy-of-builtin.mk"></a>11.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 files: </p> <pre class="programlisting"> @@ -4354,7 +4365,7 @@ a security check before building any package. See with similar functionality to <em class="replaceable"><code>pkg</code></em>; it should only be “<span class="quote">yes</span>” if the actual package is included as part of the base system. This variable is only - used internally within the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> + used internally within the <code class="filename">builtin.mk</code> file. </p> <p> The second section sets <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code> @@ -4362,11 +4373,11 @@ a security check before building any package. See system if it exists (if <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> is “<span class="quote">yes</span>”). This variable is only used internally - within the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file. </p> + within the <code class="filename">builtin.mk</code> file. </p> <p> The third section sets <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> and is <span class="emphasis"><em>required</em></span> in all - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> files. The code in this + <code class="filename">builtin.mk</code> files. The code in this section must make the determination whether the built-in software is adequate to satisfy the dependencies listed in <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>. @@ -4376,7 +4387,7 @@ a security check before building any package. See <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>. <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> <span class="emphasis"><em>must</em></span> be set to the correct value by the - end of the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> file. Note that + end of the <code class="filename">builtin.mk</code> file. Note that <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> may be “<span class="quote">yes</span>” even if <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code> @@ -4390,7 +4401,7 @@ a security check before building any package. See set in the previous section. This typically includes, e.g., adding additional dependency restrictions and listing additional files to symlink into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${BUILDLINK_DIR}</code> (via + <code class="filename">${BUILDLINK_DIR}</code> (via <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>). </p> </div> @@ -4422,7 +4433,7 @@ a security check before building any package. See PREFER_NATIVE= getopt skey tcp_wrappers </pre> <p> A package <span class="emphasis"><em>must</em></span> have a - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">builtin.mk</code> + <code class="filename">builtin.mk</code> file to be listed in <code class="varname">PREFER_NATIVE</code>, otherwise it is simply ignored in that list. </p> @@ -4480,21 +4491,21 @@ automatically generated by pkginstall.</p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="files-and-dirs-outside-prefix"></a>12.1. Files and directories outside the installation prefix</h2></div></div></div> -<p>As you already know, the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file holds a list +<p>As you already know, the <code class="filename">PLIST</code> file holds a list of files and directories that belong to a package. The names used in it -are relative to the installation prefix (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}</code>), +are relative to the installation prefix (<code class="filename">${PREFIX}</code>), which means that it cannot register files outside this directory (absolute path names are not allowed). Despite this restriction, some packages need to install files outside this location; e.g., under -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${VARBASE}</code> or -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFDIR}</code>.</p> +<code class="filename">${VARBASE}</code> or +<code class="filename">${PKG_SYSCONFDIR}</code>.</p> <p>The only way to achieve this is to create such files during installation time by using the installation scripts. These scripts can run arbitrary commands, so they have the potential to create and manage files anywhere in the file system. Here is where pkginstall comes into play: it provides generic scripts to abstract the manipulation of such files and directories based on variables set in the package's -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>. The rest of this section describes these +<code class="filename">Makefile</code>. The rest of this section describes these variables.</p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> @@ -4527,7 +4538,7 @@ directories anywhere in the file system:</p> <div class="titlepage"><div><div><h3 class="title"> <a name="files-outside-prefix"></a>12.1.2. File manipulation</h3></div></div></div> <p>Creating non-empty files outside the installation prefix is tricky -because the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> forces all files to be inside it. +because the <code class="filename">PLIST</code> forces all files to be inside it. To overcome this problem, the only solution is to extract the file in the known place (i.e., inside the installation prefix) and copy it to the appropriate location during installation (done by the installation scripts @@ -4583,20 +4594,20 @@ specifies where configuration files shall be installed. Its contents are set based upon the following variables:</p> <div class="itemizedlist"><ul type="disc"> <li><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root - directory. Defaults to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/etc</code> although it may + 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., - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc</code>, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/pkg</code>, etc.). + <code class="filename">/etc</code>, <code class="filename">/etc/pkg</code>, etc.). Packages must not use it directly.</p></li> <li> <p><code class="varname">PKG_SYSCONFSUBDIR</code>: A subdirectory of <code class="varname">PKG_SYSCONFBASE</code> under which the configuration files for the package being built shall be installed. The definition of this variable only makes sense in the package's - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> (i.e., it is not user-customizable).</p> + <code class="filename">Makefile</code> (i.e., it is not user-customizable).</p> <p>As an example, consider the Apache package, - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/apache2/README.html" target="_top"><code xmlns="" class="filename">www/apache2</code></a>, which places its + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/apache2/README.html" target="_top"><code class="filename">www/apache2</code></a>, which places its configuration files under the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">httpd/</code> subdirectory of + <code class="filename">httpd/</code> subdirectory of <code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package Makefile.</p> </li> @@ -4619,13 +4630,13 @@ following:</p> its value is used.</p></li> <li><p>If the previous variable is not defined but <code class="varname">PKG_SYSCONFSUBDIR</code> is set in the package's - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, the resulting value is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li> + <code class="filename">Makefile</code>, the resulting value is + <code class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li> <li><p>Otherwise, it is set to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFBASE}</code>.</p></li> + <code class="filename">${PKG_SYSCONFBASE}</code>.</p></li> </ol></div> -<p>It is worth mentioning that <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFDIR}</code> is -automatically added to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">OWN_DIRS</code>. See <a href="#dirs-outside-prefix" title="12.1.1. Directory manipulation">Section 12.1.1, “Directory manipulation”</a> what this means.</p> +<p>It is worth mentioning that <code class="filename">${PKG_SYSCONFDIR}</code> is +automatically added to <code class="filename">OWN_DIRS</code>. See <a href="#dirs-outside-prefix" title="12.1.1. Directory manipulation">Section 12.1.1, “Directory manipulation”</a> what this means.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> @@ -4649,23 +4660,23 @@ unfortunately).</p> <a name="conf-files-patching"></a>12.2.3. Patching installations</h3></div></div></div> <p>As said before, pkginstall automatically handles configuration files. This means that <span class="strong"><strong>the packages themselves must not -touch the contents of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFDIR}</code> +touch the contents of <code class="filename">${PKG_SYSCONFDIR}</code> directly</strong></span>. Bad news is that many software installation scripts will, out of the box, mess with the contents of that directory. So what is the correct procedure to fix this issue?</p> <p>You must teach the package (usually by manually patching it) to install any configuration files under the examples hierarchy, -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/examples/${PKGBASE}/</code>. This way, the -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> registers them and the administrator always +<code class="filename">share/examples/${PKGBASE}/</code>. This way, the +<code class="filename">PLIST</code> registers them and the administrator always has the original copies available.</p> <p>Once the required configuration files are in place (i.e., under the examples hierarchy), the pkginstall framework can use them as master copies during the package installation to update what is in -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables +<code class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables <code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are used. Check out <a href="#files-outside-prefix" title="12.1.2. File manipulation">Section 12.1.2, “File manipulation”</a> for information about their syntax and their purpose. Here is an example, taken from the -<a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/mail/mutt/README.html" target="_top"><code xmlns="" class="filename">mail/mutt</code></a> package:</p> +<a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/mail/mutt/README.html" target="_top"><code class="filename">mail/mutt</code></a> package:</p> <pre class="programlisting"> EGDIR= ${PREFIX}/share/doc/mutt/samples CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc @@ -4692,10 +4703,10 @@ these files.</p> <p>In order to provide system startup scripts, the package has to:</p> <div class="orderedlist"><ol type="1"> -<li><p>Store the script inside <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${FILESDIR}</code>, with +<li><p>Store the script inside <code class="filename">${FILESDIR}</code>, with the <code class="literal">.sh</code> suffix appended. Considering the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/cups/README.html" target="_top"><code xmlns="" class="filename">print/cups</code></a> package as an example, it has a - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">cupsd.sh</code> in its files directory.</p></li> + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/cups/README.html" target="_top"><code class="filename">print/cups</code></a> package as an example, it has a + <code class="filename">cupsd.sh</code> in its files directory.</p></li> <li> <p>Tell pkginstall to handle it, appending the name of the script, without its extension, to the <code class="varname">RCD_SCRIPTS</code> variable. @@ -4709,12 +4720,12 @@ to:</p> script in an automated fashion:</p> <div class="orderedlist"><ol type="1"> <li><p>Process the file found in the files directory applying all the - substitutions described in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">FILES_SUBST</code> + substitutions described in the <code class="filename">FILES_SUBST</code> variable.</p></li> <li><p>Copy the script from the files directory to the examples - hierarchy, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/examples/rc.d/</code>. Note + hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>. Note that this master file must be explicitly registered in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>.</p></li> + <code class="filename">PLIST</code>.</p></li> <li><p>Add code to the installation scripts to copy the startup script from the examples hierarchy into the system-wide startup scripts directory.</p></li> @@ -4725,7 +4736,7 @@ script in an automated fashion:</p> <p>The automatic copying of config files can be toggled by setting the environment variable <code class="varname">PKG_RCD_SCRIPTS</code> prior to package installation. Note that the scripts will be always copied inside the -examples hierarchy, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/examples/rc.d/</code>, no +examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>, no matter what the value of this variable is.</p> </div> </div> @@ -4747,10 +4758,10 @@ UID for the user. <code class="varname">PKG_GECOS.<em class="replaceable"><code>user</code></em></code> is the user's description or comment. <code class="varname">PKG_HOME.<em class="replaceable"><code>user</code></em></code> is the user's -home directory, and defaults to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/nonexistent</code> if not +home directory, and defaults to <code class="filename">/nonexistent</code> if not specified. <code class="varname">PKG_SHELL.<em class="replaceable"><code>user</code></em></code> is the user's -shell, and defaults to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/sbinno/login</code> if not specified. +shell, and defaults to <code class="filename">/sbinno/login</code> if not specified. </p> <p>Similarly, groups can be created by adding entries to the <code class="varname">PKG_GROUPS</code> variable, whose syntax is:</p> @@ -4770,14 +4781,14 @@ are automatically hardcoded into the final installation scripts.</p> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="shells"></a>12.5. System shells</h2></div></div></div> <p>Packages that install system shells should register them in the shell -database, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/shells</code>, to make things easier to the +database, <code class="filename">/etc/shells</code>, to make things easier to the administrator. This must be done from the installation scripts to keep binary packages working on any system. pkginstall provides an easy way to accomplish this task.</p> <p>When a package provides a shell interpreter, it has to set the <code class="varname">PKG_SHELL</code> variable to its absolute file name. This will add some hooks to the installation scripts to handle it. Consider the -following example, taken from <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/zsh/README.html" target="_top"><code xmlns="" class="filename">shells/zsh</code></a>:</p> +following example, taken from <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/zsh/README.html" target="_top"><code class="filename">shells/zsh</code></a>:</p> <pre class="programlisting"> PKG_SHELL= ${PREFIX}/bin/zsh </pre> @@ -4785,7 +4796,7 @@ following example, taken from <a xmlns="http://www.w3.org/TR/xhtml1/transitional <div class="titlepage"><div><div><h3 class="title"> <a name="shells-disable"></a>12.5.1. Disabling shell registration</h3></div></div></div> <p>The automatic registration of shell interpreters can be disabled by -the administrator by setting the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PKG_REGISTER_SHELLS</code> +the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</code> environment variable to <code class="literal">NO</code>.</p> </div> </div> @@ -4803,7 +4814,7 @@ where <em class="replaceable"><code>type</code></em> can be one of “<span installation scripts to run the appropriate commands to update the fonts database files within each of those directories. For convenience, if the directory path is relative, it is taken to be relative to the package's -installation prefix. Consider the following example, taken from <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/fonts/dbz-ttf/README.html" target="_top"><code xmlns="" class="filename">fonts/dbz-ttf</code></a>:</p> +installation prefix. Consider the following example, taken from <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/fonts/dbz-ttf/README.html" target="_top"><code class="filename">fonts/dbz-ttf</code></a>:</p> <pre class="programlisting"> FONTS_DIRS.ttf= ${PREFIX}/lib/X11/fonts/TTF </pre> @@ -4811,7 +4822,7 @@ installation prefix. Consider the following example, taken from <a xmlns="http: <div class="titlepage"><div><div><h3 class="title"> <a name="fonts-disable"></a>12.6.1. Disabling automatic update of the fonts databases</h3></div></div></div> <p>The automatic update of fonts databases can be disabled by -the administrator by setting the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PKG_UPDATE_FONTS_DB</code> +the administrator by setting the <code class="filename">PKG_UPDATE_FONTS_DB</code> environment variable to <code class="literal">NO</code>.</p> </div> </div> @@ -4823,12 +4834,12 @@ environment variable to <code class="literal">NO</code>.</p> <p><b>Table of Contents</b></p> <dl> <dt><span class="sect1"><a href="#global-default-options">13.1. Global default options</a></span></dt> -<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code></a></span></dt> +<dt><span class="sect1"><a href="#converting-to-options">13.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt> <dt><span class="sect1"><a href="#option-names">13.3. Option Names</a></span></dt> </dl> </div> <p>Many packages have the ability to be built to support different -sets of features. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code> is a framework +sets of features. <code class="filename">bsd.options.mk</code> is a framework in pkgsrc that provides generic handling of those options that determine different ways in which the packages can be built. It's possible for the user to specify exactly which sets of options will be @@ -4840,17 +4851,17 @@ apply.</p> <p>Global default options are listed in <code class="varname">PKG_DEFAULT_OPTIONS</code>, which is a list of the options that should be built into every package if that option is supported. -This variable should be set in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>.</p> +This variable should be set in <code class="filename">/etc/mk.conf</code>.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="converting-to-options"></a>13.2. Converting packages to use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code></h2></div></div></div> +<a name="converting-to-options"></a>13.2. Converting packages to use <code class="filename">bsd.options.mk</code></h2></div></div></div> <p>The following example shows how -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code> should be used +<code class="filename">bsd.options.mk</code> should be used by the hypothetical ``wibble'' package, either in the package -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, or in a file, -e.g. <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">options.mk</code>, that is included by the -main package <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>.</p> +<code class="filename">Makefile</code>, or in a file, +e.g. <code class="filename">options.mk</code>, that is included by the +main package <code class="filename">Makefile</code>.</p> <pre class="programlisting"> PKG_OPTIONS_VAR= PKG_OPTIONS.wibble PKG_SUPPORTED_OPTIONS= wibble-foo ldap @@ -4934,7 +4945,7 @@ build options which are enabled by default.</p></li> <li><p><code class="varname">PKG_OPTIONS_LEGACY_VARS</code> is a list of “<span class="quote"><em class="replaceable"><code>USE_VARIABLE</code></em>:<em class="replaceable"><code>option</code></em></span>” -pairs that map legacy <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> variables to +pairs that map legacy <code class="filename">/etc/mk.conf</code> variables to their option counterparts. Pairs should be added with “<span class="quote">+=</span>” to keep the listing of global legacy variables. A warning will be issued if the user uses a legacy @@ -4961,7 +4972,7 @@ what to use instead.</p></li> To suggest a default set of options, use <code class="varname">PKG_SUGGESTED_OPTIONS</code>.</p> <p><code class="varname">PKG_OPTIONS_VAR</code> must be defined before -including <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code>. If none of +including <code class="filename">bsd.options.mk</code>. If none of <code class="varname">PKG_SUPPORTED_OPTIONS</code>, <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, and <code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> are defined (as can @@ -4969,7 +4980,7 @@ happen with platform-specific options if none of them is supported on the current platform), <code class="varname">PKG_OPTIONS</code> is set to the empty list and the package is otherwise treated as not using the options framework.</p> -<p>After the inclusion of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.options.mk</code>, the +<p>After the inclusion of <code class="filename">bsd.options.mk</code>, the variable <code class="varname">PKG_OPTIONS</code> contains the list of selected build options, properly filtered to remove unsupported and duplicate options.</p> @@ -4997,7 +5008,7 @@ specific to that group, prefix it with the name of the “<span class="quote">main</span>” package (e. g. <code class="varname">djbware-errno-hack</code>).</p> <p>For new options, add a line to -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/defaults/options.description</code>. Lines have two +<code class="filename">mk/defaults/options.description</code>. Lines have two fields, separated by tab. The first field is the option name, the second its description. The description should be a whole sentence (starting with an uppercase letter and ending with a period) that @@ -5058,7 +5069,7 @@ can be put into place on the system.</p> <p>The automatic variable <code class="varname">PREFIX</code> indicates where all files of the final program shall be installed. It is usually set to <code class="varname">LOCALBASE</code> - (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code> + (<code class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code> for pkgs in the “<span class="quote">cross</span>” category. The value of <code class="varname">PREFIX</code> needs to be put into the various places in the program's source where paths to @@ -5082,7 +5093,7 @@ can be put into place on the system.</p> either <code class="varname">X11BASE</code> or <code class="varname">LOCALBASE</code>.</p> <p>Usually, X11 packages should be installed under <code class="varname">LOCALBASE</code> whenever possible. Note that you will - need to include <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../mk/x11.buildlink3.mk</code> + need to include <code class="filename">../../mk/x11.buildlink3.mk</code> in them to request the presence of X11 and to get the right compilation flags.</p> <p>Even though, there are some packages that cannot be installed @@ -5094,11 +5105,11 @@ can be put into place on the system.</p> <p>Some notes: If you need to find includes or libraries installed by a pkg that has <code class="varname">USE_IMAKE</code> or <code class="varname">USE_X11BASE</code> in - its pkg <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, you need to look in - <span class="emphasis"><em>both</em></span> <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${X11BASE}</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${LOCALBASE}</code>. To force installation of + its pkg <code class="filename">Makefile</code>, you need to look in + <span class="emphasis"><em>both</em></span> <code class="filename">${X11BASE}</code> and + <code class="filename">${LOCALBASE}</code>. To force installation of all X11 packages in <code class="varname">LOCALBASE</code>, the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html" target="_top"><code xmlns="" class="filename">pkgtools/xpkgwedge</code></a> package + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/xpkgwedge/README.html" target="_top"><code class="filename">pkgtools/xpkgwedge</code></a> package is enabled by default.</p> </li> <li><p><code class="varname">X11PREFIX</code> should be used to refer to the installed @@ -5116,7 +5127,7 @@ can be put into place on the system.</p> not installed.</p> <p>This is best illustrated by example.</p> <p>The following lines are taken from - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/wm/scwm/Makefile</code>:</p> + <code class="filename">pkgsrc/wm/scwm/Makefile</code>:</p> <pre class="programlisting"> EVAL_PREFIX+= GTKDIR=gtk+ CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE:Q} @@ -5132,10 +5143,10 @@ can be put into place on the system.</p> to the first definition in the <code class="varname">EVAL_PREFIX</code> pair.</p> </li> -<li><p>Within <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}</code>, packages should +<li><p>Within <code class="filename">${PREFIX}</code>, packages should install files according to <a href="http://netbsd.gw.com/cgi-bin/man-cgi?hier+7+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">hier</span>(7)</span></a>, with the exception that - manual pages go into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/man</code>, not - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/man</code>.</p></li> + manual pages go into <code class="filename">${PREFIX}/man</code>, not + <code class="filename">${PREFIX}/share/man</code>.</p></li> </ul></div> </div> <div class="sect1" lang="en"> @@ -5169,7 +5180,7 @@ the <span class="emphasis"><em>wrappers</em></span>.</p></dd> where the distfiles are extracted. It is usually a direct subdirectory of <code class="varname">WRKDIR</code>, and often it's the only directory entry that isn't hidden. This variable may be changed by a package -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>.</p></dd> +<code class="filename">Makefile</code>.</p></dd> </dl></div> </div> <div class="sect1" lang="en"> @@ -5188,7 +5199,7 @@ the package will be built, but not installed.</p> <p>This will check if the file(s) given in the variables <code class="varname">DISTFILES</code> and <code class="varname">PATCHFILES</code> (as defined in the package's Makefile) are present on the - local system in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkgsrc/distfiles</code>. If they + local system in <code class="filename">/usr/pkgsrc/distfiles</code>. If they are not present, an attempt will be made to fetch them using commands of the form:</p> <pre class="programlisting"> @@ -5225,7 +5236,7 @@ the package will be built, but not installed.</p> <code class="varname">EXTRACT_ONLY</code> variable to the list of those files.</p> <p>Extracting the files is usually done by a little program, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/scripts/extract</code>, which already knows how + <code class="filename">mk/scripts/extract</code>, which 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> @@ -5233,18 +5244,18 @@ the package will be built, but not installed.</p> <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 - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/scripts/extract</code>.</p></dd> + <code class="filename">mk/scripts/extract</code>.</p></dd> <dt><span class="term"><code class="varname">EXTRACT_USING</code></span></dt> <dd><p>This variable can be set to <code class="literal">pax</code>, <code class="literal">tar</code> or an absolute pathname pointing to the command with which tar archives should be extracted.</p></dd> </dl></div> -<p>If the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">extract</code> program doesn't serve +<p>If the <code class="filename">extract</code> program doesn't serve your needs, you can also override the <code class="varname">EXTRACT_CMD</code> variable, which holds the command used for extracting the files. This command is executed in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${WRKSRC}</code> directory. During execution of + <code class="filename">${WRKSRC}</code> directory. During execution of this command, the shell variable <code class="varname">extract_file</code> holds the absolute pathname of the file that is going to be extracted.</p> @@ -5258,11 +5269,11 @@ the package will be built, but not installed.</p> <p>After extraction, all the patches named by the <code class="varname">PATCHFILES</code>, those present in the patches subdirectory of the package as well as in $LOCALPATCHES/$PKGPATH (e.g. - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/local/patches/graphics/png</code>) are applied. - Patchfiles ending in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.Z</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.gz</code> are uncompressed before they are applied, - files ending in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.orig</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.rej</code> are ignored. Any special options to <a href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> + <code class="filename">/usr/local/patches/graphics/png</code>) are applied. + Patchfiles ending in <code class="filename">.Z</code> or + <code class="filename">.gz</code> are uncompressed before they are applied, + files ending in <code class="filename">.orig</code> or + <code class="filename">.rej</code> are ignored. Any special options to <a href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in <code class="varname">PATCH_DIST_ARGS</code>. See <a href="#components.patches" title="8.3. patches/*">Section 8.3, “patches/*”</a> for more details.</p> <p>By default <a href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given special args to make it fail if the @@ -5347,7 +5358,7 @@ these directories, the configure script is run with the environment (default: “<span class="quote">./configure</span>”) and <code class="varname">CONFIGURE_ARGS</code> may all be changed by the package.</p> -<p>If the program uses an <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Imakefile</code> for +<p>If the program uses an <code class="filename">Imakefile</code> for configuration, the appropriate steps can be invoked by setting <code class="varname">USE_IMAKE</code> to “<span class="quote">yes</span>”. (If you only want the package installed in <code class="varname">${X11PREFIX}</code> but xmkmf not @@ -5451,7 +5462,7 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< assumed, which means that the package claims to create all needed directories itself before installing files to it. Therefore this variable should only be set in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s that are under control of + <code class="filename">Makefile</code>s that are under control of the package's author.</p></dd> </dl></div> </div> @@ -5496,7 +5507,7 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< This can be used to remove any packages that may have been pulled in by a given package, e.g. if <span><strong class="command">make deinstall DEINSTALLDEPENDS=1</strong></span> is done in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/x11/kde</code>, this is likely to remove whole + <code class="filename">pkgsrc/x11/kde</code>, this is likely to remove whole KDE. Works by adding “<span class="quote">-R</span>” to the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command line.</p></dd> </dl></div> </dd> @@ -5521,7 +5532,7 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< one of the packages to be updated has been changed, resuming <span><strong class="command">make update</strong></span> will most certainly fail!</p> <p>The following variables can be used either on the command line or in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to alter the behaviour of + <code class="filename">/etc/mk.conf</code> to alter the behaviour of <span><strong class="command">make update</strong></span>:</p> <div class="variablelist"><dl> <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt> @@ -5572,7 +5583,7 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< <code class="prompt">#</code> <strong class="userinput"><code>make clean CLEANDEPENDS=YES</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make update</code></strong></pre> <p>The following variables can be used either on the command line or in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to alter the behaviour of + <code class="filename">/etc/mk.conf</code> to alter the behaviour of <span><strong class="command">make clean-update</strong></span>:</p> <div class="variablelist"><dl> <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt> @@ -5589,40 +5600,40 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< package. You can use this to check which version of a package is installed.</p></dd> <dt><span class="term">readme</span></dt> -<dd><p>This target generates a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README.html</code> file, which +<dd><p>This target generates a <code class="filename">README.html</code> file, which can be viewed using a browser such as - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html" target="_top"><code xmlns="" class="filename">www/mozilla</code></a> or - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/links/README.html" target="_top"><code xmlns="" class="filename">www/links</code></a>. + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/mozilla/README.html" target="_top"><code class="filename">www/mozilla</code></a> or + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/www/links/README.html" target="_top"><code class="filename">www/links</code></a>. The generated files contain references to any packages which are in the <code class="varname">PACKAGES</code> directory on the local host. The generated files can be made to refer to URLs based on <code class="varname">FTP_PKG_URL_HOST</code> and <code class="varname">FTP_PKG_URL_DIR</code>. For example, if I wanted to generate - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README.html</code> files which pointed to binary packages + <code class="filename">README.html</code> files which pointed to binary packages on the local machine, in the directory - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/packages</code>, set + <code class="filename">/usr/packages</code>, set <code class="varname">FTP_PKG_URL_HOST=file://localhost</code> and <code class="varname">FTP_PKG_URL_DIR=/usr/packages</code>. The <code class="varname">${PACKAGES}</code> directory and its subdirectories will be searched for all the binary packages.</p></dd> <dt><span class="term">readme-all</span></dt> -<dd><p>Use this target to create a file <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README-all.html</code> +<dd><p>Use this target to create a file <code class="filename">README-all.html</code> which contains a list of all packages currently available in the NetBSD Packages Collection, together with the category they belong to and a short description. This file is compiled from the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/*/README.html</code> files, so be sure to run + <code class="filename">pkgsrc/*/README.html</code> files, so be sure to run this <span class="emphasis"><em>after</em></span> a <span><strong class="command">make readme</strong></span>.</p></dd> <dt><span class="term">cdrom-readme</span></dt> <dd><p>This is very much the same as the “<span class="quote">readme</span>” target (see above), but is to be used when generating a pkgsrc tree to be written to a CD-ROM. This target also produces - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">README.html</code> files, and can be made to refer + <code class="filename">README.html</code> files, and can be made to refer to URLs based on <code class="varname">CDROM_PKG_URL_HOST</code> and <code class="varname">CDROM_PKG_URL_DIR</code>.</p></dd> <dt><span class="term">show-distfiles</span></dt> <dd><p>This target shows which distfiles and patchfiles are needed to build the package. (<code class="varname">DISTFILES</code> and - <code class="varname">PATCHFILES</code>, but not <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">patches/*</code>)</p></dd> + <code class="varname">PATCHFILES</code>, but not <code class="filename">patches/*</code>)</p></dd> <dt><span class="term">show-downlevel</span></dt> <dd><p>This target shows nothing if the package is not installed. If a version of this package is installed, but is not the version provided in this @@ -5644,23 +5655,23 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< <dd><p>After a package is installed, check all its binaries and (on ELF platforms) shared libraries to see if they find the shared libs they need. Run by default if <code class="varname">PKG_DEVELOPER</code> is set in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>.</p></dd> + <code class="filename">/etc/mk.conf</code>.</p></dd> <dt><span class="term">print-PLIST</span></dt> <dd> <p>After a “<span class="quote">make install</span>” from a new or upgraded pkg, this prints out an attempt to generate a new - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> from a <span><strong class="command">find -newer + <code class="filename">PLIST</code> from a <span><strong class="command">find -newer work/.extract_done</strong></span>. An attempt is made to care for shared libs etc., but it is <span class="emphasis"><em>strongly</em></span> recommended to review the result before putting it into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>. On upgrades, it's useful to + <code class="filename">PLIST</code>. On upgrades, it's useful to diff the output of this command against an already - existing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file.</p> + existing <code class="filename">PLIST</code> file.</p> <p>If the package installs files via <a href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a> or other methods that don't update file access times, be sure to add these files manually to your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>, as the “<span class="quote">find + <code class="filename">PLIST</code>, as the “<span class="quote">find -newer</span>” command used by this target won't catch them!</p> <p> See <a href="#print-PLIST" title="10.3. Tweaking output of make print-PLIST">Section 10.3, “Tweaking output of <span><strong class="command">make print-PLIST</strong></span>”</a> for more @@ -5687,7 +5698,7 @@ of <code class="varname">MAKEFILE</code> is “<span class="quote">Makefile< <p> A binary package is considered “<span class="quote">up-to-date</span>” to be installed via <a href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> if:</p> <div class="itemizedlist"><ul type="disc"> -<li><p>None of the package's files (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, +<li><p>None of the package's files (<code class="filename">Makefile</code>, ...) were modified since it was built.</p></li> <li><p>None of the package's required (binary) packages were modified since it was built.</p></li> @@ -5743,7 +5754,7 @@ The tools used by a package can be listed by running <a name="pkgsrc-tools"></a>15.1. Tools for pkgsrc builds</h2></div></div></div> <p> The default set of tools used by pkgsrc is defined in -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bsd.pkg.mk</code>. This includes standard Unix tools, +<code class="filename">bsd.pkg.mk</code>. This includes standard Unix tools, such as: <span><strong class="command">cat</strong></span>, <span><strong class="command">awk</strong></span>, <span><strong class="command">chmod</strong></span>, <span><strong class="command">test</strong></span>, and so on. These can be seen by running: @@ -5790,7 +5801,7 @@ tool at run-time, then just use <code class="varname">DEPENDS</code> instead. <p> When improving or porting pkgsrc to a new platform, have a look at (or create) the corresponding platform specific make file fragment under -<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines +<code class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines the name of the common tools. For example:</p> <pre class="programlisting"> .if exists(/usr/bin/bzcat) @@ -5871,17 +5882,17 @@ TOOLS_PLATFORM.true?= true # shell builtin <a name="pulling-vars-from-etc-mk.conf"></a>16.1.1. How to pull in variables from /etc/mk.conf</h3></div></div></div> <p>The problem with package-defined variables that can be overridden via <code class="varname">MAKECONF</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> is that <a href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> expands a + <code class="filename">/etc/mk.conf</code> is that <a href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> expands a variable as it is used, but evaluates preprocessor-like statements (.if, .ifdef and .ifndef) as they are read. So, to use any variable (which may be set in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>) in one of the .if* - statements, the file <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> must be + <code class="filename">/etc/mk.conf</code>) in one of the .if* + statements, the file <code class="filename">/etc/mk.conf</code> must be included before that .if* statement.</p> <p>Rather than having a number of ad-hoc ways of including - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, should it exist, or + <code class="filename">/etc/mk.conf</code>, should it exist, or <code class="varname">MAKECONF</code>, should it exist, include the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/bsd.prefs.mk</code> file in the package + <code class="filename">pkgsrc/mk/bsd.prefs.mk</code> file in the package Makefile before any preprocessor-like .if, .ifdef, or .ifndef statements:</p> <pre class="programlisting"> @@ -5892,7 +5903,7 @@ TOOLS_PLATFORM.true?= true # shell builtin .endif </pre> <p>If you wish to set the <code class="varname">CFLAGS</code> variable - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>, please make sure to use: + in <code class="filename">/etc/mk.conf</code>, please make sure to use: </p> <pre class="programlisting"> @@ -5903,15 +5914,15 @@ TOOLS_PLATFORM.true?= true # shell builtin Using <code class="varname">CFLAGS=</code> (i.e. without the “<span class="quote">+</span>”) may lead to problems with packages that need to add their own flags. Also, you may want to take a look at - the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html" target="_top"><code xmlns="" class="filename">devel/cpuflags</code></a> package if + the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/cpuflags/README.html" target="_top"><code class="filename">devel/cpuflags</code></a> package if you're interested in optimization for the current CPU.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="where-to-install-documentation"></a>16.1.2. Where to install documentation</h3></div></div></div> <p>Documentation should be installed into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/doc/${PKGNAME}</code> (the + <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or + <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code> (the latter includes the version number of the package).</p> </div> <div class="sect2" lang="en"> @@ -5970,7 +5981,7 @@ TOOLS_PLATFORM.true?= true # shell builtin dependency. pkgsrc supports the <code class="varname">BUILD_DEPENDS</code> and <code class="varname">DEPENDS</code> definitions, the <code class="varname">USE_TOOLS</code> definition, as well as - dependencies via <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code>, which is + dependencies via <code class="filename">buildlink3.mk</code>, which is the preferred way to handle dependencies, and which uses the variables named above. See <a href="#buildlink" title="Chapter 11. Buildlink methodology">Chapter 11, <i>Buildlink methodology</i></a> for more information.</p> @@ -5996,7 +6007,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <li> <p>If your package needs another package's binaries or libraries to build or run, and if that package has a - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file available, use it: + <code class="filename">buildlink3.mk</code> file available, use it: </p> <pre class="programlisting"> .include "../../graphics/jpeg/buildlink3.mk" @@ -6004,7 +6015,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </li> <li> <p>If your package needs to use another package to build - itself and there is no <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> + itself and there is no <code class="filename">buildlink3.mk</code> file available, use the <code class="varname">BUILD_DEPENDS</code> definition:</p> <pre class="programlisting"> @@ -6013,7 +6024,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </li> <li> <p>If your package needs a library with which to link and - again there is no <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file + again there is no <code class="filename">buildlink3.mk</code> file available, this is specified using the <code class="varname">DEPENDS</code> definition. For example:</p> <pre class="programlisting"> @@ -6079,9 +6090,9 @@ TOOLS_PLATFORM.true?= true # shell builtin <li> <p>If your package needs some executable to be able to run correctly and if there's no - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file, this is specified + <code class="filename">buildlink3.mk</code> file, this is specified using the <code class="varname">DEPENDS</code> variable. The - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/lyx/README.html" target="_top"><code xmlns="" class="filename">print/lyx</code></a> package needs to + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/lyx/README.html" target="_top"><code class="filename">print/lyx</code></a> package needs to be able to execute the latex binary from the teTeX package when it runs, and that is specified:</p> <pre class="programlisting"> @@ -6094,17 +6105,17 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>If your package needs files from another package to build, add the relevant distribution files to <code class="varname">DISTFILES</code>, so they will be extracted - automatically. See the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/ghostscript/README.html" target="_top"><code xmlns="" class="filename">print/ghostscript</code></a> package for an example. + automatically. See the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/print/ghostscript/README.html" target="_top"><code class="filename">print/ghostscript</code></a> package for an example. (It relies on the jpeg sources being present in source form during the build.)</p> <p>Please also note the <code class="varname">BUILD_USES_MSGFMT</code> and <code class="varname">BUILD_USES_GETTEXT_M4</code> definitions, which are provided as convenience definitions. The former works out whether <a href="http://netbsd.gw.com/cgi-bin/man-cgi?msgfmt+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">msgfmt</span>(1)</span></a> is part of the base system, and, if it isn't, - installs the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext/README.html" target="_top"><code xmlns="" class="filename">devel/gettext</code></a> package. + installs the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext/README.html" target="_top"><code class="filename">devel/gettext</code></a> package. The latter adds a build dependency on either an installed version of an older gettext package, or if it isn't, installs the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext-m4/README.html" target="_top"><code xmlns="" class="filename">devel/gettext-m4</code></a> package.</p> + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gettext-m4/README.html" target="_top"><code class="filename">devel/gettext-m4</code></a> package.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> @@ -6116,14 +6127,14 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>In this case you can set <code class="varname">CONFLICTS</code> to a space-separated list of packages (including version string) your package conflicts with.</p> -<p>For example, <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw3d/README.html" target="_top"><code xmlns="" class="filename">x11/Xaw3d</code></a> - and <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw-Xpm/README.html" target="_top"><code xmlns="" class="filename">x11/Xaw-Xpm</code></a> +<p>For example, <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw3d/README.html" target="_top"><code class="filename">x11/Xaw3d</code></a> + and <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/x11/Xaw-Xpm/README.html" target="_top"><code class="filename">x11/Xaw-Xpm</code></a> install the same shared library, thus you set in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/x11/Xaw3d/Makefile</code>:</p> + <code class="filename">pkgsrc/x11/Xaw3d/Makefile</code>:</p> <pre class="programlisting"> CONFLICTS= Xaw-Xpm-[0-9]* </pre> -<p>and in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>: +<p>and in <code class="filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>: </p> <pre class="programlisting"> CONFLICTS= Xaw3d-[0-9]* @@ -6169,7 +6180,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="security-handling"></a>16.1.8. Handling packages with security problems</h3></div></div></div> <p>When a vulnerability is found, this should be noted in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">localsrc/security/advisories/pkg-vulnerabilities</code>, + <code class="filename">localsrc/security/advisories/pkg-vulnerabilities</code>, and after committing that file, use <span><strong class="command">make upload</strong></span> in the same directory to update the file on ftp.NetBSD.org.</p> <p>After fixing the vulnerability by a patch, its @@ -6193,7 +6204,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <code class="varname">MACHINE_ARCH</code> and compiler version, disabling optimisation for that file/<code class="varname">MACHINE_ARCH</code>/compiler combination, and - documenting it in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/HACKS</code>. See + documenting it in <code class="filename">pkgsrc/doc/HACKS</code>. See that file for a number of examples!</p> </div> <div class="sect2" lang="en"> @@ -6247,10 +6258,10 @@ TOOLS_PLATFORM.true?= true # shell builtin <a name="no-plain-download"></a>16.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 <code class="varname">DYNAMIC_MASTER_SITES</code> and a <span><strong class="command">make - fetch</strong></span> will call <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">files/getsite.sh</code> + fetch</strong></span> will call <code class="filename">files/getsite.sh</code> with the name of each file to download as an argument, expecting it to output the URL of the directory from which to download - it. <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/ns-cult3d/README.html" target="_top"><code xmlns="" class="filename">graphics/ns-cult3d</code></a> is an + it. <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/ns-cult3d/README.html" target="_top"><code class="filename">graphics/ns-cult3d</code></a> is an example of this usage. </p> <p>If the download can't be automated, because the user must @@ -6279,9 +6290,9 @@ TOOLS_PLATFORM.true?= true # shell builtin set <code class="varname">DIST_SUBDIR</code> to a unique directory name, usually based on <code class="varname">PKGNAME_NOREV</code>. In case this happens more often, <code class="varname">PKGNAME</code> can be used (thus - including the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">nbX</code> suffix) or a date stamp + including the <code class="filename">nbX</code> suffix) or a date stamp can be appended, like <code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>. - Do not forget regenerating the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code> file + Do not forget regenerating the <code class="filename">distinfo</code> file after that, since it contains the <code class="varname">DIST_SUBDIR</code> path in the filenames. Furthermore, a mail to the package's authors seems appropriate @@ -6302,7 +6313,7 @@ TOOLS_PLATFORM.true?= true # shell builtin compiler, linker, etc. to get the Right Thing, which can be pretty annoying especially if you don't have all the machines at your hand to test things. The - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/libtool/README.html" target="_top"><code xmlns="" class="filename">devel/libtool</code></a> pkg + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/libtool/README.html" target="_top"><code class="filename">devel/libtool</code></a> pkg can help here, as it just “<span class="quote">knows</span>” how to build both static and dynamic libraries from a set of source files, thus being platform-independent.</p> @@ -6326,12 +6337,12 @@ TOOLS_PLATFORM.true?= true # shell builtin -rpath ${PREFIX}/lib -version-info major:minor </pre> <p>Note that the library is changed to have a - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.la</code> extension, and the objects are - changed to have a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.lo</code> + <code class="filename">.la</code> extension, and the objects are + changed to have a <code class="filename">.lo</code> extension. Change <code class="varname">OBJS</code> as necessary. This automatically creates all of the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.a</code>, - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.so.major.minor</code>, and ELF symlinks (if + <code class="filename">.a</code>, + <code class="filename">.so.major.minor</code>, and ELF symlinks (if necessary) in the build directory. Be sure to include “<span class="quote">-version-info</span>”, especially when major and minor are zero, as libtool will otherwise strip off the @@ -6365,18 +6376,18 @@ TOOLS_PLATFORM.true?= true # shell builtin automatically.</p> <p>The “<span class="quote">-rpath argument</span>” is the install directory of the library being built.</p> -<p>In the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>, include only the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.la</code> file, the other files will be +<p>In the <code class="filename">PLIST</code>, include only the + <code class="filename">.la</code> file, the other files will be added automatically.</p> </li> <li> -<p>When linking shared object (<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.so</code>) +<p>When linking shared object (<code class="filename">.so</code>) files, i.e. files that are loaded via <a href="http://netbsd.gw.com/cgi-bin/man-cgi?dlopen+3+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">dlopen</span>(3)</span></a>, NOT shared libraries, use “<span class="quote">-module -avoid-version</span>” to prevent them getting version tacked on.</p> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> file gets the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">foo.so</code> entry.</p> +<p>The <code class="filename">PLIST</code> file gets the + <code class="filename">foo.so</code> entry.</p> </li> <li> <p>When linking programs that depend on these libraries @@ -6387,7 +6398,7 @@ TOOLS_PLATFORM.true?= true # shell builtin libtool will not allow you to specify a relative path in -L (such as “<span class="quote">-L../somelib</span>”), because it expects you to change that argument to be the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.la</code> file. e.g.</p> + <code class="filename">.la</code> file. e.g.</p> <pre class="programlisting"> ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib </pre> @@ -6401,16 +6412,16 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>When installing libraries, preface the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> or <a href="http://netbsd.gw.com/cgi-bin/man-cgi?cp+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with “<span class="quote">${LIBTOOL} --mode=install</span>”, and change the library name to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.la</code>. e.g.</p> + <code class="filename">.la</code>. e.g.</p> <pre class="programlisting"> ${LIBTOOL} --mode=install ${BSD_INSTALL_DATA} ${SOMELIB:.a=.la} ${PREFIX}/lib </pre> -<p>This will install the static <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.a</code>, +<p>This will install the static <code class="filename">.a</code>, shared library, any needed symlinks, and run <a href="http://netbsd.gw.com/cgi-bin/man-cgi?ldconfig+8+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p> </li> -<li><p>In your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>, include only - the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.la</code> +<li><p>In your <code class="filename">PLIST</code>, include only + the <code class="filename">.la</code> file (this is a change from previous behaviour).</p></li> </ol></div> </div> @@ -6428,7 +6439,7 @@ TOOLS_PLATFORM.true?= true # shell builtin default, it is set to “<span class="quote">libtool */libtool */*/libtool</span>”. If this does not match the location of the package's libtool script(s), set it as appropriate.</p> -<p>If you do not need <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">*.a</code> static +<p>If you do not need <code class="filename">*.a</code> static libraries built and installed, then use <code class="varname">SHLIBTOOL_OVERRIDE</code> instead.</p> <p>If your package makes use of the platform-independent library @@ -6443,8 +6454,8 @@ TOOLS_PLATFORM.true?= true # shell builtin has been done:</p> <div class="orderedlist"><ol type="1"> <li><p>The shared object is named correctly, i.e. - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libfoo.la</code>, not - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">foo.la</code></p></li> + <code class="filename">libfoo.la</code>, not + <code class="filename">foo.la</code></p></li> <li><p>The -dlopen option is used when linking an executable.</p></li> </ol></div> </li> @@ -6623,7 +6634,7 @@ TOOLS_PLATFORM.true?= true # shell builtin </ul></div> <p>The <code class="varname">INTERACTIVE_STAGE</code> definition is provided to notify the pkgsrc mechanism of an interactive stage which will be needed, and - this should be set in the package's <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, e.g.:</p> + this should be set in the package's <code class="filename">Makefile</code>, e.g.:</p> <pre class="programlisting"> INTERACTIVE_STAGE= build </pre> @@ -6660,10 +6671,10 @@ TOOLS_PLATFORM.true?= true # shell builtin <p> Denoting that a package is covered by a particular license is done by placing the license in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/licenses</code> and setting the + <code class="filename">pkgsrc/licenses</code> and setting the <code class="varname">LICENSE</code> variable to a string identifying the license, e.g. in - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/xv/README.html" target="_top"><code xmlns="" class="filename">graphics/xv</code></a>: </p> + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/graphics/xv/README.html" target="_top"><code class="filename">graphics/xv</code></a>: </p> <pre class="programlisting"> LICENSE= xv-license </pre> @@ -6682,18 +6693,18 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>The license can be viewed with <span><strong class="command">make show-license</strong></span>, and if it is considered appropriate, the line printed above can be added to - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> to indicate acceptance of + <code class="filename">/etc/mk.conf</code> to indicate acceptance of the particular license:</p> <pre class="programlisting"> ACCEPTABLE_LICENSES+=xv-license </pre> <p>When adding a package with a new license, the license - text should be added to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/licenses</code> + text should be added to <code class="filename">pkgsrc/licenses</code> for displaying. A list of known licenses can be seen in this directory as well as by looking at the list of (commented out) <code class="varname">ACCEPTABLE_LICENSES</code> variable settings in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/mk/defaults/mk.conf</code>.</p> + <code class="filename">pkgsrc/mk/defaults/mk.conf</code>.</p> <p>The use of <code class="varname">LICENSE=shareware</code>, <code class="varname">LICENSE=no-commercial-use</code>, and similar language is deprecated because it does not crisply refer to @@ -6713,7 +6724,7 @@ TOOLS_PLATFORM.true?= true # shell builtin installed setgid and the score files owned by the appropriate group and/or owner (traditionally the "games" user/group). The following variables, documented in more detail in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/defaults/mk.conf</code>, control this + <code class="filename">mk/defaults/mk.conf</code>, control this behaviour: <code class="varname">SETGIDGAME</code>, <code class="varname">GAMEDATAMODE</code>, <code class="varname">GAMEGRP</code>, <code class="varname">GAMEMODE</code>, <code class="varname">GAMEOWN</code>.</p> @@ -6742,7 +6753,7 @@ TOOLS_PLATFORM.true?= true # shell builtin Your package may also contain scripts with hardcoded paths to other interpreters besides (or as well as) perl. To correct the full pathname to the script interpreter, you need to set the - following definitions in your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> (we + following definitions in your <code class="filename">Makefile</code> (we shall use <span><strong class="command">tclsh</strong></span> in this example):</p> <pre class="programlisting"> REPLACE_INTERPRETER+= tcl @@ -6763,7 +6774,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <a name="perl-modules"></a>16.5.6. Packages installing perl modules</h3></div></div></div> <p>Makefiles of packages providing perl5 modules should include the Makefile fragment - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../lang/perl5/module.mk</code>. It provides a + <code class="filename">../../lang/perl5/module.mk</code>. It provides a <span><strong class="command">do-configure</strong></span> target for the standard perl configuration for such modules as well as various hooks to tune this configuration. See comments in this file for @@ -6771,8 +6782,8 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>Perl5 modules will install into different places depending on the version of perl used during the build process. To address this, pkgsrc will append lines to the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> corresponding to the files listed in - the installed <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.packlist</code> file generated by + <code class="filename">PLIST</code> corresponding to the files listed in + the installed <code class="filename">.packlist</code> file generated by most perl5 modules. This is invoked by defining <code class="varname">PERL5_PACKLIST</code> to a space-separated list of paths to packlist files, e.g.:</p> @@ -6785,7 +6796,7 @@ TOOLS_PLATFORM.true?= true # shell builtin in which perl5 modules may be installed, and may be used by perl5 packages that don't have a packlist. These three variables are also substituted for in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>.</p> + <code class="filename">PLIST</code>.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> @@ -6793,36 +6804,36 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>Some packages install info files or use the “<span class="quote">makeinfo</span>” or “<span class="quote">install-info</span>” commands. <code class="varname">INFO_FILES</code> should be defined in - the package Makefile so that <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">INSTALL</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DEINSTALL</code> scripts will be generated to + the package Makefile so that <code class="filename">INSTALL</code> and + <code class="filename">DEINSTALL</code> scripts will be generated to handle registration of the info files in the Info directory file. The “<span class="quote">install-info</span>” command used for the info files registration is either provided by the system, or by a special purpose package automatically added as dependency if needed.</p> <p><code class="varname">PKGINFODIR</code> is the directory under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}</code> where info files are primarily + <code class="filename">${PREFIX}</code> where info files are primarily located. <code class="varname">PKGINFODIR</code> defaults to “<span class="quote">info</span>” and can be overridden by the user.</p> <p>The info files for the package should be listed in the - package <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>; however any split info files + package <code class="filename">PLIST</code>; however any split info files need not be listed.</p> <p>A package which needs the “<span class="quote">makeinfo</span>” command at build time must add “<span class="quote">makeinfo</span>” to <code class="varname">USE_TOOLS</code> in its Makefile. If a minimum version of the “<span class="quote">makeinfo</span>” command is needed it should be noted with the <code class="varname">TEXINFO_REQD</code> - variable in the package <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>. By + variable in the package <code class="filename">Makefile</code>. By default, a minimum version of 3.12 is required. If the system does not provide a <span><strong class="command">makeinfo</strong></span> command or if it does not match the required minimum, a build dependency on the - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gtexinfo/README.html" target="_top"><code xmlns="" class="filename">devel/gtexinfo</code></a> package will + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/devel/gtexinfo/README.html" target="_top"><code class="filename">devel/gtexinfo</code></a> package will be added automatically.</p> <p>The build and installation process of the software provided by the package should not use the <span><strong class="command">install-info</strong></span> command as the registration of info files is the task of the package - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">INSTALL</code> script, and it must use the + <code class="filename">INSTALL</code> script, and it must use the appropriate <span><strong class="command">makeinfo</strong></span> command.</p> <p>To achieve this goal, the pkgsrc infrastructure creates overriding scripts for the <span><strong class="command">install-info</strong></span> and @@ -6839,11 +6850,11 @@ TOOLS_PLATFORM.true?= true # shell builtin <a name="manpages"></a>16.5.8. Packages installing man pages</h3></div></div></div> <p>Many packages install manual pages. The man pages are installed under <code class="varname">${PREFIX}/${PKGMANDIR}</code> - which is <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg/man</code> by default. + which is <code class="filename">/usr/pkg/man</code> by default. <code class="varname">PKGMANDIR</code> defaults to “<span class="quote">man</span>”. For example, you can set <code class="varname">PKGMANDIR</code> to “<span class="quote">share/man</span>” to have man pages install under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/usr/pkg/share/man/</code> by default. + <code class="filename">/usr/pkg/share/man/</code> by default. </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> @@ -6851,15 +6862,15 @@ TOOLS_PLATFORM.true?= true # shell builtin is not complete. </p> </div> -<p>The <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> files can just - use <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">man/</code> as the top level directory +<p>The <code class="filename">PLIST</code> files can just + use <code class="filename">man/</code> as the top level directory for the man page file entries and the pkgsrc framework will convert as needed. </p> <p> Packages that are configured with <code class="varname">GNU_CONFIGURE</code> set as “<span class="quote">yes</span>”, by default will use the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">./configure</code> + <code class="filename">./configure</code> --mandir switch to set where the man pages should be installed. The path is <code class="varname">GNU_CONFIGURE_MANDIR</code> which defaults to <code class="varname">${PREFIX}/${PKGMANDIR}</code>. @@ -6868,7 +6879,7 @@ TOOLS_PLATFORM.true?= true # shell builtin Packages that use <code class="varname">GNU_CONFIGURE</code> but do not use --mandir, can set <code class="varname">CONFIGURE_HAS_MANDIR</code> to “<span class="quote">no</span>”. - Or if the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">./configure</code> script uses + Or if the <code class="filename">./configure</code> script uses a non-standard use of --mandir, you can set <code class="varname">GNU_CONFIGURE_MANDIR</code> as needed. </p> @@ -6880,34 +6891,34 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="gconf2-data-files"></a>16.5.9. Packages installing GConf2 data files</h3></div></div></div> <p> - If a package installs <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.schemas</code> or - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.entries</code> files, used by GConf2, + If a package installs <code class="filename">.schemas</code> or + <code class="filename">.entries</code> files, used by GConf2, you need to take some extra steps to make sure they get registered in the database: </p> <div class="orderedlist"><ol type="1"> -<li><p>Include <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../devel/GConf2/schemas.mk</code> - instead of its <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file. This +<li><p>Include <code class="filename">../../devel/GConf2/schemas.mk</code> + instead of its <code class="filename">buildlink3.mk</code> file. This takes care of rebuilding the GConf2 database at installation and deinstallation time, and tells the package where to install GConf2 data files using some standard configure arguments. It also disallows any access to the database directly from the package.</p></li> <li><p>Ensure that the package installs its - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.schemas</code> files under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/gconf/schemas</code>. If they get - installed under <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/etc</code>, you will + <code class="filename">.schemas</code> files under + <code class="filename">${PREFIX}/share/gconf/schemas</code>. If they get + installed under <code class="filename">${PREFIX}/etc</code>, you will need to manually patch the package.</p></li> <li><p>Check the PLIST and remove any entries under the etc/gconf directory, as they will be handled automatically. See <a href="#faq.conf" title="7.14. How do I change the location of configuration files?">Section 7.14, “How do I change the location of configuration files?”</a> for more information.</p></li> <li><p>Define the <code class="varname">GCONF2_SCHEMAS</code> variable in - your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> with a list of all - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.schemas</code> files installed by the package, if + your <code class="filename">Makefile</code> with a list of all + <code class="filename">.schemas</code> files installed by the package, if any. Names must not contain any directories in them.</p></li> <li><p>Define the <code class="varname">GCONF2_ENTRIES</code> variable in - your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> with a - list of all <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.entries</code> files installed by the + your <code class="filename">Makefile</code> with a + list of all <code class="filename">.entries</code> files installed by the package, if any. Names must not contain any directories in them.</p></li> </ol></div> @@ -6916,22 +6927,22 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="scrollkeeper-data-files"></a>16.5.10. Packages installing scrollkeeper data files</h3></div></div></div> <p> - If a package installs <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.omf</code> files, used by + If a package installs <code class="filename">.omf</code> files, used by scrollkeeper, you need to take some extra steps to make sure they get registered in the database: </p> <div class="orderedlist"><ol type="1"> <li><p>Include - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../textproc/scrollkeeper/omf.mk</code> - instead of its <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file. This + <code class="filename">../../textproc/scrollkeeper/omf.mk</code> + instead of its <code class="filename">buildlink3.mk</code> file. This takes care of rebuilding the scrollkeeper database at installation and deinstallation time, and disallows any access to it directly from the package. </p></li> <li><p>Check the PLIST and remove any entries under the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libdata/scrollkeeper</code> directory, as they + <code class="filename">libdata/scrollkeeper</code> directory, as they will be handled automatically.</p></li> -<li><p>Remove the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/omf</code> directory from +<li><p>Remove the <code class="filename">share/omf</code> directory from the PLIST. It will be handled by scrollkeeper.</p></li> </ol></div> </div> @@ -6947,7 +6958,7 @@ TOOLS_PLATFORM.true?= true # shell builtin variables, where <em class="replaceable"><code>type</code></em> can be one of “<span class="quote">ttf</span>”, “<span class="quote">type1</span>” or “<span class="quote">x11</span>”. Also make sure that the database file - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">fonts.dir</code> is not listed in the PLIST.</p> + <code class="filename">fonts.dir</code> is not listed in the PLIST.</p> <p>Note that you should not create new directories for fonts; instead use the standard ones to avoid that the user needs to manually configure his X server to find them.</p> @@ -6960,8 +6971,8 @@ TOOLS_PLATFORM.true?= true # shell builtin properly:</p> <div class="orderedlist"><ol type="1"> <li><p>Include - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../x11/gtk2/modules.mk</code> instead of its - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file. This takes care of + <code class="filename">../../x11/gtk2/modules.mk</code> instead of its + <code class="filename">buildlink3.mk</code> file. This takes care of rebuilding the database at installation and deinstallation time. </p></li> <li><p> @@ -6977,15 +6988,15 @@ TOOLS_PLATFORM.true?= true # shell builtin </p> <div class="itemizedlist"><ul type="disc"> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libdata/gtk-2.0/gdk-pixbuf.loaders</code></p></li> -<li><p><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libdata/gtk-2.0/gtk.immodules</code></p></li> +<li><p><code class="filename">libdata/gtk-2.0/gdk-pixbuf.loaders</code></p></li> +<li><p><code class="filename">libdata/gtk-2.0/gtk.immodules</code></p></li> </ul></div> <p> </p> </li> <li><p> Check the PLIST and remove any entries under the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">libdata/gtk-2.0</code> directory, as they will be + <code class="filename">libdata/gtk-2.0</code> directory, as they will be handled automatically.</p></li> </ol></div> </div> @@ -6998,8 +7009,8 @@ TOOLS_PLATFORM.true?= true # shell builtin </p> <div class="orderedlist"><ol type="1"> <li><p>Include - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in - your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, which takes care of + <code class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in + your <code class="filename">Makefile</code>, which takes care of registering those files in system-wide catalogs at installation and deinstallation time.</p></li> <li><p>Set <code class="varname">SGML_CATALOGS</code> to the full path of @@ -7023,29 +7034,29 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="mime-database"></a>16.5.14. Packages installing extensions to the MIME database</h3></div></div></div> <p>If a package provides extensions to the MIME database by - installing <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.xml</code> files inside - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">${PREFIX}/share/mime/packages</code>, you + installing <code class="filename">.xml</code> files inside + <code class="filename">${PREFIX}/share/mime/packages</code>, you need to take some extra steps to ensure that the database is kept consistent with respect to these new files: </p> <div class="orderedlist"><ol type="1"> <li><p>Include - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../databases/shared-mime-info/mimedb.mk</code> - (avoid using the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> file from + <code class="filename">../../databases/shared-mime-info/mimedb.mk</code> + (avoid using the <code class="filename">buildlink3.mk</code> file from this same directory, which is reserved for inclusion from - other <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">buildlink3.mk</code> files). It takes + other <code class="filename">buildlink3.mk</code> files). It takes care of rebuilding the MIME database at installation and deinstallation time, and disallows any access to it directly from the package.</p></li> <li><p>Check the PLIST and remove any entries under the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/mime</code> directory, + <code class="filename">share/mime</code> directory, <span class="emphasis"><em>except</em></span> for files saved under - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/mime/packages</code>. The former are + <code class="filename">share/mime/packages</code>. The former are handled automatically by the update-mime-database program, but the latter are package-dependent and must be removed by the package that installed them in the first place.</p></li> -<li><p>Remove any <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">share/mime/*</code> directories +<li><p>Remove any <code class="filename">share/mime/*</code> directories from the PLIST. They will be handled by the shared-mime-info package.</p></li> </ol></div> @@ -7054,7 +7065,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="intltool"></a>16.5.15. Packages using intltool</h3></div></div></div> <p>If a package uses intltool during its build, include the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../textproc/intltool/buildlink3.mk</code> file, + <code class="filename">../../textproc/intltool/buildlink3.mk</code> file, which forces it to use the intltool package provided by pkgsrc, instead of the one bundled with the distribution file. </p> @@ -7069,8 +7080,8 @@ TOOLS_PLATFORM.true?= true # shell builtin <p>If a package contains a rc.d script, it won't be copied into the startup directory by default, but you can enable it, by adding the option <code class="varname">PKG_RCD_SCRIPTS=YES</code> in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code>. This option will copy the scripts - into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/rc.d</code> when a package is installed, and + <code class="filename">/etc/mk.conf</code>. This option will copy the scripts + into <code class="filename">/etc/rc.d</code> when a package is installed, and it will automatically remove the scripts when the package is deinstalled.</p> </div> @@ -7078,7 +7089,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h3 class="title"> <a name="tex-packages"></a>16.5.17. Packages installing TeX modules</h3></div></div></div> <p>If a package installs TeX packages into the texmf tree, - the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ls-R</code> database of the tree needs to be + the <code class="filename">ls-R</code> database of the tree needs to be updated.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> @@ -7089,9 +7100,9 @@ TOOLS_PLATFORM.true?= true # shell builtin </div> <div class="orderedlist"><ol type="1"> <li><p>Include - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../print/teTeX/module.mk</code> instead - of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">../../mk/tex.buildlink3.mk</code>. This - takes care of rebuilding the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ls-R</code> + <code class="filename">../../print/teTeX/module.mk</code> instead + of <code class="filename">../../mk/tex.buildlink3.mk</code>. This + takes care of rebuilding the <code class="filename">ls-R</code> database at installation and deinstallation time.</p></li> <li> <p>If your package installs files into a texmf @@ -7107,8 +7118,8 @@ TOOLS_PLATFORM.true?= true # shell builtin enable/disable font map files for TeX output drivers.</p> </li> -<li><p>Make sure that none of <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">ls-R</code> - databases are included in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>, as +<li><p>Make sure that none of <code class="filename">ls-R</code> + databases are included in <code class="filename">PLIST</code>, as they will be removed only by the teTeX-bin package.</p></li> </ol></div> </div> @@ -7135,22 +7146,22 @@ TOOLS_PLATFORM.true?= true # shell builtin debugging aids.</p> <div class="itemizedlist"><ul type="disc"> <li><p>Be sure to set <code class="varname">PKG_DEVELOPER=1</code> - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code></p></li> + in <code class="filename">/etc/mk.conf</code></p></li> <li> -<p>Install <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code xmlns="" class="filename">pkgtools/url2pkg</code></a>, +<p>Install <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>, create a directory for a new package, change into it, then run <span><strong class="command">url2pkg</strong></span>:</p> <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>mkdir /usr/pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>examplepkg</code></em></code></strong> <code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>examplepkg</code></em></code></strong> <code class="prompt">%</code> <strong class="userinput"><code>url2pkg http://www.example.com/path/to/distfile.tar.gz</code></strong></pre> </li> -<li><p>Edit the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code> as requested.</p></li> -<li><p>Fill in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DESCR</code> file</p></li> +<li><p>Edit the <code class="filename">Makefile</code> as requested.</p></li> +<li><p>Fill in the <code class="filename">DESCR</code> file</p></li> <li><p>Run <span><strong class="command">make configure</strong></span> </p></li> <li><p>Add any dependencies glimpsed from documentation and the configure step to the package's - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>.</p></li> + <code class="filename">Makefile</code>.</p></li> <li> <p>Make the package compile, doing multiple rounds of</p> <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make</code></strong> @@ -7164,26 +7175,26 @@ TOOLS_PLATFORM.true?= true # shell builtin shouldn't be, especially during the build phase. <span><strong class="command">mkpatches</strong></span>, <span><strong class="command">patchdiff</strong></span> and <span><strong class="command">pkgvi</strong></span> are - from the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkgdiff</code></a> + from the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package. </p> </li> -<li><p>Look at the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, fix if necessary; - see <a href="#components.Makefile" title="8.1. Makefile">Section 8.1, “<code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>”</a>.</p></li> +<li><p>Look at the <code class="filename">Makefile</code>, fix if necessary; + see <a href="#components.Makefile" title="8.1. Makefile">Section 8.1, “<code class="filename">Makefile</code>”</a>.</p></li> <li> -<p>Generate a <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>:</p> +<p>Generate a <code class="filename">PLIST</code>:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make print-PLIST >PLIST</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make deinstall</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make deinstall</code></strong></pre> -<p>You usually need to be <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="username">root</code> to do this. +<p>You usually need to be <code class="username">root</code> to do this. Look if there are any files left:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make print-PLIST</code></strong></pre> <p>If this reveals any files that are missing in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code>, add them.</p> + <code class="filename">PLIST</code>, add them.</p> </li> <li> -<p>Now that the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> is OK, +<p>Now that the <code class="filename">PLIST</code> is OK, install the package again and make a binary package:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make reinstall</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong></pre> @@ -7204,7 +7215,7 @@ TOOLS_PLATFORM.true?= true # shell builtin <li><p>Play with it. Make sure everything works.</p></li> <li> <p>Run <span><strong class="command">pkglint</strong></span> from - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkglint</code></a>, + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>, and fix the problems it reports:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>pkglint</code></strong></pre> </li> @@ -7261,34 +7272,34 @@ TOOLS_PLATFORM.true?= true # shell builtin <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="general-notes-for-changes"></a>18.3. General notes when adding, updating, or removing packages</h2></div></div></div> <p>Please note all package additions, updates, moves, and - removals in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/CHANGES</code>. It's very + removals in <code class="filename">pkgsrc/doc/CHANGES</code>. It's very important to keep this file up to date and conforming to the existing format, because it will be used by scripts to automatically update pages on <a href="http://www.NetBSD.org/" target="_top">www.NetBSD.org</a> and other sites. Additionally, check the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/TODO</code> file and remove the entry + <code class="filename">pkgsrc/doc/TODO</code> file and remove the entry for the package you updated or removed, in case it was mentioned there.</p> <p>When the <code class="varname">PKGREVISION</code> of a package is bumped, the change should appear in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/CHANGES</code> if it is security + <code class="filename">pkgsrc/doc/CHANGES</code> if it is security related or otherwise relevant. Mass bumps that result from a dependency being updated should not be mentioned. In all other cases it's the developer's decision.</p> <p>There is a make target that helps in creating proper - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">CHANGES</code> entries: <span><strong class="command">make + <code class="filename">CHANGES</code> entries: <span><strong class="command">make changes-entry</strong></span>. It uses the optional <code class="varname">CTYPE</code> and <code class="varname">NETBSD_LOGIN_NAME</code> variables. The general - usage is to first make sure that your <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">CHANGES</code> + usage is to first make sure that your <code class="filename">CHANGES</code> file is up-to-date (to avoid having to resolve conflicts later-on) and then to <span><strong class="command">cd</strong></span> to the package directory. For package updates, <span><strong class="command">make changes-entry</strong></span> is enough. For new packages, or package moves or removals, set the <code class="varname">CTYPE</code> variable on the command line to "Added", "Moved", or "Removed". You can set <code class="varname">NETBSD_LOGIN_NAME</code> - in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">/etc/mk.conf</code> if your local login name is + in <code class="filename">/etc/mk.conf</code> if your local login name is not the same as your NetBSD login name. Don't forget to commit - the changes to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/CHANGES</code>!</p> + the changes to <code class="filename">pkgsrc/doc/CHANGES</code>!</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> @@ -7311,11 +7322,11 @@ TOOLS_PLATFORM.true?= true # shell builtin Remember to move the directory from which you imported out of the way, or cvs will complain the next time you “<span class="quote">cvs update</span>” your source tree. Also don't forget to add the new - package to the category's <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>. + package to the category's <code class="filename">Makefile</code>. </p> <p> The commit message of the initial import should include part of the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DESCR</code> file, so people reading the mailing lists know + <code class="filename">DESCR</code> file, so people reading the mailing lists know what the package is/does. </p> <p> @@ -7388,8 +7399,8 @@ place.</p></li> </li> <li><p>Fix paths in packages from step 5 to point to new location.</p></li> <li><p><span><strong class="command">cvs rm (-f)</strong></span> the package at the old location.</p></li> -<li><p>Remove from <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">oldcategory/Makefile</code>.</p></li> -<li><p>Add to <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">newcategory/Makefile</code>.</p></li> +<li><p>Remove from <code class="filename">oldcategory/Makefile</code>.</p></li> +<li><p>Add to <code class="filename">newcategory/Makefile</code>.</p></li> <li> <p>Commit the changed and removed files:</p> <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong></pre> @@ -7410,24 +7421,24 @@ place.</p></li> <code class="literal">pkgsrc-users</code> mailing list.</p> <div class="qandaset"> <dl> -<dt>19.1. <a href="#id2654769">What is the difference between +<dt>19.1. <a href="#id2654892">What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?</a> </dt> -<dt>19.2. <a href="#id2654805">What is the difference between +<dt>19.2. <a href="#id2654929">What is the difference between MAKE, GMAKE and MAKE_PROGRAM?</a> </dt> -<dt>19.3. <a href="#id2654843">What is the difference between +<dt>19.3. <a href="#id2655035">What is the difference between CC, PKG_CC and PKGSRC_COMPILER?</a> </dt> -<dt>19.4. <a href="#id2654881">What is the difference between +<dt>19.4. <a href="#id2655073">What is the difference between BUILDLINK_LDFLAGS, BUILDLINK_LDADD and BUILDLINK_LIBS?</a> </dt> -<dt>19.5. <a href="#id2654899">Why does make show-var +<dt>19.5. <a href="#id2655091">Why does make show-var VARNAME=BUILDLINK_PREFIX.foo say it's empty?</a> </dt> @@ -7437,7 +7448,7 @@ place.</p></li> <tbody> <tr class="question"> <td align="left" valign="top"> -<a name="id2654769"></a><a name="id2654770"></a><b>19.1.</b> +<a name="id2654892"></a><a name="id2654893"></a><b>19.1.</b> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and @@ -7453,7 +7464,7 @@ place.</p></li> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="id2654805"></a><a name="id2654806"></a><b>19.2.</b> +<a name="id2654929"></a><a name="id2654930"></a><b>19.2.</b> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and @@ -7471,7 +7482,7 @@ place.</p></li> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="id2654843"></a><a name="id2654844"></a><b>19.3.</b> +<a name="id2655035"></a><a name="id2655036"></a><b>19.3.</b> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and @@ -7484,12 +7495,12 @@ place.</p></li> <code class="varname">PKG_CC</code> is the path to the compiler wrapper. <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a path to a compiler, but the type of compiler that should be - used. See <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/compiler.mk</code> for more + used. See <code class="filename">mk/compiler.mk</code> for more information about the latter variable.</p></td> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="id2654881"></a><a name="id2654882"></a><b>19.4.</b> +<a name="id2655073"></a><a name="id2655074"></a><b>19.4.</b> </td> <td align="left" valign="top"><p>What is the difference between <code class="varname">BUILDLINK_LDFLAGS</code>, @@ -7502,7 +7513,7 @@ place.</p></li> </tr> <tr class="question"> <td align="left" valign="top"> -<a name="id2654899"></a><a name="id2654900"></a><b>19.5.</b> +<a name="id2655091"></a><a name="id2655092"></a><b>19.5.</b> </td> <td align="left" valign="top"><p>Why does <span><strong class="command">make show-var VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> @@ -7642,7 +7653,7 @@ place.</p></li> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="infr.design.intf"></a>20.2. Designing interfaces for Makefile fragments</h2></div></div></div> -<p>Most of the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.mk</code> files fall into one +<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> @@ -7650,10 +7661,10 @@ place.</p></li> <div class="titlepage"><div><div><h3 class="title"> <a name="infr.design.intf.proc"></a>20.2.1. Procedures with parameters</h3></div></div></div> <p>In a traditional imperative programming language some of - the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">.mk</code> files could be described as + the <code class="filename">.mk</code> files could be described as procedures. They take some input parameters and—after inclusion—provide a result in output parameters. Since all - variables in <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>s have global scope + variables in <code class="filename">Makefile</code>s have global scope care must be taken not to use parameter names that have already another meaning. For example, <code class="varname">PKGNAME</code> is a bad choice for a parameter name.</p> @@ -7674,8 +7685,8 @@ place.</p></li> call the procedure more than once. That is, the file must not contain multiple-inclusion guards.</p> <p>Examples for procedures are - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bsd.options.mk</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express + <code class="filename">mk/bsd.options.mk</code> and + <code class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express that the parameters are evaluated at load time, they should be assigned using the <code class="literal">:=</code> operator, which should be used only for this purpose.</p> @@ -7689,7 +7700,7 @@ place.</p></li> pkgsrc infrastructure, while other must be included explicitly.</p> <p>An example for action files is - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/subst.mk</code>.</p> + <code class="filename">mk/subst.mk</code>.</p> </div> </div> </div> @@ -7724,16 +7735,16 @@ place.</p></li> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="regression.run"></a>21.2. Running the regression tests</h2></div></div></div> -<p>You first need to install the <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_regress/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkg_regress</code></a> package, which +<p>You first need to install the <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkg_regress/README.html" target="_top"><code class="filename">pkgtools/pkg_regress</code></a> package, which provides the <span><strong class="command">pkg_regress</strong></span> command. Then you can simply run that command, which will run all tests in the - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">regress</code> category.</p> + <code class="filename">regress</code> category.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="regression.new"></a>21.3. Adding a new regression test</h2></div></div></div> -<p>Every directory in the <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">regress</code> - category that contains a file called <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">spec</code> +<p>Every directory in the <code class="filename">regress</code> + category that contains a file called <code class="filename">spec</code> is considered a regression test. This file is a shell program that is included by the <span><strong class="command">pkg_regress</strong></span> command. The following functions can be overridden to suit your @@ -7809,11 +7820,11 @@ place.</p></li> <code class="literal">MyOS</code> in this example), you need to touch the following files:</p> <div class="variablelist"><dl> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">bootstrap/mods/mk/<em class="replaceable"><code>MyOS</code></em>.sys.mk</code></span></dt> +<dt><span class="term"><code class="filename">bootstrap/mods/mk/<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 compiler.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/bsd.prefs.mk</code></span></dt> +<dt><span class="term"><code class="filename">mk/bsd.prefs.mk</code></span></dt> <dd><p>Insert code that defines the variables <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code>, <code class="varname">LOWER_OS_VERSION</code>, @@ -7821,37 +7832,37 @@ place.</p></li> <code class="varname">MACHINE_ARCH</code>, <code class="varname">OBJECT_FMT</code>, <code class="varname">APPEND_ELF</code>, and the other variables that appear in this file.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/platform/MyOS.mk</code></span></dt> +<dt><span class="term"><code class="filename">mk/platform/MyOS.mk</code></span></dt> <dd><p>This file contains the platform-specific definitions that are used by pkgsrc. Start by copying one of the other files and edit it to your needs.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/platform/MyOS.pkg.dist</code></span></dt> +<dt><span class="term"><code class="filename">mk/platform/MyOS.pkg.dist</code></span></dt> <dd><p>This file contains a list of directories, together with their permission bits and ownership. These directories will be created automatically with every package that does not explicitly set <code class="varname">NO_MTREE</code>. There have been some discussions about whether this file is needed at all, but with no result.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/platform/MyOS.x11.dist</code></span></dt> +<dt><span class="term"><code class="filename">mk/platform/MyOS.x11.dist</code></span></dt> <dd><p>Just copy one of the pre-existing x11.dist files to your - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename"><em class="replaceable"><code>MyOS</code></em>.x11.dist</code>.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/tools/bootstrap.mk</code></span></dt> + <code class="filename"><em class="replaceable"><code>MyOS</code></em>.x11.dist</code>.</p></dd> +<dt><span class="term"><code class="filename">mk/tools/bootstrap.mk</code></span></dt> <dd><p>On some operating systems, the tools that are provided with the base system are not good enough for pkgsrc. For example, there are many versions of <a href="http://netbsd.gw.com/cgi-bin/man-cgi?sed+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> that have a narrow limit on the line length they can process. Therefore pkgsrc brings its own tools, which can be enabled here.</p></dd> -<dt><span class="term"><code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">mk/tools/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt> +<dt><span class="term"><code class="filename">mk/tools/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt> <dd><p>This file defines the paths to all the tools that are needed by one or the other package in pkgsrc, as well as by pkgsrc itself. Find out where these tools are on your platform and add them.</p></dd> </dl></div> <p>Now, you should be able to build some basic packages, like - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/perl5/README.html" target="_top"><code xmlns="" class="filename">lang/perl5</code></a>, <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/bash/README.html" target="_top"><code xmlns="" class="filename">shells/bash</code></a>.</p> + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/lang/perl5/README.html" target="_top"><code class="filename">lang/perl5</code></a>, <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a>.</p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> @@ -7929,7 +7940,7 @@ place.</p></li> <div class="titlepage"><div><div><h3 class="title"> <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with <span><strong class="command">pkglint</strong></span></h3></div></div></div> <p>The NetBSD package system comes with - <a xmlns="http://www.w3.org/TR/xhtml1/transitional" href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code xmlns="" class="filename">pkgtools/pkglint</code></a> + <a href="ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a> which helps to check the contents of these files. After installation it is quite easy to use, just change to the directory of the package you wish to examine and execute @@ -7950,8 +7961,8 @@ looks fine.</pre> <code class="prompt">#</code> <strong class="userinput"><code>mkdir bison</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>cd bison</code></strong> <code class="prompt">#</code> <strong class="userinput"><code>mkdir patches</code></strong></pre> -<p>Create <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">Makefile</code>, <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">DESCR</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">PLIST</code> (see <a href="#components" title="Chapter 8. Package components - files, directories and contents">Chapter 8, <i>Package components - files, directories and contents</i></a>) +<p>Create <code class="filename">Makefile</code>, <code class="filename">DESCR</code> and + <code class="filename">PLIST</code> (see <a href="#components" title="Chapter 8. Package components - files, directories and contents">Chapter 8, <i>Package components - files, directories and contents</i></a>) then continue with fetching the distfile:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make fetch</code></strong> >> bison-1.25.tar.gz doesn't seem to exist on this system. @@ -7967,7 +7978,7 @@ ftp: Error retrieving file: 500 Internal error Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/) Successfully retrieved file.</pre> <p>Generate the checksum of the distfile into - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">distinfo</code>:</p> + <code class="filename">distinfo</code>:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make makesum</code></strong></pre> <p>Now compile:</p> <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong> @@ -8167,83 +8178,91 @@ Registering depends:. </div> <div class="appendix" lang="en"> <div class="titlepage"><div><div><h2 class="title"> -<a name="ftp-layout"></a>Appendix C. Layout of the FTP server's package archive</h2></div></div></div> -<p>Layout for precompiled binary packages on ftp.NetBSD.org:</p> -<pre class="programlisting"> - /pub/NetBSD/packages/ - distfiles/ - - # Unpacked pkgsrc trees - pkgsrc-current -> /pub/NetBSD/NetBSD-current/pkgsrc - pkgsrc-2003Q4 -> N/A - pkgsrc-2004Q1/pkgsrc - - # pkgsrc archives - pkgsrc-current.tar.gz -> ../NetBSD-current/tar_files/pkgsrc.tar.gz - pkgsrc-2003Q4.tar.gz -> N/A - pkgsrc-2004Q1.tar.gz -> N/A - - # Per pkgsrc-release/OS-release/arch package archives - pkgsrc-2003Q4/ - NetBSD-1.6.2/ - i386/ - All/ - archivers/ - foo -> ../All/foo - ... - pkgsrc-2004Q1/ - NetBSD-1.6.2/ - i386/ - All/ - ... - NetBSD-2.0/ - i386/ - All/ - ... - SunOS-5.9/ - sparc/ - All/ - ... - x86/ - All/ - ... - - # Per os-release package archive convenience links - NetBSD-1.6.2 -> 1.6.2 - 1.6.2/ - i386 -> ../pkgsrc-2004Q1/NetBSD-1.6.2/i386 - m68k/ - All/ - archivers/ - foo -> ../All/foo - ... - amiga -> m68k - atari -> m68k - ... - - 2.0 -> NetBSD-2.0 # backward compat, historic - NetBSD-2.0/ - i386 -> ../pkgsrc-2004Q1/NetBSD-2.0/i386 - SunOS-5.9/ - sparc -> ../pkgsrc-2004Q1/SunOS-5.9/sparc - x86 -> ../pkgsrc-2004Q1/SunOS-5.9/x86 -</pre> -<p> - To create:</p> -<div class="orderedlist"><ol type="1"> -<li><p> Run bulk build, see <a href="#bulkbuild" title="6.3. Doing a bulk build of all packages">Section 6.3, “Doing a bulk build of all packages”</a> </p></li> -<li> -<p> Upload /usr/pkgsrc/packages to </p> -<pre class="programlisting"> - ftp://ftp.NetBSD.org/pub/NetBSD/packages/\ - pkgsrc-2004Q4/\ # pkgsrc-branch - `uname -s`-`uname -r`/\ # OS & version - `uname -p` # architecture -</pre> -</li> -<li><p> If necessary, create a symlink <span><strong class="command">ln -s `uname -m` `uname - -p`</strong></span> (amiga -> m68k, ...) </p></li> -</ol></div> +<a name="ftp-layout"></a>Appendix C. Directory layout of the pkgsrc FTP server</h2></div></div></div> +<div class="toc"> +<p><b>Table of Contents</b></p> +<dl> +<dt><span class="sect1"><a href="#ftp-bootstrap">C.1. <code class="filename">bootstrap-pkgsrc</code>: Bootstrap kits</a></span></dt> +<dt><span class="sect1"><a href="#ftp-distfiles">C.2. <code class="filename">distfiles</code>: The distributed source files</a></span></dt> +<dt><span class="sect1"><a href="#ftp-iso">C.3. <code class="filename">iso</code>: Currently empty</a></span></dt> +<dt><span class="sect1"><a href="#ftp-misc">C.4. <code class="filename">misc</code>: Miscellaneous things</a></span></dt> +<dt><span class="sect1"><a href="#ftp-packages">C.5. <code class="filename">packages*</code>: Binary packages</a></span></dt> +<dt><span class="sect1"><a href="#ftp-source">C.6. <code class="filename">current</code>, +<code class="filename">200<em class="replaceable"><code>x</code></em>Q<em class="replaceable"><code>y</code></em></code>: +source packages</a></span></dt> +</dl> +</div> +<p>As in other big projects, the directory layout of pkgsrc + is quite complex for newbies. This chapter explains where you + find things on the FTP server. The base directory on + <code class="filename">ftp.NetBSD.org</code> is <a href="ftp://ftp.NetBSD.org/pub/pkgsrc" target="_top"><code class="filename">/pub/pkgsrc</code></a>. + This directory contains some subdirectories, which are explained + below.</p> +<div class="sect1" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-bootstrap"></a>C.1. <code class="filename">bootstrap-pkgsrc</code>: Bootstrap kits</h2></div></div></div> +<p>For those who only want to manage binary packages on + systems other than NetBSD, we provide the package management + tools in a separate, small tar file.</p> +</div> +<div class="sect1" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-distfiles"></a>C.2. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div> +<p>The directory <code class="filename">distfiles</code> contains lots + of archive files from all pkgsrc packages, which are mirrored + here. The subdirectories are called after their package names + and are used when the distributed files have names that don't + explicitly contain a version number or are otherwise too generic + (for example <code class="filename">release.tar.gz</code>).</p> +</div> +<div class="sect1" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-iso"></a>C.3. <code class="filename">iso</code>: Currently empty</h2></div></div></div> +<p>This directory is currently not in use.</p> +</div> +<div class="sect1" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-misc"></a>C.4. <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" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-packages"></a>C.5. <code class="filename">packages*</code>: Binary packages</h2></div></div></div> +<p>These directories contain binary packages. Those + directories that have a branch name + (200<em class="replaceable"><code>x</code></em>Q<em class="replaceable"><code>y</code></em>) + contain packages from that particular branch. The directory + <code class="filename">packages</code> contains binary packages from + pkgsrc-current. (However, this does not necessarily mean that + the packages are still current anymore.)</p> +<p>Below the <code class="filename">packages*</code> directories are + directories that distinguish the packages by operating system + and version, the next directory level specifies the hardware + architecture.</p> +<p>In each of the platform-specific directories, there is a + whole binary packages collection. It has a directory called + <code class="filename">All</code> which contains all binary packages. + Besides that, there are various category directories that + contain symbolic links to the real binary packages.</p> +</div> +<div class="sect1" lang="en"> +<div class="titlepage"><div><div><h2 class="title" style="clear: both"> +<a name="ftp-source"></a>C.6. <code class="filename">current</code>, +<code class="filename">200<em class="replaceable"><code>x</code></em>Q<em class="replaceable"><code>y</code></em></code>: +source packages</h2></div></div></div> +<p>These directories contain the “<span class="quote">real</span>” pkgsrc, + that is the files that define how to create binary packages from + source archives.</p> +<p>The directory <code class="filename">pkgsrc</code> contains a + snapshot of the CVS repository, which is updated on a regularly + basis. The file <code class="filename">pkgsrc.tar.gz</code> contains the + same as the directory, ready to be downloaded as a whole.</p> +<p>In the directories for the quarterly branches, there is an + additional file called + <code class="filename">pkgsrc-200<em class="replaceable"><code>x</code></em>Q<em class="replaceable"><code>y</code></em>.tar.gz</code>, + which contains the state of pkgsrc when it was branched.</p> +</div> </div> <div class="appendix" lang="en"> <div class="titlepage"><div><div><h2 class="title"> @@ -8264,29 +8283,29 @@ Registering depends:. <a name="targets"></a>D.1. Targets</h2></div></div></div> <p> The pkgsrc guide's source code is stored in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/guide/files</code>, and several files are + <code class="filename">pkgsrc/doc/guide/files</code>, and several files are created from it: </p> <div class="itemizedlist"><ul type="disc"> <li><p> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/pkgsrc.txt</code> + <code class="filename">pkgsrc/doc/pkgsrc.txt</code> </p></li> <li><p> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/pkgsrc.html</code> + <code class="filename">pkgsrc/doc/pkgsrc.html</code> </p></li> <li><p> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">http://www.NetBSD.org/Documentation/pkgsrc/</code>: + <code class="filename">http://www.NetBSD.org/Documentation/pkgsrc/</code>: the documentation on the NetBSD website will be built from pkgsrc and kept up to date on the web server itself. This means you <span class="emphasis"><em>must</em></span> make sure that your changes haven't broken the build! </p></li> <li><p> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.pdf</code>: + <code class="filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.pdf</code>: PDF version of the pkgsrc guide. </p></li> <li><p> - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.ps</code>: + <code class="filename">http://www.NetBSD.org/Documentation/pkgsrc/pkgsrc.ps</code>: PostScript version of the pkgsrc guide. </p></li> </ul></div> @@ -8307,26 +8326,26 @@ Registering depends:. versions. You will need both packages installed, to make sure documentation is consistent across all formats. The packages can be found in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/meta-pkgs/netbsd-doc</code> and - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/meta-pkgs/netbsd-doc-print</code>. + <code class="filename">pkgsrc/meta-pkgs/netbsd-doc</code> and + <code class="filename">pkgsrc/meta-pkgs/netbsd-doc-print</code>. </p></li> <li><p> Edit the XML file(s) in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/guide/files</code>. + <code class="filename">pkgsrc/doc/guide/files</code>. </p></li> <li><p> Run <span><strong class="command">make extract && make do-lint</strong></span> in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/guide</code> to check the XML + <code class="filename">pkgsrc/doc/guide</code> to check the XML syntax, and fix it if needed. </p></li> <li><p> Run <span><strong class="command">make</strong></span> in - <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc/guide</code> to build the HTML and + <code class="filename">pkgsrc/doc/guide</code> to build the HTML and ASCII version. </p></li> <li><p> If all is well, run <span><strong class="command">make install-doc</strong></span> to put - the generated files into <code xmlns="http://www.w3.org/TR/xhtml1/transitional" class="filename">pkgsrc/doc</code>. + the generated files into <code class="filename">pkgsrc/doc</code>. </p></li> <li><p> <span><strong class="command">cvs commit pkgsrc/doc/guide/files</strong></span> |