Annotation of pkgsrc/doc/pkgsrc.html, revision 1.340
1.75 rillig 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
1.1 grant 3: <head>
1.75 rillig 4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5: <title>The pkgsrc guide</title>
1.132 spz 6: <link rel="stylesheet" type="text/css" href="/global.css">
1.75 rillig 7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
1.91 rillig 8: <meta name="description" content="pkgsrc is a centralized package management system for Unix-like operating systems. This guide provides information for users and developers of pkgsrc. It covers installation of binary and source packages, creation of binary and source packages and a high-level overview about the infrastructure.">
1.75 rillig 9: </head>
1.148 asau 10: <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book">
1.75 rillig 11: <div class="titlepage">
12: <div>
13: <div><h1 class="title">
14: <a name="the-pkgsrc-guide"></a>The pkgsrc guide</h1></div>
15: <div><h2 class="subtitle">Documentation on the NetBSD packages system</h2></div>
16: <div><div class="authorgroup">
17: <div class="author">
18: <h3 class="author">
19: <span class="firstname">Alistair</span> <span class="surname">Crooks</span>
20: </h3>
1.110 hubertf 21: <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:agc@NetBSD.org">agc@NetBSD.org</a>></code></p></div></div>
1.75 rillig 22: </div>
23: <div class="author">
24: <h3 class="author">
25: <span class="firstname">Hubert</span> <span class="surname">Feyrer</span>
26: </h3>
1.110 hubertf 27: <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:hubertf@NetBSD.org">hubertf@NetBSD.org</a>></code></p></div></div>
1.75 rillig 28: </div>
29: <h3 class="corpauthor">
30: The pkgsrc Developers
31: </h3>
32: </div></div>
1.328 jnemeth 33: <div><p class="copyright">Copyright © 1994-2022 The NetBSD Foundation, Inc</p></div>
34: <div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.41 2022/01/01 06:45:38 jnemeth Exp $</p></div>
1.148 asau 35: <div><div class="abstract">
1.75 rillig 36: <p class="title"><b>Abstract</b></p>
37: <p>pkgsrc is a centralized package management system for
38: Unix-like operating systems. This guide provides information for
39: users and developers of pkgsrc. It covers installation of binary
40: and source packages, creation of binary and source packages and
41: a high-level overview about the infrastructure.</p>
42: </div></div>
43: </div>
44: <hr>
45: </div>
46: <div class="toc">
47: <p><b>Table of Contents</b></p>
1.210 leot 48: <dl class="toc">
1.75 rillig 49: <dt><span class="chapter"><a href="#introduction">1. What is pkgsrc?</a></span></dt>
50: <dd><dl>
51: <dt><span class="sect1"><a href="#introduction-section">1.1. Introduction</a></span></dt>
1.82 rillig 52: <dd><dl>
53: <dt><span class="sect2"><a href="#why-pkgsrc">1.1.1. Why pkgsrc?</a></span></dt>
54: <dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt>
55: </dl></dd>
1.75 rillig 56: <dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt>
57: <dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt>
1.88 wiz 58: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
1.75 rillig 59: <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
60: </dl></dd>
61: <dt><span class="part"><a href="#users-guide">I. The pkgsrc user's guide</a></span></dt>
62: <dd><dl>
1.267 rillig 63: <dt><span class="chapter"><a href="#help-user">2. Getting help</a></span></dt>
64: <dt><span class="chapter"><a href="#getting">3. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
1.75 rillig 65: <dd><dl>
1.267 rillig 66: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.75 rillig 67: <dd><dl>
1.267 rillig 68: <dt><span class="sect2"><a href="#getting-via-tar">3.1.1. As tar archive</a></span></dt>
69: <dt><span class="sect2"><a href="#getting-via-cvs">3.1.2. Via anonymous CVS</a></span></dt>
1.75 rillig 70: </dl></dd>
1.267 rillig 71: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.75 rillig 72: <dd><dl>
1.267 rillig 73: <dt><span class="sect2"><a href="#uptodate-tar">3.2.1. Via tar files</a></span></dt>
74: <dt><span class="sect2"><a href="#uptodate-cvs">3.2.2. Via CVS</a></span></dt>
1.75 rillig 75: </dl></dd>
76: </dl></dd>
1.267 rillig 77: <dt><span class="chapter"><a href="#platforms">4. Using pkgsrc on systems other than NetBSD</a></span></dt>
1.75 rillig 78: <dd><dl>
1.267 rillig 79: <dt><span class="sect1"><a href="#binarydist">4.1. Binary distribution</a></span></dt>
80: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">4.2. Bootstrapping pkgsrc</a></span></dt>
1.75 rillig 81: </dl></dd>
1.267 rillig 82: <dt><span class="chapter"><a href="#using">5. Using pkgsrc</a></span></dt>
1.75 rillig 83: <dd><dl>
1.267 rillig 84: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.75 rillig 85: <dd><dl>
1.267 rillig 86: <dt><span class="sect2"><a href="#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
87: <dt><span class="sect2"><a href="#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
1.317 nia 88: <dt><span class="sect2"><a href="#using.pkgin_update">5.1.3. Updating packages</a></span></dt>
89: <dt><span class="sect2"><a href="#using.pkg_delete">5.1.4. Deinstalling packages</a></span></dt>
90: <dt><span class="sect2"><a href="#using.pkg_info">5.1.5. Getting information about installed packages</a></span></dt>
91: <dt><span class="sect2"><a href="#vulnerabilities">5.1.6. Checking for security vulnerabilities in installed packages</a></span></dt>
92: <dt><span class="sect2"><a href="#pkg_versions">5.1.7. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
93: <dt><span class="sect2"><a href="#using.pkg_admin">5.1.8. Other administrative functions</a></span></dt>
1.75 rillig 94: </dl></dd>
1.267 rillig 95: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.75 rillig 96: <dd><dl>
1.267 rillig 97: <dt><span class="sect2"><a href="#requirements">5.2.1. Requirements</a></span></dt>
98: <dt><span class="sect2"><a href="#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
99: <dt><span class="sect2"><a href="#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.75 rillig 100: </dl></dd>
101: </dl></dd>
1.267 rillig 102: <dt><span class="chapter"><a href="#configuring">6. Configuring pkgsrc</a></span></dt>
1.75 rillig 103: <dd><dl>
1.267 rillig 104: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
105: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
106: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
107: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1.88 wiz 108: <dd><dl>
1.267 rillig 109: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
110: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
111: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.88 wiz 112: </dl></dd>
1.267 rillig 113: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
114: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.75 rillig 115: </dl></dd>
1.267 rillig 116: <dt><span class="chapter"><a href="#binary">7. Creating binary packages</a></span></dt>
1.75 rillig 117: <dd><dl>
1.267 rillig 118: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
119: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.106 rillig 120: </dl></dd>
1.267 rillig 121: <dt><span class="chapter"><a href="#bulk">8. Creating binary packages for everything in pkgsrc (bulk
1.106 rillig 122: builds)</a></span></dt>
1.75 rillig 123: <dd><dl>
1.267 rillig 124: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.295 rillig 125: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.267 rillig 126: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
127: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.293 rillig 128: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
129: <dd><dl>
1.294 rillig 130: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
131: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.296 rillig 132: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
133: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
134: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
135: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
136: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
137: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
138: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
139: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.293 rillig 140: </dl></dd>
141: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
142: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.267 rillig 143: </dl></dd>
144: <dt><span class="chapter"><a href="#files">9. Directory layout of the installed files</a></span></dt>
145: <dd><dl>
146: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
147: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
148: </dl></dd>
149: <dt><span class="chapter"><a href="#faq">10. Frequently Asked Questions</a></span></dt>
150: <dd><dl>
151: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
152: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
153: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
154: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
155: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">10.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
156: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
157: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
158: <dt><span class="sect1"><a href="#passive-ftp">10.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
159: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
160: <dt><span class="sect1"><a href="#tmac.andoc-missing">10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.128 wiz 161: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.267 rillig 162: <dt><span class="sect1"><a href="#bsd.own.mk-missing">10.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
1.336 nia 163: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.267 rillig 164: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
165: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
166: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
167: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
168: <dt><span class="sect1"><a href="#faq.rcs-conflicts">10.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</a></span></dt>
1.75 rillig 169: </dl></dd>
170: </dl></dd>
171: <dt><span class="part"><a href="#developers-guide">II. The pkgsrc developer's guide</a></span></dt>
172: <dd><dl>
1.267 rillig 173: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.299 rillig 174: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.91 rillig 175: <dd><dl>
1.299 rillig 176: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
177: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
178: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.91 rillig 179: <dd><dl>
1.299 rillig 180: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
181: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
182: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
183: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
184: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.91 rillig 185: </dl></dd>
1.299 rillig 186: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
187: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
188: <dd><dl>
189: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
190: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
191: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
192: </dl></dd>
193: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
194: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.106 rillig 195: </dl></dd>
1.299 rillig 196: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.106 rillig 197: <dd><dl>
1.299 rillig 198: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
199: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
200: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
201: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
202: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.106 rillig 203: <dd><dl>
1.299 rillig 204: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
205: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.106 rillig 206: </dl></dd>
1.299 rillig 207: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
208: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
209: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
210: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
211: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
212: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
213: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
214: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
215: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
216: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
217: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
218: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
219: </dl></dd>
220: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
221: <dd><dl>
222: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.106 rillig 223: <dd><dl>
1.334 nia 224: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
225: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
226: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.106 rillig 227: </dl></dd>
1.299 rillig 228: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
229: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">14.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
1.106 rillig 230: </dl></dd>
1.299 rillig 231: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.106 rillig 232: <dd><dl>
1.299 rillig 233: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
234: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
235: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
236: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.106 rillig 237: <dd><dl>
1.299 rillig 238: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
239: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
240: <dt><span class="sect2"><a href="#cflags-gnu-configure">15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</a></span></dt>
241: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.106 rillig 242: </dl></dd>
243: </dl></dd>
1.299 rillig 244: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.106 rillig 245: <dd><dl>
1.299 rillig 246: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
247: <dt><span class="sect1"><a href="#converting-to-options">16.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt>
248: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
249: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.106 rillig 250: </dl></dd>
1.299 rillig 251: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.106 rillig 252: <dd><dl>
1.299 rillig 253: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
254: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
255: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
256: </dl></dd>
257: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
258: <dd><dl>
259: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
260: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.106 rillig 261: <dd><dl>
1.299 rillig 262: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
263: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.133 wiz 264: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
265: and
266: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
267: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.106 rillig 268: </dl></dd>
1.299 rillig 269: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
270: <dd><dl>
271: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
272: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
273: </dl></dd>
274: </dl></dd>
275: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.106 rillig 276: <dd><dl>
1.299 rillig 277: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
278: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
279: <dt><span class="sect1"><a href="#print-PLIST">19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
280: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
281: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
282: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
283: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
284: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
285: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.106 rillig 286: </dl></dd>
1.299 rillig 287: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
288: <dd><dl>
289: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
290: <dd><dl>
291: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
292: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.106 rillig 293: </dl></dd>
1.299 rillig 294: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.106 rillig 295: <dd><dl>
1.299 rillig 296: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
297: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
298: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
299: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
300: </dl></dd>
301: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
302: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">20.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
303: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
304: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
305: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
306: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
307: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">20.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
1.267 rillig 308: </dl></dd>
309: <dt><span class="chapter"><a href="#fixes">21. Making your package work</a></span></dt>
310: <dd><dl>
311: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
312: <dd><dl>
313: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">21.1.1. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
314: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
315: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
316: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
317: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
318: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
319: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
320: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
321: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
322: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
323: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
324: </dl></dd>
325: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
326: <dd><dl>
327: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
328: <dt><span class="sect2"><a href="#modified-distfiles-same-name">21.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
329: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
330: </dl></dd>
331: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
332: <dd><dl>
333: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
334: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
335: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.338 nia 336: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.267 rillig 337: </dl></dd>
338: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
339: <dd><dl>
340: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
341: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.320 wiz 342: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.338 nia 343: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
344: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
345: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
346: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.267 rillig 347: </dl></dd>
348: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
349: <dd><dl>
350: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
351: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.287 rillig 352: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
353: <dt><span class="sect2"><a href="#undefined-reference">21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
354: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.267 rillig 355: </dl></dd>
356: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
357: <dd><dl>
358: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
359: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
360: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
361: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
362: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.318 nia 363: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.267 rillig 364: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
365: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.318 nia 366: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
367: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
368: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
369: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
370: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
371: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
372: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.87 wiz 373: emulation</a></span></dt>
1.318 nia 374: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
375: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.77 rillig 376: </dl></dd>
1.267 rillig 377: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.77 rillig 378: </dl></dd>
1.299 rillig 379: <dt><span class="chapter"><a href="#gnome">22. GNOME packaging and porting</a></span></dt>
380: <dd><dl>
381: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
382: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
383: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
384: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
385: </dl></dd>
1.267 rillig 386: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.77 rillig 387: <dd><dl>
1.267 rillig 388: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
389: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
390: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
391: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
392: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
393: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
394: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
395: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
396: </dl></dd>
397: <dt><span class="chapter"><a href="#devfaq">24. Frequently Asked Questions</a></span></dt>
1.75 rillig 398: </dl></dd>
399: <dt><span class="part"><a href="#infrastructure">III. The pkgsrc infrastructure internals</a></span></dt>
400: <dd><dl>
1.299 rillig 401: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.75 rillig 402: <dd><dl>
1.299 rillig 403: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
404: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
405: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.81 rillig 406: <dd><dl>
1.299 rillig 407: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
408: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.81 rillig 409: </dl></dd>
1.299 rillig 410: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
411: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.75 rillig 412: <dd><dl>
1.299 rillig 413: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
414: <dt><span class="sect2"><a href="#infr.design.intf.action">25.5.2. Actions taken on behalf of parameters</a></span></dt>
1.75 rillig 415: </dl></dd>
1.299 rillig 416: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.75 rillig 417: <dd><dl>
1.299 rillig 418: <dt><span class="sect2"><a href="#infr.order.prefs">25.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
419: <dt><span class="sect2"><a href="#infr.order.pkg">25.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.75 rillig 420: </dl></dd>
421: </dl></dd>
1.299 rillig 422: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.75 rillig 423: <dd><dl>
1.299 rillig 424: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
425: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.75 rillig 426: <dd><dl>
1.299 rillig 427: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
428: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.75 rillig 429: </dl></dd>
430: </dl></dd>
1.299 rillig 431: <dt><span class="chapter"><a href="#porting">27. Porting pkgsrc</a></span></dt>
432: <dd><dl><dt><span class="sect1"><a href="#porting.opsys">27.1. Porting pkgsrc to a new operating system</a></span></dt></dl></dd>
1.75 rillig 433: </dl></dd>
434: <dt><span class="appendix"><a href="#examples">A. A simple example package: bison</a></span></dt>
435: <dd><dl>
436: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
437: <dd><dl>
438: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
439: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
440: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.287 rillig 441: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.75 rillig 442: </dl></dd>
443: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
444: </dl></dd>
1.322 leot 445: <dt><span class="appendix"><a href="#hardening">B. Security hardening</a></span></dt>
1.75 rillig 446: <dd><dl>
1.322 leot 447: <dt><span class="sect1"><a href="#hardening.mechanisms">B.1. Mechanisms</a></span></dt>
448: <dd><dl>
449: <dt><span class="sect2"><a href="#hardening.mechanisms.enabled">B.1.1. Enabled by default</a></span></dt>
450: <dt><span class="sect2"><a href="#hardening.mechanisms.disabled">B.1.2. Not enabled by default</a></span></dt>
451: </dl></dd>
452: <dt><span class="sect1"><a href="#hardening.caveats">B.2. Caveats</a></span></dt>
453: <dd><dl>
454: <dt><span class="sect2"><a href="#hardening.caveats.pie">B.2.1. Problems with PKGSRC_MKPIE</a></span></dt>
455: <dt><span class="sect2"><a href="#hardening.caveats.fortify">B.2.2. Problems with PKGSRC_USE_FORTIFY</a></span></dt>
456: <dt><span class="sect2"><a href="#hardening.caveats.relro">B.2.3. Problems with PKGSRC_USE_RELRO</a></span></dt>
457: <dt><span class="sect2"><a href="#hardening.caveats.ssp">B.2.4. Problems with PKGSRC_USE_SSP</a></span></dt>
458: </dl></dd>
459: <dt><span class="sect1"><a href="#hardening.audit">B.3. Auditing the system</a></span></dt>
460: <dd><dl>
461: <dt><span class="sect2"><a href="#hardening.audit.pie">B.3.1. Checking for PIE</a></span></dt>
462: <dt><span class="sect2"><a href="#hardening.audit.relropartial">B.3.2. Checking for partial RELRO</a></span></dt>
463: <dt><span class="sect2"><a href="#hardening.audit.relrofull">B.3.3. Checking for full RELRO</a></span></dt>
464: <dt><span class="sect2"><a href="#hardening.audit.ssp">B.3.4. Checking for SSP</a></span></dt>
465: </dl></dd>
466: </dl></dd>
467: <dt><span class="appendix"><a href="#logs">C. Build logs</a></span></dt>
468: <dd><dl>
469: <dt><span class="sect1"><a href="#logs.building">C.1. Building figlet</a></span></dt>
470: <dt><span class="sect1"><a href="#logs.package">C.2. Packaging figlet</a></span></dt>
1.75 rillig 471: </dl></dd>
1.322 leot 472: <dt><span class="appendix"><a href="#ftp-layout">D. Directory layout of the pkgsrc FTP server</a></span></dt>
1.76 rillig 473: <dd><dl>
1.322 leot 474: <dt><span class="sect1"><a href="#ftp-distfiles">D.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
475: <dt><span class="sect1"><a href="#ftp-misc">D.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
476: <dt><span class="sect1"><a href="#ftp-packages">D.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
477: <dt><span class="sect1"><a href="#ftp-reports">D.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
478: <dt><span class="sect1"><a href="#ftp-source">D.5. <code class="filename">current</code>,
1.261 leot 479: <code class="filename">stable</code>,
1.128 wiz 480: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.76 rillig 481: source packages</a></span></dt>
482: </dl></dd>
1.322 leot 483: <dt><span class="appendix"><a href="#help-topics">E. Help topics</a></span></dt>
484: <dt><span class="appendix"><a href="#editing">F. Editing guidelines for the pkgsrc guide</a></span></dt>
1.75 rillig 485: <dd><dl>
1.322 leot 486: <dt><span class="sect1"><a href="#targets">F.1. Make targets</a></span></dt>
487: <dt><span class="sect1"><a href="#procedure">F.2. Procedure</a></span></dt>
1.75 rillig 488: </dl></dd>
489: </dl>
490: </div>
1.82 rillig 491: <div class="list-of-tables">
492: <p><b>List of Tables</b></p>
493: <dl>
494: <dt>1.1. <a href="#supported-platforms">Platforms supported by pkgsrc</a>
495: </dt>
1.299 rillig 496: <dt>12.1. <a href="#patch-examples">Patching examples</a>
1.85 jmmv 497: </dt>
1.299 rillig 498: <dt>22.1. <a href="#plist-handling">PLIST handling for GNOME packages</a>
1.85 jmmv 499: </dt>
1.82 rillig 500: </dl>
501: </div>
1.148 asau 502: <div class="chapter">
503: <div class="titlepage"><div><div><h1 class="title">
504: <a name="introduction"></a>Chapter 1. What is pkgsrc?</h1></div></div></div>
1.75 rillig 505: <div class="toc">
506: <p><b>Table of Contents</b></p>
1.210 leot 507: <dl class="toc">
1.75 rillig 508: <dt><span class="sect1"><a href="#introduction-section">1.1. Introduction</a></span></dt>
1.82 rillig 509: <dd><dl>
510: <dt><span class="sect2"><a href="#why-pkgsrc">1.1.1. Why pkgsrc?</a></span></dt>
511: <dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt>
512: </dl></dd>
1.75 rillig 513: <dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt>
514: <dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt>
1.88 wiz 515: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
1.75 rillig 516: <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
517: </dl>
518: </div>
1.148 asau 519: <div class="sect1">
1.75 rillig 520: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
521: <a name="introduction-section"></a>1.1. Introduction</h2></div></div></div>
1.82 rillig 522: <p>There is a lot of software freely available for Unix-based
523: systems, which is usually available in form of the source code. Before
524: such software can be used, it needs to be configured to the local
525: system, compiled and installed, and this is exactly what The NetBSD
526: Packages Collection (pkgsrc) does. pkgsrc also has some basic commands
527: to handle binary packages, so that not every user has to build the
528: packages for himself, which is a time-costly task.</p>
1.75 rillig 529: <p>pkgsrc currently contains several thousand packages,
530: including:</p>
1.148 asau 531: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 532: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/index.html" target="_top"><code class="filename">www/apache24</code></a> - The Apache
1.75 rillig 533: web server</p></li>
1.322 leot 534: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/index.html" target="_top"><code class="filename">www/firefox</code></a> - The Firefox
1.75 rillig 535: web browser</p></li>
1.322 leot 536: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/index.html" target="_top"><code class="filename">meta-pkgs/gnome</code></a> - The GNOME
1.75 rillig 537: Desktop Environment</p></li>
1.322 leot 538: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/index.html" target="_top"><code class="filename">meta-pkgs/kde4</code></a> - The K
1.75 rillig 539: Desktop Environment</p></li>
540: </ul></div>
1.219 rillig 541: <p>… just to name a few.</p>
1.75 rillig 542: <p>pkgsrc has built-in support for handling varying dependencies,
543: such as pthreads and X11, and extended features such as IPv6 support on
544: a range of platforms.</p>
1.148 asau 545: <div class="sect2">
1.82 rillig 546: <div class="titlepage"><div><div><h3 class="title">
547: <a name="why-pkgsrc"></a>1.1.1. Why pkgsrc?</h3></div></div></div>
548: <p>
549: pkgsrc provides the following key features:
550: </p>
1.148 asau 551: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 552: <li class="listitem"><p>Easy building of software from source as well as the creation
1.82 rillig 553: and installation of binary packages. The source and latest
554: patches are retrieved from a master or mirror download site, checksum
555: verified, then built on your system. Support for binary-only
556: distributions is available for both native platforms and NetBSD
557: emulated platforms.</p></li>
1.128 wiz 558: <li class="listitem"><p>All packages are installed in a consistent directory tree,
1.82 rillig 559: including binaries, libraries, man pages and other
560: documentation.</p></li>
1.214 sevan 561: <li class="listitem"><p>Tracking of package dependencies automatically, including when
562: performing updates, to ensure required packages are installed. The
563: configuration files of various packages are handled automatically during
564: updates, so local changes are preserved.</p></li>
1.128 wiz 565: <li class="listitem"><p>Like NetBSD, pkgsrc is designed with portability in mind and
1.82 rillig 566: consists of highly portable code. This allows the greatest speed of
1.132 spz 567: development when porting to a new platform. This portability also
1.82 rillig 568: ensures that pkgsrc is <span class="emphasis"><em>consistent across all
569: platforms</em></span>.</p></li>
1.128 wiz 570: <li class="listitem"><p>The installation prefix, acceptable software licenses,
1.82 rillig 571: international encryption requirements and build-time options for a
572: large number of packages are all set in a simple, central
573: configuration file.</p></li>
1.128 wiz 574: <li class="listitem"><p>The entire source (not including the distribution files) is
1.82 rillig 575: freely available under a BSD license, so you may extend and adapt
576: pkgsrc to your needs. Support for local packages and patches is
577: available right out of the box, so you can configure it specifically
578: for your environment.</p></li>
579: </ul></div>
1.91 rillig 580: <p>The following principles are basic to pkgsrc:</p>
1.148 asau 581: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 582: <li class="listitem"><p><span class="quote">“<span class="quote">It should only work if it's right.</span>”</span>
1.126 jakllsch 583: — That means, if a package contains bugs, it's better to find
1.91 rillig 584: them and to complain about them rather than to just install the package
585: and hope that it works. There are numerous checks in pkgsrc that try to
1.322 leot 586: find such bugs: static analysis tools (<a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/index.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>), build-time checks (portability
1.91 rillig 587: of shell scripts), and post-installation checks (installed files,
588: references to shared libraries, script interpreters).</p></li>
1.128 wiz 589: <li class="listitem"><p><span class="quote">“<span class="quote">If it works, it should work everywhere</span>”</span>
1.126 jakllsch 590: — Like NetBSD has been ported to many hardware architectures,
1.91 rillig 591: pkgsrc has been ported to many operating systems. Care is taken that
592: packages behave the same on all platforms.</p></li>
593: </ul></div>
1.82 rillig 594: </div>
1.148 asau 595: <div class="sect2">
1.82 rillig 596: <div class="titlepage"><div><div><h3 class="title">
597: <a name="intro.platforms"></a>1.1.2. Supported platforms</h3></div></div></div>
598: <p>pkgsrc consists of both a source distribution and a binary
599: distribution for these operating systems. After retrieving the required
600: source or binaries, you can be up and running with pkgsrc in just
601: minutes!</p>
1.75 rillig 602: <p>pkgsrc was derived from FreeBSD's ports system, and
603: initially developed for NetBSD only. Since then, pkgsrc has
604: grown a lot, and now supports the following platforms:</p>
1.82 rillig 605: <div class="table">
606: <a name="supported-platforms"></a><p class="title"><b>Table 1.1. Platforms supported by pkgsrc</b></p>
1.216 tnn 607: <div class="table-contents"><table class="table" summary="Platforms supported by pkgsrc" border="1">
1.82 rillig 608: <colgroup>
609: <col>
610: <col>
1.202 sevan 611: <col>
1.82 rillig 612: </colgroup>
613: <thead><tr>
614: <th>Platform</th>
615: <th>Date Support Added</th>
1.202 sevan 616: <th>Notes</th>
1.82 rillig 617: </tr></thead>
618: <tbody>
619: <tr>
1.289 leot 620: <td><a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a></td>
1.82 rillig 621: <td align="center">Aug 1997</td>
1.202 sevan 622: <td class="auto-generated"> </td>
1.82 rillig 623: </tr>
624: <tr>
1.110 hubertf 625: <td><a class="ulink" href="http://wwws.sun.com/software/solaris/" target="_top">Solaris</a></td>
1.82 rillig 626: <td align="center">Mar 1999</td>
1.264 sevan 627: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Solaris" target="_top">README.Solaris</a></td>
1.82 rillig 628: </tr>
629: <tr>
1.289 leot 630: <td><a class="ulink" href="https://www.kernel.org/" target="_top">Linux</a></td>
1.82 rillig 631: <td align="center">Jun 1999</td>
1.264 sevan 632: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Linux" target="_top">README.Linux</a></td>
1.82 rillig 633: </tr>
634: <tr>
635: <td>
1.230 sevan 636: <a class="ulink" href="https://developer.apple.com/macos/" target="_top">Darwin / Mac OS X / OS X / macOS</a>
1.82 rillig 637: </td>
638: <td align="center">Oct 2001</td>
1.305 bacon 639: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.macOS" target="_top">README.macOS</a></td>
1.82 rillig 640: </tr>
641: <tr>
1.289 leot 642: <td><a class="ulink" href="https://www.freebsd.org/" target="_top">FreeBSD</a></td>
1.82 rillig 643: <td align="center">Nov 2002</td>
1.264 sevan 644: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.FreeBSD" target="_top">README.FreeBSD</a></td>
1.82 rillig 645: </tr>
646: <tr>
1.289 leot 647: <td><a class="ulink" href="https://www.openbsd.org/" target="_top">OpenBSD</a></td>
1.82 rillig 648: <td align="center">Nov 2002</td>
1.264 sevan 649: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OpenBSD" target="_top">README.OpenBSD</a></td>
1.82 rillig 650: </tr>
651: <tr>
1.289 leot 652: <td><a class="ulink" href="https://www.sgi.com/software/irix/" target="_top">IRIX</a></td>
1.82 rillig 653: <td align="center">Dec 2002</td>
1.202 sevan 654: <td>
1.264 sevan 655: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX" target="_top">README.IRIX</a>
656: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX5.3" target="_top">README.IRIX5.3</a>
1.202 sevan 657: </td>
1.82 rillig 658: </tr>
659: <tr>
660: <td>BSD/OS</td>
661: <td align="center">Dec 2003</td>
1.202 sevan 662: <td class="auto-generated"> </td>
1.82 rillig 663: </tr>
664: <tr>
1.289 leot 665: <td><a class="ulink" href="https://www-1.ibm.com/servers/aix/" target="_top">AIX</a></td>
1.82 rillig 666: <td align="center">Dec 2003</td>
1.264 sevan 667: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.AIX" target="_top">README.AIX</a></td>
1.82 rillig 668: </tr>
669: <tr>
670: <td>
1.289 leot 671: <a class="ulink" href="https://www.microsoft.com/windows/sfu/" target="_top">Interix</a>
1.82 rillig 672: (Microsoft Windows Services for Unix)
673: </td>
674: <td align="center">Mar 2004</td>
1.264 sevan 675: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Interix" target="_top">README.Interix</a></td>
1.82 rillig 676: </tr>
677: <tr>
1.289 leot 678: <td><a class="ulink" href="https://www.dragonflybsd.org/" target="_top">DragonFlyBSD</a></td>
1.82 rillig 679: <td align="center">Oct 2004</td>
1.202 sevan 680: <td class="auto-generated"> </td>
1.82 rillig 681: </tr>
682: <tr>
1.110 hubertf 683: <td><a class="ulink" href="http://www.tru64.org/" target="_top">OSF/1</a></td>
1.82 rillig 684: <td align="center">Nov 2004</td>
1.264 sevan 685: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OSF1" target="_top">README.OSF1</a></td>
1.82 rillig 686: </tr>
1.98 wiz 687: <tr>
1.289 leot 688: <td><a class="ulink" href="https://www.hp.com/products1/unix/" target="_top">HP-UX</a></td>
1.98 wiz 689: <td align="center">Apr 2007</td>
1.264 sevan 690: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.HPUX" target="_top">README.HPUX</a></td>
1.98 wiz 691: </tr>
1.128 wiz 692: <tr>
1.289 leot 693: <td><a class="ulink" href="https://www.haiku-os.org/" target="_top">Haiku</a></td>
1.128 wiz 694: <td align="center">Sep 2010</td>
1.264 sevan 695: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Haiku" target="_top">README.Haiku</a></td>
1.128 wiz 696: </tr>
1.151 obache 697: <tr>
1.289 leot 698: <td><a class="ulink" href="https://www.mirbsd.org/" target="_top">MirBSD</a></td>
1.163 bsiegert 699: <td align="center">Jan 2011</td>
1.202 sevan 700: <td class="auto-generated"> </td>
1.151 obache 701: </tr>
702: <tr>
1.289 leot 703: <td><a class="ulink" href="https://www.minix3.org/" target="_top">Minix3</a></td>
1.151 obache 704: <td align="center">Nov 2011</td>
1.264 sevan 705: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Minix3" target="_top">README.Minix3</a></td>
1.151 obache 706: </tr>
707: <tr>
1.289 leot 708: <td><a class="ulink" href="https://cygwin.com/" target="_top">Cygwin</a></td>
1.151 obache 709: <td align="center">Mar 2013</td>
1.264 sevan 710: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Cygwin" target="_top">README.Cygwin</a></td>
1.151 obache 711: </tr>
1.166 jnemeth 712: <tr>
1.289 leot 713: <td><a class="ulink" href="https://www.debian.org/ports/kfreebsd-gnu/" target="_top">GNU/kFreeBSD</a></td>
1.166 jnemeth 714: <td align="center">Jul 2013</td>
1.264 sevan 715: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.GNUkFreeBSD" target="_top">README.GNUkFreeBSD</a></td>
1.166 jnemeth 716: </tr>
1.214 sevan 717: <tr>
1.289 leot 718: <td><a class="ulink" href="https://www.bitrig.org/" target="_top">Bitrig</a></td>
1.214 sevan 719: <td align="center">Jun 2014</td>
1.264 sevan 720: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Bitrig" target="_top">README.Bitrig</a></td>
1.214 sevan 721: </tr>
1.82 rillig 722: </tbody>
1.91 rillig 723: </table></div>
1.82 rillig 724: </div>
1.91 rillig 725: <br class="table-break">
1.82 rillig 726: </div>
1.75 rillig 727: </div>
1.148 asau 728: <div class="sect1">
1.75 rillig 729: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
730: <a name="overview"></a>1.2. Overview</h2></div></div></div>
731: <p>This document is divided into three parts. The first,
1.110 hubertf 732: <a class="link" href="#users-guide" title="Part I. The pkgsrc user's guide">The pkgsrc user's guide</a>,
1.75 rillig 733: describes how one can use one of the packages in the Package
734: Collection, either by installing a precompiled binary package,
1.93 rillig 735: or by building one's own copy using the NetBSD package system.
1.110 hubertf 736: The second part, <a class="link" href="#developers-guide" title="Part II. The pkgsrc developer's guide">The pkgsrc developer's guide</a>, explains how to prepare a
1.75 rillig 737: package so it can be easily built by other NetBSD users without
738: knowing about the package's building details. The third part,
1.110 hubertf 739: <a class="link" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">The pkgsrc infrastructure internals</a>
1.75 rillig 740: is intended for those who want to understand how pkgsrc is
741: implemented.</p>
742: <p>This document is available in various formats:
1.110 hubertf 743: <span class="simplelist"><a class="ulink" href="index.html" target="_top">HTML</a>, <a class="ulink" href="pkgsrc.pdf" target="_top">PDF</a>, <a class="ulink" href="pkgsrc.ps" target="_top">PS</a>, <a class="ulink" href="pkgsrc.txt" target="_top">TXT</a></span>.</p>
1.75 rillig 744: </div>
1.148 asau 745: <div class="sect1">
1.75 rillig 746: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
747: <a name="terminology"></a>1.3. Terminology</h2></div></div></div>
1.128 wiz 748: <p>There has been a lot of talk about <span class="quote">“<span class="quote">ports</span>”</span>,
749: <span class="quote">“<span class="quote">packages</span>”</span>, etc. so far. Here is a description of all the
1.75 rillig 750: terminology used within this document.</p>
1.148 asau 751: <div class="variablelist"><dl class="variablelist">
1.75 rillig 752: <dt><span class="term">Package</span></dt>
753: <dd><p>A set of files and building instructions
754: that describe what's necessary
755: to build a certain piece of software using
756: pkgsrc. Packages are traditionally stored under
1.236 wiz 757: <code class="filename">/usr/pkgsrc</code>,
758: but may be stored in any location,
759: referred to as <code class="varname">PKGSRCDIR</code>.</p></dd>
1.75 rillig 760: <dt><span class="term">The NetBSD package system</span></dt>
1.128 wiz 761: <dd><p>This is the former name of <span class="quote">“<span class="quote">pkgsrc</span>”</span>. It
1.87 wiz 762: is part of the NetBSD operating system and can be bootstrapped
763: to run on non-NetBSD operating systems as well. It handles
764: building (compiling), installing, and removing of
765: packages.</p></dd>
1.75 rillig 766: <dt><span class="term">Distfile</span></dt>
767: <dd><p>This term describes the file or files that are
768: provided by the author of the piece of software to
769: distribute his work. All the changes necessary to build on
770: NetBSD are reflected in the corresponding package. Usually
771: the distfile is in the form of a compressed tar-archive,
772: but other types are possible, too. Distfiles are usually
773: stored below
1.76 rillig 774: <code class="filename">/usr/pkgsrc/distfiles</code>.</p></dd>
1.75 rillig 775: <dt><span class="term">Port</span></dt>
776: <dd><p>This is the term used by FreeBSD and OpenBSD people
777: for what we call a package.
1.128 wiz 778: In NetBSD terminology, <span class="quote">“<span class="quote">port</span>”</span> refers to a different
1.75 rillig 779: architecture.</p></dd>
780: <dt><span class="term">Precompiled/binary package</span></dt>
781: <dd>
782: <p>A set of binaries built with pkgsrc from a distfile
1.76 rillig 783: and stuffed together in a single <code class="filename">.tgz</code>
1.75 rillig 784: file so it can be installed on machines of the same
785: machine architecture without the need to
786: recompile. Packages are usually generated in
1.76 rillig 787: <code class="filename">/usr/pkgsrc/packages</code>; there is also
1.132 spz 788: an archive on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/" target="_top">ftp.NetBSD.org</a>.</p>
1.128 wiz 789: <p>Sometimes, this is referred to by the term <span class="quote">“<span class="quote">package</span>”</span> too,
1.75 rillig 790: especially in the context of precompiled packages.</p>
791: </dd>
792: <dt><span class="term">Program</span></dt>
1.88 wiz 793: <dd><p>The piece of software to be installed which will be
794: constructed from all the files in the distfile by the
795: actions defined in the corresponding package.</p></dd>
1.75 rillig 796: </dl></div>
1.148 asau 797: <div class="sect2">
1.75 rillig 798: <div class="titlepage"><div><div><h3 class="title">
1.88 wiz 799: <a name="term.roles"></a>1.3.1. Roles involved in pkgsrc</h3></div></div></div>
1.148 asau 800: <div class="variablelist"><dl class="variablelist">
1.75 rillig 801: <dt><span class="term">pkgsrc users</span></dt>
802: <dd>
803: <p>The
804: pkgsrc users are people who use the packages provided by pkgsrc.
805: Typically they are system administrators. The people using the
1.128 wiz 806: software that is inside the packages (maybe called <span class="quote">“<span class="quote">end
807: users</span>”</span>) are not covered by the pkgsrc guide.</p>
1.75 rillig 808: <p>There are two kinds of pkgsrc users: Some only want to
809: install pre-built binary packages. Others build the pkgsrc
810: packages from source, either for installing them directly or for
1.110 hubertf 811: building binary packages themselves. For pkgsrc users <a class="xref" href="#users-guide" title="Part I. The pkgsrc user's guide">Part I, “The pkgsrc user's guide”</a> should provide all necessary
1.75 rillig 812: documentation.</p>
813: </dd>
814: <dt><span class="term">package maintainers</span></dt>
815: <dd><p>A
1.110 hubertf 816: package maintainer creates packages as described in <a class="xref" href="#developers-guide" title="Part II. The pkgsrc developer's guide">Part II, “The pkgsrc developer's guide”</a>.</p></dd>
1.75 rillig 817: <dt><span class="term">infrastructure developers</span></dt>
818: <dd><p>These people are involved in all those files
1.76 rillig 819: that live in the <code class="filename">mk/</code> directory and below.
1.110 hubertf 820: Only these people should need to read through <a class="xref" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">Part III, “The pkgsrc infrastructure internals”</a>, though others might be curious,
1.75 rillig 821: too.</p></dd>
822: </dl></div>
823: </div>
824: </div>
1.148 asau 825: <div class="sect1">
1.75 rillig 826: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
827: <a name="typography"></a>1.4. Typography</h2></div></div></div>
828: <p>When giving examples for commands, shell prompts are used to
829: show if the command should/can be issued as root, or if
1.128 wiz 830: <span class="quote">“<span class="quote">normal</span>”</span> user privileges are sufficient. We use a
1.226 sevan 831: <code class="prompt">#</code> for root's shell prompt, a <code class="prompt">%</code> for users'
832: shell prompt, assuming they use the C-shell or tcsh and a <code class="prompt">$</code> for
833: bourne shell and derivatives.</p>
1.75 rillig 834: </div>
835: </div>
1.148 asau 836: <div class="part">
1.75 rillig 837: <div class="titlepage"><div><div><h1 class="title">
838: <a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div>
839: <div class="toc">
840: <p><b>Table of Contents</b></p>
1.210 leot 841: <dl class="toc">
1.267 rillig 842: <dt><span class="chapter"><a href="#help-user">2. Getting help</a></span></dt>
843: <dt><span class="chapter"><a href="#getting">3. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
1.75 rillig 844: <dd><dl>
1.267 rillig 845: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.75 rillig 846: <dd><dl>
1.267 rillig 847: <dt><span class="sect2"><a href="#getting-via-tar">3.1.1. As tar archive</a></span></dt>
848: <dt><span class="sect2"><a href="#getting-via-cvs">3.1.2. Via anonymous CVS</a></span></dt>
1.75 rillig 849: </dl></dd>
1.267 rillig 850: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.75 rillig 851: <dd><dl>
1.267 rillig 852: <dt><span class="sect2"><a href="#uptodate-tar">3.2.1. Via tar files</a></span></dt>
853: <dt><span class="sect2"><a href="#uptodate-cvs">3.2.2. Via CVS</a></span></dt>
1.75 rillig 854: </dl></dd>
855: </dl></dd>
1.267 rillig 856: <dt><span class="chapter"><a href="#platforms">4. Using pkgsrc on systems other than NetBSD</a></span></dt>
1.75 rillig 857: <dd><dl>
1.267 rillig 858: <dt><span class="sect1"><a href="#binarydist">4.1. Binary distribution</a></span></dt>
859: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">4.2. Bootstrapping pkgsrc</a></span></dt>
1.75 rillig 860: </dl></dd>
1.267 rillig 861: <dt><span class="chapter"><a href="#using">5. Using pkgsrc</a></span></dt>
1.75 rillig 862: <dd><dl>
1.267 rillig 863: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.75 rillig 864: <dd><dl>
1.267 rillig 865: <dt><span class="sect2"><a href="#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
866: <dt><span class="sect2"><a href="#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
1.317 nia 867: <dt><span class="sect2"><a href="#using.pkgin_update">5.1.3. Updating packages</a></span></dt>
868: <dt><span class="sect2"><a href="#using.pkg_delete">5.1.4. Deinstalling packages</a></span></dt>
869: <dt><span class="sect2"><a href="#using.pkg_info">5.1.5. Getting information about installed packages</a></span></dt>
870: <dt><span class="sect2"><a href="#vulnerabilities">5.1.6. Checking for security vulnerabilities in installed packages</a></span></dt>
871: <dt><span class="sect2"><a href="#pkg_versions">5.1.7. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
872: <dt><span class="sect2"><a href="#using.pkg_admin">5.1.8. Other administrative functions</a></span></dt>
1.75 rillig 873: </dl></dd>
1.267 rillig 874: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.75 rillig 875: <dd><dl>
1.267 rillig 876: <dt><span class="sect2"><a href="#requirements">5.2.1. Requirements</a></span></dt>
877: <dt><span class="sect2"><a href="#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
878: <dt><span class="sect2"><a href="#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.75 rillig 879: </dl></dd>
880: </dl></dd>
1.267 rillig 881: <dt><span class="chapter"><a href="#configuring">6. Configuring pkgsrc</a></span></dt>
1.75 rillig 882: <dd><dl>
1.267 rillig 883: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
884: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
885: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
886: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1.88 wiz 887: <dd><dl>
1.267 rillig 888: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
889: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
890: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.88 wiz 891: </dl></dd>
1.267 rillig 892: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
893: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.75 rillig 894: </dl></dd>
1.267 rillig 895: <dt><span class="chapter"><a href="#binary">7. Creating binary packages</a></span></dt>
1.75 rillig 896: <dd><dl>
1.267 rillig 897: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
898: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.106 rillig 899: </dl></dd>
1.267 rillig 900: <dt><span class="chapter"><a href="#bulk">8. Creating binary packages for everything in pkgsrc (bulk
1.106 rillig 901: builds)</a></span></dt>
1.75 rillig 902: <dd><dl>
1.267 rillig 903: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.295 rillig 904: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.267 rillig 905: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
906: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.293 rillig 907: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
908: <dd><dl>
1.294 rillig 909: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
910: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.296 rillig 911: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
912: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
913: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
914: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
915: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
916: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
917: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
918: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.293 rillig 919: </dl></dd>
920: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
921: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.267 rillig 922: </dl></dd>
923: <dt><span class="chapter"><a href="#files">9. Directory layout of the installed files</a></span></dt>
924: <dd><dl>
925: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
926: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
927: </dl></dd>
928: <dt><span class="chapter"><a href="#faq">10. Frequently Asked Questions</a></span></dt>
929: <dd><dl>
930: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
931: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
932: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
933: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
934: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">10.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
935: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
936: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
937: <dt><span class="sect1"><a href="#passive-ftp">10.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
938: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
939: <dt><span class="sect1"><a href="#tmac.andoc-missing">10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.128 wiz 940: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.267 rillig 941: <dt><span class="sect1"><a href="#bsd.own.mk-missing">10.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
1.336 nia 942: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.267 rillig 943: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
944: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
945: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
946: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
947: <dt><span class="sect1"><a href="#faq.rcs-conflicts">10.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</a></span></dt>
1.75 rillig 948: </dl></dd>
949: </dl>
950: </div>
1.148 asau 951: <div class="chapter">
1.75 rillig 952: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 953: <a name="help-user"></a>Chapter 2. Getting help</h2></div></div></div>
954: <p>
955: To get help when using pkgsrc, the definitive source is this
956: document, the pkgsrc guide. If you don't find anything here,
957: there are alternatives:
958: </p>
959: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
960: <li class="listitem">
961: <p>
962: The built-in pkgsrc help, which is available after bootstrapping
963: pkgsrc. Run <span class="command"><strong>bmake help topic=…</strong></span> to get
964: help for any topic, such as a variable name like
965: <code class="varname">BUILD_DEFS</code>, a make target like
966: <span class="command"><strong>do-build</strong></span>, a missing C or C++ function like
967: <span class="command"><strong>strcasecmp</strong></span> or any other topic.</p>
1.322 leot 968: <p>The available help topics are listed in <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.267 rillig 969: </li>
970: <li class="listitem"><p>
1.278 rillig 971: To see the value of a single variable, run <span class="command"><strong>bmake
972: show-var VARNAME=<em class="replaceable"><code>X</code></em></strong></span>.
973: </p></li>
974: <li class="listitem"><p>
975: To see the values of the most common variables, run
976: <span class="command"><strong>bmake show-all</strong></span>. These variables are grouped by
977: topic. To see the variables for a single topic, run
978: <span class="command"><strong>bmake
979: show-all-<em class="replaceable"><code>topic</code></em></strong></span>, for example
980: <span class="command"><strong>bmake show-all-fetch</strong></span>.
981: </p></li>
982: <li class="listitem"><p>
1.267 rillig 983: The pkgsrc-users mailing list, to which
984: <a class="ulink" href="https://www.NetBSD.org/mailinglists/#pkgsrc-users" target="_top">you
985: can subscribe</a> and then <a class="ulink" href="mailto:pkgsrc-users@NetBSD.org" target="_top">ask your
986: questions</a>.</p></li>
987: <li class="listitem"><p>The #pkgsrc IRC channel, which is accessible
988: <a class="ulink" href="https://webchat.freenode.net/" target="_top">via a web browser</a>
989: or by using a specialized chat program such as
990: <a class="ulink" href="http://xchat.org/" target="_top">XChat</a>.
991: Pick any user name and join the channel #pkgsrc.</p></li>
992: </ul></div>
993: </div>
994: <div class="chapter">
995: <div class="titlepage"><div><div><h2 class="title">
996: <a name="getting"></a>Chapter 3. Where to get pkgsrc and how to keep it up-to-date</h2></div></div></div>
1.75 rillig 997: <div class="toc">
998: <p><b>Table of Contents</b></p>
1.210 leot 999: <dl class="toc">
1.267 rillig 1000: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.75 rillig 1001: <dd><dl>
1.267 rillig 1002: <dt><span class="sect2"><a href="#getting-via-tar">3.1.1. As tar archive</a></span></dt>
1003: <dt><span class="sect2"><a href="#getting-via-cvs">3.1.2. Via anonymous CVS</a></span></dt>
1.75 rillig 1004: </dl></dd>
1.267 rillig 1005: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.75 rillig 1006: <dd><dl>
1.267 rillig 1007: <dt><span class="sect2"><a href="#uptodate-tar">3.2.1. Via tar files</a></span></dt>
1008: <dt><span class="sect2"><a href="#uptodate-cvs">3.2.2. Via CVS</a></span></dt>
1.75 rillig 1009: </dl></dd>
1010: </dl>
1011: </div>
1.91 rillig 1012: <p>Before you download and extract the files, you need to decide
1013: where you want to extract them. When using pkgsrc as root user, pkgsrc
1014: is usually installed in <code class="filename">/usr/pkgsrc</code>. You are though
1015: free to install the sources and binary packages wherever you want in
1016: your filesystem, provided that the pathname does not contain white-space
1017: or other characters that are interpreted specially by the shell and some
1018: other programs. A safe bet is to use only letters, digits, underscores
1019: and dashes.</p>
1.148 asau 1020: <div class="sect1">
1.75 rillig 1021: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1022: <a name="getting-first"></a>3.1. Getting pkgsrc for the first time</h2></div></div></div>
1.75 rillig 1023: <p>Before you download any pkgsrc files, you should decide
1024: whether you want the <span class="emphasis"><em>current</em></span> branch or the
1025: <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a
1026: quarterly basis from the current branch and only gets modified
1027: for security updates. The names of the stable branches are built
1028: from the year and the quarter, for example
1.329 leot 1029: <code class="literal">2021Q4</code>.</p>
1.75 rillig 1030: <p>The second step is to decide <span class="emphasis"><em>how</em></span> you
1.128 wiz 1031: want to download pkgsrc. You can get it as a tar file or via CVS.
1032: Both ways are described here.</p>
1.157 asau 1033: <p>Note that tar archive contains CVS working copy.
1034: Thus you can switch to using CVS at any later time.</p>
1.148 asau 1035: <div class="sect2">
1.75 rillig 1036: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1037: <a name="getting-via-tar"></a>3.1.1. As tar archive</h3></div></div></div>
1.75 rillig 1038: <p>The primary download location for all pkgsrc files is
1.264 sevan 1039: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/" target="_top">https://cdn.NetBSD.org/pub/pkgsrc/</a> or
1.157 asau 1040: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a>
1041: (it points to the same location).
1042: There are a number of subdirectories for different purposes,
1.322 leot 1043: which are described in detail in <a class="xref" href="#ftp-layout" title="Appendix D. Directory layout of the pkgsrc FTP server">Appendix D, <i>Directory layout of the pkgsrc FTP server</i></a>.</p>
1.157 asau 1044: <p>The tar archive for the current branch is in the directory
1.264 sevan 1045: <code class="filename">current</code> and is called <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.
1.230 sevan 1046: It is autogenerated weekly.</p>
1.157 asau 1047: <p>To save download time we provide bzip2- and
1048: xz-compressed archives which are published at
1.264 sevan 1049: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.bz2" target="_top"><code class="filename">pkgsrc.tar.bz2</code></a>
1.157 asau 1050: and
1.264 sevan 1051: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.xz" target="_top"><code class="filename">pkgsrc.tar.xz</code></a>
1.157 asau 1052: respectively.
1053: </p>
1054: <p>You can fetch the same files using FTP.</p>
1.329 leot 1055: <p>The tar file for the stable branch 2021Q4 is in the
1056: directory <code class="filename">pkgsrc-2021Q4</code> and is also called <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/pkgsrc-2021Q4/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p>
1.249 leot 1057: <p>To download the latest pkgsrc stable tarball, run:</p>
1.112 weinem 1058: <pre class="screen">
1.329 leot 1059: <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2021Q4/pkgsrc.tar.gz</code></strong></pre>
1.188 snj 1060: <p>If you prefer, you can also fetch it using "wget", "curl",
1.157 asau 1061: or your web browser.</p>
1.112 weinem 1062: <p>Then, extract it with:</p>
1.188 snj 1063: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre>
1.112 weinem 1064: <p>This will create the directory <code class="filename">pkgsrc/</code>
1065: in <code class="filename">/usr/</code> and all the package source will be
1066: stored under <code class="filename">/usr/pkgsrc/</code>.</p>
1067: <p>To download pkgsrc-current, run:</p>
1068: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</code></strong></pre>
1.75 rillig 1069: </div>
1.148 asau 1070: <div class="sect2">
1.75 rillig 1071: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1072: <a name="getting-via-cvs"></a>3.1.2. Via anonymous CVS</h3></div></div></div>
1.128 wiz 1073: <p>To fetch a specific pkgsrc stable branch, run:</p>
1.329 leot 1074: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-2021Q4 -P pkgsrc</code></strong>
1.128 wiz 1075: </pre>
1076: <p>This will create the directory <code class="filename">pkgsrc/</code>
1077: in your <code class="filename">/usr/</code> directory and all the package source
1078: will be stored under <code class="filename">/usr/pkgsrc/</code>.</p>
1079: <p>To fetch the pkgsrc current branch, run:</p>
1.146 wiz 1080: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong>
1.1 grant 1081: </pre>
1.289 leot 1082: <p>Refer to the <a class="ulink" href="https://www.NetBSD.org/mirrors/#anoncvs" target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p>
1.128 wiz 1083: <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable. E.g.:</p>
1.146 wiz 1084: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && env CVS_RSH=ssh cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong>
1.128 wiz 1085: </pre>
1086: <p>Refer to documentation on your command shell how to set CVS_RSH=ssh permanently.
1087: For Bourne shells, you can set it in your <code class="filename">.profile</code>
1088: or better globally in <code class="filename">/etc/profile</code>:</p>
1089: <pre class="programlisting">
1090: # set CVS remote shell command
1091: CVS_RSH=ssh
1092: export CVS_RSH
1093: </pre>
1094: <p>By default, CVS doesn't do things like most people would expect it to do.
1095: But there is a way to convince CVS, by creating a file called <code class="filename">.cvsrc</code>
1096: in your home directory and saving the following lines to it.
1097: This file will save you lots of headache and some bug reports, so we strongly recommend it.
1098: You can find an explanation of this file in the CVS documentation.</p>
1.101 rillig 1099: <pre class="programlisting">
1100: # recommended CVS configuration file from the pkgsrc guide
1.268 sevan 1101: cvs -q
1.101 rillig 1102: checkout -P
1.103 wiz 1103: update -dP
1104: diff -upN
1.101 rillig 1105: rdiff -u
1.128 wiz 1106: release -d
1.101 rillig 1107: </pre>
1.75 rillig 1108: </div>
1109: </div>
1.148 asau 1110: <div class="sect1">
1.75 rillig 1111: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1112: <a name="uptodate"></a>3.2. Keeping pkgsrc up-to-date</h2></div></div></div>
1.75 rillig 1113: <p>The preferred way to keep pkgsrc up-to-date is via CVS
1114: (which also works if you have first installed it via a tar
1115: file). It saves bandwidth and hard disk activity, compared to
1116: downloading the tar file again.</p>
1.148 asau 1117: <div class="sect2">
1.75 rillig 1118: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1119: <a name="uptodate-tar"></a>3.2.1. Via tar files</h3></div></div></div>
1.148 asau 1120: <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
1.75 rillig 1121: <h3 class="title">Warning</h3>
1.77 rillig 1122: <p>When updating from a tar file, you first need to
1123: completely remove the old pkgsrc directory. Otherwise those
1124: files that have been removed from pkgsrc in the mean time will
1125: not be removed on your local disk, resulting in inconsistencies.
1126: When removing the old files, any changes that you have done to
1127: the pkgsrc files will be lost after updating. Therefore updating
1128: via CVS is strongly recommended.</p>
1.75 rillig 1129: </div>
1.82 rillig 1130: <p>Note that by default the distfiles and the binary packages
1131: are saved in the pkgsrc tree, so don't forget to rescue them
1.188 snj 1132: before updating. You can also configure pkgsrc to store distfiles
1133: and packages in directories outside the pkgsrc tree by setting the
1.82 rillig 1134: <code class="varname">DISTDIR</code> and <code class="varname">PACKAGES</code>
1.267 rillig 1135: variables. See <a class="xref" href="#configuring" title="Chapter 6. Configuring pkgsrc">Chapter 6, <i>Configuring pkgsrc</i></a> for the details.</p>
1.75 rillig 1136: <p>To update pkgsrc from a tar file, download the tar file as
1137: explained above. Then, make sure that you have not made any
1138: changes to the files in the pkgsrc directory. Remove the pkgsrc
1139: directory and extract the new tar file. Done.</p>
1140: </div>
1.148 asau 1141: <div class="sect2">
1.75 rillig 1142: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1143: <a name="uptodate-cvs"></a>3.2.2. Via CVS</h3></div></div></div>
1.132 spz 1144: <p>To update pkgsrc via CVS, change to the <code class="filename">pkgsrc</code> directory and run cvs:</p>
1145: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && cvs update -dP</code></strong>
1146: </pre>
1147: <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable as described above. E.g.:</p>
1148: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP</code></strong>
1149: </pre>
1.148 asau 1150: <div class="sect3">
1.75 rillig 1151: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 1152: <a name="uptodate-cvs-switch"></a>3.2.2.1. Switching between different pkgsrc branches</h4></div></div></div>
1.75 rillig 1153: <p>When updating pkgsrc, the CVS program keeps track of the
1154: branch you selected. But if you, for whatever reason, want to
1155: switch from the stable branch to the current one, you can do it
1.128 wiz 1156: by adding the option <span class="quote">“<span class="quote">-A</span>”</span> after the
1157: <span class="quote">“<span class="quote">update</span>”</span> keyword. To switch from the current branch
1.75 rillig 1158: back to the stable branch, add the
1.329 leot 1159: <span class="quote">“<span class="quote">-rpkgsrc-2021Q4</span>”</span> option.</p>
1.75 rillig 1160: </div>
1.148 asau 1161: <div class="sect3">
1.75 rillig 1162: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 1163: <a name="uptodate-cvs-changes"></a>3.2.2.2. What happens to my changes when updating?</h4></div></div></div>
1.75 rillig 1164: <p>When you update pkgsrc, the CVS program will only touch
1165: those files that are registered in the CVS repository. That
1166: means that any packages that you created on your own will stay
1167: unmodified. If you change files that are managed by CVS, later
1168: updates will try to merge your changes with those that have been
1169: done by others. See the CVS manual, chapter
1.128 wiz 1170: <span class="quote">“<span class="quote">update</span>”</span> for details.</p>
1.75 rillig 1171: </div>
1172: </div>
1173: </div>
1174: </div>
1.148 asau 1175: <div class="chapter">
1.75 rillig 1176: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 1177: <a name="platforms"></a>Chapter 4. Using pkgsrc on systems other than NetBSD</h2></div></div></div>
1.75 rillig 1178: <div class="toc">
1179: <p><b>Table of Contents</b></p>
1.210 leot 1180: <dl class="toc">
1.267 rillig 1181: <dt><span class="sect1"><a href="#binarydist">4.1. Binary distribution</a></span></dt>
1182: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">4.2. Bootstrapping pkgsrc</a></span></dt>
1.75 rillig 1183: </dl>
1184: </div>
1.148 asau 1185: <div class="sect1">
1.75 rillig 1186: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1187: <a name="binarydist"></a>4.1. Binary distribution</h2></div></div></div>
1188: <p>See <a class="xref" href="#using-pkg" title="5.1. Using binary packages">Section 5.1, “Using binary packages”</a>.</p>
1.82 rillig 1189: </div>
1.148 asau 1190: <div class="sect1">
1.82 rillig 1191: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1192: <a name="bootstrapping-pkgsrc"></a>4.2. Bootstrapping pkgsrc</h2></div></div></div>
1.149 asau 1193: <p>pkgsrc can be bootstrapped for use in two different modes:
1194: privileged and unprivileged one. In unprivileged mode in contrast
1.150 asau 1195: to privileged one all programs are installed under one particular user
1.149 asau 1196: and cannot utilise privileged operations (packages don't create
1197: special users and all special file permissions like setuid are ignored).
1198: </p>
1.82 rillig 1199: <p>Installing the bootstrap kit from source should be as simple as:</p>
1.75 rillig 1200: <pre class="screen">
1.167 asau 1201: <code class="prompt">#</code> <strong class="userinput"><code>env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong>
1.75 rillig 1202: <code class="prompt">#</code> <strong class="userinput"><code>cd pkgsrc/bootstrap</code></strong>
1.87 wiz 1203: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap</code></strong>
1204: </pre>
1.149 asau 1205: <p>To bootstrap in unprivileged mode pass <span class="quote">“<span class="quote">--unprivileged</span>”</span> flag to <span class="command"><strong>bootstrap</strong></span></p>
1206: <p>By default, in privileged mode pkgsrc uses
1207: <code class="filename">/usr/pkg</code> for <span class="emphasis"><em>prefix</em></span>
1208: where programs will be installed in,
1.230 sevan 1209: and <code class="filename">/usr/pkg/pkgdb</code> for the package database
1.149 asau 1210: directory where pkgsrc will do its internal bookkeeping,
1211: <code class="filename">/var</code> is used as <span class="emphasis"><em>varbase</em></span>,
1212: where packages install their persistent data.
1213: In unprivileged mode pkgsrc uses
1214: <code class="filename">~/pkg</code> for <span class="emphasis"><em>prefix</em></span>,
1.230 sevan 1215: <code class="filename">~/pkg/pkgdb</code> for the package database,
1.149 asau 1216: and <code class="filename">~/pkg/var</code> for <span class="emphasis"><em>varbase</em></span>.
1217: </p>
1218: <p>You can change default layout using command-line arguments.
1219: Run <span class="quote">“<span class="quote">./bootstrap --help</span>”</span> to get details.
1220: </p>
1.148 asau 1221: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.75 rillig 1222: <h3 class="title">Note</h3>
1.110 hubertf 1223: <p>The bootstrap installs a <span class="command"><strong>bmake</strong></span> tool.
1224: Use this <span class="command"><strong>bmake</strong></span> when building via pkgsrc.
1225: For examples in this guide, use <span class="command"><strong>bmake</strong></span>
1.128 wiz 1226: instead of <span class="quote">“<span class="quote">make</span>”</span>.</p>
1.75 rillig 1227: </div>
1.149 asau 1228: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1229: <h3 class="title">Note</h3>
1230: <p>It is possible to bootstrap multiple instances of pkgsrc
1231: using non-intersecting directories. Use <span class="command"><strong>bmake</strong></span>
1232: corresponding to the installation you're working with to build
1233: and install packages.
1234: </p>
1235: </div>
1.75 rillig 1236: </div>
1237: </div>
1.148 asau 1238: <div class="chapter">
1.75 rillig 1239: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 1240: <a name="using"></a>Chapter 5. Using pkgsrc</h2></div></div></div>
1.75 rillig 1241: <div class="toc">
1242: <p><b>Table of Contents</b></p>
1.210 leot 1243: <dl class="toc">
1.267 rillig 1244: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.75 rillig 1245: <dd><dl>
1.267 rillig 1246: <dt><span class="sect2"><a href="#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
1247: <dt><span class="sect2"><a href="#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
1.317 nia 1248: <dt><span class="sect2"><a href="#using.pkgin_update">5.1.3. Updating packages</a></span></dt>
1249: <dt><span class="sect2"><a href="#using.pkg_delete">5.1.4. Deinstalling packages</a></span></dt>
1250: <dt><span class="sect2"><a href="#using.pkg_info">5.1.5. Getting information about installed packages</a></span></dt>
1251: <dt><span class="sect2"><a href="#vulnerabilities">5.1.6. Checking for security vulnerabilities in installed packages</a></span></dt>
1252: <dt><span class="sect2"><a href="#pkg_versions">5.1.7. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
1253: <dt><span class="sect2"><a href="#using.pkg_admin">5.1.8. Other administrative functions</a></span></dt>
1.267 rillig 1254: </dl></dd>
1255: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1256: <dd><dl>
1257: <dt><span class="sect2"><a href="#requirements">5.2.1. Requirements</a></span></dt>
1258: <dt><span class="sect2"><a href="#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
1259: <dt><span class="sect2"><a href="#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.75 rillig 1260: </dl></dd>
1261: </dl>
1262: </div>
1263: <p>Basically, there are two ways of using pkgsrc. The first
1.88 wiz 1264: is to only install the package tools and to use binary packages
1.128 wiz 1265: that someone else has prepared. This is the <span class="quote">“<span class="quote">pkg</span>”</span>
1266: in pkgsrc. The second way is to install the <span class="quote">“<span class="quote">src</span>”</span>
1.88 wiz 1267: of pkgsrc, too. Then you are able to build your own packages,
1268: and you can still use binary packages from someone else.</p>
1.148 asau 1269: <div class="sect1">
1.75 rillig 1270: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1271: <a name="using-pkg"></a>5.1. Using binary packages</h2></div></div></div>
1.317 nia 1272: <p>On the <a class="ulink" href="https://cdn.NetBSD.org/" target="_top">cdn.NetBSD.org</a>
1.264 sevan 1273: site and mirrors, there are collections of binary packages,
1.109 rillig 1274: ready to be installed. These binary packages have been built using the
1275: default settings for the directories, that is:</p>
1.148 asau 1276: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 1277: <li class="listitem"><p><code class="filename">/usr/pkg</code> for <code class="varname">LOCALBASE</code>, where most of the files are installed,</p></li>
1278: <li class="listitem"><p><code class="filename">/usr/pkg/etc</code> for configuration files,</p></li>
1279: <li class="listitem"><p><code class="filename">/var</code> for <code class="varname">VARBASE</code>, where those files are installed that may change after installation.</p></li>
1.109 rillig 1280: </ul></div>
1281: <p>If you cannot use these directories for whatever reasons (maybe
1282: because you're not root), you cannot use these binary packages, but
1.267 rillig 1283: have to build the packages yourself, which is explained in <a class="xref" href="#bootstrapping-pkgsrc" title="4.2. Bootstrapping pkgsrc">Section 4.2, “Bootstrapping pkgsrc”</a>.</p>
1.148 asau 1284: <div class="sect2">
1.75 rillig 1285: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1286: <a name="finding-binary-packages"></a>5.1.1. Finding binary packages</h3></div></div></div>
1.105 weinem 1287: <p>To install binary packages, you first need to know from where
1288: to get them. The first place where you should look is on the main
1.317 nia 1289: pkgsrc CDN in the directory <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/" target="_top"><code class="filename">/pub/pkgsrc/packages</code></a>.</p>
1.105 weinem 1290: <p>This directory contains binary packages for multiple
1291: platforms. First, select your operating system. (Ignore the
1292: directories with version numbers attached to it, they just exist for
1293: legacy reasons.) Then, select your hardware architecture, and in the
1.128 wiz 1294: third step, the OS version and the <span class="quote">“<span class="quote">version</span>”</span> of pkgsrc.</p>
1.109 rillig 1295: <p>In this directory, you often find a file called
1296: <code class="filename">bootstrap.tar.gz</code> which contains the package
1297: management tools. If the file is missing, it is likely that your
1298: operating system already provides those tools. Download the file and
1299: extract it in the <code class="filename">/</code> directory. It will create
1300: the directories <code class="filename">/usr/pkg</code> (containing the tools
1.230 sevan 1301: for managing binary packages and the database of installed packages).</p>
1.75 rillig 1302: </div>
1.148 asau 1303: <div class="sect2">
1.75 rillig 1304: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1305: <a name="installing-binary-packages"></a>5.1.2. Installing binary packages</h3></div></div></div>
1.109 rillig 1306: <p>In the directory from the last section, there is a
1.196 wiz 1307: subdirectory called <code class="filename">All/</code>, which contains all the
1.109 rillig 1308: binary packages that are available for the platform, excluding those
1.317 nia 1309: that may not be distributed via HTTP or FTP.</p>
1.109 rillig 1310: <p>To install packages directly from an FTP or HTTP server, run
1311: the following commands in a Bourne-compatible shell (be sure to
1.110 hubertf 1312: <span class="command"><strong>su</strong></span> to root first):</p>
1.109 rillig 1313: <pre class="screen">
1.317 nia 1314: <code class="prompt">#</code> <strong class="userinput"><code>PATH="/usr/pkg/sbin:/usr/pkg/bin:$PATH"</code></strong>
1315: <code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="https://cdn.NetBSD.org/pub/pkgsrc/packages"</code></strong>
1.284 rillig 1316: <code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="$PKG_PATH/<em class="replaceable"><code>OPSYS</code></em>/<em class="replaceable"><code>ARCH</code></em>/<em class="replaceable"><code>VERSIONS</code></em>/All/"</code></strong>
1.109 rillig 1317: <code class="prompt">#</code> <strong class="userinput"><code>export PATH PKG_PATH</code></strong>
1.317 nia 1318: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add pkgin</code></strong>
1.109 rillig 1319: </pre>
1320: <p>Instead of URLs, you can also use local paths, for example if
1321: you are installing from a set of CDROMs, DVDs or an NFS-mounted
1322: repository. If you want to install packages from multiple sources,
1323: you can separate them by a semicolon in
1324: <code class="varname">PKG_PATH</code>.</p>
1325: <p>After these preparations, installing a package is very
1326: easy:</p>
1327: <pre class="screen">
1.317 nia 1328: <code class="prompt">#</code> <strong class="userinput"><code>pkgin search nginx</code></strong>
1329: nginx-1.19.6 Lightweight HTTP server and mail proxy server
1330: nginx-1.18.0nb8 Lightweight HTTP server and mail proxy server
1331: <code class="prompt">#</code> <strong class="userinput"><code>pkgin install zsh nginx-1.19.6 vim</code></strong>
1332: </pre>
1333: <p>Note that <span class="command"><strong>pkgin</strong></span> is a user-friendly frontend
1334: to the <span class="command"><strong>pkg_*</strong></span> tools.</p>
1335: <p>Any prerequisite packages needed to run the
1.88 wiz 1336: package in question will be installed, too, assuming they are
1.317 nia 1337: present in the repository.</p>
1.75 rillig 1338: <p>After you've installed packages, be sure to have
1.88 wiz 1339: <code class="filename">/usr/pkg/bin</code> and <code class="filename">/usr/pkg/sbin</code> in your
1340: <code class="varname">PATH</code> so you can actually start the just
1341: installed program.</p>
1.75 rillig 1342: </div>
1.148 asau 1343: <div class="sect2">
1.75 rillig 1344: <div class="titlepage"><div><div><h3 class="title">
1.317 nia 1345: <a name="using.pkgin_update"></a>5.1.3. Updating packages</h3></div></div></div>
1346: <p>To update binary packages, it is recommended that you use
1347: <span class="command"><strong>pkgin upgrade</strong></span>. This will compare the remote
1348: package repository to your locally installed packages and safely
1349: replace any older packages.</p>
1350: <p>Note that pkgsrc is released as quarterly branches.
1351: If you are updating to a newer quarterly branch of pkgsrc, you may
1352: need to adjust the repository in
1353: <code class="filename">/usr/pkg/etc/pkgin/repositories.conf</code>.</p>
1354: </div>
1355: <div class="sect2">
1356: <div class="titlepage"><div><div><h3 class="title">
1357: <a name="using.pkg_delete"></a>5.1.4. Deinstalling packages</h3></div></div></div>
1.82 rillig 1358: <p>To deinstall a package, it does not matter whether it was
1.317 nia 1359: installed from source code or from a binary package. Neither the
1360: <span class="command"><strong>pkgin</strong></span> or the <span class="command"><strong>pkg_delete</strong></span>
1361: command need to know.</p>
1362: <p>To delete a package, you can just run <span class="command"><strong>pkgin remove
1.88 wiz 1363: <em class="replaceable"><code>package-name</code></em></strong></span>. The package
1.317 nia 1364: name can be given with or without version number.</p>
1.82 rillig 1365: </div>
1.148 asau 1366: <div class="sect2">
1.82 rillig 1367: <div class="titlepage"><div><div><h3 class="title">
1.317 nia 1368: <a name="using.pkg_info"></a>5.1.5. Getting information about installed packages</h3></div></div></div>
1.110 hubertf 1369: <p>The <span class="command"><strong>pkg_info</strong></span> shows information about
1.317 nia 1370: installed packages or binary package files.
1371: As with other management tools, it works with packages installed
1372: from source or binaries.</p>
1.82 rillig 1373: </div>
1.148 asau 1374: <div class="sect2">
1.82 rillig 1375: <div class="titlepage"><div><div><h3 class="title">
1.317 nia 1376: <a name="vulnerabilities"></a>5.1.6. Checking for security vulnerabilities in installed packages</h3></div></div></div>
1.82 rillig 1377: <p>
1.279 leot 1378: The pkgsrc Security Team and Packages Groups maintain a list of
1.317 nia 1379: known vulnerabilities to packages which are (or have been)
1.88 wiz 1380: included in pkgsrc. The list is available from the NetBSD
1.317 nia 1381: CDN at <a class="ulink" href="https://cdn.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities" target="_top">https://cdn.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities</a>.
1382: </p>
1383: <p>
1384: Please note that not every "vulnerability" with a CVE assignment is
1385: exploitable in every configuration.
1386: Some bugs are marked as active simply because an fix was not
1387: marked as such.
1388: Operating system specific hardening and mitigation features may also
1389: reduce the impact of bugs.
1.88 wiz 1390: </p>
1.82 rillig 1391: <p>
1.125 wiz 1392: Through <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1.88 wiz 1393: this list can be downloaded
1394: automatically, and a security audit of all packages installed on a system
1395: can take place.
1396: </p>
1.82 rillig 1397: <p>
1.125 wiz 1398: There are two components to auditing. The first
1399: step, <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1400: is for downloading
1.88 wiz 1401: the list of vulnerabilities from the NetBSD FTP site. The second
1.125 wiz 1402: step, <span class="command"><strong>pkg_admin audit</strong></span>, checks to see if any of your
1.88 wiz 1403: installed packages are vulnerable. If a package is vulnerable, you
1404: will see output similar to the following:
1405: </p>
1.82 rillig 1406: <pre class="screen">Package samba-2.0.9 has a local-root-shell vulnerability, see
1.289 leot 1407: https://www.samba.org/samba/whatsnew/macroexploit.html</pre>
1.82 rillig 1408: <p>
1.125 wiz 1409: You may wish to have the
1.317 nia 1410: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities" target="_top">vulnerabilities</a>
1.125 wiz 1411: file downloaded daily so that
1412: it remains current. This may be done by adding an appropriate entry
1.322 leot 1413: to the root users <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/crontab.5"><span class="citerefentry"><span class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
1.125 wiz 1414: </p>
1415: <pre class="screen">
1.233 sevan 1416: # Download vulnerabilities file
1.230 sevan 1417: 0 3 * * * /usr/pkg/sbin/pkg_admin fetch-pkg-vulnerabilities >/dev/null 2>&1
1.233 sevan 1418: # Audit the installed packages and email results to root
1419: 9 3 * * * /usr/pkg/sbin/pkg_admin audit |mail -s "Installed package audit result" \
1420: root >/dev/null 2>&1
1.125 wiz 1421: </pre>
1422: <p>
1.230 sevan 1423: will update the vulnerability list every day at 3AM, followed by an audit
1424: at 3:09AM. The result of the audit are then emailed to root.
1.125 wiz 1425:
1.230 sevan 1426: On NetBSD this may be accomplished instead by adding the following
1427: line to <code class="filename">/etc/daily.conf</code>:
1428: </p>
1429: <pre class="screen">
1430: fetch_pkg_vulnerabilities=YES
1431: </pre>
1432: <p>
1433: to fetch the vulnerability list from the daily security script. The system
1434: is set to audit the packages by default but can be set explicitly, if
1.235 yyamano 1435: desired (not required), by adding the following line to
1.230 sevan 1436: <code class="filename">/etc/security.conf</code>:
1.125 wiz 1437: </p>
1438: <pre class="screen">
1.230 sevan 1439: check_pkg_vulnerabilities=YES
1.125 wiz 1440: </pre>
1441: <p>
1.322 leot 1442: see <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/daily.conf.5"><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a> and <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/security.conf.5"><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for more details.
1.88 wiz 1443: </p>
1.82 rillig 1444: </div>
1.148 asau 1445: <div class="sect2">
1.82 rillig 1446: <div class="titlepage"><div><div><h3 class="title">
1.317 nia 1447: <a name="pkg_versions"></a>5.1.7. Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div>
1.82 rillig 1448: <p>
1.322 leot 1449: Install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/index.html" target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
1.128 wiz 1450: <span class="command"><strong>lintpkgsrc</strong></span> with the <span class="quote">“<span class="quote">-i</span>”</span>
1.317 nia 1451: argument to check if any packages are stale, e.g.
1.88 wiz 1452: </p>
1453: <pre class="screen">
1454: <code class="prompt">%</code> <strong class="userinput"><code>lintpkgsrc -i</code></strong>
1.82 rillig 1455: ...
1.88 wiz 1456: Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
1457: </pre>
1.82 rillig 1458: </div>
1.148 asau 1459: <div class="sect2">
1.82 rillig 1460: <div class="titlepage"><div><div><h3 class="title">
1.317 nia 1461: <a name="using.pkg_admin"></a>5.1.8. Other administrative functions</h3></div></div></div>
1.110 hubertf 1462: <p>The <span class="command"><strong>pkg_admin</strong></span> executes various
1.88 wiz 1463: administrative functions on the package system.</p>
1.82 rillig 1464: </div>
1.75 rillig 1465: </div>
1.148 asau 1466: <div class="sect1">
1.75 rillig 1467: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1468: <a name="building-packages-from-source"></a>5.2. Building packages from source</h2></div></div></div>
1.88 wiz 1469: <p>After obtaining pkgsrc, the <code class="filename">pkgsrc</code>
1470: directory now contains a set of packages, organized into
1471: categories. You can browse the online index of packages, or run
1.110 hubertf 1472: <span class="command"><strong>make readme</strong></span> from the <code class="filename">pkgsrc</code>
1.88 wiz 1473: directory to build local <code class="filename">README.html</code> files for
1.322 leot 1474: all packages, viewable with any web browser such as <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/index.html" target="_top"><code class="filename">www/lynx</code></a> or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/index.html" target="_top"><code class="filename">www/firefox</code></a>.</p>
1.88 wiz 1475: <p>The default <span class="emphasis"><em>prefix</em></span> for installed packages
1476: is <code class="filename">/usr/pkg</code>. If you wish to change this, you
1477: should do so by setting <code class="varname">LOCALBASE</code> in
1.110 hubertf 1478: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. You should not try to use multiple
1.88 wiz 1479: different <code class="varname">LOCALBASE</code> definitions on the same
1480: system (inside a chroot is an exception). </p>
1481: <p>The rest of this chapter assumes that the package is already
1.110 hubertf 1482: in pkgsrc. If it is not, see <a class="xref" href="#developers-guide" title="Part II. The pkgsrc developer's guide">Part II, “The pkgsrc developer's guide”</a> for
1.88 wiz 1483: instructions how to create your own packages.</p>
1.148 asau 1484: <div class="sect2">
1.75 rillig 1485: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1486: <a name="requirements"></a>5.2.1. Requirements</h3></div></div></div>
1.82 rillig 1487: <p>To build packages from source, you need a working C
1.88 wiz 1488: compiler. On NetBSD, you need to install the
1.128 wiz 1489: <span class="quote">“<span class="quote">comp</span>”</span> and the <span class="quote">“<span class="quote">text</span>”</span> distribution
1.88 wiz 1490: sets. If you want to build X11-related packages, the
1.128 wiz 1491: <span class="quote">“<span class="quote">xbase</span>”</span> and <span class="quote">“<span class="quote">xcomp</span>”</span> distribution
1.88 wiz 1492: sets are required, too.</p>
1.75 rillig 1493: </div>
1.148 asau 1494: <div class="sect2">
1.75 rillig 1495: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1496: <a name="fetching-distfiles"></a>5.2.2. Fetching distfiles</h3></div></div></div>
1.75 rillig 1497: <p>The first step for building a package is downloading the
1.88 wiz 1498: distfiles (i.e. the unmodified source). If they have not yet been
1499: downloaded, pkgsrc will fetch them automatically.</p>
1500: <p>If you have all files that you need in the
1501: <code class="filename">distfiles</code> directory,
1502: you don't need to connect. If the distfiles are on CD-ROM, you can
1503: mount the CD-ROM on <code class="filename">/cdrom</code> and add:
1504: </p>
1.82 rillig 1505: <pre class="screen">DISTDIR=/cdrom/pkgsrc/distfiles</pre>
1506: <p>
1.110 hubertf 1507: to your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.91 rillig 1508: <p>By default a list of distribution sites will be randomly
1509: intermixed to prevent huge load on servers which holding popular
1510: packages (for example, SourceForge.net mirrors). Thus, every
1511: time when you need to fetch yet another distfile all the mirrors
1512: will be tried in new (random) order. You can turn this feature
1513: off by setting <code class="varname">MASTER_SORT_RANDOM=NO</code> (for
1514: <code class="varname">PKG_DEVELOPER</code>s it's already disabled).</p>
1.88 wiz 1515: <p>You can overwrite some of the major distribution sites to
1516: fit to sites that are close to your own. By setting one or two
1517: variables you can modify the order in which the master sites are
1518: accessed. <code class="varname">MASTER_SORT</code> contains a whitespace
1519: delimited list of domain suffixes.
1520: <code class="varname">MASTER_SORT_REGEX</code> is even more flexible, it
1521: contains a whitespace delimited list of regular expressions. It
1522: has higher priority than <code class="varname">MASTER_SORT</code>. Have a
1523: look at <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to find
1524: some examples. This may save some of your bandwidth and
1525: time.</p>
1.75 rillig 1526: <p>You can change these settings either in your shell's environment, or,
1.88 wiz 1527: if you want to keep the settings, by editing the
1.110 hubertf 1528: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file,
1.88 wiz 1529: and adding the definitions there.</p>
1.82 rillig 1530: <p>
1.88 wiz 1531: If a package depends on many other packages (such as
1.322 leot 1532: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/index.html" target="_top"><code class="filename">meta-pkgs/kde4</code></a>), the build process may
1.88 wiz 1533: alternate between periods of
1534: downloading source, and compiling. To ensure you have all the source
1535: downloaded initially you can run the command:
1536: </p>
1.82 rillig 1537: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch-list | sh</code></strong></pre>
1538: <p>
1.88 wiz 1539: which will output and run a set of shell commands to fetch the
1540: necessary files into the <code class="filename">distfiles</code> directory. You can
1541: also choose to download the files manually.
1542: </p>
1.75 rillig 1543: </div>
1.148 asau 1544: <div class="sect2">
1.75 rillig 1545: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1546: <a name="how-to-build-and-install"></a>5.2.3. How to build and install</h3></div></div></div>
1.82 rillig 1547: <p>
1.88 wiz 1548: Once the software has downloaded, any patches will be applied, then it
1549: will be compiled for you. This may take some time depending on your
1550: computer, and how many other packages the software depends on and their
1551: compile time.
1552: </p>
1.148 asau 1553: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.75 rillig 1554: <h3 class="title">Note</h3>
1555: <p>If using bootstrap or pkgsrc on a non-NetBSD system,
1.110 hubertf 1556: use the pkgsrc <span class="command"><strong>bmake</strong></span> command instead of
1.128 wiz 1557: <span class="quote">“<span class="quote">make</span>”</span> in the examples in this guide.</p>
1.75 rillig 1558: </div>
1.87 wiz 1559: <p>For example, type</p>
1.88 wiz 1560: <pre class="screen">
1561: <code class="prompt">%</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
1562: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
1563: </pre>
1.75 rillig 1564: <p>at the shell prompt to build the various components of the
1.88 wiz 1565: package.</p>
1.82 rillig 1566: <p>The next stage is to actually install the newly compiled
1.88 wiz 1567: program onto your system. Do this by entering:
1.82 rillig 1568:
1.88 wiz 1569: </p>
1.82 rillig 1570: <pre class="screen">
1.88 wiz 1571: <code class="prompt">%</code> <strong class="userinput"><code>make install</code></strong>
1572: </pre>
1.82 rillig 1573: <p>
1574:
1.88 wiz 1575: while you are still in the directory for whatever package you
1576: are installing.</p>
1.82 rillig 1577: <p>Installing the package on your system may require you to
1.88 wiz 1578: be root. However, pkgsrc has a
1579: <span class="emphasis"><em>just-in-time-su</em></span> feature, which allows you
1580: to only become root for the actual installation step.</p>
1.82 rillig 1581: <p>That's it, the software should now be installed and setup for use.
1.88 wiz 1582: You can now enter:
1.82 rillig 1583:
1.88 wiz 1584: </p>
1.82 rillig 1585: <pre class="screen">
1.88 wiz 1586: <code class="prompt">%</code> <strong class="userinput"><code>make clean</code></strong>
1587: </pre>
1.82 rillig 1588: <p>
1589:
1.88 wiz 1590: to remove the compiled files in the work directory, as you shouldn't need
1591: them any more. If other packages were also added to your system
1592: (dependencies) to allow your program to compile, you can tidy these up
1593: also with the command:</p>
1.82 rillig 1594: <pre class="screen">
1.88 wiz 1595: <code class="prompt">%</code> <strong class="userinput"><code>make clean-depends</code></strong>
1596: </pre>
1.75 rillig 1597: <p>Taking the figlet utility as an example, we can install it on our
1.322 leot 1598: system by building as shown in <a class="xref" href="#logs" title="Appendix C. Build logs">Appendix C, <i>Build logs</i></a>.</p>
1.88 wiz 1599: <p>The program is installed under the default root of the
1600: packages tree - <code class="filename">/usr/pkg</code>. Should this not
1601: conform to your tastes, set the <code class="varname">LOCALBASE</code>
1602: variable in your environment, and it will use that value as the
1603: root of your packages tree. So, to use
1604: <code class="filename">/usr/local</code>, set
1605: <code class="varname">LOCALBASE=/usr/local</code> in your environment.
1606: Please note that you should use a directory which is dedicated to
1607: packages and not shared with other programs (i.e., do not try and
1608: use <code class="varname">LOCALBASE=/usr</code>). Also, you should not try
1609: to add any of your own files or directories (such as
1610: <code class="filename">src/</code>, <code class="filename">obj/</code>, or
1611: <code class="filename">pkgsrc/</code>) below the
1612: <code class="varname">LOCALBASE</code> tree. This is to prevent possible
1613: conflicts between programs and other files installed by the
1614: package system and whatever else may have been installed
1615: there.</p>
1.110 hubertf 1616: <p>Some packages look in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.88 wiz 1617: alter some configuration options at build time. Have a look at
1618: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to get an overview
1619: of what will be set there by default. Environment variables such
1620: as <code class="varname">LOCALBASE</code> can be set in
1.110 hubertf 1621: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to save having to remember to
1.88 wiz 1622: set them each time you want to use pkgsrc.</p>
1.128 wiz 1623: <p>Occasionally, people want to <span class="quote">“<span class="quote">look under the
1624: covers</span>”</span> to see what is going on when a package is building
1.88 wiz 1625: or being installed. This may be for debugging purposes, or out of
1626: simple curiosity. A number of utility values have been added to
1627: help with this.</p>
1.128 wiz 1628: <div class="orderedlist"><ol class="orderedlist" type="1">
1629: <li class="listitem">
1.322 leot 1630: <p>If you invoke the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> command with
1.88 wiz 1631: <code class="varname">PKG_DEBUG_LEVEL=2</code>, then a huge amount of
1632: information will be displayed. For example,</p>
1.75 rillig 1633: <pre class="screen"><strong class="userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong></pre>
1.88 wiz 1634: <p>will show all the commands that are invoked, up to and
1.128 wiz 1635: including the <span class="quote">“<span class="quote">patch</span>”</span> stage.</p>
1.75 rillig 1636: </li>
1.128 wiz 1637: <li class="listitem">
1.322 leot 1638: <p>If you want to know the value of a certain <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.88 wiz 1639: definition, then the <code class="varname">VARNAME</code> definition
1640: should be used, in conjunction with the show-var
1.322 leot 1641: target. e.g. to show the expansion of the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.88 wiz 1642: variable <code class="varname">LOCALBASE</code>:</p>
1643: <pre class="screen">
1644: <code class="prompt">%</code> <strong class="userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
1.75 rillig 1645: /usr/pkg
1646: <code class="prompt">%</code>
1.88 wiz 1647: </pre>
1.75 rillig 1648: </li>
1649: </ol></div>
1650: <p>If you want to install a binary package that you've either
1.88 wiz 1651: created yourself (see next section), that you put into
1652: pkgsrc/packages manually or that is located on a remote FTP
1653: server, you can use the "bin-install" target. This target will
1.322 leot 1654: install a binary package - if available - via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>,
1.110 hubertf 1655: else do a <span class="command"><strong>make package</strong></span>. The list of remote FTP
1.88 wiz 1656: sites searched is kept in the variable
1657: <code class="varname">BINPKG_SITES</code>, which defaults to
1.322 leot 1658: ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>
1.88 wiz 1659: can be put into <code class="varname">BIN_INSTALL_FLAGS</code>. See
1660: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more
1661: details.</p>
1662: <p>A final word of warning: If you set up a system that has a
1663: non-standard setting for <code class="varname">LOCALBASE</code>, be sure to
1664: set that before any packages are installed, as you cannot use
1665: several directories for the same purpose. Doing so will result in
1666: pkgsrc not being able to properly detect your installed packages,
1667: and fail miserably. Note also that precompiled binary packages are
1668: usually built with the default <code class="varname">LOCALBASE</code> of
1669: <code class="filename">/usr/pkg</code>, and that you should
1670: <span class="emphasis"><em>not</em></span> install any if you use a non-standard
1671: <code class="varname">LOCALBASE</code>.</p>
1.75 rillig 1672: </div>
1673: </div>
1674: </div>
1.148 asau 1675: <div class="chapter">
1.75 rillig 1676: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 1677: <a name="configuring"></a>Chapter 6. Configuring pkgsrc</h2></div></div></div>
1.75 rillig 1678: <div class="toc">
1679: <p><b>Table of Contents</b></p>
1.210 leot 1680: <dl class="toc">
1.267 rillig 1681: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
1682: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
1683: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
1684: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1685: <dd><dl>
1686: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
1687: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
1688: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.88 wiz 1689: </dl></dd>
1.267 rillig 1690: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
1691: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.75 rillig 1692: </dl>
1693: </div>
1.104 rillig 1694: <a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
1.89 rillig 1695: called <code class="filename">mk.conf</code>. In which directory pkgsrc looks for
1696: that file depends on the installation. On NetBSD, when you use
1.322 leot 1697: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it is in the directory
1.89 rillig 1698: <code class="filename">/etc/</code>. In all other cases the default location is
1699: <code class="literal">${PREFIX}/etc/</code>, depending on where you told the
1700: bootstrap program to install the binary packages.</p>
1701: <p>The format of the configuration file is that of the usual
1702: BSD-style <code class="filename">Makefile</code>s. The whole pkgsrc configuration
1703: is done by setting variables in this file. Note that you can define all
1704: kinds of variables, and no special error checking (for example for
1.223 rillig 1705: spelling mistakes) takes place.</p>
1.148 asau 1706: <div class="sect1">
1.75 rillig 1707: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1708: <a name="general-configuration"></a>6.1. General configuration</h2></div></div></div>
1.223 rillig 1709: <p>The following variables apply to all
1.89 rillig 1710: pkgsrc packages. A complete list of the variables that can be
1711: configured by the user is available in
1712: <code class="filename">mk/defaults/mk.conf</code>, together with some
1713: comments that describe each variable's intent.</p>
1.148 asau 1714: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 1715: <li class="listitem"><p><code class="varname">LOCALBASE</code>: Where
1.75 rillig 1716: packages will be installed. The default is
1.76 rillig 1717: <code class="filename">/usr/pkg</code>. Do not mix binary packages
1.75 rillig 1718: with different <code class="varname">LOCALBASE</code>s!</p></li>
1.128 wiz 1719: <li class="listitem"><p><code class="varname">CROSSBASE</code>: Where
1720: <span class="quote">“<span class="quote">cross</span>”</span> category packages will be
1.75 rillig 1721: installed. The default is
1.76 rillig 1722: <code class="filename">${LOCALBASE}/cross</code>.</p></li>
1.128 wiz 1723: <li class="listitem"><p><code class="varname">X11BASE</code>: Where
1.75 rillig 1724: X11 is installed on the system. The default is
1.194 bsiegert 1725: <code class="filename">/usr/X11R7</code>.</p></li>
1.128 wiz 1726: <li class="listitem"><p><code class="varname">DISTDIR</code>: Where to store the
1.75 rillig 1727: downloaded copies of the original source distributions used
1728: for building pkgsrc packages. The default is
1.76 rillig 1729: <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li>
1.128 wiz 1730: <li class="listitem"><p><code class="varname">PKG_DBDIR</code>: Where the
1.97 rillig 1731: database about installed packages is stored. The default is
1.230 sevan 1732: <code class="filename">/usr/pkg/pkgdb</code>.</p></li>
1.128 wiz 1733: <li class="listitem"><p><code class="varname">MASTER_SITE_OVERRIDE</code>:
1.75 rillig 1734: If set, override the packages'
1735: <code class="varname">MASTER_SITES</code> with this value.</p></li>
1.128 wiz 1736: <li class="listitem"><p><code class="varname">MASTER_SITE_BACKUP</code>:
1.75 rillig 1737: Backup location(s) for distribution files and patch files
1738: if not found locally or in
1.76 rillig 1739: <code class="filename">${MASTER_SITES}</code> or
1740: <code class="filename">${PATCH_SITES}</code> respectively.
1.230 sevan 1741: The defaults is
1742: <code class="filename">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}/</code>.</p></li>
1.128 wiz 1743: <li class="listitem"><p><code class="varname">BINPKG_SITES</code>:
1.93 rillig 1744: List of sites carrying binary pkgs. <em class="replaceable"><code>rel</code></em> and
1745: <em class="replaceable"><code>arch</code></em> are replaced with OS
1.128 wiz 1746: release (<span class="quote">“<span class="quote">2.0</span>”</span>, etc.) and architecture
1747: (<span class="quote">“<span class="quote">mipsel</span>”</span>, etc.).</p></li>
1748: <li class="listitem"><p><code class="varname">ACCEPTABLE_LICENSES</code>:
1.125 wiz 1749: List of acceptable licenses. License names are case-sensitive.
1750: Whenever you try to build a package whose license is not in this
1751: list, you will get an error message. If the license condition is
1752: simple enough, the error message will include specific
1753: instructions on how to change this variable.</p></li>
1.75 rillig 1754: </ul></div>
1755: </div>
1.148 asau 1756: <div class="sect1">
1.75 rillig 1757: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1758: <a name="variables-affecting-build"></a>6.2. Variables affecting the build process</h2></div></div></div>
1.219 rillig 1759: <p>
1.75 rillig 1760: </p>
1.148 asau 1761: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 1762: <li class="listitem"><p><code class="varname">PACKAGES</code>: The top level
1.75 rillig 1763: directory for the binary packages. The default is
1.76 rillig 1764: <code class="filename">${PKGSRCDIR}/packages</code>.</p></li>
1.128 wiz 1765: <li class="listitem"><p><code class="varname">WRKOBJDIR</code>:
1.75 rillig 1766: The top level directory where, if defined, the separate
1767: working directories will get created, and symbolically
1.76 rillig 1768: linked to from <code class="filename">${WRKDIR}</code> (see below).
1.75 rillig 1769: This is useful for building packages on several
1.76 rillig 1770: architectures, then <code class="filename">${PKGSRCDIR}</code>
1771: can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code>
1.75 rillig 1772: is local to every architecture. (It should be noted that
1773: <code class="varname">PKGSRCDIR</code> should not be set by the user
1.126 jakllsch 1774: — it is an internal definition which refers to the
1.75 rillig 1775: root of the pkgsrc tree. It is possible to have many
1776: pkgsrc tree instances.)</p></li>
1.128 wiz 1777: <li class="listitem"><p><code class="varname">LOCALPATCHES</code>:
1.75 rillig 1778: Directory for local patches that aren't part of pkgsrc.
1.299 rillig 1779: See <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a> for more
1.93 rillig 1780: information.</p></li>
1.128 wiz 1781: <li class="listitem"><p><code class="varname">PKGMAKECONF</code>: Location of
1.110 hubertf 1782: the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file used by a package's
1.75 rillig 1783: BSD-style Makefile. If this is not set,
1784: <code class="varname">MAKECONF</code> is set to
1.76 rillig 1785: <code class="filename">/dev/null</code> to avoid picking up
1786: settings used by builds in <code class="filename">/usr/src</code>.</p></li>
1.75 rillig 1787: </ul></div>
1788: </div>
1.148 asau 1789: <div class="sect1">
1.75 rillig 1790: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1791: <a name="variables-affecting-installation"></a>6.3. Variables affecting the installation process</h2></div></div></div>
1.312 gdt 1792: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><code class="varname">PKGSRC_KEEP_BIN_PKGS</code>:
1.256 maya 1793: By default, binary packages of built packages are
1.263 leot 1794: preserved in <code class="filename">${PACKAGES}/All</code>. Setting
1.256 maya 1795: this variable to "no" prevents this.</p></li></ul></div>
1.217 jnemeth 1796: <p>Packages have to support installation into a
1.103 wiz 1797: subdirectory of <code class="varname">WRKDIR</code>. This allows a package
1798: to be built, before the actual filesystem is touched. DESTDIR
1799: support exists in two variations:</p>
1.148 asau 1800: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 1801: <li class="listitem"><p>Basic DESTDIR support means that the package
1.131 wiz 1802: installation and packaging is still run as root.</p></li>
1803: <li class="listitem"><p>Full DESTDIR support can run the complete
1804: build, installation and packaging as normal user. Root
1805: privileges are only needed to add packages.</p></li>
1806: </ul></div>
1.103 wiz 1807: <p>With basic DESTDIR support, <strong class="userinput"><code>make
1808: clean</code></strong> needs to be run as root.</p>
1.118 imil 1809: <p>Considering the <code class="filename">foo/bar</code> package,
1810: DESTDIR full support can be tested using the following commands
1811:
1812: </p>
1813: <pre class="programlisting">
1814: <code class="prompt">$</code> id
1815: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
1816: <code class="prompt">$</code> mkdir $HOME/packages
1817: <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
1818: </pre>
1819: <p>
1820:
1821: Verify <code class="varname">DESTDIR</code> full support, no root privileges
1822: should be needed
1823:
1824: </p>
1825: <pre class="programlisting">
1.174 asau 1826: <code class="prompt">$</code> make stage-install
1.118 imil 1827: </pre>
1828: <p>
1829:
1830: Create a package without root privileges
1831:
1832: </p>
1833: <pre class="programlisting">
1.174 asau 1834: <code class="prompt">$</code> make PACKAGES=$HOME/packages package
1.118 imil 1835: </pre>
1836: <p>
1837:
1838: For the following command, you must be able to gain root
1.322 leot 1839: privileges using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/su.1"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
1.118 imil 1840:
1841: </p>
1842: <pre class="programlisting">
1.174 asau 1843: <code class="prompt">$</code> make PACKAGES=$HOME/packages install
1.118 imil 1844: </pre>
1845: <p>
1846:
1847: Then, as a simple user
1848:
1849: </p>
1850: <pre class="programlisting">
1851: <code class="prompt">$</code> make clean
1852: </pre>
1853: <p>
1854:
1855: </p>
1.103 wiz 1856: </div>
1.148 asau 1857: <div class="sect1">
1.103 wiz 1858: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1859: <a name="conf.compiler"></a>6.4. Selecting and configuring the compiler</h2></div></div></div>
1.148 asau 1860: <div class="sect2">
1.78 rillig 1861: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1862: <a name="selecting-the-compiler"></a>6.4.1. Selecting the compiler</h3></div></div></div>
1.89 rillig 1863: <p>By default, pkgsrc will use GCC to build packages. This may be
1864: overridden by setting the following variables in /etc/mk.conf:</p>
1.148 asau 1865: <div class="variablelist"><dl class="variablelist">
1.89 rillig 1866: <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
1867: <dd>
1868: <p>This is a list of values specifying the chain of
1869: compilers to invoke when building packages. Valid values
1870: are:</p>
1.148 asau 1871: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.174 asau 1872: <li class="listitem"><p><code class="varname">ccc</code>:
1873: Compaq C Compilers (Tru64)</p></li>
1874: <li class="listitem"><p><code class="varname">ccache</code>:
1875: compiler cache (chainable)</p></li>
1876: <li class="listitem"><p><code class="varname">clang</code>:
1877: Clang C and Objective-C compiler</p></li>
1.128 wiz 1878: <li class="listitem"><p><code class="varname">distcc</code>:
1.89 rillig 1879: distributed C/C++ (chainable)</p></li>
1.174 asau 1880: <li class="listitem"><p><code class="varname">f2c</code>:
1881: Fortran 77 to C compiler (chainable)</p></li>
1882: <li class="listitem"><p><code class="varname">icc</code>:
1883: Intel C++ Compiler (Linux)</p></li>
1884: <li class="listitem"><p><code class="varname">ido</code>:
1885: SGI IRIS Development Option cc (IRIX 5)</p></li>
1.128 wiz 1886: <li class="listitem"><p><code class="varname">gcc</code>:
1.89 rillig 1887: GNU C/C++ Compiler</p></li>
1.174 asau 1888: <li class="listitem"><p><code class="varname">hp</code>:
1889: HP-UX C/aC++ compilers</p></li>
1.128 wiz 1890: <li class="listitem"><p><code class="varname">mipspro</code>:
1.89 rillig 1891: Silicon Graphics, Inc. MIPSpro (n32/n64)</p></li>
1.174 asau 1892: <li class="listitem"><p><code class="varname">mipspro-ucode</code>:
1.89 rillig 1893: Silicon Graphics, Inc. MIPSpro (o32)</p></li>
1.128 wiz 1894: <li class="listitem"><p><code class="varname">sunpro</code>:
1.89 rillig 1895: Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio</p></li>
1.174 asau 1896: <li class="listitem"><p><code class="varname">xlc</code>:
1.230 sevan 1897: IBM's XL C/C++ compiler suite</p></li>
1.89 rillig 1898: </ul></div>
1899: <p>The default is
1.128 wiz 1900: <span class="quote">“<span class="quote"><code class="varname">gcc</code></span>”</span>. You can use
1.89 rillig 1901: <code class="varname">ccache</code> and/or
1902: <code class="varname">distcc</code> with an appropriate
1903: <code class="varname">PKGSRC_COMPILER</code> setting,
1.128 wiz 1904: e.g. <span class="quote">“<span class="quote"><code class="varname">ccache gcc</code></span>”</span>. This
1.94 dmcmahil 1905: variable should always be terminated with a value for
1906: a real compiler. Note that only one real compiler
1.128 wiz 1907: should be listed (e.g. <span class="quote">“<span class="quote"><code class="varname">sunpro gcc</code></span>”</span>
1.94 dmcmahil 1908: is not allowed).</p>
1.89 rillig 1909: </dd>
1910: <dt><span class="term"><code class="varname">GCC_REQD</code>:</span></dt>
1911: <dd><p>This specifies the minimum version of GCC to use
1912: when building packages. If the system GCC doesn't
1913: satisfy this requirement, then pkgsrc will build and
1914: install one of the GCC packages to use instead.</p></dd>
1.266 leot 1915: <dt><span class="term"><code class="varname">PYTHON_VERSION_DEFAULT</code>:</span></dt>
1.225 maya 1916: <dd><p>Specifies which version of python to use when several
1917: options are available.</p></dd>
1918: <dt><span class="term"><code class="varname">PKGSRC_FORTRAN</code>:</span></dt>
1.291 gutterid 1919: <dd><p>Specifies the Fortran compiler to use.
1920: The default is <code class="varname">gfortran</code>.</p></dd>
1.225 maya 1921: <dt><span class="term"><code class="varname">GFORTRAN_VERSION</code>:</span></dt>
1922: <dd><p>If <code class="varname">PKGSRC_FORTRAN</code><code class="literal">=</code>
1923: <code class="varname">gfortran</code> is used, this option specifies which
1924: version to use.</p></dd>
1.89 rillig 1925: </dl></div>
1926: </div>
1.148 asau 1927: <div class="sect2">
1.89 rillig 1928: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1929: <a name="conf.cflags"></a>6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div>
1.78 rillig 1930: <p>If you wish to set the <code class="varname">CFLAGS</code> variable,
1931: please make sure to use the <code class="literal">+=</code> operator
1932: instead of the <code class="literal">=</code> operator:</p>
1933: <pre class="programlisting">
1.100 rillig 1934: CFLAGS+= -your -flags
1.78 rillig 1935: </pre>
1936: <p>Using <code class="varname">CFLAGS=</code> (i.e. without the
1.128 wiz 1937: <span class="quote">“<span class="quote">+</span>”</span>) may lead to problems with packages that
1.117 jnemeth 1938: need to add their own flags. You may want to take a look
1.322 leot 1939: at the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/index.html" target="_top"><code class="filename">devel/cpuflags</code></a>
1.128 wiz 1940: package if you're interested in optimization specifically
1941: for the current CPU. </p>
1.78 rillig 1942: </div>
1.148 asau 1943: <div class="sect2">
1.88 wiz 1944: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 1945: <a name="conf.ldflags"></a>6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div>
1.88 wiz 1946: <p>If you want to pass flags to the linker, both in the configure
1947: step and the build step, you can do this in two ways. Either set
1948: <code class="varname">LDFLAGS</code> or <code class="varname">LIBS</code>. The difference
1949: between the two is that <code class="varname">LIBS</code> will be appended to
1950: the command line, while <code class="varname">LDFLAGS</code> come earlier.
1951: <code class="varname">LDFLAGS</code> is pre-loaded with rpath settings for ELF
1952: machines depending on the setting of <code class="varname">USE_IMAKE</code> or
1953: the inclusion of <code class="filename">mk/x11.buildlink3.mk</code>. As with
1954: <code class="varname">CFLAGS</code>, if you do not wish to override these
1955: settings, use the <code class="literal">+=</code> operator:</p>
1956: <pre class="programlisting">
1.100 rillig 1957: LDFLAGS+= -your -linkerflags
1.88 wiz 1958: </pre>
1959: </div>
1.78 rillig 1960: </div>
1.148 asau 1961: <div class="sect1">
1.78 rillig 1962: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1963: <a name="developer-advanced-settings"></a>6.5. Developer/advanced settings</h2></div></div></div>
1.194 bsiegert 1964: <p>
1.75 rillig 1965: </p>
1.148 asau 1966: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 1967: <li class="listitem">
1.75 rillig 1968: <p><code class="varname">PKG_DEVELOPER</code>:
1969: Run some sanity checks that package developers want:
1970: </p>
1.148 asau 1971: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
1.128 wiz 1972: <li class="listitem"><p>make sure patches apply with zero
1.88 wiz 1973: fuzz</p></li>
1.128 wiz 1974: <li class="listitem"><p>run check-shlibs to see that all
1.88 wiz 1975: binaries will find their shared libs.</p></li>
1.75 rillig 1976: </ul></div>
1977: <p>
1.87 wiz 1978: </p>
1.75 rillig 1979: </li>
1.128 wiz 1980: <li class="listitem"><p><code class="varname">PKG_DEBUG_LEVEL</code>: The level
1.88 wiz 1981: of debugging output which is displayed whilst making and
1982: installing the package. The default value for this is 0,
1983: which will not display the commands as they are executed
1984: (normal, default, quiet operation); the value 1 will display
1985: all shell commands before their invocation, and the value 2
1986: will display both the shell commands before their invocation,
1.223 rillig 1987: as well as their actual execution progress with <span class="command"><strong>set
1988: -x</strong></span>.</p></li>
1.75 rillig 1989: </ul></div>
1990: <p>
1991: </p>
1992: </div>
1.148 asau 1993: <div class="sect1">
1.75 rillig 1994: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 1995: <a name="selecting-build-options"></a>6.6. Selecting Build Options</h2></div></div></div>
1.88 wiz 1996: <p>Some packages have build time options, usually to select
1997: between different dependencies, enable optional support for big
1998: dependencies or enable experimental features.</p>
1.75 rillig 1999: <p>To see which options, if any, a package supports, and which
1.110 hubertf 2000: options are mutually exclusive, run <span class="command"><strong>make
1.88 wiz 2001: show-options</strong></span>, for example:</p>
1.75 rillig 2002: <pre class="programlisting">
2003: The following options are supported by this package:
2004: ssl Enable SSL support.
2005: Exactly one of the following gecko options is required:
2006: firefox Use firefox as gecko rendering engine.
2007: mozilla Use mozilla as gecko rendering engine.
2008: At most one of the following database options may be selected:
2009: mysql Enable support for MySQL database.
2010: pgsql Enable support for PostgreSQL database.
1.1 grant 2011:
1.75 rillig 2012: These options are enabled by default: firefox
2013: These options are currently enabled: mozilla ssl
1.1 grant 2014: </pre>
1.75 rillig 2015: <p>The following variables can be defined in
1.110 hubertf 2016: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to select which options to
1.88 wiz 2017: enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>,
2018: which can be used to select or disable options for all packages
2019: that support them, and
2020: <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>,
2021: which can be used to select or disable options specifically for
2022: package <em class="replaceable"><code>pkgbase</code></em>. Options listed in
1.128 wiz 2023: these variables are selected, options preceded by <span class="quote">“<span class="quote">-</span>”</span>
1.88 wiz 2024: are disabled. A few examples:</p>
1.75 rillig 2025: <pre class="screen">
1.110 hubertf 2026: <code class="prompt">$</code> <span class="command"><strong>grep "PKG.*OPTION" <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a></strong></span>
1.75 rillig 2027: PKG_DEFAULT_OPTIONS= -arts -dvdread -esound
2028: PKG_OPTIONS.kdebase= debug -sasl
2029: PKG_OPTIONS.apache= suexec </pre>
1.111 rillig 2030: <p>It is important to note that options that were specifically
1.120 snj 2031: suggested by the package maintainer must be explicitly removed if
1.111 rillig 2032: you do not wish to include the option. If you are unsure you can view
2033: the current state with <span class="command"><strong>make show-options</strong></span>.</p>
1.88 wiz 2034: <p>The following settings are consulted in the order given, and
2035: the last setting that selects or disables an option is
2036: used:</p>
1.128 wiz 2037: <div class="orderedlist"><ol class="orderedlist" type="1">
2038: <li class="listitem"><p>the default options as suggested by the package
1.88 wiz 2039: maintainer</p></li>
1.128 wiz 2040: <li class="listitem"><p>the options implied by the settings of legacy
1.88 wiz 2041: variables (see below)</p></li>
1.128 wiz 2042: <li class="listitem"><p><code class="varname">PKG_DEFAULT_OPTIONS</code></p></li>
2043: <li class="listitem"><p><code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code></p></li>
1.75 rillig 2044: </ol></div>
2045: <p>For groups of mutually exclusive options, the last option
1.88 wiz 2046: selected is used, all others are automatically disabled. If an
2047: option of the group is explicitly disabled, the previously
2048: selected option, if any, is used. It is an error if no option
2049: from a required group of options is selected, and building the
2050: package will fail.</p>
2051: <p>Before the options framework was introduced, build options
2052: were selected by setting a variable (often named
2053: <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in
1.110 hubertf 2054: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> for each option. To ease
1.88 wiz 2055: transition to the options framework for the user, these legacy
2056: variables are converted to the appropriate options setting
2057: (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>)
2058: automatically. A warning is issued to prompt the user to update
1.110 hubertf 2059: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to use the options framework
1.88 wiz 2060: directly. Support for the legacy variables will be removed
2061: eventually.</p>
1.75 rillig 2062: </div>
2063: </div>
1.148 asau 2064: <div class="chapter">
1.75 rillig 2065: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 2066: <a name="binary"></a>Chapter 7. Creating binary packages</h2></div></div></div>
1.75 rillig 2067: <div class="toc">
2068: <p><b>Table of Contents</b></p>
1.210 leot 2069: <dl class="toc">
1.267 rillig 2070: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
2071: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.75 rillig 2072: </dl>
2073: </div>
1.148 asau 2074: <div class="sect1">
1.75 rillig 2075: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2076: <a name="building-a-single-binary-package"></a>7.1. Building a single binary package</h2></div></div></div>
1.87 wiz 2077: <p>Once you have built and installed a package, you can create
2078: a <span class="emphasis"><em>binary package</em></span> which can be installed on
1.322 leot 2079: another system with <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
1.87 wiz 2080: the same package on a group of hosts and wasting CPU time. It also
2081: provides a simple means for others to install your package, should
2082: you distribute it.</p>
2083: <p>To create a binary package, change into the appropriate
1.110 hubertf 2084: directory in pkgsrc, and run <span class="command"><strong>make
1.87 wiz 2085: package</strong></span>:</p>
2086: <pre class="screen">
1.223 rillig 2087: <code class="prompt">$</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
2088: <code class="prompt">$</code> <strong class="userinput"><code>make package</code></strong>
2089: </pre>
1.87 wiz 2090: <p>This will build and install your package (if not already done),
2091: and then build a binary package from what was installed. You can
1.110 hubertf 2092: then use the <span class="command"><strong>pkg_*</strong></span> tools to manipulate
1.87 wiz 2093: it. Binary packages are created by default in
2094: <code class="filename">/usr/pkgsrc/packages</code>, in the form of a
1.322 leot 2095: gzipped tar file. See <a class="xref" href="#logs.package" title="C.2. Packaging figlet">Section C.2, “Packaging figlet”</a> for a
2096: continuation of the above <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/misc/figlet/index.html" target="_top"><code class="filename">misc/figlet</code></a> example.</p>
1.267 rillig 2097: <p>See <a class="xref" href="#submit" title="Chapter 23. Submitting and Committing">Chapter 23, <i>Submitting and Committing</i></a> for information on how to submit
1.87 wiz 2098: such a binary package.</p>
1.75 rillig 2099: </div>
1.148 asau 2100: <div class="sect1">
1.75 rillig 2101: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2102: <a name="settings-for-creationg-of-binary-packages"></a>7.2. Settings for creation of binary packages</h2></div></div></div>
1.299 rillig 2103: <p>See <a class="xref" href="#build.helpful-targets" title="13.17. Other helpful targets">Section 13.17, “Other helpful targets”</a>.</p>
1.106 rillig 2104: </div>
2105: </div>
1.148 asau 2106: <div class="chapter">
1.106 rillig 2107: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 2108: <a name="bulk"></a>Chapter 8. Creating binary packages for everything in pkgsrc (bulk
1.106 rillig 2109: builds)</h2></div></div></div>
2110: <div class="toc">
2111: <p><b>Table of Contents</b></p>
1.210 leot 2112: <dl class="toc">
1.267 rillig 2113: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.295 rillig 2114: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.267 rillig 2115: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
2116: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.293 rillig 2117: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
2118: <dd><dl>
1.294 rillig 2119: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
2120: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.296 rillig 2121: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
2122: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
2123: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
2124: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
2125: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
2126: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
2127: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
2128: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.293 rillig 2129: </dl></dd>
2130: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
2131: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.106 rillig 2132: </dl>
2133: </div>
1.290 gutterid 2134: <p>For a number of reasons, you may want to build binary packages
2135: for a large selected set of packages in pkgsrc, or even for all pkgsrc packages.
1.180 wiz 2136: For instance, when you have multiple machines that should run the same software,
2137: it is wasted time if they all build their packages themselves from source.
2138: Or you may want to build a list of packages you want and check them before
1.290 gutterid 2139: deploying onto production systems.
1.180 wiz 2140: There is a way of getting a set of binary packages:
1.290 gutterid 2141: the bulk build system, or pbulk ("p" stands for "parallel").
1.223 rillig 2142: This chapter describes how to set it up.</p>
1.148 asau 2143: <div class="sect1">
1.106 rillig 2144: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2145: <a name="bulk.pre"></a>8.1. Preparations</h2></div></div></div>
1.180 wiz 2146: <p>First of all, you have to decide whether you build all packages
2147: or a limited set of them. Full bulk builds usually consume a lot more resources,
2148: both space and time, than builds for some practical sets of packages.
1.290 gutterid 2149: A number of particularly heavy packages exist that are not actually
2150: interesting to a wide audience. (The approximate resource consumption for a
2151: full bulk build is given in section <a class="xref" href="#bulk.req" title="8.3. Requirements of a full bulk build">Section 8.3, “Requirements of a full bulk build”</a>.)
2152: For limited bulk builds you need to make a list of packages you want to build.
1.223 rillig 2153: Note that all their dependencies will be built, so you don't need to track them manually.
1.180 wiz 2154: </p>
2155: <p>During bulk builds various packages are installed and deinstalled
2156: in <code class="filename">/usr/pkg</code> (or whatever <code class="filename">LOCALBASE</code> is),
2157: so make sure that you don't need any package during the builds.
1.223 rillig 2158: Essentially, you should provide a fresh system, either a chroot environment
1.180 wiz 2159: or something even more restrictive, depending on what the operating system provides,
2160: or dedicate the whole physical machine.
2161: As a useful side effect this makes sure that bulk builds cannot
2162: break anything in your system. There have been numerous cases where
1.106 rillig 2163: certain packages tried to install files outside the
2164: <code class="filename">LOCALBASE</code> or wanted to edit some files in
1.180 wiz 2165: <code class="filename">/etc</code>.
2166: </p>
1.106 rillig 2167: </div>
1.148 asau 2168: <div class="sect1">
1.106 rillig 2169: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.295 rillig 2170: <a name="bulk.pbulk"></a>8.2. Running a bulk build</h2></div></div></div>
2171: <p>Running a bulk build works roughly as follows:</p>
1.148 asau 2172: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 2173: <li class="listitem"><p>First, build the pbulk infrastructure in a fresh pkgsrc location.</p></li>
2174: <li class="listitem"><p>Then, build each of the packages from a clean installation directory using the infrastructure.</p></li>
1.116 rillig 2175: </ul></div>
1.148 asau 2176: <div class="sect2">
1.116 rillig 2177: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 2178: <a name="bulk.pbulk.conf"></a>8.2.1. Configuration</h3></div></div></div>
1.223 rillig 2179: <p>To simplify configuration, we provide the helper script <code class="filename">mk/pbulk/pbulk.sh</code>.</p>
1.178 asau 2180: <p>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
2181: Configure network access to fetch distribution files.
1.223 rillig 2182: Create a user with name "pbulk".</p>
1.178 asau 2183: <p>Fetch and extract pkgsrc. Use a command like one of these:</p>
2184: <pre class="screen">
1.264 sevan 2185: <code class="prompt">#</code> <strong class="userinput"><code>(cd /usr && ftp -o - https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)</code></strong>
2186: <code class="prompt">#</code> <strong class="userinput"><code>(cd /usr && fetch -o - https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)</code></strong>
1.181 wiz 2187: <code class="prompt">#</code> <strong class="userinput"><code>(cd /usr && cvs -Q -z3 -d anoncvs@anoncvs.NetBSD.org:/cvsroot get -P pkgsrc)</code></strong>
1.178 asau 2188: </pre>
2189: <p>Or any other way that fits (e.g., curl, wget).</p>
2190: <p>Deploy and configure pbulk tools, e.g.:</p>
2191: <pre class="screen">
1.230 sevan 2192: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -n # use native make, no bootstrap kit needed (for use on NetBSD)</code></strong>
1.178 asau 2193: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -n -c mk.conf.frag # native, apply settings from given mk.conf fragment</code></strong>
2194: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build</code></strong>
2195: </pre>
2196: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2197: <h3 class="title">Note</h3>
2198: <p><code class="filename">mk.conf.frag</code> is a fragment of
2199: <code class="filename">mk.conf</code> that contains settings you want to
2200: apply to packages you build. For instance,</p>
2201: <pre class="programlisting">
1.223 rillig 2202: PKG_DEVELOPER= yes # perform more checks
2203: X11_TYPE= modular # use pkgsrc X11
2204: SKIP_LICENSE_CHECK= yes # accept all licences (useful
2205: # when building all packages)
1.178 asau 2206: </pre>
2207: </div>
2208: <p>If configured for limited list, replace the list in <code class="filename">/usr/pbulk/etc/pbulk.list</code>
1.223 rillig 2209: with your list of packages, one per line without empty lines or comments. E.g.:</p>
1.178 asau 2210: <pre class="programlisting">
2211: www/firefox
2212: mail/thunderbird
2213: misc/libreoffice4
2214: </pre>
1.179 asau 2215: <p>At this point you can also review configuration in <code class="filename">/usr/pbulk/etc</code>
2216: and make final amendments, if wanted.</p>
1.178 asau 2217: <p>Start it:</p>
2218: <pre class="screen">
2219: <code class="prompt">#</code> <strong class="userinput"><code>/usr/pbulk/bin/bulkbuild</code></strong>
2220: </pre>
2221: <p>After it finishes, you'll have <code class="filename">/mnt</code> filled with distribution files, binary packages, and reports,
2222: plain text summary in <code class="filename">/mnt/bulklog/meta/report.txt</code>
2223: </p>
2224: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2225: <h3 class="title">Note</h3>
2226: <p>The <code class="filename">pbulk.sh</code> script does not cover all possible use cases.
2227: While being ready to run, it serves as a good starting point to understand and build more complex setups.
2228: The script is kept small enough for better understanding.</p>
2229: </div>
2230: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2231: <h3 class="title">Note</h3>
2232: <p>The <code class="filename">pbulk.sh</code> script supports running
1.320 wiz 2233: unprivileged bulk build and helps configuring distributed bulk builds.
2234: Distributed bulk builds support either building in worker chroots
2235: (each node is a path to a different chroot)
2236: that replicate the target system, including the pbulk prefix,
2237: or remote machines (each node is
2238: an IP address that must be accessible over SSH without a password).</p>
1.178 asau 2239: </div>
1.106 rillig 2240: </div>
2241: </div>
1.148 asau 2242: <div class="sect1">
1.106 rillig 2243: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2244: <a name="bulk.req"></a>8.3. Requirements of a full bulk build</h2></div></div></div>
1.180 wiz 2245: <p>A complete bulk build requires lots of disk space. Some of the
2246: disk space can be read-only, some other must be writable. Some can be on
2247: remote filesystems (such as NFS) and some should be local. Some can be
2248: temporary filesystems, others must survive a sudden reboot.</p>
2249: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.320 wiz 2250: <li class="listitem"><p>70 GB for the distfiles (read-write, remote, temporary)</p></li>
2251: <li class="listitem"><p>60 GB for the binary packages (read-write, remote, permanent)</p></li>
1.180 wiz 2252: <li class="listitem"><p>1 GB for the pkgsrc tree (read-only, remote, permanent)</p></li>
2253: <li class="listitem"><p>5 GB for <code class="filename">LOCALBASE</code> (read-write, local, temporary)</p></li>
2254: <li class="listitem"><p>10 GB for the log files (read-write, remote, permanent)</p></li>
2255: <li class="listitem"><p>5 GB for temporary files (read-write, local, temporary)</p></li>
2256: </ul></div>
2257: </div>
2258: <div class="sect1">
2259: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.293 rillig 2260: <a name="bulk.var"></a>8.4. Bulk build variants</h2></div></div></div>
2261: <p>To ensure that pkgsrc packages work in different configurations, it
2262: makes sense to run non-default bulk builds from time to time. This
2263: section lists some ideas for bulk builds that intentionally let packages
2264: fail if they don't follow the pkgsrc style.</p>
2265: <div class="sect2">
2266: <div class="titlepage"><div><div><h3 class="title">
1.294 rillig 2267: <a name="bulk.var.confopt"></a>8.4.1. Detect unknown configure options</h3></div></div></div>
1.293 rillig 2268: <p>Add the following line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2269: <pre class="programlisting">
2270: GNU_CONFIGURE_STRICT= yes
2271: </pre>
2272: <p>When a package fails this additional check, the most common cause
2273: is that the configure option was valid for an older version of the
2274: package but does not apply anymore. In that case, just remove it.</p>
2275: </div>
2276: <div class="sect2">
2277: <div class="titlepage"><div><div><h3 class="title">
1.294 rillig 2278: <a name="bulk.var.comperr"></a>8.4.2. Detect classes of bugs by forcing compiler warnings</h3></div></div></div>
1.293 rillig 2279: <p>The job of a compiler is not restricted to producing executable
1.294 rillig 2280: code, most compilers also detect typical programming mistakes. The pkgsrc
2281: compiler wrappers make it easy to force compiler options when the package
2282: is built. This can be used to find typical bugs across all packages that
2283: are in pkgsrc. By reporting these bugs upstream, the packages will be
2284: more reliable with the next updates.</p>
2285: <p>Add some of the following lines to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.293 rillig 2286: <pre class="programlisting">
2287: CFLAGS+= -Werror=char-subscripts
1.294 rillig 2288: CFLAGS+= -Werror=implicit-function-declaration
1.293 rillig 2289: </pre>
1.294 rillig 2290: <p>When a package fails to build using these stricter compiler
2291: options, document the circumstances in which the compiler produced the
2292: error message. This includes:</p>
1.293 rillig 2293: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
2294: <li class="listitem"><p>The platform
2295: (<code class="varname">MACHINE_PLATFORM</code>)</p></li>
2296: <li class="listitem"><p>The source file</p></li>
2297: <li class="listitem"><p>An excerpt of the code. GCC and Clang already do this as
2298: part of the diagnostic.</p></li>
1.294 rillig 2299: <li class="listitem"><p>The exact error message from the compiler.</p></li>
1.293 rillig 2300: </ul></div>
2301: <p>If a package produces these error messages, but the package is
1.294 rillig 2302: fine, record this in your local <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, like this, to skip this check
2303: in the next builds:</p>
1.293 rillig 2304: <pre class="programlisting">
1.294 rillig 2305: .if ${PKGPATH} == category/package
1.293 rillig 2306: # Version ${VERSION} failed on ${MACHINE_PLATFORM}:
2307: # error message
2308: # code
1.294 rillig 2309: # Reason why the code does not need to be fixed.
1.293 rillig 2310: BUILDLINK_TRANSFORM+= rm:-Werror=char-subscripts
1.294 rillig 2311: .endif
1.293 rillig 2312: </pre>
2313: <p>If the error messages from the compiler are valid and the code
1.294 rillig 2314: needs to be fixed, prepare a local patch (see
2315: <code class="varname">LOCALPATCHES</code>) and report the bug to the upstream
2316: authors of the package, providing them with the information you collected
2317: above.</p>
2318: <p>Patches that are not essential for the package to work should only
2319: be reported upstream but not committed to pkgsrc, to make future updates
2320: easier.</p>
1.293 rillig 2321: </div>
2322: <div class="sect2">
2323: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2324: <a name="bulk.var.builderr"></a>8.4.3. Force compiler options only in the build phase</h3></div></div></div>
2325: <p>When adding custom compiler flags via <code class="varname">CFLAGS</code>,
2326: these apply to all phases of the package build process. Especially in the
2327: configure phase, adding <code class="literal">-Werror</code> leads to wrong
2328: decisions. The GNU configure scripts feed many small test programs to the
2329: C compiler to see whether certain headers are available, functions are
2330: defined in a library and programs can be run. In many cases these
2331: programs would not survive a strict compiler run with <code class="literal">-Wall
2332: -Wextra -Werror</code>.</p>
2333: <p>The pkgsrc infrastructure is flexible enough to support compiler
2334: options being added between the <code class="literal">configure</code> and
2335: <code class="literal">build</code> phases. It's a little more complicated than the
2336: other examples in this section but still easy enough.</p>
2337: <p>The basic idea is to use the pkgsrc compiler wrapper to inject the
2338: desired compiler options. The compiler wrapper's original task is to hide
2339: unwanted directories of include files and to normalize compiler options.
2340: It does this by wrapping the compiler command and rewriting the command
2341: line. To see this in action, run <span class="command"><strong>bmake patch</strong></span> in a
2342: package directory and examine the
2343: <code class="filename">work/.cwrappers/config</code> directory. It contains
2344: individual configurations for the C compiler and the related tools. The
2345: plan is to find a hook between the configure and build phases, and to
2346: modify these configuration files at that point.</p>
2347: <p>To find this hook, have a look at
2348: <code class="filename">mk/build/build.mk</code>, which contains among others the
2349: <code class="literal">pre-build-checks-hook</code>. The word
2350: <code class="literal">checks</code> doesn't quite fit, but the
2351: <code class="literal">pre-build-hook</code> sounds good enough.</p>
2352: <p>The code to be included in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> is:</p>
2353: <pre class="programlisting">
2354: # Just a few example options.
2355: BUILD_ONLY_CFLAGS= -Wall -Werror -O2 -DTEMPDIR='"/tmp"'
2356:
2357: .if ${BUILD_ONLY_CFLAGS:U:M*}
2358: pre-build-checks-hook: add-build-only-cflags
2359:
2360: add-build-only-cflags: .PHONY
2361: ${RUN} cd ${CWRAPPERS_CONFIG_DIR}; \
2362: ${TEST} ! -f ${.TARGET} || exit 0; \
2363: for flag in ${BUILD_ONLY_CFLAGS}; do \
2364: ${ECHO} "append=$$flag" >> cc; \
2365: done; \
2366: > ${.TARGET}
2367: .endif
2368: </pre>
2369: <p>(When editing the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, make sure that the commands of the
2370: <code class="literal">add-build-only-cflags</code> target are indented with a tab,
2371: not with spaces.)</p>
2372: <p>The condition in the <code class="literal">.if</code> statement contains the
2373: <code class="literal">:U</code> modifier to prevent parse errors if the variable
2374: should be undefined, possibly because it is only defined for a subset of
2375: the packages. The <code class="literal">:M*</code> modifier ensures that there is
2376: at least one compiler option, to prevent a syntax error in the shell
2377: parser.</p>
2378: <p>The code around the <code class="literal">${.TARGET}</code> variable ensures
2379: that the additional compiler options are only appended once, even if
2380: <span class="command"><strong>bmake build</strong></span> is run multiple times. To do this, it
2381: creates a marker file.</p>
2382: <p>To verify that this setup works, run <span class="command"><strong>bmake
2383: configure</strong></span> in a package directory. Up to now, everything works
2384: as usual. Examine the directory
2385: <code class="filename">work/.cwrappers/config</code> to see that the compiler
2386: options from <code class="varname">BUILD_ONLY_CFLAGS</code> are not yet added to
2387: the file <code class="filename">cc</code>. Examine the tail of the
2388: <code class="filename">work/.work.log</code> file to see that the normal compiler
2389: options are used.</p>
2390: <p>Now run <span class="command"><strong>bmake build</strong></span>. This will append the
2391: options to the file <code class="filename">cc</code> and will create the marker
2392: file in the same directory. After that, the build starts as usual, but
2393: with the added compiler options. Examine the tail of the file
2394: <code class="filename">work/.work.log</code> to see that the lines starting with
2395: <code class="literal">[*]</code> don't contain the compiler options, but the
2396: corresponding lines starting with <code class="literal"><.></code> do end
2397: with these options.</p>
2398: <p>Building packages using this setup variant and fixing the resulting
2399: bugs is the same as in <a class="xref" href="#bulk.var.comperr" title="8.4.2. Detect classes of bugs by forcing compiler warnings">Section 8.4.2, “Detect classes of bugs by forcing compiler warnings”</a>.</p>
2400: </div>
2401: <div class="sect2">
2402: <div class="titlepage"><div><div><h3 class="title">
2403: <a name="bulk.var.dirs"></a>8.4.4. Use custom directories</h3></div></div></div>
1.293 rillig 2404: <p>Some directories like <code class="varname">PREFIX</code>,
2405: <code class="varname">VARBASE</code>, <code class="varname">PKG_SYSCONFDIR</code>,
2406: <code class="varname">PKGMANDIR</code>, <code class="varname">PKG_INFODIR</code> can be
2407: configured in pkgsrc. Set these to arbitrary paths during bootstrap or
2408: afterwards in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2409: <pre class="programlisting">
2410: PREFIX= /a-random-uuid
2411: PKG_SYSCONFDIR= /a-random-uuid
2412: VARBASE= /a-random-uuid
2413: PKGMANDIR= a-random-uuid
2414: PKG_INFODIR= a-random-uuid
2415: </pre>
2416: </div>
2417: <div class="sect2">
2418: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2419: <a name="bulk.var.warn"></a>8.4.5. Turn warnings into errors</h3></div></div></div>
1.293 rillig 2420: <p>When building a package, warnings are typically ignored since they
2421: just flow by and do not cause the build to fail immediately. To find
2422: these warnings, redefine them to errors in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2423: <pre class="programlisting">
2424: DELAYED_WARNING_MSG= ${DELAYED_ERROR_MSG} "(was warning)"
2425: WARNING_MSG= ${FAIL_MSG} "(was warning)"
2426: </pre>
2427: <p>(There are many more classes of warnings in pkgsrc, and most of
2428: them can be redefined with a simple definition like above.</p>
1.294 rillig 2429: <p>If a package suggests to add <code class="varname">USE_TOOLS+=perl</code> to
1.293 rillig 2430: the package Makefile, research whether the package actually needs Perl.
2431: If it does, add <code class="varname">USE_TOOLS+=perl</code> to the package
2432: Makefile, and if it doesn't, add
2433: <code class="varname">TOOLS_BROKEN+=perl</code>.</p>
2434: </div>
2435: <div class="sect2">
2436: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2437: <a name="bulk.var.pkglint"></a>8.4.6. Reject packages for which pkglint reports errors</h3></div></div></div>
1.293 rillig 2438: <p>Using pkglint as part of the regular build process is mostly a
2439: waste of time. If you want to fix some of the warnings, just run pkglint
2440: recursively on the whole pkgsrc tree. This will take a few minutes (up to
2441: 10), which is much faster than a complete bulk build.</p>
2442: </div>
2443: <div class="sect2">
2444: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2445: <a name="bulk.var.strings"></a>8.4.7. Reject packages that contain forbidden strings</h3></div></div></div>
1.293 rillig 2446: <p>To ensure that the binary packages don't contain references to the
2447: build directory, there is already <code class="varname">CHECK_WRKREF</code>. If
2448: that variable includes the item <code class="literal">extra</code>, it is
2449: possible to define additional patterns that must not appear in any
2450: installed file. This is specified in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2451: <pre class="programlisting">
2452: CHECK_WRKREF= extra
2453: CHECK_WRKREF_EXTRA_DIRS+= /usr/local
2454: CHECK_WRKREF_EXTRA_DIRS+= /usr/pkg
2455: CHECK_WRKREF_EXTRA_DIRS+= @[A-Z][A-Z]*@
2456: </pre>
2457: <p>The above patterns will probably generate many false positives,
2458: therefore the results need to be taken with a grain of salt.</p>
2459: </div>
2460: <div class="sect2">
2461: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2462: <a name="bulk.var.test"></a>8.4.8. Reject packages whose self-test fails</h3></div></div></div>
1.293 rillig 2463: <p>To run the test suites that come with each package, add this line
2464: to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2465: <pre class="programlisting">
2466: PKGSRC_RUN_TEST= yes
2467: </pre>
2468: <p>Be prepared that even the most basic packages fail this test. When
2469: doing a bulk build with this, it will often abort in the early phase
2470: where the packages are scanned for their dependencies since there are
2471: cyclic dependencies. There is still a lot to do in this area.</p>
2472: </div>
2473: <div class="sect2">
2474: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2475: <a name="bulk.var.shvar"></a>8.4.9. Reject packages that use undefined shell variables</h3></div></div></div>
1.293 rillig 2476: <p>To catch typos in the shell snippets from the Makefile fragments,
2477: add the <code class="literal">-u</code> flag to most of the commands by adding this
2478: line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2479: <pre class="programlisting">
2480: RUN= @set -eu;
2481: </pre>
1.296 rillig 2482: <p>After that, ensure that none of the bulk build log files (even
2483: those for successfully built packages) contains the string
2484: <code class="literal">parameter not set</code> or whatever error message the
2485: command <span class="command"><strong>sh -ceu '$undefined'</strong></span> outputs.</p>
1.293 rillig 2486: <p>See <code class="filename">mk/misc/common.mk</code> for the existing
2487: definition.</p>
2488: </div>
2489: <div class="sect2">
2490: <div class="titlepage"><div><div><h3 class="title">
1.296 rillig 2491: <a name="bulk.var.quiet"></a>8.4.10. Turn off verbose logging</h3></div></div></div>
1.293 rillig 2492: <p>The build logs of a package are often quite long. This allows error
2493: messages or other interesting details to hide between the noise. To make
2494: the actual error message stand out more, add these lines to
2495: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2496: <pre class="programlisting">
2497: GNU_CONFIGURE_QUIET= yes
2498: MAKE_FLAGS+= -s
2499: </pre>
2500: <p>The <code class="literal">-s</code> option works for both GNU Make and BSD
2501: Make. On exotic platforms with their own make, it may be a little
2502: different.</p>
2503: </div>
2504: </div>
2505: <div class="sect1">
2506: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2507: <a name="creating-cdroms"></a>8.5. Creating a multiple CD-ROM packages collection</h2></div></div></div>
1.87 wiz 2508: <p>After your pkgsrc bulk-build has completed, you may wish to
2509: create a CD-ROM set of the resulting binary packages to assist
2510: in installing packages on other machines. The
1.322 leot 2511: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/cdpack/index.html" target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides
1.87 wiz 2512: a simple tool for creating the ISO 9660 images.
1.110 hubertf 2513: <span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a
1.87 wiz 2514: way that keeps all the dependencies for a given package on the same
2515: CD as that package.</p>
1.148 asau 2516: <div class="sect2">
1.75 rillig 2517: <div class="titlepage"><div><div><h3 class="title">
1.293 rillig 2518: <a name="cdpack-example"></a>8.5.1. Example of cdpack</h3></div></div></div>
1.87 wiz 2519: <p>Complete documentation for cdpack is found in the cdpack(1)
2520: man page. The following short example assumes that the binary
2521: packages are left in
2522: <code class="filename">/usr/pkgsrc/packages/All</code> and that
2523: sufficient disk space exists in <code class="filename">/u2</code> to
2524: hold the ISO 9660 images.</p>
2525: <pre class="screen">
2526: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /u2/images</code></strong>
1.75 rillig 2527: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong>
1.87 wiz 2528: <code class="prompt">#</code> <strong class="userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong>
2529: </pre>
2530: <p>If you wish to include a common set of files
2531: (<code class="filename">COPYRIGHT</code>, <code class="filename">README</code>,
2532: etc.) on each CD in the collection, then you need to create a
1.290 gutterid 2533: directory which contains these files, e.g.:</p>
1.87 wiz 2534: <pre class="screen">
2535: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common</code></strong>
1.75 rillig 2536: <code class="prompt">#</code> <strong class="userinput"><code>echo "This is a README" > /tmp/common/README</code></strong>
2537: <code class="prompt">#</code> <strong class="userinput"><code>echo "Another file" > /tmp/common/COPYING</code></strong>
2538: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common/bin</code></strong>
2539: <code class="prompt">#</code> <strong class="userinput"><code>echo "#!/bin/sh" > /tmp/common/bin/myscript</code></strong>
2540: <code class="prompt">#</code> <strong class="userinput"><code>echo "echo Hello world" >> /tmp/common/bin/myscript</code></strong>
1.87 wiz 2541: <code class="prompt">#</code> <strong class="userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong>
2542: </pre>
1.75 rillig 2543: <p>Now create the images:</p>
2544: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong></pre>
1.76 rillig 2545: <p>Each image will contain <code class="filename">README</code>,
1.87 wiz 2546: <code class="filename">COPYING</code>, and <code class="filename">bin/myscript</code>
2547: in their root directories.</p>
1.75 rillig 2548: </div>
2549: </div>
2550: </div>
1.148 asau 2551: <div class="chapter">
1.75 rillig 2552: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 2553: <a name="files"></a>Chapter 9. Directory layout of the installed files</h2></div></div></div>
1.90 rillig 2554: <div class="toc">
2555: <p><b>Table of Contents</b></p>
1.210 leot 2556: <dl class="toc">
1.267 rillig 2557: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
2558: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
1.90 rillig 2559: </dl>
2560: </div>
2561: <p>The files that are installed by pkgsrc are organized in a way that
2562: is similar to what you find in the <code class="filename">/usr</code> directory
2563: of the base system. But some details are different. This is because
2564: pkgsrc initially came from FreeBSD and had adopted its file system
2565: hierarchy. Later it was largely influenced by NetBSD. But no matter
2566: which operating system you are using pkgsrc with, you can expect the
2567: same layout for pkgsrc.</p>
1.91 rillig 2568: <p>There are mainly four root directories for pkgsrc, which are all
2569: configurable in the <code class="filename">bootstrap/bootstrap</code> script.
2570: When pkgsrc has been installed as root, the default locations
2571: are:</p>
2572: <pre class="programlisting">
1.100 rillig 2573: LOCALBASE= /usr/pkg
2574: PKG_SYSCONFBASE= /usr/pkg/etc
2575: VARBASE= /var
1.231 sevan 2576: PKG_DBDIR= /usr/pkg/pkgdb
1.91 rillig 2577: </pre>
2578: <p>In unprivileged mode (when pkgsrc has been installed as any other
2579: user), the default locations are:</p>
2580: <pre class="programlisting">
1.100 rillig 2581: LOCALBASE= ${HOME}/pkg
2582: PKG_SYSCONFBASE= ${HOME}/pkg/etc
2583: VARBASE= ${HOME}/pkg/var
1.231 sevan 2584: PKG_DBDIR= ${HOME}/pkg/pkgdb
1.91 rillig 2585: </pre>
2586: <p>What these four directories are for, and what they look like is
2587: explained below.</p>
1.148 asau 2588: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 2589: <li class="listitem"><p><code class="varname">LOCALBASE</code> corresponds to the
1.90 rillig 2590: <code class="filename">/usr</code> directory in the base system. It is the
1.128 wiz 2591: <span class="quote">“<span class="quote">main</span>”</span> directory where the files are installed and contains
1.90 rillig 2592: the well-known subdirectories like <code class="filename">bin</code>,
2593: <code class="filename">include</code>, <code class="filename">lib</code>,
2594: <code class="filename">share</code> and
2595: <code class="filename">sbin</code>.</p></li>
1.128 wiz 2596: <li class="listitem"><p><code class="varname">VARBASE</code> corresponds to
1.90 rillig 2597: <code class="filename">/var</code> in the base system. Some programs (especially
2598: games, network daemons) need write access to it during normal
2599: operation.</p></li>
1.128 wiz 2600: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR</code> corresponds to
1.90 rillig 2601: <code class="filename">/etc</code> in the base system. It contains configuration
1.110 hubertf 2602: files of the packages, as well as pkgsrc's <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
1.90 rillig 2603: itself.</p></li>
2604: </ul></div>
1.148 asau 2605: <div class="sect1">
1.90 rillig 2606: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2607: <a name="files.localbase"></a>9.1. File system layout in <code class="literal">${LOCALBASE}</code>
1.93 rillig 2608: </h2></div></div></div>
1.90 rillig 2609: <p>The following directories exist in a typical pkgsrc installation
1.91 rillig 2610: in <code class="filename">${LOCALBASE}</code>.</p>
1.148 asau 2611: <div class="variablelist"><dl class="variablelist">
1.90 rillig 2612: <dt><span class="term"><code class="filename">bin</code></span></dt>
2613: <dd><p>Contains executable programs that are intended to be
2614: directly used by the end user.</p></dd>
2615: <dt><span class="term"><code class="filename">emul</code></span></dt>
2616: <dd><p>Contains files for the emulation layers of various other
2617: operating systems, especially for
2618: NetBSD.</p></dd>
2619: <dt><span class="term"><code class="filename">etc</code> (the usual location of
2620: <code class="filename">${PKG_SYSCONFDIR}</code>)</span></dt>
2621: <dd><p>Contains
2622: the configuration files.</p></dd>
2623: <dt><span class="term"><code class="filename">include</code></span></dt>
2624: <dd><p>Contains headers for the C and C++ programming
2625: languages.</p></dd>
2626: <dt><span class="term"><code class="filename">info</code></span></dt>
2627: <dd><p>Contains GNU info files of various
2628: packages.</p></dd>
2629: <dt><span class="term"><code class="filename">lib</code></span></dt>
2630: <dd><p>Contains shared and static
2631: libraries.</p></dd>
2632: <dt><span class="term"><code class="filename">libdata</code></span></dt>
2633: <dd><p>Contains data files that don't change after
2634: installation. Other data files belong into
2635: <code class="filename">${VARBASE}</code>.</p></dd>
2636: <dt><span class="term"><code class="filename">libexec</code></span></dt>
2637: <dd><p>Contains programs that are not intended to be used by
2638: end users, such as helper programs or network
2639: daemons.</p></dd>
2640: <dt><span class="term"><code class="filename">libexec/cgi-bin</code></span></dt>
2641: <dd><p>Contains programs that are intended to be executed as
2642: CGI scripts by a web server.</p></dd>
2643: <dt><span class="term"><code class="filename">man</code> (the usual value of
2644: <code class="filename">${PKGMANDIR}</code>)</span></dt>
2645: <dd><p>Contains brief
2646: documentation in form of manual pages.</p></dd>
2647: <dt><span class="term"><code class="filename">sbin</code></span></dt>
2648: <dd><p>Contains programs that are intended to be used only by
2649: the super-user.</p></dd>
2650: <dt><span class="term"><code class="filename">share</code></span></dt>
2651: <dd><p>Contains platform-independent data files that don't
2652: change after installation.</p></dd>
2653: <dt><span class="term"><code class="filename">share/doc</code></span></dt>
2654: <dd><p>Contains documentation files provided by the
2655: packages.</p></dd>
2656: <dt><span class="term"><code class="filename">share/examples</code></span></dt>
2657: <dd><p>Contains example files provided by the packages. Among
2658: others, the original configuration files are saved here and copied to
2659: <code class="filename">${PKG_SYSCONFDIR}</code> during
2660: installation.</p></dd>
2661: <dt><span class="term"><code class="filename">share/examples/rc.d</code></span></dt>
2662: <dd><p>Contains the original files for rc.d
2663: scripts.</p></dd>
2664: <dt><span class="term"><code class="filename">var</code> (the usual location of
2665: <code class="filename">${VARBASE}</code>)</span></dt>
2666: <dd><p>Contains files
2667: that may be modified after
2668: installation.</p></dd>
2669: </dl></div>
2670: </div>
1.148 asau 2671: <div class="sect1">
1.90 rillig 2672: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2673: <a name="files.varbase"></a>9.2. File system layout in <code class="literal">${VARBASE}</code>
1.93 rillig 2674: </h2></div></div></div>
1.148 asau 2675: <div class="variablelist"><dl class="variablelist">
1.90 rillig 2676: <dt><span class="term"><code class="filename">db/pkg</code> (the usual location of
2677: <code class="filename">${PKG_DBDIR}</code>)</span></dt>
2678: <dd><p>Contains
2679: information about the currently installed
2680: packages.</p></dd>
2681: <dt><span class="term"><code class="filename">games</code></span></dt>
2682: <dd><p>Contains highscore
2683: files.</p></dd>
2684: <dt><span class="term"><code class="filename">log</code></span></dt>
2685: <dd><p>Contains log files.</p></dd>
2686: <dt><span class="term"><code class="filename">run</code></span></dt>
2687: <dd><p>Contains informational files about daemons that are
2688: currently running.</p></dd>
2689: </dl></div>
2690: </div>
2691: </div>
1.148 asau 2692: <div class="chapter">
1.90 rillig 2693: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 2694: <a name="faq"></a>Chapter 10. Frequently Asked Questions</h2></div></div></div>
1.75 rillig 2695: <div class="toc">
2696: <p><b>Table of Contents</b></p>
1.210 leot 2697: <dl class="toc">
1.267 rillig 2698: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
2699: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
2700: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
2701: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
2702: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">10.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
2703: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
2704: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
2705: <dt><span class="sect1"><a href="#passive-ftp">10.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
2706: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
2707: <dt><span class="sect1"><a href="#tmac.andoc-missing">10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.128 wiz 2708: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.267 rillig 2709: <dt><span class="sect1"><a href="#bsd.own.mk-missing">10.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
1.336 nia 2710: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.267 rillig 2711: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
2712: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
2713: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
2714: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
2715: <dt><span class="sect1"><a href="#faq.rcs-conflicts">10.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</a></span></dt>
1.75 rillig 2716: </dl>
2717: </div>
2718: <p>This section contains hints, tips & tricks on special things in
2719: pkgsrc that we didn't find a better place for in the previous chapters, and
2720: it contains items for both pkgsrc users and developers.</p>
1.148 asau 2721: <div class="sect1">
1.75 rillig 2722: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2723: <a name="mailing-list-pointers"></a>10.1. Are there any mailing lists for pkg-related discussion?</h2></div></div></div>
1.75 rillig 2724: <p>The following mailing lists may be of interest to pkgsrc users:</p>
1.148 asau 2725: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 2726: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-users" target="_top">pkgsrc-users</a>:
1.78 rillig 2727: This is a general purpose list for most issues regarding
2728: pkgsrc, regardless of platform, e.g. soliciting user help
2729: for pkgsrc configuration, unexpected build failures, using
2730: particular packages, upgrading pkgsrc installations,
2731: questions regarding the pkgsrc release branches, etc. General announcements or
2732: proposals for changes that impact the pkgsrc user community,
2733: e.g. major infrastructure changes, new features, package
2734: removals, etc., may also be posted.</p></li>
1.289 leot 2735: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-bulk" target="_top">pkgsrc-bulk</a>:
1.75 rillig 2736: A list where the results of pkgsrc bulk builds are sent and
2737: discussed.</p></li>
1.289 leot 2738: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-changes" target="_top">pkgsrc-changes</a>:
1.75 rillig 2739: This list is for those who are interested in getting a
2740: commit message for every change committed to pkgsrc. It is
2741: also available in digest form, meaning one daily message
2742: containing all commit messages for changes to the package
2743: source tree in that 24 hour period.</p></li>
2744: </ul></div>
2745: <p>To subscribe, do:</p>
2746: <pre class="programlisting">
1.100 rillig 2747: <code class="prompt">%</code> echo subscribe <em class="replaceable"><code>listname</code></em> | mail majordomo@NetBSD.org
1.75 rillig 2748: </pre>
2749: <p>Archives for all these mailing lists are available from
1.289 leot 2750: <a class="ulink" href="https://mail-index.NetBSD.org/" target="_top">https://mail-index.NetBSD.org/</a>.</p>
1.75 rillig 2751: </div>
1.148 asau 2752: <div class="sect1">
1.75 rillig 2753: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2754: <a name="faq-pkgtools"></a>10.2. Utilities for package management (pkgtools)</h2></div></div></div>
1.80 rillig 2755: <p>The directory <code class="filename">pkgsrc/pkgtools</code> contains
1.75 rillig 2756: a number of useful utilities for both users and developers of pkgsrc. This
1.233 sevan 2757: section attempts only to make the reader aware of some of the utilities and when
1.75 rillig 2758: they might be useful, and not to duplicate the documentation that comes
2759: with each package.</p>
2760: <p>Utilities used by pkgsrc (automatically installed when needed):</p>
1.322 leot 2761: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/index.html" target="_top"><code class="filename">pkgtools/x11-links</code></a>:
1.75 rillig 2762: Symlinks for use by buildlink.</p></li></ul></div>
2763: <p>OS tool augmentation (automatically installed when needed):</p>
1.148 asau 2764: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 2765: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/digest/index.html" target="_top"><code class="filename">pkgtools/digest</code></a>:
1.233 sevan 2766: Calculates various kinds of checksums (including SHA3).</p></li>
1.322 leot 2767: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libnbcompat/index.html" target="_top"><code class="filename">pkgtools/libnbcompat</code></a>:
1.75 rillig 2768: Compatibility library for pkgsrc tools.</p></li>
1.322 leot 2769: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/index.html" target="_top"><code class="filename">pkgtools/mtree</code></a>: Installed on
1.87 wiz 2770: non-BSD systems due to lack of native mtree.</p></li>
1.322 leot 2771: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/index.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a>:
1.75 rillig 2772: Up-to-date replacement for
1.76 rillig 2773: <code class="filename">/usr/sbin/pkg_install</code>, or for use on operating
1.75 rillig 2774: systems where pkg_install is not present.</p></li>
2775: </ul></div>
2776: <p>Utilities used by pkgsrc (not automatically installed):</p>
1.148 asau 2777: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 2778: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/index.html" target="_top"><code class="filename">pkgtools/pkg_tarup</code></a>:
1.75 rillig 2779: Create a binary package from an
1.110 hubertf 2780: already-installed package. Used by <span class="command"><strong>make replace</strong></span> to
1.75 rillig 2781: save the old package.</p></li>
1.322 leot 2782: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/dfdisk/index.html" target="_top"><code class="filename">pkgtools/dfdisk</code></a>:
1.75 rillig 2783: Adds extra functionality to pkgsrc, allowing it to fetch distfiles
2784: from multiple locations. It currently supports the following
2785: methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li>
1.322 leot 2786: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/index.html" target="_top"><code class="filename">devel/cpuflags</code></a>: Determine
1.117 jnemeth 2787: the best compiler flags to optimise code for your current
1.128 wiz 2788: CPU and compiler. </p></li>
1.75 rillig 2789: </ul></div>
2790: <p>Utilities for keeping track of installed packages, being up to date,
2791: etc:</p>
1.148 asau 2792: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 2793: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgin/index.html" target="_top"><code class="filename">pkgtools/pkgin</code></a>: A package
1.173 wiz 2794: update tool similar to apt(1). Download, install, and upgrade
2795: binary packages easily.</p></li>
1.322 leot 2796: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/index.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a>: Reports on
1.75 rillig 2797: packages whose installed versions do not match the latest pkgsrc
2798: entries.</p></li>
1.322 leot 2799: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/index.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a>: Makes
1.75 rillig 2800: dependency graphs of packages, to aid in choosing a strategy for
2801: updating.</p></li>
1.322 leot 2802: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdepgraph/index.html" target="_top"><code class="filename">pkgtools/pkgdepgraph</code></a>: Makes
2803: graphs from the output of <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/index.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a> (uses graphviz).</p></li>
2804: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/index.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>: The
1.112 weinem 2805: pkglint(1) program checks a pkgsrc entry for errors.</p></li>
1.322 leot 2806: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/index.html" target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a>: The lintpkgsrc(1) program
1.75 rillig 2807: does various checks on the complete pkgsrc system.</p></li>
1.322 leot 2808: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgsurvey/index.html" target="_top"><code class="filename">pkgtools/pkgsurvey</code></a>: Report what
1.75 rillig 2809: packages you have installed.</p></li>
2810: </ul></div>
2811: <p>Utilities for people maintaining or creating individual packages:</p>
1.148 asau 2812: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 2813: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a>: Automate
1.75 rillig 2814: making and maintaining patches for a package (includes pkgdiff,
2815: pkgvi, mkpatches, etc.).</p></li>
1.322 leot 2816: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/index.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>: Aids in
1.75 rillig 2817: converting to pkgsrc.</p></li>
2818: </ul></div>
2819: <p>Utilities for people maintaining pkgsrc (or: more obscure pkg
2820: utilities)</p>
1.148 asau 2821: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 2822: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_comp/index.html" target="_top"><code class="filename">pkgtools/pkg_comp</code></a>: Build
1.75 rillig 2823: packages in a chrooted area.</p></li>
1.322 leot 2824: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libkver/index.html" target="_top"><code class="filename">pkgtools/libkver</code></a>: Spoof
1.75 rillig 2825: kernel version for chrooted cross builds.</p></li>
2826: </ul></div>
2827: </div>
1.148 asau 2828: <div class="sect1">
1.75 rillig 2829: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2830: <a name="non-root-pkgsrc"></a>10.3. How to use pkgsrc as non-root</h2></div></div></div>
1.219 rillig 2831: <p>To install packages from source as a non-root user, download
1.267 rillig 2832: pkgsrc as described in <a class="xref" href="#getting" title="Chapter 3. Where to get pkgsrc and how to keep it up-to-date">Chapter 3, <i>Where to get pkgsrc and how to keep it up-to-date</i></a>, cd into that
1.219 rillig 2833: directory and run the command <span class="command"><strong>./bootstrap/bootstrap
2834: --unprivileged</strong></span>.</p>
2835: <p>This will install the binary part of pkgsrc to
2836: <code class="filename">~/pkg</code> and put the pkgsrc configuration <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
2837: into <code class="filename">~/pkg/etc</code>.</p>
2838: <p>For more details, see <code class="filename">mk/unprivileged.mk</code>.</p>
1.75 rillig 2839: </div>
1.148 asau 2840: <div class="sect1">
1.75 rillig 2841: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2842: <a name="resume-transfers"></a>10.4. How to resume transfers when fetching distfiles?</h2></div></div></div>
1.75 rillig 2843: <p>By default, resuming transfers in pkgsrc is disabled, but you can
2844: enable this feature by adding the option
2845: <code class="varname">PKG_RESUME_TRANSFERS=YES</code> into
1.110 hubertf 2846: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. If, during a fetch step, an incomplete
1.75 rillig 2847: distfile is found, pkgsrc will try to resume it.</p>
2848: <p>You can also
1.168 wiz 2849: use a different program than the platform default program by changing the
1.117 jnemeth 2850: <code class="varname">FETCH_USING</code> variable. You can specify the program by
2851: using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
2852: by using the value manual. A value of custom disables the system defaults
2853: and dependency tracking for the fetch program. In that case you have to
2854: provide <code class="varname">FETCH_CMD</code>, <code class="varname">FETCH_BEFORE_ARGS</code>,
2855: <code class="varname">FETCH_RESUME_ARGS</code>, <code class="varname">FETCH_OUTPUT_ARGS</code>,
2856: <code class="varname">FETCH_AFTER_ARGS</code>.</p>
1.75 rillig 2857: <p>For example, if you want to use
1.117 jnemeth 2858: <code class="filename">wget</code> to download, you'll have to use something
1.75 rillig 2859: like:</p>
2860: <pre class="programlisting">
1.223 rillig 2861: FETCH_USING= wget
1.1 grant 2862: </pre>
1.75 rillig 2863: </div>
1.148 asau 2864: <div class="sect1">
1.75 rillig 2865: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2866: <a name="x.org-from-pkgsrc"></a>10.5. How can I install/use modular X.org from pkgsrc?</h2></div></div></div>
1.103 wiz 2867: <p>If you want to use modular X.org from pkgsrc instead of your system's own X11
1.76 rillig 2868: (<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...)
1.75 rillig 2869: you will have to add the following line into
1.110 hubertf 2870: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.75 rillig 2871: <pre class="programlisting">
1.103 wiz 2872: X11_TYPE=modular
1.1 grant 2873: </pre>
1.75 rillig 2874: </div>
1.148 asau 2875: <div class="sect1">
1.75 rillig 2876: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2877: <a name="fetch-behind-firewall"></a>10.6. How to fetch files from behind a firewall</h2></div></div></div>
1.75 rillig 2878: <p>If you are sitting behind a firewall which does not allow direct
2879: connections to Internet hosts (i.e. non-NAT), you may specify the
2880: relevant proxy hosts. This is done using an environment variable in the
2881: form of a URL, e.g. in Amdahl, the machine
1.128 wiz 2882: <span class="quote">“<span class="quote">orpheus.amdahl.com</span>”</span> is one of the firewalls, and it uses
1.75 rillig 2883: port 80 as the proxy port number. So the proxy environment variables
2884: are:</p>
2885: <pre class="programlisting">
1.100 rillig 2886: ftp_proxy=ftp://orpheus.amdahl.com:80/
2887: http_proxy=http://orpheus.amdahl.com:80/
1.1 grant 2888: </pre>
1.75 rillig 2889: </div>
1.148 asau 2890: <div class="sect1">
1.75 rillig 2891: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2892: <a name="fetch-https"></a>10.7. How to fetch files from HTTPS sites</h2></div></div></div>
1.173 wiz 2893: <p>Some fetch tools are not prepared to support HTTPS by default
2894: (for example, the one in NetBSD 6.0), or the one installed by the
2895: pkgsrc bootstrap (to avoid an openssl dependency that low in the
2896: dependency graph).</p>
2897: <p>Usually you won't notice, because distribution files are
2898: mirrored weekly to <span class="quote">“<span class="quote">ftp.NetBSD.org</span>”</span>, but that might not
2899: be often enough if you are following pkgsrc-current. In that case, set
2900: <code class="varname">FETCH_USING</code> in your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file to
2901: <span class="quote">“<span class="quote">curl</span>”</span> or <span class="quote">“<span class="quote">wget</span>”</span>, which are both compiled
2902: with HTTPS support by default. Of course, these tools need to be
2903: installed before you can use them this way.</p>
2904: </div>
2905: <div class="sect1">
2906: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2907: <a name="passive-ftp"></a>10.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</h2></div></div></div>
1.75 rillig 2908: <p>This depends on which utility is used to retrieve distfiles. From
1.76 rillig 2909: <code class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned
1.75 rillig 2910: the first available command from the following list:</p>
1.148 asau 2911: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 2912: <li class="listitem"><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li>
2913: <li class="listitem"><p><code class="filename">/usr/bin/ftp</code></p></li>
1.75 rillig 2914: </ul></div>
2915: <p>On a default NetBSD installation, this will be
1.76 rillig 2916: <code class="filename">/usr/bin/ftp</code>, which automatically tries passive
1.75 rillig 2917: connections first, and falls back to active connections if the server
2918: refuses to do passive. For the other tools, add the following to your
1.110 hubertf 2919: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:
1.75 rillig 2920: <code class="varname">PASSIVE_FETCH=1</code>.</p>
2921: <p>Having that option present will prevent
1.76 rillig 2922: <code class="filename">/usr/bin/ftp</code> from falling back to active
1.75 rillig 2923: transfers.</p>
2924: </div>
1.148 asau 2925: <div class="sect1">
1.75 rillig 2926: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2927: <a name="fetching-all-distfiles"></a>10.9. How to fetch all distfiles at once</h2></div></div></div>
1.88 wiz 2928: <p>You would like to download all the distfiles in a single batch
1.110 hubertf 2929: from work or university, where you can't run a <span class="command"><strong>make
1.132 spz 2930: fetch</strong></span>. There is an archive of distfiles on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/" target="_top">ftp.NetBSD.org</a>,
1.75 rillig 2931: but downloading the entire directory may not be appropriate.</p>
1.110 hubertf 2932: <p>The answer here is to do a <span class="command"><strong>make fetch-list</strong></span> in
1.76 rillig 2933: <code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the
1.75 rillig 2934: resulting list to your machine at work/school and use it there. If you
1.322 leot 2935: don't have a NetBSD-compatible <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ftp.1"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
1.75 rillig 2936: forget to set <code class="varname">FETCH_CMD</code> to something that fetches a
2937: URL:</p>
2938: <p>At home:</p>
2939: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
2940: <code class="prompt">%</code> <strong class="userinput"><code>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</code></strong>
2941: <code class="prompt">%</code> <strong class="userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong></pre>
2942: <p>At work:</p>
2943: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>sh /tmp/fetch.sh</code></strong></pre>
1.76 rillig 2944: <p>then tar up <code class="filename">/tmp/distfiles</code> and take it
1.75 rillig 2945: home.</p>
2946: <p>If you have a machine running NetBSD, and you want to get
1.88 wiz 2947: <span class="emphasis"><em>all</em></span> distfiles (even ones that aren't for your
2948: machine architecture), you can do so by using the above-mentioned
1.110 hubertf 2949: <span class="command"><strong>make fetch-list</strong></span> approach, or fetch the distfiles
1.88 wiz 2950: directly by running:</p>
1.75 rillig 2951: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make mirror-distfiles</code></strong></pre>
2952: <p>If you even decide to ignore
2953: <code class="varname">NO_{SRC,BIN}_ON_{FTP,CDROM}</code>, then you can get everything
2954: by running:</p>
2955: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch NO_SKIP=yes</code></strong></pre>
2956: </div>
1.148 asau 2957: <div class="sect1">
1.75 rillig 2958: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2959: <a name="tmac.andoc-missing"></a>10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.128 wiz 2960: /usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div>
1.322 leot 2961: <p>When compiling the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/index.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a>
1.75 rillig 2962: package, you get the error from make that it doesn't know how to make
1.76 rillig 2963: <code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that
1.128 wiz 2964: you don't have installed the <span class="quote">“<span class="quote">text</span>”</span> set (nroff, ...) from
1.75 rillig 2965: the NetBSD base distribution on your machine. It is recommended to do
2966: that to format man pages.</p>
1.322 leot 2967: <p>In the case of the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/index.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you
1.75 rillig 2968: can get away with setting <code class="varname">NOMAN=YES</code> either in the
1.110 hubertf 2969: environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.75 rillig 2970: </div>
1.148 asau 2971: <div class="sect1">
1.75 rillig 2972: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 2973: <a name="bsd.own.mk-missing"></a>10.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</h2></div></div></div>
1.87 wiz 2974: <p>You didn't install the compiler set, <code class="filename">comp.tgz</code>,
1.75 rillig 2975: when you installed your NetBSD machine. Please get and install it, by
1.76 rillig 2976: extracting it in <code class="filename">/</code>:</p>
1.75 rillig 2977: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong>
2978: <code class="prompt">#</code> <strong class="userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong></pre>
1.76 rillig 2979: <p><code class="filename">comp.tgz</code> is part of every NetBSD release. Get
1.110 hubertf 2980: the one that corresponds to your release (determine via <span class="command"><strong>uname
1.75 rillig 2981: -r</strong></span>).</p>
2982: </div>
1.148 asau 2983: <div class="sect1">
1.75 rillig 2984: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.336 nia 2985: <a name="using-sudo-with-pkgsrc"></a>10.12. Using 'sudo' or `priv` with pkgsrc</h2></div></div></div>
1.75 rillig 2986: <p>When installing packages as non-root user and using the just-in-time
1.322 leot 2987: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/su.1"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a> feature of pkgsrc, it can become annoying to type in the root
1.75 rillig 2988: password for each required package installed. To avoid this, the sudo
2989: package can be used, which does password caching over a limited time. To
1.336 nia 2990: use it, install <span class="command"><strong>sudo</strong></span> or
2991: <span class="command"><strong>priv</strong></span> (either as binary package, from
2992: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/priv/index.html" target="_top"><code class="filename">security/priv</code></a>, or
1.322 leot 2993: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/sudo/index.html" target="_top"><code class="filename">security/sudo</code></a>) and then put the
1.110 hubertf 2994: following into your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, somewhere
1.98 wiz 2995: <span class="emphasis"><em>after</em></span> the definition of the
2996: <code class="varname">LOCALBASE</code> variable:</p>
1.75 rillig 2997: <pre class="programlisting">
1.100 rillig 2998: .if exists(${LOCALBASE}/bin/sudo)
2999: SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
3000: .endif
1.1 grant 3001: </pre>
1.75 rillig 3002: </div>
1.148 asau 3003: <div class="sect1">
1.75 rillig 3004: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 3005: <a name="faq.conf"></a>10.13. How do I change the location of configuration files?</h2></div></div></div>
1.75 rillig 3006: <p>As the system administrator, you can choose where configuration files
3007: are installed. The default settings make all these files go into
1.76 rillig 3008: <code class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may
1.75 rillig 3009: be suboptimal depending on your expectations (e.g., a read-only,
3010: NFS-exported <code class="varname">PREFIX</code> with a need of per-machine
3011: configuration of the provided packages).</p>
3012: <p>In order to change the defaults, you can modify the
3013: <code class="varname">PKG_SYSCONFBASE</code> variable (in
1.110 hubertf 3014: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>) to point to your preferred configuration
1.76 rillig 3015: directory; some common examples include <code class="filename">/etc</code> or
3016: <code class="filename">/etc/pkg</code>.</p>
1.75 rillig 3017: <p>Furthermore, you can change this value on a per-package basis by
3018: setting the <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> variable.
3019: <code class="varname">PKG_SYSCONFVAR</code>'s value usually matches the name of the
3020: package you would like to modify, that is, the contents of
3021: <code class="varname">PKGBASE</code>.</p>
3022: <p>Note that after changing these settings, you must rebuild and
3023: reinstall any affected packages.</p>
3024: </div>
1.148 asau 3025: <div class="sect1">
1.75 rillig 3026: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 3027: <a name="audit-packages"></a>10.14. Automated security checks</h2></div></div></div>
1.75 rillig 3028: <p>Please be aware that there can often be bugs in third-party software,
3029: and some of these bugs can leave a machine vulnerable to exploitation by
3030: attackers. In an effort to lessen the exposure, the NetBSD packages team
3031: maintains a database of known-exploits to packages which have at one time
3032: been included in pkgsrc. The database can be downloaded automatically, and
3033: a security audit of all packages installed on a system can take place. To
1.114 jmcneill 3034: do this, refer to the following two tools (installed as part of the
1.322 leot 3035: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/index.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package):</p>
1.128 wiz 3036: <div class="orderedlist"><ol class="orderedlist" type="1">
3037: <li class="listitem">
1.122 reed 3038: <p><span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>, an easy way to
1.75 rillig 3039: download a list of the security vulnerabilities information. This list
1.132 spz 3040: is kept up to date by the pkgsrc security team, and is distributed
3041: from the NetBSD ftp server:</p>
1.292 leot 3042: <p><a class="ulink" href="https://ftp.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities" target="_top">https://ftp.NetBSD.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities</a></p>
1.75 rillig 3043: </li>
1.128 wiz 3044: <li class="listitem"><p><span class="command"><strong>pkg_admin audit</strong></span>, an easy way to audit the
3045: current machine, checking each known vulnerability. If a
1.75 rillig 3046: vulnerable package is installed, it will be shown by output to stdout,
3047: including a description of the type of vulnerability, and a URL
3048: containing more information.</p></li>
3049: </ol></div>
1.233 sevan 3050: <p>Use of these tools is strongly recommended!
1.317 nia 3051: See <a class="xref" href="#vulnerabilities" title="5.1.6. Checking for security vulnerabilities in installed packages">Section 5.1.6, “Checking for security vulnerabilities in installed packages”</a> for instructions on how to automate checking and
1.233 sevan 3052: reporting.</p>
3053: <p>If this database is installed, pkgsrc builds will use it to
3054: perform a security check before building any package.</p>
1.75 rillig 3055: </div>
1.148 asau 3056: <div class="sect1">
1.75 rillig 3057: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 3058: <a name="ufaq-cflags"></a>10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</h2></div></div></div>
1.75 rillig 3059: <p>When you add your own preferences to the
3060: <code class="varname">CFLAGS</code> variable in your
1.110 hubertf 3061: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, these flags are passed in
1.76 rillig 3062: environment variables to the <code class="filename">./configure</code>
1.322 leot 3063: scripts and to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>. Some package authors ignore the
1.75 rillig 3064: <code class="varname">CFLAGS</code> from the environment variable by
1.76 rillig 3065: overriding them in the <code class="filename">Makefile</code>s of their
1.75 rillig 3066: package.</p>
3067: <p>Currently there is no solution to this problem. If you
3068: really need the package to use your <code class="varname">CFLAGS</code>
1.110 hubertf 3069: you should run <span class="command"><strong>make patch</strong></span> in the package
1.76 rillig 3070: directory and then inspect any <code class="filename">Makefile</code> and
3071: <code class="filename">Makefile.in</code> for whether they define
1.75 rillig 3072: <code class="varname">CFLAGS</code> explicitly. Usually you can remove
1.128 wiz 3073: these lines. But be aware that some <span class="quote">“<span class="quote">smart</span>”</span>
1.75 rillig 3074: programmers write so bad code that it only works for the
3075: specific combination of <code class="varname">CFLAGS</code> they have
3076: chosen.</p>
1.287 rillig 3077: <p>To find out where the CFLAGS are ignored, add the following lines to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
3078: <pre class="programlisting">
3079: CPPFLAGS+= -Dpkgsrc___CPPFLAGS
3080: CFLAGS+= -Dpkgsrc___CFLAGS
3081: CXXFLAGS+= -Dpkgsrc___CXXFLAGS
3082: </pre>
3083: <p>Then run <span class="command"><strong>bmake show-all-configure show-all-build</strong></span>
3084: to see whether the above flags are passed to the actual build
3085: commands in general.</p>
3086: <p>To find out whether the flags are passed to individual compiler
3087: commands, have a look at the file <code class="filename">work/.work.log</code>. In
3088: most cases, the flags from the original command lines (the lines starting
3089: with <code class="literal">[*]</code>) are passed unmodified to the actual compiler
3090: (the lines starting with <code class="literal"><.></code>). If the flag is
3091: missing from the actual compiler command, it must have been removed by
1.299 rillig 3092: the <a class="link" href="#build.wrapper" title="13.10. The wrapper phase">pkgsrc compiler wrappers</a>.</p>
1.75 rillig 3093: </div>
1.148 asau 3094: <div class="sect1">
1.80 rillig 3095: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 3096: <a name="ufaq-fail"></a>10.16. A package does not build. What shall I do?</h2></div></div></div>
1.128 wiz 3097: <div class="procedure"><ol class="procedure" type="1">
1.148 asau 3098: <li class="step"><p>Make sure that your copy of pkgsrc is consistent. A
1.80 rillig 3099: case that occurs often is that people only update pkgsrc in
3100: parts, because of performance reasons. Since pkgsrc is one large
3101: system, not a collection of many small systems, there are
3102: sometimes changes that only work when the whole pkgsrc tree is
3103: updated.</p></li>
1.148 asau 3104: <li class="step"><p>Make sure that you don't have any CVS conflicts.
1.128 wiz 3105: Search for <span class="quote">“<span class="quote"><<<<<<</span>”</span> or
3106: <span class="quote">“<span class="quote">>>>>>></span>”</span> in all your pkgsrc
1.80 rillig 3107: files.</p></li>
1.148 asau 3108: <li class="step"><p>Make sure that you don't have old copies of the packages
1.110 hubertf 3109: extracted. Run <span class="command"><strong>make clean clean-depends</strong></span> to
1.80 rillig 3110: verify this.</p></li>
1.218 rillig 3111: <li class="step"><p>If you are a package developer who wants to invest
1.267 rillig 3112: some work, have a look at <a class="xref" href="#fixes" title="Chapter 21. Making your package work">Chapter 21, <i>Making your package work</i></a>.</p></li>
1.148 asau 3113: <li class="step"><p>If the problem still exists, write a mail to the
1.80 rillig 3114: <code class="literal">pkgsrc-users</code> mailing list.</p></li>
3115: </ol></div>
3116: </div>
1.148 asau 3117: <div class="sect1">
1.88 wiz 3118: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 3119: <a name="faq.rcs-conflicts"></a>10.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</h2></div></div></div>
1.89 rillig 3120: <p>You have modified a file from pkgsrc, and someone else has
3121: modified that same file afterwards in the CVS repository. Both changes
3122: are in the same region of the file, so when you updated pkgsrc, the
3123: <code class="literal">cvs</code> command marked the conflicting changes in the
3124: file. Because of these markers, the file is no longer a valid
3125: <code class="filename">Makefile</code>.</p>
3126: <p>Have a look at that file, and if you don't need your local changes
1.110 hubertf 3127: anymore, you can remove that file and run <span class="command"><strong>cvs -q update
1.89 rillig 3128: -dP</strong></span> in that directory to download the current version.</p>
3129: </div>
1.75 rillig 3130: </div>
3131: </div>
1.148 asau 3132: <div class="part">
1.75 rillig 3133: <div class="titlepage"><div><div><h1 class="title">
3134: <a name="developers-guide"></a>Part II. The pkgsrc developer's guide</h1></div></div></div>
1.148 asau 3135: <div class="partintro">
1.77 rillig 3136: <div></div>
3137: <p>This part of the book deals with creating and
1.128 wiz 3138: modifying packages. It starts with a <span class="quote">“<span class="quote">HOWTO</span>”</span>-like
1.77 rillig 3139: guide on creating a new package. The remaining chapters are more
3140: like a reference manual for pkgsrc.</p>
1.75 rillig 3141: <div class="toc">
3142: <p><b>Table of Contents</b></p>
1.210 leot 3143: <dl class="toc">
1.267 rillig 3144: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.299 rillig 3145: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.91 rillig 3146: <dd><dl>
1.299 rillig 3147: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3148: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3149: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.91 rillig 3150: <dd><dl>
1.299 rillig 3151: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3152: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3153: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3154: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3155: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.91 rillig 3156: </dl></dd>
1.299 rillig 3157: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3158: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3159: <dd><dl>
3160: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3161: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3162: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
3163: </dl></dd>
3164: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3165: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.106 rillig 3166: </dl></dd>
1.299 rillig 3167: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.106 rillig 3168: <dd><dl>
1.299 rillig 3169: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
3170: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
3171: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
3172: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
3173: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.106 rillig 3174: <dd><dl>
1.299 rillig 3175: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
3176: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.106 rillig 3177: </dl></dd>
1.299 rillig 3178: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
3179: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
3180: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
3181: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
3182: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
3183: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3184: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3185: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
3186: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3187: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
3188: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
3189: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
3190: </dl></dd>
3191: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
3192: <dd><dl>
3193: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.106 rillig 3194: <dd><dl>
1.334 nia 3195: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
3196: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
3197: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.106 rillig 3198: </dl></dd>
1.299 rillig 3199: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
3200: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">14.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
1.106 rillig 3201: </dl></dd>
1.299 rillig 3202: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.106 rillig 3203: <dd><dl>
1.299 rillig 3204: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
3205: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
3206: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
3207: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.106 rillig 3208: <dd><dl>
1.299 rillig 3209: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
3210: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
3211: <dt><span class="sect2"><a href="#cflags-gnu-configure">15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</a></span></dt>
3212: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.106 rillig 3213: </dl></dd>
3214: </dl></dd>
1.299 rillig 3215: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.106 rillig 3216: <dd><dl>
1.299 rillig 3217: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
3218: <dt><span class="sect1"><a href="#converting-to-options">16.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt>
3219: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
3220: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.106 rillig 3221: </dl></dd>
1.299 rillig 3222: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.106 rillig 3223: <dd><dl>
1.299 rillig 3224: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
3225: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
3226: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
3227: </dl></dd>
3228: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
3229: <dd><dl>
3230: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
3231: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.106 rillig 3232: <dd><dl>
1.299 rillig 3233: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
3234: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.133 wiz 3235: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3236: and
3237: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3238: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.106 rillig 3239: </dl></dd>
1.299 rillig 3240: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
3241: <dd><dl>
3242: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
3243: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
3244: </dl></dd>
3245: </dl></dd>
3246: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.106 rillig 3247: <dd><dl>
1.299 rillig 3248: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
3249: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
3250: <dt><span class="sect1"><a href="#print-PLIST">19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
3251: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
3252: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
3253: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
3254: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
3255: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
3256: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.106 rillig 3257: </dl></dd>
1.299 rillig 3258: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
3259: <dd><dl>
3260: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
3261: <dd><dl>
3262: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
3263: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.106 rillig 3264: </dl></dd>
1.299 rillig 3265: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.106 rillig 3266: <dd><dl>
1.299 rillig 3267: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
3268: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
3269: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
3270: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
3271: </dl></dd>
3272: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
3273: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">20.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
3274: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
3275: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
3276: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
3277: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
3278: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">20.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
1.267 rillig 3279: </dl></dd>
3280: <dt><span class="chapter"><a href="#fixes">21. Making your package work</a></span></dt>
3281: <dd><dl>
3282: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
3283: <dd><dl>
3284: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">21.1.1. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
3285: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
3286: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
3287: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
3288: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
3289: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
3290: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
3291: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
3292: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
3293: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
3294: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
3295: </dl></dd>
3296: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
3297: <dd><dl>
3298: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
3299: <dt><span class="sect2"><a href="#modified-distfiles-same-name">21.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
3300: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
3301: </dl></dd>
3302: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3303: <dd><dl>
3304: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
3305: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
3306: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.338 nia 3307: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.267 rillig 3308: </dl></dd>
3309: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
3310: <dd><dl>
3311: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
3312: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.320 wiz 3313: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.338 nia 3314: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
3315: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
3316: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
3317: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.267 rillig 3318: </dl></dd>
3319: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3320: <dd><dl>
3321: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
3322: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.287 rillig 3323: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
3324: <dt><span class="sect2"><a href="#undefined-reference">21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
3325: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.267 rillig 3326: </dl></dd>
3327: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3328: <dd><dl>
3329: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
3330: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
3331: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
3332: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
3333: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.318 nia 3334: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.267 rillig 3335: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
3336: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.318 nia 3337: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
3338: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
3339: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
3340: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
3341: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
3342: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
3343: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.87 wiz 3344: emulation</a></span></dt>
1.318 nia 3345: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
3346: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.77 rillig 3347: </dl></dd>
1.267 rillig 3348: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.77 rillig 3349: </dl></dd>
1.299 rillig 3350: <dt><span class="chapter"><a href="#gnome">22. GNOME packaging and porting</a></span></dt>
3351: <dd><dl>
3352: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
3353: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
3354: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
3355: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
3356: </dl></dd>
1.267 rillig 3357: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.77 rillig 3358: <dd><dl>
1.267 rillig 3359: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
3360: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
3361: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
3362: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
3363: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
3364: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
3365: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
3366: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
3367: </dl></dd>
3368: <dt><span class="chapter"><a href="#devfaq">24. Frequently Asked Questions</a></span></dt>
1.75 rillig 3369: </dl>
3370: </div>
1.77 rillig 3371: </div>
1.148 asau 3372: <div class="chapter">
1.77 rillig 3373: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 3374: <a name="help-devel"></a>Chapter 11. Getting help</h2></div></div></div>
3375: <p>
3376: To get help when developing pkgsrc, the definitive source is this
3377: document, the pkgsrc guide. If you don't find anything here,
3378: there are alternatives:
3379: </p>
3380: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3381: <li class="listitem">
3382: <p>
3383: The built-in pkgsrc help, which is available after bootstrapping
3384: pkgsrc. Run <span class="command"><strong>bmake help topic=…</strong></span> to get
3385: help for any topic, such as a variable name like
3386: <code class="varname">BUILD_DEFS</code>, a make target like
3387: <span class="command"><strong>do-build</strong></span>, a missing C or C++ function like
3388: <span class="command"><strong>strcasecmp</strong></span> or any other topic.</p>
1.322 leot 3389: <p>The available help topics are listed in <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.267 rillig 3390: </li>
3391: <li class="listitem"><p>
1.278 rillig 3392: To see the value of a single variable, run <span class="command"><strong>bmake
3393: show-var VARNAME=<em class="replaceable"><code>X</code></em></strong></span>.
3394: </p></li>
3395: <li class="listitem"><p>
3396: To see the values of the most common variables, run
3397: <span class="command"><strong>bmake show-all</strong></span>. These variables are grouped by
3398: topic. To see the variables for a single topic, run
3399: <span class="command"><strong>bmake
3400: show-all-<em class="replaceable"><code>topic</code></em></strong></span>, for example
3401: <span class="command"><strong>bmake show-all-fetch</strong></span>.
3402: </p></li>
3403: <li class="listitem"><p>
1.267 rillig 3404: The tech-pkg mailing list, to which
3405: <a class="ulink" href="https://www.NetBSD.org/mailinglists/#tech-pkg" target="_top">you
3406: can subscribe</a> and then <a class="ulink" href="mailto:tech-pkg@NetBSD.org" target="_top">ask your
3407: questions</a>.</p></li>
3408: <li class="listitem"><p>The #pkgsrc IRC channel, which is accessible
3409: <a class="ulink" href="https://webchat.freenode.net/" target="_top">via a web browser</a>
3410: or by using a specialized chat program such as
3411: <a class="ulink" href="http://xchat.org/" target="_top">XChat</a>.
3412: Pick any user name and join the channel #pkgsrc.</p></li>
3413: </ul></div>
3414: </div>
3415: <div class="chapter">
3416: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 3417: <a name="components"></a>Chapter 12. Package components - files, directories and contents</h2></div></div></div>
1.91 rillig 3418: <div class="toc">
3419: <p><b>Table of Contents</b></p>
1.210 leot 3420: <dl class="toc">
1.299 rillig 3421: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3422: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3423: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
3424: <dd><dl>
3425: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3426: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3427: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3428: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3429: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
3430: </dl></dd>
3431: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3432: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3433: <dd><dl>
3434: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3435: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3436: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
1.91 rillig 3437: </dl></dd>
1.299 rillig 3438: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3439: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.91 rillig 3440: </dl>
3441: </div>
1.299 rillig 3442: <p>Whenever you're preparing a package, there are a number of
3443: files involved which are described in the following
3444: sections.</p>
3445: <div class="sect1">
3446: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3447: <a name="components.Makefile"></a>12.1. <code class="filename">Makefile</code>
3448: </h2></div></div></div>
3449: <p>Building, installation and creation of a binary package are all
3450: controlled by the package's <code class="filename">Makefile</code>.
3451: The <code class="filename">Makefile</code> describes various things about
3452: a package, for example from where to get it, how to configure,
3453: build, and install it.</p>
3454: <p>A package <code class="filename">Makefile</code> contains several
3455: sections that describe the package.</p>
3456: <p>In the first section there are the following variables, which
3457: should appear exactly in the order given here. The order and
3458: grouping of the variables is mostly historical and has no further
3459: meaning.</p>
3460: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3461: <li class="listitem"><p><code class="varname">DISTNAME</code> is the basename of the
3462: distribution file to be downloaded from the package's
3463: website.</p></li>
3464: <li class="listitem"><p><code class="varname">PKGNAME</code> is the name of the
3465: package, as used by pkgsrc. You need to provide it if
3466: <code class="varname">DISTNAME</code> (which is the default) is not a good
3467: name for the package in pkgsrc or <code class="varname">DISTNAME</code> is not
3468: provided (no distribution file is required). Usually it is the pkgsrc
3469: directory name together with the version number. It must match the
3470: regular expression
3471: <code class="varname">^[A-Za-z0-9][A-Za-z0-9-_.+]*$</code>, that is, it
3472: starts with a letter or digit, and contains only letters, digits,
1.319 nia 3473: dashes, underscores, dots and plus signs.
3474: New packages should have entirely lower-case names, with the exception
3475: of some that must follow pre-existing conventions
3476: (e.g. R packages begin with <code class="varname">R-</code>).
3477: You can use the <code class="code">:tl</code> variable modifier to lower-case
3478: the package name.</p></li>
1.299 rillig 3479: <li class="listitem">
3480: <p><code class="varname">CATEGORIES</code> is a list of categories
3481: which the package fits in. You can choose any of the top-level
3482: directories of pkgsrc for it.</p>
3483: <p>Currently the following values are available for
3484: <code class="varname">CATEGORIES</code>. If more than
3485: one is used, they need to be separated by spaces:</p>
1.77 rillig 3486: <pre class="programlisting">
1.299 rillig 3487: archivers cross geography meta-pkgs security
3488: audio databases graphics misc shells
3489: benchmarks devel ham multimedia sysutils
3490: biology editors inputmethod net textproc
3491: cad emulators lang news time
3492: chat finance mail parallel wm
3493: comms fonts math pkgtools www
3494: converters games mbone print x11
1.77 rillig 3495: </pre>
3496: </li>
1.299 rillig 3497: <li class="listitem"><p><code class="varname">MASTER_SITES</code>,
3498: <code class="varname">DYNAMIC_MASTER_SITES</code>,
3499: <code class="varname">DIST_SUBDIR</code>, <code class="varname">EXTRACT_SUFX</code>
3500: and <code class="varname">DISTFILES</code> are discussed in detail in
3501: <a class="xref" href="#build.fetch" title="13.5. The fetch phase">Section 13.5, “The <span class="emphasis"><em>fetch</em></span> phase”</a>.</p></li>
3502: </ul></div>
3503: <p>The second section contains information about separately
3504: downloaded patches, if any.
3505: </p>
3506: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3507: <li class="listitem"><p><code class="varname">PATCHFILES</code>:
3508: Name(s) of additional files that contain distribution patches.
3509: There is no default. pkgsrc will look for them at
3510: <code class="varname">PATCH_SITES</code>.
3511: They will automatically be uncompressed before patching if
3512: the names end with <code class="filename">.gz</code> or
3513: <code class="filename">.Z</code>.</p></li>
3514: <li class="listitem"><p><code class="varname">PATCH_SITES</code>:
3515: Primary location(s) for distribution patch files (see
3516: <code class="varname">PATCHFILES</code> above) if not found locally.</p></li>
3517: <li class="listitem"><p><code class="varname">PATCH_DIST_STRIP</code>:
1.322 leot 3518: an argument to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> that sets the pathname strip count to
1.299 rillig 3519: help find the correct files to patch. It defaults to
3520: <span class="command"><strong>-p0</strong></span>.</p></li>
3521: </ul></div>
3522: <p>The third section contains the following variables.
3523: </p>
3524: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3525: <li class="listitem"><p><code class="varname">MAINTAINER</code> is the email
3526: address of the person who feels responsible for this package,
3527: and who is most likely to look at problems or questions regarding
1.322 leot 3528: this package which have been reported with <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a>.
1.299 rillig 3529: Other developers may contact the <code class="varname">MAINTAINER</code>
3530: before making changes to the package, but are not required to
3531: do so. When packaging a new program, set <code class="varname">MAINTAINER</code>
3532: to yourself. If you really can't maintain the package for future
3533: updates, set it to
3534: <code class="email"><<a class="email" href="mailto:pkgsrc-users@NetBSD.org">pkgsrc-users@NetBSD.org</a>></code>.</p></li>
3535: <li class="listitem"><p><code class="varname">OWNER</code> should be used instead
3536: of <code class="varname">MAINTAINER</code> when you do not want other
3537: developers to update or change the package without contacting
3538: you first. A package Makefile should contain one of
3539: <code class="varname">MAINTAINER</code> or <code class="varname">OWNER</code>, but
3540: not both. </p></li>
3541: <li class="listitem"><p><code class="varname">HOMEPAGE</code> is a URL where users can
3542: find more information about the package.</p></li>
3543: <li class="listitem"><p><code class="varname">COMMENT</code> is a one-line
3544: description of the package (should not include the package
3545: name).</p></li>
3546: <li class="listitem"><p><code class="varname">LICENSE</code> indicates the license(s)
3547: applicable for the package. See <a class="xref" href="#handling-licenses" title="21.1.3. Handling licenses">Section 21.1.3, “Handling licenses”</a> for further details.</p></li>
3548: </ul></div>
3549: <p>Other variables that affect the build:
3550: </p>
3551: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3552: <p><code class="varname">WRKSRC</code>: The directory where the
3553: interesting distribution files of the package are found. The
3554: default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which
3555: works for most packages.</p>
3556: <p>If a package doesn't create a subdirectory for itself
3557: (most GNU software does, for instance), but extracts itself in
3558: the current directory, you should set
3559: <code class="varname">WRKSRC=${WRKDIR}</code>.</p>
3560: <p>If a package doesn't create a subdirectory with the
3561: name of <code class="varname">DISTNAME</code> but some different name,
3562: set <code class="varname">WRKSRC</code> to point to the proper name in
3563: <code class="filename">${WRKDIR}</code>, for example
3564: <code class="varname">WRKSRC=${WRKDIR}/${DISTNAME}/unix</code>. See
1.322 leot 3565: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/tcl/index.html" target="_top"><code class="filename">lang/tcl</code></a> and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/tk/index.html" target="_top"><code class="filename">x11/tk</code></a> for other examples.</p>
1.299 rillig 3566: <p>The name of the working directory created by pkgsrc is
3567: taken from the <code class="varname">WRKDIR_BASENAME</code>
3568: variable. By default, its value is
3569: <code class="filename">work</code>. If you want to use the same
3570: pkgsrc tree for building different kinds of binary packages,
3571: you can change the variable according to your needs. Two
3572: other variables handle common cases of setting
3573: <code class="varname">WRKDIR_BASENAME</code> individually. If
3574: <code class="varname">OBJHOSTNAME</code> is defined in
3575: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the first component of
3576: the host's name is attached to the directory name. If
3577: <code class="varname">OBJMACHINE</code> is defined, the platform name
3578: is attached, which might look like
3579: <code class="filename">work.i386</code> or
3580: <code class="filename">work.sparc</code>.</p>
3581: </li></ul></div>
3582: <p>Please pay attention to the following gotchas:</p>
3583: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3584: <li class="listitem"><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are
3585: installed in compressed form by the package. For packages using
3586: BSD-style makefiles which honor MANZ, there is
3587: <code class="varname">MANCOMPRESSED_IF_MANZ</code>.</p></li>
3588: <li class="listitem"><p>Replace <code class="filename">/usr/local</code> with
3589: <span class="quote">“<span class="quote">${PREFIX}</span>”</span> in all files (see patches,
3590: below).</p></li>
3591: <li class="listitem"><p>If the package installs any info files, see <a class="xref" href="#faq.info-files" title="21.6.7. Packages installing info files">Section 21.6.7, “Packages installing info files”</a>.</p></li>
3592: </ul></div>
3593: </div>
1.148 asau 3594: <div class="sect1">
1.91 rillig 3595: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 3596: <a name="components.distinfo"></a>12.2. <code class="filename">distinfo</code>
3597: </h2></div></div></div>
3598: <p>The <code class="filename">distinfo</code> file contains the message
3599: digest, or checksum, of each distfile needed for the package. This
3600: ensures that the distfiles retrieved from the Internet have not been
3601: corrupted during transfer or altered by a malign force to introduce
3602: a security hole. To provide maximum security, all distfiles are
3603: protected using three different message digest algorithms (SHA1,
3604: RMD160, SHA512), as well as the file size.</p>
3605: <p>The <code class="filename">distinfo</code> file also contains the
3606: checksums for all the patches found in the
3607: <code class="filename">patches</code> directory (see <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a>). These checksums ensure that patches
3608: are only applied intentionally and that they don't accidentally change,
3609: e.g. when merging different changes together. They also make sure that
3610: new patches are actually added to CVS and old ones are removed.
3611: Too see whether the patches and the <code class="filename">distinfo</code> file
3612: match, run <span class="command"><strong>pkglint</strong></span> after changing the patches.</p>
3613: <p>To regenerate the <code class="filename">distinfo</code> file, use the
3614: <span class="command"><strong>make distinfo</strong></span> command.</p>
3615: <p>Some packages have different sets of distfiles depending on
1.322 leot 3616: the platform, for example <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/openjdk8/index.html" target="_top"><code class="filename">lang/openjdk8</code></a>. These are kept in the same
1.299 rillig 3617: <code class="filename">distinfo</code> file and care should be taken when
3618: upgrading such a package to ensure distfile information is not
3619: lost.</p>
3620: </div>
3621: <div class="sect1">
3622: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3623: <a name="components.patches"></a>12.3. <code class="filename">patches/*</code>
3624: </h2></div></div></div>
3625: <p>Some packages don't work out-of-the box on the various
3626: platforms that are supported by pkgsrc. These packages need
3627: to be patched to make them work. The patch files can be
3628: found in the <code class="filename">patches/</code> directory.</p>
3629: <p>In the <span class="emphasis"><em>patch</em></span> phase, these patches are
3630: applied to the files in <code class="varname">WRKSRC</code> directory after
3631: extracting them, in alphabetic order.</p>
1.148 asau 3632: <div class="sect2">
1.91 rillig 3633: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 3634: <a name="components.patch.structure"></a>12.3.1. Structure of a single patch file</h3></div></div></div>
3635: <p>The <code class="filename">patch-*</code> files should be in
3636: <span class="command"><strong>diff -bu</strong></span> format, and apply without a fuzz to avoid
3637: problems. (To force patches to apply with fuzz you can set
3638: <code class="varname">PATCH_FUZZ_FACTOR=-F2</code>). Furthermore, each patch
3639: should contain only changes for a single file, and no file should be
3640: patched by more than one patch file. This helps to keep future
3641: modifications simple.</p>
3642: <p>Each patch file is structured as follows: In the first line,
3643: there is the RCS Id of the patch itself. The second line should be
3644: empty for aesthetic reasons. After that, there should be a comment for
3645: each change that the patch does. There are a number of standard
3646: cases:</p>
3647: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3648: <li class="listitem"><p>Patches for commonly known vulnerabilities should
3649: mention the vulnerability ID (CAN, CVE).</p></li>
3650: <li class="listitem"><p>Patches that change source code should mention the
3651: platform and other environment (for example, the compiler) that the
3652: patch is needed for.</p></li>
3653: </ul></div>
3654: <p>The patch should be commented so that any
3655: developer who knows the code of the application can make some use of
3656: the patch. Special care should be taken for the upstream developers,
3657: since we generally want that they accept our patches, so we have less
3658: work in the future.</p>
1.91 rillig 3659: </div>
1.148 asau 3660: <div class="sect2">
1.91 rillig 3661: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 3662: <a name="components.patches.caveats"></a>12.3.2. Creating patch files</h3></div></div></div>
3663: <p>One important thing to mention is to pay attention that no RCS
3664: IDs get stored in the patch files, as these will cause problems when
3665: later checked into the NetBSD CVS tree. Use the
1.322 leot 3666: <span class="command"><strong>pkgdiff</strong></span> command from the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package to avoid these
1.299 rillig 3667: problems.</p>
3668: <p>For even more automation, we recommend using
3669: <span class="command"><strong>mkpatches</strong></span> from the same package to make a
1.337 gutterid 3670: whole set of patches. You just have to back up files before you
3671: edit them to <code class="filename">filename.orig</code>, e.g., with
1.299 rillig 3672: <span class="command"><strong>cp -p filename filename.orig</strong></span> or, easier, by
3673: using <span class="command"><strong>pkgvi</strong></span> again from the same package. If
3674: you upgrade a package this way, you can easily compare the new
3675: set of patches with the previously existing one with
3676: <span class="command"><strong>patchdiff</strong></span>. The files in <code class="filename">patches</code>
3677: are replaced by new files, so carefully check if you want to take all
3678: the changes.</p>
3679: <p>When you have finished a package, remember to generate
3680: the checksums for the patch files by using the <span class="command"><strong>make
3681: makepatchsum</strong></span> command, see <a class="xref" href="#components.distinfo" title="12.2. distinfo">Section 12.2, “<code class="filename">distinfo</code>”</a>.</p>
3682: <p>When adding a patch that corrects a problem in the
3683: distfile (rather than e.g. enforcing pkgsrc's view of where
3684: man pages should go), send the patch as a bug report to the
3685: maintainer. This benefits non-pkgsrc users of the package,
3686: and usually makes it possible to remove the patch in future
3687: version.</p>
3688: <p>The file names of the patch files are usually of the form
3689: <code class="filename">patch-<em class="replaceable"><code>path_to_file__with__underscores.c</code></em></code>.
3690: Many packages still use the previous convention
3691: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>,
3692: but new patches should be of the form containing the filename.
1.322 leot 3693: <span class="command"><strong>mkpatches</strong></span> included in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> takes care of the name
1.299 rillig 3694: automatically.</p>
1.337 gutterid 3695: <p>When updating pre-existing patch files, if a file uses the old
3696: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>
3697: convention, it's best not to change it to the new form, as that will
3698: just cause churn that makes it harder to track changes to patching
3699: over time. Similarly, if a patch now applies at different line offsets,
3700: but still applies cleanly as-is, there's no need to update it, as that
3701: also unnecessarily complicates the patch history.</p>
1.118 imil 3702: </div>
1.275 brook 3703: <div class="sect2">
3704: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 3705: <a name="components.patches.sources"></a>12.3.3. Sources where the patch files come from</h3></div></div></div>
3706: <p>If you want to share patches between multiple packages
3707: in pkgsrc, e.g. because they use the same distfiles, set
3708: <code class="varname">PATCHDIR</code> to the path where the patch files
3709: can be found, e.g.:</p>
3710: <pre class="programlisting">
3711: PATCHDIR= ../../editors/xemacs/patches
3712: </pre>
3713: <p>Patch files that are distributed by the author or other
3714: maintainers can be listed in
3715: <code class="varname">PATCHFILES</code>.</p>
3716: <p>If it is desired to store any patches that should not be
3717: committed into pkgsrc, they can be kept outside the pkgsrc
3718: tree in the <code class="filename">$LOCALPATCHES</code> directory. The
3719: directory tree there is expected to have the same
3720: <span class="quote">“<span class="quote">category/package</span>”</span> structure as pkgsrc, and
3721: patches are expected to be stored inside these dirs (also
3722: known as <code class="filename">$LOCALPATCHES/$PKGPATH</code>). For
3723: example, if you want to keep a private patch for
3724: <code class="filename">pkgsrc/graphics/png</code>, keep it in
3725: <code class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All
3726: files in the named directory are expected to be patch files,
3727: and <span class="emphasis"><em>they are applied after pkgsrc patches are
3728: applied</em></span>.</p>
1.275 brook 3729: </div>
3730: <div class="sect2">
3731: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 3732: <a name="components.patches.guidelines"></a>12.3.4. Patching guidelines</h3></div></div></div>
3733: <p>When fixing a portability issue in the code do not use
3734: preprocessor magic to check for the current operating system nor
3735: platform. Doing so hurts portability to other platforms because
3736: the OS-specific details are not abstracted appropriately.</p>
3737: <p>The general rule to follow is: instead of checking for the
3738: operating system the application is being built on, check for the
3739: specific <span class="emphasis"><em>features</em></span> you need. For example,
3740: instead of assuming that kqueue is available under NetBSD and
3741: using the <code class="varname">__NetBSD__</code> macro to conditionalize
3742: kqueue support, add a check that detects kqueue itself —
3743: yes, this generally involves patching the
3744: <span class="command"><strong>configure</strong></span> script. There is absolutely nothing
3745: that prevents some OSes from adopting interfaces from other OSes
3746: (e.g. Linux implementing kqueue), something that the above checks
3747: cannot take into account.</p>
3748: <p>Of course, checking for features generally involves more
3749: work on the developer's side, but the resulting changes are
3750: cleaner and there are chances they will work on many other
3751: platforms. Not to mention that there are higher chances of being
3752: later integrated into the mainstream sources. Remember:
3753: <span class="emphasis"><em>It doesn't work unless it is right!</em></span></p>
3754: <p>Some typical examples:</p>
3755: <div class="table">
3756: <a name="patch-examples"></a><p class="title"><b>Table 12.1. Patching examples</b></p>
3757: <div class="table-contents"><table class="table" summary="Patching examples" border="1">
3758: <colgroup>
3759: <col>
3760: <col>
3761: <col>
3762: </colgroup>
3763: <thead><tr>
3764: <th>Where</th>
3765: <th>Incorrect</th>
3766: <th>Correct</th>
3767: </tr></thead>
3768: <tbody>
3769: <tr>
3770: <td>configure script</td>
3771: <td>
1.275 brook 3772: <pre class="programlisting">
1.299 rillig 3773: case ${target_os} in
3774: netbsd*) have_kvm=yes ;;
3775: *) have_kvm=no ;;
3776: esac
1.275 brook 3777: </pre>
1.299 rillig 3778: </td>
3779: <td>
1.275 brook 3780: <pre class="programlisting">
1.299 rillig 3781: AC_CHECK_LIB(kvm, kvm_open, have_kvm=yes, have_kvm=no)
1.275 brook 3782: </pre>
1.299 rillig 3783: </td>
3784: </tr>
3785: <tr>
3786: <td>C source file</td>
3787: <td>
1.91 rillig 3788: <pre class="programlisting">
1.299 rillig 3789: #if defined(__NetBSD__)
3790: # include <sys/event.h>
3791: #endif
1.91 rillig 3792: </pre>
1.299 rillig 3793: </td>
3794: <td>
1.91 rillig 3795: <pre class="programlisting">
1.299 rillig 3796: #if defined(HAVE_SYS_EVENT_H)
3797: # include <sys/event.h>
3798: #endif
1.91 rillig 3799: </pre>
1.299 rillig 3800: </td>
3801: </tr>
3802: <tr>
3803: <td>C source file</td>
3804: <td>
1.91 rillig 3805: <pre class="programlisting">
1.299 rillig 3806: int
3807: monitor_file(...)
3808: {
3809: #if defined(__NetBSD__)
3810: int fd = kqueue();
3811: ...
3812: #else
3813: ...
3814: #endif
3815: }
1.91 rillig 3816: </pre>
1.299 rillig 3817: </td>
3818: <td>
1.91 rillig 3819: <pre class="programlisting">
1.299 rillig 3820: int
3821: monitor_file(...)
3822: {
3823: #if defined(HAVE_KQUEUE)
3824: int fd = kqueue();
3825: ...
3826: #else
3827: ...
3828: #endif
3829: }
1.91 rillig 3830: </pre>
1.299 rillig 3831: </td>
3832: </tr>
3833: </tbody>
3834: </table></div>
3835: </div>
3836: <br class="table-break">
3837: </div>
3838: <div class="sect2">
3839: <div class="titlepage"><div><div><h3 class="title">
3840: <a name="components.patches.feedback"></a>12.3.5. Feedback to the author</h3></div></div></div>
3841: <p>Always, always, <span class="strong"><strong>always</strong></span>
3842: feed back any <span class="emphasis"><em>portability fixes</em></span> or
3843: improvements you do to a package to the mainstream developers.
3844: This is the only way to get their attention on portability issues
3845: and to ensure that future versions can be built out-of-the box on
3846: NetBSD. Furthermore, any user that gets newer distfiles will get
3847: the fixes straight from the packaged code.</p>
3848: <p>This generally involves cleaning up the patches
3849: (because sometimes the patches that are
3850: added to pkgsrc are quick hacks), filing bug reports in the
3851: appropriate trackers for the projects and working with the
3852: mainstream authors to accept your changes. It is
3853: <span class="emphasis"><em>extremely important</em></span> that you do it so that
3854: the packages in pkgsrc are kept simple and thus further changes
3855: can be done without much hassle.</p>
3856: <p>When you have done this, please add a URL to the upstream
3857: bug report to the patch comment.</p>
3858: <p>Support the idea of free software!</p>
3859: </div>
1.91 rillig 3860: </div>
1.299 rillig 3861: <div class="sect1">
3862: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3863: <a name="other-mandatory-files"></a>12.4. Other mandatory files</h2></div></div></div>
3864: <div class="variablelist"><dl class="variablelist">
3865: <dt><span class="term"><code class="filename">DESCR</code></span></dt>
3866: <dd><p>A multi-line description of the piece of software. This should include
3867: any credits where they are due. Please bear in mind that others do not
3868: share your sense of humour (or spelling idiosyncrasies), and that others
3869: will read everything that you write here.</p></dd>
3870: <dt><span class="term"><code class="filename">PLIST</code></span></dt>
3871: <dd><p>This file governs the files that are installed on your
3872: system: all the binaries, manual pages, etc. There are other
3873: directives which may be entered in this file, to control the
3874: creation and deletion of directories, and the location of
3875: inserted files. See <a class="xref" href="#plist" title="Chapter 19. PLIST issues">Chapter 19, <i>PLIST issues</i></a> for more
3876: information.</p></dd>
3877: </dl></div>
3878: </div>
3879: <div class="sect1">
3880: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3881: <a name="components.optional"></a>12.5. Optional files</h2></div></div></div>
3882: <div class="sect2">
3883: <div class="titlepage"><div><div><h3 class="title">
3884: <a name="components.optional.bin"></a>12.5.1. Files affecting the binary package</h3></div></div></div>
3885: <div class="variablelist"><dl class="variablelist">
3886: <dt><span class="term"><code class="filename">INSTALL</code></span></dt>
3887: <dd>
1.322 leot 3888: <p>This shell script is invoked twice by <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>.
1.299 rillig 3889: First time after package extraction and before files are
3890: moved in place, the second time after the files to install
3891: are moved in place. This can be used to do any custom
3892: procedures not possible with @exec commands in
1.322 leot 3893: <code class="filename">PLIST</code>. See <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> and
3894: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information. See also <a class="xref" href="#files-and-dirs-outside-prefix" title="20.1. Files and directories outside the installation prefix">Section 20.1, “Files and directories outside the installation prefix”</a>.
1.299 rillig 3895: Please note that you can modify variables in it easily by using
3896: <code class="varname">FILES_SUBST</code> in the package's
3897: <code class="filename">Makefile</code>:</p>
1.91 rillig 3898: <pre class="programlisting">
1.299 rillig 3899: FILES_SUBST+= SOMEVAR="somevalue"
1.91 rillig 3900: </pre>
1.299 rillig 3901: <p>replaces "@SOMEVAR@" with <span class="quote">“<span class="quote">somevalue</span>”</span> in the
3902: <code class="filename">INSTALL</code>. By default, substitution is
3903: performed for <code class="varname">PREFIX</code>,
3904: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
3905: <code class="varname">VARBASE</code>, and a few others, type
3906: <span class="command"><strong>make help topic=FILES_SUBST</strong></span> for a
3907: complete list.</p>
3908: </dd>
3909: <dt><span class="term"><code class="filename">DEINSTALL</code></span></dt>
3910: <dd><p>This script is executed before and after any files are removed. It is
3911: this script's responsibility to clean up any additional messy details
3912: around the package's installation, since all pkg_delete knows is how to
3913: delete the files created in the original distribution.
1.322 leot 3914: See <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
3915: and <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.
1.299 rillig 3916: The same methods to replace variables can be used as for
3917: the <code class="filename">INSTALL</code> file.</p></dd>
3918: <dt><span class="term"><code class="filename">MESSAGE</code></span></dt>
3919: <dd>
3920: <p>This file is displayed after installation of the package.
1.312 gdt 3921: While this was used often in the past, it has two
3922: problems: the display will be missed if many packages are
3923: intalled at once, and the person installing the package
3924: and the one using or configuring it may be different. It
3925: should therefore be used only in exceptional circumstances
3926: where lasting negative consequences would result from
3927: someone not reading it.</p>
3928: <p>MESSAGE should not be used for:</p>
3929: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3930: <li class="listitem"><p>exhortations to read the documentation</p></li>
3931: <li class="listitem"><p>reminders to install rc.d files and set variables</p></li>
3932: <li class="listitem"><p>anything that should be explained in the
3933: installation/configuration documentation that should
3934: come with the package</p></li>
3935: </ul></div>
3936: <p>If the documentation provided by upstream needs
1.313 leot 3937: enhancing, create e.g. files/README.pkgsrc and install it
3938: in the package's documentation directory.
1.312 gdt 3939: </p>
3940: <p>Note that MESSAGE is shown for all operating
3941: systems and all init systems. If a MESSAGE is necessary,
1.313 leot 3942: it should be narrowed to only those operating systems and
1.312 gdt 3943: init systems to which it applies.</p>
3944: <p>Note that you can modify variables in it easily by using
1.299 rillig 3945: <code class="varname">MESSAGE_SUBST</code> in the package's
3946: <code class="filename">Makefile</code>:</p>
1.91 rillig 3947: <pre class="programlisting">
1.299 rillig 3948: MESSAGE_SUBST+= SOMEVAR="somevalue"
1.91 rillig 3949: </pre>
1.299 rillig 3950: <p>replaces "${SOMEVAR}" with <span class="quote">“<span class="quote">somevalue</span>”</span> in
3951: <code class="filename">MESSAGE</code>. By default, substitution is
3952: performed for <code class="varname">PKGNAME</code>,
3953: <code class="varname">PKGBASE</code>, <code class="varname">PREFIX</code>,
3954: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
3955: <code class="varname">PKG_SYSCONFDIR</code>,
3956: <code class="varname">ROOT_GROUP</code>, and
3957: <code class="varname">ROOT_USER</code>.</p>
3958: <p>You can display a different or additional files by
3959: setting the <code class="varname">MESSAGE_SRC</code> variable. Its
3960: default is <code class="filename">MESSAGE</code>, if the file
3961: exists.</p>
3962: </dd>
3963: <dt><span class="term"><code class="filename">ALTERNATIVES</code></span></dt>
3964: <dd>
3965: <p>This file is used by the alternatives framework.
3966: It creates, configures, and destroys generic wrappers used to
3967: run programs with similar interfaces.
3968: See pkg_alternatives(8) from pkgtools/pkg_alternatives
3969: for more information.</p>
3970: <p>Each line of the file contains two filenames, first
3971: the wrapper and then the alternative provided by the package.
3972: Both paths are relative to <code class="varname">PREFIX</code>.</p>
3973: </dd>
3974: </dl></div>
3975: </div>
3976: <div class="sect2">
3977: <div class="titlepage"><div><div><h3 class="title">
3978: <a name="components.optional.build"></a>12.5.2. Files affecting the build process</h3></div></div></div>
3979: <div class="variablelist"><dl class="variablelist">
3980: <dt><span class="term"><code class="filename">Makefile.common</code></span></dt>
3981: <dd><p>This file contains arbitrary things that could
3982: also go into a <code class="filename">Makefile</code>, but its purpose is
3983: to be used by more than one package. This file should only be
3984: used when the packages that will use the file are known in
3985: advance. For other purposes it is often better to write a
3986: <code class="filename">*.mk</code> file and give it a good name that
3987: describes what it does.</p></dd>
3988: <dt><span class="term"><code class="filename">buildlink3.mk</code></span></dt>
3989: <dd><p>This file contains the dependency information
3990: for the buildlink3 framework (see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p></dd>
3991: <dt><span class="term"><code class="filename">hacks.mk</code></span></dt>
3992: <dd><p>This file contains workarounds for compiler bugs
3993: and similar things. It is included automatically by the pkgsrc
3994: infrastructure, so you don't need an extra
3995: <code class="literal">.include</code> line for
3996: it.</p></dd>
3997: <dt><span class="term"><code class="filename">options.mk</code></span></dt>
3998: <dd><p>This file contains the code for the
3999: package-specific options (see <a class="xref" href="#options" title="Chapter 16. Options handling">Chapter 16, <i>Options handling</i></a>) that can be
4000: selected by the user. If a package has only one or two options,
4001: it is equally acceptable to put the code directly into the
4002: <code class="filename">Makefile</code>.</p></dd>
4003: </dl></div>
4004: </div>
4005: <div class="sect2">
4006: <div class="titlepage"><div><div><h3 class="title">
4007: <a name="components.optional.none"></a>12.5.3. Files affecting nothing at all</h3></div></div></div>
4008: <div class="variablelist"><dl class="variablelist">
4009: <dt><span class="term"><code class="filename">README*</code></span></dt>
4010: <dd><p>These files do not take place in the creation of
4011: a package and thus are purely informative to the package
4012: developer.</p></dd>
4013: <dt><span class="term"><code class="filename">TODO</code></span></dt>
4014: <dd><p>This file contains things that need to be done
4015: to make the package even
4016: better.</p></dd>
4017: </dl></div>
4018: </div>
4019: </div>
4020: <div class="sect1">
4021: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4022: <a name="work-dir"></a>12.6. <code class="filename">work*</code>
4023: </h2></div></div></div>
4024: <p>When you type <span class="command"><strong>make</strong></span>, the distribution files are
4025: unpacked into the directory denoted by
4026: <code class="varname">WRKDIR</code>. It can be removed by running
4027: <span class="command"><strong>make clean</strong></span>. Besides the sources, this
4028: directory is also used to keep various timestamp files.
4029: The directory gets <span class="emphasis"><em>removed completely</em></span> on clean.
4030: The default is <code class="filename">${.CURDIR}/work</code>
4031: or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code>
4032: if <code class="varname">OBJMACHINE</code> is set.</p>
1.91 rillig 4033: </div>
1.299 rillig 4034: <div class="sect1">
4035: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4036: <a name="files-dir"></a>12.7. <code class="filename">files/*</code>
4037: </h2></div></div></div>
4038: <p>If you have any files that you wish to be placed in the package
4039: prior to configuration or building, you can place these files here
4040: and use a <span class="command"><strong>${CP}</strong></span> command in the
4041: <span class="quote">“<span class="quote">post-extract</span>”</span> target to achieve this.</p>
4042: <p>If you want to share files in this way with other
4043: packages, set the <code class="varname">FILESDIR</code> variable to point
4044: to the other package's <code class="filename">files</code> directory,
4045: e.g.:</p>
1.91 rillig 4046: <pre class="programlisting">
1.299 rillig 4047: FILESDIR= ../../editors/xemacs/files
1.91 rillig 4048: </pre>
4049: </div>
4050: </div>
1.148 asau 4051: <div class="chapter">
1.75 rillig 4052: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 4053: <a name="build"></a>Chapter 13. The build process</h2></div></div></div>
1.75 rillig 4054: <div class="toc">
4055: <p><b>Table of Contents</b></p>
1.210 leot 4056: <dl class="toc">
1.299 rillig 4057: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
4058: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
4059: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
4060: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
4061: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
4062: <dd><dl>
4063: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
4064: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
4065: </dl></dd>
4066: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
4067: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
4068: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
4069: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
4070: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
4071: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
4072: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
4073: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
4074: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
4075: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
4076: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
4077: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
1.75 rillig 4078: </dl>
4079: </div>
1.148 asau 4080: <div class="sect1">
1.75 rillig 4081: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4082: <a name="build.intro"></a>13.1. Introduction</h2></div></div></div>
4083: <p>This chapter gives a detailed description on how a package is
4084: built. Building a package is separated into different
4085: <span class="emphasis"><em>phases</em></span> (for example <code class="varname">fetch</code>,
4086: <code class="varname">build</code>, <code class="varname">install</code>), all of which are
4087: described in the following sections. Each phase is split into
4088: so-called <span class="emphasis"><em>stages</em></span>, which take the name of the
4089: containing phase, prefixed by one of <code class="varname">pre-</code>,
4090: <code class="varname">do-</code> or <code class="varname">post-</code>. (Examples are
4091: <code class="varname">pre-configure</code>, <code class="varname">post-build</code>.) Most
4092: of the actual work is done in the <code class="varname">do-*</code> stages.</p>
4093: <p>Never override the regular targets (like
4094: <code class="varname">fetch</code>), if you have to, override the
4095: <code class="varname">do-*</code> ones instead.</p>
4096: <p>The basic steps for building a program are always the same. First
4097: the program's source (<span class="emphasis"><em>distfile</em></span>) must be brought to
4098: the local system and then extracted. After any pkgsrc-specific patches
4099: to compile properly are applied, the software can be configured, then
4100: built (usually by compiling), and finally the generated binaries, etc.
4101: can be put into place on the system.</p>
4102: <p>To get more details about what is happening at each step,
4103: you can set the <code class="varname">PKG_VERBOSE</code> variable, or the
4104: <code class="varname">PATCH_DEBUG</code> variable if you are just interested
4105: in more details about the <span class="emphasis"><em>patch</em></span> step.</p>
4106: </div>
4107: <div class="sect1">
4108: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4109: <a name="build.prefix"></a>13.2. Program location</h2></div></div></div>
4110: <p>Before outlining the process performed by the NetBSD package system in
4111: the next section, here's a brief discussion on where programs are
4112: installed, and which variables influence this.</p>
4113: <p>The automatic variable <code class="varname">PREFIX</code> indicates
4114: where all files of the final program shall be installed. It is
4115: usually set to <code class="varname">LOCALBASE</code>
4116: (<code class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code>
4117: for pkgs in the <code class="filename">cross</code> category. The value of
4118: <code class="varname">PREFIX</code> needs to be put
4119: into the various places in the program's source where paths to
4120: these files are encoded. See <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a> and <a class="xref" href="#fixes.libtool" title="21.3.1. Shared libraries - libtool">Section 21.3.1, “Shared libraries - libtool”</a> for more details.</p>
4121: <p>When choosing which of these variables to use,
4122: follow the following rules:</p>
1.148 asau 4123: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.299 rillig 4124: <li class="listitem"><p><code class="varname">PREFIX</code> always points to the location
4125: where the current pkg will be installed. When referring to a
4126: pkg's own installation path, use
4127: <span class="quote">“<span class="quote">${PREFIX}</span>”</span>.</p></li>
1.338 nia 4128: <li class="listitem"><p><code class="varname">LOCALBASE</code> is where all pkgs
1.299 rillig 4129: are installed. If you need to construct a -I or -L argument
4130: to the compiler to find includes and libraries installed by
1.338 nia 4131: another pkg, use <span class="quote">“<span class="quote">${LOCALBASE}</span>”</span>. The name
1.299 rillig 4132: <code class="varname">LOCALBASE</code> stems from FreeBSD, which
4133: installed all packages in <code class="filename">/usr/local</code>. As
4134: pkgsrc leaves <code class="filename">/usr/local</code> for the system
4135: administrator, this variable is a misnomer.</p></li>
4136: <li class="listitem"><p><code class="varname">X11BASE</code> is where the actual X11
4137: distribution (from xsrc, etc.) is installed. When looking for
4138: <span class="emphasis"><em>standard</em></span> X11 includes (not those
4139: installed by a package), use <span class="quote">“<span class="quote">${X11BASE}</span>”</span>.</p></li>
4140: <li class="listitem"><p>X11-based packages using imake must set
4141: <code class="varname">USE_IMAKE</code> to be installed correctly under
4142: <code class="varname">LOCALBASE</code>.</p></li>
4143: <li class="listitem"><p>Within <code class="filename">${PREFIX}</code>, packages should
1.322 leot 4144: install files according to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/hier.7"><span class="citerefentry"><span class="refentrytitle">hier</span>(7)</span></a>, with the exception that
1.299 rillig 4145: manual pages go into <code class="filename">${PREFIX}/man</code>, not
4146: <code class="filename">${PREFIX}/share/man</code>.</p></li>
4147: </ul></div>
4148: </div>
4149: <div class="sect1">
4150: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4151: <a name="build.builddirs"></a>13.3. Directories used during the build process</h2></div></div></div>
4152: <p>When building a package, various directories are used to store
4153: source files, temporary files, pkgsrc-internal files, and so on. These
4154: directories are explained here.</p>
4155: <p>Some of the directory variables contain relative pathnames. There
4156: are two common base directories for these relative directories:
4157: <code class="varname">PKGSRCDIR/PKGPATH</code> is used for directories that are
4158: pkgsrc-specific. <code class="varname">WRKSRC</code> is used for directories
4159: inside the package itself.</p>
4160: <div class="variablelist"><dl class="variablelist">
4161: <dt><span class="term"><code class="varname">PKGSRCDIR</code></span></dt>
4162: <dd><p>This is an absolute pathname that points to the pkgsrc
4163: root directory. Generally, you don't need
4164: it.</p></dd>
4165: <dt><span class="term"><code class="varname">PKGDIR</code></span></dt>
4166: <dd><p>This is an absolute pathname that points to the
4167: current package.</p></dd>
4168: <dt><span class="term"><code class="varname">PKGPATH</code></span></dt>
4169: <dd><p>This is a pathname relative to
4170: <code class="varname">PKGSRCDIR</code> that points to the current
4171: package.</p></dd>
4172: <dt><span class="term"><code class="varname">WRKDIR</code></span></dt>
4173: <dd><p>This is an absolute pathname pointing to the directory
4174: where all work takes place. The distfiles are extracted to this
4175: directory. It also contains temporary directories and log files used by
4176: the various pkgsrc frameworks, like <span class="emphasis"><em>buildlink</em></span> or
4177: the <span class="emphasis"><em>wrappers</em></span>.</p></dd>
4178: <dt><span class="term"><code class="varname">WRKSRC</code></span></dt>
4179: <dd><p>This is an absolute pathname pointing to the directory
4180: where the distfiles are extracted. It is usually a direct subdirectory
4181: of <code class="varname">WRKDIR</code>, and often it's the only directory entry
4182: that isn't hidden. This variable may be changed by a package
4183: <code class="filename">Makefile</code>.</p></dd>
4184: </dl></div>
4185: <p>The <code class="varname">CREATE_WRKDIR_SYMLINK</code> definition takes either
4186: the value <span class="emphasis"><em>yes</em></span> or <span class="emphasis"><em>no</em></span> and defaults
4187: to <span class="emphasis"><em>no</em></span>. It indicates whether a symbolic link to the
4188: <code class="varname">WRKDIR</code> is to be created in the pkgsrc entry's directory.
4189: If users would like to have their pkgsrc trees behave in a
4190: read-only manner, then the value of
4191: <code class="varname">CREATE_WRKDIR_SYMLINK</code> should be set to
4192: <span class="emphasis"><em>no</em></span>.</p>
1.75 rillig 4193: </div>
1.148 asau 4194: <div class="sect1">
1.75 rillig 4195: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4196: <a name="build.running"></a>13.4. Running a phase</h2></div></div></div>
4197: <p>You can run a particular phase by typing <span class="command"><strong>make
4198: phase</strong></span>, where <span class="emphasis"><em>phase</em></span> is the name of the
4199: phase. This will automatically run all phases that are required for this
4200: phase. The default phase is <code class="varname">build</code>, that is, when you
4201: run <span class="command"><strong>make</strong></span> without parameters in a package directory,
4202: the package will be built, but not installed.</p>
1.75 rillig 4203: </div>
1.148 asau 4204: <div class="sect1">
1.75 rillig 4205: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4206: <a name="build.fetch"></a>13.5. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
4207: <p>The first step in building a package is to fetch the
4208: distribution files (distfiles) from the sites that are providing
4209: them. This is the task of the <span class="emphasis"><em>fetch</em></span>
4210: phase.</p>
1.148 asau 4211: <div class="sect2">
1.93 rillig 4212: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 4213: <a name="build.fetch.what"></a>13.5.1. What to fetch and where to get it from</h3></div></div></div>
4214: <p>In simple cases, <code class="varname">MASTER_SITES</code>
4215: defines all URLs from where the distfile, whose name is
4216: derived from the <code class="varname">DISTNAME</code> variable, is
4217: fetched. The more complicated cases are described
4218: below.</p>
4219: <p>The variable <code class="varname">DISTFILES</code> specifies
4220: the list of distfiles that have to be fetched. Its value
4221: defaults to <code class="literal">${DEFAULT_DISTFILES}</code> and
4222: its value is <code class="literal">${DISTNAME}${EXTRACT_SUFX}</code>,
4223: so that most packages don't need to define it at all.
4224: <code class="varname">EXTRACT_SUFX</code> is
4225: <code class="literal">.tar.gz</code> by default, but can be changed
4226: freely. Note that if your package requires additional
4227: distfiles to the default one, you cannot just append the
4228: additional filenames using the <code class="literal">+=</code>
4229: operator, but you have write for example:</p>
4230: <pre class="programlisting">
4231: DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
4232: </pre>
4233: <p>Each distfile is fetched from a list of sites, usually
4234: <code class="varname">MASTER_SITES</code>. If the package has multiple
4235: <code class="varname">DISTFILES</code> or multiple
4236: <code class="varname">PATCHFILES</code> from different sites, you can
4237: set
4238: <code class="varname">SITES.<em class="replaceable"><code>distfile</code></em></code>
4239: to the list of URLs where the file
4240: <code class="filename"><em class="replaceable"><code>distfile</code></em></code>
4241: (including the suffix) can be found.</p>
4242: <pre class="programlisting">
4243: DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
4244: DISTFILES+= foo-file.tar.gz
4245: SITES.foo-file.tar.gz= \
4246: https://www.somewhere.com/somehow/ \
4247: https://www.somewhereelse.com/mirror/somehow/
4248: </pre>
4249: <p>When actually fetching the distfiles, each item from
4250: <code class="varname">MASTER_SITES</code> or
4251: <code class="varname">SITES.*</code> gets the name of each distfile
4252: appended to it, without an intermediate slash. Therefore,
4253: all site values have to end with a slash or other separator
4254: character. This allows for example to set
4255: <code class="varname">MASTER_SITES</code> to a URL of a CGI script
4256: that gets the name of the distfile as a parameter. In this
4257: case, the definition would look like:</p>
4258: <pre class="programlisting">
4259: MASTER_SITES= https://www.example.com/download.cgi?file=
4260: </pre>
4261: <p> The exception to this rule are URLs starting with a dash.
4262: In that case the URL is taken as is, fetched and the result
4263: stored under the name of the distfile. You can use this style
4264: for the case when the download URL style does not match the
4265: above common case. For example, if permanent download URL is a
4266: redirector to the real download URL, or the download file name
4267: is offered by an HTTP Content-Disposition header. In the
4268: following example, <code class="filename">foo-1.0.0.tar.gz</code> will be
4269: created instead of the default
4270: <code class="filename">v1.0.0.tar.gz</code>.</p>
4271: <pre class="programlisting">
4272: DISTNAME= foo-1.0.0
4273: MASTER_SITES= -https://www.example.com/archive/v1.0.0.tar.gz
4274: </pre>
4275: <p>There are some predefined values for
4276: <code class="varname">MASTER_SITES</code>, which can be used in
4277: packages. The names of the variables should speak for
4278: themselves.</p>
4279: <table border="0" summary="Simple list" class="simplelist">
4280: <tr>
4281: <td>MASTER_SITE_APACHE</td>
4282: <td>MASTER_SITE_BACKUP</td>
4283: </tr>
4284: <tr>
4285: <td>MASTER_SITE_CRATESIO</td>
4286: <td>MASTER_SITE_CYGWIN</td>
4287: </tr>
4288: <tr>
4289: <td>MASTER_SITE_DEBIAN</td>
4290: <td>MASTER_SITE_FREEBSD</td>
4291: </tr>
4292: <tr>
4293: <td>MASTER_SITE_FREEBSD_LOCAL</td>
4294: <td>MASTER_SITE_GENTOO</td>
4295: </tr>
4296: <tr>
4297: <td>MASTER_SITE_GITHUB</td>
1.340 ! gutterid 4298: <td>MASTER_SITE_GITLAB</td>
! 4299: </tr>
! 4300: <tr>
1.299 rillig 4301: <td>MASTER_SITE_GNOME</td>
1.340 ! gutterid 4302: <td>MASTER_SITE_GNU</td>
1.299 rillig 4303: </tr>
4304: <tr>
4305: <td>MASTER_SITE_GNUSTEP</td>
1.340 ! gutterid 4306: <td>MASTER_SITE_HASKELL_HACKAGE</td>
1.299 rillig 4307: </tr>
4308: <tr>
4309: <td>MASTER_SITE_IFARCHIVE</td>
1.340 ! gutterid 4310: <td>MASTER_SITE_KDE</td>
1.299 rillig 4311: </tr>
4312: <tr>
4313: <td>MASTER_SITE_MOZILLA</td>
1.340 ! gutterid 4314: <td>MASTER_SITE_MOZILLA_ALL</td>
1.299 rillig 4315: </tr>
4316: <tr>
4317: <td>MASTER_SITE_MYSQL</td>
1.340 ! gutterid 4318: <td>MASTER_SITE_NETLIB</td>
1.299 rillig 4319: </tr>
4320: <tr>
4321: <td>MASTER_SITE_OPENBSD</td>
1.340 ! gutterid 4322: <td>MASTER_SITE_OPENOFFICE</td>
1.299 rillig 4323: </tr>
4324: <tr>
4325: <td>MASTER_SITE_OSDN</td>
1.340 ! gutterid 4326: <td>MASTER_SITE_PERL_CPAN</td>
1.299 rillig 4327: </tr>
4328: <tr>
4329: <td>MASTER_SITE_PGSQL</td>
1.340 ! gutterid 4330: <td>MASTER_SITE_PYPI</td>
1.299 rillig 4331: </tr>
4332: <tr>
4333: <td>MASTER_SITE_RUBYGEMS</td>
1.340 ! gutterid 4334: <td>MASTER_SITE_R_CRAN</td>
1.299 rillig 4335: </tr>
4336: <tr>
4337: <td>MASTER_SITE_SOURCEFORGE</td>
1.340 ! gutterid 4338: <td>MASTER_SITE_SUNSITE</td>
1.299 rillig 4339: </tr>
1.85 jmmv 4340: <tr>
1.299 rillig 4341: <td>MASTER_SITE_SUSE</td>
1.340 ! gutterid 4342: <td>MASTER_SITE_TEX_CTAN</td>
1.85 jmmv 4343: </tr>
4344: <tr>
1.299 rillig 4345: <td>MASTER_SITE_XCONTRIB</td>
1.340 ! gutterid 4346: <td>MASTER_SITE_XEMACS</td>
1.85 jmmv 4347: </tr>
4348: <tr>
1.299 rillig 4349: <td>MASTER_SITE_XORG</td>
1.340 ! gutterid 4350: <td> </td>
1.299 rillig 4351: </tr>
4352: </table>
4353: <p>Some explanations for the less self-explaining ones:
4354: <code class="varname">MASTER_SITE_BACKUP</code> contains backup sites
4355: for packages that are maintained in <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/%24%7BDIST_SUBDIR%7D" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}</a>. <code class="varname">MASTER_SITE_LOCAL</code> contains local
4356: package source distributions that are maintained in <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/LOCAL_PORTS/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/LOCAL_PORTS/</a>.</p>
4357: <p>If you choose one of these predefined sites, you may
4358: want to specify a subdirectory of that site. Since these
4359: macros may expand to more than one actual site, you
4360: <span class="emphasis"><em>must</em></span> use the following construct to
4361: specify a subdirectory:</p>
1.100 rillig 4362: <pre class="programlisting">
1.299 rillig 4363: MASTER_SITES= ${MASTER_SITE_GNU:=subdirectory/name/}
4364: MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/}
1.100 rillig 4365: </pre>
1.299 rillig 4366: <p>Note the trailing slash after the subdirectory
4367: name.</p>
4368: </div>
4369: <div class="sect2">
4370: <div class="titlepage"><div><div><h3 class="title">
4371: <a name="build.fetch.how"></a>13.5.2. How are the files fetched?</h3></div></div></div>
4372: <p>The <span class="emphasis"><em>fetch</em></span> phase makes sure that
4373: all the distfiles exist in a local directory
4374: (<code class="varname">DISTDIR</code>, which can be set by the pkgsrc
4375: user). If the files do not exist, they are fetched using
4376: commands of the form</p>
1.100 rillig 4377: <pre class="programlisting">
1.299 rillig 4378: ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
4379: </pre>
4380: <p>where <code class="literal">${site}</code> varies through
4381: several possibilities in turn: first,
4382: <code class="varname">MASTER_SITE_OVERRIDE</code> is tried, then the
4383: sites specified in either <code class="varname">SITES.file</code> if
4384: defined, else <code class="varname">MASTER_SITES</code> or
4385: <code class="varname">PATCH_SITES</code>, as applies, then finally the
4386: value of <code class="varname">MASTER_SITE_BACKUP</code>. The order of
4387: all except the first and the last can be optionally sorted
4388: by the user, via setting either
4389: <code class="varname">MASTER_SORT_RANDOM</code>, and
4390: <code class="varname">MASTER_SORT_AWK</code> or
4391: <code class="varname">MASTER_SORT_REGEX</code>.</p>
4392: <p> The specific command and arguments used depend on the
4393: <code class="varname">FETCH_USING</code> parameter. The example above is
4394: for <code class="literal">FETCH_USING=custom</code>.</p>
4395: <p>The distfiles mirror run by the NetBSD Foundation uses the
4396: <span class="emphasis"><em>mirror-distfiles</em></span> target to mirror the
4397: distfiles, if they are freely distributable. Packages setting
4398: <code class="varname">NO_SRC_ON_FTP</code> (usually to
4399: <span class="quote">“<span class="quote">${RESTRICTED}</span>”</span>) will not have their distfiles
4400: mirrored.</p>
1.85 jmmv 4401: </div>
4402: </div>
1.299 rillig 4403: <div class="sect1">
4404: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4405: <a name="build.checksum"></a>13.6. The <span class="emphasis"><em>checksum</em></span> phase</h2></div></div></div>
4406: <p>After the distfile(s) are fetched, their checksum is
4407: generated and compared with the checksums stored in the
4408: distinfo file. If the checksums don't match, the build is
4409: aborted. This is to ensure the same distfile is used for
4410: building, and that the distfile wasn't changed, e.g. by some
4411: malign force, deliberately changed distfiles on the master
4412: distribution site or network lossage.</p>
1.75 rillig 4413: </div>
1.148 asau 4414: <div class="sect1">
1.75 rillig 4415: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4416: <a name="build.extract"></a>13.7. The <span class="emphasis"><em>extract</em></span> phase</h2></div></div></div>
4417: <p>When the distfiles are present on the local system, they
4418: need to be extracted, as they usually come in the form of some
4419: compressed archive format.</p>
4420: <p>By default, all <code class="varname">DISTFILES</code> are
4421: extracted. If you only need some of them, you can set the
4422: <code class="varname">EXTRACT_ONLY</code> variable to the list of those
4423: files.</p>
4424: <p>Extracting the files is usually done by a little
4425: program, <code class="filename">mk/extract/extract</code>, which
4426: already knows how to extract various archive formats, so most
4427: likely you will not need to change anything here. But if you
4428: need, the following variables may help you:</p>
1.148 asau 4429: <div class="variablelist"><dl class="variablelist">
1.299 rillig 4430: <dt><span class="term"><code class="varname">EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}</code></span></dt>
4431: <dd><p>Use these variables to override the default
4432: options for an extract command, which are defined in
4433: <code class="filename">mk/extract/extract</code>.</p></dd>
4434: <dt><span class="term"><code class="varname">EXTRACT_USING</code></span></dt>
4435: <dd><p>This variable can be set to
4436: <code class="literal">bsdtar</code>, <code class="literal">gtar</code>, <code class="literal">nbtar</code>
4437: (which is the default value), <code class="literal">pax</code>, or an
4438: absolute pathname pointing to the command with which tar
4439: archives should be extracted. It is preferred to choose bsdtar over gtar
4440: if NetBSD's pax-as-tar is not good enough.</p></dd>
1.75 rillig 4441: </dl></div>
1.299 rillig 4442: <p>If the <code class="filename">extract</code> program doesn't
4443: serve your needs, you can also override the
4444: <code class="varname">EXTRACT_CMD</code> variable, which holds the
4445: command used for extracting the files. This command is
4446: executed in the <code class="filename">${WRKSRC}</code>
4447: directory. During execution of this command, the shell
4448: variable <code class="varname">extract_file</code> holds the absolute
4449: pathname of the file that is going to be extracted.</p>
4450: <p>And if that still does not suffice, you can override the
4451: <code class="varname">do-extract</code> target in the package
4452: Makefile.</p>
1.75 rillig 4453: </div>
1.148 asau 4454: <div class="sect1">
1.75 rillig 4455: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4456: <a name="build.patch"></a>13.8. The <span class="emphasis"><em>patch</em></span> phase</h2></div></div></div>
4457: <p>After extraction, all the patches named by the
4458: <code class="varname">PATCHFILES</code>, those present in the patches
4459: subdirectory of the package as well as in
4460: $LOCALPATCHES/$PKGPATH (e.g.
4461: <code class="filename">/usr/local/patches/graphics/png</code>) are
4462: applied. Patchfiles ending in <code class="filename">.Z</code> or
4463: <code class="filename">.gz</code> are uncompressed before they are
4464: applied, files ending in <code class="filename">.orig</code> or
4465: <code class="filename">.rej</code> are ignored. Any special options to
1.322 leot 4466: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
1.299 rillig 4467: <code class="varname">PATCH_DIST_ARGS</code>. See <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a> for more details.</p>
1.322 leot 4468: <p>By default <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given special arguments to make it
1.299 rillig 4469: fail if the expected text from the patch context is not found in the
4470: patched file. If that happens, fix the patch file by comparing it
4471: with the actual text in the file to be patched.</p>
1.78 rillig 4472: </div>
1.148 asau 4473: <div class="sect1">
1.75 rillig 4474: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4475: <a name="build.tools"></a>13.9. The <span class="emphasis"><em>tools</em></span> phase</h2></div></div></div>
4476: <p>This is covered in <a class="xref" href="#tools" title="Chapter 17. Tools needed for building or running">Chapter 17, <i>Tools needed for building or running</i></a>.
4477: </p>
1.75 rillig 4478: </div>
1.148 asau 4479: <div class="sect1">
1.75 rillig 4480: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4481: <a name="build.wrapper"></a>13.10. The <span class="emphasis"><em>wrapper</em></span> phase</h2></div></div></div>
4482: <p>This phase creates wrapper programs for the compilers and
4483: linkers. The following variables can be used to tweak the
4484: wrappers.</p>
4485: <div class="variablelist"><dl class="variablelist">
4486: <dt><span class="term"><code class="varname">ECHO_WRAPPER_MSG</code></span></dt>
4487: <dd><p>The command used to print progress
4488: messages. Does nothing by default. Set to
4489: <code class="literal">${ECHO}</code> to see the progress
4490: messages.</p></dd>
4491: <dt><span class="term"><code class="varname">WRAPPER_DEBUG</code></span></dt>
4492: <dd><p>This variable can be set to
4493: <code class="literal">yes</code> (default) or <code class="literal">no</code>,
4494: depending on whether you want additional information in the
4495: wrapper log file.</p></dd>
4496: <dt><span class="term"><code class="varname">WRAPPER_UPDATE_CACHE</code></span></dt>
4497: <dd><p>This variable can be set to
4498: <code class="literal">yes</code> or <code class="literal">no</code>, depending
4499: on whether the wrapper should use its cache, which will
4500: improve the speed. The default value is
4501: <code class="literal">yes</code>, but is forced to
4502: <code class="literal">no</code> if the platform does not support
4503: it.</p></dd>
4504: <dt><span class="term"><code class="varname">WRAPPER_REORDER_CMDS</code></span></dt>
4505: <dd><p>A list of reordering commands. A reordering
4506: command has the form
4507: <code class="literal">reorder:l:<em class="replaceable"><code>lib1</code></em>:<em class="replaceable"><code>lib2</code></em></code>.
4508: It ensures that that
4509: <code class="literal">-l<em class="replaceable"><code>lib1</code></em></code> occurs
4510: before <code class="literal">-l<em class="replaceable"><code>lib2</code></em></code>.
4511: </p></dd>
4512: </dl></div>
4513: </div>
4514: <div class="sect1">
4515: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4516: <a name="build.configure"></a>13.11. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
4517: <p>Most pieces of software need information on the header
4518: files, system calls, and library routines which are available
4519: on the platform they run on. The process of determining this
4520: information is known as configuration, and is usually
4521: automated. In most cases, a script is supplied with the
4522: distfiles, and its invocation results in generation of header
4523: files, Makefiles, etc.</p>
4524: <p>If the package contains a configure script, this can be
4525: invoked by setting <code class="varname">HAS_CONFIGURE</code> to
4526: <span class="quote">“<span class="quote">yes</span>”</span>. If the configure script is a GNU autoconf
4527: script, you should set <code class="varname">GNU_CONFIGURE</code> to
1.301 rillig 4528: <span class="quote">“<span class="quote">yes</span>”</span> instead.</p>
4529: <p>In the <code class="literal">do-configure</code> stage, a rough
4530: equivalent of the following command is run. See
4531: <code class="filename">mk/configure/configure.mk</code>, target
4532: <code class="literal">do-configure-script</code> for the exact
4533: definition.</p>
4534: <pre class="programlisting">
4535: .for dir in ${CONFIGURE_DIRS}
4536: cd ${WRKSRC} && cd ${dir} \
4537: && env ${CONFIGURE_ENV} \
4538: ${CONFIG_SHELL} ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
1.299 rillig 4539: .endfor
1.100 rillig 4540: </pre>
1.299 rillig 4541: <p><code class="varname">CONFIGURE_DIRS</code> (default:
4542: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4543: <code class="varname">WRKSRC</code>. In each of these directories, the
4544: configure script is run with the environment
4545: <code class="varname">CONFIGURE_ENV</code> and arguments
4546: <code class="varname">CONFIGURE_ARGS</code>. The variables
4547: <code class="varname">CONFIGURE_ENV</code>,
4548: <code class="varname">CONFIGURE_SCRIPT</code> (default:
4549: <span class="quote">“<span class="quote">./configure</span>”</span>) and
4550: <code class="varname">CONFIGURE_ARGS</code> may all be changed by the
4551: package.</p>
4552: <p>If the program uses the Perl way of configuration (mainly Perl
4553: modules, but not only), i.e. a file called
4554: <code class="filename">Makefile.PL</code>, it should include
4555: <code class="filename">../../lang/perl5/module.mk</code>. To set any parameter for
4556: <code class="filename">Makefile.PL</code> use the <code class="varname">MAKE_PARAMS</code>
4557: variable (e.g., <code class="literal">MAKE_PARAMS+=foo=bar</code></p>
4558: <p>If the program uses an <code class="filename">Imakefile</code>
4559: for configuration, the appropriate steps can be invoked by
4560: setting <code class="varname">USE_IMAKE</code> to
4561: <span class="quote">“<span class="quote">yes</span>”</span>. If you only need xmkmf, add it to <code class="varname">USE_TOOLS</code>.
4562: You can add variables to xmkmf's environment by adding them to the
4563: <code class="varname">SCRIPTS_ENV</code> variable.</p>
4564: <p>If the program uses <code class="filename">cmake</code>
4565: for configuration, the appropriate steps can be invoked by
4566: setting <code class="varname">USE_CMAKE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.
4567: You can add variables to cmake's environment by adding them to the
4568: <code class="varname">CONFIGURE_ENV</code> variable and arguments to cmake
4569: by adding them to the <code class="varname">CMAKE_ARGS</code> variable.
4570: The top directory argument is given by the
4571: <code class="varname">CMAKE_ARG_PATH</code> variable, that defaults to
4572: <span class="quote">“<span class="quote">.</span>”</span> (relative to <code class="varname">CONFIGURE_DIRS</code>)</p>
4573: <p>If there is no configure step at all, set
4574: <code class="varname">NO_CONFIGURE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.75 rillig 4575: </div>
1.148 asau 4576: <div class="sect1">
1.75 rillig 4577: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4578: <a name="build.build"></a>13.12. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.301 rillig 4579: <p>For building a package, a rough equivalent of the following
4580: code is executed; see <code class="filename">mk/build/build.mk</code>, target
4581: <code class="literal">do-build</code> for the exact definition.</p>
1.97 rillig 4582: <pre class="programlisting">
1.301 rillig 4583: .for dir in ${BUILD_DIRS}
4584: cd ${WRKSRC} && cd ${dir} \
1.299 rillig 4585: && env ${MAKE_ENV} \
1.301 rillig 4586: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${BUILD_MAKE_FLAGS} \
1.299 rillig 4587: -f ${MAKE_FILE} \
4588: ${BUILD_TARGET}
4589: .endfor
1.97 rillig 4590: </pre>
1.299 rillig 4591: <p><code class="varname">BUILD_DIRS</code> (default:
4592: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4593: <code class="varname">WRKSRC</code>. In each of these directories,
4594: <code class="varname">MAKE_PROGRAM</code> is run with the environment
4595: <code class="varname">MAKE_ENV</code> and arguments
4596: <code class="varname">BUILD_MAKE_FLAGS</code>. The variables
4597: <code class="varname">MAKE_ENV</code>,
4598: <code class="varname">BUILD_MAKE_FLAGS</code>,
4599: <code class="varname">MAKE_FILE</code> and
4600: <code class="varname">BUILD_TARGET</code> may all be changed by the
4601: package.</p>
4602: <p>The default value of <code class="varname">MAKE_PROGRAM</code> is
4603: <span class="quote">“<span class="quote">gmake</span>”</span> if <code class="varname">USE_TOOLS</code> contains
4604: <span class="quote">“<span class="quote">gmake</span>”</span>, <span class="quote">“<span class="quote">make</span>”</span> otherwise. The
4605: default value of <code class="varname">MAKE_FILE</code> is
4606: <span class="quote">“<span class="quote">Makefile</span>”</span>, and <code class="varname">BUILD_TARGET</code>
4607: defaults to <span class="quote">“<span class="quote">all</span>”</span>.</p>
4608: <p>If there is no build step at all, set
4609: <code class="varname">NO_BUILD</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.97 rillig 4610: </div>
1.148 asau 4611: <div class="sect1">
1.97 rillig 4612: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4613: <a name="build.test"></a>13.13. The <span class="emphasis"><em>test</em></span> phase</h2></div></div></div>
4614: <p>[TODO]</p>
1.75 rillig 4615: </div>
1.148 asau 4616: <div class="sect1">
1.75 rillig 4617: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4618: <a name="build.install"></a>13.14. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
4619: <p>Once the build stage has completed, the final step is to
4620: install the software in public directories, so users can
4621: access the programs and files.</p>
1.301 rillig 4622: <p>In the <span class="emphasis"><em>install</em></span> phase, a rough equivalent
4623: of the following code is executed; see
4624: <code class="filename">mk/install/install.mk</code>, target
4625: <code class="literal">do-install</code> for the exact definition. Additionally,
4626: before and after this code, several consistency checks are run
4627: against the files-to-be-installed, see
4628: <code class="filename">mk/check/*.mk</code> for details.</p>
4629: <pre class="programlisting">
4630: .for dir in ${INSTALL_DIRS}
4631: cd ${WRKSRC} && cd ${dir} \
4632: && env ${INSTALL_ENV} ${MAKE_ENV} \
4633: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${INSTALL_MAKE_FLAGS} \
4634: -f ${MAKE_FILE} ${INSTALL_TARGET}
1.299 rillig 4635: .endfor
1.220 wiz 4636: </pre>
1.299 rillig 4637: <p>The variable's meanings are analogous to the ones in the
4638: <span class="emphasis"><em>build</em></span> phase.
4639: <code class="varname">INSTALL_DIRS</code> defaults to
4640: <code class="varname">BUILD_DIRS</code>. <code class="varname">INSTALL_TARGET</code>
4641: is <span class="quote">“<span class="quote">install</span>”</span> by default, plus
4642: <span class="quote">“<span class="quote">install.man</span>”</span> if <code class="varname">USE_IMAKE</code> is
4643: defined and <code class="varname">NO_INSTALL_MANPAGES</code> is not
4644: defined.</p>
4645: <p>In the <span class="emphasis"><em>install</em></span> phase, the following
4646: variables are useful. They are all variations of the
1.322 leot 4647: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that have the owner, group and
1.299 rillig 4648: permissions preset. <code class="varname">INSTALL</code> is the plain
4649: install command. The specialized variants, together with their
4650: intended use, are:</p>
4651: <div class="variablelist"><dl class="variablelist">
4652: <dt><span class="term"><code class="varname">INSTALL_PROGRAM_DIR</code></span></dt>
4653: <dd><p>directories that contain
4654: binaries</p></dd>
4655: <dt><span class="term"><code class="varname">INSTALL_SCRIPT_DIR</code></span></dt>
4656: <dd><p>directories that contain
4657: scripts</p></dd>
4658: <dt><span class="term"><code class="varname">INSTALL_LIB_DIR</code></span></dt>
4659: <dd><p>directories that contain shared and static
4660: libraries</p></dd>
4661: <dt><span class="term"><code class="varname">INSTALL_DATA_DIR</code></span></dt>
4662: <dd><p>directories that contain data
4663: files</p></dd>
4664: <dt><span class="term"><code class="varname">INSTALL_MAN_DIR</code></span></dt>
4665: <dd><p>directories that contain man
4666: pages</p></dd>
4667: <dt><span class="term"><code class="varname">INSTALL_GAME_DIR</code></span></dt>
4668: <dd><p>directories that contain data files for games
4669: </p></dd>
4670: <dt><span class="term"><code class="varname">INSTALL_PROGRAM</code></span></dt>
4671: <dd><p>binaries that can be stripped from debugging
4672: symbols</p></dd>
4673: <dt><span class="term"><code class="varname">INSTALL_SCRIPT</code></span></dt>
4674: <dd><p>binaries that cannot be
4675: stripped</p></dd>
4676: <dt><span class="term"><code class="varname">INSTALL_GAME</code></span></dt>
4677: <dd><p>game
4678: binaries</p></dd>
4679: <dt><span class="term"><code class="varname">INSTALL_LIB</code></span></dt>
4680: <dd><p>shared and static
4681: libraries</p></dd>
4682: <dt><span class="term"><code class="varname">INSTALL_DATA</code></span></dt>
4683: <dd><p>data files</p></dd>
4684: <dt><span class="term"><code class="varname">INSTALL_GAME_DATA</code></span></dt>
4685: <dd><p>data files for
4686: games</p></dd>
4687: <dt><span class="term"><code class="varname">INSTALL_MAN</code></span></dt>
4688: <dd><p>man pages</p></dd>
4689: </dl></div>
4690: <p>Some other variables are:</p>
4691: <div class="variablelist"><dl class="variablelist">
4692: <dt><span class="term"><code class="varname">INSTALL_UNSTRIPPED</code></span></dt>
1.322 leot 4693: <dd><p>If set to <code class="literal">yes</code>, do not run <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/strip.1"><span class="citerefentry"><span class="refentrytitle">strip</span>(1)</span></a>
1.299 rillig 4694: when installing binaries. Any debugging sections and symbols present in
4695: binaries will be preserved.
4696: </p></dd>
4697: <dt><span class="term"><code class="varname">INSTALLATION_DIRS</code></span></dt>
4698: <dd><p>A list of directories relative to
4699: <code class="varname">PREFIX</code> that are created by pkgsrc at the
4700: beginning of the <span class="emphasis"><em>install</em></span> phase.
4701: The package is supposed to create all needed directories itself
4702: before installing files to it and list all other directories here.
4703: </p></dd>
4704: </dl></div>
4705: <p>In the rare cases that a package shouldn't install anything,
4706: set <code class="varname">NO_INSTALL</code> to <span class="quote">“<span class="quote">yes</span>”</span>. This is
4707: mostly relevant for packages in the <code class="filename">regress</code>
4708: category.</p>
1.75 rillig 4709: </div>
1.148 asau 4710: <div class="sect1">
1.75 rillig 4711: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4712: <a name="build.package"></a>13.15. The <span class="emphasis"><em>package</em></span> phase</h2></div></div></div>
4713: <p>Once the install stage has completed, a binary package of
4714: the installed files can be built. These binary packages can be
4715: used for quick installation without previous compilation, e.g. by
4716: the <span class="command"><strong>make bin-install</strong></span> or by using
4717: <span class="command"><strong>pkg_add</strong></span>.</p>
4718: <p>By default, the binary packages are created in
4719: <code class="filename">${PACKAGES}/All</code> and symlinks are created in
4720: <code class="filename">${PACKAGES}/<em class="replaceable"><code>category</code></em></code>,
4721: one for each category in the <code class="varname">CATEGORIES</code>
4722: variable. <code class="varname">PACKAGES</code> defaults to
4723: <code class="filename">pkgsrc/packages</code>.</p>
1.75 rillig 4724: </div>
1.148 asau 4725: <div class="sect1">
1.75 rillig 4726: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4727: <a name="build.clean"></a>13.16. Cleaning up</h2></div></div></div>
4728: <p>Once you're finished with a package, you can clean the work
4729: directory by running <span class="command"><strong>make clean</strong></span>. If you want
4730: to clean the work directories of all dependencies too, use
4731: <span class="command"><strong>make clean-depends</strong></span>.</p>
1.75 rillig 4732: </div>
1.148 asau 4733: <div class="sect1">
1.75 rillig 4734: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 4735: <a name="build.helpful-targets"></a>13.17. Other helpful targets</h2></div></div></div>
1.148 asau 4736: <div class="variablelist"><dl class="variablelist">
1.299 rillig 4737: <dt><span class="term">pre/post-*</span></dt>
4738: <dd>
4739: <p>For any of the main targets described in the previous
4740: section (configure, build, install, etc.), two auxiliary
4741: targets exist with
4742: <span class="quote">“<span class="quote">pre-</span>”</span> and <span class="quote">“<span class="quote">post-</span>”</span> used as a
4743: prefix for the main target's name. These targets are
4744: invoked before and after the main target is called,
4745: allowing extra configuration or installation steps be
4746: performed from a package's Makefile, for example, which
4747: a program's configure script or install target
4748: omitted.</p>
4749: <p>About 5% of the pkgsrc packages define their custom
4750: post-extract target, another 5% define pre-configure, and 10%
4751: define post-install. The other pre/post-* targets are defined
4752: even less often.</p>
4753: </dd>
4754: <dt><span class="term">do-*</span></dt>
1.75 rillig 4755: <dd>
1.299 rillig 4756: <p>Should one of the main targets do the wrong thing,
4757: and should there be no variable to fix this, you can
4758: redefine it with the do-* target. (Note that redefining
4759: the target itself instead of the do-* target is a bad
4760: idea, as the pre-* and post-* targets won't be called
4761: anymore, etc.)</p>
4762: <p>About 15% of the pkgsrc packages override the default
4763: do-install, the other do-* targets are overridden even less
4764: often.</p>
1.75 rillig 4765: </dd>
1.299 rillig 4766: <dt><span class="term">reinstall</span></dt>
1.75 rillig 4767: <dd>
1.299 rillig 4768: <p>If you did a <span class="command"><strong>make install</strong></span> and
4769: you noticed some file was not installed properly, you
4770: can repeat the installation with this target, which will
4771: ignore the <span class="quote">“<span class="quote">already installed</span>”</span> flag.</p>
4772: <p>This is the default value of
4773: <code class="varname">DEPENDS_TARGET</code> except in the case of
4774: <span class="command"><strong>make update</strong></span> and <span class="command"><strong>make
4775: package</strong></span>, where the defaults are
4776: <span class="quote">“<span class="quote">package</span>”</span> and <span class="quote">“<span class="quote">update</span>”</span>,
4777: respectively.</p>
1.75 rillig 4778: </dd>
1.299 rillig 4779: <dt><span class="term">deinstall</span></dt>
4780: <dd>
1.322 leot 4781: <p>This target does a <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> in the
1.299 rillig 4782: current directory, effectively de-installing the
4783: package. The following variables can be used to tune the
4784: behaviour:</p>
4785: <div class="variablelist"><dl class="variablelist">
4786: <dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt>
1.322 leot 4787: <dd><p>Add a "-v" to the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
1.299 rillig 4788: <dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt>
4789: <dd><p>Remove all packages that require (depend on)
4790: the given package. This can be used to remove any
4791: packages that may have been pulled in by a given
4792: package, e.g. if <span class="command"><strong>make deinstall
4793: DEINSTALLDEPENDS=1</strong></span> is done in
4794: <code class="filename">pkgsrc/x11/kde</code>, this is
4795: likely to remove whole KDE. Works by adding
1.322 leot 4796: <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
1.299 rillig 4797: command line.</p></dd>
4798: </dl></div>
4799: </dd>
4800: <dt><span class="term">bin-install</span></dt>
4801: <dd><p>Install a binary package from local disk and via FTP
4802: from a list of sites (see the
4803: <code class="varname">BINPKG_SITES</code> variable), and do a
4804: <span class="command"><strong>make package</strong></span> if no binary package is
4805: available anywhere. The arguments given to
4806: <span class="command"><strong>pkg_add</strong></span> can be set via
4807: <code class="varname">BIN_INSTALL_FLAGS</code> e.g., to do verbose
4808: operation, etc.</p></dd>
4809: <dt><span class="term">install-clean</span></dt>
4810: <dd><p>This target removes the state files for the "install" and later
4811: phases so that the "install" target may be re-invoked. This can be
4812: used after editing the PLIST to install the package without
4813: rebuilding it.</p></dd>
4814: <dt><span class="term">build-clean</span></dt>
4815: <dd><p>This target removes the state files for the "build" and later
4816: phases so that the "build" target may be re-invoked.</p></dd>
4817: <dt><span class="term">update</span></dt>
4818: <dd>
4819: <p>This target causes the current package to be
4820: updated to the latest version. The package and all
4821: depending packages first get de-installed, then current
4822: versions of the corresponding packages get compiled and
4823: installed. This is similar to manually noting which
4824: packages are currently installed, then performing a
4825: series of <span class="command"><strong>make deinstall</strong></span> and
4826: <span class="command"><strong>make install</strong></span> (or whatever
4827: <code class="varname">UPDATE_TARGET</code> is set to) for these
4828: packages.</p>
4829: <p>You can use the <span class="quote">“<span class="quote">update</span>”</span> target to
4830: resume package updating in case a previous <span class="command"><strong>make
4831: update</strong></span> was interrupted for some reason.
4832: However, in this case, make sure you don't call
4833: <span class="command"><strong>make clean</strong></span> or otherwise remove the
4834: list of dependent packages in <code class="varname">WRKDIR</code>.
4835: Otherwise, you lose the ability to automatically update
4836: the current package along with the dependent packages
4837: you have installed.</p>
4838: <p>Resuming an interrupted <span class="command"><strong>make
4839: update</strong></span> will only work as long as the package
4840: tree remains unchanged. If the source code for one of
4841: the packages to be updated has been changed, resuming
4842: <span class="command"><strong>make update</strong></span> will most certainly
4843: fail!</p>
4844: <p>The following variables can be used either on the
4845: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
4846: alter the behaviour of <span class="command"><strong>make
4847: update</strong></span>:</p>
4848: <div class="variablelist"><dl class="variablelist">
4849: <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt>
4850: <dd><p>Install target to recursively use for the
4851: updated package and the dependent packages.
4852: Defaults to <code class="varname">DEPENDS_TARGET</code> if
4853: set, <span class="quote">“<span class="quote">install</span>”</span> otherwise for
4854: <span class="command"><strong>make update</strong></span>. Other good
4855: targets are <span class="quote">“<span class="quote">package</span>”</span> or
4856: <span class="quote">“<span class="quote">bin-install</span>”</span>. Do not set this to
4857: <span class="quote">“<span class="quote">update</span>”</span> or you will get stuck in an
4858: endless loop!</p></dd>
4859: <dt><span class="term"><code class="varname">NOCLEAN</code></span></dt>
4860: <dd><p>Don't clean up after updating. Useful if
4861: you want to leave the work sources of the updated
4862: packages around for inspection or other purposes.
4863: Be sure you eventually clean up the source tree
4864: (see the <span class="quote">“<span class="quote">clean-update</span>”</span> target below)
4865: or you may run into troubles with old source code
4866: still lying around on your next
4867: <span class="command"><strong>make</strong></span> or <span class="command"><strong>make
4868: update</strong></span>.</p></dd>
4869: <dt><span class="term"><code class="varname">REINSTALL</code></span></dt>
4870: <dd><p>Deinstall each package before installing
4871: (making <code class="varname">DEPENDS_TARGET</code>). This
4872: may be necessary if the
4873: <span class="quote">“<span class="quote">clean-update</span>”</span> target (see below) was
4874: called after interrupting a running <span class="command"><strong>make
4875: update</strong></span>.</p></dd>
4876: <dt><span class="term"><code class="varname">DEPENDS_TARGET</code></span></dt>
4877: <dd><p>Allows you to disable recursion and hardcode
4878: the target for packages. The default is
4879: <span class="quote">“<span class="quote">update</span>”</span> for the update target,
4880: facilitating a recursive update of prerequisite
4881: packages. Only set
4882: <code class="varname">DEPENDS_TARGET</code> if you want to
4883: disable recursive updates. Use
4884: <code class="varname">UPDATE_TARGET</code> instead to just
4885: set a specific target for each package to be
4886: installed during <span class="command"><strong>make update</strong></span>
4887: (see above).</p></dd>
4888: </dl></div>
4889: </dd>
4890: <dt><span class="term">clean-update</span></dt>
4891: <dd>
4892: <p>Clean the source tree for all packages that would
4893: get updated if <span class="command"><strong>make update</strong></span> was called
4894: from the current directory. This target should not be
4895: used if the current package (or any of its depending
4896: packages) have already been de-installed (e.g., after
4897: calling <span class="command"><strong>make update</strong></span>) or you may lose
4898: some packages you intended to update. As a rule of
4899: thumb: only use this target <span class="emphasis"><em>before</em></span>
4900: the first time you run <span class="command"><strong>make update</strong></span>
4901: and only if you have a dirty package tree (e.g., if you
4902: used <code class="varname">NOCLEAN</code>).</p>
4903: <p>If you are unsure about whether your tree is
4904: clean, you can either perform a <span class="command"><strong>make
4905: clean</strong></span> at the top of the tree, or use the
4906: following sequence of commands from the directory of the
4907: package you want to update (<span class="emphasis"><em>before</em></span>
4908: running <span class="command"><strong>make update</strong></span> for the first
4909: time, otherwise you lose all the packages you wanted to
4910: update!):</p>
4911: <pre class="screen">
4912: <code class="prompt">#</code> <strong class="userinput"><code>make clean-update</code></strong>
4913: <code class="prompt">#</code> <strong class="userinput"><code>make clean CLEANDEPENDS=YES</code></strong>
4914: <code class="prompt">#</code> <strong class="userinput"><code>make update</code></strong>
4915: </pre>
4916: <p>The following variables can be used either on the
4917: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of
4918: <span class="command"><strong>make clean-update</strong></span>:</p>
4919: <div class="variablelist"><dl class="variablelist">
4920: <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt>
4921: <dd><p>After <span class="command"><strong>make clean</strong></span>, do not
4922: reconstruct the list of directories to update for
4923: this package. Only use this if <span class="command"><strong>make
4924: update</strong></span> successfully installed all
4925: packages you wanted to update. Normally, this is
4926: done automatically on <span class="command"><strong>make
4927: update</strong></span>, but may have been suppressed by
4928: the <code class="varname">NOCLEAN</code> variable (see
4929: above).</p></dd>
4930: </dl></div>
4931: </dd>
4932: <dt><span class="term">replace</span></dt>
4933: <dd>
4934: <p>Update the installation of the current package. This
4935: differs from update in that it does not replace dependent
1.322 leot 4936: packages. You will need to install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/index.html" target="_top"><code class="filename">pkgtools/pkg_tarup</code></a> for this
1.299 rillig 4937: target to work.</p>
4938: <p><span class="emphasis"><em>Be careful when using this
4939: target!</em></span> There are no guarantees that dependent
4940: packages will still work, in particular they will most
4941: certainly break if you <span class="command"><strong>make replace</strong></span> a
4942: library package whose shared library major version changed
4943: between your installed version and the new one. For this
4944: reason, this target is not officially supported and only
4945: recommended for advanced users.</p>
4946: </dd>
4947: <dt><span class="term">info</span></dt>
1.322 leot 4948: <dd><p>This target invokes <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a> for the current
1.299 rillig 4949: package. You can use this to check which version of a
4950: package is installed.</p></dd>
4951: <dt><span class="term">index</span></dt>
4952: <dd>
4953: <p>This is a top-level command, i.e. it should be used in
4954: the <code class="filename">pkgsrc</code> directory. It creates a
4955: database of all packages in the local pkgsrc tree, including
4956: dependencies, comment, maintainer, and some other useful
4957: information. Individual entries are created by running
4958: <span class="command"><strong>make describe</strong></span> in the packages'
4959: directories. This index file is saved as
4960: <code class="filename">pkgsrc/INDEX</code>. It can be displayed in
4961: verbose format by running <span class="command"><strong>make
4962: print-index</strong></span>. You can search in it with
4963: <span class="command"><strong>make search
4964: key=<em class="replaceable"><code>something</code></em></strong></span>. You can
4965: extract a list of all packages that depend on a particular
4966: one by running <span class="command"><strong>make show-deps
4967: PKG=<em class="replaceable"><code>somepackage</code></em></strong></span>.</p>
4968: <p>Running this command takes a very long time, some
4969: hours even on fast machines!</p>
4970: </dd>
4971: <dt><span class="term">readme</span></dt>
4972: <dd>
4973: <p>This target generates a
1.314 nia 4974: <code class="filename">index.html</code> file, which can be
1.322 leot 4975: viewed using a browser such as <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/index.html" target="_top"><code class="filename">www/firefox</code></a> or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/links/index.html" target="_top"><code class="filename">www/links</code></a>. The generated files
1.299 rillig 4976: contain references to any packages which are in the
4977: <code class="varname">PACKAGES</code> directory on the local
4978: host. The generated files can be made to refer to URLs
4979: based on <code class="varname">FTP_PKG_URL_HOST</code> and
4980: <code class="varname">FTP_PKG_URL_DIR</code>. For example, if I
1.314 nia 4981: wanted to generate <code class="filename">index.html</code>
1.299 rillig 4982: files which pointed to binary packages on the local
4983: machine, in the directory
4984: <code class="filename">/usr/packages</code>, set
4985: <code class="varname">FTP_PKG_URL_HOST=file://localhost</code> and
4986: <code class="varname">FTP_PKG_URL_DIR=/usr/packages</code>. The
4987: <code class="varname">${PACKAGES}</code> directory and its
4988: subdirectories will be searched for all the binary
4989: packages.</p>
4990: <p>The target can be run at the toplevel or in category
4991: directories, in which case it descends recursively.</p>
4992: </dd>
4993: <dt><span class="term">readme-all</span></dt>
4994: <dd><p>This is a top-level command, run it in
4995: <code class="filename">pkgsrc</code>. Use this target to create a
4996: file <code class="filename">README-all.html</code> which contains a
4997: list of all packages currently available in the NetBSD
4998: Packages Collection, together with the category they belong
4999: to and a short description. This file is compiled from the
1.314 nia 5000: <code class="filename">pkgsrc/*/index.html</code> files, so be sure
1.299 rillig 5001: to run this <span class="emphasis"><em>after</em></span> a <span class="command"><strong>make
5002: readme</strong></span>.</p></dd>
5003: <dt><span class="term">cdrom-readme</span></dt>
5004: <dd><p>This is very much the same as the
5005: <span class="quote">“<span class="quote">readme</span>”</span> target (see above), but is to be
5006: used when generating a pkgsrc tree to be written to a
5007: CD-ROM. This target also produces
1.314 nia 5008: <code class="filename">index.html</code> files, and can be made
1.299 rillig 5009: to refer to URLs based on
5010: <code class="varname">CDROM_PKG_URL_HOST</code> and
5011: <code class="varname">CDROM_PKG_URL_DIR</code>.</p></dd>
5012: <dt><span class="term">show-distfiles</span></dt>
5013: <dd><p>This target shows which distfiles and patchfiles
5014: are needed to build the package
5015: (<code class="varname">ALLFILES</code>, which contains all
5016: <code class="varname">DISTFILES</code> and
5017: <code class="varname">PATCHFILES</code>, but not
5018: <code class="filename">patches/*</code>).</p></dd>
5019: <dt><span class="term">show-downlevel</span></dt>
5020: <dd><p>This target shows nothing if the package is not
5021: installed. If a version of this package is installed,
5022: but is not the version provided in this version of
5023: pkgsrc, then a warning message is displayed. This target
5024: can be used to show which of your installed packages are
5025: downlevel, and so the old versions can be deleted, and
5026: the current ones added.</p></dd>
5027: <dt><span class="term">show-pkgsrc-dir</span></dt>
5028: <dd><p>This target shows the directory in the pkgsrc
5029: hierarchy from which the package can be built and
5030: installed. This may not be the same directory as the one
5031: from which the package was installed. This target is
5032: intended to be used by people who may wish to upgrade
5033: many packages on a single host, and can be invoked from
5034: the top-level pkgsrc Makefile by using the
5035: <span class="quote">“<span class="quote">show-host-specific-pkgs</span>”</span> target.</p></dd>
5036: <dt><span class="term">show-installed-depends</span></dt>
5037: <dd><p>This target shows which installed packages match
5038: the current package's <code class="varname">DEPENDS</code>. Useful
5039: if out of date dependencies are causing build
5040: problems.</p></dd>
5041: <dt><span class="term">print-build-depends-list</span></dt>
5042: <dd><p>This target shows the list of packages that the current package
5043: depends on for building.</p></dd>
5044: <dt><span class="term">print-run-depends-list</span></dt>
5045: <dd><p>This target shows the list of packages that the current package
5046: depends on for running.</p></dd>
5047: <dt><span class="term">check-shlibs</span></dt>
5048: <dd><p>After a package is installed, check all its
5049: binaries and (on ELF platforms) shared libraries to see
5050: if they find the shared libs they need. Run by default
5051: if <code class="varname">PKG_DEVELOPER</code> is set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p></dd>
5052: <dt><span class="term">print-PLIST</span></dt>
5053: <dd>
5054: <p>After a <span class="quote">“<span class="quote">make install</span>”</span> from a new or
5055: upgraded pkg, this prints out an attempt to generate a
5056: new <code class="filename">PLIST</code> from a <span class="command"><strong>find
5057: -newer work/.extract_done</strong></span>. An attempt is made
5058: to care for shared libs etc., but it is
5059: <span class="emphasis"><em>strongly</em></span> recommended to review the
5060: result before putting it into
5061: <code class="filename">PLIST</code>. On upgrades, it's useful to
5062: diff the output of this command against an already
5063: existing <code class="filename">PLIST</code> file.</p>
1.322 leot 5064: <p>If the package installs files via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/tar.1"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a> or
1.299 rillig 5065: other methods that don't update file access times, be
5066: sure to add these files manually to your
5067: <code class="filename">PLIST</code>, as the <span class="quote">“<span class="quote">find
5068: -newer</span>”</span> command used by this target won't catch
5069: them!</p>
5070: <p>See <a class="xref" href="#print-PLIST" title="19.3. Tweaking output of make print-PLIST">Section 19.3, “Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>”</a> for more
5071: information on this target.</p>
5072: </dd>
5073: </dl></div>
5074: </div>
5075: </div>
5076: <div class="chapter">
5077: <div class="titlepage"><div><div><h2 class="title">
5078: <a name="creating"></a>Chapter 14. Creating a new pkgsrc package from scratch</h2></div></div></div>
5079: <div class="toc">
5080: <p><b>Table of Contents</b></p>
5081: <dl class="toc">
5082: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
5083: <dd><dl>
1.334 nia 5084: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
5085: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
5086: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.299 rillig 5087: </dl></dd>
5088: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
5089: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">14.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
5090: </dl>
5091: </div>
5092: <p>When you find a package that is not yet in pkgsrc, you
5093: most likely have a URL from where you can download the source
5094: code. Starting with this URL, creating a package involves only a
5095: few steps.</p>
5096: <div class="procedure"><ol class="procedure" type="1">
5097: <li class="step"><p>In your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, set <code class="code">PKG_DEVELOPER=yes</code> to
5098: enable the basic quality checks.</p></li>
5099: <li class="step">
1.322 leot 5100: <p>Install the package <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/pkg_developer/index.html" target="_top"><code class="filename">meta-pkgs/pkg_developer</code></a>, which among others will
1.299 rillig 5101: install the utilities <span class="command"><strong>url2pkg</strong></span>,
5102: <span class="command"><strong>pkglint</strong></span>, <span class="command"><strong>pkgvi</strong></span> and
5103: <span class="command"><strong>mkpatches</strong></span>:</p>
5104: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
5105: <code class="prompt">$</code> <strong class="userinput"><code>(cd meta-pkgs/pkg_developer && bmake update)</code></strong></pre>
5106: </li>
5107: <li class="step">
5108: <p>Choose one of the top-level directories as the category in
5109: which you want to place your package. You can also create a directory of
1.334 nia 5110: your own (maybe called <code class="filename">local</code>). Change into that
5111: category directory:</p>
5112: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd <em class="replaceable"><code>category</code></em></code></strong></pre>
1.299 rillig 5113: </li>
5114: <li class="step">
1.334 nia 5115: <p>Run the program <span class="command"><strong>url2pkg</strong></span>, passing as
5116: argument the URL of the distribution file (in most cases a
5117: <code class="filename">.tar.gz</code> file). This will download the distribution
5118: file and create the necessary files of the package, based on what's in
5119: the distribution file:</p>
1.299 rillig 5120: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>url2pkg <em class="replaceable"><code>https://www.example.org/packages/package-1.0.tar.gz</code></em></code></strong></pre>
5121: </li>
5122: <li class="step">
5123: <p>Examine the extracted files to determine the dependencies of
5124: your package. Ideally, this is mentioned in some
5125: <code class="filename">README</code> file, but things may differ. For each of
5126: these dependencies, look where it exists in pkgsrc, and if there is a
5127: file called <code class="filename">buildlink3.mk</code> in that directory, add a
5128: line to your package <code class="filename">Makefile</code> which includes that
5129: file just before the last line. If the
5130: <code class="filename">buildlink3.mk</code> file does not exist, it must be
5131: created first. The <code class="filename">buildlink3.mk</code> file makes sure
5132: that the package's include files and libraries are provided.</p>
1.334 nia 5133: <p>If you just need binaries from a dependent package, add a
1.299 rillig 5134: <code class="varname">DEPENDS</code> line to the Makefile, which specifies the
5135: version of the dependency and where it can be found in pkgsrc. This line
5136: should be placed in the third paragraph. If the dependency is only
5137: needed for building the package, but not when using it, use
5138: <code class="varname">TOOL_DEPENDS</code> or <code class="varname">BUILD_DEPENDS</code>
5139: instead of <code class="varname">DEPENDS</code>.
5140: The difference between <code class="varname">TOOL_DEPENDS</code> and
5141: <code class="varname">BUILD_DEPENDS</code> occurs when cross-compiling:
5142: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
1.334 nia 5143: packages, i.e. packages for the platform where the package is built;
1.299 rillig 5144: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.334 nia 5145: packages, i.e. packages for the platform for which the package
5146: is built. There is also <code class="varname">TEST_DEPENDS</code>, which
5147: specifies a dependency used only for testing the resulting package
5148: built, using the upstream project's included test suite, on the native
5149: platform.
1.299 rillig 5150: Your package may then look like this:</p>
5151: <pre class="programlisting">
5152: [...]
5153:
5154: TOOL_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
5155: DEPENDS+= screen-[0-9]*:../../misc/screen
5156: DEPENDS+= screen>=4.0:../../misc/screen
5157:
5158: [...]
5159:
5160: .include "../../<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>package</code></em>/buildlink3.mk"
5161: .include "../../devel/glib2/buildlink3.mk"
5162: .include "../../mk/bsd.pkg.mk"
5163: </pre>
5164: </li>
5165: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need
5166: to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't
5167: know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint
5168: --explain</strong></span> or <span class="command"><strong>pkglint -e</strong></span>, which outputs
5169: additional explanations.</p></li>
5170: <li class="step"><p>In many cases the package is not yet ready to build. You can
5171: find instructions for the most common cases in the next section, <a class="xref" href="#creating.common" title="14.1. Common types of packages">Section 14.1, “Common types of packages”</a>. After you have followed the instructions
5172: over there, you can hopefully continue here.</p></li>
5173: <li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working
5174: directory from the extracted files. Besides these files, a lot of cache
1.334 nia 5175: files and other system information have been saved in the working
5176: directory, which may have become outdated after you edited the
1.299 rillig 5177: <code class="filename">Makefile</code>.</p></li>
5178: <li class="step">
5179: <p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For
5180: the various things that can go wrong in this phase, consult <a class="xref" href="#fixes" title="Chapter 21. Making your package work">Chapter 21, <i>Making your package work</i></a>.</p>
1.334 nia 5181: <p>If the extracted files from the package need to be fixed, run
5182: multiple rounds of these commands:</p>
5183: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>bmake</code></strong>
1.299 rillig 5184: <code class="prompt">$</code> <strong class="userinput"><code>pkgvi ${WRKSRC}/some/file/that/does/not/compile</code></strong>
5185: <code class="prompt">$</code> <strong class="userinput"><code>mkpatches</code></strong>
1.334 nia 5186: <code class="prompt">$</code> <strong class="userinput"><code>bmake mps</code></strong>
5187: <code class="prompt">$</code> <strong class="userinput"><code>bmake clean</code></strong></pre>
1.299 rillig 5188: </li>
5189: <li class="step"><p>When the package builds fine, the next step is to install
5190: the package. Run <span class="command"><strong>bmake install</strong></span> and hope that
5191: everything works.</p></li>
5192: <li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which
5193: contains a list of the files that are installed by the package, is
5194: nearly empty. Run <span class="command"><strong>bmake print-PLIST
5195: >PLIST</strong></span> to generate a probably correct list. Check
5196: the file using your preferred text editor to see if the list of
5197: files looks plausible.</p></li>
5198: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated
5199: <code class="filename">PLIST</code> contains garbage or not.</p></li>
5200: <li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package
5201: had been registered in the database of installed files, but with an
5202: empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span>
5203: and <span class="command"><strong>bmake install</strong></span> again. Now the package is
5204: registered with the list of files from
5205: <code class="filename">PLIST</code>.</p></li>
5206: <li class="step"><p>Run <span class="command"><strong>bmake clean update</strong></span> to run everything
5207: from above again in a single step, making sure that the PLIST is correct
5208: and the whole package is created as intended.</p></li>
1.334 nia 5209: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see if there's anything
5210: left to do.</p></li>
1.299 rillig 5211: <li class="step"><p>Commit the package to pkgsrc-wip or main pkgsrc; see <a class="xref" href="#submit" title="Chapter 23. Submitting and Committing">Chapter 23, <i>Submitting and Committing</i></a>.</p></li>
5212: </ol></div>
5213: <div class="sect1">
5214: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5215: <a name="creating.common"></a>14.1. Common types of packages</h2></div></div></div>
5216: <div class="sect2">
5217: <div class="titlepage"><div><div><h3 class="title">
1.334 nia 5218: <a name="creating.python-module"></a>14.1.1. Python modules and programs</h3></div></div></div>
1.299 rillig 5219: <p>Python modules and programs packages are easily created using a
5220: set of predefined variables.</p>
5221: <p>
5222: If some Python versions are not supported by the software, set the
5223: <code class="varname">PYTHON_VERSIONS_INCOMPATIBLE</code> variable to the Python versions
5224: that are not supported, e.g.
5225: </p>
5226: <pre class="programlisting">
5227: PYTHON_VERSIONS_INCOMPATIBLE= 27
5228: </pre>
5229: <p>
5230: If the packaged software is a Python module, include one of
1.330 wiz 5231: <code class="filename">../../lang/python/egg.mk</code> or
1.299 rillig 5232: <code class="filename">../../lang/python/extension.mk</code>.</p>
1.330 wiz 5233: <p>Most Python packages use setuptools (<span class="quote">“<span class="quote">eggs</span>”</span>).
1.299 rillig 5234: If the packaged software is using setuptools, you only need
5235: to include <span class="quote">“<span class="quote"><code class="filename">../../lang/python/egg.mk</code></span>”</span>.
1.330 wiz 5236: </p>
1.299 rillig 5237: <p>Either way, the package directory should be called
5238: <span class="quote">“<span class="quote">py-software</span>”</span> and <code class="varname">PKGNAME</code> should be set to
5239: <span class="quote">“<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>”</span>, e.g.
5240: </p>
5241: <pre class="programlisting">
5242: DISTNAME= foopymodule-1.2.10
5243: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
5244: </pre>
5245: <p>If it is an application, include
5246: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>”</span>.
5247: In order to correctly set the path to the Python interpreter, use the
5248: <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
5249: (paths relative to <code class="varname">WRKSRC</code>) that must be corrected.
5250: For example:
5251: </p>
5252: <pre class="programlisting">
5253: REPLACE_PYTHON= *.py
5254: </pre>
5255: <p>Some Python modules have separate distributions for Python-2.x
5256: and Python-3.x support. In pkgsrc this is handled by the
5257: <code class="filename">versioned_dependencies.mk</code> file. Set
5258: <code class="varname">PYTHON_VERSIONED_DEPENDENCIES</code> to the list of
5259: packages that should be depended upon and include
5260: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/versioned_dependencies.mk</code></span>”</span>,
5261: then the pkgsrc infrastructure will depend on the appropriate package
5262: version. For example:
5263: </p>
5264: <pre class="programlisting">
5265: PYTHON_VERSIONED_DEPENDENCIES=dialog
5266: </pre>
5267: <p>
5268: Look inside <code class="filename">versioned_dependencies.mk</code> for a list
5269: of supported packages.</p>
5270: </div>
5271: <div class="sect2">
5272: <div class="titlepage"><div><div><h3 class="title">
1.334 nia 5273: <a name="creating.R-package"></a>14.1.2. R packages</h3></div></div></div>
1.299 rillig 5274: <p>Simple R packages from <a class="ulink" href="https://cran.r-project.org/web/packages/available_packages_by_name.html" target="_top">CRAN</a>
5275: are handled automatically by <span class="command"><strong>R2pkg</strong></span>, which is
1.322 leot 5276: available in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/R2pkg/index.html" target="_top"><code class="filename">pkgtools/R2pkg</code></a>.
1.299 rillig 5277: Individual packages (and optionally their dependencies) may be created
5278: and updated. R packages generally follow the same form, and most of
5279: the relevant information needed is contained in a
5280: <code class="filename">DESCRIPTION</code> file as part of each R package on
5281: <a class="ulink" href="https://cran.r-project.org/web/packages/available_packages_by_name.html" target="_top">CRAN</a>.
5282: Consequently, <span class="command"><strong>R2pkg</strong></span> downloads that information and
5283: creates or updates a package in the canonical form. The resulting
5284: package should be reviewed for correctness.</p>
5285: </div>
5286: <div class="sect2">
5287: <div class="titlepage"><div><div><h3 class="title">
1.334 nia 5288: <a name="creating.TeX-package"></a>14.1.3. TeXlive packages</h3></div></div></div>
1.299 rillig 5289: <p>TeXlive packages from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> are handled automatically by
1.322 leot 5290: <span class="command"><strong>texlive2pkg</strong></span>, which is available in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/texlive2pkg/index.html" target="_top"><code class="filename">pkgtools/texlive2pkg</code></a>.</p>
1.299 rillig 5291: <p>If the TeXlive package name is not known, it may be useful to
5292: search <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>. A
5293: <span class="quote">“<span class="quote">Contained in</span>”</span> field on the package page typically
5294: identifies the basename of the package file in the <a class="ulink" href="https://www.ctan.org/tex-archive/systems/texlive/tlnet/archive" target="_top">TeXlive
5295: archive</a>.</p>
5296: <p>If the TeXlive package name is known, download the files from
5297: the <a class="ulink" href="https://www.ctan.org/tex-archive/systems/texlive/tlnet/archive" target="_top">TeXlive
5298: archive</a>. For package <code class="filename">foo</code>, you will need
5299: to download <code class="filename">foo.tar.xz</code>. Most TeXlive packages
5300: also have associated documentation packages, so download
5301: <code class="filename">foo.doc.tar.xz</code> at the same time. These files
5302: should be placed in the appropriate category directory, which is often
5303: but not always <code class="filename">print</code>. Then run the following
5304: command in the category directory.</p>
5305: <pre class="programlisting">
5306: texlive2pkg foo.tar.xz foo.doc.tar.xz
5307: </pre>
5308: <p>This will create two packages, <code class="filename">tex-foo</code> and
5309: <code class="filename">tex-foo-doc</code>. Be sure to check that both packages
5310: are correct.</p>
5311: <p>Finally, <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>
5312: currently does not include version information in package filenames
5313: and changes their contents periodically when updates occur.
5314: Consequently, pkgsrc avoids downloading distfiles directly from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> and instead relies on the
5315: pkgsrc archives. For each new or updated TeXlive package, e.g., the
5316: main one and the corresponding documentation, upload the distfiles
5317: with the following command in each package directory.</p>
5318: <pre class="programlisting">
5319: make upload-distfiles
5320: </pre>
5321: </div>
5322: </div>
5323: <div class="sect1">
5324: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5325: <a name="creating.examples"></a>14.2. Examples</h2></div></div></div>
5326: <div class="sect2">
5327: <div class="titlepage"><div><div><h3 class="title">
5328: <a name="creating.nvu"></a>14.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div>
5329: <div class="sect3">
5330: <div class="titlepage"><div><div><h4 class="title">
5331: <a name="creating.nvu.init"></a>14.2.1.1. The initial package</h4></div></div></div>
5332: <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
5333: that the <span class="quote">“<span class="quote">nvu</span>”</span> package has not yet been imported into
5334: pkgsrc. As the description says it has to do with the web, the obvious
5335: choice for the category is <span class="quote">“<span class="quote">www</span>”</span>.</p>
5336: <pre class="programlisting">
5337: <code class="prompt">$</code> mkdir www/nvu
5338: <code class="prompt">$</code> cd www/nvu
5339: </pre>
5340: <p>The web site says that the sources are available as a tar file, so
5341: I fed that URL to the <span class="command"><strong>url2pkg</strong></span> program:</p>
5342: <pre class="programlisting">
5343: <code class="prompt">$</code> url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5344: </pre>
5345: <p>My editor popped up, and I added a <code class="varname">PKGNAME</code> line
5346: below the <code class="varname">DISTNAME</code> line, as the package name should
5347: not have the word <span class="quote">“<span class="quote">sources</span>”</span> in it. I also filled in the
5348: <code class="varname">MAINTAINER</code>, <code class="varname">HOMEPAGE</code> and
5349: <code class="varname">COMMENT</code> fields. Then the package
5350: <code class="filename">Makefile</code> looked like that:</p>
5351: <pre class="programlisting">
5352: # $NetBSD $
5353: #
5354:
5355: DISTNAME= nvu-1.0-sources
5356: PKGNAME= nvu-1.0
5357: CATEGORIES= www
5358: MASTER_SITES= http://cvs.nvu.com/download/
5359: EXTRACT_SUFX= .tar.bz2
5360:
5361: MAINTAINER= rillig@NetBSD.org
5362: HOMEPAGE= http://cvs.nvu.com/
5363: COMMENT= Web Authoring System
5364:
5365: # url2pkg-marker (please do not remove this line.)
5366: .include "../../mk/bsd.pkg.mk"
5367: </pre>
5368: <p>On the first line of output above, an artificial space has been added between NetBSD and $,
5369: this is a workaround to prevent CVS expanding to the filename of the
5370: guide.</p>
5371: <p>Then, I quit the editor and watched pkgsrc downloading a large
5372: source archive:</p>
5373: <pre class="programlisting">
5374: url2pkg> Running "make makesum" ...
5375: => Required installed package digest>=20010302: digest-20060826 found
5376: => Fetching nvu-1.0-sources.tar.bz2
5377: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5378: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
5379: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
5380: url2pkg> Running "make extract" ...
5381: => Required installed package digest>=20010302: digest-20060826 found
5382: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5383: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5384: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
5385: ===> Installing dependencies for nvu-1.0
5386: ===> Overriding tools for nvu-1.0
5387: ===> Extracting for nvu-1.0
5388: url2pkg> Adjusting the Makefile.
5389:
5390: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
5391:
5392: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
5393: </pre>
5394: </div>
5395: <div class="sect3">
5396: <div class="titlepage"><div><div><h4 class="title">
5397: <a name="creating.nvu.problems"></a>14.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div>
5398: <p>Now that the package has been extracted, let's see what's inside
5399: it. The package has a <code class="filename">README.txt</code>, but that only
5400: says something about mozilla, so it's probably useless for seeing what
5401: dependencies this package has. But since there is a GNU configure script
5402: in the package, let's hope that it will complain about everything it
5403: needs.</p>
5404: <pre class="programlisting">
5405: <code class="prompt">$</code> bmake
5406: => Required installed package digest>=20010302: digest-20060826 found
5407: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5408: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5409: ===> Patching for nvu-1.0
5410: ===> Creating toolchain wrappers for nvu-1.0
5411: ===> Configuring for nvu-1.0
5412: [...]
5413: configure: error: Perl 5.004 or higher is required.
5414: [...]
5415: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
5416: [...]
5417: </pre>
5418: <p>That worked quite well. So I opened the package Makefile in my
5419: editor, and since it already has a <code class="varname">USE_TOOLS</code> line, I
5420: just appended <span class="quote">“<span class="quote">perl</span>”</span> to it. Since the dependencies of the
5421: package have changed now, and since a perl wrapper is automatically
5422: installed in the <span class="quote">“<span class="quote">tools</span>”</span> phase, I need to build the package
5423: from scratch.</p>
5424: <pre class="programlisting">
5425: <code class="prompt">$</code> bmake clean
5426: ===> Cleaning for nvu-1.0
5427: <code class="prompt">$</code> bmake
5428: [...]
5429: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
5430: GNU Make. You will not be able to build Mozilla without GNU Make.
5431: [...]
5432: </pre>
5433: <p>So I added <span class="quote">“<span class="quote">gmake</span>”</span> to the
5434: <code class="varname">USE_TOOLS</code> line and tried again (from scratch).</p>
5435: <pre class="programlisting">
5436: [...]
5437: checking for GTK - version >= 1.2.0... no
5438: *** Could not run GTK test program, checking why...
5439: [...]
5440: </pre>
5441: <p>Now to the other dependencies. The first question is: Where is the
5442: GTK package hidden in pkgsrc?</p>
5443: <pre class="programlisting">
5444: <code class="prompt">$</code> echo ../../*/gtk*
5445: [many packages ...]
5446: <code class="prompt">$</code> echo ../../*/gtk
5447: ../../x11/gtk
5448: <code class="prompt">$</code> echo ../../*/gtk2
5449: ../../x11/gtk2
5450: <code class="prompt">$</code> echo ../../*/gtk2/bui*
5451: ../../x11/gtk2/buildlink3.mk
5452: </pre>
5453: <p>The first try was definitely too broad. The second one had exactly
5454: one result, which is very good. But there is one pitfall with GNOME
5455: packages. Before GNOME 2 had been released, there were already many
5456: GNOME 1 packages in pkgsrc. To be able to continue to use these
5457: packages, the GNOME 2 packages were imported as separate packages, and
5458: their names usually have a <span class="quote">“<span class="quote">2</span>”</span> appended. So I checked
5459: whether this was the case here, and indeed it was.</p>
5460: <p>Since the GTK2 package has a <code class="filename">buildlink3.mk</code>
5461: file, adding the dependency is very easy. I just inserted an
5462: <code class="literal">.include</code> line before the last line of the package
5463: <code class="filename">Makefile</code>, so that it now looks like this:</p>
5464: <pre class="programlisting">
5465: [...]
5466: .include "../../x11/gtk2/buildlink3.mk"
5467: .include "../../mk/bsd.pkg.mk
5468: </pre>
5469: <p>After another <span class="command"><strong>bmake clean && bmake</strong></span>, the answer
5470: was:</p>
1.75 rillig 5471: <pre class="programlisting">
1.299 rillig 5472: [...]
5473: checking for gtk-config... /home/roland/pkg/bin/gtk-config
5474: checking for GTK - version >= 1.2.0... no
5475: *** Could not run GTK test program, checking why...
5476: *** The test program failed to compile or link. See the file config.log for the
5477: *** exact error that occured. This usually means GTK was incorrectly installed
5478: *** or that you have moved GTK since it was installed. In the latter case, you
5479: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
5480: configure: error: Test for GTK failed.
5481: [...]
1.222 sevan 5482: </pre>
1.299 rillig 5483: <p>In this particular case, the assumption that <span class="quote">“<span class="quote">every package
5484: prefers GNOME 2</span>”</span> had been wrong. The first of the lines above
5485: told me that this package really wanted to have the GNOME 1 version of
5486: GTK. If the package had looked for GTK2, it would have looked for
5487: <span class="command"><strong>pkg-config</strong></span> instead of <span class="command"><strong>gtk-config</strong></span>.
5488: So I changed the <code class="literal">x11/gtk2</code> to
5489: <code class="literal">x11/gtk</code> in the package <code class="filename">Makefile</code>,
5490: and tried again.</p>
1.119 mishka 5491: <pre class="programlisting">
1.299 rillig 5492: [...]
5493: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
5494: In file included from xpidl.c:42:
5495: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
5496: In file included from xpidl.c:42:
5497: xpidl.h:132: error: parse error before "IDL_ns"
5498: [...]
1.222 sevan 5499: </pre>
1.299 rillig 5500: <p>The package still does not find all of its dependencies. Now the
5501: question is: Which package provides the
5502: <code class="filename">libIDL/IDL.h</code> header file?</p>
1.119 mishka 5503: <pre class="programlisting">
1.299 rillig 5504: <code class="prompt">$</code> echo ../../*/*idl*
5505: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
5506: <code class="prompt">$</code> echo ../../*/*IDL*
5507: ../../net/libIDL
1.222 sevan 5508: </pre>
1.299 rillig 5509: <p>Let's take the one from the second try. So I included the
5510: <code class="filename">../../net/libIDL/buildlink3.mk</code> file and tried
5511: again. But the error didn't change. After digging through some of the
5512: code, I concluded that the build process of the package was broken and
5513: couldn't have ever worked, but since the Mozilla source tree is quite
5514: large, I didn't want to fix it. So I added the following to the package
5515: <code class="filename">Makefile</code> and tried again:</p>
1.197 wiz 5516: <pre class="programlisting">
1.299 rillig 5517: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
5518: BUILDLINK_TRANSFORM+= l:IDL:IDL-2
1.222 sevan 5519: </pre>
1.299 rillig 5520: <p>The latter line is needed because the package expects the library
5521: <code class="filename">libIDL.so</code>, but only
5522: <code class="filename">libIDL-2.so</code> is available. So I told the compiler
5523: wrapper to rewrite that on the fly.</p>
5524: <p>The next problem was related to a recent change of the FreeType
1.322 leot 5525: interface. I looked up in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/seamonkey/index.html" target="_top"><code class="filename">www/seamonkey</code></a>
1.299 rillig 5526: which patch files were relevant for this issue and copied them to the
5527: <code class="filename">patches</code> directory. Then I retried, fixed the
5528: patches so that they applied cleanly and retried again. This time,
5529: everything worked.</p>
1.197 wiz 5530: </div>
1.299 rillig 5531: <div class="sect3">
5532: <div class="titlepage"><div><div><h4 class="title">
5533: <a name="creating.nvu.inst"></a>14.2.1.3. Installing the package</h4></div></div></div>
1.87 wiz 5534: <pre class="programlisting">
1.299 rillig 5535: <code class="prompt">$</code> bmake CHECK_FILES=no install
5536: [...]
5537: <code class="prompt">$</code> bmake print-PLIST >PLIST
5538: <code class="prompt">$</code> bmake deinstall
5539: <code class="prompt">$</code> bmake install
1.222 sevan 5540: </pre>
1.299 rillig 5541: </div>
5542: </div>
1.75 rillig 5543: </div>
5544: </div>
1.148 asau 5545: <div class="chapter">
1.75 rillig 5546: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 5547: <a name="makefile"></a>Chapter 15. Programming in <code class="filename">Makefile</code>s</h2></div></div></div>
1.75 rillig 5548: <div class="toc">
5549: <p><b>Table of Contents</b></p>
1.210 leot 5550: <dl class="toc">
1.299 rillig 5551: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
5552: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
5553: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
5554: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
5555: <dd><dl>
5556: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
5557: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
5558: <dt><span class="sect2"><a href="#cflags-gnu-configure">15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</a></span></dt>
5559: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.75 rillig 5560: </dl></dd>
5561: </dl>
5562: </div>
1.299 rillig 5563: <p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments,
5564: each of which forms a well-defined part of the pkgsrc system. Using
1.322 leot 5565: the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a programming language for a big system
1.299 rillig 5566: like pkgsrc requires some discipline to keep the code correct and
5567: understandable.</p>
5568: <p>The basic ingredients for <code class="filename">Makefile</code>
5569: programming are variables and shell
5570: commands. Among these shell commands may even be more complex ones
1.322 leot 5571: like <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/awk.1"><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make sure that every shell command runs
1.299 rillig 5572: as intended it is necessary to quote all variables correctly when they
5573: are used.</p>
5574: <p>This chapter describes some patterns that appear quite often in
5575: <code class="filename">Makefile</code>s, including the pitfalls that come along
5576: with them.</p>
1.148 asau 5577: <div class="sect1">
1.75 rillig 5578: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 5579: <a name="makefile.style"></a>15.1. Caveats</h2></div></div></div>
5580: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
5581: <p>When you are creating a file as a
5582: target of a rule, always write the data to a temporary file first
5583: and finally rename that file. Otherwise there might occur an error
5584: in the middle of generating the file, and when the user runs
1.322 leot 5585: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> for the second time, the file exists and will not be
1.299 rillig 5586: regenerated properly. Example:</p>
1.75 rillig 5587: <pre class="programlisting">
1.299 rillig 5588: wrong:
5589: @echo "line 1" > ${.TARGET}
5590: @echo "line 2" >> ${.TARGET}
5591: @false
5592:
5593: correct:
5594: @echo "line 1" > ${.TARGET}.tmp
5595: @echo "line 2" >> ${.TARGET}.tmp
5596: @false
5597: @mv ${.TARGET}.tmp ${.TARGET}
1.100 rillig 5598: </pre>
1.299 rillig 5599: <p>When you run <span class="command"><strong>make wrong</strong></span> twice, the file
5600: <code class="filename">wrong</code> will exist, although there was an error
5601: message in the first run. On the other hand, running <span class="command"><strong>make
5602: correct</strong></span> gives an error message twice, as expected.</p>
1.322 leot 5603: <p>You might remember that <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> sometimes removes
1.299 rillig 5604: <code class="literal">${.TARGET}</code> in case of error, but this only
5605: happens when it is interrupted, for example by pressing
5606: <code class="literal">Ctrl+C</code>. This does <span class="emphasis"><em>not</em></span> happen
1.322 leot 5607: when one of the commands fails (like <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/false.1"><span class="citerefentry"><span class="refentrytitle">false</span>(1)</span></a> above).</p>
1.299 rillig 5608: </li></ul></div>
5609: </div>
5610: <div class="sect1">
5611: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5612: <a name="makefile.variables"></a>15.2. <code class="filename">Makefile</code> variables</h2></div></div></div>
5613: <p><code class="filename">Makefile</code> variables contain strings that
5614: can be processed using the five operators <code class="code">=</code>,
5615: <code class="code">+=</code>, <code class="code">?=</code>, <code class="code">:=</code> and
1.322 leot 5616: <code class="code">!=</code>, which are described in the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man
1.299 rillig 5617: page.</p>
5618: <p>When a variable's value is parsed from a
5619: <code class="filename">Makefile</code>, the hash character <code class="code">#</code> and
5620: the backslash character <code class="code">\</code> are handled specially. If a
5621: backslash is the last character in a line, that backslash is removed
5622: from the line and the line continues with the next line of the file.</p>
5623: <p>The <code class="code">#</code> character starts a comment that reaches
5624: until the end of the line. To get an actual <code class="code">#</code> character,
5625: such as in a URL, write <code class="code">\#</code> instead.</p>
5626: <p>The evaluation of variables either happens immediately or lazy.
5627: It happens immediately when the variable occurs on the right-hand
5628: side of the <code class="code">:=</code> or the <code class="code">!=</code> operator, in a
5629: <code class="varname">.if</code> condition or a <code class="varname">.for</code> loop.
5630: In the other cases, it is evaluated lazily.</p>
5631: <p>Some of the modifiers split the string into words and then
5632: operate on the words, others operate on the string as a whole. When a
5633: string is split into words, double quotes and single quotes are
1.322 leot 5634: interpreted as delimiters, just like in <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/sh.1"><span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span></a>.</p>
1.299 rillig 5635: <div class="sect2">
5636: <div class="titlepage"><div><div><h3 class="title">
5637: <a name="makefile.variables.names"></a>15.2.1. Naming conventions</h3></div></div></div>
5638: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
5639: <li class="listitem"><p>All variable names starting with an underscore
5640: are reserved for use by the pkgsrc infrastructure. They shall
5641: not be used by packages.</p></li>
5642: <li class="listitem"><p>In <span class="command"><strong>.for</strong></span> loops you should use
5643: lowercase variable names for the iteration
5644: variables.</p></li>
5645: <li class="listitem"><p>All list variables should have a plural name,
5646: such as <code class="varname">PKG_OPTIONS</code> or
5647: <code class="varname">DISTFILES</code>.</p></li>
5648: </ul></div>
5649: </div>
5650: </div>
5651: <div class="sect1">
5652: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5653: <a name="makefile.code"></a>15.3. Code snippets</h2></div></div></div>
5654: <div class="sect2">
5655: <div class="titlepage"><div><div><h3 class="title">
5656: <a name="adding-to-list"></a>15.3.1. Adding things to a list</h3></div></div></div>
5657: <p>When adding a string that possibly contains whitespace or quotes to
5658: a list (example 1), it must be quoted using the <code class="code">:Q</code>
5659: modifier.</p>
5660: <p>When adding another list to a list (example 2), it must not be
5661: quoted, since its elements are already quoted.</p>
1.75 rillig 5662: <pre class="programlisting">
1.299 rillig 5663: STRING= foo * bar `date`
5664: LIST= # empty
5665: ANOTHER_LIST= a=b c=d
5666:
5667: LIST+= ${STRING:Q} # 1
5668: LIST+= ${ANOTHER_LIST} # 2
1.100 rillig 5669: </pre>
1.299 rillig 5670: </div>
5671: <div class="sect2">
5672: <div class="titlepage"><div><div><h3 class="title">
5673: <a name="echo-literal"></a>15.3.2. Echoing a string exactly as-is</h3></div></div></div>
5674: <p>Echoing a string containing special characters needs special
5675: work.</p>
1.75 rillig 5676: <pre class="programlisting">
1.299 rillig 5677: STRING= foo bar < > * `date` $$HOME ' "
5678: EXAMPLE_ENV= string=${STRING:Q} x=multiple\ quoted\ words
5679:
5680: all:
5681: echo ${STRING} # 1
5682: echo ${STRING:Q} # 2
5683: printf '%s\n' ${STRING:Q}'' # 3
5684: env ${EXAMPLE_ENV} sh -c 'echo "$$string"; echo "$$x"' # 4
1.100 rillig 5685: </pre>
1.299 rillig 5686: <p>Example 1 leads to a syntax error in the shell, as the characters
5687: are just copied.</p>
5688: <p>Example 2 quotes the string so that the shell interprets it
5689: correctly. But the echo command may additionally interpret strings with a
5690: leading dash or those containing backslashes.</p>
1.322 leot 5691: <p>Example 3 can handle arbitrary strings, since <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> only
1.299 rillig 5692: interprets the format string, but not the next argument. The trailing
5693: single quotes handle the case when the string is empty. In that case, the
5694: :Q modifier would result in an empty string too, which would then be
1.322 leot 5695: skipped by the shell. For <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> this doesn't make a difference,
1.299 rillig 5696: but other programs may care.</p>
5697: <p>In example 4, the <code class="varname">EXAMPLE_ENV</code> does not
5698: need to be quoted because the quoting has already been done
5699: when adding elements to the list.</p>
1.75 rillig 5700: </div>
1.148 asau 5701: <div class="sect2">
1.75 rillig 5702: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 5703: <a name="cflags-gnu-configure"></a>15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</h3></div></div></div>
5704: <p>When passing <code class="varname">CFLAGS</code> or similar variables to a
5705: GNU-style configure script (especially those that call other configure
5706: scripts), it must not have leading or trailing whitespace, since
5707: otherwise the configure script gets confused. To trim leading and
5708: trailing whitespace, use the <code class="code">:M</code> modifier, as in the
5709: following example:</p>
1.75 rillig 5710: <pre class="programlisting">
1.299 rillig 5711: CPPFLAGS= # empty
5712: CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX}\"
5713: CPPFLAGS+= ${MY_CPPFLAGS}
1.1 grant 5714:
1.299 rillig 5715: CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
1.1 grant 5716:
1.299 rillig 5717: all:
5718: echo x${CPPFLAGS:Q}x # leading and trailing whitespace
5719: echo x${CONFIGURE_ARGS:Q}x # properly trimmed
5720: </pre>
5721: <p>In this example, <code class="varname">CPPFLAGS</code> has both leading and
5722: trailing whitespace because the <code class="code">+=</code> operator always adds a
5723: space.</p>
5724: </div>
5725: <div class="sect2">
5726: <div class="titlepage"><div><div><h3 class="title">
5727: <a name="empty-variables"></a>15.3.4. Handling possibly empty variables</h3></div></div></div>
5728: <p>When a possibly empty variable is used in a shell program, it may
5729: lead to a syntax error.</p>
5730: <pre class="programlisting">
5731: EGFILES= # empty
1.87 wiz 5732:
1.299 rillig 5733: install-examples: # produces a syntax error in the shell
5734: for egfile in ${EGFILES}; do \
5735: echo "Installing $$egfile"; \
5736: done
5737: </pre>
5738: <p>The shell only sees the text <code class="code">for egfile in ; do</code>, since
1.322 leot 5739: <code class="code">${EGFILES}</code> is replaced with an empty string by <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.
1.299 rillig 5740: To fix this syntax error, use one of the snippets below.</p>
5741: <pre class="programlisting">
5742: EMPTY= # empty
1.87 wiz 5743:
1.299 rillig 5744: install-examples:
5745: for egfile in ${EGFILES} ""; do \
5746: [ -n "$$egfile" ] || continue; \
5747: echo "Installing $$egfile"; \
5748: done
5749: </pre>
5750: <p>In this case, an empty string is appended to the iteration list (to
5751: prevent the syntax error) and filtered out later.</p>
5752: <pre class="programlisting">
5753: EGFILES= # empty
1.87 wiz 5754:
1.299 rillig 5755: install-examples:
5756: .for egfile in ${EGFILES}
5757: echo "Installing ${egfile}"
5758: .endfor
1.100 rillig 5759: </pre>
1.299 rillig 5760: <p>If one of the filenames contains special characters, it should be
5761: enclosed in single or double quotes.</p>
5762: <p>To have a shell command test whether a make variable is empty, use
5763: the following code: <code class="code">${TEST} -z ${POSSIBLY_EMPTY:Q}""</code>.</p>
5764: </div>
5765: </div>
5766: </div>
5767: <div class="chapter">
5768: <div class="titlepage"><div><div><h2 class="title">
5769: <a name="options"></a>Chapter 16. Options handling</h2></div></div></div>
5770: <div class="toc">
5771: <p><b>Table of Contents</b></p>
5772: <dl class="toc">
5773: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
5774: <dt><span class="sect1"><a href="#converting-to-options">16.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt>
5775: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
5776: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
5777: </dl>
1.75 rillig 5778: </div>
1.299 rillig 5779: <p>Many packages have the ability to be built to support different
5780: sets of features. <code class="filename">bsd.options.mk</code> is a framework
5781: in pkgsrc that provides generic handling of those options that
5782: determine different ways in which the packages can be built. It's
5783: possible for the user to specify exactly which sets of options will be
5784: built into a package or to allow a set of global default options
5785: apply.</p>
5786: <p>There are two broad classes of behaviors that one might want to
5787: control via options. One is whether some particular feature is
5788: enabled in a program that will be built anyway, often by including or
5789: not including a dependency on some other package. The other is
5790: whether or not an additional program will be built as part of the
5791: package. Generally, it is better to make a split package for such
5792: additional programs instead of using options, because it enables
5793: binary packages to be built which can then be added separately. For
5794: example, the foo package might have minimal dependencies (those
5795: packages without which foo doesn't make sense), and then the foo-gfoo
5796: package might include the GTK frontend program gfoo. This is better
5797: than including a gtk option to foo that adds gfoo, because either that
5798: option is default, in which case binary users can't get foo without
5799: gfoo, or not default, in which case they can't get gfoo. With split
5800: packages, they can install foo without having GTK, and later decide to
5801: install gfoo (pulling in GTK at that time). This is an advantage to
5802: source users too, avoiding the need for rebuilds.</p>
5803: <p>Plugins with widely varying dependencies should usually be split
5804: instead of options.</p>
5805: <p>It is often more work to maintain split packages, especially if
5806: the upstream package does not support this. The decision of split
5807: vs. option should be made based on the likelihood that users will want
5808: or object to the various pieces, the size of the dependencies that are
5809: included, and the amount of work.</p>
5810: <p>A further consideration is licensing. Non-free parts, or parts
5811: that depend on non-free dependencies (especially plugins) should
5812: almost always be split if feasible.</p>
5813: <div class="sect1">
5814: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5815: <a name="global-default-options"></a>16.1. Global default options</h2></div></div></div>
5816: <p>Global default options are listed in
5817: <code class="varname">PKG_DEFAULT_OPTIONS</code>, which is a list of the options
5818: that should be built into every package if that option is supported.
5819: This variable should be set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.75 rillig 5820: </div>
1.148 asau 5821: <div class="sect1">
1.75 rillig 5822: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 5823: <a name="converting-to-options"></a>16.2. Converting packages to use <code class="filename">bsd.options.mk</code>
5824: </h2></div></div></div>
5825: <p>The following example shows how
5826: <code class="filename">bsd.options.mk</code> should be used
5827: by the hypothetical ``wibble'' package, either in the package
5828: <code class="filename">Makefile</code>, or in a file,
5829: e.g. <code class="filename">options.mk</code>, that is included by the
5830: main package <code class="filename">Makefile</code>.</p>
1.75 rillig 5831: <pre class="programlisting">
1.299 rillig 5832: PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
5833: PKG_SUPPORTED_OPTIONS= wibble-foo ldap
5834: PKG_OPTIONS_OPTIONAL_GROUPS= database
5835: PKG_OPTIONS_GROUP.database= mysql pgsql
5836: PKG_SUGGESTED_OPTIONS= wibble-foo
5837: PKG_OPTIONS_LEGACY_VARS+= WIBBLE_USE_OPENLDAP:ldap
5838: PKG_OPTIONS_LEGACY_OPTS+= foo:wibble-foo
5839:
5840: .include "../../mk/bsd.prefs.mk"
5841:
5842: # this package was previously named wibble2
5843: .if defined(PKG_OPTIONS.wibble2)
5844: PKG_LEGACY_OPTIONS+= ${PKG_OPTIONS.wibble2}
5845: PKG_OPTIONS_DEPRECATED_WARNINGS+= \
5846: "Deprecated variable PKG_OPTIONS.wibble2 used, use ${PKG_OPTIONS_VAR} instead."
5847: .endif
5848:
5849: .include "../../mk/bsd.options.mk"
5850:
5851: # Package-specific option-handling
1.100 rillig 5852:
1.299 rillig 5853: ###
5854: ### FOO support
5855: ###
5856: .if !empty(PKG_OPTIONS:Mwibble-foo)
5857: CONFIGURE_ARGS+= --enable-foo
5858: .endif
1.100 rillig 5859:
1.299 rillig 5860: ###
5861: ### LDAP support
5862: ###
5863: .if !empty(PKG_OPTIONS:Mldap)
5864: . include "../../databases/openldap-client/buildlink3.mk"
5865: CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap-client}
5866: .endif
1.100 rillig 5867:
1.299 rillig 5868: ###
5869: ### database support
5870: ###
5871: .if !empty(PKG_OPTIONS:Mmysql)
5872: . include "../../mk/mysql.buildlink3.mk"
5873: .endif
5874: .if !empty(PKG_OPTIONS:Mpgsql)
5875: . include "../../mk/pgsql.buildlink3.mk"
5876: .endif
5877: </pre>
5878: <p>The first section contains the information about which build
5879: options are supported by the package, and any default options settings
5880: if needed.</p>
5881: <div class="orderedlist"><ol class="orderedlist" type="1">
5882: <li class="listitem"><p><code class="varname">PKG_OPTIONS_VAR</code> is the name of the
1.322 leot 5883: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> variable that the user can set to override the default
1.299 rillig 5884: options. It should be set to
5885: PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em>. Do not set it to
5886: PKG_OPTIONS.${PKGBASE}, since <code class="varname">PKGBASE</code> is not defined
5887: at the point where the options are processed.</p></li>
5888: <li class="listitem"><p><code class="varname">PKG_SUPPORTED_OPTIONS</code> is a list of
5889: build options supported by the package.</p></li>
5890: <li class="listitem"><p><code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code> is a
5891: list of names of groups of mutually exclusive options. The options in
5892: each group are listed in
5893: <code class="varname">PKG_OPTIONS_GROUP.<em class="replaceable"><code>groupname</code></em></code>.
5894: The most specific setting of any option from the group takes
5895: precedence over all other options in the group. Options from the
5896: groups will be automatically added to
5897: <code class="varname">PKG_SUPPORTED_OPTIONS</code>.</p></li>
5898: <li class="listitem"><p><code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> is like
5899: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, but building the
5900: packages will fail if no option from the group is
5901: selected.</p></li>
5902: <li class="listitem"><p><code class="varname">PKG_OPTIONS_NONEMPTY_SETS</code> is a list
5903: of names of sets of options. At least one option from each set must
5904: be selected. The options in each set are listed in
5905: <code class="varname">PKG_OPTIONS_SET.<em class="replaceable"><code>setname</code></em></code>.
5906: Options from the sets will be automatically added to
5907: <code class="varname">PKG_SUPPORTED_OPTIONS</code>. Building the package will
5908: fail if no option from the set is selected.</p></li>
5909: <li class="listitem"><p><code class="varname">PKG_SUGGESTED_OPTIONS</code> is a list of
5910: build options which are enabled by default.</p></li>
5911: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_VARS</code> is a list
5912: of
5913: <span class="quote">“<span class="quote"><em class="replaceable"><code>USE_VARIABLE</code></em>:<em class="replaceable"><code>option</code></em></span>”</span>
5914: pairs that map legacy <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> variables to
5915: their option counterparts. Pairs should be added with
5916: <span class="quote">“<span class="quote">+=</span>”</span> to keep the listing of global legacy variables. A
5917: warning will be issued if the user uses a legacy
5918: variable.</p></li>
5919: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> is a list
5920: of
5921: <span class="quote">“<span class="quote"><em class="replaceable"><code>old-option</code></em>:<em class="replaceable"><code>new-option</code></em></span>”</span>
5922: pairs that map options that have been renamed to their new
5923: counterparts. Pairs should be added with <span class="quote">“<span class="quote">+=</span>”</span> to keep
5924: the listing of global legacy options. A warning will be issued if
5925: the user uses a legacy option.</p></li>
5926: <li class="listitem"><p><code class="varname">PKG_LEGACY_OPTIONS</code> is a list of
5927: options implied by deprecated variables used. This can be used for
5928: cases that neither <code class="varname">PKG_OPTIONS_LEGACY_VARS</code> nor
5929: <code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> can handle, e. g. when
5930: <code class="varname">PKG_OPTIONS_VAR</code> is renamed.</p></li>
5931: <li class="listitem"><p><code class="varname">PKG_OPTIONS_DEPRECATED_WARNINGS</code> is
5932: a list of warnings about deprecated variables or options used, and
5933: what to use instead.</p></li>
5934: </ol></div>
5935: <p>A package should never modify
5936: <code class="varname">PKG_DEFAULT_OPTIONS</code> or the variable named in
5937: <code class="varname">PKG_OPTIONS_VAR</code>. These are strictly user-settable.
5938: To suggest a default set of options, use
5939: <code class="varname">PKG_SUGGESTED_OPTIONS</code>.</p>
5940: <p><code class="varname">PKG_OPTIONS_VAR</code> must be defined before
5941: including <code class="filename">bsd.options.mk</code>. If none of
5942: <code class="varname">PKG_SUPPORTED_OPTIONS</code>,
5943: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, and
5944: <code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> are defined (as can
5945: happen with platform-specific options if none of them is supported on
5946: the current platform), <code class="varname">PKG_OPTIONS</code> is set to the
5947: empty list and the package is otherwise treated as not using the
5948: options framework.</p>
5949: <p>After the inclusion of <code class="filename">bsd.options.mk</code>, the
5950: variable <code class="varname">PKG_OPTIONS</code> contains the list of selected
5951: build options, properly filtered to remove unsupported and duplicate
5952: options.</p>
5953: <p>The remaining sections contain the logic that is specific to
5954: each option. The correct way to check for an option is to check
5955: whether it is listed in <code class="varname">PKG_OPTIONS</code>:</p>
5956: <pre class="programlisting">
5957: .if !empty(PKG_OPTIONS:M<em class="replaceable"><code>option</code></em>)
1.100 rillig 5958: </pre>
1.75 rillig 5959: </div>
1.299 rillig 5960: <div class="sect1">
5961: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5962: <a name="option-names"></a>16.3. Option Names</h2></div></div></div>
5963: <p>Options that enable similar features in different packages (like
5964: optional support for a library) should use a common name in all
5965: packages that support it (like the name of the library). If another
5966: package already has an option with the same meaning, use the same
5967: name.</p>
5968: <p>Options that enable features specific to one package, where it's
5969: unlikely that another (unrelated) package has the same (or a similar)
5970: optional feature, should use a name prefixed with
5971: <code class="varname"><em class="replaceable"><code>pkgname</code></em>-</code>.</p>
5972: <p>If a group of related packages share an optional feature
5973: specific to that group, prefix it with the name of the
5974: <span class="quote">“<span class="quote">main</span>”</span> package
5975: (e. g. <code class="varname">djbware-errno-hack</code>).</p>
5976: <p>For new options, add a line to
5977: <code class="filename">mk/defaults/options.description</code>. Lines have two
5978: fields, separated by tab. The first field is the option name, the
5979: second its description. The description should be a whole sentence
5980: (starting with an uppercase letter and ending with a period) that
5981: describes what enabling the option does. E. g. <span class="quote">“<span class="quote">Enable ispell
5982: support.</span>”</span> The file is sorted by option names.</p>
5983: </div>
5984: <div class="sect1">
5985: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5986: <a name="option-build"></a>16.4. Determining the options of dependencies</h2></div></div></div>
5987: <p>When writing <a class="link" href="#buildlink3.mk"><code class="filename">buildlink3.mk</code></a> files, it is often necessary to list
5988: different dependencies based on the options with which the package was
5989: built. For querying these options, the file
5990: <code class="filename">pkgsrc/mk/pkg-build-options.mk</code> should be used. A
5991: typical example looks like this:</p>
1.87 wiz 5992: <pre class="programlisting">
1.299 rillig 5993: pkgbase := libpurple
5994: .include "../../mk/pkg-build-options.mk"
5995:
5996: .if !empty(PKG_BUILD_OPTIONS.libpurple:Mdbus)
5997: ...
5998: .endif
1.229 sevan 5999: </pre>
1.299 rillig 6000: <p>Including <code class="filename">pkg-build-options.mk</code> here will set
6001: the variable <code class="varname">PKG_BUILD_OPTIONS.libpurple</code> to the build
6002: options of the libpurple package, which can then be queried like
6003: <code class="varname">PKG_OPTIONS</code> in the <code class="filename">options.mk</code>
6004: file. See the file <code class="filename">pkg-build-options.mk</code> for more
6005: details.</p>
1.75 rillig 6006: </div>
6007: </div>
1.148 asau 6008: <div class="chapter">
1.75 rillig 6009: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 6010: <a name="tools"></a>Chapter 17. Tools needed for building or running</h2></div></div></div>
1.75 rillig 6011: <div class="toc">
6012: <p><b>Table of Contents</b></p>
1.210 leot 6013: <dl class="toc">
1.299 rillig 6014: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
6015: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
6016: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
1.75 rillig 6017: </dl>
6018: </div>
1.299 rillig 6019: <p>The <code class="varname">USE_TOOLS</code> definition is used both internally
6020: by pkgsrc and also for individual packages to define what commands
6021: are needed for building a package (like <code class="varname">TOOL_DEPENDS</code>)
6022: or for later run-time of an installed packaged (such as
6023: <code class="varname">DEPENDS</code>).
6024: If the native system provides an adequate tool, then in many cases, a pkgsrc
6025: package will not be used.</p>
6026: <p>When building a package, the replacement tools are
6027: made available in a directory (as symlinks or wrapper scripts)
6028: that is early in the executable search path. Just like the buildlink
6029: system, this helps with consistent builds.</p>
6030: <p>A tool may be needed to help build a specific package. For example,
6031: perl, GNU make (gmake) or yacc may be needed.</p>
6032: <p>Also a tool may be needed, for example, because the native system's supplied
6033: tool may be inefficient for building a package with pkgsrc.
6034: For example, a package may need GNU awk, bison (instead of
6035: yacc) or a better sed.</p>
6036: <p>The tools used by a package can be listed by running
6037: <span class="command"><strong>make show-tools</strong></span>.</p>
1.148 asau 6038: <div class="sect1">
1.75 rillig 6039: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6040: <a name="pkgsrc-tools"></a>17.1. Tools for pkgsrc builds</h2></div></div></div>
6041: <p>The default set of tools used by pkgsrc is defined in
6042: <code class="filename">bsd.pkg.mk</code>. This includes standard Unix tools,
6043: such as: <span class="command"><strong>cat</strong></span>, <span class="command"><strong>awk</strong></span>,
6044: <span class="command"><strong>chmod</strong></span>, <span class="command"><strong>test</strong></span>, and so on.
6045: These can be seen by running:
6046: <span class="command"><strong>make show-var VARNAME=USE_TOOLS</strong></span>.</p>
6047: <p>If a package needs a specific program to build
6048: then the <code class="varname">USE_TOOLS</code> variable can be used
6049: to define the tools needed.</p>
1.75 rillig 6050: </div>
1.299 rillig 6051: <div class="sect1">
6052: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6053: <a name="package-tools"></a>17.2. Tools needed by packages</h2></div></div></div>
6054: <p>In the following examples, the :run means that it is needed at
6055: run-time (and becomes a DEPENDS).
6056: The default is a build dependency which can be set with
6057: :build. (So in this example, it is the same as gmake:build
6058: and pkg-config:build.)</p>
1.75 rillig 6059: <pre class="programlisting">
1.299 rillig 6060: USE_TOOLS+= gmake perl:run pkg-config
1.1 grant 6061: </pre>
1.299 rillig 6062: <p>When using the tools framework, a
6063: <code class="varname">TOOLS_PATH.foo</code> variable is defined
6064: which contains the full path to the appropriate tool. For example,
6065: <code class="varname">TOOLS_PATH.bash</code> could be <span class="quote">“<span class="quote">/bin/bash</span>”</span>
6066: on Linux systems.</p>
6067: <p>If you always need a pkgsrc version of the
6068: tool at run-time, then just use <code class="varname">DEPENDS</code> instead.
6069: </p>
1.75 rillig 6070: </div>
1.299 rillig 6071: <div class="sect1">
6072: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6073: <a name="platform-tools"></a>17.3. Tools provided by platforms</h2></div></div></div>
6074: <p>When improving or porting pkgsrc to a new platform, have a look
6075: at (or create) the corresponding platform specific make file fragment under
6076: <code class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines
6077: the name of the common tools. For example:</p>
1.75 rillig 6078: <pre class="programlisting">
1.299 rillig 6079: .if exists(/usr/bin/bzcat)
6080: TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
6081: .elif exists(/usr/bin/bzip2)
6082: TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
6083: .endif
6084:
6085: TOOLS_PLATFORM.true?= true # shell builtin
1.1 grant 6086: </pre>
1.75 rillig 6087: </div>
6088: </div>
1.299 rillig 6089: <div class="chapter">
6090: <div class="titlepage"><div><div><h2 class="title">
6091: <a name="buildlink"></a>Chapter 18. Buildlink methodology</h2></div></div></div>
6092: <div class="toc">
6093: <p><b>Table of Contents</b></p>
6094: <dl class="toc">
6095: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
6096: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
6097: <dd><dl>
6098: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
6099: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
6100: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6101: and
6102: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6103: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
6104: </dl></dd>
6105: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
6106: <dd><dl>
6107: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
6108: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
6109: </dl></dd>
6110: </dl>
1.75 rillig 6111: </div>
1.299 rillig 6112: <p>Buildlink is a framework in pkgsrc that controls what headers and libraries
6113: are seen by a package's configure and build processes. This is implemented
6114: in a two step process:</p>
6115: <div class="orderedlist"><ol class="orderedlist" type="1">
6116: <li class="listitem"><p>Symlink headers and libraries for dependencies into
6117: <code class="varname">BUILDLINK_DIR</code>, which by default is a subdirectory
6118: of <code class="varname">WRKDIR</code>.</p></li>
6119: <li class="listitem"><p>Create wrapper scripts that are used in place of the normal compiler
6120: tools that translate <code class="option">-I${LOCALBASE}/include</code> and
6121: <code class="option">-L${LOCALBASE}/lib</code> into references to
6122: <code class="varname">BUILDLINK_DIR</code>. The wrapper scripts also make
6123: native compiler on some operating systems look like GCC, so that
6124: packages that expect GCC won't require modifications to build with
6125: those native compilers.</p></li>
6126: </ol></div>
6127: <p>This normalizes the environment in which a package is built so that the
6128: package may be built consistently despite what other software may be
6129: installed. Please note that the normal system header and library paths,
6130: e.g. <code class="filename">/usr/include</code>,
6131: <code class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is
6132: designed to insulate the package build from non-system-supplied
6133: software.</p>
1.148 asau 6134: <div class="sect1">
1.75 rillig 6135: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6136: <a name="converting-to-buildlink3"></a>18.1. Converting packages to use buildlink3</h2></div></div></div>
6137: <p>The process of converting packages to use the buildlink3
6138: framework (<span class="quote">“<span class="quote">bl3ifying</span>”</span>) is fairly straightforward.
6139: The things to keep in mind are:</p>
1.128 wiz 6140: <div class="orderedlist"><ol class="orderedlist" type="1">
1.299 rillig 6141: <li class="listitem"><p>Ensure that the build always calls the wrapper scripts
6142: instead of the actual toolchain. Some packages are tricky,
6143: and the only way to know for sure is the check
6144: <code class="filename">${WRKDIR}/.work.log</code> to see if the
6145: wrappers are being invoked.</p></li>
6146: <li class="listitem"><p>Don't override <code class="varname">PREFIX</code> from within
6147: the package Makefile, e.g. Java VMs, standalone shells,
6148: etc., because the code to symlink files into
6149: <code class="filename">${BUILDLINK_DIR}</code> looks for files
6150: relative to <span class="quote">“<span class="quote">pkg_info -qp <em class="replaceable"><code>pkgname</code></em></span>”</span>.
6151: </p></li>
6152: <li class="listitem"><p>Remember that <span class="emphasis"><em>only</em></span> the
6153: <code class="filename">buildlink3.mk</code> files that you list in a
6154: package's Makefile are added as dependencies for that package.
6155: </p></li>
6156: </ol></div>
6157: <p>If a dependency on a particular package is required for its libraries and
6158: headers, then we replace:</p>
6159: <pre class="programlisting">
6160: DEPENDS+= foo>=1.1.0:../../category/foo
6161: </pre>
6162: <p>with</p>
6163: <pre class="programlisting">
6164: .include "../../category/foo/buildlink3.mk"
6165: </pre>
6166: <p>The buildlink3.mk files usually define the required dependencies.
6167: If you need a newer version of the dependency when using buildlink3.mk
6168: files, then you can define it in your Makefile; for example:</p>
1.75 rillig 6169: <pre class="programlisting">
1.299 rillig 6170: BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
6171: .include "../../category/foo/buildlink3.mk"
1.1 grant 6172: </pre>
1.299 rillig 6173: <p>There are several <code class="filename">buildlink3.mk</code>
6174: files in <code class="filename">pkgsrc/mk</code>
6175: that handle special package issues:</p>
6176: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6177: <li class="listitem"><p><code class="filename">bdb.buildlink3.mk</code> chooses either
6178: the native or a pkgsrc Berkeley DB implementation based on
6179: the values of <code class="varname">BDB_ACCEPTED</code> and
6180: <code class="varname">BDB_DEFAULT</code>.</p></li>
6181: <li class="listitem"><p><code class="filename">curses.buildlink3.mk</code>: If the system
6182: comes with neither Curses nor NCurses, this will take care
1.322 leot 6183: to install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/ncurses/index.html" target="_top"><code class="filename">devel/ncurses</code></a> package.</p></li>
1.299 rillig 6184: <li class="listitem"><p><code class="filename">krb5.buildlink3.mk</code> uses the value
6185: of <code class="varname">KRB5_ACCEPTED</code> to choose between
6186: adding a dependency on Heimdal or MIT-krb5 for packages that
6187: require a Kerberos 5 implementation.</p></li>
6188: <li class="listitem"><p><code class="filename">motif.buildlink3.mk</code> checks for a
6189: system-provided Motif installation or adds a dependency on
1.322 leot 6190: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/lesstif/index.html" target="_top"><code class="filename">x11/lesstif</code></a> or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/motif/index.html" target="_top"><code class="filename">x11/motif</code></a>. The user can set
1.299 rillig 6191: <code class="varname">MOTIF_TYPE</code> to <span class="quote">“<span class="quote">dt</span>”</span>,
6192: <span class="quote">“<span class="quote">lesstif</span>”</span> or <span class="quote">“<span class="quote">motif</span>”</span>
6193: to choose which Motif version will be used.</p></li>
6194: <li class="listitem"><p><code class="filename">readline.buildlink3.mk</code> checks for a
6195: system-provided GNU readline or editline (libedit) installation,
1.322 leot 6196: or adds a dependency on <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/readline/index.html" target="_top"><code class="filename">devel/readline</code></a>,
6197: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/editline/index.html" target="_top"><code class="filename">devel/editline</code></a>. The user can set
1.299 rillig 6198: <code class="varname">READLINE_DEFAULT</code> to choose readline implementation.
6199: If your package really needs GNU readline library, its Makefile
6200: should include <code class="filename">devel/readline/buildlink3.mk</code>
6201: instead of <code class="filename">readline.buildlink3.mk</code>.</p></li>
6202: <li class="listitem"><p><code class="filename">oss.buildlink3.mk</code> defines several
6203: variables that may be used by packages that use the
6204: Open Sound System (OSS) API.</p></li>
6205: <li class="listitem"><p><code class="filename">pgsql.buildlink3.mk</code> will accept
6206: any of the Postgres versions in the variable
6207: <code class="varname">PGSQL_VERSIONS_ACCEPTED</code> and default to
6208: the version <code class="varname">PGSQL_VERSION_DEFAULT</code>. See
6209: the file for more information.</p></li>
6210: <li class="listitem"><p><code class="filename">pthread.buildlink3.mk</code> uses the value of
6211: <code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds
1.322 leot 6212: a dependency on <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/pth/index.html" target="_top"><code class="filename">devel/pth</code></a> as needed.</p></li>
1.299 rillig 6213: <li class="listitem"><p><code class="filename">xaw.buildlink3.mk</code> uses the value of
6214: <code class="varname">XAW_TYPE</code> to choose a particular Athena widgets
6215: library.</p></li>
6216: </ul></div>
6217: <p>The comments in those <code class="filename">buildlink3.mk</code>
6218: files provide a more complete
6219: description of how to use them properly.</p>
1.75 rillig 6220: </div>
1.148 asau 6221: <div class="sect1">
1.75 rillig 6222: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6223: <a name="creating-buildlink3.mk"></a>18.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div>
6224: <a name="buildlink3.mk"></a><p>A package's <code class="filename">buildlink3.mk</code> file is
6225: included by Makefiles to indicate the need to compile and link
6226: against header files and libraries provided by the package. A
6227: <code class="filename">buildlink3.mk</code> file should always provide
6228: enough information to add the correct type of dependency
6229: relationship and include any other
6230: <code class="filename">buildlink3.mk</code> files that it needs to find
6231: headers and libraries that it needs in turn.</p>
6232: <p>To generate an initial <code class="filename">buildlink3.mk</code>
1.322 leot 6233: file for further editing, Rene Hexel's <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/createbuildlink/index.html" target="_top"><code class="filename">pkgtools/createbuildlink</code></a>
1.299 rillig 6234: package is highly recommended. For most packages, the following
6235: command will generate a good starting point for
6236: <code class="filename">buildlink3.mk</code> files:</p>
6237: <pre class="screen">
6238: <code class="prompt">%</code> <strong class="userinput"><code>cd pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>pkgdir</code></em>
6239: <code class="prompt">%</code> createbuildlink >buildlink3.mk</code></strong>
6240: </pre>
1.148 asau 6241: <div class="sect2">
1.75 rillig 6242: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 6243: <a name="anatomy-of-bl3"></a>18.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div>
6244: <p>The following real-life example
6245: <code class="filename">buildlink3.mk</code> is taken
6246: from <code class="filename">pkgsrc/graphics/tiff</code>:</p>
1.75 rillig 6247: <pre class="programlisting">
1.299 rillig 6248: # $NetBSD: buildlink3.mk,v 1.16 2009/03/20 19:24:45 joerg Exp $
6249:
6250: BUILDLINK_TREE+= tiff
6251:
6252: .if !defined(TIFF_BUILDLINK3_MK)
6253: TIFF_BUILDLINK3_MK:=
6254:
6255: BUILDLINK_API_DEPENDS.tiff+= tiff>=3.6.1
6256: BUILDLINK_ABI_DEPENDS.tiff+= tiff>=3.7.2nb1
6257: BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
6258:
6259: .include "../../devel/zlib/buildlink3.mk"
6260: .include "../../graphics/jpeg/buildlink3.mk"
6261: .endif # TIFF_BUILDLINK3_MK
6262:
6263: BUILDLINK_TREE+= -tiff
1.1 grant 6264: </pre>
1.299 rillig 6265: <p>The header and footer manipulate
6266: <code class="varname">BUILDLINK_TREE</code>, which is common across all
6267: <code class="filename">buildlink3.mk</code> files and is used to track
6268: the dependency tree.</p>
6269: <p>The main section is protected from multiple inclusion
6270: and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is
6271: added. Several important variables are set in the section:</p>
6272: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6273: <li class="listitem"><p><code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.300 wiz 6274: is the dependency version recorded in the installed
1.299 rillig 6275: package; this should always be set using
6276: <span class="command"><strong>+=</strong></span> to ensure that
6277: we're appending to any pre-existing list of values. This
1.300 wiz 6278: variable should be set to the last version of the
1.299 rillig 6279: package that had an backwards-incompatible API change.
6280: </p></li>
6281: <li class="listitem"><p><code class="varname">BUILDLINK_PKGSRCDIR.<em class="replaceable"><code>pkg</code></em></code>
6282: is the location of the <em class="replaceable"><code>pkg</code></em>
6283: pkgsrc directory.</p></li>
6284: <li class="listitem"><p><code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
6285: (not shown above) controls whether we use
6286: <code class="varname">BUILD_DEPENDS</code> or
6287: <code class="varname">DEPENDS</code> to add the dependency on
6288: <em class="replaceable"><code>pkg</code></em>. The build dependency is
6289: selected by setting
6290: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
6291: to <span class="quote">“<span class="quote">build</span>”</span>. By default, the full dependency is
6292: used.</p></li>
6293: <li class="listitem"><p><code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code>
6294: and
6295: <code class="varname">BUILDLINK_LIBDIRS.<em class="replaceable"><code>pkg</code></em></code>
6296: (not shown above) are lists of subdirectories of
6297: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6298: to add to the header and library search paths. These
6299: default to <span class="quote">“<span class="quote">include</span>”</span> and <span class="quote">“<span class="quote">lib</span>”</span>
6300: respectively.</p></li>
6301: <li class="listitem"><p><code class="varname">BUILDLINK_CPPFLAGS.<em class="replaceable"><code>pkg</code></em></code>
6302: (not shown above) is the list of preprocessor flags to add
6303: to <code class="varname">CPPFLAGS</code>, which are passed on to the
6304: configure and build phases. The <span class="quote">“<span class="quote">-I</span>”</span> option
6305: should be avoided and instead be handled using
6306: <code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code> as
6307: above.</p></li>
6308: </ul></div>
6309: <p>The following variables are all optionally defined within
6310: this second section (protected against multiple inclusion) and
6311: control which package files are symlinked into
6312: <code class="filename">${BUILDLINK_DIR}</code> and how their names are
6313: transformed during the symlinking:</p>
6314: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6315: <li class="listitem"><p><code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>
6316: (not shown above) is a shell glob pattern relative to
6317: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6318: to be symlinked into
6319: <code class="filename">${BUILDLINK_DIR}</code>,
6320: e.g. <code class="filename">include/*.h</code>.</p></li>
6321: <li class="listitem"><p><code class="varname">BUILDLINK_FILES_CMD.<em class="replaceable"><code>pkg</code></em></code>
6322: (not shown above) is a shell pipeline that
6323: outputs to stdout a list of files relative to
6324: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>.
6325: The resulting files are to be symlinked
6326: into <code class="filename">${BUILDLINK_DIR}</code>. By default,
6327: this takes the <code class="filename">+CONTENTS</code> of a
6328: <em class="replaceable"><code>pkg</code></em> and filters it through
6329: <code class="varname">${BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em>}</code>.</p></li>
6330: <li class="listitem"><p><code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6331: (not shown above) is a filter command that filters
6332: <code class="filename">+CONTENTS</code> input into a list of files
6333: relative to
6334: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6335: on stdout. By default,
6336: <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6337: outputs the contents of the <code class="filename">include</code>
6338: and <code class="filename">lib</code> directories in the package
6339: <code class="filename">+CONTENTS</code>.</p></li>
6340: <li class="listitem"><p><code class="varname">BUILDLINK_FNAME_TRANSFORM.<em class="replaceable"><code>pkg</code></em></code>
6341: (not shown above) is a list of sed arguments used to
6342: transform the name of the source filename into a
6343: destination filename, e.g. <span class="command"><strong>-e
6344: "s|/curses.h|/ncurses.h|g"</strong></span>.</p></li>
6345: </ul></div>
6346: <p>This section can additionally include any
6347: <code class="filename">buildlink3.mk</code> needed for
6348: <em class="replaceable"><code>pkg</code></em>'s library dependencies.
6349: Including these <code class="filename">buildlink3.mk</code> files
6350: means that the headers and libraries for these
6351: dependencies are also symlinked into
6352: <code class="filename">${BUILDLINK_DIR}</code>
6353: whenever the <em class="replaceable"><code>pkg</code></em>
6354: <code class="filename">buildlink3.mk</code>
6355: file is included. Dependencies are only added for directly
6356: include <code class="filename">buildlink3.mk</code> files.</p>
6357: <p>When providing a <code class="filename">buildlink3.mk</code> and
6358: including other <code class="filename">buildlink3.mk</code> files in it,
6359: please only add necessary ones, i.e., those whose libraries or
6360: header files are automatically exposed when the package is
6361: use.</p>
6362: <p>In particular, if only an executable
6363: (<code class="filename">bin/foo</code>) is linked against a library, that
6364: library does not need to be propagated in the
6365: <code class="filename">buildlink3.mk</code> file.</p>
6366: <p>The following steps should help you decide if a
6367: <code class="filename">buildlink3.mk</code> file needs to be included:
6368: </p>
6369: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6370: <li class="listitem"><p>Look at the installed header files: What
6371: headers do they include? The packages providing these files
6372: must be buildlinked.</p></li>
6373: <li class="listitem"><p>Run <code class="filename">ldd</code> on all installed
6374: libraries and look against what other libraries they link.
6375: Some of the packages providing these probably need to be
6376: buildlinked; however, it's not automatic, since e.g. GTK on
6377: some systems pulls in the X libraries, so they will show up in
6378: the <code class="filename">ldd</code> output, while on others (like OS
6379: X) it won't. <code class="filename">ldd</code> output can thus only be
6380: used as a hint.</p></li>
6381: </ul></div>
6382: <p>
6383: </p>
6384: </div>
1.148 asau 6385: <div class="sect2">
1.75 rillig 6386: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 6387: <a name="updating-buildlink-depends"></a>18.2.2. Updating
6388: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6389: and
6390: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6391: in <code class="filename">buildlink3.mk</code> files</h3></div></div></div>
1.300 wiz 6392: <p>Both variables set lower bounds for a version of this package.
6393: The two variables differ in that one describes source
1.299 rillig 6394: compatibility (API) and the other binary compatibility (ABI).
6395: The difference is that a change in the API breaks compilation of
6396: programs while changes in the ABI stop compiled programs from
6397: running.</p>
1.300 wiz 6398: <p>The
6399: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6400: variable in a <code class="filename">buildlink3.mk</code> should be
6401: changed very rarely. (One possible scenario: If all packages
6402: using this package need a higher version than defined in the
6403: <code class="filename">buildlink3.mk</code>,
1.299 rillig 6404: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.300 wiz 6405: could be updated to that higher version.)</p>
6406: <p>On the other hand, changes to
1.299 rillig 6407: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.300 wiz 6408: are more common. The variable will need to be updated every
6409: time the major version of one of its shared libraries is changed,
6410: or any other change where a binary built against the previous
6411: version of the package will not run against the new version any
6412: longer.</p>
6413: <p>In such a case, the package's
1.299 rillig 6414: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.300 wiz 6415: must be increased to require the new package version. Then the
6416: <code class="varname">PKGREVISION</code> of all packages
6417: <em class="replaceable"><code>foo</code></em> that depend on this package need
6418: to be increased, and if they have
6419: <code class="filename">buildlink3.mk</code> files,
6420: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>foo</code></em></code>
6421: in their <code class="filename">buildlink3.mk</code> files must be
6422: increased to the new version as well. This is required so that a
6423: package will pull in the versions of the packages that use the
6424: new ABI and that the packages' <code class="varname">PKGREVISION</code>s
6425: uniquely identify the packages built against the new ABI. The
1.322 leot 6426: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/revbump/index.html" target="_top"><code class="filename">pkgtools/revbump</code></a> package can
1.300 wiz 6427: help with these updates.</p>
6428: <p>See <a class="xref" href="#dependencies" title="21.1.5. Handling dependencies">Section 21.1.5, “Handling dependencies”</a> for more information
6429: about dependencies on other packages, including the
6430: <code class="varname">BUILDLINK_API_DEPENDS</code> definitions.</p>
1.299 rillig 6431: <p>Please take careful consideration before adjusting
6432: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6433: or
6434: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.300 wiz 6435: in a <code class="filename">buildlink3.mk</code> file as we don't want to
6436: cause unneeded package deletions and rebuilds. In many cases,
6437: new versions of packages work just fine with older
6438: dependencies.</p>
1.326 gutterid 6439: <p>Also, it is not needed to set
1.299 rillig 6440: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6441: when it is identical to
1.326 gutterid 6442: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.</p>
6443: <p>Note there is also the distinction that users are able to disable
6444: enforcement of ABI dependencies using the <code class="varname">USE_ABI_DEPENDS</code>
6445: variable, but there is no equivalent option for API dependencies.</p>
1.75 rillig 6446: </div>
6447: </div>
1.148 asau 6448: <div class="sect1">
1.75 rillig 6449: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6450: <a name="writing-builtin.mk"></a>18.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div>
6451: <p>Some packages in pkgsrc install headers and libraries that
6452: coincide with headers and libraries present in the base system.
6453: Aside from a <code class="filename">buildlink3.mk</code> file, these
6454: packages should also include a <code class="filename">builtin.mk</code>
6455: file that includes the necessary checks to decide whether using
6456: the built-in software or the pkgsrc software is
6457: appropriate.</p>
6458: <p>The only requirements of a builtin.mk file for
6459: <em class="replaceable"><code>pkg</code></em> are:</p>
6460: <div class="orderedlist"><ol class="orderedlist" type="1">
6461: <li class="listitem"><p>It should set
6462: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6463: to either <span class="quote">“<span class="quote">yes</span>”</span> or <span class="quote">“<span class="quote">no</span>”</span>
6464: after it is included.</p></li>
6465: <li class="listitem"><p>It should <span class="emphasis"><em>not</em></span> override any
6466: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6467: which is already set before the
6468: <code class="filename">builtin.mk</code> file is included.</p></li>
6469: <li class="listitem"><p>It should be written to allow multiple inclusion. This
6470: is <span class="emphasis"><em>very</em></span> important and takes careful
6471: attention to <code class="filename">Makefile</code> coding.</p></li>
6472: </ol></div>
6473: <div class="sect2">
6474: <div class="titlepage"><div><div><h3 class="title">
6475: <a name="anatomy-of-builtin.mk"></a>18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</h3></div></div></div>
6476: <p>The following is the recommended template for builtin.mk
6477: files:</p>
1.75 rillig 6478: <pre class="programlisting">
1.299 rillig 6479: .if !defined(IS_BUILTIN.foo)
6480: #
6481: # IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
6482: # genuinely exists in the system or not.
6483: #
6484: IS_BUILTIN.foo?= no
1.100 rillig 6485:
1.299 rillig 6486: # BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
6487: # version can be determined.
6488: #
6489: . if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
6490: BUILTIN_PKG.foo?= foo-1.0
6491: . endif
6492: .endif # IS_BUILTIN.foo
1.100 rillig 6493:
1.299 rillig 6494: .if !defined(USE_BUILTIN.foo)
6495: USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
6496: . if defined(BUILTIN_PKG.foo)
6497: . for _depend_ in ${BUILDLINK_API_DEPENDS.foo}
6498: . if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
6499: USE_BUILTIN.foo!= \
6500: ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo} \
6501: && ${ECHO} "yes" || ${ECHO} "no"
6502: . endif
6503: . endfor
6504: . endif
6505: .endif # USE_BUILTIN.foo
1.100 rillig 6506:
1.299 rillig 6507: CHECK_BUILTIN.foo?= no
6508: .if !empty(CHECK_BUILTIN.foo:M[nN][oO])
6509: #
6510: # Here we place code that depends on whether USE_BUILTIN.foo is set to
6511: # "yes" or "no".
6512: #
6513: .endif # CHECK_BUILTIN.foo
1.75 rillig 6514: </pre>
1.299 rillig 6515: <p>The first section sets
6516: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6517: depending on if <em class="replaceable"><code>pkg</code></em> really exists
6518: in the base system. This should not be a base system software
6519: with similar functionality to <em class="replaceable"><code>pkg</code></em>;
6520: it should only be <span class="quote">“<span class="quote">yes</span>”</span> if the actual package is
6521: included as part of the base system. This variable is only
6522: used internally within the <code class="filename">builtin.mk</code>
6523: file.</p>
6524: <p>The second section sets
6525: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6526: to the version of <em class="replaceable"><code>pkg</code></em> in the base
6527: system if it exists (if
6528: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6529: is <span class="quote">“<span class="quote">yes</span>”</span>). This variable is only used internally
6530: within the <code class="filename">builtin.mk</code> file.</p>
6531: <p>The third section sets
6532: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6533: and is <span class="emphasis"><em>required</em></span> in all
6534: <code class="filename">builtin.mk</code> files. The code in this
6535: section must make the determination whether the built-in
6536: software is adequate to satisfy the dependencies listed in
6537: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6538: This is typically done by comparing
6539: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6540: against each of the dependencies in
6541: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6542: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6543: <span class="emphasis"><em>must</em></span> be set to the correct value by the
6544: end of the <code class="filename">builtin.mk</code> file. Note that
6545: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6546: may be <span class="quote">“<span class="quote">yes</span>”</span> even if
6547: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6548: is <span class="quote">“<span class="quote">no</span>”</span> because we may make the determination
6549: that the built-in version of the software is similar enough to
6550: be used as a replacement.</p>
6551: <p>The last section is guarded by
6552: <code class="varname">CHECK_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>,
6553: and includes code that uses the value of
6554: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6555: set in the previous section. This typically includes, e.g.,
6556: adding additional dependency restrictions and listing additional
6557: files to symlink into <code class="filename">${BUILDLINK_DIR}</code> (via
6558: <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>).</p>
6559: </div>
6560: <div class="sect2">
6561: <div class="titlepage"><div><div><h3 class="title">
6562: <a name="native-or-pkgsrc-preference"></a>18.3.2. Global preferences for native or pkgsrc software</h3></div></div></div>
6563: <p>When building packages, it's possible to choose whether to set
6564: a global preference for using either the built-in (native)
6565: version or the pkgsrc version of software to satisfy a
6566: dependency. This is controlled by setting
6567: <code class="varname">PREFER_PKGSRC</code> and
6568: <code class="varname">PREFER_NATIVE</code>. These variables take values
6569: of either <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">no</span>”</span>, or a list of
6570: packages. <code class="varname">PREFER_PKGSRC</code> tells pkgsrc to
6571: use the pkgsrc versions of software, while
6572: <code class="varname">PREFER_NATIVE</code> tells pkgsrc to use the
6573: built-in versions. Preferences are determined by the most
6574: specific instance of the package in either
6575: <code class="varname">PREFER_PKGSRC</code> or
6576: <code class="varname">PREFER_NATIVE</code>. If a package is specified
6577: in neither or in both variables, then
6578: <code class="varname">PREFER_PKGSRC</code> has precedence over
6579: <code class="varname">PREFER_NATIVE</code>. For example, to require
6580: using pkgsrc versions of software for all but the most basic
6581: bits on a NetBSD system, you can set:</p>
1.75 rillig 6582: <pre class="programlisting">
1.299 rillig 6583: PREFER_PKGSRC= yes
6584: PREFER_NATIVE= getopt skey tcp_wrappers
6585: </pre>
6586: <p>A package <span class="emphasis"><em>must</em></span> have a
6587: <code class="filename">builtin.mk</code>
6588: file to be listed in <code class="varname">PREFER_NATIVE</code>,
6589: otherwise it is simply ignored in that list.</p>
1.305 bacon 6590: <p><code class="varname">PREFER_PKGSRC</code> and
6591: <code class="varname">PREFER_NATIVE</code> should be set during bootstrap
6592: to ensure that the bootstrap process does not use inapropriate
6593: native tools as dependencies for core packages.
6594:
6595: </p>
6596: <pre class="screen">
6597: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap --prefer-pkgsrc yes --prefer-native openssl</code></strong>
6598: </pre>
6599: <p>
6600:
1.299 rillig 6601: Switching between settings globally at a later date can introduce
6602: complications with dependency resolution. This is caused by packages
1.305 bacon 6603: built with the opposite preference being installed alongside each
6604: other. Hence, any changes to these variables after bootstrap will
6605: necessitate rebuilding all packages depending on one whose preference
6606: has been changed. This is not trivial and should be avoided.</p>
6607: <p>When using pkgsrc on Linux systems, there is high risk of
6608: "leakage", where programs installed by pkgsrc may inadvertently use a
6609: command or library not installed by pkgsrc, e.g. those installed by
6610: yum or apt. Such foreign dependencies may be installed, removed, or
6611: upgraded to a version incompatible with the pkgsrc package at any
6612: time, causing pkgsrc packages to subsequently malfunction. Pkgsrc
6613: cannot prevent this, as it has no control over other package managers.
6614: Another potential problem is that under Redhat Enterprise and related
6615: Linux systems, yum packages are only patched and never upgraded, so
6616: eventually they may become too outdated for use by pkgsrc. Even
6617: intentionally using foreign dependencies, not considered leakage, can
6618: lead to these problems, so it is generally discouraged. In order to
6619: minimize such problems, PREFER_PKGSRC defaults to "yes" on Linux systems.
6620: This ensures that pkgsrc is aware of any changes to dependency packages
6621: and can rebuild or upgrade the entire dependency tree as needed. This
6622: default can be overridden by setting --prefer-pkgsrc to "no" or a list of
6623: packages, or by setting --prefer-native to "yes".</p>
1.75 rillig 6624: </div>
1.107 rillig 6625: </div>
1.75 rillig 6626: </div>
1.148 asau 6627: <div class="chapter">
1.75 rillig 6628: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 6629: <a name="plist"></a>Chapter 19. PLIST issues</h2></div></div></div>
1.75 rillig 6630: <div class="toc">
6631: <p><b>Table of Contents</b></p>
1.210 leot 6632: <dl class="toc">
1.299 rillig 6633: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
6634: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
6635: <dt><span class="sect1"><a href="#print-PLIST">19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
6636: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
6637: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
6638: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
6639: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
6640: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
6641: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.75 rillig 6642: </dl>
6643: </div>
1.299 rillig 6644: <p>The <code class="filename">PLIST</code> file contains a package's
6645: <span class="quote">“<span class="quote">packing list</span>”</span>, i.e. a list of files that belong to
6646: the package (relative to the <code class="filename">${PREFIX}</code>
6647: directory it's been installed in) plus some additional statements
1.322 leot 6648: - see the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> man page for a full list.
1.299 rillig 6649: This chapter addresses some issues that need attention when
6650: dealing with the <code class="filename">PLIST</code> file (or files, see
6651: below!).</p>
1.148 asau 6652: <div class="sect1">
1.75 rillig 6653: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6654: <a name="rcs-id"></a>19.1. RCS ID</h2></div></div></div>
6655: <p>Be sure to add a RCS ID line as the first thing in any
6656: <code class="filename">PLIST</code> file you write:</p>
6657: <pre class="programlisting">
6658: @comment $NetBSD $
6659: </pre>
6660: <p>An artificial space has been added between NetBSD and $, this is a
6661: workaround here to prevent CVS expanding to the filename of the guide. When
6662: adding the RCS ID the space should be omitted.</p>
1.75 rillig 6663: </div>
1.148 asau 6664: <div class="sect1">
1.75 rillig 6665: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6666: <a name="automatic-plist-generation"></a>19.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div>
6667: <p>You can use the <span class="command"><strong>make print-PLIST</strong></span> command
6668: to output a PLIST that matches any new files since the package
6669: was extracted. See <a class="xref" href="#build.helpful-targets" title="13.17. Other helpful targets">Section 13.17, “Other helpful targets”</a> for
6670: more information on this target.</p>
1.75 rillig 6671: </div>
1.148 asau 6672: <div class="sect1">
1.75 rillig 6673: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6674: <a name="print-PLIST"></a>19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>
6675: </h2></div></div></div>
6676: <p>The <code class="varname">PRINT_PLIST_AWK</code> variable takes a set
6677: of AWK patterns and actions that are used to filter the output of
6678: print-PLIST. You can <span class="emphasis"><em>append</em></span> any chunk of AWK
6679: scripting you like to it, but be careful with quoting.</p>
6680: <p>For example, to get all files inside the
6681: <code class="filename">libdata/foo</code> directory removed from the
6682: resulting PLIST:</p>
1.88 wiz 6683: <pre class="programlisting">
1.299 rillig 6684: PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
1.100 rillig 6685: </pre>
1.300 wiz 6686: <p>The <code class="varname">PRINT_PLIST_AWK</code> transformations are
6687: evaluated after the file list and directory list are sorted.
6688: <code class="varname">EARLY_PRINT_PLIST_AWK</code> is like
6689: <code class="varname">PRINT_PLIST_AWK</code> except it operates before the file
6690: list and directory list are sorted.</p>
1.299 rillig 6691: </div>
6692: <div class="sect1">
6693: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6694: <a name="plist.misc"></a>19.4. Variable substitution in PLIST</h2></div></div></div>
6695: <p>A number of variables are substituted automatically in
6696: PLISTs when a package is installed on a system. This includes the
6697: following variables:</p>
6698: <div class="variablelist"><dl class="variablelist">
6699: <dt><span class="term"><code class="varname">${MACHINE_ARCH}</code>, <code class="varname">${MACHINE_GNU_ARCH}</code></span></dt>
6700: <dd>
6701: <p>Some packages like emacs and perl embed information
6702: about which architecture they were built on into the
6703: pathnames where they install their files. To handle this
6704: case, PLIST will be preprocessed before actually used, and
6705: the symbol
6706: <span class="quote">“<span class="quote"><code class="varname">${MACHINE_ARCH}</code></span>”</span> will be
6707: replaced by what <span class="command"><strong>uname -p</strong></span> gives. The
6708: same is done if the string
6709: <code class="varname">${MACHINE_GNU_ARCH}</code> is embedded in
6710: PLIST somewhere - use this on packages that have GNU
6711: autoconf-created configure scripts.</p>
6712: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
6713: <h3 class="title">Legacy note</h3>
6714: <p>There used to be a symbol
6715: <span class="quote">“<span class="quote"><code class="varname">$ARCH</code></span>”</span> that
6716: was replaced by the output of <span class="command"><strong>uname
6717: -m</strong></span>, but that's no longer supported and has
6718: been removed.</p>
6719: </div>
6720: </dd>
6721: <dt><span class="term"><code class="varname">${OPSYS}</code>, <code class="varname">${LOWER_OPSYS}</code>, <code class="varname">${OS_VERSION}</code></span></dt>
6722: <dd>
6723: <p>Some packages want to embed the OS name and version
6724: into some paths. To do this, use these variables in the
6725: <code class="filename">PLIST</code>:
6726: </p>
6727: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6728: <li class="listitem"><p><code class="varname">${OPSYS}</code> - output of <span class="quote">“<span class="quote"><span class="command"><strong>uname -s</strong></span></span>”</span></p></li>
6729: <li class="listitem"><p><code class="varname">${LOWER_OPSYS}</code> - lowercase common name (eg. <span class="quote">“<span class="quote">solaris</span>”</span>)</p></li>
6730: <li class="listitem"><p><code class="varname">${OS_VERSION}</code> - <span class="quote">“<span class="quote"><span class="command"><strong>uname -r</strong></span></span>”</span></p></li>
6731: </ul></div>
6732: </dd>
6733: </dl></div>
6734: <p>For a list of values which are replaced by
6735: default, the output of <span class="command"><strong>make help topic=PLIST_SUBST</strong></span> as
6736: well as searching the <code class="filename">pkgsrc/mk</code> directory with <span class="command"><strong>grep</strong></span> for
6737: <code class="varname">PLIST_SUBST</code> should help.</p>
6738: <p>If you want to change other variables not listed above, you
6739: can add variables and their expansions to this variable in the
6740: following way, similar to <code class="varname">MESSAGE_SUBST</code> (see <a class="xref" href="#components.optional" title="12.5. Optional files">Section 12.5, “Optional files”</a>):</p>
1.81 rillig 6741: <pre class="programlisting">
1.299 rillig 6742: PLIST_SUBST+= SOMEVAR="somevalue"
1.100 rillig 6743: </pre>
1.299 rillig 6744: <p>This replaces all occurrences of <span class="quote">“<span class="quote">${SOMEVAR}</span>”</span>
6745: in the <code class="filename">PLIST</code> with
6746: <span class="quote">“<span class="quote">somevalue</span>”</span>.</p>
6747: <p>The <code class="varname">PLIST_VARS</code> variable can be used to simplify
6748: the common case of conditionally including some
6749: <code class="filename">PLIST</code> entries. It can be done by adding
6750: <code class="literal"><code class="varname">PLIST_VARS</code>+=foo</code> and
6751: setting the corresponding <code class="varname">PLIST.foo</code> variable
6752: to <code class="literal">yes</code> if the entry should be included.
6753: This will substitute <span class="quote">“<span class="quote"><code class="varname">${PLIST.foo}</code></span>”</span>
6754: in the <code class="filename">PLIST</code> with either
6755: <span class="quote">“<span class="quote"><code class="literal">""</code></span>”</span> or
6756: <span class="quote">“<span class="quote"><code class="literal">"@comment "</code></span>”</span>.
6757: For example, in <code class="filename">Makefile</code>:</p>
1.174 asau 6758: <pre class="programlisting">
1.299 rillig 6759: PLIST_VARS+= foo
6760: .if <em class="replaceable"><code>condition</code></em>
6761: PLIST.foo= yes
6762: .else
1.174 asau 6763: </pre>
1.299 rillig 6764: <p>And then in <code class="filename">PLIST</code>:</p>
1.81 rillig 6765: <pre class="programlisting">
1.299 rillig 6766: @comment $NetBSD $
6767: bin/bar
6768: man/man1/bar.1
6769: ${PLIST.foo}bin/foo
6770: ${PLIST.foo}man/man1/foo.1
6771: ${PLIST.foo}share/bar/foo.data
1.100 rillig 6772: </pre>
1.299 rillig 6773: <p>An artificial space has been added between NetBSD and $, this is a
6774: workaround here to prevent CVS expanding to the filename of the guide. When
1.309 gutterid 6775: adding the RCS ID the space should be omitted.</p>
1.81 rillig 6776: </div>
1.299 rillig 6777: <div class="sect1">
6778: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6779: <a name="manpage-compression"></a>19.5. Man page compression</h2></div></div></div>
6780: <p>Man pages should be installed in compressed form if
6781: <code class="varname">MANZ</code> is set (in <code class="filename">bsd.own.mk</code>),
6782: and uncompressed otherwise. To handle this in the
6783: <code class="filename">PLIST</code> file, the suffix <span class="quote">“<span class="quote">.gz</span>”</span> is
6784: appended/removed automatically for man pages according to
6785: <code class="varname">MANZ</code> and <code class="varname">MANCOMPRESSED</code> being set
6786: or not, see above for details. This modification of the
6787: <code class="filename">PLIST</code> file is done on a copy of it, not
6788: <code class="filename">PLIST</code> itself.</p>
1.75 rillig 6789: </div>
1.148 asau 6790: <div class="sect1">
1.75 rillig 6791: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6792: <a name="using-PLIST_SRC"></a>19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code>
6793: </h2></div></div></div>
6794: <p>To use one or more files as source for the <code class="filename">PLIST</code> used
6795: in generating the binary package, set the variable
6796: <code class="varname">PLIST_SRC</code> to the names of that file(s).
1.322 leot 6797: The files are later concatenated using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cat.1"><span class="citerefentry"><span class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
1.299 rillig 6798: important. The default for <code class="varname">PLIST_SRC</code> is
6799: <code class="filename">${PKGDIR}/PLIST</code>.</p>
1.75 rillig 6800: </div>
1.148 asau 6801: <div class="sect1">
1.75 rillig 6802: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6803: <a name="platform-specific-plist"></a>19.7. Platform-specific and differing PLISTs</h2></div></div></div>
6804: <p>Some packages decide to install a different set of files based on
6805: the operating system being used. These differences can be
6806: automatically handled by using the following files:</p>
6807: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6808: <li class="listitem"><p><code class="filename">PLIST.common</code></p></li>
6809: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}</code></p></li>
6810: <li class="listitem"><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li>
6811: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li>
6812: <li class="listitem"><p><code class="filename">PLIST.common_end</code></p></li>
6813: </ul></div>
1.75 rillig 6814: </div>
1.148 asau 6815: <div class="sect1">
1.75 rillig 6816: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6817: <a name="build-plist"></a>19.8. Build-specific PLISTs</h2></div></div></div>
6818: <p>Some packages decide to generate hard-to-guess file names
6819: during installation that are hard to wire down.</p>
6820: <p>In such cases, you can set the
6821: <code class="varname">GENERATE_PLIST</code> variable to shell code
6822: terminated (with a semicolon) that will output PLIST entries which
6823: will be appended to the PLIST</p>
6824: <p>You can find one example in editors/xemacs:</p>
6825: <pre class="programlisting">
6826: GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ;
6827: </pre>
6828: <p>which will append something like
6829: <code class="filename">bin/xemacs-21.4.23-54e8ea71.dmp</code> to the
6830: <code class="filename">PLIST</code>.
6831: </p>
1.75 rillig 6832: </div>
1.148 asau 6833: <div class="sect1">
1.75 rillig 6834: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6835: <a name="faq.common-dirs"></a>19.9. Sharing directories between packages</h2></div></div></div>
6836: <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where
6837: multiple (and unrelated) packages install files. These
6838: directories were problematic because you had to add special
6839: tricks in the PLIST to conditionally remove them, or have some
6840: centralized package handle them.</p>
6841: <p>In pkgsrc, it is now easy: Each package should create
6842: directories and install files as needed; <span class="command"><strong>pkg_delete</strong></span>
6843: will remove any directories left empty after uninstalling a
6844: package.</p>
6845: <p>If a package needs an empty directory to work, create
6846: the directory during installation as usual, and also add an
6847: entry to the PLIST:
6848:
6849: </p>
6850: <pre class="programlisting">
6851: @pkgdir path/to/empty/directory
6852: </pre>
6853: <p>
6854:
6855: or take a look at <code class="varname">MAKE_DIRS</code> and
6856: <code class="varname">OWN_DIRS</code>.
1.88 wiz 6857: </p>
1.75 rillig 6858: </div>
1.299 rillig 6859: </div>
6860: <div class="chapter">
6861: <div class="titlepage"><div><div><h2 class="title">
6862: <a name="pkginstall"></a>Chapter 20. The pkginstall framework</h2></div></div></div>
6863: <div class="toc">
6864: <p><b>Table of Contents</b></p>
6865: <dl class="toc">
6866: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
6867: <dd><dl>
6868: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
6869: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
6870: </dl></dd>
6871: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
6872: <dd><dl>
6873: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
6874: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
6875: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
6876: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
6877: </dl></dd>
6878: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
6879: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">20.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
6880: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
6881: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
6882: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
6883: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
6884: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">20.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
6885: </dl>
6886: </div>
6887: <p>This chapter describes the framework known as
6888: <code class="literal">pkginstall</code>, whose key features are:</p>
6889: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6890: <li class="listitem"><p>Generic installation and manipulation of directories and files
6891: outside the pkgsrc-handled tree, <code class="varname">LOCALBASE</code>.</p></li>
6892: <li class="listitem"><p>Automatic handling of configuration files during installation,
6893: provided that packages are correctly designed.</p></li>
6894: <li class="listitem"><p>Generation and installation of system startup scripts.</p></li>
6895: <li class="listitem"><p>Registration of system users and groups.</p></li>
6896: <li class="listitem"><p>Registration of system shells.</p></li>
6897: <li class="listitem"><p>Automatic updating of fonts databases.</p></li>
6898: </ul></div>
6899: <p>The following sections inspect each of the above points in detail.</p>
6900: <p>You may be thinking that many of the things described here could be
6901: easily done with simple code in the package's post-installation target
6902: (<code class="literal">post-install</code>). <span class="emphasis"><em>This is incorrect</em></span>,
6903: as the code in them is only executed when building from source. Machines
6904: using binary packages could not benefit from it at all (as the code itself
6905: could be unavailable). Therefore, the only way to achieve any of the items
6906: described above is by means of the installation scripts, which are
6907: automatically generated by pkginstall.</p>
1.148 asau 6908: <div class="sect1">
1.75 rillig 6909: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 6910: <a name="files-and-dirs-outside-prefix"></a>20.1. Files and directories outside the installation prefix</h2></div></div></div>
6911: <p>As you already know, the <code class="filename">PLIST</code> file holds a list
6912: of files and directories that belong to a package. The names used in it
6913: are relative to the installation prefix (<code class="filename">${PREFIX}</code>),
6914: which means that it cannot register files outside this directory (absolute
6915: path names are not allowed). Despite this restriction, some packages need
6916: to install files outside this location; e.g., under
6917: <code class="filename">${VARBASE}</code> or
6918: <code class="filename">${PKG_SYSCONFDIR}</code>. The only way to achieve this
6919: is to create such files during installation time by using
6920: installation scripts.</p>
6921: <p>The generic installation scripts are shell scripts that can
6922: contain arbitrary code. The list of scripts to execute is taken from
6923: the <code class="varname">INSTALL_FILE</code> variable, which defaults to
6924: <code class="filename">INSTALL</code>. A similar variable exists for package
6925: removal (<code class="varname">DEINSTALL_FILE</code>, whose default is
6926: <code class="filename">DEINSTALL</code>). These scripts can run arbitrary
6927: commands, so they have the potential to create and manage files
6928: anywhere in the file system.</p>
6929: <p>Using these general installation files is not recommended, but
6930: may be needed in some special cases. One reason for avoiding them is
6931: that the user has to trust the packager that there is no unwanted or
6932: simply erroneous code included in the installation script. Also,
6933: previously there were many similar scripts for the same functionality,
6934: and fixing a common error involved finding and changing all of
6935: them.</p>
6936: <p>The pkginstall framework offers another, standardized way. It
6937: provides generic scripts to abstract the manipulation of such files
6938: and directories based on variables set in the package's
6939: <code class="filename">Makefile</code>. The rest of this section describes
6940: these variables.</p>
6941: <div class="sect2">
6942: <div class="titlepage"><div><div><h3 class="title">
6943: <a name="dirs-outside-prefix"></a>20.1.1. Directory manipulation</h3></div></div></div>
6944: <p>The following variables can be set to request the creation of
6945: directories anywhere in the file system:</p>
6946: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6947: <li class="listitem">
6948: <p><code class="varname">MAKE_DIRS</code> and <code class="varname">OWN_DIRS</code>
6949: contain a list of directories that should be created and should attempt
6950: to be destroyed by the installation scripts. The difference between
6951: the two is that the latter prompts the administrator to remove any
6952: directories that may be left after deinstallation (because they were
6953: not empty), while the former does not. Example:</p>
6954: <pre class="programlisting">
6955: MAKE_DIRS+= ${VARBASE}/foo/private
6956: </pre>
6957: </li>
6958: <li class="listitem">
6959: <p><code class="varname">MAKE_DIRS_PERMS</code> and
6960: <code class="varname">OWN_DIRS_PERMS</code> contain a list of tuples describing
6961: which directories should be created and should attempt to be destroyed
6962: by the installation scripts. Each tuple holds the following values,
6963: separated by spaces: the directory name, its owner, its group and its
6964: numerical mode. For example:</p>
6965: <pre class="programlisting">
6966: MAKE_DIRS_PERMS+= ${VARBASE}/foo/private \
6967: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
6968: </pre>
6969: <p>The difference between the two is exactly the same as their
6970: non-<code class="varname">PERMS</code> counterparts.</p>
6971: </li>
6972: </ul></div>
1.75 rillig 6973: </div>
1.299 rillig 6974: <div class="sect2">
6975: <div class="titlepage"><div><div><h3 class="title">
6976: <a name="files-outside-prefix"></a>20.1.2. File manipulation</h3></div></div></div>
6977: <p>Creating non-empty files outside the installation prefix is tricky
6978: because the <code class="filename">PLIST</code> forces all files to be inside it.
6979: To overcome this problem, the only solution is to extract the file in the
6980: known place (i.e., inside the installation prefix) and copy it to the
6981: appropriate location during installation (done by the installation scripts
6982: generated by pkginstall). We will call the former the <span class="emphasis"><em>master
6983: file</em></span> in the following paragraphs, which describe the variables
6984: that can be used to automatically and consistently handle files outside the
6985: installation prefix:</p>
6986: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6987: <li class="listitem">
6988: <p><code class="varname">CONF_FILES</code> and
6989: <code class="varname">REQD_FILES</code> are pairs of master and target files.
6990: During installation time, the master file is copied to the target one
6991: if and only if the latter does not exist. Upon deinstallation, the
6992: target file is removed provided that it was not modified by the
6993: installation.</p>
6994: <p>The difference between the two is that the latter prompts the
6995: administrator to remove any files that may be left after
6996: deinstallation (because they were not empty), while the former does
6997: not.</p>
6998: </li>
6999: <li class="listitem">
7000: <p><code class="varname">CONF_FILES_PERMS</code> and
7001: <code class="varname">REQD_FILES_PERMS</code> contain tuples describing master
7002: files as well as their target locations. For each of them, it also
7003: specifies their owner, their group and their numeric permissions, in
7004: this order. For example:</p>
1.88 wiz 7005: <pre class="programlisting">
1.299 rillig 7006: REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile \
7007: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
1.100 rillig 7008: </pre>
1.299 rillig 7009: <p>The difference between the two is exactly the same as their
7010: non-<code class="varname">PERMS</code> counterparts.</p>
7011: </li>
7012: </ul></div>
7013: </div>
1.75 rillig 7014: </div>
1.148 asau 7015: <div class="sect1">
1.75 rillig 7016: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 7017: <a name="conf-files"></a>20.2. Configuration files</h2></div></div></div>
7018: <p>Configuration files are special in the sense that they are installed
7019: in their own specific directory, <code class="varname">PKG_SYSCONFDIR</code>, and
7020: need special treatment during installation (most of which is automated by
7021: pkginstall). The main concept you must bear in mind is that files marked
7022: as configuration files are automatically copied to the right place (somewhere
7023: inside <code class="varname">PKG_SYSCONFDIR</code>) during installation <span class="emphasis"><em>if
7024: and only if</em></span> they didn't exist before. Similarly, they will not
7025: be removed if they have local modifications. This ensures that
7026: administrators never lose any custom changes they may have made.</p>
7027: <div class="sect2">
7028: <div class="titlepage"><div><div><h3 class="title">
7029: <a name="conf-files-sysconfdir"></a>20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</h3></div></div></div>
7030: <p>As said before, the <code class="varname">PKG_SYSCONFDIR</code> variable
7031: specifies where configuration files shall be installed. Its contents are
7032: set based upon the following variables:</p>
7033: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7034: <li class="listitem"><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root
7035: directory. Defaults to <code class="filename">${PREFIX}/etc</code> although it may
7036: be overridden by the user to point to his preferred location (e.g.,
7037: <code class="filename">/etc</code>, <code class="filename">/etc/pkg</code>, etc.).
7038: Packages must not use it directly.</p></li>
7039: <li class="listitem">
7040: <p><code class="varname">PKG_SYSCONFSUBDIR</code>: A subdirectory of
7041: <code class="varname">PKG_SYSCONFBASE</code> under which the configuration files
7042: for the package being built shall be installed. The definition of this
7043: variable only makes sense in the package's
7044: <code class="filename">Makefile</code> (i.e., it is not user-customizable).</p>
7045: <p>As an example, consider the Apache package,
1.322 leot 7046: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/index.html" target="_top"><code class="filename">www/apache24</code></a>, which places its
1.299 rillig 7047: configuration files under the
7048: <code class="filename">httpd/</code> subdirectory of
7049: <code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package
7050: Makefile.</p>
7051: </li>
7052: <li class="listitem"><p><code class="varname">PKG_SYSCONFVAR</code>: Specifies the name of the
7053: variable that holds this package's configuration directory (if
7054: different from <code class="varname">PKG_SYSCONFBASE</code>). It defaults to
7055: <code class="varname">PKGBASE</code>'s value, and is always prefixed with
7056: <code class="literal">PKG_SYSCONFDIR</code>.</p></li>
7057: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>: Holds the
7058: directory where the configuration files for the package identified by
7059: <code class="varname">PKG_SYSCONFVAR</code>'s shall be placed.</p></li>
7060: </ul></div>
7061: <p>Based on the above variables, pkginstall determines the value of
7062: <code class="varname">PKG_SYSCONFDIR</code>, which is the <span class="emphasis"><em>only</em></span>
7063: variable that can be used within a package to refer to its configuration
7064: directory. The algorithm used to set its value is basically the
7065: following:</p>
7066: <div class="orderedlist"><ol class="orderedlist" type="1">
7067: <li class="listitem"><p>If <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> is set,
7068: its value is used.</p></li>
7069: <li class="listitem"><p>If the previous variable is not defined but
7070: <code class="varname">PKG_SYSCONFSUBDIR</code> is set in the package's
7071: <code class="filename">Makefile</code>, the resulting value is
7072: <code class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li>
7073: <li class="listitem"><p>Otherwise, it is set to
7074: <code class="filename">${PKG_SYSCONFBASE}</code>.</p></li>
7075: </ol></div>
7076: <p>It is worth mentioning that <code class="filename">${PKG_SYSCONFDIR}</code> is
7077: automatically added to <code class="filename">OWN_DIRS</code>. See <a class="xref" href="#dirs-outside-prefix" title="20.1.1. Directory manipulation">Section 20.1.1, “Directory manipulation”</a> what this means. This does not apply to
7078: subdirectories of <code class="filename">${PKG_SYSCONFDIR}</code>, they still have to
7079: be created with OWN_DIRS or MAKE_DIRS.</p>
7080: </div>
7081: <div class="sect2">
7082: <div class="titlepage"><div><div><h3 class="title">
7083: <a name="conf-files-configure"></a>20.2.2. Telling the software where configuration files are</h3></div></div></div>
7084: <p>Given that pkgsrc (and users!) expect configuration files to be in a
7085: known place, you need to teach each package where it shall install its
7086: files. In some cases you will have to patch the package Makefiles to
7087: achieve it. If you are lucky, though, it may be as easy as passing an
7088: extra flag to the configuration script; this is the case of GNU Autoconf-
7089: generated files:</p>
1.75 rillig 7090: <pre class="programlisting">
1.299 rillig 7091: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
1.100 rillig 7092: </pre>
1.299 rillig 7093: <p>Note that this specifies where the package has to <span class="emphasis"><em>look
7094: for</em></span> its configuration files, not where they will be originally
7095: installed (although the difference is never explicit,
7096: unfortunately).</p>
1.75 rillig 7097: </div>
1.299 rillig 7098: <div class="sect2">
7099: <div class="titlepage"><div><div><h3 class="title">
7100: <a name="conf-files-patching"></a>20.2.3. Patching installations</h3></div></div></div>
7101: <p>As said before, pkginstall automatically handles configuration files.
7102: This means that <span class="strong"><strong>the packages themselves must not
7103: touch the contents of <code class="filename">${PKG_SYSCONFDIR}</code>
7104: directly</strong></span>. Bad news is that many software installation scripts
7105: will, out of the box, mess with the contents of that directory. So what is
7106: the correct procedure to fix this issue?</p>
7107: <p>You must teach the package (usually by manually patching it) to
7108: install any configuration files under the examples hierarchy,
7109: <code class="filename">share/examples/${PKGBASE}/</code>. This way, the
7110: <code class="filename">PLIST</code> registers them and the administrator always
7111: has the original copies available.</p>
7112: <p>Once the required configuration files are in place (i.e., under the
7113: examples hierarchy), the pkginstall framework can use them as master copies
7114: during the package installation to update what is in
7115: <code class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables
7116: <code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are
7117: used. Check out <a class="xref" href="#files-outside-prefix" title="20.1.2. File manipulation">Section 20.1.2, “File manipulation”</a> for information
7118: about their syntax and their purpose. Here is an example, taken from the
1.322 leot 7119: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/index.html" target="_top"><code class="filename">mail/mutt</code></a> package:</p>
1.88 wiz 7120: <pre class="programlisting">
1.299 rillig 7121: EGDIR= ${PREFIX}/share/doc/mutt/samples
7122: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
1.100 rillig 7123: </pre>
1.299 rillig 7124: <p>Note that the <code class="varname">EGDIR</code> variable is specific to that
7125: package and has no meaning outside it.</p>
1.75 rillig 7126: </div>
1.299 rillig 7127: <div class="sect2">
7128: <div class="titlepage"><div><div><h3 class="title">
7129: <a name="conf-files-disable"></a>20.2.4. Disabling handling of configuration files</h3></div></div></div>
7130: <p>The automatic copying of config files can be toggled by setting the
7131: environment variable <code class="varname">PKG_CONFIG</code> prior to package
7132: installation.</p>
1.88 wiz 7133: </div>
1.75 rillig 7134: </div>
1.148 asau 7135: <div class="sect1">
1.75 rillig 7136: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 7137: <a name="rcd-scripts"></a>20.3. System startup scripts</h2></div></div></div>
7138: <p>System startup scripts are special files because they must be
7139: installed in a place known by the underlying OS, usually outside the
7140: installation prefix. Therefore, the same rules described in <a class="xref" href="#files-and-dirs-outside-prefix" title="20.1. Files and directories outside the installation prefix">Section 20.1, “Files and directories outside the installation prefix”</a> apply, and the same solutions
7141: can be used. However, pkginstall provides a special mechanism to handle
7142: these files.</p>
7143: <p>In order to provide system startup scripts, the package has
7144: to:</p>
7145: <div class="orderedlist"><ol class="orderedlist" type="1">
7146: <li class="listitem"><p>Store the script inside <code class="filename">${FILESDIR}</code>, with
7147: the <code class="literal">.sh</code> suffix appended. Considering the
1.338 nia 7148: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/cups-base/index.html" target="_top"><code class="filename">print/cups-base</code></a> package as an example, it
7149: has a <code class="filename">cupsd.sh</code> in its files directory.</p></li>
1.299 rillig 7150: <li class="listitem">
7151: <p>Tell pkginstall to handle it, appending the name of the script,
7152: without its extension, to the <code class="varname">RCD_SCRIPTS</code> variable.
7153: Continuing the previous example:</p>
7154: <pre class="programlisting">
7155: RCD_SCRIPTS+= cupsd
7156: </pre>
7157: </li>
7158: </ol></div>
7159: <p>Once this is done, pkginstall will do the following steps for each
7160: script in an automated fashion:</p>
7161: <div class="orderedlist"><ol class="orderedlist" type="1">
7162: <li class="listitem"><p>Process the file found in the files directory applying all the
7163: substitutions described in the <code class="filename">FILES_SUBST</code>
7164: variable.</p></li>
7165: <li class="listitem"><p>Copy the script from the files directory to the examples
7166: hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>. Note
7167: that this master file must be explicitly registered in the
7168: <code class="filename">PLIST</code>.</p></li>
7169: <li class="listitem"><p>Add code to the installation scripts to copy the startup script
7170: from the examples hierarchy into the system-wide startup scripts
7171: directory.</p></li>
7172: </ol></div>
7173: <div class="sect2">
7174: <div class="titlepage"><div><div><h3 class="title">
7175: <a name="rcd-scripts-disable"></a>20.3.1. Disabling handling of system startup scripts</h3></div></div></div>
7176: <p>The automatic copying of config files can be toggled by setting the
7177: environment variable <code class="varname">PKG_RCD_SCRIPTS</code> prior to package
7178: installation. Note that the scripts will be always copied inside the
7179: examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>, no
7180: matter what the value of this variable is.</p>
1.75 rillig 7181: </div>
7182: </div>
1.299 rillig 7183: <div class="sect1">
7184: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
7185: <a name="users-and-groups"></a>20.4. System users and groups</h2></div></div></div>
7186: <p>If a package needs to create special users and/or groups during
7187: installation, it can do so by using the pkginstall framework.</p>
7188: <p>Users can be created by adding entries to the
7189: <code class="varname">PKG_USERS</code> variable. Each entry has the following
7190: syntax:</p>
7191: <pre class="programlisting">
7192: user:group
7193: </pre>
7194: <p>Further specification of user details may be done by setting
7195: per-user variables.
7196: <code class="varname">PKG_UID.<em class="replaceable"><code>user</code></em></code> is the
7197: numeric UID for the user.
7198: <code class="varname">PKG_GECOS.<em class="replaceable"><code>user</code></em></code> is the
7199: user's description or comment.
7200: <code class="varname">PKG_HOME.<em class="replaceable"><code>user</code></em></code> is the
7201: user's home directory, and defaults to
7202: <code class="filename">/nonexistent</code> if not specified.
7203: <code class="varname">PKG_SHELL.<em class="replaceable"><code>user</code></em></code> is the
7204: user's shell, and defaults to <code class="filename">/sbin/nologin</code> if
7205: not specified.</p>
7206: <p>Similarly, groups can be created by adding entries to the
7207: <code class="varname">PKG_GROUPS</code> variable, whose syntax is:</p>
7208: <pre class="programlisting">
7209: group
7210: </pre>
7211: <p>The numeric GID of the group may be set by defining
7212: <code class="varname">PKG_GID.<em class="replaceable"><code>group</code></em></code>.</p>
7213: <p>If a package needs to create the users and groups at an earlier
7214: stage, then it can set <code class="varname">USERGROUP_PHASE</code> to either
7215: <code class="literal">configure</code>,<code class="literal">build</code>, or
7216: <code class="literal">pre-install</code> to indicate the phase before which the
7217: users and groups are created. In this case, the numeric UIDs and GIDs
7218: of the created users and groups are automatically hardcoded into the
7219: final installation scripts.</p>
1.75 rillig 7220: </div>
1.148 asau 7221: <div class="sect1">
1.75 rillig 7222: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 7223: <a name="shells"></a>20.5. System shells</h2></div></div></div>
7224: <p>Packages that install system shells should register them in the shell
7225: database, <code class="filename">/etc/shells</code>, to make things easier to the
7226: administrator. This must be done from the installation scripts to keep
7227: binary packages working on any system. pkginstall provides an easy way to
7228: accomplish this task.</p>
7229: <p>When a package provides a shell interpreter, it has to set the
7230: <code class="varname">PKG_SHELL</code> variable to its absolute file name. This will
7231: add some hooks to the installation scripts to handle it. Consider the
1.322 leot 7232: following example, taken from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/zsh/index.html" target="_top"><code class="filename">shells/zsh</code></a>:</p>
1.299 rillig 7233: <pre class="programlisting">
7234: PKG_SHELL= ${PREFIX}/bin/zsh
7235: </pre>
7236: <div class="sect2">
7237: <div class="titlepage"><div><div><h3 class="title">
7238: <a name="shells-disable"></a>20.5.1. Disabling shell registration</h3></div></div></div>
7239: <p>The automatic registration of shell interpreters can be disabled by
7240: the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</code>
7241: environment variable to <code class="literal">NO</code>.</p>
7242: </div>
1.75 rillig 7243: </div>
1.148 asau 7244: <div class="sect1">
1.75 rillig 7245: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 7246: <a name="fonts"></a>20.6. Fonts</h2></div></div></div>
7247: <p>Packages that install X11 fonts should update the database files
7248: that index the fonts within each fonts directory. This can easily be
7249: accomplished within the pkginstall framework.</p>
7250: <p>When a package installs X11 fonts, it must list the directories in
7251: which fonts are installed in the
7252: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code> variables,
7253: where <em class="replaceable"><code>type</code></em> can be one of <span class="quote">“<span class="quote">ttf</span>”</span>,
7254: <span class="quote">“<span class="quote">type1</span>”</span> or <span class="quote">“<span class="quote">x11</span>”</span>. This will add hooks to the
7255: installation scripts to run the appropriate commands to update the fonts
7256: database files within each of those directories. For convenience, if the
7257: directory path is relative, it is taken to be relative to the package's
1.322 leot 7258: installation prefix. Consider the following example, taken from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/fonts/dbz-ttf/index.html" target="_top"><code class="filename">fonts/dbz-ttf</code></a>:</p>
1.75 rillig 7259: <pre class="programlisting">
1.299 rillig 7260: FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
1.75 rillig 7261: </pre>
1.299 rillig 7262: <div class="sect2">
7263: <div class="titlepage"><div><div><h3 class="title">
7264: <a name="fonts-disable"></a>20.6.1. Disabling automatic update of the fonts databases</h3></div></div></div>
7265: <p>The automatic update of fonts databases can be disabled by
7266: the administrator by setting the <code class="filename">PKG_UPDATE_FONTS_DB</code>
7267: environment variable to <code class="literal">NO</code>.</p>
1.75 rillig 7268: </div>
7269: </div>
7270: </div>
1.148 asau 7271: <div class="chapter">
1.75 rillig 7272: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 7273: <a name="fixes"></a>Chapter 21. Making your package work</h2></div></div></div>
1.75 rillig 7274: <div class="toc">
7275: <p><b>Table of Contents</b></p>
1.210 leot 7276: <dl class="toc">
1.267 rillig 7277: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
1.75 rillig 7278: <dd><dl>
1.267 rillig 7279: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">21.1.1. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
7280: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
7281: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
7282: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
7283: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
7284: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
7285: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
7286: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
7287: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
7288: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
7289: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
7290: </dl></dd>
7291: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
7292: <dd><dl>
7293: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
7294: <dt><span class="sect2"><a href="#modified-distfiles-same-name">21.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
7295: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
7296: </dl></dd>
7297: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
7298: <dd><dl>
7299: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
7300: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
7301: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.338 nia 7302: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.267 rillig 7303: </dl></dd>
7304: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
7305: <dd><dl>
7306: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
7307: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.320 wiz 7308: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.338 nia 7309: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
7310: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
7311: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
7312: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.267 rillig 7313: </dl></dd>
7314: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
7315: <dd><dl>
7316: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
7317: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.287 rillig 7318: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
7319: <dt><span class="sect2"><a href="#undefined-reference">21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
7320: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.267 rillig 7321: </dl></dd>
7322: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
7323: <dd><dl>
7324: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
7325: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
7326: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
7327: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
7328: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.318 nia 7329: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.267 rillig 7330: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
7331: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.318 nia 7332: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
7333: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
7334: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
7335: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
7336: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
7337: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
7338: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.87 wiz 7339: emulation</a></span></dt>
1.318 nia 7340: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
7341: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.75 rillig 7342: </dl></dd>
1.267 rillig 7343: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.75 rillig 7344: </dl>
7345: </div>
1.148 asau 7346: <div class="sect1">
1.75 rillig 7347: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 7348: <a name="general-operation"></a>21.1. General operation</h2></div></div></div>
1.78 rillig 7349: <p>One appealing feature of pkgsrc is that it runs on many
1.218 rillig 7350: different platforms. As a result, it is important to ensure,
7351: where possible, that packages in pkgsrc are portable. This
7352: chapter mentions some particular details you should pay
7353: attention to while working on pkgsrc.</p>
1.148 asau 7354: <div class="sect2">
1.78 rillig 7355: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7356: <a name="pulling-vars-from-etc-mk.conf"></a>21.1.1. How to pull in user-settable variables from <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
1.93 rillig 7357: </h3></div></div></div>
1.78 rillig 7358: <p>The pkgsrc user can configure pkgsrc by overriding several
1.87 wiz 7359: variables in the file pointed to by <code class="varname">MAKECONF</code>,
1.110 hubertf 7360: which is <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> by default. When you
1.87 wiz 7361: want to use those variables in the preprocessor directives of
1.322 leot 7362: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> (for example <code class="literal">.if</code> or
1.87 wiz 7363: <code class="literal">.for</code>), you need to include the file
7364: <code class="filename">../../mk/bsd.prefs.mk</code> before, which in turn
7365: loads the user preferences.</p>
1.78 rillig 7366: <p>But note that some variables may not be completely defined
1.219 rillig 7367: after <code class="filename">../../mk/bsd.prefs.mk</code> has been
7368: included, as they may contain references to variables that are
7369: not yet defined. In shell commands (the lines in
7370: <code class="filename">Makefile</code> that are indented with a tab) this
7371: is no problem, since variables are only expanded when they are
7372: used. But in the preprocessor directives mentioned above and in
7373: dependency lines (of the form <code class="literal">target:
7374: dependencies</code>) the variables are expanded at load
7375: time.</p>
1.148 asau 7376: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.78 rillig 7377: <h3 class="title">Note</h3>
1.218 rillig 7378: <p>To check whether a variable can be used at load time,
7379: run <span class="command"><strong>pkglint -Wall</strong></span> on your package.</p>
1.78 rillig 7380: </div>
7381: </div>
1.148 asau 7382: <div class="sect2">
1.78 rillig 7383: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7384: <a name="user-interaction"></a>21.1.2. User interaction</h3></div></div></div>
1.88 wiz 7385: <p>Occasionally, packages require interaction from the user,
7386: and this can be in a number of ways:</p>
1.148 asau 7387: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 7388: <li class="listitem"><p>When fetching the distfiles, some packages require user
1.87 wiz 7389: interaction such as entering username/password or accepting a
7390: license on a web page.</p></li>
1.128 wiz 7391: <li class="listitem"><p>When extracting the distfiles, some packages may ask for
1.88 wiz 7392: passwords.</p></li>
1.128 wiz 7393: <li class="listitem"><p>help to configure the package before it is built</p></li>
7394: <li class="listitem"><p>help during the build process</p></li>
7395: <li class="listitem"><p>help during the installation of a package</p></li>
1.78 rillig 7396: </ul></div>
1.218 rillig 7397: <p>A package can set the <code class="varname">INTERACTIVE_STAGE</code>
7398: variable to define which stages need interaction. This should be
7399: done in the package's <code class="filename">Makefile</code>, e.g.:</p>
1.75 rillig 7400: <pre class="programlisting">
1.100 rillig 7401: INTERACTIVE_STAGE= configure install
1.222 sevan 7402: </pre>
1.88 wiz 7403: <p>The user can then decide to skip this package by setting the
1.218 rillig 7404: <code class="varname">BATCH</code> variable. Packages that require interaction
7405: are also excluded from bulk builds.</p>
1.75 rillig 7406: </div>
1.148 asau 7407: <div class="sect2">
1.75 rillig 7408: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7409: <a name="handling-licenses"></a>21.1.3. Handling licenses</h3></div></div></div>
1.222 sevan 7410: <p>Authors of software can choose the licence under which software
7411: can be copied. The Free Software Foundation has declared some
7412: licenses "Free", and the Open Source Initiative has a definition of
7413: "Open Source".</p>
7414: <p>By default, pkgsrc allows packages with Free or Open Source
7415: licenses to be built. To allow packages with other licenses to be
7416: built as well, the pkgsrc user needs to add these licenses to the
7417: <code class="varname">ACCEPTABLE_LICENSES</code> variable in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. Note
7418: that this variable only affects which packages may be
7419: <span class="emphasis"><em>built</em></span>, while the license terms often also
7420: restrict the actual use of the package and its redistribution.</p>
1.98 wiz 7421: <p>One might want to only install packages with a BSD license,
1.218 rillig 7422: or the GPL, and not the other. The free licenses are added to the
1.222 sevan 7423: default <code class="varname">ACCEPTABLE_LICENSES</code> variable. The pkgsrc
1.121 jnemeth 7424: user can override the default by setting the
7425: <code class="varname">ACCEPTABLE_LICENSES</code> variable with "=" instead
1.222 sevan 7426: of "+=". The licenses accepted by default are defined in the
7427: <code class="varname">DEFAULT_ACCEPTABLE_LICENSES</code> variable in the file
7428: <code class="filename">pkgsrc/mk/license.mk</code>.</p>
1.78 rillig 7429: <p>The license tag mechanism is intended to address
1.87 wiz 7430: copyright-related issues surrounding building, installing and
7431: using a package, and not to address redistribution issues (see
7432: <code class="varname">RESTRICTED</code> and
1.222 sevan 7433: <code class="varname">NO_SRC_ON_FTP</code>, etc.).
1.121 jnemeth 7434: Packages with redistribution restrictions should set these
7435: tags.</p>
1.98 wiz 7436: <p>Denoting that a package may be copied according to a
7437: particular license is done by placing the license in
1.87 wiz 7438: <code class="filename">pkgsrc/licenses</code> and setting the
7439: <code class="varname">LICENSE</code> variable to a string identifying the
1.322 leot 7440: license, e.g. in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/xv/index.html" target="_top"><code class="filename">graphics/xv</code></a>:</p>
1.87 wiz 7441: <pre class="programlisting">
1.100 rillig 7442: LICENSE= xv-license
1.222 sevan 7443: </pre>
1.87 wiz 7444: <p>When trying to build, the user will get a notice that the
1.98 wiz 7445: package is covered by a license which has not been placed in the
7446: <code class="varname">ACCEPTABLE_LICENSES</code> variable:</p>
1.87 wiz 7447: <pre class="programlisting">
1.100 rillig 7448: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
7449: ===> xv-3.10anb9 has an unacceptable license: xv-license.
7450: ===> To view the license, enter "/usr/bin/make show-license".
7451: ===> To indicate acceptance, add this line to your /etc/mk.conf:
7452: ===> ACCEPTABLE_LICENSES+=xv-license
7453: *** Error code 1
1.222 sevan 7454: </pre>
1.110 hubertf 7455: <p>The license can be viewed with <span class="command"><strong>make
1.98 wiz 7456: show-license</strong></span>, and if the user so chooses, the line
1.110 hubertf 7457: printed above can be added to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.98 wiz 7458: convey to pkgsrc that it should not in the future fail because of
7459: that license:</p>
1.78 rillig 7460: <pre class="programlisting">
1.100 rillig 7461: ACCEPTABLE_LICENSES+=xv-license
1.222 sevan 7462: </pre>
7463: <p>The use of <code class="varname">LICENSE=shareware</code>,
7464: <code class="varname">LICENSE=no-commercial-use</code>, and similar language
7465: is deprecated because it does not crisply refer to a particular
7466: license text. Another problem with such usage is that it does not
7467: enable a user to tell pkgsrc to proceed for a single package
7468: without also telling pkgsrc to proceed for all packages with that
7469: tag.</p>
7470: <div class="sect3">
7471: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 7472: <a name="new-license"></a>21.1.3.1. Adding a package with a new license</h4></div></div></div>
1.154 rodent 7473: <p>When adding a package with a new license, the following steps
7474: are required:</p>
7475: <div class="orderedlist"><ol class="orderedlist" type="1">
7476: <li class="listitem">
1.284 rillig 7477: <p>Check whether the license qualifies as Free or Open Source by
7478: referencing <a class="ulink" href="https://www.gnu.org/licenses/license-list.en.html" target="_top">Various
7479: Licenses and Comments about Them</a> and <a class="ulink" href="https://opensource.org/licenses/alphabetical" target="_top">Licenses by Name |
1.222 sevan 7480: Open Source Initiative</a>. If this is the case, the filename in
7481: <code class="filename">pkgsrc/licenses/</code> does not need the
7482: <code class="filename">-license</code> suffix, and the license name should be
7483: added to:</p>
1.154 rodent 7484: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.284 rillig 7485: <li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in
7486: <code class="filename">pkgsrc/mk/license.mk</code></p></li>
7487: <li class="listitem"><p>default_acceptable_licenses in
7488: <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
1.154 rodent 7489: </ul></div>
7490: </li>
1.284 rillig 7491: <li class="listitem"><p>The license text should be added to
7492: <code class="filename">pkgsrc/licenses</code> for displaying. A list of known
7493: licenses can be seen in this directory.</p></li>
1.154 rodent 7494: </ol></div>
1.222 sevan 7495: </div>
7496: <div class="sect3">
7497: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 7498: <a name="change-license"></a>21.1.3.2. Change to the license</h4></div></div></div>
1.98 wiz 7499: <p>When the license changes (in a way other than formatting),
1.222 sevan 7500: make sure that the new license has a different name (e.g.,
1.98 wiz 7501: append the version number if it exists, or the date). Just
7502: because a user told pkgsrc to build programs under a previous
7503: version of a license does not mean that pkgsrc should build
1.99 rillig 7504: programs under the new licenses. The higher-level point is that
1.98 wiz 7505: pkgsrc does not evaluate licenses for reasonableness; the only
7506: test is a mechanistic test of whether a particular text has been
1.222 sevan 7507: approved by either of two bodies (FSF or OSI).</p>
7508: </div>
1.75 rillig 7509: </div>
1.148 asau 7510: <div class="sect2">
1.75 rillig 7511: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7512: <a name="restricted-packages"></a>21.1.4. Restricted packages</h3></div></div></div>
1.75 rillig 7513: <p>Some licenses restrict how software may be re-distributed.
1.222 sevan 7514: By declaring the restrictions, package tools can
1.98 wiz 7515: automatically refrain from e.g. placing binary packages on FTP
7516: sites.</p>
1.222 sevan 7517: <p>There are four possible restrictions, which are
1.98 wiz 7518: the cross product of sources (distfiles) and binaries not being
7519: placed on FTP sites and CD-ROMs. Because this is rarely the exact
7520: language in any license, and because non-Free licenses tend to be
7521: different from each other, pkgsrc adopts a definition of FTP and
1.222 sevan 7522: CD-ROM.
7523:
7524: "FTP" means making the source or binary file available over the
7525: Internet at no charge.
7526:
7527: "CD-ROM" means making the source or binary available on some kind of
7528: media, together with other source and binary packages, which is sold
7529: for a distribution charge.
1.98 wiz 7530: </p>
7531: <p>In order to encode these restrictions, the package system
1.87 wiz 7532: defines five make variables that can be set to note these
7533: restrictions:</p>
1.148 asau 7534: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 7535: <li class="listitem">
1.75 rillig 7536: <p><code class="varname">RESTRICTED</code></p>
7537: <p>This variable should be set whenever a restriction
1.87 wiz 7538: exists (regardless of its kind). Set this variable to a
1.98 wiz 7539: string containing the reason for the restriction. It should
7540: be understood that those wanting to understand the restriction
7541: will have to read the license, and perhaps seek advice of
7542: counsel.</p>
1.75 rillig 7543: </li>
1.128 wiz 7544: <li class="listitem">
1.75 rillig 7545: <p><code class="varname">NO_BIN_ON_CDROM</code></p>
1.98 wiz 7546: <p>Binaries may not be placed on CD-ROM containing other
7547: binary packages, for which a distribution charge may be made.
7548: In this case, set this variable to
7549: <code class="varname">${RESTRICTED}</code>.</p>
1.75 rillig 7550: </li>
1.128 wiz 7551: <li class="listitem">
1.75 rillig 7552: <p><code class="varname">NO_BIN_ON_FTP</code></p>
1.98 wiz 7553: <p>Binaries may not made available on the Internet without
7554: charge. In this case, set this variable to
7555: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7556: binary packages will not be included on ftp.NetBSD.org.</p>
1.75 rillig 7557: </li>
1.128 wiz 7558: <li class="listitem">
1.75 rillig 7559: <p><code class="varname">NO_SRC_ON_CDROM</code></p>
1.98 wiz 7560: <p>Distfiles may not be placed on CD-ROM, together with
7561: other distfiles, for which a fee may be charged. In this
7562: case, set this variable to <code class="varname">${RESTRICTED}</code>.
7563: </p>
1.75 rillig 7564: </li>
1.128 wiz 7565: <li class="listitem">
1.75 rillig 7566: <p><code class="varname">NO_SRC_ON_FTP</code></p>
1.98 wiz 7567: <p>Distfiles may not made available via FTP at no charge.
7568: In this case, set this variable to
7569: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7570: the distfile(s) will not be mirrored on ftp.NetBSD.org.</p>
1.75 rillig 7571: </li>
7572: </ul></div>
1.222 sevan 7573: <p>Please note that packages will be removed from pkgsrc when the
7574: distfiles are not distributable and cannot be obtained for a period
7575: of one full quarter branch. Packages with manual/interactive fetch
7576: must have a maintainer and it is his/her responsibility to ensure
7577: this.</p>
1.75 rillig 7578: </div>
1.148 asau 7579: <div class="sect2">
1.75 rillig 7580: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7581: <a name="dependencies"></a>21.1.5. Handling dependencies</h3></div></div></div>
1.290 gutterid 7582: <p>Your package may depend on some other package being present,
7583: and there are various ways of expressing this dependency.
7584: pkgsrc supports the <code class="varname">DEPENDS</code>,
7585: <code class="varname">BUILD_DEPENDS</code>,
7586: <code class="varname">TOOL_DEPENDS</code>, and
7587: <code class="varname">TEST_DEPENDS</code> definitions, the
1.88 wiz 7588: <code class="varname">USE_TOOLS</code> definition, as well as dependencies
7589: via <code class="filename">buildlink3.mk</code>, which is the preferred way
7590: to handle dependencies, and which uses the variables named above.
1.299 rillig 7591: See <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a> for more information.</p>
1.290 gutterid 7592: <p>The basic difference is that the <code class="varname">DEPENDS</code>
7593: definition registers that pre-requisite in the binary package so it
7594: will be pulled in when the binary package is later installed, whilst
7595: the <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7596: and <code class="varname">TEST_DEPENDS</code> definitions do not, marking a
7597: dependency that is only needed for building or testing the resulting
1.299 rillig 7598: package. See also <a class="xref" href="#creating" title="Chapter 14. Creating a new pkgsrc package from scratch">Chapter 14, <i>Creating a new pkgsrc package from scratch</i></a> for more information.</p>
1.75 rillig 7599: <p>This means that if you only need a package present whilst
1.290 gutterid 7600: you are building or testing, it should be noted as a
7601: <code class="varname">TOOL_DEPENDS</code>,
7602: <code class="varname">BUILD_DEPENDS</code>, or
7603: <code class="varname">TEST_DEPENDS</code>. When cross-compiling,
1.269 leot 7604: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
7605: packages, i.e. packages for the architecture where the package
7606: is built;
7607: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.290 gutterid 7608: packages, i.e., packages for the architecture for which the package
1.269 leot 7609: is built.</p>
1.290 gutterid 7610: <p>The format for a <code class="varname">DEPENDS</code>,
7611: <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7612: and <code class="varname">TEST_DEPENDS</code> definition is:</p>
1.75 rillig 7613: <pre class="programlisting">
1.100 rillig 7614: <pre-req-package-name>:../../<category>/<pre-req-package>
1.222 sevan 7615: </pre>
1.128 wiz 7616: <p>Please note that the <span class="quote">“<span class="quote">pre-req-package-name</span>”</span>
1.87 wiz 7617: may include any of the wildcard version numbers recognized by
1.322 leot 7618: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
1.128 wiz 7619: <div class="orderedlist"><ol class="orderedlist" type="1">
7620: <li class="listitem">
1.75 rillig 7621: <p>If your package needs another package's binaries or
1.160 wiz 7622: libraries to build and run, and if that package has a
1.87 wiz 7623: <code class="filename">buildlink3.mk</code> file available, use it:</p>
1.75 rillig 7624: <pre class="programlisting">
1.100 rillig 7625: .include "../../graphics/jpeg/buildlink3.mk"
1.222 sevan 7626: </pre>
1.75 rillig 7627: </li>
1.128 wiz 7628: <li class="listitem">
1.160 wiz 7629: <p>If your package needs another package's binaries or
7630: libraries only for building, and if that package has a
7631: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7632: <pre class="programlisting">
7633: .include "../../graphics/jpeg/buildlink3.mk"
1.222 sevan 7634: </pre>
1.160 wiz 7635: <p>but set
7636: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>jpeg</code></em>?=build</code>
7637: to make it a build dependency only. This case is rather
7638: rare.</p>
7639: </li>
7640: <li class="listitem">
1.132 spz 7641: <p>If your package needs binaries from another package to build,
1.269 leot 7642: use the <code class="varname">TOOL_DEPENDS</code> definition:</p>
1.75 rillig 7643: <pre class="programlisting">
1.269 leot 7644: TOOL_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
1.222 sevan 7645: </pre>
1.75 rillig 7646: </li>
1.269 leot 7647: <li class="listitem"><p>If your package needs static libraries to link against, header
7648: files to include, etc. from another package to build,
7649: use the <code class="varname">BUILD_DEPENDS</code> definition.</p></li>
1.132 spz 7650: <li class="listitem"><p>If your package needs a library with which to link and
7651: there is no <code class="filename">buildlink3.mk</code> file
7652: available, create one. Using
7653: <code class="varname">DEPENDS</code> won't be sufficient because the
7654: include files and libraries will be hidden from the compiler.</p></li>
1.128 wiz 7655: <li class="listitem">
1.132 spz 7656: <p>If your package needs some executable to be able to run
7657: correctly and if there's no
7658: <code class="filename">buildlink3.mk</code> file, this is specified
7659: using the <code class="varname">DEPENDS</code> variable. The
1.322 leot 7660: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/lyx/index.html" target="_top"><code class="filename">print/lyx</code></a> package needs to
1.242 wiz 7661: be able to execute the latex binary from the tex-latex-bin package
1.132 spz 7662: when it runs, and that is specified:</p>
1.75 rillig 7663: <pre class="programlisting">
1.242 wiz 7664: DEPENDS+= tex-latex-bin-[0-9]*:../../print/tex-latex-bin
1.222 sevan 7665: </pre>
1.132 spz 7666: </li>
1.290 gutterid 7667: <li class="listitem"><p>If your package includes a test suite that has extra
7668: dependencies only required for this purpose (frequently this
7669: can be run as a <span class="quote">“<span class="quote">make test</span>”</span> target), use the
7670: <code class="varname">TEST_DEPENDS</code> variable.</p></li>
1.132 spz 7671: <li class="listitem">
7672: <p>You can use wildcards in package dependencies. Note that
7673: such wildcard dependencies are retained when creating binary
7674: packages. The dependency is checked when installing the binary
7675: package and any package which matches the pattern will be
7676: used. Wildcard dependencies should be used with care.</p>
1.128 wiz 7677: <p>The <span class="quote">“<span class="quote">-[0-9]*</span>”</span> should be used instead of
7678: <span class="quote">“<span class="quote">-*</span>”</span> to avoid potentially ambiguous matches
7679: such as <span class="quote">“<span class="quote">tk-postgresql</span>”</span> matching a
7680: <span class="quote">“<span class="quote">tk-*</span>”</span> <code class="varname">DEPENDS</code>.</p>
1.75 rillig 7681: <p>Wildcards can also be used to specify that a package
1.87 wiz 7682: will only build against a certain minimum version of a
7683: pre-requisite:</p>
1.75 rillig 7684: <pre class="programlisting">
1.132 spz 7685: DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
1.222 sevan 7686: </pre>
1.132 spz 7687: <p>This means that the package will build using version 6.0
7688: of ImageMagick or newer. Such a dependency may be warranted
7689: if, for example, the command line options of an executable
7690: have changed.</p>
7691: <p>If you need to depend on minimum versions of libraries,
1.298 wiz 7692: set
7693: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
7694: to the appropriate pattern before including its
7695: <code class="filename">buildlink3.mk</code> file, e.g.</p>
7696: <pre class="programlisting">
7697: BUILDLINK_API_DEPENDS.jpeg+= jpeg>=9.0
7698: .include "../../graphics/jpeg/buildlink3.mk"
7699: </pre>
1.75 rillig 7700: <p>For security fixes, please update the package
1.267 rillig 7701: vulnerabilities file. See <a class="xref" href="#security-handling" title="21.1.9. Handling packages with security problems">Section 21.1.9, “Handling packages with security problems”</a> for more
1.87 wiz 7702: information.</p>
1.75 rillig 7703: </li>
7704: </ol></div>
7705: <p>If your package needs files from another package to build,
1.87 wiz 7706: add the relevant distribution files to
7707: <code class="varname">DISTFILES</code>, so they will be extracted
1.322 leot 7708: automatically. See the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/ghostscript/index.html" target="_top"><code class="filename">print/ghostscript</code></a> package for an example.
1.87 wiz 7709: (It relies on the jpeg sources being present in source form
7710: during the build.)</p>
1.75 rillig 7711: </div>
1.148 asau 7712: <div class="sect2">
1.75 rillig 7713: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7714: <a name="conflicts"></a>21.1.6. Handling conflicts with other packages</h3></div></div></div>
1.75 rillig 7715: <p>Your package may conflict with other packages a user might
1.87 wiz 7716: already have installed on his system, e.g. if your package
1.88 wiz 7717: installs the same set of files as another package in the pkgsrc
1.190 wiz 7718: tree or has the same <code class="varname">PKGNAME</code>.</p>
1.322 leot 7719: <p>For example, <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/libXaw3d/index.html" target="_top"><code class="filename">x11/libXaw3d</code></a>
7720: and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/Xaw-Xpm/index.html" target="_top"><code class="filename">x11/Xaw-Xpm</code></a>
1.255 leot 7721: install the same shared library, thus you set in
7722: <code class="filename">pkgsrc/x11/libXaw3d/Makefile</code>:</p>
7723: <pre class="programlisting">
7724: CONFLICTS= Xaw-Xpm-[0-9]*
7725: </pre>
7726: <p>and in <code class="filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>:</p>
7727: <pre class="programlisting">
7728: CONFLICTS= libXaw3d-[0-9]*
7729: </pre>
1.322 leot 7730: <p><a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> is able to detect attempts to install packages
1.255 leot 7731: that conflict with existing packages and abort. However, in many
7732: situations this is too late in the process. Binary package managers
7733: will not know about the conflict until they attempt to install the
7734: package after already downloading it and all its dependencies.
7735: Users may also waste time building a package and its dependencies
7736: only to find out at the end that it conflicts with another package
7737: they have installed.</p>
7738: <p>To avoid these issues <code class="varname">CONFLICTS</code> entries
7739: should be added in all cases where it is known that packages conflict
7740: with each other. These <code class="varname">CONFLICTS</code> entries are
1.322 leot 7741: exported in <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> files and consumed by binary package
1.255 leot 7742: managers to inform users that packages cannot be installed onto
7743: the target system.</p>
1.75 rillig 7744: </div>
1.148 asau 7745: <div class="sect2">
1.75 rillig 7746: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7747: <a name="not-building-packages"></a>21.1.7. Packages that cannot or should not be built</h3></div></div></div>
1.75 rillig 7748: <p>There are several reasons why a package might be
1.88 wiz 7749: instructed to not build under certain circumstances. If the
1.87 wiz 7750: package builds and runs on most platforms, the exceptions
1.193 dholland 7751: should be noted with <code class="varname">BROKEN_ON_PLATFORM</code>. If
7752: the package builds and runs on a small handful of platforms,
7753: set <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> instead.
7754: Both <code class="varname">BROKEN_ON_PLATFORM</code> and
7755: <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> are OS triples
7756: (OS-version-platform) that can use glob-style
7757: wildcards.</p>
7758: <p>If a package is not appropriate for some platforms (as
1.225 maya 7759: opposed to merely broken), a different set of variables should be
1.193 dholland 7760: used as this affects failure reporting and statistics.
7761: If the package is appropriate for most platforms, the exceptions
1.87 wiz 7762: should be noted with <code class="varname">NOT_FOR_PLATFORM</code>. If
1.193 dholland 7763: the package is appropriate for only a small handful of platforms
7764: (often exactly one), set <code class="varname">ONLY_FOR_PLATFORM</code> instead.
1.87 wiz 7765: Both <code class="varname">ONLY_FOR_PLATFORM</code> and
7766: <code class="varname">NOT_FOR_PLATFORM</code> are OS triples
7767: (OS-version-platform) that can use glob-style
7768: wildcards.</p>
1.88 wiz 7769: <p>Some packages are tightly bound to a specific version of an
1.322 leot 7770: operating system, e.g. LKMs or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/lsof/index.html" target="_top"><code class="filename">sysutils/lsof</code></a>. Such binary packages are not
1.88 wiz 7771: backwards compatible with other versions of the OS, and should be
7772: uploaded to a version specific directory on the FTP server. Mark
7773: these packages by setting <code class="varname">OSVERSION_SPECIFIC</code> to
1.128 wiz 7774: <span class="quote">“<span class="quote">yes</span>”</span>. This variable is not currently used by any of
1.88 wiz 7775: the package system internals, but may be used in the
7776: future.</p>
1.75 rillig 7777: <p>If the package should be skipped (for example, because it
1.87 wiz 7778: provides functionality already provided by the system), set
1.88 wiz 7779: <code class="varname">PKG_SKIP_REASON</code> to a descriptive message. If
7780: the package should fail because some preconditions are not met,
7781: set <code class="varname">PKG_FAIL_REASON</code> to a descriptive
1.87 wiz 7782: message.</p>
1.75 rillig 7783: </div>
1.148 asau 7784: <div class="sect2">
1.75 rillig 7785: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7786: <a name="undeletable-packages"></a>21.1.8. Packages which should not be deleted, once installed</h3></div></div></div>
1.75 rillig 7787: <p>To ensure that a package may not be deleted, once it has been
1.87 wiz 7788: installed, the <code class="varname">PKG_PRESERVE</code> definition should
7789: be set in the package Makefile. This will be carried into any
7790: binary package that is made from this pkgsrc entry. A
1.128 wiz 7791: <span class="quote">“<span class="quote">preserved</span>”</span> package will
1.322 leot 7792: not be deleted using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
1.128 wiz 7793: <span class="quote">“<span class="quote">-f</span>”</span> option is used.</p>
1.75 rillig 7794: </div>
1.148 asau 7795: <div class="sect2">
1.75 rillig 7796: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7797: <a name="security-handling"></a>21.1.9. Handling packages with security problems</h3></div></div></div>
1.75 rillig 7798: <p>When a vulnerability is found, this should be noted in
1.320 wiz 7799: <code class="filename">localsrc/security/advisories/pkg-vulnerabilities</code>.
7800: Entries in that file consist of three parts:</p>
7801: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7802: <li class="listitem"><p>package version pattern</p></li>
7803: <li class="listitem"><p>type of vulnerability (please cut'n'paste an existing one where possible)</p></li>
7804: <li class="listitem"><p>URL providing additional information about the issue</p></li>
7805: </ul></div>
7806: <p>For the package version pattern please always use `<' to
7807: mark an upper bound (not `<='!). This will avoid possible
7808: problems due unrelated <code class="varname">PKGREVISION</code> bumps not
7809: related to security fixes. Lower bounds can be added too, using
7810: '>' or '>='. For example,
1.321 wiz 7811: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.2</code></span>”</span> would mark
1.320 wiz 7812: versions 1.0 (included) to 1.2 (excluded) of
7813: <span class="quote">“<span class="quote"><code class="literal">foo</code></span>”</span> as affected by the security
7814: issue.</p>
7815: <p>Entries should always be added at the bottom of the file.</p>
7816: <p>When fixing packages, please modify the upper bound of the
7817: corresponding entry. To continue the previous example, if a fix
7818: was backported to version 1.1nb2, change the previous pattern to
1.321 wiz 7819: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.1nb2</code></span>”</span>.</p>
1.320 wiz 7820: <p>To locally test a package version pattern against a
7821: <code class="varname">PKGNAME</code> you can use the <span class="command"><strong>pkg_admin
7822: pmatch</strong></span> command.</p>
7823: <p>The URL should be as permanent as possible and provide as
7824: much information about the issue as possible. CVE entries are
7825: preferred.</p>
7826: <p>After committing that file, ask pkgsrc-security@NetBSD.org to
1.138 wiz 7827: update the file on ftp.NetBSD.org.</p>
1.75 rillig 7828: <p>After fixing the vulnerability by a patch, its
1.138 wiz 7829: <code class="varname">PKGREVISION</code> should be increased (this is of
7830: course not necessary if the problem is fixed by using a newer
7831: release of the software), and the pattern in the
7832: pkg-vulnerabilities file must be updated.</p>
1.75 rillig 7833: <p>Also, if the fix should be applied to the stable pkgsrc
1.87 wiz 7834: branch, be sure to submit a pullup request!</p>
1.75 rillig 7835: <p>Binary packages already on ftp.NetBSD.org will be handled
1.87 wiz 7836: semi-automatically by a weekly cron job.</p>
1.320 wiz 7837: <p>In case a security issue is disputed, please contact
7838: pkgsrc-security@NetBSD.org.</p>
1.75 rillig 7839: </div>
1.148 asau 7840: <div class="sect2">
1.75 rillig 7841: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7842: <a name="bumping-pkgrevision"></a>21.1.10. How to handle incrementing versions when fixing an existing package</h3></div></div></div>
1.75 rillig 7843: <p>When making fixes to an existing package it can be useful
1.87 wiz 7844: to change the version number in <code class="varname">PKGNAME</code>. To
7845: avoid conflicting with future versions by the original author, a
1.128 wiz 7846: <span class="quote">“<span class="quote">nb1</span>”</span>, <span class="quote">“<span class="quote">nb2</span>”</span>, ... suffix can be used
1.87 wiz 7847: on package versions by setting <code class="varname">PKGREVISION=1</code>
1.128 wiz 7848: (2, ...). The <span class="quote">“<span class="quote">nb</span>”</span> is treated like a
7849: <span class="quote">“<span class="quote">.</span>”</span> by the package tools. e.g.</p>
1.87 wiz 7850: <pre class="programlisting">
1.100 rillig 7851: DISTNAME= foo-17.42
7852: PKGREVISION= 9
1.222 sevan 7853: </pre>
1.75 rillig 7854: <p>will result in a <code class="varname">PKGNAME</code> of
1.128 wiz 7855: <span class="quote">“<span class="quote">foo-17.42nb9</span>”</span>. If you want to use the original
7856: value of <code class="varname">PKGNAME</code> without the <span class="quote">“<span class="quote">nbX</span>”</span>
1.87 wiz 7857: suffix, e.g. for setting <code class="varname">DIST_SUBDIR</code>, use
7858: <code class="varname">PKGNAME_NOREV</code>.</p>
1.75 rillig 7859: <p>When a new release of the package is released, the
1.87 wiz 7860: <code class="varname">PKGREVISION</code> should be removed, e.g. on a new
7861: minor release of the above package, things should be like:</p>
1.75 rillig 7862: <pre class="programlisting">
1.100 rillig 7863: DISTNAME= foo-17.43
1.222 sevan 7864: </pre>
1.87 wiz 7865: <p><code class="varname">PKGREVISION</code> should be incremented for any
7866: non-trivial change in the resulting binary package. Without a
7867: <code class="varname">PKGREVISION</code> bump, someone with the previous
7868: version installed has no way of knowing that their package is out
7869: of date. Thus, changes without increasing
7870: <code class="varname">PKGREVISION</code> are essentially labeled "this is so
7871: trivial that no reasonable person would want to upgrade", and this
7872: is the rough test for when increasing
7873: <code class="varname">PKGREVISION</code> is appropriate. Examples of
7874: changes that do not merit increasing
7875: <code class="varname">PKGREVISION</code> are:</p>
1.148 asau 7876: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 7877: <li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>,
1.284 rillig 7878: <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>, or
7879: comments in Makefile.</p></li>
7880: <li class="listitem"><p>Changing build variables if the resulting binary
7881: package is the same.</p></li>
7882: <li class="listitem"><p>Changing
7883: <code class="filename">DESCR</code>.</p></li>
7884: <li class="listitem"><p>Adding <code class="varname">PKG_OPTIONS</code> if the
7885: default options don't change.</p></li>
1.100 rillig 7886: </ul></div>
1.87 wiz 7887: <p>Examples of changes that do merit an increase to
7888: <code class="varname">PKGREVISION</code> include:</p>
1.148 asau 7889: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.284 rillig 7890: <li class="listitem"><p>Security fixes</p></li>
7891: <li class="listitem"><p>Changes or additions to a patch
7892: file</p></li>
7893: <li class="listitem"><p>Changes to the
7894: <code class="filename">PLIST</code></p></li>
7895: <li class="listitem"><p>A dependency is changed or
7896: renamed.</p></li>
1.100 rillig 7897: </ul></div>
1.78 rillig 7898: <p>PKGREVISION must also be incremented when dependencies have ABI
7899: changes.</p>
1.75 rillig 7900: </div>
1.148 asau 7901: <div class="sect2">
1.79 rillig 7902: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 7903: <a name="fixes.subst"></a>21.1.11. Substituting variable text in the package files (the SUBST framework)</h3></div></div></div>
1.295 rillig 7904: <p>When you want to replace the same text in multiple files, or
7905: multiple times in the same file, it is cumbersome to maintain a patch
7906: file for this. This is where the SUBST framework steps in. It provides an
7907: easy-to-use interface for replacing text in files. It just needs the
7908: following information:</p>
7909: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7910: <li class="listitem"><p>In which phase of the package build cycle should the
7911: replacement happen?</p></li>
7912: <li class="listitem"><p>In which files should the replacement
1.287 rillig 7913: happen?</p></li>
1.295 rillig 7914: <li class="listitem"><p>Which text should be replaced with
7915: what?</p></li>
1.287 rillig 7916: </ul></div>
7917: <p>This information is encoded in a block of <code class="varname">SUBST</code>
1.295 rillig 7918: variables. A minimal example is:</p>
7919: <pre class="programlisting">
7920: SUBST_CLASSES+= paths
7921: SUBST_STAGE.paths= pre-configure
7922: SUBST_FILES.paths= src/*.c
7923: SUBST_SED.paths= -e 's,/usr/local,${PREFIX},g'
7924: </pre>
7925: <p>Translated into English, it means: In the pre-configure stage (that
7926: is, after applying the patches from the patches/ directory and before
7927: running the configure script and the portability check), replace the text
7928: <code class="literal">/usr/local</code> with the content of the variable
7929: <code class="varname">PREFIX</code>.</p>
7930: <p>Each SUBST block starts by appending an identifier to
7931: <code class="varname">SUBST_CLASSES</code> (note the <code class="literal">+=</code>). This
7932: identifier can be chosen freely by the package. If there should ever be
7933: duplicate identifiers, the pkgsrc infrastructure will catch this and fail
7934: early, so don't worry about name collisions.</p>
7935: <p>Except for <code class="varname">SUBST_CLASSES</code>, all variables in a
7936: SUBST block are parameterized using this identifier. In the remainder of
7937: this section, these parameterized variables are written as
7938: <code class="varname">SUBST_STAGE.*</code>.</p>
7939: <pre class="programlisting">
7940: SUBST_CLASSES+= paths
7941: SUBST_STAGE.paths= pre-configure
7942: SUBST_MESSAGE.paths= Fixing absolute paths.
7943: SUBST_FILES.paths= src/*.c
7944: SUBST_FILES.paths+= scripts/*.sh
7945: SUBST_SED.paths= -e 's,"/usr/local,"${PREFIX},g'
7946: SUBST_SED.paths+= -e 's,"/var/log,"${VARBASE}/log,g'
7947: SUBST_VARS.paths= LOCALBASE PREFIX PKGVERSION
7948: </pre>
7949: <p>To get a complete picture about the SUBST substitutions, run
7950: <span class="command"><strong>bmake show-all-subst</strong></span>. If something doesn't work as
7951: expected, run pkglint on the package, which detects several typical
7952: mistakes surrounding the SUBST blocks. For any questions that might
7953: remain after this, have a look at
7954: <code class="filename">mk/subst.mk</code>.</p>
7955: <div class="sect3">
7956: <div class="titlepage"><div><div><h4 class="title">
7957: <a name="fixes.subst.when"></a>21.1.11.1. Choosing the time where the substitutions happen</h4></div></div></div>
7958: <p>The <code class="varname">SUBST_STAGE.*</code> is one of
7959: {pre,do,post}-{extract,patch,configure,build,test,install}. Of these,
7960: <code class="literal">pre-configure</code> is used most often, by far. The most
7961: popular stages are, in chronological order:</p>
7962: <div class="variablelist"><dl class="variablelist">
7963: <dt><span class="term"><code class="literal">post-extract</code></span></dt>
7964: <dd>
7965: <p>The substitutions are applied immediately after the
7966: distfiles are extracted. Running <span class="command"><strong>bmake extract</strong></span> on the
7967: package will leave no traces of the original files.</p>
7968: <p>When the substitution applies to files for which there is also a
7969: patch in the <code class="filename">patches/</code> directory, this means that the
7970: patches will be computed based on the result of the substitution. When
7971: these patches are sent to the upstream maintainer later, to be fixed in
7972: the upstream package, these patches may no longer match what the upstream
7973: author is used to. Because of this, <code class="literal">pre-configure</code> is
7974: often a better choice.</p>
7975: </dd>
7976: <dt><span class="term"><code class="literal">pre-configure</code></span></dt>
7977: <dd>
7978: <p>The substitutions are applied after the patches from the
7979: <code class="filename">patches/</code> directory. This makes it possible to run
7980: <span class="command"><strong>bmake patch</strong></span> on the package, after which the patches
1.322 leot 7981: can be edited using the tools pkgvi and mkpatches from the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package.</p>
1.295 rillig 7982: <p>When updating the patches, it is helpful to explicitly separate the
7983: <span class="command"><strong>bmake patch</strong></span> from the <span class="command"><strong>bmake
7984: configure</strong></span>, and to only edit the patches between these commands.
7985: Otherwise the substitutions from the SUBST block will end up in the patch
7986: file. When this happens in really obvious ways, pkglint will complain
7987: about patches that contain a hard-coded <code class="literal">/usr/pkg</code>
7988: instead of the correct and intended <code class="literal">@PREFIX@</code>, but it
7989: can only detect these really obvious
7990: cases.</p>
7991: </dd>
7992: <dt><span class="term"><code class="literal">do-configure</code></span></dt>
7993: <dd><p>This stage should only be used if the package defines a
7994: <code class="literal">pre-configure</code> action itself, and the substitution must
7995: happen after that. Typical examples are packages that use the
7996: <code class="literal">pre-configure</code> stage to regenerate the GNU configure
7997: script from
7998: <code class="filename">configure.ac</code>.</p></dd>
7999: <dt><span class="term"><code class="literal">post-configure</code></span></dt>
8000: <dd><p>This stage is used to fix up any mistakes by the
8001: configure stage.</p></dd>
8002: <dt><span class="term"><code class="literal">pre-build</code></span></dt>
8003: <dd><p>This stage should only be used for substitutions that are
8004: clearly related to building the package, not for fixing the
8005: configuration. Substitutions for pathnames (such as replacing
8006: <code class="filename">/usr/local</code> with <code class="literal">${PREFIX}</code>) or
8007: user names (such as replacing <code class="literal">@MY_USER@</code> with the
8008: actual username) belong in pre-configure or post-configure
8009: instead.</p></dd>
8010: <dt><span class="term"><code class="literal">post-build</code></span></dt>
8011: <dd>
8012: <p>Just as with pre-build, this stage should only be used
8013: for substitutions that are clearly related to building the package, not
8014: for fixing the configuration. Substitutions for pathnames (such as
8015: replacing <code class="filename">/usr/local</code> with
8016: <code class="literal">${PREFIX}</code>) or user names (such as replacing
8017: <code class="literal">@MY_USER@</code> with the actual username) belong in
8018: pre-configure or post-configure instead.</p>
8019: <p>A typical use is to update pkg-config files to include the rpath
8020: compiler options.</p>
8021: </dd>
8022: <dt><span class="term"><code class="literal">pre-install</code></span></dt>
8023: <dd><p>In general, the install phase should be as simple as
8024: possible. As with the pre-build and post-build stages, it should not be
8025: used to fix pathnames or user names, these belong in pre-configure
8026: instead. There are only few legitimate use cases for applying
8027: substitutions in this stage.</p></dd>
8028: </dl></div>
8029: </div>
8030: <div class="sect3">
8031: <div class="titlepage"><div><div><h4 class="title">
1.296 rillig 8032: <a name="fixes.subst.where"></a>21.1.11.2. Choosing the files where the substitutions happen</h4></div></div></div>
1.295 rillig 8033: <p>The <code class="varname">SUBST_FILES.*</code> variable contains a list of
8034: filename patterns. These patterns are relative to
8035: <code class="varname">WRKSRC</code> since that is where most substitutions happen.
8036: A typical example is:</p>
8037: <pre class="programlisting">
8038: SUBST_FILES.path= Makefile */Makefile */*/Makefile *.[ch]
8039: </pre>
8040: <p>The above patterns, especially the last, are quite broad. The SUBST
8041: implementation checks that each filename pattern that is mentioned here
8042: has an effect. For example, if none of the
8043: <code class="filename">*/*/Makefile</code> files contains the patterns to be found
8044: and substituted, that filename pattern is redundant and should be left
1.296 rillig 8045: out. By default, the SUBST framework will complain with an error message.
8046: If the text to be substituted occurs in some of the files from a single
8047: pattern, but not in all of them, that is totally ok, and the SUBST
1.295 rillig 8048: framework will only print an INFO message for those files.</p>
8049: <p>If there is a good reason for having redundant filename patterns,
1.296 rillig 8050: set <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
1.295 rillig 8051: <p>Another popular way of choosing the files for the substitutions is
8052: via a shell command, like this:</p>
8053: <pre class="programlisting">
1.296 rillig 8054: C_FILES_CMD= cd ${WRKSRC} && ${FIND} . -name '*.c'
1.295 rillig 8055: SUBST_FILES.path= ${C_FILES_CMD:sh}
8056: </pre>
8057: <p>The variable name <code class="varname">C_FILES_CMD</code> in this example is
8058: freely chosen and independent of the SUBST framework.</p>
8059: <p>In this variant, the <code class="varname">SUBST_FILES.*</code> variable
8060: lists each file individually. Thereby chances are higher that there are
8061: filename patterns in which no substitution happens. Since the SUBST
8062: framework cannot know whether the filename patterns in
8063: <code class="varname">SUBST_FILES.*</code> have been explicitly listed in the
8064: Makefile (where any redundant filename pattern would be suspicious) or
8065: been generated by a shell command (in which redundant filename patterns
8066: are more likely and to be expected), it will complain about these
8067: redundant filename patterns. Therefore, SUBST blocks that use a shell
8068: command to generate the list of filename patterns often need to set
8069: <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
8070: </div>
8071: <div class="sect3">
8072: <div class="titlepage"><div><div><h4 class="title">
8073: <a name="fixes.subst.what"></a>21.1.11.3. Choosing what to substitute</h4></div></div></div>
8074: <p>In most cases, the substitutions are given using one or more
1.322 leot 8075: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/sed.1"><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> commands, like this:</p>
1.295 rillig 8076: <pre class="programlisting">
8077: SUBST_SED.path= -e 's|/usr/local|${PREFIX}|g'
8078: </pre>
8079: <p>Each of the sed commands needs to be preceded by the
8080: <code class="literal">-e</code> option and should be specified on a line of its
8081: own, to avoid hiding short sed commands at the end of a line.</p>
8082: <p>Since the sed commands often contain shell metacharacters as the
8083: separator (the <code class="literal">|</code> in the above example), it is common
8084: to enclose them in single quotes.</p>
8085: <p>A common substitution is to replace placeholders of the form
8086: <code class="literal">@VARNAME@</code> with their pkgsrc counterpart variable
8087: <code class="literal">${VARNAME}</code>. A typical example is:</p>
8088: <pre class="programlisting">
8089: SUBST_VARS.path= PREFIX
8090: </pre>
8091: <p>This type of substitutions is typically done by the GNU configure
1.296 rillig 8092: scripts during the do-configure stage, but in some cases these need to be
8093: overridden. The same pattern is also used when a package defines patches
8094: that replace previously hard-coded paths like
8095: <code class="literal">/usr/local</code> with a <code class="literal">@PREFIX@</code>
8096: placeholder first, which then gets substituted by the actual
8097: <code class="literal">${PREFIX}</code> in the pre-configure stage. In many of these
8098: cases, it works equally well to just use the SUBST framework to directly
8099: replace <code class="literal">/usr/local</code> with <code class="literal">${PREFIX}</code>,
8100: thereby omitting the intermediate patch file.</p>
1.295 rillig 8101: <p>If the above is not flexible enough, it is possible to not use sed
8102: at all for the substitution but to specify an entirely different command,
8103: like this:</p>
1.87 wiz 8104: <pre class="programlisting">
1.295 rillig 8105: SUBST_FILTER_CMD.path= LC_ALL=C ${TR} -d '\r'
8106: </pre>
8107: <p>This is used for the few remaining packages in which the
8108: distributed files use Windows-style line endings that need to be
8109: converted to UNIX-style line endings.</p>
8110: </div>
8111: <div class="sect3">
8112: <div class="titlepage"><div><div><h4 class="title">
8113: <a name="fixes.subst.other"></a>21.1.11.4. Other SUBST variables</h4></div></div></div>
8114: <p>When a SUBST block is applied during a package build, a message is
8115: logged. The default message is fine for most purposes but can be
8116: overridden by setting <code class="literal">SUBST_MESSAGE.*</code> to an individual
8117: message.</p>
8118: </div>
1.79 rillig 8119: </div>
1.75 rillig 8120: </div>
1.148 asau 8121: <div class="sect1">
1.75 rillig 8122: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 8123: <a name="fixes.fetch"></a>21.2. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
1.148 asau 8124: <div class="sect2">
1.75 rillig 8125: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8126: <a name="no-plain-download"></a>21.2.1. Packages whose distfiles aren't available for plain downloading</h3></div></div></div>
1.75 rillig 8127: <p>If you need to download from a dynamic URL you can set
1.110 hubertf 8128: <code class="varname">DYNAMIC_MASTER_SITES</code> and a <span class="command"><strong>make
1.87 wiz 8129: fetch</strong></span> will call <code class="filename">files/getsite.sh</code>
8130: with the name of each file to download as an argument, expecting
8131: it to output the URL of the directory from which to download
1.322 leot 8132: it. <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/ns-cult3d/index.html" target="_top"><code class="filename">graphics/ns-cult3d</code></a> is an
1.87 wiz 8133: example of this usage.</p>
1.75 rillig 8134: <p>If the download can't be automated, because the user must
1.87 wiz 8135: submit personal information to apply for a password, or must pay
8136: for the source, or whatever, you can set
8137: <code class="varname">FETCH_MESSAGE</code> to a list of lines that are
8138: displayed to the user before aborting the build. Example:</p>
8139: <pre class="programlisting">
1.100 rillig 8140: FETCH_MESSAGE= "Please download the files"
8141: FETCH_MESSAGE+= " "${DISTFILES:Q}
8142: FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
1.222 sevan 8143: </pre>
1.75 rillig 8144: </div>
1.148 asau 8145: <div class="sect2">
1.75 rillig 8146: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8147: <a name="modified-distfiles-same-name"></a>21.2.2. How to handle modified distfiles with the 'old' name</h3></div></div></div>
1.75 rillig 8148: <p>Sometimes authors of a software package make some
1.87 wiz 8149: modifications after the software was released, and they put up a
8150: new distfile without changing the package's version number. If a
8151: package is already in pkgsrc at that time, the checksum will
8152: no longer match. The contents of the new distfile should be
8153: compared against the old one before changing anything, to make
8154: sure the distfile was really updated on purpose, and that
8155: no trojan horse or so crept in.
1.97 rillig 8156: Please mention that the distfiles were compared and what was found
1.159 rodent 8157: in your commit message.</p>
1.220 wiz 8158: <p>Then, the correct way to work around this is to set
8159: <code class="varname">DIST_SUBDIR</code> to a unique directory name, usually
8160: based on <code class="varname">PKGNAME_NOREV</code> (but take care with
8161: python or ruby packages, where <code class="varname">PKGNAME</code> includes
8162: a variable prefix). All <code class="varname">DISTFILES</code> and
1.93 rillig 8163: <code class="varname">PATCHFILES</code> for this package will be put in that
1.267 rillig 8164: subdirectory of the local distfiles directory. (See <a class="xref" href="#bumping-pkgrevision" title="21.1.10. How to handle incrementing versions when fixing an existing package">Section 21.1.10, “How to handle incrementing versions when fixing an existing package”</a> for more details.) In case this
1.87 wiz 8165: happens more often, <code class="varname">PKGNAME</code> can be used (thus
1.220 wiz 8166: including the <code class="filename">nbX</code> suffix) or a date stamp can
8167: be appended, like
8168: <code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>.</p>
1.284 rillig 8169: <p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's
8170: name does not contain a version and the distfile is apt to change. In
8171: cases where the likelihood of this is very small,
8172: <code class="varname">DIST_SUBDIR</code> might not be required. Additionally,
8173: <code class="varname">DIST_SUBDIR</code> must not be removed unless the
8174: distfile name changes, even if a package is being moved or
8175: renamed.</p>
1.159 rodent 8176: <p>Do not forget regenerating the <code class="filename">distinfo</code> file
1.87 wiz 8177: after that, since it contains the <code class="varname">DIST_SUBDIR</code>
8178: path in the filenames.
1.159 rodent 8179: Also, increase the PKGREVISION if the installed package is different.
1.87 wiz 8180: Furthermore, a mail to the package's authors seems appropriate
8181: telling them that changing distfiles after releases without
8182: changing the file names is not good practice.</p>
1.75 rillig 8183: </div>
1.199 tnn 8184: <div class="sect2">
8185: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8186: <a name="build.fetch.github"></a>21.2.3. Packages hosted on github.com</h3></div></div></div>
1.284 rillig 8187: <p>Helper methods exist for packages hosted on github.com which
8188: will often have distfile names that clash with other packages, for
8189: example <code class="filename">1.0.tar.gz</code>. Use one of the three recipes
8190: from below:</p>
1.199 tnn 8191: <div class="sect3">
8192: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 8193: <a name="build.fetch.github.tag"></a>21.2.3.1. Fetch based on a tagged release</h4></div></div></div>
1.284 rillig 8194: <p>If your distfile URL looks similar to
1.303 bacon 8195: <code class="literal">https://github.com/username/example/archive/v1.0.zip</code>,
1.284 rillig 8196: then you are packaging a tagged release.</p>
1.199 tnn 8197: <pre class="programlisting">
1.303 bacon 8198: DISTNAME= example-1.0
1.200 tnn 8199: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.303 bacon 8200: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.200 tnn 8201: GITHUB_TAG= v${PKGVERSION_NOREV}
1.199 tnn 8202: EXTRACT_SUFX= .zip
8203: </pre>
8204: </div>
8205: <div class="sect3">
8206: <div class="titlepage"><div><div><h4 class="title">
1.303 bacon 8207: <a name="build.fetch.github.commit.prerelease"></a>21.2.3.2. Fetch based on a specific commit before the first release</h4></div></div></div>
8208: <p>If your distfile looks similar to
8209: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit before the first
8210: release, then set the package version to 0.0.0.N, where N is the number
8211: of commits to the repository, and set GITHUB_TAG to the commit hash.
8212: This will (almost) ensure that the first tagged release will have a
8213: version greater than this one so that package upgrades will function
8214: properly.</p>
8215: <pre class="programlisting">
8216: DISTNAME= example-0.0.0.347
8217: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8218: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
8219: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
8220: </pre>
8221: </div>
8222: <div class="sect3">
8223: <div class="titlepage"><div><div><h4 class="title">
8224: <a name="build.fetch.github.commit.postrelease"></a>21.2.3.3. Fetch based on a specific commit after a release</h4></div></div></div>
8225: <p>If your distfile looks similar to
8226: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit after a release,
8227: then include the last release version and the commit count since that
8228: release in the package version and set GITHUB_TAG to the commit hash.
8229: The latest release and commit count are shown in the output of
8230: "git describe --tags":
8231: </p>
8232: <pre class="screen">
8233: # git clone https://github.com/username/example
8234: # cd example
8235: # git describe --tags
8236: 1.2.3-5-g988881a
8237: </pre>
1.199 tnn 8238: <pre class="programlisting">
1.303 bacon 8239: DISTNAME= example-1.2.3.5
8240: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8241: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.200 tnn 8242: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
1.222 sevan 8243: </pre>
1.199 tnn 8244: </div>
8245: <div class="sect3">
8246: <div class="titlepage"><div><div><h4 class="title">
1.303 bacon 8247: <a name="build.fetch.github.release"></a>21.2.3.4. Fetch based on release</h4></div></div></div>
1.284 rillig 8248: <p>If your distfile URL looks similar to
1.303 bacon 8249: <code class="literal">https://github.com/username/example/releases/download/rel-1.6/offensive-1.6.zip</code>,
1.284 rillig 8250: then you are packaging a release.</p>
1.199 tnn 8251: <pre class="programlisting">
8252: DISTNAME= offensive-1.6
1.200 tnn 8253: PKGNAME= ${DISTNAME:S/offensive/proper/}
8254: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.303 bacon 8255: GITHUB_PROJECT= example
1.200 tnn 8256: GITHUB_RELEASE= rel-${PKGVERSION_NOREV} # usually just set this to ${DISTNAME}
8257: EXTRACT_SUFX= .zip
1.222 sevan 8258: </pre>
1.199 tnn 8259: </div>
8260: </div>
1.75 rillig 8261: </div>
1.148 asau 8262: <div class="sect1">
1.75 rillig 8263: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 8264: <a name="fixes.configure"></a>21.3. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
1.148 asau 8265: <div class="sect2">
1.75 rillig 8266: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8267: <a name="fixes.libtool"></a>21.3.1. Shared libraries - libtool</h3></div></div></div>
1.75 rillig 8268: <p>pkgsrc supports many different machines, with different
1.87 wiz 8269: object formats like a.out and ELF, and varying abilities to do
8270: shared library and dynamic loading at all. To accompany this,
8271: varying commands and options have to be passed to the
8272: compiler, linker, etc. to get the Right Thing, which can be
8273: pretty annoying especially if you don't have all the machines
8274: at your hand to test things. The
1.322 leot 8275: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool/index.html" target="_top"><code class="filename">devel/libtool</code></a> pkg
1.128 wiz 8276: can help here, as it just <span class="quote">“<span class="quote">knows</span>”</span> how to build
1.87 wiz 8277: both static and dynamic libraries from a set of source files,
8278: thus being platform-independent.</p>
8279: <p>Here's how to use libtool in a package in seven simple
8280: steps:</p>
1.128 wiz 8281: <div class="orderedlist"><ol class="orderedlist" type="1">
8282: <li class="listitem"><p>Add <code class="varname">USE_LIBTOOL=yes</code> to the package
1.87 wiz 8283: Makefile.</p></li>
1.128 wiz 8284: <li class="listitem"><p>For library objects, use <span class="quote">“<span class="quote">${LIBTOOL} --mode=compile
8285: ${CC}</span>”</span> in place of <span class="quote">“<span class="quote">${CC}</span>”</span>. You could even
1.87 wiz 8286: add it to the definition of <code class="varname">CC</code>, if only
8287: libraries are being built in a given Makefile. This one command
8288: will build both PIC and non-PIC library objects, so you need not
8289: have separate shared and non-shared library rules.</p></li>
1.128 wiz 8290: <li class="listitem">
1.75 rillig 8291: <p>For the linking of the library, remove any
1.128 wiz 8292: <span class="quote">“<span class="quote">ar</span>”</span>, <span class="quote">“<span class="quote">ranlib</span>”</span>, and <span class="quote">“<span class="quote">ld
8293: -Bshareable</span>”</span> commands, and instead use:</p>
1.75 rillig 8294: <pre class="programlisting">
1.100 rillig 8295: ${LIBTOOL} --mode=link \
8296: ${CC} -o ${.TARGET:.a=.la} \
8297: ${OBJS:.o=.lo} \
8298: -rpath ${PREFIX}/lib \
8299: -version-info major:minor
1.222 sevan 8300: </pre>
1.75 rillig 8301: <p>Note that the library is changed to have a
1.87 wiz 8302: <code class="filename">.la</code> extension, and the objects are
8303: changed to have a <code class="filename">.lo</code>
8304: extension. Change <code class="varname">OBJS</code> as
8305: necessary. This automatically creates all of the
8306: <code class="filename">.a</code>,
8307: <code class="filename">.so.major.minor</code>, and ELF symlinks (if
8308: necessary) in the build directory. Be sure to include
1.128 wiz 8309: <span class="quote">“<span class="quote">-version-info</span>”</span>, especially when major and
1.87 wiz 8310: minor are zero, as libtool will otherwise strip off the
8311: shared library version.</p>
1.75 rillig 8312: <p>From the libtool manual:</p>
8313: <pre class="programlisting">
1.100 rillig 8314: So, libtool library versions are described by three integers:
1.69 rillig 8315:
1.100 rillig 8316: CURRENT
8317: The most recent interface number that this library implements.
1.69 rillig 8318:
1.100 rillig 8319: REVISION
8320: The implementation number of the CURRENT interface.
1.69 rillig 8321:
1.100 rillig 8322: AGE
8323: The difference between the newest and oldest interfaces that
8324: this library implements. In other words, the library implements
8325: all the interface numbers in the range from number `CURRENT -
8326: AGE' to `CURRENT'.
1.1 grant 8327:
1.100 rillig 8328: If two libraries have identical CURRENT and AGE numbers, then the
8329: dynamic linker chooses the library with the greater REVISION number.
1.222 sevan 8330: </pre>
1.128 wiz 8331: <p>The <span class="quote">“<span class="quote">-release</span>”</span> option will produce
1.87 wiz 8332: different results for a.out and ELF (excluding symlinks)
8333: in only one case. An ELF library of the form
1.128 wiz 8334: <span class="quote">“<span class="quote">libfoo-release.so.<span class="emphasis"><em>x</em></span>.<span class="emphasis"><em>y</em></span></span>”</span>
1.87 wiz 8335: will have a symlink of
1.128 wiz 8336: <span class="quote">“<span class="quote">libfoo.so.<span class="emphasis"><em>x</em></span>.<span class="emphasis"><em>y</em></span></span>”</span>
1.87 wiz 8337: on an a.out platform. This is handled
8338: automatically.</p>
1.128 wiz 8339: <p>The <span class="quote">“<span class="quote">-rpath argument</span>”</span> is the install
1.87 wiz 8340: directory of the library being built.</p>
1.76 rillig 8341: <p>In the <code class="filename">PLIST</code>, include only the
1.87 wiz 8342: <code class="filename">.la</code> file, the other files will be
8343: added automatically.</p>
1.75 rillig 8344: </li>
1.128 wiz 8345: <li class="listitem">
1.76 rillig 8346: <p>When linking shared object (<code class="filename">.so</code>)
1.322 leot 8347: files, i.e. files that are loaded via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/dlopen.3"><span class="citerefentry"><span class="refentrytitle">dlopen</span>(3)</span></a>, NOT
1.128 wiz 8348: shared libraries, use <span class="quote">“<span class="quote">-module
8349: -avoid-version</span>”</span> to prevent them getting version
1.87 wiz 8350: tacked on.</p>
1.76 rillig 8351: <p>The <code class="filename">PLIST</code> file gets the
1.87 wiz 8352: <code class="filename">foo.so</code> entry.</p>
1.75 rillig 8353: </li>
1.128 wiz 8354: <li class="listitem">
1.75 rillig 8355: <p>When linking programs that depend on these libraries
1.87 wiz 8356: <span class="emphasis"><em>before</em></span> they are installed, preface
1.322 leot 8357: the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cc.1"><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ld.1"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span class="quote">“<span class="quote">${LIBTOOL}
1.128 wiz 8358: --mode=link</span>”</span>, and it will find the correct
1.87 wiz 8359: libraries (static or shared), but please be aware that
8360: libtool will not allow you to specify a relative path in
1.128 wiz 8361: -L (such as <span class="quote">“<span class="quote">-L../somelib</span>”</span>), because it
1.87 wiz 8362: expects you to change that argument to be the
8363: <code class="filename">.la</code> file. e.g.</p>
1.75 rillig 8364: <pre class="programlisting">
1.100 rillig 8365: ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
1.222 sevan 8366: </pre>
1.75 rillig 8367: <p>should be changed to:</p>
8368: <pre class="programlisting">
1.100 rillig 8369: ${LIBTOOL} --mode=link ${CC} -o <em class="replaceable"><code>someprog</code></em> <em class="replaceable"><code>../somelib/somelib.la</code></em>
1.222 sevan 8370: </pre>
1.75 rillig 8371: <p>and it will do the right thing with the libraries.</p>
8372: </li>
1.128 wiz 8373: <li class="listitem">
1.322 leot 8374: <p>When installing libraries, preface the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a>
8375: or <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cp.1"><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span class="quote">“<span class="quote">${LIBTOOL}
1.128 wiz 8376: --mode=install</span>”</span>, and change the library name to
1.87 wiz 8377: <code class="filename">.la</code>. e.g.</p>
1.75 rillig 8378: <pre class="programlisting">
1.126 jakllsch 8379: ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib
1.222 sevan 8380: </pre>
1.76 rillig 8381: <p>This will install the static <code class="filename">.a</code>,
1.87 wiz 8382: shared library, any needed symlinks, and run
1.322 leot 8383: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ldconfig.8"><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
1.75 rillig 8384: </li>
1.128 wiz 8385: <li class="listitem"><p>In your <code class="filename">PLIST</code>, include only
1.87 wiz 8386: the <code class="filename">.la</code>
8387: file (this is a change from previous behaviour).</p></li>
1.75 rillig 8388: </ol></div>
8389: </div>
1.148 asau 8390: <div class="sect2">
1.75 rillig 8391: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8392: <a name="using-libtool"></a>21.3.2. Using libtool on GNU packages that already support libtool</h3></div></div></div>
1.75 rillig 8393: <p>Add <code class="varname">USE_LIBTOOL=yes</code> to the
1.87 wiz 8394: package Makefile. This will override the package's own libtool
8395: in most cases. For older libtool using packages, libtool is
8396: made by ltconfig script during the do-configure step; you can
1.110 hubertf 8397: check the libtool script location by doing <span class="command"><strong>make
1.87 wiz 8398: configure; find work*/ -name libtool</strong></span>.</p>
1.75 rillig 8399: <p><code class="varname">LIBTOOL_OVERRIDE</code> specifies which libtool
1.87 wiz 8400: scripts, relative to <code class="varname">WRKSRC</code>, to override. By
1.128 wiz 8401: default, it is set to <span class="quote">“<span class="quote">libtool */libtool
8402: */*/libtool</span>”</span>. If this does not match the location of the
1.87 wiz 8403: package's libtool script(s), set it as appropriate.</p>
1.76 rillig 8404: <p>If you do not need <code class="filename">*.a</code> static
1.87 wiz 8405: libraries built and installed, then use
8406: <code class="varname">SHLIBTOOL_OVERRIDE</code> instead.</p>
1.75 rillig 8407: <p>If your package makes use of the platform-independent library
1.87 wiz 8408: for loading dynamic shared objects, that comes with libtool
8409: (libltdl), you should include devel/libltdl/buildlink3.mk.</p>
8410: <p>Some packages use libtool incorrectly so that the package
8411: may not work or build in some circumstances. Some of the more
8412: common errors are:</p>
1.148 asau 8413: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 8414: <li class="listitem">
1.75 rillig 8415: <p>The inclusion of a shared object (-module) as a dependent library in an
1.87 wiz 8416: executable or library. This in itself isn't a problem if one of two things
8417: has been done:</p>
1.128 wiz 8418: <div class="orderedlist"><ol class="orderedlist" type="1">
8419: <li class="listitem"><p>The shared object is named correctly, i.e.
1.87 wiz 8420: <code class="filename">libfoo.la</code>, not
8421: <code class="filename">foo.la</code></p></li>
1.128 wiz 8422: <li class="listitem"><p>The -dlopen option is used when linking an executable.</p></li>
1.75 rillig 8423: </ol></div>
8424: </li>
1.128 wiz 8425: <li class="listitem"><p>The use of libltdl without the correct calls to initialisation routines.
1.87 wiz 8426: The function lt_dlinit() should be called and the macro
8427: <code class="varname">LTDL_SET_PRELOADED_SYMBOLS</code> included in
8428: executables.</p></li>
1.75 rillig 8429: </ul></div>
8430: </div>
1.148 asau 8431: <div class="sect2">
1.75 rillig 8432: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8433: <a name="autoconf-automake"></a>21.3.3. GNU Autoconf/Automake</h3></div></div></div>
1.75 rillig 8434: <p>If a package needs GNU autoconf or automake to be executed
1.338 nia 8435: to regenerate the
8436: <code class="filename">configure</code>
8437: script and <code class="filename">Makefile.in</code> makefile
8438: templates from <code class="filename">configure.ac</code> and
8439: <code class="filename">Makefile.am</code>,
8440: then they should be executed in a pre-configure target:</p>
1.75 rillig 8441: <pre class="programlisting">
1.338 nia 8442: USE_TOOLS+= autoconf automake autoreconf
8443: GNU_CONFIGURE= yes
1.100 rillig 8444: ...
1.1 grant 8445:
1.100 rillig 8446: pre-configure:
1.338 nia 8447: set -e; cd ${WRKSRC} && autoreconf -fi
1.100 rillig 8448: ...
1.222 sevan 8449: </pre>
1.338 nia 8450: <p>Packages which use GNU Automake will sometimes
8451: require GNU Make (<code class="literal">gmake</code> in
8452: <code class="varname">USE_TOOLS</code>),
8453: but not always. Note that autoreconf
8454: only needs to be executed if <code class="filename">configure.ac</code>
8455: or Makefiles are modified, or <code class="filename">configure</code>
8456: is not present.</p>
1.75 rillig 8457: <p>There are times when the configure process makes
1.87 wiz 8458: additional changes to the generated files, which then causes
8459: the build process to try to re-execute the automake sequence.
8460: This is prevented by touching various files in the configure
8461: stage. If this causes problems with your package you can set
8462: <code class="varname">AUTOMAKE_OVERRIDE=NO</code> in the package
8463: Makefile.</p>
1.75 rillig 8464: </div>
1.338 nia 8465: <div class="sect2">
8466: <div class="titlepage"><div><div><h3 class="title">
8467: <a name="meson"></a>21.3.4. Meson / ninja</h3></div></div></div>
8468: <p>Packages using Meson to configure need to include:
8469:
8470: </p>
8471: <pre class="programlisting">
8472: .include "../../devel/meson/build.mk"
8473: </pre>
8474: <p>In nearly all cases (any program with dependencies),
8475: pkg-config needs to be added to
8476: <code class="varname">USE_TOOLS</code>. If the package installs
8477: translation files for non-English languages, also
8478: add msgfmt and xgettext:
8479:
8480: </p>
8481: <pre class="programlisting">
8482: USE_TOOLS+= pkg-config msgfmt xgettext
8483: </pre>
8484: <p>If any options need to be passed to Meson, use
8485: <code class="varname">MESON_ARGS</code> instead of
8486: <code class="varname">CONFIGURE_ARGS</code>:
8487:
8488: </p>
8489: <pre class="programlisting">
8490: MESON_ARGS+= -Dx11=false
8491: </pre>
8492: </div>
1.75 rillig 8493: </div>
1.148 asau 8494: <div class="sect1">
1.75 rillig 8495: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 8496: <a name="programming-languages"></a>21.4. Programming languages</h2></div></div></div>
1.148 asau 8497: <div class="sect2">
1.87 wiz 8498: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8499: <a name="basic-programming-languages"></a>21.4.1. C, C++, and Fortran</h3></div></div></div>
1.338 nia 8500: <p>Compilers for the C and C++ languages comes with
1.87 wiz 8501: the NetBSD base system. By default, pkgsrc assumes that a package
8502: is written in C and will hide all other compilers (via the wrapper
1.299 rillig 8503: framework, see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p>
1.87 wiz 8504: <p>To declare which language's compiler a package needs, set
8505: the <code class="varname">USE_LANGUAGES</code> variable. Allowed values
1.327 wiz 8506: currently are:
8507: </p>
8508: <pre class="programlisting">
8509: c99, c++, c++03, gnu++03, c++0x, gnu++0x, c++11, gnu++11,
8510: c++14, gnu++14, c++17, gnu++17, c++20, gnu++20, fortran,
8511: fortran77, java, objc, obj-c++, and ada.
8512: </pre>
8513: <p>
8514: (and any combination). The default is
1.128 wiz 8515: <span class="quote">“<span class="quote">c</span>”</span>. Packages using GNU configure scripts, even if
1.87 wiz 8516: written in C++, usually need a C compiler for the configure
8517: phase.</p>
1.338 nia 8518: <p>To express a general requirement on a specific C or C++
8519: version, normally only <code class="varname">GCC_REQD</code> needs to be set.
8520: For example, GCC 7 includes support for C++17, so if the package uses
8521: C++17 it should specify:
8522:
8523: </p>
8524: <pre class="programlisting">
8525: GCC_REQD+= 7
8526: </pre>
8527: <p>Language variants like <code class="literal">c++11</code> for
8528: <code class="varname">USE_LANGUAGES</code> should only be specified
8529: if the package does not explicitly set <code class="literal">-std=...</code>
8530: when compiling (i.e. the package assumes the compiler defaults to
8531: C++11 or some other standard). This is usually a bug in the
8532: upstream build system.</p>
8533: <p>GCC version 5 includes support for C++14, while GCC 4.7 includes
8534: more-or-less complete support for C++11. For more information, consult
8535: <a class="ulink" href="https://gcc.gnu.org/projects/cxx-status.html" target="_top">GCC's own documentation on programming language support.</a></p>
1.87 wiz 8536: </div>
1.148 asau 8537: <div class="sect2">
1.87 wiz 8538: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8539: <a name="java-programming-language"></a>21.4.2. Java</h3></div></div></div>
1.87 wiz 8540: <p>If a program is written in Java, use the Java framework in
8541: pkgsrc. The package must include
8542: <code class="filename">../../mk/java-vm.mk</code>. This Makefile fragment
8543: provides the following variables:</p>
1.148 asau 8544: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 8545: <li class="listitem"><p><code class="varname">USE_JAVA</code> defines if a build
1.87 wiz 8546: dependency on the JDK is added. If
1.128 wiz 8547: <code class="varname">USE_JAVA</code> is set to <span class="quote">“<span class="quote">run</span>”</span>, then
1.87 wiz 8548: there is only a runtime dependency on the JDK. The default is
1.128 wiz 8549: <span class="quote">“<span class="quote">yes</span>”</span>, which also adds a build dependency on the
1.87 wiz 8550: JDK.</p></li>
1.128 wiz 8551: <li class="listitem"><p>Set <code class="varname">USE_JAVA2</code> to declare that
1.87 wiz 8552: a package needs a Java2 implementation. The supported values
1.128 wiz 8553: are <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">1.4</span>”</span>, and
8554: <span class="quote">“<span class="quote">1.5</span>”</span>. <span class="quote">“<span class="quote">yes</span>”</span> accepts any Java2
8555: implementation, <span class="quote">“<span class="quote">1.4</span>”</span> insists on versions 1.4 or
8556: above, and <span class="quote">“<span class="quote">1.5</span>”</span> only accepts versions 1.5 or
1.87 wiz 8557: above. This variable is not set by default.</p></li>
1.130 wiz 8558: <li class="listitem"><p><code class="varname">PKG_JAVA_HOME</code> is
8559: automatically set to the runtime location of the used Java
8560: implementation dependency. It may be used to set
8561: <code class="varname">JAVA_HOME</code> to a good value if the program
8562: needs this variable to be defined.
8563: </p></li>
1.87 wiz 8564: </ul></div>
8565: </div>
1.148 asau 8566: <div class="sect2">
1.87 wiz 8567: <div class="titlepage"><div><div><h3 class="title">
1.320 wiz 8568: <a name="go-programming-language"></a>21.4.3. Go</h3></div></div></div>
8569: <p>If a program is written in Go and has any dependencies on
8570: other Go modules, have the package include
8571: <code class="filename">../../lang/go/go-module.mk</code>.</p>
8572: <div class="orderedlist"><ol class="orderedlist" type="1">
8573: <li class="listitem"><p>Generate a list of those dependencies with
8574: <span class="command"><strong>make clean && make patch && make show-go-modules >
8575: go-modules.mk</strong></span>.</p></li>
1.338 nia 8576: <li class="listitem"><p>Prepend
8577: <code class="literal">.include "go-modules.mk"</code> to any other
8578: <code class="literal">.include</code>s.</p></li>
8579: <li class="listitem"><p>Incorporate these modules in
8580: <code class="filename">distinfo</code> with <span class="command"><strong>make
8581: makesum</strong></span>.</p></li>
8582: </ol></div>
8583: </div>
8584: <div class="sect2">
8585: <div class="titlepage"><div><div><h3 class="title">
8586: <a name="rust-programming-language"></a>21.4.4. Rust</h3></div></div></div>
8587: <p>If a program is written in Rust and uses Cargo to build,
8588: have the package include
8589: <code class="filename">../../lang/rust/cargo.mk</code>.</p>
8590: <div class="orderedlist"><ol class="orderedlist" type="1">
8591: <li class="listitem"><p>Generate a list of those dependencies with
8592: <span class="command"><strong>make CARGO_ARGS="build --release" build &&
8593: make print-cargo-depends > cargo-depends.mk</strong></span>.</p></li>
8594: <li class="listitem"><p>Prepend
8595: <code class="literal">.include "cargo-depends.mk"</code> to any other
8596: <code class="literal">.include</code>s.</p></li>
1.320 wiz 8597: <li class="listitem"><p>Incorporate these modules in
8598: <code class="filename">distinfo</code> with <span class="command"><strong>make
8599: makesum</strong></span>.</p></li>
8600: </ol></div>
8601: </div>
8602: <div class="sect2">
8603: <div class="titlepage"><div><div><h3 class="title">
1.338 nia 8604: <a name="perl-scripts"></a>21.4.5. Packages containing Perl scripts</h3></div></div></div>
1.318 nia 8605: <p>If your package contains interpreted Perl scripts, add
1.128 wiz 8606: <span class="quote">“<span class="quote">perl</span>”</span> to the <code class="varname">USE_TOOLS</code> variable
1.87 wiz 8607: and set <code class="varname">REPLACE_PERL</code> to ensure that the proper
8608: interpreter path is set. <code class="varname">REPLACE_PERL</code> should
8609: contain a list of scripts, relative to <code class="varname">WRKSRC</code>,
1.183 wiz 8610: that you want adjusted. Every occurrence of
8611: <code class="filename">*/bin/perl</code> in a she-bang line will be
1.325 gutterid 8612: replaced with the full path to the Perl executable.</p>
8613: <p>If a particular version of Perl is needed, set the
1.87 wiz 8614: <code class="varname">PERL5_REQD</code> variable to the version number. The
1.128 wiz 8615: default is <span class="quote">“<span class="quote">5.0</span>”</span>.</p>
1.318 nia 8616: <p>See <a class="xref" href="#perl-modules" title="21.6.6. Packages installing Perl modules">Section 21.6.6, “Packages installing Perl modules”</a> for information
1.325 gutterid 8617: about handling Perl modules.</p>
8618: <p>There is also the <code class="varname">REPLACE_PERL6</code> variable
8619: for the language now known as Raku.</p>
1.87 wiz 8620: </div>
1.148 asau 8621: <div class="sect2">
1.87 wiz 8622: <div class="titlepage"><div><div><h3 class="title">
1.338 nia 8623: <a name="shell-scripts"></a>21.4.6. Packages containing shell scripts</h3></div></div></div>
1.147 wiz 8624: <p><code class="varname">REPLACE_SH</code>,
8625: <code class="varname">REPLACE_BASH</code>, <code class="varname">REPLACE_CSH</code>,
8626: and <code class="varname">REPLACE_KSH</code> can be used to replace shell
1.340 ! gutterid 8627: she-bangs in files. Please use the appropriate one, preferring
! 8628: <code class="varname">REPLACE_SH</code> when this shell is sufficient.
1.183 wiz 8629: Each should contain a list of scripts, relative to
8630: <code class="varname">WRKSRC</code>, that you want adjusted. Every
8631: occurrence of the matching shell in a she-bang line will be
8632: replaced with the full path to the shell executable.
1.147 wiz 8633: When using <code class="varname">REPLACE_BASH</code>, don't forget to add
8634: <code class="filename">bash</code> to <code class="varname">USE_TOOLS</code>.</p>
8635: </div>
1.148 asau 8636: <div class="sect2">
1.147 wiz 8637: <div class="titlepage"><div><div><h3 class="title">
1.338 nia 8638: <a name="other-programming-languages"></a>21.4.7. Other programming languages</h3></div></div></div>
1.325 gutterid 8639: <p>There are further similar REPLACE variables available, e.g.,
8640: <code class="varname">REPLACE_AWK</code> for packages containing awk scripts,
8641: and <code class="varname">REPLACE_R</code> for R. These two, like the others
1.326 gutterid 8642: noted above, have their actions defined centrally in
1.325 gutterid 8643: <code class="filename">mk/configure/replace-interpreter.mk</code>. Other
1.326 gutterid 8644: languages define the actions of these variables within their own
8645: dedicated part of the tree, e.g., <code class="varname">REPLACE_PHP</code> is
8646: actioned in <code class="filename">lang/php/phpversion.mk</code>, and
8647: <code class="varname">REPLACE_PYTHON</code> is actioned in
1.325 gutterid 8648: <code class="filename">lang/python/application.mk</code>. For other languages,
8649: consult the mk files found within their specific directories (the
1.331 gutterid 8650: naming convention varies), or check the list found in
8651: <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.325 gutterid 8652: <p>Currently, special handling for other languages varies
1.87 wiz 8653: in pkgsrc. If a compiler package provides a
8654: <code class="filename">buildlink3.mk</code> file, include that, otherwise
8655: just add a (build) dependency on the appropriate compiler
8656: package.</p>
8657: </div>
8658: </div>
1.148 asau 8659: <div class="sect1">
1.87 wiz 8660: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 8661: <a name="fixes.build"></a>21.5. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.77 rillig 8662: <p>The most common failures when building a package are that
8663: some platforms do not provide certain header files, functions or
8664: libraries, or they provide the functions in a library that the
8665: original package author didn't know. To work around this, you
8666: can rewrite the source code in most cases so that it does not
8667: use the missing functions or provides a replacement function.</p>
1.148 asau 8668: <div class="sect2">
1.77 rillig 8669: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8670: <a name="fixes.build.cpp"></a>21.5.1. Compiling C and C++ code conditionally</h3></div></div></div>
1.77 rillig 8671: <p>If a package already comes with a GNU configure script, the
8672: preferred way to fix the build failure is to change the
8673: configure script, not the code. In the other cases, you can
8674: utilize the C preprocessor, which defines certain macros
8675: depending on the operating system and hardware architecture it
8676: compiles for. These macros can be queried using for example
8677: <code class="varname">#if defined(__i386)</code>. Almost every operating
8678: system, hardware architecture and compiler has its own macro.
8679: For example, if the macros <code class="varname">__GNUC__</code>,
8680: <code class="varname">__i386__</code> and <code class="varname">__NetBSD__</code>
8681: are all defined, you know that you are using NetBSD on an i386
8682: compatible CPU, and your compiler is GCC.</p>
8683: <p>The list of the following macros for hardware and
8684: operating system depends on the compiler that is used. For
8685: example, if you want to conditionally compile code on Solaris,
8686: don't use <code class="varname">__sun__</code>, as the SunPro compiler
8687: does not define it. Use <code class="varname">__sun</code> instead.</p>
1.148 asau 8688: <div class="sect3">
1.75 rillig 8689: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 8690: <a name="fixes.build.cpp.os"></a>21.5.1.1. C preprocessor macros to identify the operating system</h4></div></div></div>
1.338 nia 8691: <p>To distinguish between specific NetBSD versions,
8692: you should use the following code.</p>
8693: <pre class="programlisting">
8694: #ifdef __NetBSD__
8695: #include <sys/param.h>
8696: #if __NetBSD_Prereq__(9,99,17)
8697: /* use a newer feature */
8698: #else
8699: /* older code */
8700: #endif
8701: #endif
8702:
8703: #ifndef _WIN32
8704: /* Unix-like specific code */
8705: #endif
8706: </pre>
1.75 rillig 8707: <p>To distinguish between 4.4 BSD-derived systems and the
8708: rest of the world, you should use the following code.</p>
8709: <pre class="programlisting">
1.100 rillig 8710: #include <sys/param.h>
8711: #if (defined(BSD) && BSD >= 199306)
8712: /* BSD-specific code goes here */
8713: #else
8714: /* non-BSD-specific code goes here */
8715: #endif
1.75 rillig 8716: </pre>
1.338 nia 8717: <p>You can also test for the following macros:</p>
1.75 rillig 8718: <pre class="programlisting">
1.151 obache 8719: Cygwin __CYGWIN__
8720: DragonFly __DragonFly__
1.100 rillig 8721: FreeBSD __FreeBSD__
1.151 obache 8722: Haiku __HAIKU__
1.100 rillig 8723: Interix __INTERIX
8724: IRIX __sgi (TODO: get a definite source for this)
1.338 nia 8725: Linux __linux
1.193 dholland 8726: Mac OS X __APPLE__
1.151 obache 8727: MirBSD __MirBSD__ (__OpenBSD__ is also defined)
8728: Minix3 __minix
1.100 rillig 8729: NetBSD __NetBSD__
8730: OpenBSD __OpenBSD__
8731: Solaris sun, __sun
1.75 rillig 8732: </pre>
8733: </div>
1.148 asau 8734: <div class="sect3">
1.75 rillig 8735: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 8736: <a name="fixes.build.cpp.arch"></a>21.5.1.2. C preprocessor macros to identify the hardware architecture</h4></div></div></div>
1.75 rillig 8737: <pre class="programlisting">
1.100 rillig 8738: i386 i386, __i386, __i386__
1.338 nia 8739: x86-64 __amd64__, __x86_64__
8740: ARM __arm__
1.100 rillig 8741: MIPS __mips
8742: SPARC sparc, __sparc
1.338 nia 8743: PowerPC __powerpc
1.75 rillig 8744: </pre>
8745: </div>
1.148 asau 8746: <div class="sect3">
1.75 rillig 8747: <div class="titlepage"><div><div><h4 class="title">
1.267 rillig 8748: <a name="fixes.build.cpp.compiler"></a>21.5.1.3. C preprocessor macros to identify the compiler</h4></div></div></div>
1.75 rillig 8749: <pre class="programlisting">
1.100 rillig 8750: GCC __GNUC__ (major version), __GNUC_MINOR__
8751: MIPSpro _COMPILER_VERSION (0x741 for MIPSpro 7.41)
8752: SunPro __SUNPRO_C (0x570 for Sun C 5.7)
8753: SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8)
1.75 rillig 8754: </pre>
8755: </div>
8756: </div>
1.148 asau 8757: <div class="sect2">
1.78 rillig 8758: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 8759: <a name="compiler-bugs"></a>21.5.2. How to handle compiler bugs</h3></div></div></div>
1.78 rillig 8760: <p>Some source files trigger bugs in the compiler, based on
1.87 wiz 8761: combinations of compiler version and architecture and almost
8762: always relation to optimisation being enabled. Common symptoms
8763: are gcc internal errors or never finishing compiling a
1.78 rillig 8764: file.</p>
8765: <p>Typically, a workaround involves testing the
8766: <code class="varname">MACHINE_ARCH</code> and compiler version, disabling
8767: optimisation for that combination of file,
1.198 tnn 8768: <code class="varname">MACHINE_ARCH</code> and compiler.</p>
8769: <p>This used to be a big problem in the past, but is rarely
8770: needed now as compiler technology has matured. If you still need
8771: to add a compiler specific workaround, please do so in the file
8772: <code class="filename">hacks.mk</code> and describe the symptom and
8773: compiler version as detailed as possible.</p>
1.78 rillig 8774: </div>
1.148 asau 8775: <div class="sect2">
1.78 rillig 8776: <div class="titlepage"><div><div><h3 class="title">
1.287 rillig 8777: <a name="fixes.build.header"></a>21.5.3. No such file or directory</h3></div></div></div>
8778: <p>Compilation sometimes fails with an error message like this:</p>
8779: <pre class="programlisting">
8780: .../x11/gtk3/work/gtk+-3.24.12/gdk/gdktypes.h:35:10:
8781: fatal error: pango/pango.h: No such file or directory
8782: </pre>
8783: <p>The proper way to fix this problem depends on the type of the
8784: header, which is described in the following sections.</p>
8785: <div class="sect3">
8786: <div class="titlepage"><div><div><h4 class="title">
8787: <a name="fixes.build.header.bl3"></a>21.5.3.1. Headers from other packages</h4></div></div></div>
8788: <p>If the header name looks like it comes from a different package,
8789: that other package should be included via the buildlink3
8790: framework.</p>
8791: <p>First, look whether the header is somewhere in the buildlink3
8792: directory below <code class="varname">WRKDIR</code>. In the above case of
8793: the missing Pango header:</p>
8794: <pre class="programlisting">
8795: <code class="prompt">$</code> find work/.buildlink/ -print | grep -F pango/pango.h
8796: </pre>
8797: <p>In the case of Pango, the output is:</p>
8798: <pre class="programlisting">
8799: work/.buildlink/include/pango-1.0/pango/pango.h
8800: </pre>
8801: <p>If the <code class="filename">pango/pango.h</code> file were placed directly
8802: in the <code class="filename">.buildlink</code> directory, it would have been
8803: found automatically. There is an extra <code class="filename">pango-1.0</code>
8804: path component though, which means that the compiler command line must
8805: contain an option of the form
8806: <code class="literal">-I${BUILDLINK3_PREFIX.pango}/include/pango-1.0</code>. In
8807: most cases this option is generated by the configure script, which can be examined using:</p>
8808: <pre class="programlisting">
8809: <code class="prompt">$</code> $ grep -o '[-]I[^[:space:]]*/pango[^[:space:]]*' work/*/Makefile
8810: -I/usr/pkg/include/pango-1.0
8811: -I/usr/pkg/include/pango-1.0
8812: -I/usr/pkg/include/pango-1.0
8813: -I/usr/pkg/include/pango-1.0
8814: -I/usr/pkg/include/pango-1.0
8815: </pre>
8816: <p>This looks good. These options are transformed by the buildlink
8817: wrapper to refer to the correct path inside
8818: <code class="filename">work/.buildlink</code>.</p>
8819: <p>Since the compilation fails though, examine the compiler command
8820: lines in <code class="filename">work/.work.log</code> to see whether the
8821: <code class="literal">-I</code> option is included in the particular command
8822: line.</p>
8823: <p>To further analyze the situation, run <span class="command"><strong>bmake
8824: build-env</strong></span>, which sets up an interactive, realistic environment
8825: including all the pkgsrc wrapper commands and environment variables. From
8826: there, try to compile some simple example programs that use the
8827: header.</p>
8828: </div>
8829: <div class="sect3">
8830: <div class="titlepage"><div><div><h4 class="title">
8831: <a name="fixes.build.header.gen"></a>21.5.3.2. Headers generated during the build</h4></div></div></div>
8832: <p>If the name of the header seems to come from the package itself,
8833: and if the build is run with parallel jobs, the package may have some
8834: undeclared dependencies between the <code class="filename">.c</code> and the
8835: <code class="filename">.h</code> files, and a C file is compiled before its
8836: required header is generated.</p>
8837: <p>To see whether the build runs with parallel jobs, run
8838: <span class="command"><strong>bmake show-all-build | grep JOBS</strong></span>. Its output looks
8839: like this:</p>
8840: <pre class="programlisting">
8841: usr MAKE_JOBS= 7
8842: pkg MAKE_JOBS_SAFE # undefined
8843: def _MAKE_JOBS_N= 7
8844: </pre>
8845: <p>In this case the pkgsrc user has asked pkgsrc to build packages
8846: with 7 jobs in parallel (<code class="varname">MAKE_JOBS</code>). The
8847: package could have disabled parallel builds by setting
8848: <code class="varname">MAKE_JOBS_SAFE</code> to <code class="literal">no</code>, but
8849: in this case it hasn't.</p>
8850: <p>To see whether the build failure is caused by parallel builds,
8851: first save the exact error message and a bit of context, maybe you need
8852: it later for reporting a bug. Next, run:</p>
8853: <pre class="programlisting">
8854: MAKE_JOBS_SAFE=no bmake clean build
8855: </pre>
8856: <p>If that succeeds, <a class="ulink" href="https://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd" target="_top">file a bug
8857: report</a> against the pkgsrc package, including the exact error
8858: message and the contents of your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file.</p>
8859: </div>
1.288 rillig 8860: <div class="sect3">
8861: <div class="titlepage"><div><div><h4 class="title">
8862: <a name="fixes.build.header.symlink"></a>21.5.3.3. Symlinks</h4></div></div></div>
8863: <p>Pkgsrc does not work reliably if any of
8864: <code class="varname">LOCALBASE</code>, <code class="varname">VARBASE</code> or
8865: <code class="varname">WRKDIR</code> contains a symlink. Since 2019Q2, the pkgsrc
8866: bootstrap program prevents installing pkgsrc in symlink-based
8867: directories. Existing pkgsrc installations are not checked for symlinks
8868: though.</p>
8869: <p>The "No such file or directory" error messages are a typical
8870: symptom of symlinks, and it's quite difficult to find out that this is
8871: the actual cause.</p>
8872: </div>
8873: <div class="sect3">
8874: <div class="titlepage"><div><div><h4 class="title">
8875: <a name="fixes.build.header.stale"></a>21.5.3.4. Stale working directories</h4></div></div></div>
8876: <p>When building a hierarchy of packages, it may happen that one
8877: package is built and then pkgsrc is updated. This situation can provoke
8878: various hard to diagnose build errors. To clean up the situation:</p>
8879: <pre class="programlisting">
1.338 nia 8880: <code class="prompt">$</code> (cd ../../ && cat mk/bsd.pkg.mk >/dev/null && rm -rf */*/work)
1.288 rillig 8881: </pre>
1.338 nia 8882: <p>(The only purpose of the <code class="filename">bsd.pkg.mk</code> is to
8883: prevent running this command in the wrong directory.)</p>
1.288 rillig 8884: <p>If you have set <code class="varname">WRKOBJDIR</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, remove
8885: that directory as well.</p>
8886: </div>
8887: <div class="sect3">
8888: <div class="titlepage"><div><div><h4 class="title">
8889: <a name="fixes.build.header.misc"></a>21.5.3.5. Other possible reasons</h4></div></div></div>
8890: <p>On platforms other than BSD, third-party packages are installed in
8891: <code class="filename">/usr/include</code>, together with the base system. This
8892: means that pkgsrc cannot distinguish between headers provided by the base
8893: system (which it needs) and headers from third-party packages (which are
8894: often included in pkgsrc as well). This can lead to subtle version
8895: mismatches.</p>
8896: <p>In pkgsrc installations that have been active for several years, it
8897: may happen that some files are manually deleted. To exclude this unlikely
8898: reason, run <span class="command"><strong>pkg_admin check</strong></span>.</p>
8899: <p>It may help to run <span class="command"><strong>pkg_admin rebuild-tree</strong></span> to
8900: check/fix dependencies.</p>
8901: <p>If all of the above doesn't help, see <a class="xref" href="#help-user" title="Chapter 2. Getting help">Chapter 2, <i>Getting help</i></a>
8902: for contact information. Be prepared to describe what you have tried so
8903: far and what any error messages were.</p>
8904: </div>
1.287 rillig 8905: </div>
8906: <div class="sect2">
8907: <div class="titlepage"><div><div><h3 class="title">
8908: <a name="undefined-reference"></a>21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span>
1.128 wiz 8909: </h3></div></div></div>
1.92 rillig 8910: <p>This error message often means that a package did not
1.78 rillig 8911: link to a shared library it needs. The following functions are
8912: known to cause this error message over and over.</p>
8913: <div class="informaltable">
1.216 tnn 8914: <a name="undefined-reference-functions"></a><table class="informaltable" border="1">
1.78 rillig 8915: <colgroup>
8916: <col>
8917: <col>
8918: <col>
8919: </colgroup>
8920: <thead><tr>
8921: <th>Function</th>
8922: <th>Library</th>
8923: <th>Affected platforms</th>
8924: </tr></thead>
8925: <tbody>
8926: <tr>
8927: <td>accept, bind, connect</td>
8928: <td>-lsocket</td>
8929: <td>Solaris</td>
8930: </tr>
8931: <tr>
8932: <td>crypt</td>
8933: <td>-lcrypt</td>
8934: <td>DragonFly, NetBSD</td>
8935: </tr>
8936: <tr>
8937: <td>dlopen, dlsym</td>
8938: <td>-ldl</td>
8939: <td>Linux</td>
8940: </tr>
8941: <tr>
8942: <td>gethost*</td>
8943: <td>-lnsl</td>
8944: <td>Solaris</td>
8945: </tr>
8946: <tr>
8947: <td>inet_aton</td>
8948: <td>-lresolv</td>
8949: <td>Solaris</td>
8950: </tr>
8951: <tr>
8952: <td>nanosleep, sem_*, timer_*</td>
8953: <td>-lrt</td>
8954: <td>Solaris</td>
8955: </tr>
8956: <tr>
8957: <td>openpty</td>
8958: <td>-lutil</td>
8959: <td>Linux</td>
8960: </tr>
8961: </tbody>
8962: </table>
8963: </div>
1.338 nia 8964: <p>To fix these linker errors, it is often sufficient to add
1.87 wiz 8965: <code class="literal">LIBS.<em class="replaceable"><code>OperatingSystem</code></em>+=
8966: -l<em class="replaceable"><code>foo</code></em></code> to the package
1.338 nia 8967: <code class="filename">Makefile</code> and then run <span class="command"><strong>bmake clean;
1.87 wiz 8968: bmake</strong></span>.</p>
1.148 asau 8969: <div class="sect3">
1.92 rillig 8970: <div class="titlepage"><div><div><h4 class="title">
1.338 nia 8971: <a name="undefined-reference-sunpro"></a>21.5.4.1. The SunPro compiler and inline functions</h4></div></div></div>
1.92 rillig 8972: <p>When you are using the SunPro compiler, there is another
8973: possibility. That compiler cannot handle the following code:</p>
8974: <pre class="programlisting">
1.100 rillig 8975: extern int extern_func(int);
1.93 rillig 8976:
1.100 rillig 8977: static inline int
8978: inline_func(int x)
8979: {
1.92 rillig 8980: return extern_func(x);
1.100 rillig 8981: }
1.93 rillig 8982:
1.100 rillig 8983: int main(void)
8984: {
1.92 rillig 8985: return 0;
1.100 rillig 8986: }
1.92 rillig 8987: </pre>
8988: <p>It generates the code for <code class="function">inline_func</code> even if
8989: that function is never used. This code then refers to
8990: <code class="function">extern_func</code>, which can usually not be resolved. To
8991: solve this problem you can try to tell the package to disable inlining
8992: of functions.</p>
8993: </div>
1.87 wiz 8994: </div>
1.148 asau 8995: <div class="sect2">
1.87 wiz 8996: <div class="titlepage"><div><div><h3 class="title">
1.287 rillig 8997: <a name="out-of-memory"></a>21.5.5. Running out of memory</h3></div></div></div>
1.87 wiz 8998: <p>Sometimes packages fail to build because the compiler runs
8999: into an operating system specific soft limit. With the
9000: <code class="varname">UNLIMIT_RESOURCES</code> variable pkgsrc can be told
1.338 nia 9001: to unlimit the resources. The allowed values are any combination of
9002: <span class="quote">“<span class="quote">cputime</span>”</span>,
9003: <span class="quote">“<span class="quote">datasize</span>”</span>,
9004: <span class="quote">“<span class="quote">memorysize</span>”</span>,
9005: <span class="quote">“<span class="quote">stacksize</span>”</span> and
9006: <span class="quote">“<span class="quote">virtualsize</span>”</span>.
1.87 wiz 9007: Setting this variable is similar to running the shell builtin
1.110 hubertf 9008: <span class="command"><strong>ulimit</strong></span> command to raise the maximum data
1.87 wiz 9009: segment size or maximum stack size of a process, respectively, to
9010: their hard limits.</p>
1.78 rillig 9011: </div>
1.75 rillig 9012: </div>
1.148 asau 9013: <div class="sect1">
1.75 rillig 9014: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9015: <a name="fixes.install"></a>21.6. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
1.148 asau 9016: <div class="sect2">
1.75 rillig 9017: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9018: <a name="install-scripts"></a>21.6.1. Creating needed directories</h3></div></div></div>
1.110 hubertf 9019: <p>The BSD-compatible <span class="command"><strong>install</strong></span> supplied
1.87 wiz 9020: with some operating systems cannot create more than one
9021: directory at a time. As such, you should call
9022: <code class="literal">${INSTALL_*_DIR}</code> like this:</p>
9023: <pre class="programlisting">
1.100 rillig 9024: ${INSTALL_DATA_DIR} ${PREFIX}/dir1
9025: ${INSTALL_DATA_DIR} ${PREFIX}/dir2
1.222 sevan 9026: </pre>
1.338 nia 9027: <p>Instead of running the <span class="command"><strong>install</strong></span> commands
9028: directly, you can also append <span class="quote">“<span class="quote"><code class="literal">dir1
9029: dir2</code></span>”</span> to the <code class="varname">INSTALLATION_DIRS</code>
9030: variable, which will automatically do the right thing.</p>
1.75 rillig 9031: </div>
1.148 asau 9032: <div class="sect2">
1.75 rillig 9033: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9034: <a name="where-to-install-documentation"></a>21.6.2. Where to install documentation</h3></div></div></div>
1.83 wiz 9035: <p>In general, documentation should be installed into
1.87 wiz 9036: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
1.338 nia 9037: <code class="filename">${PREFIX}/share/doc/${PKGNAME_NOREV}</code> (the latter
1.87 wiz 9038: includes the version number of the package).</p>
1.84 wiz 9039: <p>Many modern packages using GNU autoconf allow to set the
1.87 wiz 9040: directory where HTML documentation is installed with the
1.338 nia 9041: <span class="quote">“<span class="quote">--with-html-dir</span>”</span> option. Sometimes using this flag is
9042: needed because otherwise the documentation ends up in
9043: <code class="filename">${PREFIX}/share/doc/html</code> or other places. In
9044: pkgsrc, the HTML documentation should go into the package-specific
9045: directory, just like any other documentation.</p>
1.87 wiz 9046: <p>An exception to the above is that library API documentation
1.322 leot 9047: generated with the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/textproc/gtk-doc/index.html" target="_top"><code class="filename">textproc/gtk-doc</code></a> tools, for use by special
1.87 wiz 9048: browsers (devhelp) should be left at their default location, which
9049: is <code class="filename">${PREFIX}/share/gtk-doc</code>. Such
9050: documentation can be recognized from files ending in
9051: <code class="filename">.devhelp</code> or <code class="filename">.devhelp2</code>.
9052: (It is also acceptable to install such files in
9053: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
9054: <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code>; the
9055: <code class="filename">.devhelp*</code> file must be directly in that
9056: directory then, no additional subdirectory level is allowed in
9057: this case. This is usually achieved by using
1.128 wiz 9058: <span class="quote">“<span class="quote">--with-html-dir=${PREFIX}/share/doc</span>”</span>.
1.87 wiz 9059: <code class="filename">${PREFIX}/share/gtk-doc</code> is preferred
9060: though.)</p>
1.75 rillig 9061: </div>
1.148 asau 9062: <div class="sect2">
1.75 rillig 9063: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9064: <a name="installing-score-files"></a>21.6.3. Installing highscore files</h3></div></div></div>
1.75 rillig 9065: <p>Certain packages, most of them in the games category, install
1.87 wiz 9066: a score file that allows all users on the system to record their
9067: highscores. In order for this to work, the binaries need to be
9068: installed setgid and the score files owned by the appropriate
1.142 wiz 9069: group and/or owner (traditionally the "games" user/group). Set
9070: <code class="varname">USE_GAMESGROUP</code> to yes to support this. The
1.87 wiz 9071: following variables, documented in more detail in
9072: <code class="filename">mk/defaults/mk.conf</code>, control this
1.142 wiz 9073: behaviour: <code class="varname">GAMEDATAMODE</code>,
9074: <code class="varname">GAMEDIRMODE</code>, <code class="varname">GAMES_GROUP</code>,
1.210 leot 9075: <code class="varname">GAMEMODE</code>, <code class="varname">GAME_USER</code>.
9076: Other useful variables are: <code class="varname">GAMEDIR_PERMS</code>,
9077: <code class="varname">GAMEDATA_PERMS</code> and
9078: <code class="varname">SETGID_GAMES_PERMS</code>.</p>
9079: <p>An example that illustrates some of the variables described above is
9080: <code class="filename">games/moon-buggy</code>. <code class="varname">OWN_DIRS_PERMS</code> is
9081: used to properly set directory permissions of the directory where the
9082: scorefile is saved, <code class="varname">REQD_FILES_PERMS</code> is used to create a
9083: dummy scorefile (<code class="filename">mbscore</code>) with the proper permissions
9084: and <code class="varname">SPECIAL_PERMS</code> is used to install setgid the game
9085: binary:</p>
9086: <pre class="programlisting">
1.223 rillig 9087: USE_GAMESGROUP= yes
1.210 leot 9088:
1.223 rillig 9089: BUILD_DEFS+= VARBASE
1.210 leot 9090:
1.223 rillig 9091: OWN_DIRS_PERMS+= ${VARBASE}/games/moon-buggy ${GAMEDIR_PERMS}
9092: REQD_FILES_PERMS+= /dev/null ${VARBASE}/games/moon-buggy/mbscore ${GAMEDATA_PERMS}
9093: SPECIAL_PERMS+= ${PREFIX}/bin/moon-buggy ${SETGID_GAMES_PERMS}
1.222 sevan 9094: </pre>
1.210 leot 9095: <p>Various <code class="varname">INSTALL_*</code> variables are also available:
9096: <code class="varname">INSTALL_GAME</code> to install setgid game binaries,
9097: <code class="varname">INSTALL_GAME_DIR</code> to install game directories that are
9098: needed to be accessed by setgid games and
9099: <code class="varname">INSTALL_GAME_DATA</code> to install scorefiles.</p>
1.114 jmcneill 9100: <p>A package should therefore never hard code file ownership or
1.210 leot 9101: access permissions but rely on <code class="varname">*_PERMS</code> as described above
9102: or alternatively on <code class="varname">INSTALL_GAME</code>,
9103: <code class="varname">INSTALL_GAME_DATA</code> and
9104: <code class="varname">INSTALL_GAME_DIR</code> to set these correctly.</p>
1.75 rillig 9105: </div>
1.148 asau 9106: <div class="sect2">
1.75 rillig 9107: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9108: <a name="destdir-support"></a>21.6.4. Adding DESTDIR support to packages</h3></div></div></div>
1.114 jmcneill 9109: <p><code class="varname">DESTDIR</code> support means that a package
9110: installs into a staging directory, not the final location of the
9111: files. Then a binary package is created which can be used for
9112: installation as usual. There are two ways: Either the package must
1.128 wiz 9113: install as root (<span class="quote">“<span class="quote">destdir</span>”</span>) or the package can
9114: install as non-root user (<span class="quote">“<span class="quote">user-destdir</span>”</span>).</p>
1.148 asau 9115: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 9116: <li class="listitem"><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be
1.224 leot 9117: set to <span class="quote">“<span class="quote">destdir</span>”</span> or <span class="quote">“<span class="quote">user-destdir</span>”</span>.
9118: By default <code class="varname">PKG_DESTDIR_SUPPORT</code>
1.145 wiz 9119: is set to <span class="quote">“<span class="quote">user-destdir</span>”</span> to help catching more
9120: potential packaging problems. If bsd.prefs.mk is included in the Makefile,
1.114 jmcneill 9121: <code class="varname">PKG_DESTDIR_SUPPORT</code> needs to be set before
9122: the inclusion.</p></li>
1.128 wiz 9123: <li class="listitem"><p>All installation operations have to be prefixed with
1.103 wiz 9124: <code class="filename">${DESTDIR}</code>.</p></li>
1.128 wiz 9125: <li class="listitem"><p>automake gets this DESTDIR mostly right
1.103 wiz 9126: automatically. Many manual rules and pre/post-install often are
9127: incorrect; fix them.</p></li>
1.128 wiz 9128: <li class="listitem"><p>If files are installed with special owner/group
1.118 imil 9129: use <code class="varname">SPECIAL_PERMS</code>.</p></li>
1.128 wiz 9130: <li class="listitem"><p>In general, packages should support
1.103 wiz 9131: <code class="varname">UNPRIVILEGED</code> to be able to use
9132: DESTDIR.</p></li>
9133: </ul></div>
9134: </div>
1.148 asau 9135: <div class="sect2">
1.103 wiz 9136: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9137: <a name="hardcoded-paths"></a>21.6.5. Packages with hardcoded paths to other interpreters</h3></div></div></div>
1.87 wiz 9138: <p>Your package may also contain scripts with hardcoded paths to
1.318 nia 9139: other interpreters besides (or as well as) Perl. To correct the
1.87 wiz 9140: full pathname to the script interpreter, you need to set the
9141: following definitions in your <code class="filename">Makefile</code> (we
1.110 hubertf 9142: shall use <span class="command"><strong>tclsh</strong></span> in this example):</p>
1.87 wiz 9143: <pre class="programlisting">
1.100 rillig 9144: REPLACE_INTERPRETER+= tcl
9145: REPLACE.tcl.old= .*/bin/tclsh
9146: REPLACE.tcl.new= ${PREFIX}/bin/tclsh
9147: REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed,
9148: # relative to ${WRKSRC}, just as in REPLACE_PERL
1.222 sevan 9149: </pre>
1.75 rillig 9150: </div>
1.148 asau 9151: <div class="sect2">
1.75 rillig 9152: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9153: <a name="perl-modules"></a>21.6.6. Packages installing Perl modules</h3></div></div></div>
1.75 rillig 9154: <p>Makefiles of packages providing perl5 modules should include
1.87 wiz 9155: the Makefile fragment
9156: <code class="filename">../../lang/perl5/module.mk</code>. It provides a
1.110 hubertf 9157: <span class="command"><strong>do-configure</strong></span> target for the standard perl
1.87 wiz 9158: configuration for such modules as well as various hooks to tune
9159: this configuration. See comments in this file for
9160: details.</p>
1.75 rillig 9161: <p>Perl5 modules will install into different places depending
1.87 wiz 9162: on the version of perl used during the build process. To
9163: address this, pkgsrc will append lines to the
9164: <code class="filename">PLIST</code> corresponding to the files listed in
9165: the installed <code class="filename">.packlist</code> file generated by
9166: most perl5 modules. This is invoked by defining
9167: <code class="varname">PERL5_PACKLIST</code> to a space-separated list of
1.153 wiz 9168: packlist files relative to <code class="varname">PERL5_PACKLIST_DIR</code>
9169: (<code class="varname">PERL5_INSTALLVENDORARCH</code> by default),
9170: e.g.:</p>
1.75 rillig 9171: <pre class="programlisting">
1.153 wiz 9172: PERL5_PACKLIST= auto/Pg/.packlist
1.222 sevan 9173: </pre>
1.153 wiz 9174: <p>The perl5 config variables
9175: <code class="varname">installarchlib</code>,
9176: <code class="varname">installscript</code>,
9177: <code class="varname">installvendorbin</code>,
9178: <code class="varname">installvendorscript</code>,
9179: <code class="varname">installvendorarch</code>,
9180: <code class="varname">installvendorlib</code>,
9181: <code class="varname">installvendorman1dir</code>, and
9182: <code class="varname">installvendorman3dir</code> represent those
9183: locations in which components of perl5 modules may be installed,
9184: provided as variable with uppercase and prefixed with
9185: <code class="varname">PERL5_</code>, e.g. <code class="varname">PERL5_INSTALLARCHLIB</code>
9186: and may be used by perl5 packages that don't have a packlist.
9187: These variables are also substituted for in the
9188: <code class="filename">PLIST</code> as uppercase prefixed with
9189: <code class="varname">PERL5_SUB_</code>.</p>
1.75 rillig 9190: </div>
1.148 asau 9191: <div class="sect2">
1.75 rillig 9192: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9193: <a name="faq.info-files"></a>21.6.7. Packages installing info files</h3></div></div></div>
1.75 rillig 9194: <p>Some packages install info files or use the
1.128 wiz 9195: <span class="quote">“<span class="quote">makeinfo</span>”</span> or <span class="quote">“<span class="quote">install-info</span>”</span>
1.87 wiz 9196: commands. <code class="varname">INFO_FILES</code> should be defined in
9197: the package Makefile so that <code class="filename">INSTALL</code> and
9198: <code class="filename">DEINSTALL</code> scripts will be generated to
9199: handle registration of the info files in the Info directory
1.128 wiz 9200: file. The <span class="quote">“<span class="quote">install-info</span>”</span> command used for the info
1.87 wiz 9201: files registration is either provided by the system, or by a
9202: special purpose package automatically added as dependency if
9203: needed.</p>
1.75 rillig 9204: <p><code class="varname">PKGINFODIR</code> is the directory under
1.87 wiz 9205: <code class="filename">${PREFIX}</code> where info files are primarily
9206: located. <code class="varname">PKGINFODIR</code> defaults to
1.128 wiz 9207: <span class="quote">“<span class="quote">info</span>”</span> and can be overridden by the user.</p>
1.75 rillig 9208: <p>The info files for the package should be listed in the
1.87 wiz 9209: package <code class="filename">PLIST</code>; however any split info files
9210: need not be listed.</p>
1.128 wiz 9211: <p>A package which needs the <span class="quote">“<span class="quote">makeinfo</span>”</span> command
9212: at build time must add <span class="quote">“<span class="quote">makeinfo</span>”</span> to
1.87 wiz 9213: <code class="varname">USE_TOOLS</code> in its Makefile. If a minimum
1.128 wiz 9214: version of the <span class="quote">“<span class="quote">makeinfo</span>”</span> command is needed it
1.87 wiz 9215: should be noted with the <code class="varname">TEXINFO_REQD</code>
9216: variable in the package <code class="filename">Makefile</code>. By
9217: default, a minimum version of 3.12 is required. If the system
1.110 hubertf 9218: does not provide a <span class="command"><strong>makeinfo</strong></span> command or if it
1.87 wiz 9219: does not match the required minimum, a build dependency on the
1.322 leot 9220: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/gtexinfo/index.html" target="_top"><code class="filename">devel/gtexinfo</code></a> package will
1.87 wiz 9221: be added automatically.</p>
1.75 rillig 9222: <p>The build and installation process of the software provided
1.87 wiz 9223: by the package should not use the
1.110 hubertf 9224: <span class="command"><strong>install-info</strong></span> command as the registration of
1.87 wiz 9225: info files is the task of the package
9226: <code class="filename">INSTALL</code> script, and it must use the
1.110 hubertf 9227: appropriate <span class="command"><strong>makeinfo</strong></span> command.</p>
1.75 rillig 9228: <p>To achieve this goal, the pkgsrc infrastructure creates
1.110 hubertf 9229: overriding scripts for the <span class="command"><strong>install-info</strong></span> and
9230: <span class="command"><strong>makeinfo</strong></span> commands in a directory listed early
1.87 wiz 9231: in <code class="varname">PATH</code>.</p>
1.110 hubertf 9232: <p>The script overriding <span class="command"><strong>install-info</strong></span> has
1.87 wiz 9233: no effect except the logging of a message. The script overriding
1.110 hubertf 9234: <span class="command"><strong>makeinfo</strong></span> logs a message and according to the
1.87 wiz 9235: value of <code class="varname">TEXINFO_REQD</code> either runs the appropriate
1.110 hubertf 9236: <span class="command"><strong>makeinfo</strong></span> command or exit on error.</p>
1.75 rillig 9237: </div>
1.148 asau 9238: <div class="sect2">
1.75 rillig 9239: <div class="titlepage"><div><div><h3 class="title">
1.267 rillig 9240: <a name="manpages"></a>21.6.8. Packages installing man pages</h3></div></div></div>
1.81 rillig 9241: <p>All packages that install manual pages should install them
1.87 wiz 9242: into the same directory, so that there is one common place to look
9243: for them. In pkgsrc, this place is
9244: <code class="literal">${PREFIX}/${PKGMANDIR}</code>, and this expression
9245: should be used in packages. The default for
9246: <code class="varname">PKGMANDIR</code> is
1.128 wiz 9247: <span class="quote">“<span class="quote"><code class="filename">man</code></span>”</span>. Another often-used value
9248: is <span class="quote">“<span class="quote"><code class="filename">share/man</code></span>”</span>.</p>
1.148 asau 9249: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.75 rillig 9250: <h3 class="title">Note</h3>
1.87 wiz 9251: <p>The support for a custom <code class="varname">PKGMANDIR</code>
9252: is far from complete.</p>
1.75 rillig 9253: </div>
1.81 rillig 9254: <p>The <code class="filename">PLIST</code> files can just use
1.87 wiz 9255: <code class="filename">man/</code> as the top level directory for the man
9256: page file entries, and the pkgsrc framework will convert as
9257: needed. In all other places, the correct
9258: <code class="varname">PKGMANDIR</code> must be used.</p>
9259: <p>Packages that are
9260: configured with <code class="varname">GNU_CONFIGURE</code> set as
1.128 wiz 9261: <span class="quote">“<span class="quote">yes</span>”</span>, by default will use the
1.87 wiz 9262: <code class="filename">./configure</code>
9263: --mandir switch to set where the man pages should be installed.
9264: The path is <code class="varname">GNU_CONFIGURE_MANDIR</code> which defaults
9265: to <code class="varname">${PREFIX}/${PKGMANDIR}</code>.</p>
9266: <p>Packages that use <code class="varname">GNU_CONFIGURE</code> but do not
9267: use --mandir, can set <code class="varname">CONFIGURE_HAS_MANDIR</code>
1.128 wiz 9268: to <span class="quote">“<span class="quote">no</span>”</span>.
1.87 wiz 9269: Or if the <code class="filename">./configure</code> script uses
9270: a non-standard use of --mandir, you can set
9271: <code class="varname">GNU_CONFIGURE_MANDIR</code> as needed.</p>
1.299 rillig 9272: <p>See <a class="xref" href="#manpage-compression" title="19.5. Man page compression">Section 19.5, “Man page compression”</a> for
1.87 wiz 9273: information on installation of compressed manual pages.</p>
1.75 rillig 9274: </div>
1.148 asau 9275: <div class="sect2">
1.75 rillig 9276: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9277: <a name="x11-fonts"></a>21.6.9. Packages installing X11 fonts</h3></div></div></div>
1.75 rillig 9278: <p>If a package installs font files, you will need to rebuild
1.87 wiz 9279: the fonts database in the directory where they get installed at
9280: installation and deinstallation time. This can be automatically
9281: done by using the pkginstall framework.</p>
1.75 rillig 9282: <p>You can list the directories where fonts are installed in the
1.87 wiz 9283: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code>
9284: variables, where <em class="replaceable"><code>type</code></em> can be one of
1.128 wiz 9285: <span class="quote">“<span class="quote">ttf</span>”</span>, <span class="quote">“<span class="quote">type1</span>”</span> or <span class="quote">“<span class="quote">x11</span>”</span>.
1.87 wiz 9286: Also make sure that the database file
9287: <code class="filename">fonts.dir</code> is not listed in the PLIST.</p>
1.75 rillig 9288: <p>Note that you should not create new directories for fonts;
1.87 wiz 9289: instead use the standard ones to avoid that the user needs to
9290: manually configure his X server to find them.</p>
1.75 rillig 9291: </div>
1.148 asau 9292: <div class="sect2">
1.75 rillig 9293: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9294: <a name="sgml-xml-data"></a>21.6.10. Packages installing SGML or XML data</h3></div></div></div>
1.75 rillig 9295: <p>If a package installs SGML or XML data files that need to be
1.87 wiz 9296: registered in system-wide catalogs (like DTDs, sub-catalogs,
9297: etc.), you need to take some extra steps:</p>
1.128 wiz 9298: <div class="orderedlist"><ol class="orderedlist" type="1">
9299: <li class="listitem"><p>Include
1.87 wiz 9300: <code class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in
9301: your <code class="filename">Makefile</code>, which takes care of
9302: registering those files in system-wide catalogs at
9303: installation and deinstallation time.</p></li>
1.128 wiz 9304: <li class="listitem"><p>Set <code class="varname">SGML_CATALOGS</code> to the full path of
1.87 wiz 9305: any SGML catalogs installed by the package.</p></li>
1.128 wiz 9306: <li class="listitem"><p>Set <code class="varname">XML_CATALOGS</code> to the full path of
1.87 wiz 9307: any XML catalogs installed by the package.</p></li>
1.128 wiz 9308: <li class="listitem"><p>Set <code class="varname">SGML_ENTRIES</code> to individual entries
1.87 wiz 9309: to be added to the SGML catalog. These come in groups of
9310: three strings; see xmlcatmgr(1) for more information
9311: (specifically, arguments recognized by the 'add' action).
9312: Note that you will normally not use this variable.</p></li>
1.128 wiz 9313: <li class="listitem"><p>Set <code class="varname">XML_ENTRIES</code> to individual entries
1.87 wiz 9314: to be added to the XML catalog. These come in groups of three
9315: strings; see xmlcatmgr(1) for more information (specifically,
9316: arguments recognized by the 'add' action). Note that you will
9317: normally not use this variable.</p></li>
1.75 rillig 9318: </ol></div>
9319: </div>
1.148 asau 9320: <div class="sect2">
1.75 rillig 9321: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9322: <a name="mime-database"></a>21.6.11. Packages installing extensions to the MIME database</h3></div></div></div>
1.75 rillig 9323: <p>If a package provides extensions to the MIME database by
1.87 wiz 9324: installing <code class="filename">.xml</code> files inside
9325: <code class="filename">${PREFIX}/share/mime/packages</code>, you
9326: need to take some extra steps to ensure that the database is kept
9327: consistent with respect to these new files:</p>
1.128 wiz 9328: <div class="orderedlist"><ol class="orderedlist" type="1">
9329: <li class="listitem"><p>Include
1.87 wiz 9330: <code class="filename">../../databases/shared-mime-info/mimedb.mk</code>
9331: (avoid using the <code class="filename">buildlink3.mk</code> file from
9332: this same directory, which is reserved for inclusion from
9333: other <code class="filename">buildlink3.mk</code> files). It takes
9334: care of rebuilding the MIME database at installation and
9335: deinstallation time, and disallows any access to it directly
9336: from the package.</p></li>
1.128 wiz 9337: <li class="listitem"><p>Check the PLIST and remove any entries under the
1.87 wiz 9338: <code class="filename">share/mime</code> directory,
9339: <span class="emphasis"><em>except</em></span> for files saved under
9340: <code class="filename">share/mime/packages</code>. The former are
9341: handled automatically by
9342: the update-mime-database program, but the latter are
9343: package-dependent and must be removed by the package that
9344: installed them in the first place.</p></li>
1.128 wiz 9345: <li class="listitem"><p>Remove any <code class="filename">share/mime/*</code> directories
1.87 wiz 9346: from the PLIST. They will be handled by the shared-mime-info
9347: package.</p></li>
1.75 rillig 9348: </ol></div>
9349: </div>
1.148 asau 9350: <div class="sect2">
1.75 rillig 9351: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9352: <a name="intltool"></a>21.6.12. Packages using intltool</h3></div></div></div>
1.93 rillig 9353: <p>If a package uses intltool during its build, add
9354: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>,
1.87 wiz 9355: which forces it to use the intltool package provided by pkgsrc,
9356: instead of the one bundled with the distribution file.</p>
1.75 rillig 9357: <p>This tracks intltool's build-time dependencies and uses the
1.87 wiz 9358: latest available version; this way, the package benefits of any
9359: bug fixes that may have appeared since it was released.</p>
1.75 rillig 9360: </div>
1.148 asau 9361: <div class="sect2">
1.75 rillig 9362: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9363: <a name="startup-scripts"></a>21.6.13. Packages installing startup scripts</h3></div></div></div>
1.75 rillig 9364: <p>If a package contains a rc.d script, it won't be copied into
1.87 wiz 9365: the startup directory by default, but you can enable it, by adding
9366: the option <code class="varname">PKG_RCD_SCRIPTS=YES</code> in
1.110 hubertf 9367: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. This option will copy the scripts
1.87 wiz 9368: into <code class="filename">/etc/rc.d</code> when a package is installed, and
9369: it will automatically remove the scripts when the package is
9370: deinstalled.</p>
1.75 rillig 9371: </div>
1.148 asau 9372: <div class="sect2">
1.75 rillig 9373: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9374: <a name="tex-packages"></a>21.6.14. Packages installing TeX modules</h3></div></div></div>
1.75 rillig 9375: <p>If a package installs TeX packages into the texmf tree,
1.87 wiz 9376: the <code class="filename">ls-R</code> database of the tree needs to be
9377: updated.</p>
1.148 asau 9378: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.75 rillig 9379: <h3 class="title">Note</h3>
1.125 wiz 9380: <p>Except the main TeX packages such as kpathsea,
1.87 wiz 9381: packages should install files
1.125 wiz 9382: into <code class="filename">${PREFIX}/share/texmf-dist</code>,
9383: not <code class="filename">${PREFIX}/share/texmf</code>.</p>
1.75 rillig 9384: </div>
1.128 wiz 9385: <div class="orderedlist"><ol class="orderedlist" type="1">
9386: <li class="listitem"><p>Include
1.125 wiz 9387: <code class="filename">../../print/kpathsea/texmf.mk</code>. This
1.87 wiz 9388: takes care of rebuilding the <code class="filename">ls-R</code>
9389: database at installation and deinstallation time.</p></li>
1.128 wiz 9390: <li class="listitem">
1.75 rillig 9391: <p>If your package installs files into a texmf
1.87 wiz 9392: tree other than the one
1.125 wiz 9393: at <code class="filename">${PREFIX}/share/texmf-dist</code>,
9394: set <code class="varname">TEX_TEXMF_DIRS</code> to the list of all texmf
1.87 wiz 9395: trees that need database update.</p>
1.75 rillig 9396: <p>If your package also installs font map files that need
1.110 hubertf 9397: to be registered using <span class="command"><strong>updmap</strong></span>,
1.136 dholland 9398: include <code class="filename">../../print/tex-tetex/map.mk</code> and
1.125 wiz 9399: set <code class="varname">TEX_MAP_FILES</code> and/or
9400: <code class="varname">TEX_MIXEDMAP_FILES</code> to the list of all
1.110 hubertf 9401: such font map files. Then <span class="command"><strong>updmap</strong></span> will
1.87 wiz 9402: be run automatically at installation/deinstallation to
9403: enable/disable font map files for TeX output
9404: drivers.</p>
1.75 rillig 9405: </li>
1.128 wiz 9406: <li class="listitem"><p>Make sure that none of <code class="filename">ls-R</code>
1.87 wiz 9407: databases are included in <code class="filename">PLIST</code>, as
1.136 dholland 9408: they will be removed only by the kpathsea package.</p></li>
1.75 rillig 9409: </ol></div>
9410: </div>
1.148 asau 9411: <div class="sect2">
1.85 jmmv 9412: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9413: <a name="emulation-packages"></a>21.6.15. Packages supporting running binaries in
1.87 wiz 9414: emulation</h3></div></div></div>
9415: <p>There are some packages that provide libraries and
9416: executables for running binaries from a one operating system
9417: on a different one (if the latter supports it). One example
9418: is running Linux binaries on NetBSD.</p>
1.322 leot 9419: <p>The <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/rpm2pkg/index.html" target="_top"><code class="filename">pkgtools/rpm2pkg</code></a>
1.87 wiz 9420: helps in extracting and packaging Linux rpm packages.</p>
9421: <p>The <code class="varname">CHECK_SHLIBS</code> can be set to no to
1.110 hubertf 9422: avoid the <span class="command"><strong>check-shlibs</strong></span> target, which tests
1.87 wiz 9423: if all libraries for each installed executable can be found by
9424: the dynamic linker. Since the standard dynamic linker is run,
9425: this fails for emulation packages, because the libraries used
9426: by the emulation are not in the standard directories.</p>
9427: </div>
1.299 rillig 9428: <div class="sect2">
9429: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9430: <a name="hicolor-theme"></a>21.6.16. Packages installing hicolor icons</h3></div></div></div>
1.299 rillig 9431: <p>If a package installs images under the
9432: <code class="filename">share/icons/hicolor</code> and/or updates the
9433: <code class="filename">share/icons/hicolor/icon-theme.cache</code>
9434: database, you need to take some extra steps to make sure that the
9435: shared theme directory is handled appropriately and that the cache
9436: database is rebuilt:</p>
9437: <div class="orderedlist"><ol class="orderedlist" type="1">
9438: <li class="listitem"><p>Include
9439: <code class="filename">../../graphics/hicolor-icon-theme/buildlink3.mk</code>.</p></li>
9440: <li class="listitem"><p>Check the <code class="filename">PLIST</code> and remove the
9441: entry that refers to the theme cache.</p></li>
9442: <li class="listitem"><p>Ensure that the PLIST does not remove the shared icon
9443: directories from the <code class="filename">share/icons/hicolor</code>
9444: hierarchy because they will be handled automatically.</p></li>
9445: </ol></div>
9446: <p>The best way to verify that the PLIST is correct with
9447: respect to the last two points is to regenerate it using
9448: <span class="command"><strong>make print-PLIST</strong></span>.</p>
9449: </div>
9450: <div class="sect2">
9451: <div class="titlepage"><div><div><h3 class="title">
1.318 nia 9452: <a name="desktop-files"></a>21.6.17. Packages installing desktop files</h3></div></div></div>
1.299 rillig 9453: <p>If a package installs <code class="filename">.desktop</code> files
9454: under <code class="filename">share/applications</code> and these include
9455: MIME information (MimeType key), you need to take extra steps to
9456: ensure that they are registered into the MIME database:</p>
9457: <div class="orderedlist"><ol class="orderedlist" type="1">
9458: <li class="listitem"><p>Include
9459: <code class="filename">../../sysutils/desktop-file-utils/desktopdb.mk</code>.</p></li>
9460: <li class="listitem"><p>Check the PLIST and remove the entry that refers to the
9461: <code class="filename">share/applications/mimeinfo.cache</code> file.
9462: It will be handled automatically.</p></li>
9463: </ol></div>
9464: <p>The best way to verify that the PLIST is correct with
9465: respect to the last point is to regenerate it using <span class="command"><strong>make
9466: print-PLIST</strong></span>.</p>
9467: </div>
9468: </div>
9469: <div class="sect1">
9470: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9471: <a name="punting"></a>21.7. Marking packages as having problems</h2></div></div></div>
9472: <p>In some cases one does not have the time to solve a problem
9473: immediately. In this case, one can plainly mark a package as broken. For
9474: this, one just sets the variable <code class="varname">BROKEN</code> to the
9475: reason why the package is broken (similar to the
9476: <code class="varname">PKG_FAIL_REASON</code> variable). A user trying to build
9477: the package will immediately be shown this message, and the build
9478: will not be even tried.</p>
9479: <p><code class="varname">BROKEN</code> packages are removed from pkgsrc in irregular
9480: intervals.</p>
9481: </div>
9482: </div>
9483: <div class="chapter">
9484: <div class="titlepage"><div><div><h2 class="title">
9485: <a name="gnome"></a>Chapter 22. GNOME packaging and porting</h2></div></div></div>
9486: <div class="toc">
9487: <p><b>Table of Contents</b></p>
9488: <dl class="toc">
9489: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
9490: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
9491: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
9492: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
9493: </dl>
9494: </div>
9495: <p>Quoting <a class="ulink" href="https://www.gnome.org/" target="_top">GNOME's web
9496: site</a>:</p>
9497: <div class="blockquote"><blockquote class="blockquote"><p>The GNOME project provides two things: The GNOME desktop
9498: environment, an intuitive and attractive desktop for users, and the
9499: GNOME development platform, an extensive framework for building
9500: applications that integrate into the rest of the desktop.</p></blockquote></div>
9501: <p>pkgsrc provides a seamless way to automatically build and install
9502: a complete GNOME environment <span class="emphasis"><em>under many different
9503: platforms</em></span>. We can say with confidence that pkgsrc is one of
9504: the most advanced build and packaging systems for GNOME due to its
9505: included technologies buildlink3, the wrappers and tools framework and
9506: automatic configuration file management. Lots of efforts are put into
9507: achieving a completely clean deinstallation of installed software
9508: components.</p>
9509: <p>Given that pkgsrc is <a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a>'s official packaging system,
9510: the above also means that great efforts are put into making GNOME work
1.316 cirnatda 9511: under this operating system.</p>
1.299 rillig 9512: <p>This chapter is aimed at pkgsrc developers and other people
9513: interested in helping our GNOME porting and packaging efforts. It
9514: provides instructions on how to manage the existing packages and some
9515: important information regarding their internals.</p>
9516: <div class="sect1">
9517: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9518: <a name="meta-packages"></a>22.1. Meta packages</h2></div></div></div>
9519: <p>pkgsrc includes three GNOME-related meta packages:</p>
9520: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.322 leot 9521: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/index.html" target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>: Provides
1.299 rillig 9522: the core GNOME desktop environment. It only includes the necessary
9523: bits to get it to boot correctly, although it may lack important
9524: functionality for daily operation. The idea behind this package is
9525: to let end users build their own configurations on top of this one,
9526: first installing this meta package to achieve a functional setup and
9527: then adding individual applications.</p></li>
1.322 leot 9528: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/index.html" target="_top"><code class="filename">meta-pkgs/gnome</code></a>: Provides a
1.299 rillig 9529: complete installation of the GNOME platform and desktop as defined
9530: by the GNOME project; this is based on the components distributed in
9531: the <code class="filename">platform/x.y/x.y.z/sources</code> and
9532: <code class="filename">desktop/x.y/x.y.z/sources</code> directories of the
9533: official FTP server. Developer-only tools found in those
9534: directories are not installed unless required by some other
9535: component to work properly. Similarly, packages from the bindings
9536: set (<code class="filename">bindings/x.y/x.y.z/sources</code>) are not pulled
9537: in unless required as a dependency for an end-user component. This
1.322 leot 9538: package "extends" <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/index.html" target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>.</p></li>
9539: <li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/index.html" target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a>:
1.299 rillig 9540: Installs all the tools required to build a GNOME component when
9541: fetched from the CVS repository. These are required to let the
9542: <span class="command"><strong>autogen.sh</strong></span> scripts work appropriately.</p></li>
9543: </ul></div>
9544: <p>In all these packages, the <code class="varname">DEPENDS</code> lines are
9545: sorted in a way that eases updates: a package may depend on other
9546: packages listed before it but not on any listed after it. It is very
9547: important to keep this order to ease updates so... <span class="emphasis"><em>do not
9548: change it to alphabetical sorting!</em></span></p>
9549: </div>
9550: <div class="sect1">
9551: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9552: <a name="new-package"></a>22.2. Packaging a GNOME application</h2></div></div></div>
9553: <p>Almost all GNOME applications are written in C and use a common
9554: set of tools as their build system. Things get different with the new
9555: bindings to other languages (such as Python), but the following will
9556: give you a general idea on the minimum required tools:</p>
9557: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9558: <li class="listitem">
9559: <p>Almost all GNOME applications use the GNU Autotools as their
9560: build system. As a general rule you will need to tell this to your
9561: package:</p>
9562: <pre class="programlisting">
1.338 nia 9563: GNU_CONFIGURE= yes
9564: USE_LIBTOOL= yes
9565: USE_TOOLS+= gmake
1.299 rillig 9566: </pre>
9567: </li>
9568: <li class="listitem">
9569: <p>If the package uses pkg-config to detect dependencies, add this
9570: tool to the list of required utilities:</p>
9571: <pre class="programlisting">
1.338 nia 9572: USE_TOOLS+= pkg-config
1.299 rillig 9573: </pre>
1.322 leot 9574: <p>Also use <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/verifypc/index.html" target="_top"><code class="filename">pkgtools/verifypc</code></a> at
1.299 rillig 9575: the end of the build process to ensure that you did not miss to
9576: specify any dependency in your package and that the version
9577: requirements are all correct.</p>
9578: </li>
9579: <li class="listitem"><p>If the package uses intltool, be sure to add
9580: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>
9581: to handle dependencies and to force the package to use the latest
9582: available version.</p></li>
9583: <li class="listitem">
9584: <p>If the package uses gtk-doc (a documentation generation
9585: utility), do <span class="emphasis"><em>not</em></span> add a dependency on it. The
9586: tool is rather big and the distfile should come with pregenerated
9587: documentation anyway; if it does not, it is a bug that you ought to
9588: report. For such packages you should disable gtk-doc (unless it is
9589: the default):</p>
9590: <pre class="programlisting">
1.338 nia 9591: CONFIGURE_ARGS+= --disable-gtk-doc
1.299 rillig 9592: </pre>
9593: <p>The default location of installed HTML files
9594: (<code class="filename">share/gtk-doc/<package-name></code>) is correct
9595: and should not be changed unless the package insists on installing
9596: them somewhere else. Otherwise programs as
9597: <span class="command"><strong>devhelp</strong></span> will not be able to open them. You can
9598: do that with an entry similar to:</p>
9599: <pre class="programlisting">
1.338 nia 9600: CONFIGURE_ARGS+= --with-html-dir=${PREFIX}/share/gtk-doc/...
1.299 rillig 9601: </pre>
9602: </li>
9603: </ul></div>
9604: <p>GNOME uses multiple <span class="emphasis"><em>shared</em></span> directories and
9605: files under the installation prefix to maintain databases. In this
9606: context, shared means that those exact same directories and files are
9607: used among several different packages, leading to conflicts in the
9608: <code class="filename">PLIST</code>. pkgsrc currently includes functionality to
9609: handle the most common cases, so you have to forget about using
9610: <code class="literal">@unexec ${RMDIR}</code> lines in your file lists and
9611: omitting shared files from them. If you find yourself doing those,
9612: <span class="emphasis"><em>your package is most likely incorrect</em></span>.</p>
9613: <p>The following table lists the common situations that result in
9614: using shared directories or files. For each of them, the appropriate
9615: solution is given. After applying the solution be sure to
9616: <span class="emphasis"><em>regenerate the package's file list</em></span> with
9617: <span class="command"><strong>make print-PLIST</strong></span> and ensure it is correct.</p>
9618: <div class="table">
9619: <a name="plist-handling"></a><p class="title"><b>Table 22.1. PLIST handling for GNOME packages</b></p>
9620: <div class="table-contents"><table class="table" summary="PLIST handling for GNOME packages" border="1">
9621: <colgroup>
9622: <col>
9623: <col>
9624: </colgroup>
9625: <thead><tr>
9626: <th>If the package...</th>
9627: <th>Then...</th>
9628: </tr></thead>
9629: <tbody>
9630: <tr>
9631: <td>Installs icons under the
9632: <code class="filename">share/icons/hicolor</code> hierarchy or updates
9633: <code class="filename">share/icons/hicolor/icon-theme.cache</code>.</td>
1.318 nia 9634: <td>See <a class="xref" href="#hicolor-theme" title="21.6.16. Packages installing hicolor icons">Section 21.6.16, “Packages installing hicolor icons”</a>.</td>
1.299 rillig 9635: </tr>
9636: <tr>
9637: <td>Installs files under
9638: <code class="filename">share/mime/packages</code>.</td>
1.318 nia 9639: <td>See <a class="xref" href="#mime-database" title="21.6.11. Packages installing extensions to the MIME database">Section 21.6.11, “Packages installing extensions to the MIME database”</a>.</td>
1.299 rillig 9640: </tr>
9641: <tr>
9642: <td>Installs <code class="filename">.desktop</code> files under
9643: <code class="filename">share/applications</code> and these include MIME
9644: information.</td>
1.318 nia 9645: <td>See <a class="xref" href="#desktop-files" title="21.6.17. Packages installing desktop files">Section 21.6.17, “Packages installing desktop files”</a>.</td>
1.299 rillig 9646: </tr>
9647: </tbody>
9648: </table></div>
1.75 rillig 9649: </div>
1.299 rillig 9650: <br class="table-break">
1.75 rillig 9651: </div>
1.148 asau 9652: <div class="sect1">
1.87 wiz 9653: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 9654: <a name="full-update"></a>22.3. Updating GNOME to a newer version</h2></div></div></div>
9655: <p>When seeing GNOME as a whole, there are two kinds of
9656: updates:</p>
9657: <div class="variablelist"><dl class="variablelist">
9658: <dt><span class="term">Major update</span></dt>
9659: <dd>
9660: <p>Given that there is still a very long way for GNOME 3 (if it
9661: ever appears), we consider a major update one that goes from a
9662: <code class="literal">2.X</code> version to a <code class="literal">2.Y</code> one,
9663: where <code class="literal">Y</code> is even and greater than
9664: <code class="literal">X</code>. These are hard to achieve because they
9665: introduce lots of changes in the components' code and almost all
9666: GNOME distfiles are updated to newer versions. Some of them can
9667: even break API and ABI compatibility with the previous major
9668: version series. As a result, the update needs to be done all at
9669: once to minimize breakage.</p>
9670: <p>A major update typically consists of around 80 package
9671: updates and the addition of some new ones.</p>
9672: </dd>
9673: <dt><span class="term">Minor update</span></dt>
9674: <dd>
9675: <p>We consider a minor update one that goes from a
9676: <code class="literal">2.A.X</code> version to a <code class="literal">2.A.Y</code>
9677: one where <code class="literal">Y</code> is greater than
9678: <code class="literal">X</code>. These are easy to achieve because they do
9679: not update all GNOME components, can be done in an incremental way
9680: and do not break API nor ABI compatibility.</p>
9681: <p>A minor update typically consists of around 50 package
9682: updates, although the numbers here may vary a lot.</p>
9683: </dd>
9684: </dl></div>
9685: <p>In order to update the GNOME components in pkgsrc to a new stable
9686: release (either major or minor), the following steps should be
9687: followed:</p>
9688: <div class="orderedlist"><ol class="orderedlist" type="1">
1.128 wiz 9689: <li class="listitem">
1.299 rillig 9690: <p>Get a list of all the tarballs that form the new release by
9691: using the following commands. These will leave the full list of the
9692: components' distfiles into the <code class="filename">list.txt</code>
9693: file:</p>
9694: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9695: ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
9696: awk '{ print $9 }' >list.txt</code></strong>
9697: <code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9698: ftp -V ftp://ftp.gnome.org/pub/gnome/desktop/x.y/x.y.z/sources/ | \
9699: awk '{ print $9 }' >>list.txt</code></strong></pre>
1.75 rillig 9700: </li>
1.299 rillig 9701: <li class="listitem"><p>Open each meta package's <code class="filename">Makefile</code> and
9702: bump their version to the release you are updating them to. The
9703: three meta packages should be always consistent with versioning.
9704: Obviously remove any <code class="varname">PKGREVISION</code>s that might be
9705: in them.</p></li>
1.128 wiz 9706: <li class="listitem">
1.299 rillig 9707: <p>For each meta package, update all its
9708: <code class="varname">DEPENDS</code> lines to match the latest versions as
9709: shown by the above commands. Do <span class="emphasis"><em>not</em></span> list any
9710: newer version (even if found in the FTP) because the meta packages
9711: are supposed to list the exact versions that form a specific GNOME
9712: release. Exceptions are permitted here if a newer version solves a
9713: serious issue in the overall desktop experience; these typically
9714: come in the form of a revision bump in pkgsrc, not in newer versions
9715: from the developers.</p>
9716: <p>Packages not listed in the <code class="filename">list.txt</code> file
9717: should be updated to the latest version available (if found in
9718: pkgsrc). This is the case, for example, of the dependencies on the
1.322 leot 9719: GNU Autotools in the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/index.html" target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a> meta package.</p>
1.75 rillig 9720: </li>
1.128 wiz 9721: <li class="listitem">
1.299 rillig 9722: <p>Generate a patch from the modified meta packages and extract the
9723: list of "new" lines. This will provide you an outline on what
9724: packages need to be updated in pkgsrc and in what order:</p>
9725: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs diff -u gnome-devel gnome-base gnome | grep '^+D' >todo.txt</code></strong></pre>
1.75 rillig 9726: </li>
1.299 rillig 9727: <li class="listitem"><p>For major desktop updates it is recommended to zap all your
9728: installed packages and start over from scratch at this point.</p></li>
9729: <li class="listitem"><p>Now comes the longest step by far: iterate over the contents
9730: of <code class="filename">todo.txt</code> and update the packages listed in
9731: it in order. For major desktop updates none of these should be
9732: committed until the entire set is completed because there are chances
9733: of breaking not-yet-updated packages.</p></li>
9734: <li class="listitem"><p>Once the packages are up to date and working, commit them to
9735: the tree one by one with appropriate log messages. At the end,
9736: commit the three meta package updates and all the corresponding
9737: changes to the <code class="filename">doc/CHANGES-<YEAR></code> and
9738: <a href="http://cvsweb.NetBSD.org/bsdweb.cgi/pkgsrc/doc/TODO?rev=HEAD&content-type=text/x-cvsweb-markup" target="_top"><code class="filename">pkgsrc/doc/TODO</code></a> files.</p></li>
9739: </ol></div>
9740: </div>
9741: <div class="sect1">
9742: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9743: <a name="patching"></a>22.4. Patching guidelines</h2></div></div></div>
9744: <p>GNOME is a very big component in pkgsrc which approaches 100
9745: packages. Please, it is very important that you always, always,
9746: <span class="strong"><strong>always</strong></span> feed back any portability
9747: fixes you do to a GNOME package to the mainstream developers (see <a class="xref" href="#components.patches.feedback" title="12.3.5. Feedback to the author">Section 12.3.5, “Feedback to the author”</a>). This is the only way to get
9748: their attention on portability issues and to ensure that future versions
9749: can be built out-of-the box on NetBSD. The less custom patches in
9750: pkgsrc, the easier further updates are. Those developers in charge of
9751: issuing major GNOME updates will be grateful if you do that.</p>
1.315 cirnatda 9752: <p>The most common places to report bugs are the <a class="ulink" href="https://gitlab.gnome.org/GNOME" target="_top">GNOME's GitLab</a> and the <a class="ulink" href="https://gitlab.freedesktop.org/explore/groups" target="_top">freedesktop.org's
9753: GitLab</a>. Not all components use these to track bugs, but most
1.299 rillig 9754: of them do. Do not be short on your reports: always provide detailed
9755: explanations of the current failure, how it can be improved to achieve
1.315 cirnatda 9756: maximum portability and, if at all possible, provide a patch against the
9757: main Git branch. The more verbose you are, the higher chances of your
9758: patch being accepted.</p>
1.299 rillig 9759: <p>Also, please avoid using preprocessor magic to fix portability
9760: issues. While the FreeBSD GNOME people are doing a great job in porting
9761: GNOME to their operating system, the official GNOME sources are now
9762: plagued by conditionals that check for <code class="varname">__FreeBSD__</code>
9763: and similar macros. This hurts portability. Please see our patching
9764: guidelines (<a class="xref" href="#components.patches.guidelines" title="12.3.4. Patching guidelines">Section 12.3.4, “Patching guidelines”</a>) for more
9765: details.</p>
9766: </div>
1.75 rillig 9767: </div>
1.148 asau 9768: <div class="chapter">
1.75 rillig 9769: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 9770: <a name="submit"></a>Chapter 23. Submitting and Committing</h2></div></div></div>
1.75 rillig 9771: <div class="toc">
9772: <p><b>Table of Contents</b></p>
1.210 leot 9773: <dl class="toc">
1.267 rillig 9774: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
9775: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
9776: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
9777: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
9778: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
9779: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
9780: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
9781: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
1.75 rillig 9782: </dl>
9783: </div>
1.148 asau 9784: <div class="sect1">
1.75 rillig 9785: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9786: <a name="submitting-binary-packages"></a>23.1. Submitting binary packages</h2></div></div></div>
1.75 rillig 9787: <p>Our policy is that we accept binaries only from pkgsrc
9788: developers to guarantee that the packages don't contain any
9789: trojan horses etc. This is not to annoy anyone but rather to
9790: protect our users! You're still free to put up your home-made
9791: binary packages and tell the world where to get them. NetBSD
9792: developers doing bulk builds and wanting to upload them please
1.267 rillig 9793: see <a class="xref" href="#bulk" title="Chapter 8. Creating binary packages for everything in pkgsrc (bulk builds)">Chapter 8, <i>Creating binary packages for everything in pkgsrc (bulk
1.174 asau 9794: builds)</i></a>.</p>
1.75 rillig 9795: </div>
1.148 asau 9796: <div class="sect1">
1.75 rillig 9797: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9798: <a name="submitting-your-package"></a>23.2. Submitting source packages (for non-NetBSD-developers)</h2></div></div></div>
1.333 nia 9799: <p>Firstly, you can import new packages into
9800: pkgsrc-wip (<span class="quote">“<span class="quote">pkgsrc work-in-progress</span>”</span>); see the
9801: homepage at <a class="ulink" href="https://pkgsrc.org/wip/" target="_top">https://pkgsrc.org/wip/</a>
9802: for details.</p>
9803: <p>Next, check that your package is complete, compiles and
1.299 rillig 9804: runs well; see <a class="xref" href="#creating" title="Chapter 14. Creating a new pkgsrc package from scratch">Chapter 14, <i>Creating a new pkgsrc package from scratch</i></a> and the rest of this
1.333 nia 9805: document. Run the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/index.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>
9806: tool and fix any errors that appear.</p>
9807: <p>Finally, send a report to the pkgsrc bug tracking system,
1.322 leot 9808: either with the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> command, or if you don't have
1.87 wiz 9809: that, go to the web page
1.289 leot 9810: <a class="ulink" href="https://www.NetBSD.org/support/send-pr.html" target="_top">https://www.NetBSD.org/support/send-pr.html</a>,
1.124 snj 9811: which contains some instructions and a link to a form where you
9812: can submit packages. The
1.322 leot 9813: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/gtk-send-pr/index.html" target="_top"><code class="filename">sysutils/gtk-send-pr</code></a> package is
1.124 snj 9814: also available as a substitute for either of the above two tools.
9815: </p>
1.87 wiz 9816: <p>In the form of the problem report, the category should be
1.128 wiz 9817: <span class="quote">“<span class="quote">pkg</span>”</span>, the synopsis should include the package name
1.87 wiz 9818: and version number, and the description field should contain a
9819: short description of your package (contents of the COMMENT
1.333 nia 9820: variable or DESCR file are OK).</p>
1.75 rillig 9821: </div>
1.148 asau 9822: <div class="sect1">
1.75 rillig 9823: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9824: <a name="general-notes-for-changes"></a>23.3. General notes when adding, updating, or removing packages</h2></div></div></div>
1.75 rillig 9825: <p>Please note all package additions, updates, moves, and
1.93 rillig 9826: removals in <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code>. It's very
1.75 rillig 9827: important to keep this file up to date and conforming to the
9828: existing format, because it will be used by scripts to
1.289 leot 9829: automatically update pages on <a class="ulink" href="https://www.NetBSD.org/" target="_top">www.NetBSD.org</a> and other
1.75 rillig 9830: sites. Additionally, check the
1.76 rillig 9831: <code class="filename">pkgsrc/doc/TODO</code> file and remove the entry
1.75 rillig 9832: for the package you updated or removed, in case it was mentioned
9833: there.</p>
9834: <p>When the <code class="varname">PKGREVISION</code> of a package is
9835: bumped, the change should appear in
1.93 rillig 9836: <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code> if it is security
1.75 rillig 9837: related or otherwise relevant. Mass bumps that result from a
9838: dependency being updated should not be mentioned. In all other
9839: cases it's the developer's decision.</p>
9840: <p>There is a make target that helps in creating proper
1.110 hubertf 9841: <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code> entries: <span class="command"><strong>make
1.75 rillig 9842: changes-entry</strong></span>. It uses the optional <code class="varname">CTYPE</code>
9843: and <code class="varname">NETBSD_LOGIN_NAME</code> variables. The general
1.93 rillig 9844: usage is to first make sure that your <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code>
1.75 rillig 9845: file is up-to-date (to avoid having to resolve conflicts later-on)
1.110 hubertf 9846: and then to <span class="command"><strong>cd</strong></span> to the package directory. For
9847: package updates, <span class="command"><strong>make changes-entry</strong></span> is enough.
1.75 rillig 9848: For new packages, or package moves or removals, set the
9849: <code class="varname">CTYPE</code> variable on the command line to "Added",
9850: "Moved", or "Removed". You can set <code class="varname">NETBSD_LOGIN_NAME</code>
1.110 hubertf 9851: in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> if your local login name is
1.125 wiz 9852: not the same as your NetBSD login name. The target also automatically
9853: removes possibly existing entries for the package in the
9854: <code class="filename">TODO</code> file. Don't forget to commit
1.174 asau 9855: the changes, e.g. by using <span class="command"><strong>make commit-changes-entry</strong></span>!
1.126 jakllsch 9856: If you are not using a checkout directly from cvs.NetBSD.org, but e.g.
1.125 wiz 9857: a local copy of the repository, you can set USE_NETBSD_REPO=yes. This
9858: makes the cvs commands use the main repository.
9859: </p>
1.75 rillig 9860: </div>
1.148 asau 9861: <div class="sect1">
1.75 rillig 9862: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9863: <a name="commit-messages"></a>23.4. Commit Messages</h2></div></div></div>
1.243 wiz 9864: <p>For several years, there have been mirrors of pkgsrc in
9865: fossil, git, and hg. Standard practise when using these tools is to
9866: make the first line of a commit message function as a summary that
9867: can be read without the rest, such as is commonly done with "git log
9868: --oneline". For this reason, we have the following guidelines for
9869: pkgsrc commit messages:</p>
9870: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9871: <li class="listitem"><p>Start the commit message with a line that explains the
1.244 wiz 9872: big picture in 65 characters or less. When a commit is for one
1.243 wiz 9873: package, include the name of the package. For updates, include the
9874: version to which it is updated.</p></li>
9875: <li class="listitem"><p>Leave the next line empty.</p></li>
9876: <li class="listitem"><p>Then come the details for the commit (changes in that
9877: package, reason for a change) and any relevant PRs. Wrap this
9878: section.</p></li>
9879: </ul></div>
9880: <p>Here is an example:
9881: </p>
9882: <pre class="programlisting">
9883: libxslt: update to 1.0.30
9884:
9885: Changes since 1.0.29:
9886: ...
9887: </pre>
9888: <p>
9889: </p>
9890: <p>Here is another example:
9891: </p>
9892: <pre class="programlisting">
9893: mk/bsd.pkg.mk: enable SSP by default on NetBSD
9894:
9895: (rationale)
9896: </pre>
9897: <p>
9898: </p>
9899: <p>Commit messages are final: no <span class="quote">“<span class="quote">cvs admin</span>”</span> is
9900: allowed on the pkgsrc repository to change commit messages.</p>
9901: </div>
9902: <div class="sect1">
9903: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9904: <a name="committing-importing"></a>23.5. Committing: Adding a package to CVS</h2></div></div></div>
1.87 wiz 9905: <p>This section is only of interest for pkgsrc developers with write
1.140 wiz 9906: access to the pkgsrc repository.</p>
9907: <p>When the package is finished, <span class="quote">“<span class="quote">cvs add</span>”</span> the files.
9908: Start by adding the directory and then files in the directory. Don't
9909: forget to add the new package to the category's
9910: <code class="filename">Makefile</code>. Make sure you don't forget any files;
9911: you can check by running <span class="quote">“<span class="quote">cvs status</span>”</span>. An example:</p>
9912: <pre class="programlisting">
9913: <code class="prompt">$</code> cd .../pkgsrc/category
9914: <code class="prompt">$</code> cvs add pkgname
9915: <code class="prompt">$</code> cd pkgname
9916: <code class="prompt">$</code> cvs add DESCR Makefile PLIST distinfo buildlink3.mk patches
9917: <code class="prompt">$</code> cvs add patches/p*
9918: <code class="prompt">$</code> cvs status | less
1.141 wiz 9919: <code class="prompt">$</code> cvs commit
1.140 wiz 9920: <code class="prompt">$</code> cd ..
9921: <code class="prompt">$</code> vi Makefile # add SUBDIRS+=pkgname line
1.141 wiz 9922: <code class="prompt">$</code> cvs commit Makefile
1.174 asau 9923: <code class="prompt">$</code> cd pkgname
1.182 jnemeth 9924: <code class="prompt">$</code> make CTYPE=Added commit-changes-entry
1.140 wiz 9925: </pre>
1.87 wiz 9926: <p>The commit message of the initial import should include part of the
1.76 rillig 9927: <code class="filename">DESCR</code> file, so people reading the mailing lists know
1.87 wiz 9928: what the package is/does.</p>
1.140 wiz 9929: <p>Also mention the new package in
9930: <code class="filename">pkgsrc/doc/CHANGES-20xx</code>.</p>
9931: <p>Previously, <span class="quote">“<span class="quote">cvs import</span>”</span> was suggested, but it was
9932: much easier to get wrong than <span class="quote">“<span class="quote">cvs add</span>”</span>.</p>
1.75 rillig 9933: </div>
1.148 asau 9934: <div class="sect1">
1.75 rillig 9935: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9936: <a name="updating-package"></a>23.6. Updating a package to a newer version</h2></div></div></div>
1.87 wiz 9937: <p>Please always put a concise, appropriate and relevant summary of the
1.75 rillig 9938: changes between old and new versions into the commit log when updating
1.87 wiz 9939: a package. There are various reasons for this:</p>
1.148 asau 9940: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 9941: <li class="listitem"><p>A URL is volatile, and can change over time. It may go away completely
1.87 wiz 9942: or its information may be overwritten by newer information.</p></li>
1.128 wiz 9943: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.87 wiz 9944: repository is very useful for people who use either cvs or anoncvs.</p></li>
1.128 wiz 9945: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.75 rillig 9946: repository is very useful for people who read the pkgsrc-changes mailing
9947: list, so that they can make tactical decisions about when to upgrade
1.87 wiz 9948: the package.</p></li>
1.75 rillig 9949: </ul></div>
1.87 wiz 9950: <p>Please also recognize that, just because a new version of a package
1.75 rillig 9951: has been released, it should not automatically be upgraded in the CVS
9952: repository. We prefer to be conservative in the packages that are
9953: included in pkgsrc - development or beta packages are not really the
9954: best thing for most places in which pkgsrc is used. Please use your
9955: judgement about what should go into pkgsrc, and bear in mind that
1.87 wiz 9956: stability is to be preferred above new and possibly untested features.</p>
1.75 rillig 9957: </div>
1.148 asau 9958: <div class="sect1">
1.75 rillig 9959: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9960: <a name="renaming-package"></a>23.7. Renaming a package in pkgsrc</h2></div></div></div>
1.122 reed 9961: <p>Renaming packages is not recommended.</p>
1.290 gutterid 9962: <p>When renaming packages, be sure to fix any references to the old name
1.122 reed 9963: in other Makefiles, options, buildlink files, etc.</p>
1.282 leot 9964: <p>
1.290 gutterid 9965: Also, when renaming a package, please add
1.282 leot 9966: the package name and version pattern(s) of the previous package
9967: to <code class="varname">SUPERSEDES</code>.
1.122 reed 9968: This may be repeated for multiple renames.
9969: The new package would be an exact replacement.
1.282 leot 9970: Example:
1.122 reed 9971: </p>
1.282 leot 9972: <pre class="programlisting">
9973: SUPERSEDES+= p5-IO-Compress-Zlib<2.017
9974: SUPERSEDES+= optcomp-[0-9]*
9975: </pre>
1.128 wiz 9976: <p>Note that <span class="quote">“<span class="quote">successor</span>”</span> in the
1.122 reed 9977: CHANGES-<em class="replaceable"><code>YYYY</code></em> file doesn't necessarily
9978: mean that it <span class="emphasis"><em>supersedes</em></span>, as that successor may
9979: not be an exact replacement but is a suggestion for the replaced
9980: functionality.</p>
9981: </div>
1.148 asau 9982: <div class="sect1">
1.122 reed 9983: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.267 rillig 9984: <a name="moving-package"></a>23.8. Moving a package in pkgsrc</h2></div></div></div>
1.122 reed 9985: <p>It is preferred that packages are not renamed or moved, but if needed
9986: please follow these steps.
9987: </p>
1.128 wiz 9988: <div class="orderedlist"><ol class="orderedlist" type="1">
9989: <li class="listitem"><p>Make a copy of the directory somewhere else.</p></li>
9990: <li class="listitem">
1.75 rillig 9991: <p>Remove all CVS dirs.</p>
1.87 wiz 9992: <p>Alternatively to the first two steps you can also do:</p>
1.75 rillig 9993: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs -d user@cvs.NetBSD.org:/cvsroot export -D today pkgsrc/category/package</code></strong></pre>
1.87 wiz 9994: <p>and use that for further work.</p>
1.75 rillig 9995: </li>
1.128 wiz 9996: <li class="listitem"><p>Fix <code class="varname">CATEGORIES</code> and any
9997: <code class="varname">DEPENDS</code> paths that just did <span class="quote">“<span class="quote">../package</span>”</span>
9998: instead of <span class="quote">“<span class="quote">../../category/package</span>”</span>.</p></li>
9999: <li class="listitem"><p>In the modified package's Makefile, consider setting
1.122 reed 10000: <code class="varname">PREV_PKGPATH</code> to the previous category/package
10001: pathname. The <code class="varname">PREV_PKGPATH</code> can be used by tools
10002: for doing an update using pkgsrc building; for example, it can
1.322 leot 10003: search the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> database for <code class="varname">PREV_PKGPATH</code>
1.122 reed 10004: (if no <code class="varname">SUPERSEDES</code>) and then use the corresponding
10005: new <code class="varname">PKGPATH</code> for that moved package. Note that
10006: it may have multiple matches, so the tool should also check on the
10007: <code class="varname">PKGBASE</code> too. The <code class="varname">PREV_PKGPATH</code>
10008: probably has no value unless <code class="varname">SUPERSEDES</code> is not
10009: set, i.e. <code class="varname">PKGBASE</code> stays the same. </p></li>
1.128 wiz 10010: <li class="listitem"><p><span class="command"><strong>cvs import</strong></span> the modified package in the new
1.75 rillig 10011: place.</p></li>
1.128 wiz 10012: <li class="listitem">
1.75 rillig 10013: <p>Check if any package depends on it:
10014: </p>
10015: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
10016: <code class="prompt">%</code> <strong class="userinput"><code>grep /package */*/Makefile* */*/buildlink*</code></strong></pre>
10017: </li>
1.128 wiz 10018: <li class="listitem"><p>Fix paths in packages from step 5 to point to new location.</p></li>
10019: <li class="listitem"><p><span class="command"><strong>cvs rm (-f)</strong></span> the package at the old location.</p></li>
10020: <li class="listitem"><p>Remove from <code class="filename">oldcategory/Makefile</code>.</p></li>
10021: <li class="listitem"><p>Add to <code class="filename">newcategory/Makefile</code>.</p></li>
10022: <li class="listitem">
1.75 rillig 10023: <p>Commit the changed and removed files:</p>
10024: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong></pre>
1.87 wiz 10025: <p>(and any packages from step 5, of course).</p>
1.75 rillig 10026: </li>
10027: </ol></div>
10028: </div>
10029: </div>
1.148 asau 10030: <div class="chapter">
1.75 rillig 10031: <div class="titlepage"><div><div><h2 class="title">
1.267 rillig 10032: <a name="devfaq"></a>Chapter 24. Frequently Asked Questions</h2></div></div></div>
1.75 rillig 10033: <p>This section contains the answers to questions that may
10034: arise when you are writing a package. If you don't find your
10035: question answered here, first have a look in the other chapters,
10036: and if you still don't have the answer, ask on the
10037: <code class="literal">pkgsrc-users</code> mailing list.</p>
1.148 asau 10038: <div class="qandaset">
1.289 leot 10039: <a name="devfaq.qandaset"></a><dl>
1.267 rillig 10040: <dt>24.1. <a href="#devfaq.makeflags">What is the difference between
1.75 rillig 10041: MAKEFLAGS, .MAKEFLAGS and
10042: MAKE_FLAGS?</a>
10043: </dt>
1.267 rillig 10044: <dt>24.2. <a href="#devfaq.make">What is the difference between
1.75 rillig 10045: MAKE, GMAKE and
10046: MAKE_PROGRAM?</a>
10047: </dt>
1.267 rillig 10048: <dt>24.3. <a href="#devfaq.cc">What is the difference between
1.75 rillig 10049: CC, PKG_CC and
10050: PKGSRC_COMPILER?</a>
10051: </dt>
1.338 nia 10052: <dt>24.4. <a href="#devfaq.bl3prefix">Why does make show-var
1.75 rillig 10053: VARNAME=BUILDLINK_PREFIX.foo
10054: say it's empty?</a>
10055: </dt>
1.338 nia 10056: <dt>24.5. <a href="#devfaq.master_sites">What does
1.78 rillig 10057: ${MASTER_SITE_SOURCEFORGE:=package/} mean? I
10058: don't understand the := inside
10059: it.</a>
10060: </dt>
1.338 nia 10061: <dt>24.6. <a href="#devfaq.mailinglists">Which mailing lists are there for package
1.78 rillig 10062: developers?</a>
10063: </dt>
1.338 nia 10064: <dt>24.7. <a href="#devfaq.documentation">Where is the pkgsrc
1.80 rillig 10065: documentation?</a>
10066: </dt>
1.338 nia 10067: <dt>24.8. <a href="#devfaq.too-much-time">I have a little time to kill.
1.289 leot 10068: What shall I do?</a>
1.92 rillig 10069: </dt>
1.75 rillig 10070: </dl>
1.148 asau 10071: <table border="0" style="width: 100%;">
10072: <colgroup>
1.75 rillig 10073: <col align="left" width="1%">
1.128 wiz 10074: <col>
1.148 asau 10075: </colgroup>
1.75 rillig 10076: <tbody>
1.148 asau 10077: <tr class="question">
1.75 rillig 10078: <td align="left" valign="top">
1.289 leot 10079: <a name="devfaq.makeflags"></a><a name="devfaq.makeflags.q"></a><p><b>24.1.</b></p>
1.75 rillig 10080: </td>
10081: <td align="left" valign="top"><p>What is the difference between
10082: <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
10083: <code class="varname">MAKE_FLAGS</code>?</p></td>
10084: </tr>
10085: <tr class="answer">
1.91 rillig 10086: <td align="left" valign="top"></td>
1.338 nia 10087: <td align="left" valign="top">
10088: <p><code class="varname">MAKEFLAGS</code> are the flags passed
10089: to the pkgsrc-internal invocations of <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.</p>
10090: <p><code class="varname">MAKE_FLAGS</code> are the flags that are
10091: passed to the <code class="varname">MAKE_PROGRAM</code> when building the
10092: package.</p>
10093: <p><code class="varname">.MAKEFLAGS</code> is an internal variable of
10094: <span class="command"><strong>bmake</strong></span> and should not be used by
10095: packages.</p>
10096: </td>
1.75 rillig 10097: </tr>
1.148 asau 10098: <tr class="question">
1.75 rillig 10099: <td align="left" valign="top">
1.289 leot 10100: <a name="devfaq.make"></a><a name="devfaq.make.q"></a><p><b>24.2.</b></p>
1.75 rillig 10101: </td>
10102: <td align="left" valign="top"><p>What is the difference between
10103: <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
10104: <code class="varname">MAKE_PROGRAM</code>?</p></td>
10105: </tr>
10106: <tr class="answer">
1.91 rillig 10107: <td align="left" valign="top"></td>
1.338 nia 10108: <td align="left" valign="top">
10109: <p><code class="varname">MAKE</code> is the path to the
1.322 leot 10110: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
1.338 nia 10111: infrastructure.</p>
10112: <p><code class="varname">GMAKE</code> is the path to GNU Make, but you
10113: need to say <code class="varname">USE_TOOLS+=gmake</code> to use
10114: that.</p>
10115: <p><code class="varname">MAKE_PROGRAM</code> is the path to the Make
10116: program that is used for building the package.</p>
10117: </td>
1.75 rillig 10118: </tr>
1.148 asau 10119: <tr class="question">
1.75 rillig 10120: <td align="left" valign="top">
1.289 leot 10121: <a name="devfaq.cc"></a><a name="devfaq.cc.q"></a><p><b>24.3.</b></p>
1.75 rillig 10122: </td>
10123: <td align="left" valign="top"><p>What is the difference between
10124: <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
10125: <code class="varname">PKGSRC_COMPILER</code>?</p></td>
10126: </tr>
10127: <tr class="answer">
1.91 rillig 10128: <td align="left" valign="top"></td>
1.75 rillig 10129: <td align="left" valign="top">
1.338 nia 10130: <p><code class="varname">CC</code> is the path to the real C
10131: compiler, which can be configured by the pkgsrc user.</p>
10132: <p><code class="varname">PKG_CC</code> is the path to the compiler
10133: wrapper.</p>
10134: <p><code class="varname">PKGSRC_COMPILER</code> is
10135: <span class="emphasis"><em>not</em></span> a path to a compiler, but the type of
10136: compiler that should be used. See
10137: <code class="filename">mk/compiler.mk</code> for more information about
10138: the latter variable.</p>
1.75 rillig 10139: </td>
10140: </tr>
1.148 asau 10141: <tr class="question">
1.75 rillig 10142: <td align="left" valign="top">
1.338 nia 10143: <a name="devfaq.bl3prefix"></a><a name="devfaq.bl3prefix.q"></a><p><b>24.4.</b></p>
1.75 rillig 10144: </td>
1.110 hubertf 10145: <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
1.75 rillig 10146: VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
10147: say it's empty?</p></td>
10148: </tr>
10149: <tr class="answer">
1.91 rillig 10150: <td align="left" valign="top"></td>
1.75 rillig 10151: <td align="left" valign="top"><p>For optimization reasons, some variables are only
1.128 wiz 10152: available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To
10153: <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append
1.110 hubertf 10154: <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
1.75 rillig 10155: command.</p></td>
10156: </tr>
1.148 asau 10157: <tr class="question">
1.78 rillig 10158: <td align="left" valign="top">
1.338 nia 10159: <a name="devfaq.master_sites"></a><a name="devfaq.master_sites.q"></a><p><b>24.5.</b></p>
1.78 rillig 10160: </td>
10161: <td align="left" valign="top"><p>What does
1.220 wiz 10162: <code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
10163: don't understand the <code class="code">:=</code> inside
1.78 rillig 10164: it.</p></td>
10165: </tr>
10166: <tr class="answer">
1.91 rillig 10167: <td align="left" valign="top"></td>
1.338 nia 10168: <td align="left" valign="top"><p>The <code class="code">:=</code> is not an
10169: assignment operator, even though it may look like one.
1.78 rillig 10170: Instead, it is a degenerate form of
1.220 wiz 10171: <code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
1.322 leot 10172: which is documented in the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which is
1.220 wiz 10173: commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the
1.78 rillig 10174: case of <code class="varname">MASTER_SITE_*</code>,
10175: <em class="replaceable"><code>old_string</code></em> is the empty string and
10176: <em class="replaceable"><code>new_string</code></em> is
1.220 wiz 10177: <code class="code">package/</code>. That's where the
10178: <code class="code">:</code> and the <code class="code">=</code> fall
1.78 rillig 10179: together.</p></td>
10180: </tr>
1.148 asau 10181: <tr class="question">
1.78 rillig 10182: <td align="left" valign="top">
1.338 nia 10183: <a name="devfaq.mailinglists"></a><a name="devfaq.mailinglists.q"></a><p><b>24.6.</b></p>
1.78 rillig 10184: </td>
10185: <td align="left" valign="top"><p>Which mailing lists are there for package
10186: developers?</p></td>
10187: </tr>
10188: <tr class="answer">
1.91 rillig 10189: <td align="left" valign="top"></td>
1.148 asau 10190: <td align="left" valign="top"><div class="variablelist"><dl class="variablelist">
1.289 leot 10191: <dt><span class="term"><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt>
1.78 rillig 10192: <dd><p>This is a list for technical discussions related
10193: to pkgsrc development, e.g. soliciting feedback for changes to
10194: pkgsrc infrastructure, proposed new features, questions related
10195: to porting pkgsrc to a new platform, advice for maintaining a
10196: package, patches that affect many packages, help requests moved
10197: from pkgsrc-users when an infrastructure bug is found,
10198: etc.</p></dd>
1.289 leot 10199: <dt><span class="term"><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt>
1.78 rillig 10200: <dd><p>All bug reports in category "pkg" sent with
1.322 leot 10201: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here
1.78 rillig 10202: directly; use one of the other mailing
10203: lists.</p></dd>
10204: </dl></div></td>
10205: </tr>
1.148 asau 10206: <tr class="question">
1.80 rillig 10207: <td align="left" valign="top">
1.338 nia 10208: <a name="devfaq.documentation"></a><a name="devfaq.documentation.q"></a><p><b>24.7.</b></p>
1.80 rillig 10209: </td>
10210: <td align="left" valign="top"><p>Where is the pkgsrc
10211: documentation?</p></td>
10212: </tr>
10213: <tr class="answer">
1.91 rillig 10214: <td align="left" valign="top"></td>
1.80 rillig 10215: <td align="left" valign="top">
10216: <p>There are many places where you can find
10217: documentation about pkgsrc:</p>
1.148 asau 10218: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 10219: <li class="listitem"><p>The pkgsrc guide (this document) is a collection
1.80 rillig 10220: of chapters that explain large parts of pkgsrc, but some
10221: chapters tend to be outdated. Which ones they are is hard to
10222: say.</p></li>
1.289 leot 10223: <li class="listitem"><p>On the mailing list archives (see <a class="ulink" href="https://mail-index.NetBSD.org/" target="_top">https://mail-index.NetBSD.org/</a>), you can find discussions
1.80 rillig 10224: about certain features, announcements of new parts of the pkgsrc
10225: infrastructure and sometimes even announcements that a certain
10226: feature has been marked as obsolete. The benefit here is that
10227: each message has a date appended to it.</p></li>
1.128 wiz 10228: <li class="listitem"><p>Many of the files in the
1.80 rillig 10229: <code class="filename">mk/</code> directory start with a comment that
10230: describes the purpose of the file and how it can be used by the
1.92 rillig 10231: pkgsrc user and package authors. An easy way to find this
1.110 hubertf 10232: documentation is to run <span class="command"><strong>bmake
1.92 rillig 10233: help</strong></span>.</p></li>
1.128 wiz 10234: <li class="listitem"><p>The CVS log messages are a rich source of
1.80 rillig 10235: information, but they tend to be highly abbreviated, especially
10236: for actions that occur often. Some contain a detailed
10237: description of what has changed, but they are geared towards the
10238: other pkgsrc developers, not towards an average pkgsrc user.
10239: They also only document <span class="emphasis"><em>changes</em></span>, so if you
10240: don't know what has been before, these messages may not be worth
10241: too much to you.</p></li>
1.128 wiz 10242: <li class="listitem"><p>Some parts of pkgsrc are only <span class="quote">“<span class="quote">implicitly
10243: documented</span>”</span>, that is the documentation exists only in the
1.80 rillig 10244: mind of the developer who wrote the code. To get this
1.110 hubertf 10245: information, use the <span class="command"><strong>cvs annotate</strong></span> command
1.80 rillig 10246: to see who has written it and ask on the
10247: <code class="literal">tech-pkg</code> mailing list, so that others can
10248: find your questions later (see above). To be sure that the
10249: developer in charge reads the mail, you may CC him or
10250: her.</p></li>
10251: </ul></div>
1.299 rillig 10252: </td>
10253: </tr>
10254: <tr class="question">
10255: <td align="left" valign="top">
1.338 nia 10256: <a name="devfaq.too-much-time"></a><a name="devfaq.too-much-time.q"></a><p><b>24.8.</b></p>
1.299 rillig 10257: </td>
1.338 nia 10258: <td align="left" valign="top"><p>I have a little time to kill.
1.299 rillig 10259: What shall I do?</p></td>
10260: </tr>
10261: <tr class="answer">
10262: <td align="left" valign="top"></td>
10263: <td align="left" valign="top">
10264: <p>This is not really an FAQ yet, but here's the answer
10265: anyway.</p>
1.148 asau 10266: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.299 rillig 10267: <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
1.322 leot 10268: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/index.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It
1.299 rillig 10269: will tell you about newer versions of installed packages that are
10270: available, but not yet updated in pkgsrc.</p></li>
10271: <li class="listitem"><p>Browse <code class="filename">pkgsrc/doc/TODO</code>
10272: — it contains a list of suggested new packages and a list of
10273: cleanups and enhancements for pkgsrc that would be nice to
10274: have.</p></li>
10275: <li class="listitem"><p>Review packages for which review was requested on
10276: the <a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a>
10277: mailing list.</p></li>
1.85 jmmv 10278: </ul></div>
1.299 rillig 10279: </td>
1.85 jmmv 10280: </tr>
10281: </tbody>
1.299 rillig 10282: </table>
1.85 jmmv 10283: </div>
10284: </div>
1.75 rillig 10285: </div>
1.148 asau 10286: <div class="part">
1.75 rillig 10287: <div class="titlepage"><div><div><h1 class="title">
10288: <a name="infrastructure"></a>Part III. The pkgsrc infrastructure internals</h1></div></div></div>
1.148 asau 10289: <div class="partintro">
1.75 rillig 10290: <div></div>
10291: <p>This part of the guide deals with everything
10292: from the infrastructure that is behind the interfaces described
10293: in the developer's guide. A casual package maintainer should not
10294: need anything from this part.</p>
10295: <div class="toc">
10296: <p><b>Table of Contents</b></p>
1.210 leot 10297: <dl class="toc">
1.299 rillig 10298: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.75 rillig 10299: <dd><dl>
1.299 rillig 10300: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10301: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10302: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.75 rillig 10303: <dd><dl>
1.299 rillig 10304: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10305: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.75 rillig 10306: </dl></dd>
1.299 rillig 10307: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10308: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.75 rillig 10309: <dd><dl>
1.299 rillig 10310: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10311: <dt><span class="sect2"><a href="#infr.design.intf.action">25.5.2. Actions taken on behalf of parameters</a></span></dt>
1.81 rillig 10312: </dl></dd>
1.299 rillig 10313: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.81 rillig 10314: <dd><dl>
1.299 rillig 10315: <dt><span class="sect2"><a href="#infr.order.prefs">25.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
10316: <dt><span class="sect2"><a href="#infr.order.pkg">25.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.75 rillig 10317: </dl></dd>
10318: </dl></dd>
1.299 rillig 10319: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.75 rillig 10320: <dd><dl>
1.299 rillig 10321: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10322: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.75 rillig 10323: <dd><dl>
1.299 rillig 10324: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10325: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.75 rillig 10326: </dl></dd>
10327: </dl></dd>
1.299 rillig 10328: <dt><span class="chapter"><a href="#porting">27. Porting pkgsrc</a></span></dt>
10329: <dd><dl><dt><span class="sect1"><a href="#porting.opsys">27.1. Porting pkgsrc to a new operating system</a></span></dt></dl></dd>
1.75 rillig 10330: </dl>
10331: </div>
10332: </div>
1.148 asau 10333: <div class="chapter">
1.75 rillig 10334: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 10335: <a name="infr.design"></a>Chapter 25. Design of the pkgsrc infrastructure</h2></div></div></div>
1.75 rillig 10336: <div class="toc">
10337: <p><b>Table of Contents</b></p>
1.210 leot 10338: <dl class="toc">
1.299 rillig 10339: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10340: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10341: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.81 rillig 10342: <dd><dl>
1.299 rillig 10343: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10344: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.81 rillig 10345: </dl></dd>
1.299 rillig 10346: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10347: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.75 rillig 10348: <dd><dl>
1.299 rillig 10349: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10350: <dt><span class="sect2"><a href="#infr.design.intf.action">25.5.2. Actions taken on behalf of parameters</a></span></dt>
1.75 rillig 10351: </dl></dd>
1.299 rillig 10352: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.75 rillig 10353: <dd><dl>
1.299 rillig 10354: <dt><span class="sect2"><a href="#infr.order.prefs">25.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
10355: <dt><span class="sect2"><a href="#infr.order.pkg">25.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.75 rillig 10356: </dl></dd>
10357: </dl>
10358: </div>
10359: <p>The pkgsrc infrastructure consists of many small Makefile
10360: fragments. Each such fragment needs a properly specified
10361: interface. This chapter explains how such an interface looks
10362: like.</p>
1.148 asau 10363: <div class="sect1">
1.75 rillig 10364: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10365: <a name="infr.vardef"></a>25.1. The meaning of variable definitions</h2></div></div></div>
1.81 rillig 10366: <p>Whenever a variable is defined in the pkgsrc
10367: infrastructure, the location and the way of definition provide
10368: much information about the intended use of that variable.
10369: Additionally, more documentation may be found in a header
10370: comment or in this pkgsrc guide.</p>
10371: <p>A special file is
10372: <code class="filename">mk/defaults/mk.conf</code>, which lists all
10373: variables that are intended to be user-defined. They are either
10374: defined using the <code class="literal">?=</code> operator or they are
10375: left undefined because defining them to anything would
1.128 wiz 10376: effectively mean <span class="quote">“<span class="quote">yes</span>”</span>. All these variables may be
1.81 rillig 10377: overridden by the pkgsrc user in the <code class="varname">MAKECONF</code>
10378: file.</p>
10379: <p>Outside this file, the following conventions apply:
10380: Variables that are defined using the <code class="literal">?=</code>
10381: operator may be overridden by a package.</p>
10382: <p>Variables that are defined using the <code class="literal">=</code>
10383: operator may be used read-only at run-time.</p>
10384: <p>Variables whose name starts with an underscore must not be
10385: accessed outside the pkgsrc infrastructure at all. They may
10386: change without further notice.</p>
1.148 asau 10387: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.81 rillig 10388: <h3 class="title">Note</h3>
10389: <p>These conventions are currently not applied
10390: consistently to the complete pkgsrc
10391: infrastructure.</p>
10392: </div>
10393: </div>
1.148 asau 10394: <div class="sect1">
1.81 rillig 10395: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10396: <a name="infr.vardef.problems"></a>25.2. Avoiding problems before they arise</h2></div></div></div>
1.81 rillig 10397: <p>All variables that contain lists of things should default
10398: to being empty. Two examples that do not follow this rule are
10399: <code class="varname">USE_LANGUAGES</code> and
10400: <code class="varname">DISTFILES</code>. These variables cannot simply be
10401: modified using the <code class="literal">+=</code> operator in package
10402: <code class="filename">Makefile</code>s (or other files included by
10403: them), since there is no guarantee whether the variable is
10404: already set or not, and what its value is. In the case of
1.128 wiz 10405: <code class="varname">DISTFILES</code>, the packages <span class="quote">“<span class="quote">know</span>”</span>
1.81 rillig 10406: the default value and just define it as in the following
10407: example.</p>
10408: <pre class="programlisting">
1.100 rillig 10409: DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz
1.81 rillig 10410: </pre>
10411: <p>Because of the selection of this default value, the same
10412: value appears in many package Makefiles. Similarly for
10413: <code class="varname">USE_LANGUAGES</code>, but in this case the default
1.128 wiz 10414: value (<span class="quote">“<span class="quote"><code class="literal">c</code></span>”</span>) is so short that it
1.81 rillig 10415: doesn't stand out. Nevertheless it is mentioned in many
10416: files.</p>
10417: </div>
1.148 asau 10418: <div class="sect1">
1.81 rillig 10419: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10420: <a name="infr.var"></a>25.3. Variable evaluation</h2></div></div></div>
1.148 asau 10421: <div class="sect2">
1.75 rillig 10422: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10423: <a name="infr.var.load"></a>25.3.1. At load time</h3></div></div></div>
1.75 rillig 10424: <p>Variable evaluation takes place either at load time or at
10425: runtime, depending on the context in which they occur. The
10426: contexts where variables are evaluated at load time are:</p>
1.148 asau 10427: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 10428: <li class="listitem"><p>The right hand side of the <code class="literal">:=</code>
1.75 rillig 10429: and <code class="literal">!=</code> operators,</p></li>
1.128 wiz 10430: <li class="listitem"><p>Make directives like <code class="literal">.if</code> or
1.75 rillig 10431: <code class="literal">.for</code>,</p></li>
1.128 wiz 10432: <li class="listitem"><p>Dependency lines.</p></li>
1.75 rillig 10433: </ul></div>
10434: <p>A special exception are references to the iteration
10435: variables of <code class="literal">.for</code> loops, which are expanded
10436: inline, no matter in which context they appear.</p>
10437: <p>As the values of variables may change during load time,
10438: care must be taken not to evaluate them by accident. Typical
10439: examples for variables that should not be evaluated at load time
10440: are <code class="varname">DEPENDS</code> and
10441: <code class="varname">CONFIGURE_ARGS</code>. To make the effect more
10442: clear, here is an example:</p>
10443: <pre class="programlisting">
1.100 rillig 10444: CONFIGURE_ARGS= # none
10445: CFLAGS= -O
10446: CONFIGURE_ARGS+= CFLAGS=${CFLAGS:Q}
1.1 grant 10447:
1.100 rillig 10448: CONFIGURE_ARGS:= ${CONFIGURE_ARGS}
1.1 grant 10449:
1.100 rillig 10450: CFLAGS+= -Wall
1.222 sevan 10451: </pre>
1.75 rillig 10452: <p>This code shows how the use of the <code class="literal">:=</code>
10453: operator can quickly lead to unexpected results. The first
10454: paragraph is fairly common code. The second paragraph evaluates
10455: the <code class="varname">CONFIGURE_ARGS</code> variable, which results in
10456: <code class="literal">CFLAGS=-O</code>. In the third paragraph, the
10457: <code class="literal">-Wall</code> is appended to the
10458: <code class="varname">CFLAGS</code>, but this addition will not appear in
10459: <code class="varname">CONFIGURE_ARGS</code>. In actual code, the three
10460: paragraphs from above typically occur in completely unrelated
10461: files.</p>
10462: </div>
1.148 asau 10463: <div class="sect2">
1.75 rillig 10464: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10465: <a name="infr.var.run"></a>25.3.2. At runtime</h3></div></div></div>
1.75 rillig 10466: <p>After all the files have been loaded, the values of the
10467: variables cannot be changed anymore. Variables that are used in
10468: the shell commands are expanded at this point.</p>
10469: </div>
10470: </div>
1.148 asau 10471: <div class="sect1">
1.75 rillig 10472: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10473: <a name="infr.varspec"></a>25.4. How can variables be specified?</h2></div></div></div>
1.78 rillig 10474: <p>There are many ways in which the definition and use of a
1.218 rillig 10475: variable can be restricted in order to detect bugs and violations
10476: of the (mostly unwritten) policies. A package can be checked with
10477: <code class="literal">pkglint -Wall</code> to see whether it meets these
10478: rules.</p>
1.78 rillig 10479: </div>
1.148 asau 10480: <div class="sect1">
1.78 rillig 10481: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10482: <a name="infr.design.intf"></a>25.5. Designing interfaces for Makefile fragments</h2></div></div></div>
1.76 rillig 10483: <p>Most of the <code class="filename">.mk</code> files fall into one
1.75 rillig 10484: of the following classes. Cases where a file falls into more
10485: than one class should be avoided as it often leads to subtle
10486: bugs.</p>
1.148 asau 10487: <div class="sect2">
1.75 rillig 10488: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10489: <a name="infr.design.intf.proc"></a>25.5.1. Procedures with parameters</h3></div></div></div>
1.75 rillig 10490: <p>In a traditional imperative programming language some of
1.76 rillig 10491: the <code class="filename">.mk</code> files could be described as
1.126 jakllsch 10492: procedures. They take some input parameters and—after
10493: inclusion—provide a result in output parameters. Since all
1.76 rillig 10494: variables in <code class="filename">Makefile</code>s have global scope
1.75 rillig 10495: care must be taken not to use parameter names that have already
10496: another meaning. For example, <code class="varname">PKGNAME</code> is a
10497: bad choice for a parameter name.</p>
10498: <p>Procedures are completely evaluated at preprocessing time.
10499: That is, when calling a procedure all input parameters must be
10500: completely resolvable. For example,
10501: <code class="varname">CONFIGURE_ARGS</code> should never be an input
10502: parameter since it is very likely that further text will be
10503: added after calling the procedure, which would effectively apply
10504: the procedure to only a part of the variable. Also, references
1.218 rillig 10505: to other variables will be modified after calling the
1.75 rillig 10506: procedure.</p>
10507: <p>A procedure can declare its output parameters either as
10508: suitable for use in preprocessing directives or as only
10509: available at runtime. The latter alternative is for variables
10510: that contain references to other runtime variables.</p>
10511: <p>Procedures shall be written such that it is possible to
10512: call the procedure more than once. That is, the file must not
10513: contain multiple-inclusion guards.</p>
10514: <p>Examples for procedures are
1.76 rillig 10515: <code class="filename">mk/bsd.options.mk</code> and
10516: <code class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express
1.75 rillig 10517: that the parameters are evaluated at load time, they should be
10518: assigned using the <code class="literal">:=</code> operator, which should
10519: be used only for this purpose.</p>
10520: </div>
1.148 asau 10521: <div class="sect2">
1.75 rillig 10522: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10523: <a name="infr.design.intf.action"></a>25.5.2. Actions taken on behalf of parameters</h3></div></div></div>
1.75 rillig 10524: <p>Action files take some input parameters and may define
10525: runtime variables. They shall not define loadtime variables.
10526: There are action files that are included implicitly by the
10527: pkgsrc infrastructure, while other must be included
10528: explicitly.</p>
10529: <p>An example for action files is
1.76 rillig 10530: <code class="filename">mk/subst.mk</code>.</p>
1.75 rillig 10531: </div>
10532: </div>
1.148 asau 10533: <div class="sect1">
1.81 rillig 10534: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10535: <a name="infr.order"></a>25.6. The order in which files are loaded</h2></div></div></div>
1.81 rillig 10536: <p>Package <code class="filename">Makefile</code>s usually consist of
10537: a set of variable definitions, and include the file
10538: <code class="filename">../../mk/bsd.pkg.mk</code> in the very last line.
10539: Before that, they may also include various other
10540: <code class="filename">*.mk</code> files if they need to query the
10541: availability of certain features like the type of compiler or
10542: the X11 implementation. Due to the heavy use of preprocessor
10543: directives like <code class="literal">.if</code> and
10544: <code class="literal">.for</code>, the order in which the files are loaded
10545: matters.</p>
10546: <p>This section describes at which point the various files
10547: are loaded and gives reasons for that order.</p>
1.148 asau 10548: <div class="sect2">
1.81 rillig 10549: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10550: <a name="infr.order.prefs"></a>25.6.1. The order in <code class="filename">bsd.prefs.mk</code>
1.93 rillig 10551: </h3></div></div></div>
10552: <p>The very first action in <code class="filename">bsd.prefs.mk</code>
1.81 rillig 10553: is to define some essential variables like
10554: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code> and
10555: <code class="varname">MACHINE_ARCH</code>.</p>
10556: <p>Then, the user settings are loaded from the file specified
1.110 hubertf 10557: in <code class="varname">MAKECONF</code>, which is usually <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.
1.104 rillig 10558: After that, those variables
1.81 rillig 10559: that have not been overridden by the user are loaded from
10560: <code class="filename">mk/defaults/mk.conf</code>.</p>
10561: <p>After the user settings, the system settings and platform
10562: settings are loaded, which may override the user
10563: settings.</p>
10564: <p>Then, the tool definitions are loaded. The tool wrappers
10565: are not yet in effect. This only happens when building a
10566: package, so the proper variables must be used instead of the
10567: direct tool names.</p>
10568: <p>As the last steps, some essential variables from the
10569: wrapper and the package system flavor are loaded, as well as the
10570: variables that have been cached in earlier phases of a package
10571: build.</p>
10572: </div>
1.148 asau 10573: <div class="sect2">
1.81 rillig 10574: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10575: <a name="infr.order.pkg"></a>25.6.2. The order in <code class="filename">bsd.pkg.mk</code>
1.93 rillig 10576: </h3></div></div></div>
1.81 rillig 10577: <p>First, <code class="filename">bsd.prefs.mk</code> is loaded.</p>
10578: <p>Then, the various <code class="filename">*-vars.mk</code> files are
10579: loaded, which fill default values for those variables that have
1.93 rillig 10580: not been defined by the package. These variables may later
1.81 rillig 10581: be used even in unrelated files.</p>
10582: <p>Then, the file <code class="filename">bsd.pkg.error.mk</code>
10583: provides the target <code class="literal">error-check</code> that is added
10584: as a special dependency to all other targets that use
10585: <code class="varname">DELAYED_ERROR_MSG</code> or
10586: <code class="varname">DELAYED_WARNING_MSG</code>.</p>
10587: <p>Then, the package-specific hacks from
10588: <code class="filename">hacks.mk</code> are included.</p>
10589: <p>Then, various other files follow. Most of them don't have
10590: any dependencies on what they need to have included before or
10591: after them, though some do.</p>
10592: <p>The code to check <code class="varname">PKG_FAIL_REASON</code> and
10593: <code class="varname">PKG_SKIP_REASON</code> is then executed, which
10594: restricts the use of these variables to all the files that have
10595: been included before. Appearances in later files will be
10596: silently ignored.</p>
10597: <p>Then, the files for the main targets are included, in the
10598: order of later execution, though the actual order should not
10599: matter.</p>
10600: <p>At last, some more files are included that don't set any
10601: interesting variables but rather just define make targets to be
10602: executed.</p>
10603: </div>
10604: </div>
1.75 rillig 10605: </div>
1.148 asau 10606: <div class="chapter">
1.75 rillig 10607: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 10608: <a name="regression"></a>Chapter 26. Regression tests</h2></div></div></div>
1.75 rillig 10609: <div class="toc">
10610: <p><b>Table of Contents</b></p>
1.210 leot 10611: <dl class="toc">
1.299 rillig 10612: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10613: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.75 rillig 10614: <dd><dl>
1.299 rillig 10615: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10616: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.75 rillig 10617: </dl></dd>
10618: </dl>
10619: </div>
10620: <p>The pkgsrc infrastructure consists of a large codebase,
10621: and there are many corners where every little bit of a file is
10622: well thought out, making pkgsrc likely to fail as soon as
10623: anything is changed near those parts. To prevent most changes
10624: from breaking anything, a suite of regression tests should go
10625: along with every important part of the pkgsrc infrastructure.
10626: This chapter describes how regression tests work in pkgsrc and
10627: how you can add new tests.</p>
1.148 asau 10628: <div class="sect1">
1.75 rillig 10629: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10630: <a name="regression.run"></a>26.1. Running the regression tests</h2></div></div></div>
1.322 leot 10631: <p>You first need to install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_regress/index.html" target="_top"><code class="filename">pkgtools/pkg_regress</code></a> package, which
1.110 hubertf 10632: provides the <span class="command"><strong>pkg_regress</strong></span> command. Then you
1.75 rillig 10633: can simply run that command, which will run all tests in the
1.283 rillig 10634: <code class="filename">regress/</code> directory.</p>
1.75 rillig 10635: </div>
1.148 asau 10636: <div class="sect1">
1.75 rillig 10637: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10638: <a name="regression.new"></a>26.2. Adding a new regression test</h2></div></div></div>
1.283 rillig 10639: <p>Every directory in the <code class="filename">regress/</code>
10640: directory that contains a file called <code class="filename">spec</code>
1.75 rillig 10641: is considered a regression test. This file is a shell program
1.110 hubertf 10642: that is included by the <span class="command"><strong>pkg_regress</strong></span> command.
1.75 rillig 10643: The following functions can be overridden to suit your
10644: needs.</p>
1.148 asau 10645: <div class="sect2">
1.75 rillig 10646: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10647: <a name="regression.fun.override"></a>26.2.1. Overridable functions</h3></div></div></div>
1.218 rillig 10648: <p>These functions do not take any parameters. Although they
10649: are called in <span class="quote">“<span class="quote">set -e</span>”</span> mode, they don't stop at the
1.289 leot 10650: first failing command. See <a class="ulink" href="https://stackoverflow.com/q/4072984" target="_top">this Stack Overflow
1.218 rillig 10651: question</a> for details.</p>
1.148 asau 10652: <div class="variablelist"><dl class="variablelist">
1.218 rillig 10653: <dt><span class="term"><code class="varname">do_setup</code></span></dt>
1.75 rillig 10654: <dd><p>This function prepares the environment for the
10655: test. By default it does nothing.</p></dd>
1.218 rillig 10656: <dt><span class="term"><code class="varname">do_test</code></span></dt>
10657: <dd>
10658: <p>This function runs the actual test. By default,
1.75 rillig 10659: it calls <code class="varname">TEST_MAKE</code> with the arguments
10660: <code class="varname">MAKEARGS_TEST</code> and writes its output including
10661: error messages into the file
1.218 rillig 10662: <code class="varname">TEST_OUTFILE</code>.</p>
10663: <p>When defining this function, make sure that all output that
10664: needs to be checked is written to the correct output file.
10665: Example:</p>
10666: <pre class="programlisting">
10667: do_test() {
1.223 rillig 10668: echo "Example output"
1.218 rillig 10669: } 1>$TEST_OUTFILE 2>&1
10670: </pre>
10671: </dd>
10672: <dt><span class="term"><code class="varname">check_result</code></span></dt>
10673: <dd>
10674: <p>This function is run after the test and is
1.75 rillig 10675: typically used to compare the actual output from the one that is
10676: expected. It can make use of the various helper functions from
1.218 rillig 10677: the next section. Example:</p>
10678: <pre class="programlisting">
10679: check_result() {
1.223 rillig 10680: exit_status 0
10681: output_require "Example"
10682: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
10683: output_prohibit "no such file or directory"
1.283 rillig 10684: regress_fail "expected $expected but got $actual for input $input"
1.218 rillig 10685: }
10686: </pre>
10687: </dd>
10688: <dt><span class="term"><code class="varname">do_cleanup</code></span></dt>
1.75 rillig 10689: <dd><p>This function cleans everything up after the
10690: test has been run. By default it does nothing.</p></dd>
10691: </dl></div>
10692: </div>
1.148 asau 10693: <div class="sect2">
1.75 rillig 10694: <div class="titlepage"><div><div><h3 class="title">
1.299 rillig 10695: <a name="regression.fun.helper"></a>26.2.2. Helper functions</h3></div></div></div>
1.148 asau 10696: <div class="variablelist"><dl class="variablelist">
1.283 rillig 10697: <dt><span class="term"><code class="varname">regress_fail <em class="replaceable"><code>message...</code></em></code></span></dt>
10698: <dd><p>This function makes the test fail with the given error message.</p></dd>
1.218 rillig 10699: <dt><span class="term"><code class="varname">exit_status expected</code></span></dt>
1.75 rillig 10700: <dd><p>This function compares the exitcode of the
1.218 rillig 10701: <span class="command"><strong>do_test</strong></span> function with its first parameter.
1.75 rillig 10702: If they differ, the test will fail.</p></dd>
1.218 rillig 10703: <dt><span class="term"><code class="varname">output_require regex...</code></span></dt>
10704: <dd>
10705: <p>This function checks for each of its parameters
10706: if the output from <span class="command"><strong>do_test</strong></span> matches the
1.75 rillig 10707: extended regular expression. If it does not, the test will
1.218 rillig 10708: fail. Example:</p>
10709: <pre class="programlisting">
1.219 rillig 10710: output_require "looks fine"
10711: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
1.218 rillig 10712: </pre>
10713: </dd>
1.292 leot 10714: <dt><span class="term"><code class="varname">output_prohibit regex...</code></span></dt>
1.75 rillig 10715: <dd><p>This function checks for each of its parameters
1.110 hubertf 10716: if the output from <span class="command"><strong>do_test()</strong></span> does
1.75 rillig 10717: <span class="emphasis"><em>not</em></span> match the extended regular expression.
10718: If any of the regular expressions matches, the test will
10719: fail.</p></dd>
10720: </dl></div>
10721: </div>
10722: </div>
10723: </div>
1.148 asau 10724: <div class="chapter">
1.75 rillig 10725: <div class="titlepage"><div><div><h2 class="title">
1.299 rillig 10726: <a name="porting"></a>Chapter 27. Porting pkgsrc</h2></div></div></div>
1.75 rillig 10727: <div class="toc">
10728: <p><b>Table of Contents</b></p>
1.299 rillig 10729: <dl class="toc"><dt><span class="sect1"><a href="#porting.opsys">27.1. Porting pkgsrc to a new operating system</a></span></dt></dl>
1.75 rillig 10730: </div>
10731: <p>The pkgsrc system has already been ported to many
10732: operating systems, hardware architectures and compilers. This
10733: chapter explains the necessary steps to make pkgsrc even more
10734: portable.</p>
1.148 asau 10735: <div class="sect1">
1.75 rillig 10736: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.299 rillig 10737: <a name="porting.opsys"></a>27.1. Porting pkgsrc to a new operating system</h2></div></div></div>
1.75 rillig 10738: <p>To port pkgsrc to a new operating system (called
10739: <code class="literal">MyOS</code> in this example), you need to touch the
10740: following files:</p>
1.148 asau 10741: <div class="variablelist"><dl class="variablelist">
1.93 rillig 10742: <dt><span class="term"><code class="filename">pkgtools/bootstrap-mk-files/files/mods/<em class="replaceable"><code>MyOS</code></em>.sys.mk</code></span></dt>
1.75 rillig 10743: <dd><p>This file contains some basic definitions, for
10744: example the name of the C
10745: compiler.</p></dd>
1.76 rillig 10746: <dt><span class="term"><code class="filename">mk/bsd.prefs.mk</code></span></dt>
1.75 rillig 10747: <dd><p>Insert code that defines the variables
10748: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code>,
1.327 wiz 10749: <code class="varname">OPSYS_VERSION</code>, <code class="varname">LOWER_VENDOR</code>,
1.75 rillig 10750: <code class="varname">MACHINE_ARCH</code>, <code class="varname">OBJECT_FMT</code>,
10751: <code class="varname">APPEND_ELF</code>, and the other variables that
10752: appear in this file.</p></dd>
1.93 rillig 10753: <dt><span class="term"><code class="filename">mk/platform/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
1.75 rillig 10754: <dd><p>This file contains the platform-specific
10755: definitions that are used by pkgsrc. Start by copying one of the
10756: other files and edit it to your
10757: needs.</p></dd>
1.93 rillig 10758: <dt><span class="term"><code class="filename">mk/tools/tools.<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
1.75 rillig 10759: <dd><p>This file defines the paths to all the tools
10760: that are needed by one or the other package in pkgsrc, as well
10761: as by pkgsrc itself. Find out where these tools are on your
10762: platform and add them.</p></dd>
10763: </dl></div>
10764: <p>Now, you should be able to build some basic packages, like
1.322 leot 10765: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/perl5/index.html" target="_top"><code class="filename">lang/perl5</code></a>, <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/index.html" target="_top"><code class="filename">shells/bash</code></a>.</p>
1.75 rillig 10766: </div>
10767: </div>
10768: </div>
1.148 asau 10769: <div class="appendix">
10770: <div class="titlepage"><div><div><h1 class="title">
10771: <a name="examples"></a>Appendix A. A simple example package: bison</h1></div></div></div>
1.75 rillig 10772: <div class="toc">
10773: <p><b>Table of Contents</b></p>
1.210 leot 10774: <dl class="toc">
1.75 rillig 10775: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
10776: <dd><dl>
10777: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
10778: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
10779: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.287 rillig 10780: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.75 rillig 10781: </dl></dd>
10782: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
10783: </dl>
10784: </div>
10785: <p>We checked to find a piece of software that wasn't in the packages
10786: collection, and picked GNU bison. Quite why someone would want to have
1.110 hubertf 10787: <span class="command"><strong>bison</strong></span> when Berkeley <span class="command"><strong>yacc</strong></span> is already
1.75 rillig 10788: present in the tree is beyond us, but it's useful for the purposes of
10789: this exercise.</p>
1.148 asau 10790: <div class="sect1">
1.75 rillig 10791: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10792: <a name="example-files"></a>A.1. files</h2></div></div></div>
1.148 asau 10793: <div class="sect2">
1.75 rillig 10794: <div class="titlepage"><div><div><h3 class="title">
10795: <a name="example-Makefile"></a>A.1.1. Makefile</h3></div></div></div>
10796: <pre class="programlisting">
1.100 rillig 10797: # $NetBSD$
10798: #
1.1 grant 10799:
1.100 rillig 10800: DISTNAME= bison-1.25
10801: CATEGORIES= devel
1.286 rillig 10802: MASTER_SITES= ${MASTER_SITE_GNU:=bison/}
1.1 grant 10803:
1.136 dholland 10804: MAINTAINER= pkgsrc-users@NetBSD.org
1.289 leot 10805: HOMEPAGE= https://www.gnu.org/software/bison/bison.html
1.100 rillig 10806: COMMENT= GNU yacc clone
1.1 grant 10807:
1.100 rillig 10808: GNU_CONFIGURE= yes
1.152 wiz 10809: INFO_FILES= yes
1.1 grant 10810:
1.100 rillig 10811: .include "../../mk/bsd.pkg.mk"
1.1 grant 10812: </pre>
1.75 rillig 10813: </div>
1.148 asau 10814: <div class="sect2">
1.75 rillig 10815: <div class="titlepage"><div><div><h3 class="title">
10816: <a name="example-descr"></a>A.1.2. DESCR</h3></div></div></div>
10817: <pre class="programlisting">
1.100 rillig 10818: GNU version of yacc. Can make re-entrant parsers, and numerous other
1.322 leot 10819: improvements. Why you would want this when Berkeley <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/yacc.1"><span class="citerefentry"><span class="refentrytitle">yacc</span>(1)</span></a> is part
1.100 rillig 10820: of the NetBSD source tree is beyond me.
1.1 grant 10821: </pre>
1.75 rillig 10822: </div>
1.148 asau 10823: <div class="sect2">
1.75 rillig 10824: <div class="titlepage"><div><div><h3 class="title">
10825: <a name="example-plist"></a>A.1.3. PLIST</h3></div></div></div>
10826: <pre class="programlisting">
1.100 rillig 10827: @comment $NetBSD$
10828: bin/bison
10829: man/man1/bison.1.gz
10830: share/bison.simple
10831: share/bison.hairy
1.1 grant 10832: </pre>
1.75 rillig 10833: </div>
1.148 asau 10834: <div class="sect2">
1.75 rillig 10835: <div class="titlepage"><div><div><h3 class="title">
1.287 rillig 10836: <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with pkglint</h3></div></div></div>
1.75 rillig 10837: <p>The NetBSD package system comes with
1.322 leot 10838: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/index.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>
1.75 rillig 10839: which helps to check the contents of these
10840: files. After installation it is quite easy to use, just change to the
1.286 rillig 10841: directory of the package you wish to examine and run
1.110 hubertf 10842: <span class="command"><strong>pkglint</strong></span>:</p>
1.75 rillig 10843: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>pkglint</code></strong>
1.286 rillig 10844: ERROR: Makefile: Each package must define its LICENSE.
10845: WARN: Makefile:9: HOMEPAGE should migrate from http to https.
10846: NOTE: PLIST:3: The .gz extension is unnecessary for manual pages.
10847: WARN: PLIST:5: "share/bison.hairy" should be sorted before "share/bison.simple".
10848: 1 error, 2 warnings and 1 note found.
10849: (Run "pkglint -e" to show explanations.)
10850: (Run "pkglint -fs" to show what can be fixed automatically.)
1.287 rillig 10851: (Run "pkglint -F" to automatically fix some issues.)</pre>
1.75 rillig 10852: <p>Depending on the supplied command line arguments (see pkglint(1)),
1.285 rillig 10853: more checks will be performed. Use e.g. <span class="command"><strong>pkglint
1.75 rillig 10854: -Wall</strong></span> for a very thorough check.</p>
10855: </div>
10856: </div>
1.148 asau 10857: <div class="sect1">
1.75 rillig 10858: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10859: <a name="steps-for-b-i-p"></a>A.2. Steps for building, installing, packaging</h2></div></div></div>
10860: <p>Create the directory where the package lives,
10861: plus any auxiliary directories:</p>
10862: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/pkgsrc/lang</code></strong>
10863: <code class="prompt">#</code> <strong class="userinput"><code>mkdir bison</code></strong>
10864: <code class="prompt">#</code> <strong class="userinput"><code>cd bison</code></strong>
10865: <code class="prompt">#</code> <strong class="userinput"><code>mkdir patches</code></strong></pre>
1.76 rillig 10866: <p>Create <code class="filename">Makefile</code>, <code class="filename">DESCR</code> and
1.299 rillig 10867: <code class="filename">PLIST</code> (see <a class="xref" href="#components" title="Chapter 12. Package components - files, directories and contents">Chapter 12, <i>Package components - files, directories and contents</i></a>)
1.75 rillig 10868: then continue with fetching the distfile:</p>
10869: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make fetch</code></strong>
1.1 grant 10870: >> bison-1.25.tar.gz doesn't seem to exist on this system.
10871: >> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
10872: Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10873: ftp: Error retrieving file: 500 Internal error
10874:
10875: >> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
10876: Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10877: ftp: Error retrieving file: 500 Internal error
10878:
10879: >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
10880: Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
1.75 rillig 10881: Successfully retrieved file.</pre>
10882: <p>Generate the checksum of the distfile into
1.76 rillig 10883: <code class="filename">distinfo</code>:</p>
1.88 wiz 10884: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make makedistinfo</code></strong></pre>
1.75 rillig 10885: <p>Now compile:</p>
10886: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
1.1 grant 10887: >> Checksum OK for bison-1.25.tar.gz.
10888: ===> Extracting for bison-1.25
10889: ===> Patching for bison-1.25
10890: ===> Ignoring empty patch directory
10891: ===> Configuring for bison-1.25
10892: creating cache ./config.cache
10893: checking for gcc... cc
10894: checking whether we are using GNU C... yes
10895: checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
10896: checking how to run the C preprocessor... cc -E
10897: checking for minix/config.h... no
10898: checking for POSIXized ISC... no
10899: checking whether cross-compiling... no
10900: checking for ANSI C header files... yes
10901: checking for string.h... yes
10902: checking for stdlib.h... yes
10903: checking for memory.h... yes
10904: checking for working const... yes
10905: checking for working alloca.h... no
10906: checking for alloca... yes
10907: checking for strerror... yes
10908: updating cache ./config.cache
10909: creating ./config.status
10910: creating Makefile
10911: ===> Building for bison-1.25
10912: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g LR0.c
10913: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g allocate.c
10914: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g closure.c
10915: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g conflicts.c
10916: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g derives.c
1.68 rillig 10917: cc -c -DXPFILE=\"/usr/pkg/share/bison.simple\" -DXPFILE1=\"/usr/pkg/share/bison.hairy\" -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -g ./files.c
1.1 grant 10918: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getargs.c
10919: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g gram.c
10920: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g lalr.c
10921: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g lex.c
10922: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g main.c
10923: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g nullable.c
10924: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g output.c
10925: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g print.c
10926: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g reader.c
10927: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g reduce.c
10928: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g symtab.c
10929: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g warshall.c
10930: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g version.c
10931: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getopt.c
10932: cc -c -DSTDC_HEADERS=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MEMORY_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRERROR=1 -I./../include -g getopt1.c
10933: cc -g -o bison LR0.o allocate.o closure.o conflicts.o derives.o files.o getargs.o gram.o lalr.o lex.o main.o nullable.o output.o print.o reader.o reduce.o symtab.o warshall.o version.o getopt.o getopt1.o
10934: ./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
10935: rm -f bison.s1
1.75 rillig 10936: sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1</pre>
10937: <p>Everything seems OK, so install the files:</p>
10938: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
1.1 grant 10939: >> Checksum OK for bison-1.25.tar.gz.
10940: ===> Installing for bison-1.25
10941: sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
10942: rm -f /usr/pkg/bin/bison
10943: cd /usr/pkg/share; rm -f bison.simple bison.hairy
10944: rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
10945: install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
10946: /usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
10947: /usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
10948: cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
10949: /usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
1.75 rillig 10950: ===> Registering installation for bison-1.25</pre>
10951: <p>You can now use bison, and also - if you decide so - remove it with
1.110 hubertf 10952: <span class="command"><strong>pkg_delete bison</strong></span>. Should you decide that you want a
1.75 rillig 10953: binary package, do this now:</p>
10954: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
1.1 grant 10955: >> Checksum OK for bison-1.25.tar.gz.
10956: ===> Building package for bison-1.25
10957: Creating package bison-1.25.tgz
10958: Registering depends:.
1.75 rillig 10959: Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre>
10960: <p>Now that you don't need the source and object files
10961: any more, clean up:</p>
10962: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make clean</code></strong>
10963: ===> Cleaning for bison-1.25</pre>
10964: </div>
10965: </div>
1.148 asau 10966: <div class="appendix">
10967: <div class="titlepage"><div><div><h1 class="title">
1.322 leot 10968: <a name="hardening"></a>Appendix B. Security hardening</h1></div></div></div>
1.75 rillig 10969: <div class="toc">
10970: <p><b>Table of Contents</b></p>
1.210 leot 10971: <dl class="toc">
1.322 leot 10972: <dt><span class="sect1"><a href="#hardening.mechanisms">B.1. Mechanisms</a></span></dt>
10973: <dd><dl>
10974: <dt><span class="sect2"><a href="#hardening.mechanisms.enabled">B.1.1. Enabled by default</a></span></dt>
10975: <dt><span class="sect2"><a href="#hardening.mechanisms.disabled">B.1.2. Not enabled by default</a></span></dt>
10976: </dl></dd>
10977: <dt><span class="sect1"><a href="#hardening.caveats">B.2. Caveats</a></span></dt>
10978: <dd><dl>
10979: <dt><span class="sect2"><a href="#hardening.caveats.pie">B.2.1. Problems with PKGSRC_MKPIE</a></span></dt>
10980: <dt><span class="sect2"><a href="#hardening.caveats.fortify">B.2.2. Problems with PKGSRC_USE_FORTIFY</a></span></dt>
10981: <dt><span class="sect2"><a href="#hardening.caveats.relro">B.2.3. Problems with PKGSRC_USE_RELRO</a></span></dt>
10982: <dt><span class="sect2"><a href="#hardening.caveats.ssp">B.2.4. Problems with PKGSRC_USE_SSP</a></span></dt>
10983: </dl></dd>
10984: <dt><span class="sect1"><a href="#hardening.audit">B.3. Auditing the system</a></span></dt>
10985: <dd><dl>
10986: <dt><span class="sect2"><a href="#hardening.audit.pie">B.3.1. Checking for PIE</a></span></dt>
10987: <dt><span class="sect2"><a href="#hardening.audit.relropartial">B.3.2. Checking for partial RELRO</a></span></dt>
10988: <dt><span class="sect2"><a href="#hardening.audit.relrofull">B.3.3. Checking for full RELRO</a></span></dt>
10989: <dt><span class="sect2"><a href="#hardening.audit.ssp">B.3.4. Checking for SSP</a></span></dt>
10990: </dl></dd>
1.75 rillig 10991: </dl>
10992: </div>
1.322 leot 10993: <p>
10994: A number of mechanisms are available in pkgsrc to improve the security of the
10995: resulting system. This page describes the mechanisms, and gives hints
10996: about detecting and fixing problems.
10997: </p>
10998: <p>
10999: Mechanisms can be enabled individually in
11000: <code class="filename">mk.conf</code>, and are
11001: individually described below.
11002: </p>
11003: <p>
11004: Typically, a feature will cause some programs to fail to build or work
11005: when first enabled. This can be due to latent problems in the
11006: program, and can be due to other reasons. After enough testing to
11007: have confidence that user problems will be quite rare, individual
11008: mechanisms will be enabled by default.
11009: </p>
11010: <p>
11011: For each mechanism, see the Caveats section below for an explanation
11012: of what might go wrong at compile time and at run time, and how to
11013: notice and address these problems.
11014: </p>
1.148 asau 11015: <div class="sect1">
1.75 rillig 11016: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.322 leot 11017: <a name="hardening.mechanisms"></a>B.1. Mechanisms</h2></div></div></div>
11018: <div class="sect2">
11019: <div class="titlepage"><div><div><h3 class="title">
11020: <a name="hardening.mechanisms.enabled"></a>B.1.1. Enabled by default</h3></div></div></div>
11021: <div class="sect3">
11022: <div class="titlepage"><div><div><h4 class="title">
11023: <a name="hardening.mechanisms.enabled.fortify"></a>B.1.1.1. PKGSRC_USE_FORTIFY</h4></div></div></div>
11024: <p>
11025: This allows substitute wrappers to be used for some commonly used
11026: library functions that do not have built-in bounds checking - but
11027: could in some cases.
11028: </p>
11029: <p>
11030: Two mitigation levels are available:
11031: </p>
11032: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11033: <li class="listitem"><p>"weak" only enables checks at compile-time.</p></li>
11034: <li class="listitem"><p>"strong" enables checks at compile-time and runtime.</p></li>
11035: </ul></div>
11036: <p>
11037: "strong" has been enabled by default since pkgsrc-2017Q3.
11038: </p>
11039: </div>
11040: <div class="sect3">
11041: <div class="titlepage"><div><div><h4 class="title">
11042: <a name="hardening.mechanisms.enabled.ssp"></a>B.1.1.2. PKGSRC_USE_SSP</h4></div></div></div>
11043: <p>
11044: This enables a stack-smashing protection mitigation. It is done by adding a
11045: guard variable to functions with vulnerable objects. The guards are initialized
11046: when a function is entered and then checked when the function exits. The guard
11047: check will fail and the program forcibly exited if the variable was modified in
11048: the meantime. This can happen in case of buffer overflows or memory corruption,
11049: and therefore exposing these bugs.
11050: </p>
11051: <p>
11052: Different mitigation levels are available:
11053: </p>
11054: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11055: <li class="listitem"><p>"yes", which will only protect functions considered vulnerable
11056: by the compiler;</p></li>
11057: <li class="listitem"><p>"all", which will protect every function;</p></li>
11058: <li class="listitem"><p>"strong", the default, which will apply a better balance between the
11059: two settings above.</p></li>
11060: </ul></div>
11061: <p>
11062: This mitigation is supported by both GCC and clang. It may be supported in
11063: additional compilers, possibly under a different name. It is particularly useful
11064: for unsafe programming languages, such as C/C++.
11065: </p>
11066: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11067: <li class="listitem"><p>"yes" is enabled by default where known supported since pkgsrc-2017Q3.</p></li>
11068: <li class="listitem"><p>"strong" is enabled by default where known supported since pkgsrc-2021Q4.</p></li>
11069: </ul></div>
11070: <p>More details can be found here:</p>
11071: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11072: <a class="ulink" href="https://en.wikipedia.org/wiki/Buffer_overflow_protection" target="_top">Buffer overflow protection on Wikipedia</a>
11073: </p></li></ul></div>
11074: </div>
11075: <div class="sect3">
11076: <div class="titlepage"><div><div><h4 class="title">
11077: <a name="hardening.mechanisms.enabled.pie"></a>B.1.1.3. PKGSRC_MKPIE</h4></div></div></div>
11078: <p>
11079: This requests the creation of PIE (Position Independent Executables) for all
11080: executables. The PIE mechanism is normally used for shared libraries, so that
11081: they can be loaded at differing addresses at runtime. PIE itself does not have
11082: useful security properties; however, it is necessary to fully leverage some,
11083: such as ASLR. Some operating systems support Address Space Layout Randomization
11084: (ASLR), which causes different addresses to be used each time a program is run.
11085: This makes it more difficult for an attacker to guess addresses and thus makes
11086: exploits harder to construct. With PIE, ASLR can really be applied to the entire
11087: program, instead of the stack and heap only.
11088: </p>
11089: <p>
11090: PIE executables will only be built for toolchains that are known to support PIE.
11091: Currently, this means NetBSD on x86, ARM, SPARC64, m68k, and MIPS.
11092: </p>
11093: <p>
11094: <code class="varname">PKGSRC_MKPIE</code> was enabled by default after the pkgsrc-2021Q3 branch.
11095: </p>
1.75 rillig 11096: </div>
1.325 gutterid 11097: <div class="sect3">
11098: <div class="titlepage"><div><div><h4 class="title">
1.334 nia 11099: <a name="hardening.mechanisms.enabled.relro"></a>B.1.1.4. PKGSRC_USE_RELRO</h4></div></div></div>
1.322 leot 11100: <p>
11101: This also makes the exploitation of some security vulnerabilities more
11102: difficult in some cases.
11103: </p>
11104: <p>Two different mitigation levels are available:</p>
11105: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11106: <li class="listitem"><p>
1.334 nia 11107: partial (the default): the ELF sections are reordered so that internal data sections
1.322 leot 11108: precede the program's own data sections, and non-PLT GOT is read-only;
11109: </p></li>
11110: <li class="listitem"><p>
11111: full: in addition to partial RELRO, every relocation is performed immediately
1.333 nia 11112: when starting the program, allowing the entire GOT to be read-only. This
11113: can greatly slow down startup of large programs.
1.322 leot 11114: </p></li>
11115: </ul></div>
11116: <p>
11117: This is currently supported by GCC. Many software distributions now enable this
1.335 nia 11118: feature by default, at the "partial" level.
1.322 leot 11119: </p>
11120: <p>
11121: More details can be found here:
11122: </p>
11123: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11124: <a class="ulink" href="https://www.redhat.com/en/blog/hardening-elf-binaries-using-relocation-read-only-relro" target="_top">Hardening ELF binaries using Relocation Read-Only (RELRO)</a>
11125: </p></li></ul></div>
1.75 rillig 11126: </div>
1.334 nia 11127: </div>
11128: <div class="sect2">
11129: <div class="titlepage"><div><div><h3 class="title">
11130: <a name="hardening.mechanisms.disabled"></a>B.1.2. Not enabled by default</h3></div></div></div>
11131: <div class="sect3">
11132: <div class="titlepage"><div><div><h4 class="title">
11133: <a name="hardening.mechanisms.disabled.repro"></a>B.1.2.1. PKGSRC_MKREPRO</h4></div></div></div>
11134: <p>
11135: With this option, pkgsrc will try to build packages reproducibly. This allows
11136: packages built from the same tree and with the same options, to produce
11137: identical results bit by bit. This option should be combined with ASLR and
11138: <code class="varname">PKGSRC_MKPIE</code> to avoid predictable address offsets for
11139: attackers attempting to exploit security vulnerabilities.
11140: </p>
11141: <p>
11142: More details can be found here:
11143: </p>
11144: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11145: <a class="ulink" href="https://reproducible-builds.org/" target="_top">Reproducible Builds - a set of software development practices that create an independently-verifiable path from source to binary code</a>
11146: </p></li></ul></div>
11147: <p>
11148: More work likely needs to be done before pkgsrc is fully reproducible.
11149: </p>
11150: </div>
1.322 leot 11151: <div class="sect3">
11152: <div class="titlepage"><div><div><h4 class="title">
1.334 nia 11153: <a name="hardening.mechanisms.disabled.stackcheck"></a>B.1.2.2. PKGSRC_USE_STACK_CHECK</h4></div></div></div>
1.322 leot 11154: <p>
11155: This uses <code class="literal">-fstack-check</code> with GCC for
11156: another stack protection mitigation.
11157: </p>
11158: <p>
11159: It asks the compiler to generate code verifying that it does not corrupt the
11160: stack. According to GCC's manual page, this is really only useful for
11161: multi-threaded programs.
11162: </p>
1.76 rillig 11163: </div>
11164: </div>
11165: </div>
1.148 asau 11166: <div class="sect1">
1.76 rillig 11167: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.322 leot 11168: <a name="hardening.caveats"></a>B.2. Caveats</h2></div></div></div>
11169: <div class="sect2">
11170: <div class="titlepage"><div><div><h3 class="title">
11171: <a name="hardening.caveats.pie"></a>B.2.1. Problems with PKGSRC_MKPIE</h3></div></div></div>
11172: <div class="sect3">
11173: <div class="titlepage"><div><div><h4 class="title">
11174: <a name="hardening.caveats.pie.build"></a>B.2.1.1. Packages failing to build</h4></div></div></div>
11175: <p>
11176: A number of packages may fail to build with this option enabled. The
11177: failures are often related to the absence of the <code class="literal">-fPIC</code>
11178: compilation flag when building libraries or executables (or ideally
11179: <code class="literal">-fPIE</code> in the latter case). This flag is added to the
11180: <code class="varname">CFLAGS</code> already, but requires the package to
11181: actually support it.
11182: </p>
11183: <div class="sect4">
11184: <div class="titlepage"><div><div><h5 class="title">
11185: <a name="hardening.caveats.pie.build.fix"></a>B.2.1.1.1. How to fix</h5></div></div></div>
11186: <p>
11187: These instructions are meant as a reference only; they likely need to be adapted
11188: for many packages individually.
11189: </p>
11190: <p>
11191: For packages using <code class="filename">Makefiles</code>:
11192: </p>
11193: <pre class="programlisting">
11194: MAKE_FLAGS+= CFLAGS=${CFLAGS:Q}
11195: MAKE_FLAGS+= LDFLAGS=${LDFLAGS:Q}
11196: </pre>
11197: <p>
11198: For packages using <code class="filename">Imakefiles</code>:
11199: </p>
11200: <pre class="programlisting">
11201: MAKE_FLAGS+= CCOPTIONS=${CFLAGS:Q}
11202: MAKE_FLAGS+= LOCAL_LDFLAGS=${LDFLAGS:Q}
11203: </pre>
11204: </div>
11205: </div>
11206: <div class="sect3">
11207: <div class="titlepage"><div><div><h4 class="title">
11208: <a name="hardening.caveats.pie.crash"></a>B.2.1.2. Run-time crashes</h4></div></div></div>
11209: <p>
11210: Some programs may fail to run, or crash at random times once built as PIE. Two
11211: scenarios are essentially possible. This is nearly always due to a bug in
11212: the program being exposed due to ASLR.
11213: </p>
11214: </div>
11215: <div class="sect3">
11216: <div class="titlepage"><div><div><h4 class="title">
11217: <a name="hardening.caveats.pie.disable"></a>B.2.1.3. Disabling PKGSRC_MKPIE on a per-package basis</h4></div></div></div>
11218: <p>
11219: Ideally, packages should be fixed for compatibility with MKPIE.
11220: However, in some cases this is very difficult, due to complex build systems,
11221: packages using non-standard toolchains, or programming languages with odd
11222: bootstrapping mechanisms.
11223: </p>
11224: <p>
11225: To disable <code class="varname">PKGSRC_MKPIE</code> on a per-package basis, set
11226: <code class="varname">MKPIE_SUPPORTED= no</code> in the package's Makefile before
11227: <code class="filename">bsd.prefs.mk</code> is included.
11228: </p>
11229: </div>
11230: </div>
11231: <div class="sect2">
11232: <div class="titlepage"><div><div><h3 class="title">
11233: <a name="hardening.caveats.fortify"></a>B.2.2. Problems with PKGSRC_USE_FORTIFY</h3></div></div></div>
11234: <div class="sect3">
11235: <div class="titlepage"><div><div><h4 class="title">
11236: <a name="hardening.caveats.fortify.build"></a>B.2.2.1. Packages failing to build</h4></div></div></div>
11237: <p>
11238: This feature makes use of pre-processing directives to look for hardened,
11239: alternative implementations of essential library calls. Some programs may fail
11240: to build as a result; this usually happens for those trying too hard to be
11241: portable, or otherwise abusing definitions in the standard library.
11242: </p>
11243: </div>
11244: <div class="sect3">
11245: <div class="titlepage"><div><div><h4 class="title">
11246: <a name="hardening.caveats.fortify.crash"></a>B.2.2.2. Run-time crashes</h4></div></div></div>
11247: <p>
11248: This feature may cause some programs to crash, usually indicating an
11249: actual bug in the program. The fix will typically involve patching the
11250: original program's source code.
11251: </p>
11252: </div>
11253: <div class="sect3">
11254: <div class="titlepage"><div><div><h4 class="title">
11255: <a name="hardening.caveats.fortify.opt"></a>B.2.2.3. Optimization is required</h4></div></div></div>
11256: <p>
11257: At least in the case of GCC, FORTIFY will only be applied if optimization is
11258: applied while compiling. This means that the <code class="varname">CFLAGS</code> should
11259: also contain <code class="literal">-O</code>, <code class="literal">-O2</code> or another
11260: optimization level. This cannot easily be applied globally, as some packages
11261: may require specific optimization levels.
11262: </p>
11263: </div>
11264: <div class="sect3">
11265: <div class="titlepage"><div><div><h4 class="title">
11266: <a name="hardening.caveats.fortify.disable"></a>B.2.2.4. Disabling FORTIFY on a per-package basis</h4></div></div></div>
11267: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11268: <h3 class="title">Note</h3>
11269: <p>FORTIFY should not be disabled to work around runtime crashes in
11270: the program! This is a very bad idea and will expose you to security
11271: vulnerabilities.
11272: </p>
11273: </div>
11274: <p>
11275: To disable FORTIFY on a per-package basis, set the following
11276: in the package's <code class="filename">Makefile</code>
11277: before <code class="filename">bsd.prefs.mk</code> is included:
11278: </p>
11279: <pre class="programlisting">
11280: FORTIFY_SUPPORTED= no
11281: </pre>
11282: </div>
11283: </div>
11284: <div class="sect2">
11285: <div class="titlepage"><div><div><h3 class="title">
11286: <a name="hardening.caveats.relro"></a>B.2.3. Problems with PKGSRC_USE_RELRO</h3></div></div></div>
11287: <div class="sect3">
11288: <div class="titlepage"><div><div><h4 class="title">
11289: <a name="hardening.caveats.relro.performance"></a>B.2.3.1. Performance impact</h4></div></div></div>
11290: <p>
11291: For better protection, full RELRO requires every symbol to be resolved when the
11292: program starts, rather than simply when required at run-time. This will have
11293: more impact on programs using a lot of symbols, or linked to libraries exposing
11294: a lot of symbols. Therefore, daemons or programs otherwise running in
11295: background are affected only when started. Programs loading plug-ins at
11296: run-time are affected when loading the plug-ins.
11297: </p>
11298: <p>
11299: The impact is not expected to be noticeable on modern hardware, except in some
11300: cases for big programs.
11301: </p>
11302: </div>
11303: <div class="sect3">
11304: <div class="titlepage"><div><div><h4 class="title">
11305: <a name="hardening.caveats.relro.crash"></a>B.2.3.2. Run-time crashes</h4></div></div></div>
11306: <p>
11307: Some programs handle plug-ins and dependencies in a way that conflicts with
11308: RELRO: for instance, with an initialization routine listing any other plug-in
11309: required. With full RELRO, the missing symbols are resolved before the
11310: initialization routine can run, and the dynamic loader will not be able to find
11311: them directly and abort as a result. Unfortunately, this is how Xorg loads its
11312: drivers. Partial RELRO can be applied instead in this case.
11313: </p>
11314: </div>
11315: <div class="sect3">
11316: <div class="titlepage"><div><div><h4 class="title">
11317: <a name="hardening.caveats.relro.disable"></a>B.2.3.3. Disabling RELRO on a per-package basis</h4></div></div></div>
11318: <p>
11319: To disable RELRO on a per-package basis, set the following
11320: in the package's <code class="filename">Makefile</code>
11321: before <code class="filename">bsd.prefs.mk</code> is included:
11322: </p>
11323: <pre class="programlisting">
11324: RELRO_SUPPORTED= no
11325: </pre>
1.324 nia 11326: <p>
11327: It is also possible to at most enable partial RELRO, by
11328: setting <code class="varname">RELRO_SUPPORTED</code> to <code class="literal">partial</code>.
11329: </p>
1.322 leot 11330: </div>
11331: </div>
11332: <div class="sect2">
11333: <div class="titlepage"><div><div><h3 class="title">
11334: <a name="hardening.caveats.ssp"></a>B.2.4. Problems with PKGSRC_USE_SSP</h3></div></div></div>
11335: <div class="sect3">
11336: <div class="titlepage"><div><div><h4 class="title">
11337: <a name="hardening.caveats.ssp.build"></a>B.2.4.1. Packages failing to build</h4></div></div></div>
11338: <p>
11339: The stack-smashing protection provided by this option does not work for some
11340: programs. The most common situation in which this happens is when the program
11341: allocates variables on the stack, with the size determined at run-time.
11342: </p>
11343: </div>
11344: <div class="sect3">
11345: <div class="titlepage"><div><div><h4 class="title">
11346: <a name="hardening.caveats.ssp.crash"></a>B.2.4.2. Run-time crashes</h4></div></div></div>
11347: <p>
11348: Again, this feature may cause some programs to crash via a
11349: <code class="varname">SIGABRT</code>, usually indicating an actual bug in the program.
11350: </p>
11351: <p>
11352: On NetBSD <code class="varname">LOG_CRIT</code> level syslog
11353: messages are sent and - by default -
11354: appended to <code class="filename">/var/log/messages</code>, e.g.:
11355: </p>
11356: <pre class="programlisting">
11357: Jan 6 15:42:51 hostname -: hostname program - - - buffer overflow detected; terminated
11358: </pre>
11359: <p>
11360: (where <code class="literal">hostname</code> is the hostname(1) and
11361: <code class="literal">program</code> is the basename(1) of the program crashed).
11362: </p>
11363: <p>
11364: Patching the original program is then required.
11365: </p>
11366: <p>
11367: Rebuilding the package via:
11368: </p>
11369: <pre class="programlisting">
11370: <strong class="userinput"><code>% env CFLAGS=-g INSTALL_UNSTRIPPED=yes make replace</code></strong>
11371: </pre>
11372: <p>
11373: and inspecting the backtrace of the coredump via the debugger
11374: should point out the problematic call by inspecting the frame
11375: calling the _chk() (SSP) function.
11376: </p>
11377: </div>
11378: <div class="sect3">
11379: <div class="titlepage"><div><div><h4 class="title">
11380: <a name="hardening.caveats.ssp.performance"></a>B.2.4.3. Performance impact</h4></div></div></div>
11381: <p>
11382: The compiler emits extra code when using this feature: a check for buffer
11383: overflows is performed when entering and exiting functions, requiring an extra
11384: variable on the stack. The level of protection can otherwise be adjusted to
11385: affect only those functions considered more sensitive by the compiler (with
11386: -fstack-protector instead of -fstack-protector-all).
11387: </p>
11388: <p>
11389: The impact is not expected to be noticeable on modern hardware. However,
11390: programs with a hard requirement to run at the fastest possible speed should
11391: avoid using this feature, or using libraries built with this feature.
11392: </p>
11393: </div>
11394: <div class="sect3">
11395: <div class="titlepage"><div><div><h4 class="title">
11396: <a name="hardening.caveats.ssp.disable"></a>B.2.4.4. Disabling SSP on a per-package basis</h4></div></div></div>
11397: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11398: <h3 class="title">Note</h3>
11399: <p>SSP should not be disabled to work around runtime crashes in
11400: the program! This is a very bad idea and will expose you to security
11401: vulnerabilities.</p>
11402: </div>
11403: <p>
11404: To disable SSP on a per-package basis, set the following
11405: in the package's <code class="filename">Makefile</code>
11406: before <code class="filename">bsd.prefs.mk</code> is included:
11407: </p>
11408: <pre class="programlisting">
11409: SSP_SUPPORTED= no
11410: </pre>
11411: </div>
11412: </div>
11413: </div>
11414: <div class="sect1">
11415: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11416: <a name="hardening.audit"></a>B.3. Auditing the system</h2></div></div></div>
11417: <p>
11418: The illusion of security is worse than having no security at all. This section
11419: lists a number of ways to ensure the security features requested are actually
11420: effective.
11421: </p>
11422: <p>
11423: These instructions were obtained and tested on a system derived from NetBSD 7
11424: (amd64). YMMV.
11425: </p>
11426: <div class="sect2">
11427: <div class="titlepage"><div><div><h3 class="title">
11428: <a name="hardening.audit.pie"></a>B.3.1. Checking for PIE</h3></div></div></div>
11429: <p>
11430: The ELF executable type in use changes for binaries built as PIE; without:
11431: </p>
11432: <pre class="programlisting">
11433: <strong class="userinput"><code>$ file /path/to/bin/ary</code></strong>
11434: /path/to/bin/ary: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for NetBSD 7.0, not stripped
11435: </pre>
11436: <p>as opposed to the following binary, built as PIE:</p>
11437: <pre class="programlisting">
11438: <strong class="userinput"><code>$ file /path/to/pie/bin/ary</code></strong>
11439: /path/to/pie/bin/ary: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for NetBSD 7.0, not stripped
11440: </pre>
11441: <p>
11442: The latter result is then what is expected.
11443: </p>
11444: </div>
11445: <div class="sect2">
11446: <div class="titlepage"><div><div><h3 class="title">
11447: <a name="hardening.audit.relropartial"></a>B.3.2. Checking for partial RELRO</h3></div></div></div>
11448: <p>
11449: The following command should list a section called RELRO:
11450: </p>
11451: <pre class="programlisting">
11452: <strong class="userinput"><code>$ objdump -p /path/to/bin/ary</code></strong>
11453:
11454: /path/to/bin/ary: file format elf64-x86-64
11455:
11456: Program Header:
11457: [...]
11458: RELRO off 0x0000000000000d78 vaddr 0x0000000000600d78 paddr 0x0000000000600d78 align 2**0
11459: </pre>
11460: <p>
11461: This check is now performed automatically if
11462: <code class="varname">PKG_DEVELOPER</code> is set and RELRO is enabled.
11463: </p>
11464: </div>
11465: <div class="sect2">
11466: <div class="titlepage"><div><div><h3 class="title">
11467: <a name="hardening.audit.relrofull"></a>B.3.3. Checking for full RELRO</h3></div></div></div>
11468: <p>
11469: The dynamic loader will apply RELRO immediately when detecting the presence of
11470: the <code class="varname">BIND_NOW</code> flag:
11471: </p>
11472: <pre class="programlisting">
11473: <strong class="userinput"><code>$ objdump -x /path/to/bin/ary</code></strong>
11474:
11475: /path/to/bin/ary: file format elf64-x86-64
11476:
11477: Dynamic Section:
11478: [...]
11479: BIND_NOW 0x0000000000000000
11480: </pre>
11481: <p>
11482: This has to be combined with partial RELRO (see above) to be fully efficient.
11483: </p>
11484: <p>
11485: This check is now performed automatically (where supported) if
11486: <code class="varname">PKG_DEVELOPER</code> is set.
11487: </p>
11488: </div>
11489: <div class="sect2">
11490: <div class="titlepage"><div><div><h3 class="title">
11491: <a name="hardening.audit.ssp"></a>B.3.4. Checking for SSP</h3></div></div></div>
1.323 nia 11492: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11493: <h3 class="title">Note</h3>
11494: <p>
11495: Checking for SSP using this method only works where the operating system
11496: uses <code class="literal">libssp</code>. <code class="literal">libssp</code> is not used
11497: on recent NetBSD/FreeBSD/Linux versions.
11498: </p>
11499: </div>
1.322 leot 11500: <p>
11501: Building objects, binaries and libraries with SSP will affect the presence of
11502: additional symbols in the resulting file:
11503: </p>
11504: <pre class="programlisting">
11505: <strong class="userinput"><code>$ nm /path/to/bin/ary</code></strong>
11506: [...]
11507: U __stack_chk_fail
11508: 0000000000600ea0 B __stack_chk_guard
11509: </pre>
11510: <p>
11511: This is an indicator that the program was indeed built with support for SSP.
11512: </p>
11513: <p>
11514: This check is now performed automatically (where supported) if
11515: <code class="varname">PKG_DEVELOPER</code> is set and SSP is enabled.
11516: </p>
11517: </div>
11518: </div>
11519: </div>
11520: <div class="appendix">
11521: <div class="titlepage"><div><div><h1 class="title">
11522: <a name="logs"></a>Appendix C. Build logs</h1></div></div></div>
11523: <div class="toc">
11524: <p><b>Table of Contents</b></p>
11525: <dl class="toc">
11526: <dt><span class="sect1"><a href="#logs.building">C.1. Building figlet</a></span></dt>
11527: <dt><span class="sect1"><a href="#logs.package">C.2. Packaging figlet</a></span></dt>
11528: </dl>
11529: </div>
11530: <div class="sect1">
11531: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11532: <a name="logs.building"></a>C.1. Building figlet</h2></div></div></div>
11533: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
11534: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11535: => figlet221.tar.gz doesn't seem to exist on this system.
11536: => Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
11537: => [172219 bytes]
11538: Connected to ftp.plig.net.
11539: 220 ftp.plig.org NcFTPd Server (licensed copy) ready.
11540: 331 Guest login ok, send your complete e-mail address as password.
11541: 230-You are user #5 of 500 simultaneous users allowed.
11542: 230-
11543: 230- ___ _ _ _
11544: 230- | _| |_ ___ ___| |_|___ ___ ___ ___
11545: 230- | _| _| . |_| . | | | . |_| . | _| . |
11546: 230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
11547: 230- |_| |_| |___| |___|
11548: 230-
11549: 230-** Welcome to ftp.plig.org **
11550: 230-
11551: 230-Please note that all transfers from this FTP site are logged. If you
11552: 230-do not like this, please disconnect now.
11553: 230-
11554: 230-This archive is available via
11555: 230-
11556: 230-HTTP: http://ftp.plig.org/
11557: 230-FTP: ftp://ftp.plig.org/ (max 500 connections)
11558: 230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
11559: 230-
11560: 230-Please email comments, bug reports and requests for packages to be
11561: 230-mirrored to ftp-admin@plig.org.
11562: 230-
11563: 230-
11564: 230 Logged in anonymously.
11565: Remote system type is UNIX.
11566: Using binary mode to transfer files.
11567: 200 Type okay.
11568: 250 "/pub" is new cwd.
11569: 250-"/pub/figlet" is new cwd.
11570: 250-
11571: 250-Welcome to the figlet archive at ftp.figlet.org
11572: 250-
11573: 250- ftp://ftp.figlet.org/pub/figlet/
11574: 250-
11575: 250-The official FIGlet web page is:
11576: 250- http://www.figlet.org/
11577: 250-
11578: 250-If you have questions, please mailto:info@figlet.org. If you want to
11579: 250-contribute a font or something else, you can email us.
11580: 250
11581: 250 "/pub/figlet/program" is new cwd.
11582: 250 "/pub/figlet/program/unix" is new cwd.
11583: local: figlet221.tar.gz remote: figlet221.tar.gz
11584: 502 Unimplemented command.
11585: 227 Entering Passive Mode (195,40,6,41,246,104)
11586: 150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
11587: 38% |************** | 65800 64.16 KB/s 00:01 ETA
11588: 226 Transfer completed.
11589: 172219 bytes received in 00:02 (75.99 KB/s)
11590: 221 Goodbye.
11591: => Checksum OK for figlet221.tar.gz.
11592: ===> Extracting for figlet-2.2.1nb2
11593: ===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
11594: ===> Patching for figlet-2.2.1nb2
11595: ===> Applying pkgsrc patches for figlet-2.2.1nb2
11596: ===> Overriding tools for figlet-2.2.1nb2
11597: ===> Creating toolchain wrappers for figlet-2.2.1nb2
11598: ===> Configuring for figlet-2.2.1nb2
11599: ===> Building for figlet-2.2.1nb2
11600: gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
11601: chmod a+x figlet
11602: gcc -O2 -o chkfont chkfont.c
11603: => Unwrapping files-to-be-installed.
11604: <code class="prompt">#</code>
11605: <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
11606: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11607: ===> Installing for figlet-2.2.1nb2
11608: install -d -o root -g wheel -m 755 /usr/pkg/bin
11609: install -d -o root -g wheel -m 755 /usr/pkg/man/man6
11610: mkdir -p /usr/pkg/share/figlet
11611: cp figlet /usr/pkg/bin
11612: cp chkfont /usr/pkg/bin
11613: chmod 555 figlist showfigfonts
11614: cp figlist /usr/pkg/bin
11615: cp showfigfonts /usr/pkg/bin
11616: cp fonts/*.flf /usr/pkg/share/figlet
11617: cp fonts/*.flc /usr/pkg/share/figlet
11618: cp figlet.6 /usr/pkg/man/man6
11619: ===> Registering installation for figlet-2.2.1nb2
11620: <code class="prompt">#</code></pre>
11621: </div>
11622: <div class="sect1">
11623: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11624: <a name="logs.package"></a>C.2. Packaging figlet</h2></div></div></div>
11625: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
11626: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11627: ===> Packaging figlet-2.2.1nb2
11628: ===> Building binary package for figlet-2.2.1nb2
11629: Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
11630: Using SrcDir value of /usr/pkg
11631: Registering depends:.
11632: <code class="prompt">#</code></pre>
11633: </div>
11634: </div>
11635: <div class="appendix">
11636: <div class="titlepage"><div><div><h1 class="title">
11637: <a name="ftp-layout"></a>Appendix D. Directory layout of the pkgsrc FTP server</h1></div></div></div>
11638: <div class="toc">
11639: <p><b>Table of Contents</b></p>
11640: <dl class="toc">
11641: <dt><span class="sect1"><a href="#ftp-distfiles">D.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
11642: <dt><span class="sect1"><a href="#ftp-misc">D.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
11643: <dt><span class="sect1"><a href="#ftp-packages">D.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
11644: <dt><span class="sect1"><a href="#ftp-reports">D.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
11645: <dt><span class="sect1"><a href="#ftp-source">D.5. <code class="filename">current</code>,
11646: <code class="filename">stable</code>,
11647: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
11648: source packages</a></span></dt>
11649: </dl>
11650: </div>
11651: <p>As in other big projects, the directory layout of pkgsrc
11652: is quite complex for newbies. This chapter explains where you
11653: find things on the FTP server. The base directory on
11654: <code class="filename">ftp.NetBSD.org</code> is <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top"><code class="filename">/pub/pkgsrc/</code></a>.
11655: On other servers it may be different, but inside this directory,
11656: everything should look the same, no matter on which server you
11657: are. This directory contains some subdirectories, which are
11658: explained below.</p>
11659: <div class="sect1">
11660: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11661: <a name="ftp-distfiles"></a>D.1. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div>
11662: <p>The directory <code class="filename">distfiles</code> contains lots
11663: of archive files from all pkgsrc packages, which are mirrored
11664: here. The subdirectories are called after their package names
11665: and are used when the distributed files have names that don't
11666: explicitly contain a version number or are otherwise too generic
11667: (for example <code class="filename">release.tar.gz</code>).</p>
11668: </div>
11669: <div class="sect1">
11670: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11671: <a name="ftp-misc"></a>D.2. <code class="filename">misc</code>: Miscellaneous things</h2></div></div></div>
11672: <p>This directory contains things that individual pkgsrc
11673: developers find worth publishing.</p>
11674: </div>
11675: <div class="sect1">
11676: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11677: <a name="ftp-packages"></a>D.3. <code class="filename">packages</code>: Binary packages</h2></div></div></div>
11678: <p>This directory contains binary packages for the various
11679: platforms that are supported by pkgsrc.
11680: Each subdirectory is of the form <em class="replaceable"><code>OPSYS</code></em>/<em class="replaceable"><code>ARCH</code></em>/<em class="replaceable"><code>OSVERSION_TAG</code></em>. The meaning of these variables is:</p>
11681: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11682: <li class="listitem"><p><code class="varname">OPSYS</code> is the name of the
11683: operating system for which the packages have been built. The
11684: name is taken from the output of the <span class="command"><strong>uname</strong></span>
11685: command, so it may differ from the one you are used to
11686: hear.</p></li>
11687: <li class="listitem"><p><code class="varname">ARCH</code> is the hardware
11688: architecture of the platform for which the packages have been
11689: built. It also includes the <code class="varname">ABI</code> (Application
11690: Binary Interface) for platforms that have several of
11691: them.</p></li>
11692: <li class="listitem"><p><code class="varname">OSVERSION</code> is the version of
11693: the operating system. For version numbers that change often (for
11694: example NetBSD-current), the often-changing part should be
11695: replaced with an <code class="literal">x</code>, for example
11696: <code class="literal">4.99.x</code>.</p></li>
11697: <li class="listitem"><p><code class="varname">TAG</code> is either
11698: <code class="literal">20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11699: for a stable branch, or <code class="literal">head</code> for packages
11700: built from the HEAD branch. The latter should only be used when
11701: the packages are updated on a regular basis. Otherwise the date
11702: from checking out pkgsrc should be appended, for example
11703: <code class="literal">head_20071015</code>.</p></li>
11704: </ul></div>
11705: <p>The rationale for exactly this scheme is that the pkgsrc users looking for binary packages
11706: can quickly click through the directories on the
11707: server and find the best binary packages for their machines. Since they
11708: usually know the operating system and the hardware architecture, OPSYS
11709: and ARCH are placed first. After these choices, they can select the
11710: best combination of OSVERSION and TAG together, since it is usually the
11711: case that packages stay compatible between different version of the
11712: operating system.</p>
11713: <p>In each of these directories, there is a
11714: whole binary packages collection for a specific platform. It has a directory called
11715: <code class="filename">All</code> which contains all binary packages.
11716: Besides that, there are various category directories that
11717: contain symbolic links to the real binary packages.</p>
11718: </div>
11719: <div class="sect1">
11720: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11721: <a name="ftp-reports"></a>D.4. <code class="filename">reports</code>: Bulk build reports</h2></div></div></div>
1.108 rillig 11722: <p>Here are the reports from bulk builds, for those who want
11723: to fix packages that didn't build on some of the platforms. The
1.322 leot 11724: structure of subdirectories should look like the one in <a class="xref" href="#ftp-packages" title="D.3. packages: Binary packages">Section D.3, “<code class="filename">packages</code>: Binary packages”</a>.</p>
1.108 rillig 11725: </div>
1.148 asau 11726: <div class="sect1">
1.108 rillig 11727: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.322 leot 11728: <a name="ftp-source"></a>D.5. <code class="filename">current</code>,
1.261 leot 11729: <code class="filename">stable</code>,
1.126 jakllsch 11730: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.76 rillig 11731: source packages</h2></div></div></div>
1.128 wiz 11732: <p>These directories contain the <span class="quote">“<span class="quote">real</span>”</span> pkgsrc,
1.76 rillig 11733: that is the files that define how to create binary packages from
11734: source archives.</p>
1.262 leot 11735: <p>Each of the <code class="filename">current</code>,
11736: <code class="filename">stable</code> and
11737: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11738: directories share the same structure. They each contain a
11739: <code class="filename">pkgsrc</code> directory and
11740: <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> file.</p>
1.76 rillig 11741: <p>The directory <code class="filename">pkgsrc</code> contains a
1.89 rillig 11742: snapshot of the CVS repository, which is updated regularly. The
1.262 leot 11743: file <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> contains the same
11744: as the directory, ready to be downloaded as a whole.</p>
11745: <p>The <code class="filename">current</code> directory contains files
11746: related to the HEAD branch of the CVS repository.
11747: In this directory there is an additional file called
11748: <code class="filename">pkgsrc-readmes.tar.{bz,gz,xz}</code> that contains
11749: all pkgsrc <code class="filename">README</code>s with information about
11750: categories and packages.
11751: </p>
11752: <p>The <code class="filename">stable</code> directory is a symlink to
11753: the latest
11754: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11755: </p>
11756: <p>The
11757: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11758: directories contain files related to the
11759: <code class="filename">-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11760: stable branch of the CVS repository. In these directories there is
11761: an additional file called
11762: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em>.tar.{bz,gz,xz}</code>,
1.76 rillig 11763: which contains the state of pkgsrc when it was branched.</p>
11764: </div>
1.75 rillig 11765: </div>
1.148 asau 11766: <div class="appendix">
11767: <div class="titlepage"><div><div><h1 class="title">
1.322 leot 11768: <a name="help-topics"></a>Appendix E. Help topics</h1></div></div></div>
1.267 rillig 11769: <p>
11770: The following list contains all help topics that are available
11771: when running <span class="command"><strong>bmake help topic=:index</strong></span>.
11772: </p>
1.269 leot 11773: <table border="0" summary="Simple list" class="simplelist">
11774: <tr>
11775: <td>#!</td>
11776: <td>-lintl</td>
11777: </tr>
11778: <tr>
1.320 wiz 11779: <td>32bit</td>
1.269 leot 11780: <td>64bit</td>
1.320 wiz 11781: </tr>
11782: <tr>
1.269 leot 11783: <td>ABI</td>
1.320 wiz 11784: <td>ACCEPTABLE_LICENSES</td>
1.269 leot 11785: </tr>
11786: <tr>
11787: <td>ACROREAD_FONTPATH</td>
1.320 wiz 11788: <td>ADDITIONAL</td>
1.269 leot 11789: </tr>
11790: <tr>
11791: <td>AFAIK</td>
1.320 wiz 11792: <td>AIX</td>
1.269 leot 11793: </tr>
11794: <tr>
11795: <td>ALLOW_VULNERABLE_PACKAGES</td>
1.320 wiz 11796: <td>ALL_ENV</td>
1.269 leot 11797: </tr>
11798: <tr>
1.315 cirnatda 11799: <td>ALTERNATIVES_SRC</td>
1.340 ! gutterid 11800: <td>AMANDA_TMP</td>
1.338 nia 11801: </tr>
11802: <tr>
11803: <td>AMANDA_USER</td>
1.340 ! gutterid 11804: <td>AMANDA_VAR</td>
1.332 rillig 11805: </tr>
11806: <tr>
1.338 nia 11807: <td>APACHE_GROUP</td>
1.340 ! gutterid 11808: <td>APACHE_MODULE_NAME</td>
1.329 leot 11809: </tr>
11810: <tr>
1.338 nia 11811: <td>APACHE_MODULE_SRC</td>
1.340 ! gutterid 11812: <td>APACHE_MODULE_SRCDIR</td>
1.327 wiz 11813: </tr>
11814: <tr>
1.338 nia 11815: <td>APACHE_PKG_PREFIX</td>
1.340 ! gutterid 11816: <td>APACHE_SUEXEC_CONFIGURE_ARGS</td>
1.311 leot 11817: </tr>
11818: <tr>
1.338 nia 11819: <td>APACHE_SUEXEC_DOCROOT</td>
1.340 ! gutterid 11820: <td>APACHE_USER</td>
1.292 leot 11821: </tr>
11822: <tr>
1.338 nia 11823: <td>APPEND_ABI</td>
1.340 ! gutterid 11824: <td>APPEND_ELF</td>
1.274 rillig 11825: </tr>
11826: <tr>
1.338 nia 11827: <td>ARLA_CACHE</td>
1.340 ! gutterid 11828: <td>AUDIT_PACKAGES_FLAGS</td>
1.269 leot 11829: </tr>
11830: <tr>
1.338 nia 11831: <td>AUTOCONF_REQD</td>
1.340 ! gutterid 11832: <td>AUTOMAKE_OVERRIDE</td>
1.269 leot 11833: </tr>
11834: <tr>
1.338 nia 11835: <td>AUTOMAKE_REQD</td>
1.340 ! gutterid 11836: <td>AUTO_MKDIRS</td>
1.269 leot 11837: </tr>
11838: <tr>
1.338 nia 11839: <td>BDB185_DEFAULT</td>
1.340 ! gutterid 11840: <td>BDBBASE</td>
1.269 leot 11841: </tr>
11842: <tr>
1.338 nia 11843: <td>BDB_ACCEPTED</td>
1.340 ! gutterid 11844: <td>BDB_DEFAULT</td>
1.269 leot 11845: </tr>
11846: <tr>
1.338 nia 11847: <td>BDB_LIBS</td>
1.340 ! gutterid 11848: <td>BDB_TYPE</td>
1.269 leot 11849: </tr>
11850: <tr>
1.338 nia 11851: <td>BINCIMAP_GROUP</td>
1.340 ! gutterid 11852: <td>BINCIMAP_USER</td>
1.269 leot 11853: </tr>
11854: <tr>
1.338 nia 11855: <td>BIND_DIR</td>
1.340 ! gutterid 11856: <td>BIND_GROUP</td>
1.269 leot 11857: </tr>
11858: <tr>
1.338 nia 11859: <td>BIND_USER</td>
1.340 ! gutterid 11860: <td>BINOWN</td>
1.269 leot 11861: </tr>
11862: <tr>
1.338 nia 11863: <td>BINPKG_SITES</td>
1.340 ! gutterid 11864: <td>BIN_INSTALL_FLAGS</td>
1.269 leot 11865: </tr>
11866: <tr>
1.338 nia 11867: <td>BISON_PKGDATADIR</td>
1.340 ! gutterid 11868: <td>BLAS</td>
1.269 leot 11869: </tr>
11870: <tr>
1.338 nia 11871: <td>BLAS_ACCEPTED</td>
1.340 ! gutterid 11872: <td>BLAS_C_INTERFACE</td>
1.312 gdt 11873: </tr>
11874: <tr>
1.338 nia 11875: <td>BLAS_INCLUDES</td>
1.340 ! gutterid 11876: <td>BLAS_INDEX64</td>
1.269 leot 11877: </tr>
11878: <tr>
1.338 nia 11879: <td>BLAS_LIBS</td>
1.340 ! gutterid 11880: <td>BLAS_TYPE</td>
1.269 leot 11881: </tr>
11882: <tr>
1.338 nia 11883: <td>BOOTSTRAP_DEPENDS</td>
1.340 ! gutterid 11884: <td>BROKEN</td>
1.303 bacon 11885: </tr>
11886: <tr>
1.338 nia 11887: <td>BROKEN_EXCEPT_ON_PLATFORM</td>
1.340 ! gutterid 11888: <td>BROKEN_ON_PLATFORM</td>
1.320 wiz 11889: </tr>
11890: <tr>
1.338 nia 11891: <td>BSDSRCDIR</td>
1.340 ! gutterid 11892: <td>BSDXSRCDIR</td>
1.269 leot 11893: </tr>
11894: <tr>
1.338 nia 11895: <td>BSD_MAKE_ENV</td>
1.340 ! gutterid 11896: <td>BUILDLINK_AUTO_DIRS</td>
1.292 leot 11897: </tr>
11898: <tr>
1.338 nia 11899: <td>BUILDLINK_AUTO_VARS</td>
1.340 ! gutterid 11900: <td>BUILDLINK_CFLAGS</td>
1.269 leot 11901: </tr>
11902: <tr>
1.338 nia 11903: <td>BUILDLINK_CONTENTS_FILTER</td>
1.329 leot 11904: <td>BUILDLINK_CPPFLAGS</td>
1.269 leot 11905: </tr>
11906: <tr>
11907: <td>BUILDLINK_FILES</td>
1.331 gutterid 11908: <td>BUILDLINK_FILES_CMD</td>
1.320 wiz 11909: </tr>
11910: <tr>
11911: <td>BUILDLINK_FNAME_TRANSFORM</td>
1.331 gutterid 11912: <td>BUILDLINK_LDFLAGS</td>
1.269 leot 11913: </tr>
11914: <tr>
1.320 wiz 11915: <td>BUILDLINK_LIBS</td>
1.331 gutterid 11916: <td>BUILDLINK_OPSYS_SUPPORT_PTHREAD</td>
1.269 leot 11917: </tr>
11918: <tr>
1.320 wiz 11919: <td>BUILDLINK_PKGNAME</td>
1.331 gutterid 11920: <td>BUILDLINK_PREFIX</td>
1.269 leot 11921: </tr>
11922: <tr>
1.320 wiz 11923: <td>BUILDLINK_RPATHDIRS</td>
1.331 gutterid 11924: <td>BUILDLINK_TREE</td>
1.269 leot 11925: </tr>
11926: <tr>
1.320 wiz 11927: <td>BUILD_DEFS</td>
1.331 gutterid 11928: <td>BUILD_DEFS_EFFECTS</td>
1.269 leot 11929: </tr>
11930: <tr>
1.320 wiz 11931: <td>BUILD_DEPENDS</td>
1.331 gutterid 11932: <td>BUILD_DIRS</td>
1.269 leot 11933: </tr>
11934: <tr>
1.320 wiz 11935: <td>BUILD_ENV_SHELL</td>
1.331 gutterid 11936: <td>BUILD_MAKE_CMD</td>
1.269 leot 11937: </tr>
11938: <tr>
1.320 wiz 11939: <td>BUILD_MAKE_FLAGS</td>
1.331 gutterid 11940: <td>BUILD_TARGET</td>
1.269 leot 11941: </tr>
11942: <tr>
1.320 wiz 11943: <td>BUILTIN_FIND_FILES</td>
1.331 gutterid 11944: <td>BUILTIN_FIND_FILES_VAR</td>
1.269 leot 11945: </tr>
11946: <tr>
1.320 wiz 11947: <td>BUILTIN_FIND_GREP</td>
1.331 gutterid 11948: <td>BUILTIN_FIND_HEADERS</td>
1.269 leot 11949: </tr>
11950: <tr>
1.320 wiz 11951: <td>BUILTIN_FIND_HEADERS_VAR</td>
1.331 gutterid 11952: <td>BUILTIN_FIND_PKGCONFIG</td>
1.269 leot 11953: </tr>
11954: <tr>
1.320 wiz 11955: <td>BUILTIN_FIND_PKGCONFIG_VAR</td>
1.331 gutterid 11956: <td>BUILTIN_PKG</td>
1.309 gutterid 11957: </tr>
11958: <tr>
1.320 wiz 11959: <td>BUILTIN_TEST_CURSES_DEFINES</td>
1.331 gutterid 11960: <td>BUILTIN_TEST_CURSES_FUNCS</td>
1.269 leot 11961: </tr>
11962: <tr>
1.320 wiz 11963: <td>BUILTIN_VERSION_SCRIPT</td>
1.331 gutterid 11964: <td>BUILTIN_X11_TYPE</td>
1.269 leot 11965: </tr>
11966: <tr>
1.320 wiz 11967: <td>BUILTIN_X11_VERSION</td>
1.331 gutterid 11968: <td>CACTI_GROUP</td>
1.269 leot 11969: </tr>
11970: <tr>
1.320 wiz 11971: <td>CACTI_USER</td>
1.331 gutterid 11972: <td>CANNA_GROUP</td>
1.269 leot 11973: </tr>
11974: <tr>
1.320 wiz 11975: <td>CANNA_USER</td>
1.331 gutterid 11976: <td>CAT</td>
1.269 leot 11977: </tr>
11978: <tr>
1.320 wiz 11979: <td>CBLAS_LIBS</td>
1.331 gutterid 11980: <td>CCACHE_BASE</td>
1.269 leot 11981: </tr>
11982: <tr>
1.303 bacon 11983: <td>CCACHE_DIR</td>
1.331 gutterid 11984: <td>CCACHE_LOGFILE</td>
1.269 leot 11985: </tr>
11986: <tr>
1.303 bacon 11987: <td>CC_VERSION</td>
1.331 gutterid 11988: <td>CC_VERSION_STRING</td>
1.269 leot 11989: </tr>
11990: <tr>
1.303 bacon 11991: <td>CDRECORD_CONF</td>
1.331 gutterid 11992: <td>CDROM_PKG_URL_DIR</td>
1.269 leot 11993: </tr>
11994: <tr>
1.303 bacon 11995: <td>CDROM_PKG_URL_HOST</td>
1.340 ! gutterid 11996: <td>CHECK_COMPILER</td>
1.338 nia 11997: </tr>
11998: <tr>
11999: <td>CHECK_FAKEHOME</td>
1.340 ! gutterid 12000: <td>CHECK_FILES</td>
1.332 rillig 12001: </tr>
12002: <tr>
1.338 nia 12003: <td>CHECK_FILES_SKIP</td>
1.340 ! gutterid 12004: <td>CHECK_FILES_STRICT</td>
1.329 leot 12005: </tr>
12006: <tr>
1.338 nia 12007: <td>CHECK_HEADERS</td>
1.340 ! gutterid 12008: <td>CHECK_HEADERS_SKIP</td>
1.327 wiz 12009: </tr>
12010: <tr>
1.338 nia 12011: <td>CHECK_INTERPRETER</td>
1.340 ! gutterid 12012: <td>CHECK_INTERPRETER_SKIP</td>
1.320 wiz 12013: </tr>
12014: <tr>
1.338 nia 12015: <td>CHECK_PERMS</td>
1.340 ! gutterid 12016: <td>CHECK_PERMS_AUTOFIX</td>
1.311 leot 12017: </tr>
12018: <tr>
1.338 nia 12019: <td>CHECK_PERMS_SKIP</td>
1.340 ! gutterid 12020: <td>CHECK_PIE</td>
1.292 leot 12021: </tr>
12022: <tr>
1.338 nia 12023: <td>CHECK_PIE_SKIP</td>
1.340 ! gutterid 12024: <td>CHECK_PIE_SUPPORTED</td>
1.274 rillig 12025: </tr>
12026: <tr>
1.338 nia 12027: <td>CHECK_PORTABILITY</td>
1.340 ! gutterid 12028: <td>CHECK_PORTABILITY_EXPERIMENTAL</td>
1.331 gutterid 12029: </tr>
12030: <tr>
1.338 nia 12031: <td>CHECK_PORTABILITY_SKIP</td>
1.340 ! gutterid 12032: <td>CHECK_RELRO</td>
1.269 leot 12033: </tr>
12034: <tr>
1.338 nia 12035: <td>CHECK_RELRO_SKIP</td>
1.340 ! gutterid 12036: <td>CHECK_RELRO_SUPPORTED</td>
1.269 leot 12037: </tr>
12038: <tr>
1.338 nia 12039: <td>CHECK_SHLIBS</td>
1.340 ! gutterid 12040: <td>CHECK_SHLIBS_SKIP</td>
1.269 leot 12041: </tr>
12042: <tr>
1.338 nia 12043: <td>CHECK_SHLIBS_SUPPORTED</td>
1.340 ! gutterid 12044: <td>CHECK_SHLIBS_TOXIC</td>
1.269 leot 12045: </tr>
12046: <tr>
1.338 nia 12047: <td>CHECK_SSP</td>
1.340 ! gutterid 12048: <td>CHECK_SSP_SKIP</td>
1.269 leot 12049: </tr>
12050: <tr>
1.338 nia 12051: <td>CHECK_SSP_SUPPORTED</td>
1.340 ! gutterid 12052: <td>CHECK_STRIPPED</td>
1.269 leot 12053: </tr>
12054: <tr>
1.338 nia 12055: <td>CHECK_STRIPPED_SKIP</td>
1.340 ! gutterid 12056: <td>CHECK_WRKREF</td>
1.269 leot 12057: </tr>
12058: <tr>
1.338 nia 12059: <td>CHECK_WRKREF_EXTRA_DIRS</td>
1.340 ! gutterid 12060: <td>CHECK_WRKREF_SKIP</td>
1.269 leot 12061: </tr>
12062: <tr>
1.338 nia 12063: <td>CLAMAV_DBDIR</td>
1.340 ! gutterid 12064: <td>CLAMAV_GROUP</td>
1.269 leot 12065: </tr>
12066: <tr>
1.338 nia 12067: <td>CLAMAV_USER</td>
1.340 ! gutterid 12068: <td>CLANGBASE</td>
1.269 leot 12069: </tr>
12070: <tr>
1.338 nia 12071: <td>CLEANDEPENDS</td>
1.340 ! gutterid 12072: <td>CMAKE_DEPENDENCIES_REWRITE</td>
1.269 leot 12073: </tr>
12074: <tr>
1.338 nia 12075: <td>CMAKE_INSTALL_NAME_DIR</td>
1.340 ! gutterid 12076: <td>CMAKE_INSTALL_PREFIX</td>
1.269 leot 12077: </tr>
12078: <tr>
1.338 nia 12079: <td>CMAKE_MODULE_PATH_OVERRIDE</td>
1.340 ! gutterid 12080: <td>CMAKE_PKGSRC_BUILD_FLAGS</td>
1.269 leot 12081: </tr>
12082: <tr>
1.338 nia 12083: <td>CMAKE_PREFIX_PATH</td>
1.305 bacon 12084: <td>CMAKE_USE_GNU_INSTALL_DIRS</td>
1.292 leot 12085: </tr>
12086: <tr>
1.305 bacon 12087: <td>COMPILER_RPATH_FLAG</td>
1.269 leot 12088: <td>COMPILER_USE_SYMLINKS</td>
12089: </tr>
12090: <tr>
1.305 bacon 12091: <td>CONFIGURE_ARGS</td>
1.269 leot 12092: <td>CONFIGURE_DIRS</td>
12093: </tr>
12094: <tr>
1.305 bacon 12095: <td>CONFIGURE_ENV</td>
1.287 rillig 12096: <td>CONFIGURE_ENV_SHELL</td>
1.269 leot 12097: </tr>
12098: <tr>
1.305 bacon 12099: <td>CONFIGURE_HAS_INFODIR</td>
1.269 leot 12100: <td>CONFIGURE_HAS_MANDIR</td>
12101: </tr>
12102: <tr>
1.305 bacon 12103: <td>CONFIGURE_SCRIPT</td>
1.269 leot 12104: <td>CONFIG_SHELL</td>
12105: </tr>
12106: <tr>
1.305 bacon 12107: <td>CONFIG_SHELL_FLAGS</td>
1.269 leot 12108: <td>CONF_FILES</td>
12109: </tr>
12110: <tr>
1.305 bacon 12111: <td>CONF_FILES_MODE</td>
1.269 leot 12112: <td>CONF_FILES_PERMS</td>
12113: </tr>
12114: <tr>
1.305 bacon 12115: <td>CONSERVER_DEFAULTHOST</td>
1.269 leot 12116: <td>CONSERVER_DEFAULTPORT</td>
12117: </tr>
12118: <tr>
1.305 bacon 12119: <td>CP</td>
1.269 leot 12120: <td>CPP</td>
12121: </tr>
12122: <tr>
1.305 bacon 12123: <td>CPP_PRECOMP_FLAGS</td>
1.269 leot 12124: <td>CREATE_WRKDIR_SYMLINK</td>
12125: </tr>
12126: <tr>
1.305 bacon 12127: <td>CROSSBASE</td>
1.269 leot 12128: <td>CTFCONVERT</td>
12129: </tr>
12130: <tr>
1.305 bacon 12131: <td>CTF_FILES_SKIP</td>
1.269 leot 12132: <td>CTF_SUPPORTED</td>
12133: </tr>
12134: <tr>
1.305 bacon 12135: <td>CTYPE</td>
1.269 leot 12136: <td>CUPS_GROUP</td>
12137: </tr>
12138: <tr>
1.305 bacon 12139: <td>CUPS_SYSTEM_GROUPS</td>
1.269 leot 12140: <td>CUPS_USER</td>
12141: </tr>
12142: <tr>
1.305 bacon 12143: <td>CURSES_DEFAULT</td>
1.269 leot 12144: <td>CURSES_TYPE</td>
1.292 leot 12145: </tr>
12146: <tr>
1.273 brook 12147: <td>CXX</td>
1.340 ! gutterid 12148: <td>CYRUS_GROUP</td>
1.332 rillig 12149: </tr>
12150: <tr>
12151: <td>CYRUS_IDLE</td>
1.340 ! gutterid 12152: <td>CYRUS_USER</td>
1.329 leot 12153: </tr>
12154: <tr>
1.332 rillig 12155: <td>DAEMONTOOLS_GROUP</td>
1.340 ! gutterid 12156: <td>DAEMONTOOLS_LOG_USER</td>
1.327 wiz 12157: </tr>
12158: <tr>
1.332 rillig 12159: <td>DARWIN_NO_SYSTEM_LIBS</td>
1.340 ! gutterid 12160: <td>DARWIN_REQUIRES_FILTER</td>
1.320 wiz 12161: </tr>
12162: <tr>
1.332 rillig 12163: <td>DBUS_GROUP</td>
1.340 ! gutterid 12164: <td>DBUS_USER</td>
1.311 leot 12165: </tr>
12166: <tr>
1.332 rillig 12167: <td>DEFANG_GROUP</td>
1.340 ! gutterid 12168: <td>DEFANG_USER</td>
1.269 leot 12169: </tr>
12170: <tr>
1.332 rillig 12171: <td>DEFAULT_ACCEPTABLE_LICENSES</td>
1.340 ! gutterid 12172: <td>DEFAULT_DISTFILES</td>
1.269 leot 12173: </tr>
12174: <tr>
1.332 rillig 12175: <td>DEFAULT_IRC_SERVER</td>
1.340 ! gutterid 12176: <td>DEFAULT_SERIAL_DEVICE</td>
1.269 leot 12177: </tr>
12178: <tr>
1.332 rillig 12179: <td>DEF_UMASK</td>
1.340 ! gutterid 12180: <td>DEINSTALLDEPENDS</td>
1.309 gutterid 12181: </tr>
12182: <tr>
1.332 rillig 12183: <td>DEINSTALL_SRC</td>
1.340 ! gutterid 12184: <td>DEINSTALL_TEMPLATES</td>
1.269 leot 12185: </tr>
12186: <tr>
1.332 rillig 12187: <td>DELAYED_ERROR_MSG</td>
1.340 ! gutterid 12188: <td>DELAYED_WARNING_MSG</td>
1.269 leot 12189: </tr>
12190: <tr>
1.332 rillig 12191: <td>DEPENDS</td>
1.340 ! gutterid 12192: <td>DEPENDS_TARGET</td>
1.269 leot 12193: </tr>
12194: <tr>
1.332 rillig 12195: <td>DEPENDS_TYPE</td>
1.340 ! gutterid 12196: <td>DESTDIR</td>
1.269 leot 12197: </tr>
12198: <tr>
1.332 rillig 12199: <td>DESTDIR_VARNAME</td>
1.340 ! gutterid 12200: <td>DIALER_GROUP</td>
1.269 leot 12201: </tr>
12202: <tr>
1.332 rillig 12203: <td>DIGEST_REQD</td>
1.340 ! gutterid 12204: <td>DISTDIR</td>
1.269 leot 12205: </tr>
12206: <tr>
1.332 rillig 12207: <td>DISTFILES</td>
1.340 ! gutterid 12208: <td>DISTINFO_FILE</td>
1.269 leot 12209: </tr>
12210: <tr>
1.332 rillig 12211: <td>DISTNAME</td>
1.340 ! gutterid 12212: <td>DIST_PATH</td>
1.269 leot 12213: </tr>
12214: <tr>
1.332 rillig 12215: <td>DIST_SUBDIR</td>
1.340 ! gutterid 12216: <td>DJBDNS_AXFR_USER</td>
1.269 leot 12217: </tr>
12218: <tr>
1.332 rillig 12219: <td>DJBDNS_CACHE_USER</td>
1.340 ! gutterid 12220: <td>DJBDNS_DJBDNS_GROUP</td>
1.269 leot 12221: </tr>
12222: <tr>
1.332 rillig 12223: <td>DJBDNS_LOG_USER</td>
1.340 ! gutterid 12224: <td>DJBDNS_RBL_USER</td>
1.269 leot 12225: </tr>
12226: <tr>
1.332 rillig 12227: <td>DJBDNS_TINY_USER</td>
1.340 ! gutterid 12228: <td>DLOPEN_REQUIRE_PTHREADS</td>
1.269 leot 12229: </tr>
12230: <tr>
1.332 rillig 12231: <td>DL_AUTO_VARS</td>
1.340 ! gutterid 12232: <td>DL_CFLAGS</td>
1.269 leot 12233: </tr>
12234: <tr>
1.332 rillig 12235: <td>DL_LDFLAGS</td>
1.340 ! gutterid 12236: <td>DL_LIBS</td>
1.269 leot 12237: </tr>
12238: <tr>
1.332 rillig 12239: <td>DNS</td>
1.340 ! gutterid 12240: <td>DOCOWN</td>
1.269 leot 12241: </tr>
12242: <tr>
1.332 rillig 12243: <td>DOWNLOADED_DISTFILE</td>
1.340 ! gutterid 12244: <td>DQCACHE_GROUP</td>
1.269 leot 12245: </tr>
12246: <tr>
1.333 nia 12247: <td>DQCACHE_USER</td>
1.340 ! gutterid 12248: <td>DT_LAYOUT</td>
1.333 nia 12249: </tr>
12250: <tr>
1.332 rillig 12251: <td>DYNAMIC_SITES_CMD</td>
1.340 ! gutterid 12252: <td>DYNAMIC_SITES_SCRIPT</td>
1.269 leot 12253: </tr>
12254: <tr>
1.332 rillig 12255: <td>ECHO</td>
1.340 ! gutterid 12256: <td>ECHO_N</td>
1.269 leot 12257: </tr>
12258: <tr>
1.332 rillig 12259: <td>ELK_GUI</td>
1.340 ! gutterid 12260: <td>EMACS_TYPE</td>
1.269 leot 12261: </tr>
12262: <tr>
1.332 rillig 12263: <td>EMULDIR</td>
1.340 ! gutterid 12264: <td>EMULSUBDIR</td>
1.269 leot 12265: </tr>
12266: <tr>
1.332 rillig 12267: <td>EMULSUBDIRSLASH</td>
1.340 ! gutterid 12268: <td>EMUL_ARCH</td>
1.269 leot 12269: </tr>
12270: <tr>
1.332 rillig 12271: <td>EMUL_DISTRO</td>
1.340 ! gutterid 12272: <td>EMUL_EXEC_FMT</td>
1.269 leot 12273: </tr>
12274: <tr>
1.332 rillig 12275: <td>EMUL_IS_NATIVE</td>
1.340 ! gutterid 12276: <td>EMUL_MODULES</td>
1.269 leot 12277: </tr>
12278: <tr>
1.332 rillig 12279: <td>EMUL_OPSYS</td>
1.340 ! gutterid 12280: <td>EMUL_PKG_FMT</td>
1.269 leot 12281: </tr>
12282: <tr>
1.332 rillig 12283: <td>EMUL_PLATFORM</td>
1.340 ! gutterid 12284: <td>EMUL_PLATFORMS</td>
1.269 leot 12285: </tr>
12286: <tr>
1.332 rillig 12287: <td>EMUL_PREFER</td>
1.340 ! gutterid 12288: <td>EMUL_REQD</td>
1.269 leot 12289: </tr>
12290: <tr>
1.332 rillig 12291: <td>EMUL_TYPE</td>
1.340 ! gutterid 12292: <td>ERROR_MSG</td>
1.269 leot 12293: </tr>
12294: <tr>
1.332 rillig 12295: <td>EXIM_GROUP</td>
1.340 ! gutterid 12296: <td>EXIM_USER</td>
1.269 leot 12297: </tr>
12298: <tr>
1.332 rillig 12299: <td>EXPORT_SYMBOLS_LDFLAGS</td>
1.340 ! gutterid 12300: <td>EXTRACTOR</td>
1.269 leot 12301: </tr>
12302: <tr>
1.332 rillig 12303: <td>EXTRACT_CMD</td>
1.340 ! gutterid 12304: <td>EXTRACT_CMD_DEFAULT</td>
1.338 nia 12305: </tr>
12306: <tr>
12307: <td>EXTRACT_DIR</td>
1.340 ! gutterid 12308: <td>EXTRACT_ELEMENTS</td>
1.269 leot 12309: </tr>
12310: <tr>
1.338 nia 12311: <td>EXTRACT_ENV</td>
1.340 ! gutterid 12312: <td>EXTRACT_ONLY</td>
1.269 leot 12313: </tr>
12314: <tr>
1.338 nia 12315: <td>EXTRACT_OPTS</td>
1.340 ! gutterid 12316: <td>EXTRACT_SUFX</td>
1.269 leot 12317: </tr>
12318: <tr>
1.338 nia 12319: <td>EXTRACT_USING</td>
1.340 ! gutterid 12320: <td>FAIL</td>
1.269 leot 12321: </tr>
12322: <tr>
1.338 nia 12323: <td>FAILOVER_FETCH</td>
1.340 ! gutterid 12324: <td>FAIL_MSG</td>
1.269 leot 12325: </tr>
12326: <tr>
1.338 nia 12327: <td>FAKE_NCURSES</td>
1.340 ! gutterid 12328: <td>FAM</td>
1.269 leot 12329: </tr>
12330: <tr>
1.338 nia 12331: <td>FAM_ACCEPTED</td>
1.340 ! gutterid 12332: <td>FAM_DEFAULT</td>
1.269 leot 12333: </tr>
12334: <tr>
1.338 nia 12335: <td>FAM_SERVER</td>
1.340 ! gutterid 12336: <td>FCPATH</td>
1.269 leot 12337: </tr>
12338: <tr>
1.338 nia 12339: <td>FEATURE_CPPFLAGS</td>
1.340 ! gutterid 12340: <td>FEATURE_LDFLAGS</td>
1.269 leot 12341: </tr>
12342: <tr>
1.338 nia 12343: <td>FEATURE_LIBS</td>
1.340 ! gutterid 12344: <td>FETCH_AFTER_ARGS</td>
1.292 leot 12345: </tr>
12346: <tr>
1.338 nia 12347: <td>FETCH_BEFORE_ARGS</td>
1.340 ! gutterid 12348: <td>FETCH_CMD</td>
1.269 leot 12349: </tr>
12350: <tr>
1.338 nia 12351: <td>FETCH_OUTPUT_ARGS</td>
1.340 ! gutterid 12352: <td>FETCH_PROXY</td>
1.269 leot 12353: </tr>
12354: <tr>
1.338 nia 12355: <td>FETCH_RESUME_ARGS</td>
1.340 ! gutterid 12356: <td>FETCH_TIMEOUT</td>
1.269 leot 12357: </tr>
12358: <tr>
1.338 nia 12359: <td>FETCH_USE_IPV4_ONLY</td>
1.340 ! gutterid 12360: <td>FETCH_USING</td>
1.269 leot 12361: </tr>
12362: <tr>
1.338 nia 12363: <td>FILES_SUBST</td>
1.340 ! gutterid 12364: <td>FILES_SUBST_SED</td>
1.269 leot 12365: </tr>
12366: <tr>
1.338 nia 12367: <td>FIX_SYSTEM_HEADERS</td>
1.295 rillig 12368: <td>FONTS_DIRS</td>
1.274 rillig 12369: </tr>
12370: <tr>
1.305 bacon 12371: <td>FONTS_VERBOSE</td>
1.295 rillig 12372: <td>FOO_HACKS_MK</td>
1.292 leot 12373: </tr>
12374: <tr>
1.305 bacon 12375: <td>FOX_USE_XUNICODE</td>
1.295 rillig 12376: <td>FREEWNN_GROUP</td>
1.269 leot 12377: </tr>
12378: <tr>
1.305 bacon 12379: <td>FREEWNN_USER</td>
1.295 rillig 12380: <td>FTP_PKG_URL_DIR</td>
1.269 leot 12381: </tr>
12382: <tr>
1.305 bacon 12383: <td>FTP_PKG_URL_HOST</td>
1.295 rillig 12384: <td>GAMEDATAMODE</td>
1.269 leot 12385: </tr>
12386: <tr>
1.305 bacon 12387: <td>GAMEDATA_PERMS</td>
1.295 rillig 12388: <td>GAMEDIRMODE</td>
1.269 leot 12389: </tr>
12390: <tr>
1.305 bacon 12391: <td>GAMEDIR_PERMS</td>
1.295 rillig 12392: <td>GAMEGRP</td>
1.269 leot 12393: </tr>
12394: <tr>
1.305 bacon 12395: <td>GAMEMODE</td>
1.295 rillig 12396: <td>GAMEOWN</td>
1.269 leot 12397: </tr>
12398: <tr>
1.305 bacon 12399: <td>GAMES_GROUP</td>
1.295 rillig 12400: <td>GAMES_USER</td>
1.269 leot 12401: </tr>
12402: <tr>
1.305 bacon 12403: <td>GCC</td>
1.295 rillig 12404: <td>GCCBASE</td>
1.269 leot 12405: </tr>
12406: <tr>
1.305 bacon 12407: <td>GCC_REQD</td>
1.295 rillig 12408: <td>GCC_VERSION_SUFFIX</td>
1.269 leot 12409: </tr>
12410: <tr>
1.305 bacon 12411: <td>GEM_BUILD</td>
1.295 rillig 12412: <td>GEM_CLEANBUILD</td>
1.269 leot 12413: </tr>
12414: <tr>
1.305 bacon 12415: <td>GEM_CLEANBUILD_EXTENSIONS</td>
1.295 rillig 12416: <td>GEM_DOCDIR</td>
1.269 leot 12417: </tr>
12418: <tr>
1.305 bacon 12419: <td>GEM_EXTSDIR</td>
1.295 rillig 12420: <td>GEM_HOME</td>
1.292 leot 12421: </tr>
12422: <tr>
1.305 bacon 12423: <td>GEM_KEEPBUILD</td>
1.295 rillig 12424: <td>GEM_LIBDIR</td>
1.269 leot 12425: </tr>
12426: <tr>
1.305 bacon 12427: <td>GEM_NAME</td>
1.295 rillig 12428: <td>GEM_PATH</td>
1.269 leot 12429: </tr>
12430: <tr>
1.312 gdt 12431: <td>GEM_PLUGINSDIR</td>
1.305 bacon 12432: <td>GEM_SPECFILE</td>
1.269 leot 12433: </tr>
12434: <tr>
1.312 gdt 12435: <td>GENERATE_PLIST</td>
1.316 cirnatda 12436: <td>GHC</td>
1.269 leot 12437: </tr>
12438: <tr>
1.316 cirnatda 12439: <td>GHOSTSCRIPT_REQD</td>
1.312 gdt 12440: <td>GITHUB_PROJECT</td>
1.292 leot 12441: </tr>
12442: <tr>
1.316 cirnatda 12443: <td>GITHUB_RELEASE</td>
1.315 cirnatda 12444: <td>GITHUB_SUBMODULES</td>
1.311 leot 12445: </tr>
12446: <tr>
1.316 cirnatda 12447: <td>GITHUB_TAG</td>
1.313 leot 12448: <td>GITHUB_TYPE</td>
1.269 leot 12449: </tr>
12450: <tr>
1.338 nia 12451: <td>GITLAB_PROJECT</td>
1.340 ! gutterid 12452: <td>GITLAB_RELEASE</td>
1.338 nia 12453: </tr>
12454: <tr>
1.340 ! gutterid 12455: <td>GITLAB_SUBMODULES</td>
! 12456: <td>GITLAB_TAG</td>
1.338 nia 12457: </tr>
12458: <tr>
1.340 ! gutterid 12459: <td>GITLAB_TYPE</td>
! 12460: <td>GNU</td>
1.338 nia 12461: </tr>
12462: <tr>
1.313 leot 12463: <td>GNU_CONFIGURE</td>
1.340 ! gutterid 12464: <td>GNU_CONFIGURE_INFODIR</td>
1.269 leot 12465: </tr>
12466: <tr>
1.313 leot 12467: <td>GNU_CONFIGURE_MANDIR</td>
1.340 ! gutterid 12468: <td>GNU_CONFIGURE_QUIET</td>
1.269 leot 12469: </tr>
12470: <tr>
1.313 leot 12471: <td>GNU_CONFIGURE_STRICT</td>
1.340 ! gutterid 12472: <td>GODEP_REDIRECTS</td>
1.269 leot 12473: </tr>
12474: <tr>
1.313 leot 12475: <td>GO_BUILD_PATTERN</td>
1.340 ! gutterid 12476: <td>GO_DEPS</td>
1.276 leot 12477: </tr>
12478: <tr>
1.313 leot 12479: <td>GO_DIST_BASE</td>
1.340 ! gutterid 12480: <td>GO_EXTRA_MOD_DIRS</td>
1.269 leot 12481: </tr>
12482: <tr>
1.316 cirnatda 12483: <td>GO_MODULE_FILES</td>
1.340 ! gutterid 12484: <td>GO_SRCPATH</td>
1.269 leot 12485: </tr>
12486: <tr>
1.316 cirnatda 12487: <td>GO_VERSION_DEFAULT</td>
1.340 ! gutterid 12488: <td>GROUP_SPECIFIC_PKGS</td>
1.269 leot 12489: </tr>
12490: <tr>
1.316 cirnatda 12491: <td>GRUB_NETWORK_CARDS</td>
1.340 ! gutterid 12492: <td>GRUB_PRESET_COMMAND</td>
1.311 leot 12493: </tr>
12494: <tr>
1.316 cirnatda 12495: <td>GRUB_SCAN_ARGS</td>
1.324 nia 12496: <td>GZIP</td>
1.338 nia 12497: </tr>
12498: <tr>
1.337 gutterid 12499: <td>HASKELL_ENABLE_DYNAMIC_EXECUTABLE</td>
1.338 nia 12500: <td>HASKELL_ENABLE_HADDOCK_DOCUMENTATION</td>
1.332 rillig 12501: </tr>
12502: <tr>
1.337 gutterid 12503: <td>HASKELL_ENABLE_LIBRARY_PROFILING</td>
1.338 nia 12504: <td>HASKELL_ENABLE_SHARED_LIBRARY</td>
1.335 nia 12505: </tr>
12506: <tr>
1.337 gutterid 12507: <td>HASKELL_OPTIMIZATION_LEVEL</td>
1.338 nia 12508: <td>HAS_CONFIGURE</td>
1.329 leot 12509: </tr>
12510: <tr>
1.332 rillig 12511: <td>HEADER_TEMPLATES</td>
1.340 ! gutterid 12512: <td>HOMEPAGE</td>
1.338 nia 12513: </tr>
12514: <tr>
1.335 nia 12515: <td>HOST_PKGTOOLS_ARGS</td>
1.340 ! gutterid 12516: <td>HOST_SPECIFIC_PKGS</td>
1.269 leot 12517: </tr>
12518: <tr>
1.335 nia 12519: <td>HOWL_GROUP</td>
1.340 ! gutterid 12520: <td>HOWL_USER</td>
1.305 bacon 12521: </tr>
12522: <tr>
1.335 nia 12523: <td>ICCBASE</td>
1.340 ! gutterid 12524: <td>ICECAST_CHROOTDIR</td>
1.269 leot 12525: </tr>
12526: <tr>
1.335 nia 12527: <td>ICON_THEMES</td>
1.340 ! gutterid 12528: <td>IDOBASE</td>
1.269 leot 12529: </tr>
12530: <tr>
1.335 nia 12531: <td>IGNORE_CCACHE</td>
1.340 ! gutterid 12532: <td>IGNORE_INFO_DIRS</td>
1.269 leot 12533: </tr>
12534: <tr>
1.335 nia 12535: <td>IGNORE_INTERACTIVE_FETCH</td>
1.340 ! gutterid 12536: <td>IMAKE</td>
1.269 leot 12537: </tr>
12538: <tr>
1.335 nia 12539: <td>IMAKEOPTS</td>
1.340 ! gutterid 12540: <td>IMAKE_MAKE</td>
1.269 leot 12541: </tr>
12542: <tr>
1.335 nia 12543: <td>IMAKE_MANINSTALL</td>
1.340 ! gutterid 12544: <td>IMAP_UW_CCLIENT_MBOX_FMT</td>
1.269 leot 12545: </tr>
12546: <tr>
1.335 nia 12547: <td>IMDICTDIR</td>
1.340 ! gutterid 12548: <td>INCOMPAT_CURSES</td>
1.269 leot 12549: </tr>
12550: <tr>
1.335 nia 12551: <td>INFO_DIR</td>
1.340 ! gutterid 12552: <td>INFO_FILES</td>
1.269 leot 12553: </tr>
12554: <tr>
1.335 nia 12555: <td>INFO_FILES_VERBOSE</td>
1.340 ! gutterid 12556: <td>INFO_MSG</td>
1.269 leot 12557: </tr>
12558: <tr>
1.335 nia 12559: <td>INIT_SYSTEM</td>
1.340 ! gutterid 12560: <td>INN_DATA_DIR</td>
1.287 rillig 12561: </tr>
12562: <tr>
1.335 nia 12563: <td>INN_GROUP</td>
1.340 ! gutterid 12564: <td>INN_USER</td>
1.269 leot 12565: </tr>
12566: <tr>
1.335 nia 12567: <td>INSTALLATION_DIRS</td>
1.340 ! gutterid 12568: <td>INSTALLATION_DIRS_FROM_PLIST</td>
1.269 leot 12569: </tr>
12570: <tr>
1.335 nia 12571: <td>INSTALL_ENV</td>
1.340 ! gutterid 12572: <td>INSTALL_SH_OVERRIDE</td>
1.269 leot 12573: </tr>
12574: <tr>
1.335 nia 12575: <td>INSTALL_SRC</td>
1.340 ! gutterid 12576: <td>INSTALL_TEMPLATES</td>
1.269 leot 12577: </tr>
12578: <tr>
1.335 nia 12579: <td>INSTALL_UNSTRIPPED</td>
1.340 ! gutterid 12580: <td>IRCD_HYBRID_IRC_GROUP</td>
1.269 leot 12581: </tr>
12582: <tr>
1.335 nia 12583: <td>IRCD_HYBRID_IRC_USER</td>
1.340 ! gutterid 12584: <td>IRCD_HYBRID_MAXCONN</td>
1.269 leot 12585: </tr>
12586: <tr>
1.335 nia 12587: <td>IRCD_HYBRID_NICLEN</td>
1.340 ! gutterid 12588: <td>IRCD_HYBRID_SYSLOG_EVENTS</td>
1.269 leot 12589: </tr>
12590: <tr>
1.335 nia 12591: <td>IRCD_HYBRID_SYSLOG_FACILITY</td>
1.340 ! gutterid 12592: <td>IRCD_HYBRID_TOPICLEN</td>
1.269 leot 12593: </tr>
12594: <tr>
1.335 nia 12595: <td>IRIX</td>
1.340 ! gutterid 12596: <td>IRRD_USE_PGP</td>
1.269 leot 12597: </tr>
12598: <tr>
1.335 nia 12599: <td>JABBERD_GROUP</td>
1.340 ! gutterid 12600: <td>JABBERD_LOGDIR</td>
1.269 leot 12601: </tr>
12602: <tr>
1.335 nia 12603: <td>JABBERD_PIDDIR</td>
1.340 ! gutterid 12604: <td>JABBERD_SPOOLDIR</td>
1.292 leot 12605: </tr>
12606: <tr>
1.335 nia 12607: <td>JABBERD_USER</td>
1.340 ! gutterid 12608: <td>JAVA_BINPREFIX</td>
1.311 leot 12609: </tr>
12610: <tr>
1.335 nia 12611: <td>JAVA_CLASSPATH</td>
1.340 ! gutterid 12612: <td>JAVA_HOME</td>
1.269 leot 12613: </tr>
12614: <tr>
1.335 nia 12615: <td>JAVA_LD_LIBRARY_PATH</td>
1.340 ! gutterid 12616: <td>JAVA_NAME</td>
1.332 rillig 12617: </tr>
12618: <tr>
1.335 nia 12619: <td>JAVA_UNLIMIT</td>
1.340 ! gutterid 12620: <td>JAVA_WRAPPERS</td>
1.332 rillig 12621: </tr>
12622: <tr>
1.335 nia 12623: <td>JPEG_ACCEPTED</td>
1.340 ! gutterid 12624: <td>JPEG_DEFAULT</td>
1.269 leot 12625: </tr>
12626: <tr>
1.335 nia 12627: <td>KERBEROS</td>
1.340 ! gutterid 12628: <td>KERMIT_SUID_UUCP</td>
1.269 leot 12629: </tr>
12630: <tr>
1.335 nia 12631: <td>KJS_USE_PCRE</td>
1.340 ! gutterid 12632: <td>KNEWS_DOMAIN_FILE</td>
1.269 leot 12633: </tr>
12634: <tr>
1.335 nia 12635: <td>KNEWS_DOMAIN_NAME</td>
1.340 ! gutterid 12636: <td>KRB5_ACCEPTED</td>
1.269 leot 12637: </tr>
12638: <tr>
1.335 nia 12639: <td>KRB5_DEFAULT</td>
1.340 ! gutterid 12640: <td>LANGUAGES</td>
1.292 leot 12641: </tr>
12642: <tr>
1.335 nia 12643: <td>LAPACKE_LIBS</td>
1.340 ! gutterid 12644: <td>LAPACK_LIBS</td>
1.271 brook 12645: </tr>
12646: <tr>
1.335 nia 12647: <td>LATEX2HTML_ICONPATH</td>
1.340 ! gutterid 12648: <td>LDCONFIG_ADD_CMD</td>
1.269 leot 12649: </tr>
12650: <tr>
1.335 nia 12651: <td>LDCONFIG_REMOVE_CMD</td>
1.340 ! gutterid 12652: <td>LDD</td>
1.269 leot 12653: </tr>
12654: <tr>
1.335 nia 12655: <td>LEAFNODE_DATA_DIR</td>
1.340 ! gutterid 12656: <td>LEAFNODE_GROUP</td>
1.269 leot 12657: </tr>
12658: <tr>
1.335 nia 12659: <td>LEAFNODE_USER</td>
1.340 ! gutterid 12660: <td>LIBDVDCSS_HOMEPAGE</td>
1.269 leot 12661: </tr>
12662: <tr>
1.335 nia 12663: <td>LIBDVDCSS_MASTER_SITES</td>
1.340 ! gutterid 12664: <td>LIBRSVG_TYPE</td>
1.320 wiz 12665: </tr>
12666: <tr>
1.335 nia 12667: <td>LIBTOOL</td>
1.340 ! gutterid 12668: <td>LIBTOOLIZE_PLIST</td>
1.270 leot 12669: </tr>
12670: <tr>
1.335 nia 12671: <td>LIBTOOL_M4_OVERRIDE</td>
1.340 ! gutterid 12672: <td>LIBUSB_TYPE</td>
1.327 wiz 12673: </tr>
12674: <tr>
1.335 nia 12675: <td>LICENSE</td>
1.340 ! gutterid 12676: <td>LINKER_RPATH_FLAG</td>
1.269 leot 12677: </tr>
12678: <tr>
1.335 nia 12679: <td>LINK_RPATH_FLAG</td>
12680: <td>LINUX_LOCALES</td>
1.338 nia 12681: </tr>
12682: <tr>
1.337 gutterid 12683: <td>LOCALBASE</td>
1.338 nia 12684: <td>LOCALBASE_LOCKTYPE</td>
1.269 leot 12685: </tr>
12686: <tr>
1.337 gutterid 12687: <td>LOCALPATCHES</td>
1.338 nia 12688: <td>LOVE_DATA</td>
1.329 leot 12689: </tr>
12690: <tr>
1.337 gutterid 12691: <td>LOVE_GAME</td>
1.338 nia 12692: <td>LOVE_VERSION</td>
1.269 leot 12693: </tr>
12694: <tr>
1.337 gutterid 12695: <td>LP32PLATFORMS</td>
1.338 nia 12696: <td>LP64PLATFORMS</td>
1.269 leot 12697: </tr>
12698: <tr>
1.337 gutterid 12699: <td>LUA_BUSTED_ARGS</td>
1.338 nia 12700: <td>LUA_CDIR</td>
1.269 leot 12701: </tr>
12702: <tr>
1.337 gutterid 12703: <td>LUA_COMPILER</td>
1.338 nia 12704: <td>LUA_DOCDIR</td>
1.336 nia 12705: </tr>
12706: <tr>
1.337 gutterid 12707: <td>LUA_EXAMPLESDIR</td>
1.338 nia 12708: <td>LUA_INCDIR</td>
1.333 nia 12709: </tr>
12710: <tr>
1.337 gutterid 12711: <td>LUA_INTERPRETER</td>
1.338 nia 12712: <td>LUA_LDIR</td>
1.333 nia 12713: </tr>
12714: <tr>
1.337 gutterid 12715: <td>LUA_LINKER_MAGIC</td>
1.338 nia 12716: <td>LUA_PKGPREFIX</td>
1.333 nia 12717: </tr>
12718: <tr>
1.337 gutterid 12719: <td>LUA_SELF_CONFLICT</td>
1.338 nia 12720: <td>LUA_USE_BUSTED</td>
1.333 nia 12721: </tr>
12722: <tr>
1.337 gutterid 12723: <td>LUA_VERSIONS_ACCEPTED</td>
1.338 nia 12724: <td>LUA_VERSIONS_INCOMPATIBLE</td>
1.333 nia 12725: </tr>
12726: <tr>
1.337 gutterid 12727: <td>LUA_VERSION_DEFAULT</td>
1.338 nia 12728: <td>LUA_VERSION_REQD</td>
1.333 nia 12729: </tr>
12730: <tr>
1.337 gutterid 12731: <td>Lua</td>
1.338 nia 12732: <td>MACHINE_PLATFORM</td>
1.333 nia 12733: </tr>
12734: <tr>
1.337 gutterid 12735: <td>MAILAGENT_DOMAIN</td>
1.338 nia 12736: <td>MAILAGENT_EMAIL</td>
1.269 leot 12737: </tr>
12738: <tr>
1.337 gutterid 12739: <td>MAILAGENT_FQDN</td>
1.338 nia 12740: <td>MAILAGENT_ORGANIZATION</td>
1.320 wiz 12741: </tr>
12742: <tr>
1.332 rillig 12743: <td>MAJORDOMO_HOMEDIR</td>
1.340 ! gutterid 12744: <td>MAKEINFO_ARGS</td>
1.269 leot 12745: </tr>
12746: <tr>
1.336 nia 12747: <td>MAKE_DIRS</td>
1.340 ! gutterid 12748: <td>MAKE_DIRS_PERMS</td>
1.327 wiz 12749: </tr>
12750: <tr>
1.336 nia 12751: <td>MAKE_ENV</td>
1.340 ! gutterid 12752: <td>MAKE_FILE</td>
1.269 leot 12753: </tr>
12754: <tr>
1.336 nia 12755: <td>MAKE_FLAGS</td>
1.340 ! gutterid 12756: <td>MAKE_JOBS</td>
1.269 leot 12757: </tr>
12758: <tr>
1.336 nia 12759: <td>MAKE_JOBS_SAFE</td>
1.340 ! gutterid 12760: <td>MAKE_PROGRAM</td>
1.269 leot 12761: </tr>
12762: <tr>
1.336 nia 12763: <td>MANCOMPRESSED_IF_MANZ</td>
1.340 ! gutterid 12764: <td>MANINSTALL</td>
1.303 bacon 12765: </tr>
12766: <tr>
1.336 nia 12767: <td>MANZ</td>
1.340 ! gutterid 12768: <td>MASTER_SITES</td>
1.269 leot 12769: </tr>
12770: <tr>
1.336 nia 12771: <td>MASTER_SITE_BACKUP</td>
1.340 ! gutterid 12772: <td>MASTER_SITE_LOCAL</td>
1.269 leot 12773: </tr>
12774: <tr>
1.336 nia 12775: <td>MASTER_SITE_MOZILLA</td>
1.340 ! gutterid 12776: <td>MASTER_SITE_OVERRIDE</td>
1.269 leot 12777: </tr>
12778: <tr>
1.336 nia 12779: <td>MASTER_SITE_PERL_CPAN</td>
1.340 ! gutterid 12780: <td>MASTER_SORT</td>
1.269 leot 12781: </tr>
12782: <tr>
1.336 nia 12783: <td>MASTER_SORT_RANDOM</td>
1.340 ! gutterid 12784: <td>MASTER_SORT_REGEX</td>
1.269 leot 12785: </tr>
12786: <tr>
1.336 nia 12787: <td>MECAB_CHARSET</td>
1.340 ! gutterid 12788: <td>MEDIATOMB_GROUP</td>
1.269 leot 12789: </tr>
12790: <tr>
1.336 nia 12791: <td>MEDIATOMB_USER</td>
1.340 ! gutterid 12792: <td>MIPSPROBASE</td>
1.269 leot 12793: </tr>
12794: <tr>
1.336 nia 12795: <td>MIREDO_GROUP</td>
1.340 ! gutterid 12796: <td>MIREDO_USER</td>
1.269 leot 12797: </tr>
12798: <tr>
1.336 nia 12799: <td>MISSING_FEATURES</td>
1.340 ! gutterid 12800: <td>MKDIR</td>
1.269 leot 12801: </tr>
12802: <tr>
1.336 nia 12803: <td>MKPIE_SUPPORTED</td>
1.340 ! gutterid 12804: <td>MLDONKEY_GROUP</td>
1.269 leot 12805: </tr>
12806: <tr>
1.336 nia 12807: <td>MLDONKEY_HOME</td>
1.340 ! gutterid 12808: <td>MLDONKEY_USER</td>
1.322 leot 12809: </tr>
12810: <tr>
1.336 nia 12811: <td>MONOTONE_GROUP</td>
1.340 ! gutterid 12812: <td>MONOTONE_USER</td>
1.269 leot 12813: </tr>
12814: <tr>
1.336 nia 12815: <td>MOTIFBASE</td>
1.340 ! gutterid 12816: <td>MOTIF_TYPE</td>
1.269 leot 12817: </tr>
12818: <tr>
1.336 nia 12819: <td>MOTIF_TYPE_DEFAULT</td>
1.340 ! gutterid 12820: <td>MPI_TYPE</td>
1.269 leot 12821: </tr>
12822: <tr>
1.336 nia 12823: <td>MSGFMT_STRIP_MSGCTXT</td>
1.340 ! gutterid 12824: <td>MSGFMT_STRIP_MSGID_PLURAL</td>
1.269 leot 12825: </tr>
12826: <tr>
1.336 nia 12827: <td>MTOOLS_ENABLE_FLOPPYD</td>
12828: <td>MV</td>
1.338 nia 12829: </tr>
12830: <tr>
1.337 gutterid 12831: <td>MYSQL_CHARSET</td>
1.338 nia 12832: <td>MYSQL_DATADIR</td>
1.329 leot 12833: </tr>
12834: <tr>
1.337 gutterid 12835: <td>MYSQL_EXTRA_CHARSET</td>
1.338 nia 12836: <td>MYSQL_GROUP</td>
1.269 leot 12837: </tr>
12838: <tr>
1.337 gutterid 12839: <td>MYSQL_USER</td>
1.338 nia 12840: <td>MYSQL_VERSION</td>
1.320 wiz 12841: </tr>
12842: <tr>
1.337 gutterid 12843: <td>MYSQL_VERSIONS_ACCEPTED</td>
1.338 nia 12844: <td>MYSQL_VERSIONS_ALL</td>
1.269 leot 12845: </tr>
12846: <tr>
1.337 gutterid 12847: <td>MYSQL_VERSION_DEFAULT</td>
1.338 nia 12848: <td>NAGIOSCMD_GROUP</td>
1.269 leot 12849: </tr>
12850: <tr>
1.337 gutterid 12851: <td>NAGIOSDIR</td>
1.338 nia 12852: <td>NAGIOS_GROUP</td>
1.269 leot 12853: </tr>
12854: <tr>
1.337 gutterid 12855: <td>NAGIOS_USER</td>
1.338 nia 12856: <td>NATIVE_APPEND_ABI</td>
1.309 gutterid 12857: </tr>
12858: <tr>
1.337 gutterid 12859: <td>NATIVE_APPEND_ELF</td>
1.338 nia 12860: <td>NATIVE_EXEC_FMT</td>
1.269 leot 12861: </tr>
12862: <tr>
1.337 gutterid 12863: <td>NATIVE_MACHINE_PLATFORM</td>
1.338 nia 12864: <td>NATIVE_OBJECT_FMT</td>
1.269 leot 12865: </tr>
12866: <tr>
1.337 gutterid 12867: <td>NBPAX_PROGRAM_PREFIX</td>
1.338 nia 12868: <td>NETBSD_LOGIN_NAME</td>
1.269 leot 12869: </tr>
12870: <tr>
1.337 gutterid 12871: <td>NMH_EDITOR</td>
1.338 nia 12872: <td>NMH_MTA</td>
1.269 leot 12873: </tr>
12874: <tr>
1.337 gutterid 12875: <td>NMH_PAGER</td>
1.338 nia 12876: <td>NODE_VERSIONS_ACCEPTED</td>
1.269 leot 12877: </tr>
12878: <tr>
1.337 gutterid 12879: <td>NODE_VERSIONS_INCOMPATIBLE</td>
1.338 nia 12880: <td>NODE_VERSION_DEFAULT</td>
1.269 leot 12881: </tr>
12882: <tr>
1.337 gutterid 12883: <td>NODE_VERSION_REQD</td>
1.338 nia 12884: <td>NOLOGIN</td>
1.333 nia 12885: </tr>
12886: <tr>
1.337 gutterid 12887: <td>NOTE</td>
1.338 nia 12888: <td>NOT_FOR_PLATFORM</td>
1.333 nia 12889: </tr>
12890: <tr>
1.337 gutterid 12891: <td>NOT_PAX_ASLR_SAFE</td>
1.338 nia 12892: <td>NOT_PAX_MPROTECT_SAFE</td>
1.293 rillig 12893: </tr>
12894: <tr>
1.337 gutterid 12895: <td>NO_BUILD</td>
1.338 nia 12896: <td>NO_CHECKSUM</td>
1.269 leot 12897: </tr>
12898: <tr>
1.337 gutterid 12899: <td>NO_CONFIGURE</td>
1.338 nia 12900: <td>NO_SKIP</td>
1.269 leot 12901: </tr>
12902: <tr>
1.337 gutterid 12903: <td>NS_PREFERRED</td>
1.338 nia 12904: <td>NULLMAILER_GROUP</td>
1.269 leot 12905: </tr>
12906: <tr>
1.337 gutterid 12907: <td>NULLMAILER_USER</td>
1.338 nia 12908: <td>OASIS</td>
1.269 leot 12909: </tr>
12910: <tr>
1.337 gutterid 12911: <td>OASIS_BUILD_ARGS</td>
1.338 nia 12912: <td>OBJHOSTNAME</td>
1.269 leot 12913: </tr>
12914: <tr>
1.337 gutterid 12915: <td>OBJMACHINE</td>
1.338 nia 12916: <td>OCAML_FINDLIB_DIRS</td>
1.269 leot 12917: </tr>
12918: <tr>
1.337 gutterid 12919: <td>OCAML_FINDLIB_REGISTER</td>
1.338 nia 12920: <td>OCAML_FINDLIB_REGISTER_VERBOSE</td>
1.269 leot 12921: </tr>
12922: <tr>
1.337 gutterid 12923: <td>OCAML_SITELIBDIR</td>
1.338 nia 12924: <td>OCAML_TOPKG_DOCDIR</td>
1.269 leot 12925: </tr>
12926: <tr>
1.337 gutterid 12927: <td>OCAML_USE_DUNE</td>
1.338 nia 12928: <td>OCAML_USE_FINDLIB</td>
1.269 leot 12929: </tr>
12930: <tr>
1.337 gutterid 12931: <td>OCAML_USE_OASIS</td>
1.338 nia 12932: <td>OCAML_USE_OASIS_DYNRUN</td>
1.269 leot 12933: </tr>
12934: <tr>
1.337 gutterid 12935: <td>OCAML_USE_OPAM</td>
1.340 ! gutterid 12936: <td>OCAML_USE_TOPKG</td>
1.269 leot 12937: </tr>
12938: <tr>
1.338 nia 12939: <td>OMF</td>
1.340 ! gutterid 12940: <td>ONLY_FOR_COMPILER</td>
1.269 leot 12941: </tr>
12942: <tr>
1.338 nia 12943: <td>ONLY_FOR_PLATFORM</td>
1.340 ! gutterid 12944: <td>OPENSSH_CHROOT</td>
1.269 leot 12945: </tr>
12946: <tr>
1.338 nia 12947: <td>OPENSSH_GROUP</td>
1.340 ! gutterid 12948: <td>OPENSSH_USER</td>
1.269 leot 12949: </tr>
12950: <tr>
1.338 nia 12951: <td>OPSYS</td>
1.340 ! gutterid 12952: <td>OPSYS_EMULDIR</td>
1.269 leot 12953: </tr>
12954: <tr>
1.338 nia 12955: <td>OPSYS_VERSION</td>
1.340 ! gutterid 12956: <td>OS</td>
1.269 leot 12957: </tr>
12958: <tr>
1.338 nia 12959: <td>OSS_TYPE</td>
1.340 ! gutterid 12960: <td>OSX</td>
1.269 leot 12961: </tr>
12962: <tr>
1.338 nia 12963: <td>OSX_TOLERATE_SDK_SKEW</td>
1.340 ! gutterid 12964: <td>OS_VARIANT</td>
1.338 nia 12965: </tr>
12966: <tr>
12967: <td>OS_VERSION</td>
1.340 ! gutterid 12968: <td>OTF_FONTS_DIR</td>
1.327 wiz 12969: </tr>
12970: <tr>
1.338 nia 12971: <td>OVERRIDE_DIRDEPTH</td>
1.340 ! gutterid 12972: <td>OVERRIDE_GEMSPEC</td>
1.329 leot 12973: </tr>
12974: <tr>
1.338 nia 12975: <td>OVERRIDE_GNU_CONFIG_SCRIPTS</td>
1.336 nia 12976: <td>OWN_DIRS</td>
1.320 wiz 12977: </tr>
12978: <tr>
1.335 nia 12979: <td>OWN_DIRS_PERMS</td>
1.336 nia 12980: <td>P4GROUP</td>
1.269 leot 12981: </tr>
12982: <tr>
1.335 nia 12983: <td>P4PORT</td>
1.336 nia 12984: <td>P4ROOT</td>
1.269 leot 12985: </tr>
12986: <tr>
1.335 nia 12987: <td>P4USER</td>
1.336 nia 12988: <td>PACKAGES</td>
1.269 leot 12989: </tr>
12990: <tr>
1.335 nia 12991: <td>PALMOS_DEFAULT_SDK</td>
1.336 nia 12992: <td>PAMBASE</td>
1.269 leot 12993: </tr>
12994: <tr>
1.335 nia 12995: <td>PAM_DEFAULT</td>
1.336 nia 12996: <td>PAPERSIZE</td>
1.269 leot 12997: </tr>
12998: <tr>
1.335 nia 12999: <td>PASSIVE_FETCH</td>
1.336 nia 13000: <td>PATCHDIR</td>
1.269 leot 13001: </tr>
13002: <tr>
1.335 nia 13003: <td>PATCHFILES</td>
1.336 nia 13004: <td>PATCH_ARGS</td>
1.324 nia 13005: </tr>
13006: <tr>
1.335 nia 13007: <td>PATCH_DEBUG</td>
1.336 nia 13008: <td>PATCH_DIST_ARGS</td>
1.269 leot 13009: </tr>
13010: <tr>
1.335 nia 13011: <td>PATCH_DIST_CAT</td>
1.336 nia 13012: <td>PATCH_DIST_STRIP</td>
1.269 leot 13013: </tr>
13014: <tr>
1.335 nia 13015: <td>PATCH_FUZZ_FACTOR</td>
1.336 nia 13016: <td>PATCH_STRIP</td>
1.284 rillig 13017: </tr>
13018: <tr>
1.335 nia 13019: <td>PATH</td>
1.336 nia 13020: <td>PCCBASE</td>
1.269 leot 13021: </tr>
13022: <tr>
1.335 nia 13023: <td>PEAR_CMD</td>
1.336 nia 13024: <td>PEAR_LIB</td>
1.332 rillig 13025: </tr>
13026: <tr>
1.335 nia 13027: <td>PEAR_PACKAGE_XML</td>
1.336 nia 13028: <td>PERL5</td>
1.320 wiz 13029: </tr>
13030: <tr>
1.335 nia 13031: <td>PERL5_CONFIGURE</td>
1.336 nia 13032: <td>PERL5_CONFIGURE_DIRS</td>
1.292 leot 13033: </tr>
13034: <tr>
1.335 nia 13035: <td>PERL5_LDFLAGS</td>
1.336 nia 13036: <td>PERL5_LICENSE</td>
1.274 rillig 13037: </tr>
13038: <tr>
1.335 nia 13039: <td>PERL5_MODULE_TYPE</td>
1.336 nia 13040: <td>PERL5_PACKLIST</td>
1.274 rillig 13041: </tr>
13042: <tr>
1.335 nia 13043: <td>PERL5_PACKLIST_DIR</td>
1.336 nia 13044: <td>PERL5_PERLBASE</td>
1.269 leot 13045: </tr>
13046: <tr>
1.335 nia 13047: <td>PERL5_SITEBASE</td>
1.336 nia 13048: <td>PERL5_USE_PACKLIST</td>
1.269 leot 13049: </tr>
13050: <tr>
1.335 nia 13051: <td>PERL5_VENDORBASE</td>
1.336 nia 13052: <td>PFCTL</td>
1.269 leot 13053: </tr>
13054: <tr>
1.335 nia 13055: <td>PFVAR_H</td>
1.336 nia 13056: <td>PF_VERSION</td>
1.269 leot 13057: </tr>
13058: <tr>
1.335 nia 13059: <td>PGGROUP</td>
1.336 nia 13060: <td>PGHOME</td>
1.269 leot 13061: </tr>
13062: <tr>
1.335 nia 13063: <td>PGPKGSRCDIR</td>
1.336 nia 13064: <td>PGSQL_TYPE</td>
1.269 leot 13065: </tr>
13066: <tr>
1.335 nia 13067: <td>PGSQL_VERSION</td>
1.336 nia 13068: <td>PGSQL_VERSIONS_ACCEPTED</td>
1.269 leot 13069: </tr>
13070: <tr>
1.335 nia 13071: <td>PGSQL_VERSION_DEFAULT</td>
1.336 nia 13072: <td>PGUSER</td>
1.269 leot 13073: </tr>
13074: <tr>
1.335 nia 13075: <td>PG_LIB_EXT</td>
1.336 nia 13076: <td>PHP</td>
1.269 leot 13077: </tr>
13078: <tr>
1.335 nia 13079: <td>PHPCOMMON_MK</td>
1.336 nia 13080: <td>PHPPKGSRCDIR</td>
1.269 leot 13081: </tr>
13082: <tr>
1.335 nia 13083: <td>PHP_BASE_VERS</td>
1.336 nia 13084: <td>PHP_CHECK_INSTALLED</td>
1.269 leot 13085: </tr>
13086: <tr>
1.335 nia 13087: <td>PHP_EXTENSION_DIR</td>
1.336 nia 13088: <td>PHP_INITIAL_TEENY</td>
1.269 leot 13089: </tr>
13090: <tr>
1.335 nia 13091: <td>PHP_PKG_PREFIX</td>
1.336 nia 13092: <td>PHP_VERSION</td>
1.269 leot 13093: </tr>
13094: <tr>
1.335 nia 13095: <td>PHP_VERSIONS_ACCEPTED</td>
1.336 nia 13096: <td>PHP_VERSIONS_INCOMPATIBLE</td>
1.269 leot 13097: </tr>
13098: <tr>
1.335 nia 13099: <td>PHP_VERSION_DEFAULT</td>
1.336 nia 13100: <td>PHP_VERSION_REQD</td>
1.269 leot 13101: </tr>
13102: <tr>
1.335 nia 13103: <td>PILRC_USE_GTK</td>
1.336 nia 13104: <td>PKGCONFIG_BASE</td>
1.269 leot 13105: </tr>
13106: <tr>
1.335 nia 13107: <td>PKGCONFIG_FILE</td>
1.336 nia 13108: <td>PKGCONFIG_OVERRIDE</td>
1.269 leot 13109: </tr>
13110: <tr>
1.335 nia 13111: <td>PKGCONFIG_OVERRIDE_STAGE</td>
1.336 nia 13112: <td>PKGDIR</td>
1.269 leot 13113: </tr>
13114: <tr>
1.335 nia 13115: <td>PKGGNUDIR</td>
1.336 nia 13116: <td>PKGINFODIR</td>
1.269 leot 13117: </tr>
13118: <tr>
1.335 nia 13119: <td>PKGLOCALEDIR</td>
1.336 nia 13120: <td>PKGMANDIR</td>
1.269 leot 13121: </tr>
13122: <tr>
1.335 nia 13123: <td>PKGNAME</td>
1.336 nia 13124: <td>PKGNAME_REQD</td>
1.269 leot 13125: </tr>
13126: <tr>
1.335 nia 13127: <td>PKGPATH</td>
1.336 nia 13128: <td>PKGREVISION</td>
1.269 leot 13129: </tr>
13130: <tr>
1.335 nia 13131: <td>PKGSRC_BLAS_TYPES</td>
1.336 nia 13132: <td>PKGSRC_CHANGES</td>
1.269 leot 13133: </tr>
13134: <tr>
1.335 nia 13135: <td>PKGSRC_COMPILER</td>
1.336 nia 13136: <td>PKGSRC_KEEP_BIN_PKGS</td>
1.269 leot 13137: </tr>
13138: <tr>
1.335 nia 13139: <td>PKGSRC_LOCKTYPE</td>
1.336 nia 13140: <td>PKGSRC_MAKE_ENV</td>
1.292 leot 13141: </tr>
13142: <tr>
1.335 nia 13143: <td>PKGSRC_MESSAGE_RECIPIENTS</td>
1.336 nia 13144: <td>PKGSRC_MKPIE</td>
1.269 leot 13145: </tr>
13146: <tr>
1.335 nia 13147: <td>PKGSRC_MKREPRO</td>
1.336 nia 13148: <td>PKGSRC_OVERRIDE_MKPIE</td>
1.274 rillig 13149: </tr>
13150: <tr>
1.335 nia 13151: <td>PKGSRC_RUN_TEST</td>
1.336 nia 13152: <td>PKGSRC_SETENV</td>
1.269 leot 13153: </tr>
13154: <tr>
1.335 nia 13155: <td>PKGSRC_SLEEPSECS</td>
1.336 nia 13156: <td>PKGSRC_TODO</td>
1.269 leot 13157: </tr>
13158: <tr>
1.335 nia 13159: <td>PKGSRC_USE_CTF</td>
1.336 nia 13160: <td>PKGSRC_USE_FORTIFY</td>
1.269 leot 13161: </tr>
13162: <tr>
1.335 nia 13163: <td>PKGSRC_USE_RELRO</td>
1.336 nia 13164: <td>PKGSRC_USE_SSP</td>
1.269 leot 13165: </tr>
13166: <tr>
1.335 nia 13167: <td>PKGSRC_USE_STACK_CHECK</td>
1.336 nia 13168: <td>PKGTASKS_DATAFILE</td>
1.269 leot 13169: </tr>
13170: <tr>
1.335 nia 13171: <td>PKGTOOLS_ARGS</td>
1.336 nia 13172: <td>PKGTOOLS_ENV</td>
1.269 leot 13173: </tr>
13174: <tr>
1.335 nia 13175: <td>PKG_ALTERNATIVES</td>
1.336 nia 13176: <td>PKG_APACHE</td>
1.269 leot 13177: </tr>
13178: <tr>
1.335 nia 13179: <td>PKG_APACHE_ACCEPTED</td>
1.336 nia 13180: <td>PKG_APACHE_DEFAULT</td>
1.269 leot 13181: </tr>
13182: <tr>
1.335 nia 13183: <td>PKG_BEST_EXISTS</td>
1.336 nia 13184: <td>PKG_BUILD_OPTIONS</td>
1.269 leot 13185: </tr>
13186: <tr>
1.335 nia 13187: <td>PKG_COMPRESSION</td>
1.336 nia 13188: <td>PKG_CONFIG</td>
1.269 leot 13189: </tr>
13190: <tr>
1.335 nia 13191: <td>PKG_CONFIG_PERMS</td>
1.336 nia 13192: <td>PKG_CREATE_USERGROUP</td>
1.269 leot 13193: </tr>
13194: <tr>
1.335 nia 13195: <td>PKG_DB_TMPDIR</td>
1.336 nia 13196: <td>PKG_DEBUG_LEVEL</td>
1.269 leot 13197: </tr>
13198: <tr>
1.335 nia 13199: <td>PKG_DEFAULT_OPTIONS</td>
1.336 nia 13200: <td>PKG_DESTDIR_SUPPORT</td>
1.269 leot 13201: </tr>
13202: <tr>
1.335 nia 13203: <td>PKG_DEVELOPER</td>
1.336 nia 13204: <td>PKG_DISABLED_OPTIONS</td>
1.269 leot 13205: </tr>
13206: <tr>
1.335 nia 13207: <td>PKG_FATAL_ERRORS</td>
1.336 nia 13208: <td>PKG_FC</td>
1.269 leot 13209: </tr>
13210: <tr>
1.335 nia 13211: <td>PKG_FILELIST_CMD</td>
1.336 nia 13212: <td>PKG_GECOS</td>
1.269 leot 13213: </tr>
13214: <tr>
1.335 nia 13215: <td>PKG_GID</td>
1.336 nia 13216: <td>PKG_GROUPS</td>
1.269 leot 13217: </tr>
13218: <tr>
1.335 nia 13219: <td>PKG_GROUPS_VARS</td>
1.336 nia 13220: <td>PKG_HOME</td>
1.269 leot 13221: </tr>
13222: <tr>
1.335 nia 13223: <td>PKG_INIT_SCRIPTS</td>
1.336 nia 13224: <td>PKG_JAVA_HOME</td>
1.269 leot 13225: </tr>
13226: <tr>
1.335 nia 13227: <td>PKG_JVM</td>
1.336 nia 13228: <td>PKG_JVMS_ACCEPTED</td>
1.269 leot 13229: </tr>
13230: <tr>
1.335 nia 13231: <td>PKG_JVM_DEFAULT</td>
1.336 nia 13232: <td>PKG_LEGACY_OPTIONS</td>
1.269 leot 13233: </tr>
13234: <tr>
1.335 nia 13235: <td>PKG_LIBTOOL</td>
1.336 nia 13236: <td>PKG_OPTIONS</td>
1.269 leot 13237: </tr>
13238: <tr>
1.335 nia 13239: <td>PKG_OPTIONS_DEPRECATED_WARNINGS</td>
1.336 nia 13240: <td>PKG_OPTIONS_LEGACY_OPTS</td>
1.269 leot 13241: </tr>
13242: <tr>
1.335 nia 13243: <td>PKG_OPTIONS_LEGACY_VARS</td>
1.336 nia 13244: <td>PKG_OPTIONS_NONEMPTY_SETS</td>
1.269 leot 13245: </tr>
13246: <tr>
1.335 nia 13247: <td>PKG_OPTIONS_OPTIONAL_GROUPS</td>
1.336 nia 13248: <td>PKG_OPTIONS_REQUIRED_GROUPS</td>
1.269 leot 13249: </tr>
13250: <tr>
1.335 nia 13251: <td>PKG_OPTIONS_VAR</td>
1.336 nia 13252: <td>PKG_PHP</td>
1.269 leot 13253: </tr>
13254: <tr>
1.335 nia 13255: <td>PKG_PHP_MAJOR_VERS</td>
1.336 nia 13256: <td>PKG_PHP_VERSION</td>
1.269 leot 13257: </tr>
13258: <tr>
1.335 nia 13259: <td>PKG_RCD_SCRIPTS</td>
1.336 nia 13260: <td>PKG_REFCOUNT_DBDIR</td>
1.269 leot 13261: </tr>
13262: <tr>
1.335 nia 13263: <td>PKG_REGISTER_SHELLS</td>
1.336 nia 13264: <td>PKG_RESUME_TRANSFERS</td>
1.269 leot 13265: </tr>
13266: <tr>
1.335 nia 13267: <td>PKG_SHELL</td>
1.336 nia 13268: <td>PKG_SUGGESTED_OPTIONS</td>
1.269 leot 13269: </tr>
13270: <tr>
1.335 nia 13271: <td>PKG_SUPPORTED_OPTIONS</td>
1.336 nia 13272: <td>PKG_SYSCONFBASE</td>
1.269 leot 13273: </tr>
13274: <tr>
1.335 nia 13275: <td>PKG_SYSCONFBASEDIR</td>
1.336 nia 13276: <td>PKG_SYSCONFDIR</td>
1.269 leot 13277: </tr>
13278: <tr>
1.335 nia 13279: <td>PKG_SYSCONFDIR_PERMS</td>
1.336 nia 13280: <td>PKG_SYSCONFSUBDIR</td>
1.269 leot 13281: </tr>
13282: <tr>
1.335 nia 13283: <td>PKG_SYSCONFVAR</td>
1.336 nia 13284: <td>PKG_TOOLS_BIN</td>
1.269 leot 13285: </tr>
13286: <tr>
1.335 nia 13287: <td>PKG_UID</td>
1.336 nia 13288: <td>PKG_UPDATE_FONTS_DB</td>
1.269 leot 13289: </tr>
13290: <tr>
1.335 nia 13291: <td>PKG_USERS</td>
1.336 nia 13292: <td>PKG_USERS_VARS</td>
1.269 leot 13293: </tr>
13294: <tr>
1.335 nia 13295: <td>PKG_VERBOSE</td>
1.336 nia 13296: <td>PLEASE</td>
1.269 leot 13297: </tr>
13298: <tr>
1.335 nia 13299: <td>PLIST</td>
1.336 nia 13300: <td>PLIST_AWK</td>
1.269 leot 13301: </tr>
13302: <tr>
1.335 nia 13303: <td>PLIST_AWK_ENV</td>
1.336 nia 13304: <td>PLIST_SRC</td>
1.269 leot 13305: </tr>
13306: <tr>
1.335 nia 13307: <td>PLIST_SUBST</td>
1.336 nia 13308: <td>PLIST_TYPE</td>
1.269 leot 13309: </tr>
13310: <tr>
1.335 nia 13311: <td>PLIST_VARS</td>
1.336 nia 13312: <td>POPTOP_USE_MPPE</td>
1.269 leot 13313: </tr>
13314: <tr>
1.335 nia 13315: <td>POSSIBLE_GFORTRAN_VERSION</td>
1.336 nia 13316: <td>POST_FETCH_HOOK</td>
1.269 leot 13317: </tr>
13318: <tr>
1.335 nia 13319: <td>PREFER</td>
1.336 nia 13320: <td>PREFER_NATIVE</td>
1.269 leot 13321: </tr>
13322: <tr>
1.335 nia 13323: <td>PREFER_NATIVE_PTHREADS</td>
1.336 nia 13324: <td>PREFER_PKGSRC</td>
1.269 leot 13325: </tr>
13326: <tr>
1.335 nia 13327: <td>PREFIX</td>
1.336 nia 13328: <td>PREPEND_PATH</td>
1.269 leot 13329: </tr>
13330: <tr>
1.335 nia 13331: <td>PRE_ROOT_CMD</td>
1.336 nia 13332: <td>PRIVILEGED_STAGES</td>
1.269 leot 13333: </tr>
13334: <tr>
1.335 nia 13335: <td>PS</td>
1.336 nia 13336: <td>PTHREAD_AUTO_VARS</td>
1.269 leot 13337: </tr>
13338: <tr>
1.335 nia 13339: <td>PTHREAD_CFLAGS</td>
1.336 nia 13340: <td>PTHREAD_LDFLAGS</td>
1.269 leot 13341: </tr>
13342: <tr>
1.335 nia 13343: <td>PTHREAD_LIBS</td>
1.336 nia 13344: <td>PTHREAD_OPTS</td>
1.269 leot 13345: </tr>
13346: <tr>
1.335 nia 13347: <td>PTHREAD_TYPE</td>
1.336 nia 13348: <td>PVM_SSH</td>
1.269 leot 13349: </tr>
13350: <tr>
1.335 nia 13351: <td>PYPKGPREFIX</td>
1.336 nia 13352: <td>PYTHON_FOR_BUILD_ONLY</td>
1.269 leot 13353: </tr>
13354: <tr>
1.335 nia 13355: <td>PYTHON_SELF_CONFLICT</td>
1.336 nia 13356: <td>PYTHON_VERSIONED_DEPENDENCIES</td>
1.269 leot 13357: </tr>
13358: <tr>
1.335 nia 13359: <td>PYTHON_VERSIONS_ACCEPTED</td>
1.336 nia 13360: <td>PYTHON_VERSIONS_INCOMPATIBLE</td>
1.269 leot 13361: </tr>
13362: <tr>
1.335 nia 13363: <td>PYTHON_VERSION_DEFAULT</td>
1.336 nia 13364: <td>PYTHON_VERSION_REQD</td>
1.269 leot 13365: </tr>
13366: <tr>
1.335 nia 13367: <td>PYVERSSUFFIX</td>
1.336 nia 13368: <td>QMAILDIR</td>
1.269 leot 13369: </tr>
13370: <tr>
1.335 nia 13371: <td>QMAIL_ALIAS_USER</td>
1.336 nia 13372: <td>QMAIL_DAEMON_USER</td>
1.269 leot 13373: </tr>
13374: <tr>
1.335 nia 13375: <td>QMAIL_LOG_USER</td>
1.336 nia 13376: <td>QMAIL_NOFILES_GROUP</td>
1.269 leot 13377: </tr>
13378: <tr>
1.335 nia 13379: <td>QMAIL_PASSWD_USER</td>
1.336 nia 13380: <td>QMAIL_QMAIL_GROUP</td>
1.269 leot 13381: </tr>
13382: <tr>
1.335 nia 13383: <td>QMAIL_QUEUE_DIR</td>
1.336 nia 13384: <td>QMAIL_QUEUE_EXTRA</td>
1.269 leot 13385: </tr>
13386: <tr>
1.335 nia 13387: <td>QMAIL_QUEUE_USER</td>
1.336 nia 13388: <td>QMAIL_REMOTE_USER</td>
1.269 leot 13389: </tr>
13390: <tr>
1.335 nia 13391: <td>QMAIL_ROOT_USER</td>
1.336 nia 13392: <td>QMAIL_SEND_USER</td>
1.269 leot 13393: </tr>
13394: <tr>
1.335 nia 13395: <td>QORE_LATEST_MODULE_API</td>
1.336 nia 13396: <td>QORE_MODULE_API</td>
1.269 leot 13397: </tr>
13398: <tr>
1.335 nia 13399: <td>QORE_MODULE_DIR</td>
1.336 nia 13400: <td>QORE_USER_MODULE_DIR</td>
1.333 nia 13401: </tr>
13402: <tr>
1.335 nia 13403: <td>QORE_VERSION</td>
1.336 nia 13404: <td>QPOPPER_FAC</td>
1.333 nia 13405: </tr>
13406: <tr>
1.335 nia 13407: <td>QPOPPER_SPOOL_DIR</td>
1.336 nia 13408: <td>QPOPPER_USER</td>
1.333 nia 13409: </tr>
13410: <tr>
1.335 nia 13411: <td>RAKE_NAME</td>
1.336 nia 13412: <td>RASMOL_DEPTH</td>
1.269 leot 13413: </tr>
13414: <tr>
1.335 nia 13415: <td>RCD_SCRIPTS</td>
1.336 nia 13416: <td>RCD_SCRIPTS_DIR</td>
1.329 leot 13417: </tr>
13418: <tr>
1.335 nia 13419: <td>RCD_SCRIPTS_EXAMPLEDIR</td>
1.336 nia 13420: <td>RCD_SCRIPTS_MODE</td>
1.332 rillig 13421: </tr>
13422: <tr>
1.335 nia 13423: <td>RCD_SCRIPTS_SHELL</td>
1.336 nia 13424: <td>RCD_SCRIPT_SRC</td>
1.320 wiz 13425: </tr>
13426: <tr>
1.336 nia 13427: <td>RDOC</td>
1.340 ! gutterid 13428: <td>READLINE_DEFAULT</td>
1.338 nia 13429: </tr>
13430: <tr>
13431: <td>READLINE_TYPE</td>
1.340 ! gutterid 13432: <td>REAL_ROOT_GROUP</td>
1.292 leot 13433: </tr>
13434: <tr>
1.338 nia 13435: <td>REAL_ROOT_USER</td>
1.340 ! gutterid 13436: <td>RECURSIVE_MAKE</td>
1.329 leot 13437: </tr>
13438: <tr>
1.338 nia 13439: <td>RELAY_CTRL_DIR</td>
1.340 ! gutterid 13440: <td>RELRO_SUPPORTED</td>
1.327 wiz 13441: </tr>
13442: <tr>
1.338 nia 13443: <td>REPLACE_AWK</td>
1.340 ! gutterid 13444: <td>REPLACE_BASH</td>
1.269 leot 13445: </tr>
13446: <tr>
1.338 nia 13447: <td>REPLACE_CSH</td>
1.340 ! gutterid 13448: <td>REPLACE_KSH</td>
1.320 wiz 13449: </tr>
13450: <tr>
1.338 nia 13451: <td>REPLACE_LUA</td>
1.340 ! gutterid 13452: <td>REPLACE_NODEJS</td>
1.311 leot 13453: </tr>
13454: <tr>
1.338 nia 13455: <td>REPLACE_OCTAVE</td>
1.340 ! gutterid 13456: <td>REPLACE_PERL</td>
1.269 leot 13457: </tr>
13458: <tr>
1.338 nia 13459: <td>REPLACE_PERL6</td>
1.340 ! gutterid 13460: <td>REPLACE_PHP</td>
1.333 nia 13461: </tr>
13462: <tr>
1.338 nia 13463: <td>REPLACE_PYTHON</td>
1.340 ! gutterid 13464: <td>REPLACE_QORE</td>
1.269 leot 13465: </tr>
13466: <tr>
1.338 nia 13467: <td>REPLACE_R</td>
1.340 ! gutterid 13468: <td>REPLACE_RUBY</td>
1.331 gutterid 13469: </tr>
13470: <tr>
1.338 nia 13471: <td>REPLACE_RUBY_DIRS</td>
1.340 ! gutterid 13472: <td>REPLACE_RUBY_PAT</td>
1.269 leot 13473: </tr>
13474: <tr>
1.338 nia 13475: <td>REPLACE_SH</td>
1.340 ! gutterid 13476: <td>REPLACE_TEXLUA</td>
1.333 nia 13477: </tr>
13478: <tr>
1.338 nia 13479: <td>REPLACE_WISH</td>
1.340 ! gutterid 13480: <td>REQD_DIRS</td>
1.269 leot 13481: </tr>
13482: <tr>
1.338 nia 13483: <td>REQD_DIRS_PERMS</td>
1.340 ! gutterid 13484: <td>REQD_FILES</td>
1.269 leot 13485: </tr>
13486: <tr>
1.338 nia 13487: <td>REQD_FILES_MODE</td>
1.340 ! gutterid 13488: <td>REQD_FILES_PERMS</td>
1.269 leot 13489: </tr>
13490: <tr>
1.338 nia 13491: <td>RESOLV_AUTO_VARS</td>
1.340 ! gutterid 13492: <td>RESOLV_LDFLAGS</td>
1.269 leot 13493: </tr>
13494: <tr>
1.338 nia 13495: <td>RESOLV_LIBS</td>
1.335 nia 13496: <td>RM</td>
1.269 leot 13497: </tr>
13498: <tr>
1.336 nia 13499: <td>ROOT_CMD</td>
1.340 ! gutterid 13500: <td>ROOT_GROUP</td>
1.320 wiz 13501: </tr>
13502: <tr>
1.336 nia 13503: <td>ROOT_USER</td>
1.340 ! gutterid 13504: <td>RPCGEN</td>
1.332 rillig 13505: </tr>
13506: <tr>
1.336 nia 13507: <td>RPM</td>
1.340 ! gutterid 13508: <td>RPM2PKG_PLIST</td>
1.329 leot 13509: </tr>
13510: <tr>
1.336 nia 13511: <td>RPM2PKG_PREFIX</td>
1.340 ! gutterid 13512: <td>RPM2PKG_STAGE</td>
1.327 wiz 13513: </tr>
13514: <tr>
1.336 nia 13515: <td>RPM2PKG_STRIP</td>
1.340 ! gutterid 13516: <td>RPM2PKG_SUBPREFIX</td>
1.269 leot 13517: </tr>
13518: <tr>
1.336 nia 13519: <td>RPMFILES</td>
1.340 ! gutterid 13520: <td>RPMIGNOREPATH</td>
1.311 leot 13521: </tr>
13522: <tr>
1.336 nia 13523: <td>RPM_DB_PREFIX</td>
1.340 ! gutterid 13524: <td>RSSH_CVS_PATH</td>
1.269 leot 13525: </tr>
13526: <tr>
1.336 nia 13527: <td>RSSH_RDIST_PATH</td>
1.340 ! gutterid 13528: <td>RSSH_RSYNC_PATH</td>
1.269 leot 13529: </tr>
13530: <tr>
1.336 nia 13531: <td>RSSH_SCP_PATH</td>
1.340 ! gutterid 13532: <td>RSSH_SFTP_SERVER_PATH</td>
1.269 leot 13533: </tr>
13534: <tr>
1.336 nia 13535: <td>RUBY</td>
1.340 ! gutterid 13536: <td>RUBYGEM</td>
1.269 leot 13537: </tr>
13538: <tr>
1.336 nia 13539: <td>RUBYGEM_NAME</td>
1.340 ! gutterid 13540: <td>RUBYGEM_OPTIONS</td>
1.269 leot 13541: </tr>
13542: <tr>
1.336 nia 13543: <td>RUBYGEM_VERBOSE</td>
1.340 ! gutterid 13544: <td>RUBY_ABI_VERSION</td>
1.269 leot 13545: </tr>
13546: <tr>
1.336 nia 13547: <td>RUBY_ARCH</td>
1.340 ! gutterid 13548: <td>RUBY_ARCHINC</td>
1.269 leot 13549: </tr>
13550: <tr>
1.336 nia 13551: <td>RUBY_ARCHLIB</td>
1.340 ! gutterid 13552: <td>RUBY_BASE</td>
1.269 leot 13553: </tr>
13554: <tr>
1.336 nia 13555: <td>RUBY_BASERIDIR</td>
1.340 ! gutterid 13556: <td>RUBY_BUILD_DOCUMENT</td>
1.269 leot 13557: </tr>
13558: <tr>
1.336 nia 13559: <td>RUBY_DLEXT</td>
1.340 ! gutterid 13560: <td>RUBY_DOC</td>
1.269 leot 13561: </tr>
13562: <tr>
1.336 nia 13563: <td>RUBY_DYNAMIC_DIRS</td>
1.340 ! gutterid 13564: <td>RUBY_EG</td>
1.269 leot 13565: </tr>
13566: <tr>
1.336 nia 13567: <td>RUBY_ENCODING_ARG</td>
1.340 ! gutterid 13568: <td>RUBY_EXTCONF</td>
1.269 leot 13569: </tr>
13570: <tr>
1.336 nia 13571: <td>RUBY_EXTCONF_CHECK</td>
1.340 ! gutterid 13572: <td>RUBY_EXTCONF_DEBUG</td>
1.269 leot 13573: </tr>
13574: <tr>
1.336 nia 13575: <td>RUBY_EXTCONF_MAKEFILE</td>
1.340 ! gutterid 13576: <td>RUBY_GEM_ARCH</td>
1.269 leot 13577: </tr>
13578: <tr>
1.336 nia 13579: <td>RUBY_GEM_BASE</td>
1.340 ! gutterid 13580: <td>RUBY_INC</td>
1.269 leot 13581: </tr>
13582: <tr>
1.336 nia 13583: <td>RUBY_LIB</td>
1.340 ! gutterid 13584: <td>RUBY_LIB_BASE</td>
1.338 nia 13585: </tr>
13586: <tr>
13587: <td>RUBY_NAME</td>
1.340 ! gutterid 13588: <td>RUBY_NOVERSION</td>
1.269 leot 13589: </tr>
13590: <tr>
1.338 nia 13591: <td>RUBY_PKGPREFIX</td>
1.340 ! gutterid 13592: <td>RUBY_RAILS</td>
1.269 leot 13593: </tr>
13594: <tr>
1.338 nia 13595: <td>RUBY_RAILS52_VERSION</td>
1.340 ! gutterid 13596: <td>RUBY_RAILS60_VERSION</td>
1.269 leot 13597: </tr>
13598: <tr>
1.338 nia 13599: <td>RUBY_RAILS61_VERSION</td>
1.340 ! gutterid 13600: <td>RUBY_RAILS70_VERSION</td>
1.269 leot 13601: </tr>
13602: <tr>
1.338 nia 13603: <td>RUBY_RAILS_ACCEPTED</td>
1.340 ! gutterid 13604: <td>RUBY_RAILS_DEFAULT</td>
1.269 leot 13605: </tr>
13606: <tr>
1.338 nia 13607: <td>RUBY_RAILS_REQD</td>
1.340 ! gutterid 13608: <td>RUBY_RAILS_STRICT_DEP</td>
1.269 leot 13609: </tr>
13610: <tr>
1.338 nia 13611: <td>RUBY_RIDIR</td>
1.340 ! gutterid 13612: <td>RUBY_SETUP</td>
1.269 leot 13613: </tr>
13614: <tr>
1.338 nia 13615: <td>RUBY_SHLIB</td>
1.340 ! gutterid 13616: <td>RUBY_SHLIBALIAS</td>
1.269 leot 13617: </tr>
13618: <tr>
1.338 nia 13619: <td>RUBY_SHLIBVER</td>
1.340 ! gutterid 13620: <td>RUBY_SIMPLE_INSTALL</td>
1.312 gdt 13621: </tr>
13622: <tr>
1.338 nia 13623: <td>RUBY_SITEARCHLIB</td>
1.340 ! gutterid 13624: <td>RUBY_SITELIB</td>
1.289 leot 13625: </tr>
13626: <tr>
1.338 nia 13627: <td>RUBY_SITELIB_BASE</td>
1.340 ! gutterid 13628: <td>RUBY_SITERIDIR</td>
1.269 leot 13629: </tr>
13630: <tr>
1.338 nia 13631: <td>RUBY_SLEXT</td>
1.340 ! gutterid 13632: <td>RUBY_SRCDIR</td>
1.269 leot 13633: </tr>
13634: <tr>
1.338 nia 13635: <td>RUBY_STATICLIB</td>
1.340 ! gutterid 13636: <td>RUBY_SUFFIX</td>
1.269 leot 13637: </tr>
13638: <tr>
1.338 nia 13639: <td>RUBY_SYSRIDIR</td>
1.340 ! gutterid 13640: <td>RUBY_USE_PTHREAD</td>
1.269 leot 13641: </tr>
13642: <tr>
1.338 nia 13643: <td>RUBY_VENDORARCHLIB</td>
1.340 ! gutterid 13644: <td>RUBY_VENDORLIB</td>
1.269 leot 13645: </tr>
13646: <tr>
1.338 nia 13647: <td>RUBY_VENDORLIB_BASE</td>
1.340 ! gutterid 13648: <td>RUBY_VER</td>
1.269 leot 13649: </tr>
13650: <tr>
1.338 nia 13651: <td>RUBY_VERSION</td>
1.340 ! gutterid 13652: <td>RUBY_VERSIONS_ACCEPTED</td>
1.269 leot 13653: </tr>
13654: <tr>
1.338 nia 13655: <td>RUBY_VERSIONS_INCOMPATIBLE</td>
1.340 ! gutterid 13656: <td>RUBY_VERSION_DEFAULT</td>
1.269 leot 13657: </tr>
13658: <tr>
1.338 nia 13659: <td>RUBY_VERSION_REQD</td>
1.340 ! gutterid 13660: <td>RUBY_VER_DIR</td>
1.269 leot 13661: </tr>
13662: <tr>
1.338 nia 13663: <td>RUN</td>
1.340 ! gutterid 13664: <td>RUN_LDCONFIG</td>
1.269 leot 13665: </tr>
13666: <tr>
1.338 nia 13667: <td>RUST_TYPE</td>
1.340 ! gutterid 13668: <td>SCO</td>
1.269 leot 13669: </tr>
13670: <tr>
1.338 nia 13671: <td>SCREWS_GROUP</td>
1.340 ! gutterid 13672: <td>SCREWS_USER</td>
1.269 leot 13673: </tr>
13674: <tr>
1.338 nia 13675: <td>SCRIPTS_ENV</td>
1.340 ! gutterid 13676: <td>SCROLLKEEPER_DATADIR</td>
1.269 leot 13677: </tr>
13678: <tr>
1.338 nia 13679: <td>SCROLLKEEPER_REBUILDDB</td>
1.340 ! gutterid 13680: <td>SCROLLKEEPER_UPDATEDB</td>
1.269 leot 13681: </tr>
13682: <tr>
1.338 nia 13683: <td>SDIST_PAWD</td>
1.340 ! gutterid 13684: <td>SDL12_TYPE</td>
1.269 leot 13685: </tr>
13686: <tr>
1.338 nia 13687: <td>SERIAL_DEVICES</td>
1.340 ! gutterid 13688: <td>SETGIDGAME</td>
1.336 nia 13689: </tr>
13690: <tr>
1.338 nia 13691: <td>SETGID_GAMES_PERMS</td>
1.340 ! gutterid 13692: <td>SETUID_ROOT_PERMS</td>
1.269 leot 13693: </tr>
13694: <tr>
1.338 nia 13695: <td>SH</td>
1.335 nia 13696: <td>SHLIB</td>
1.269 leot 13697: </tr>
13698: <tr>
1.335 nia 13699: <td>SIGN_PACKAGES</td>
1.336 nia 13700: <td>SILC_CLIENT_WITH_PERL</td>
1.269 leot 13701: </tr>
13702: <tr>
1.335 nia 13703: <td>SITE_SPECIFIC_PKGS</td>
1.336 nia 13704: <td>SKIP_DEPENDS</td>
1.292 leot 13705: </tr>
13706: <tr>
1.335 nia 13707: <td>SMF_INSTANCES</td>
1.336 nia 13708: <td>SMF_MANIFEST</td>
1.269 leot 13709: </tr>
13710: <tr>
1.335 nia 13711: <td>SMF_METHODS</td>
1.336 nia 13712: <td>SMF_METHOD_SHELL</td>
1.332 rillig 13713: </tr>
13714: <tr>
1.335 nia 13715: <td>SMF_METHOD_SRC</td>
1.336 nia 13716: <td>SMF_NAME</td>
1.269 leot 13717: </tr>
13718: <tr>
1.335 nia 13719: <td>SMF_PREFIX</td>
1.336 nia 13720: <td>SMF_SRCDIR</td>
1.274 rillig 13721: </tr>
13722: <tr>
1.335 nia 13723: <td>SNIPROXY_GROUP</td>
1.336 nia 13724: <td>SNIPROXY_USER</td>
1.269 leot 13725: </tr>
13726: <tr>
1.335 nia 13727: <td>SOURCE_BUFFSIZE</td>
1.336 nia 13728: <td>SPECIAL_PERMS</td>
1.269 leot 13729: </tr>
13730: <tr>
1.335 nia 13731: <td>SPECIFIC_PKGS</td>
1.336 nia 13732: <td>SSH_SUID</td>
1.269 leot 13733: </tr>
13734: <tr>
1.335 nia 13735: <td>SSP_SUPPORTED</td>
1.336 nia 13736: <td>SSYNC_PAWD</td>
1.269 leot 13737: </tr>
13738: <tr>
1.335 nia 13739: <td>STEP_MSG</td>
1.336 nia 13740: <td>STRIP</td>
1.269 leot 13741: </tr>
13742: <tr>
1.335 nia 13743: <td>STRIP_DBG</td>
1.336 nia 13744: <td>STRIP_DEBUG</td>
1.269 leot 13745: </tr>
13746: <tr>
1.335 nia 13747: <td>STRIP_DEBUG_SUPPORTED</td>
1.336 nia 13748: <td>STRIP_FILES_SKIP</td>
1.269 leot 13749: </tr>
13750: <tr>
1.335 nia 13751: <td>SU</td>
1.336 nia 13752: <td>SUBDIR</td>
1.269 leot 13753: </tr>
13754: <tr>
1.335 nia 13755: <td>SUBST</td>
1.336 nia 13756: <td>SUBST_CLASSES</td>
1.269 leot 13757: </tr>
13758: <tr>
1.335 nia 13759: <td>SUBST_FILES</td>
1.336 nia 13760: <td>SUBST_FILTER_CMD</td>
1.269 leot 13761: </tr>
13762: <tr>
1.335 nia 13763: <td>SUBST_MESSAGE</td>
1.336 nia 13764: <td>SUBST_NOOP_OK</td>
1.269 leot 13765: </tr>
13766: <tr>
1.335 nia 13767: <td>SUBST_SED</td>
1.336 nia 13768: <td>SUBST_SHOW_DIFF</td>
1.289 leot 13769: </tr>
13770: <tr>
1.335 nia 13771: <td>SUBST_SKIP_TEXT_CHECK</td>
1.336 nia 13772: <td>SUBST_STAGE</td>
1.269 leot 13773: </tr>
13774: <tr>
1.335 nia 13775: <td>SUBST_VARS</td>
1.336 nia 13776: <td>SUNWSPROBASE</td>
1.269 leot 13777: </tr>
13778: <tr>
1.335 nia 13779: <td>SUSE_PREFER</td>
1.336 nia 13780: <td>SU_CMD</td>
1.269 leot 13781: </tr>
13782: <tr>
1.337 gutterid 13783: <td>SYSCONFBASE</td>
13784: <td>TARGET_ARCH</td>
1.332 rillig 13785: </tr>
13786: <tr>
1.336 nia 13787: <td>TBL</td>
1.337 gutterid 13788: <td>TERMCAP_TYPE</td>
1.327 wiz 13789: </tr>
13790: <tr>
1.336 nia 13791: <td>TERMINFO_DEFAULT</td>
1.337 gutterid 13792: <td>TERMINFO_TYPE</td>
1.332 rillig 13793: </tr>
13794: <tr>
1.336 nia 13795: <td>TEST</td>
1.337 gutterid 13796: <td>TEST_DEPENDS</td>
1.320 wiz 13797: </tr>
13798: <tr>
1.336 nia 13799: <td>TEST_DIRS</td>
1.337 gutterid 13800: <td>TEST_ENV</td>
1.303 bacon 13801: </tr>
13802: <tr>
1.336 nia 13803: <td>TEST_ENV_SHELL</td>
1.337 gutterid 13804: <td>TEST_MAKE_CMD</td>
1.274 rillig 13805: </tr>
13806: <tr>
1.336 nia 13807: <td>TEST_MAKE_FLAGS</td>
1.337 gutterid 13808: <td>TEST_TARGET</td>
1.269 leot 13809: </tr>
13810: <tr>
1.336 nia 13811: <td>TEXLIVE_IGNORE_PATTERNS</td>
1.337 gutterid 13812: <td>TEXLIVE_REV</td>
1.269 leot 13813: </tr>
13814: <tr>
1.336 nia 13815: <td>TEXLIVE_UNVERSIONED</td>
1.337 gutterid 13816: <td>TEXMFSITE</td>
1.269 leot 13817: </tr>
13818: <tr>
1.336 nia 13819: <td>TEX_FORMATS</td>
1.337 gutterid 13820: <td>TEX_HYPHEN_DAT</td>
1.269 leot 13821: </tr>
13822: <tr>
1.336 nia 13823: <td>TEX_HYPHEN_DEF</td>
1.337 gutterid 13824: <td>TEX_TEXMF_DIRS</td>
1.269 leot 13825: </tr>
13826: <tr>
1.336 nia 13827: <td>THTTPD_LOG_FACILITY</td>
1.337 gutterid 13828: <td>TINYDYN_USER</td>
1.269 leot 13829: </tr>
13830: <tr>
1.336 nia 13831: <td>TLSWRAPPER_CHROOT</td>
1.337 gutterid 13832: <td>TO</td>
1.269 leot 13833: </tr>
13834: <tr>
1.336 nia 13835: <td>TOOLS_ALIASES</td>
1.337 gutterid 13836: <td>TOOLS_ALWAYS_WRAP</td>
1.269 leot 13837: </tr>
13838: <tr>
1.336 nia 13839: <td>TOOLS_ARGS</td>
1.337 gutterid 13840: <td>TOOLS_BROKEN</td>
1.269 leot 13841: </tr>
13842: <tr>
1.336 nia 13843: <td>TOOLS_CMD</td>
1.337 gutterid 13844: <td>TOOLS_CMDLINE_SED</td>
1.269 leot 13845: </tr>
13846: <tr>
1.336 nia 13847: <td>TOOLS_CREATE</td>
1.337 gutterid 13848: <td>TOOLS_CROSS_DESTDIR</td>
1.269 leot 13849: </tr>
13850: <tr>
1.335 nia 13851: <td>TOOLS_DIR</td>
1.336 nia 13852: <td>TOOLS_FAIL</td>
1.269 leot 13853: </tr>
13854: <tr>
1.335 nia 13855: <td>TOOLS_GNU_MISSING</td>
1.336 nia 13856: <td>TOOLS_LDCONFIG</td>
1.269 leot 13857: </tr>
13858: <tr>
1.335 nia 13859: <td>TOOLS_NOOP</td>
1.336 nia 13860: <td>TOOLS_PATH</td>
1.269 leot 13861: </tr>
13862: <tr>
1.335 nia 13863: <td>TOOLS_SCRIPT</td>
1.337 gutterid 13864: <td>TOOLS_USE_CROSS_COMPILE</td>
1.269 leot 13865: </tr>
13866: <tr>
1.337 gutterid 13867: <td>TOOL_DEPENDS</td>
1.340 ! gutterid 13868: <td>TTF_FONTS_DIR</td>
1.338 nia 13869: </tr>
13870: <tr>
13871: <td>TYPE</td>
1.340 ! gutterid 13872: <td>UAC_REQD_EXECS</td>
1.269 leot 13873: </tr>
13874: <tr>
1.338 nia 13875: <td>UCSPI_SSL_GROUP</td>
1.340 ! gutterid 13876: <td>UCSPI_SSL_USER</td>
1.329 leot 13877: </tr>
13878: <tr>
1.338 nia 13879: <td>UNLIMIT_RESOURCES</td>
1.340 ! gutterid 13880: <td>UNPRIVILEGED</td>
1.327 wiz 13881: </tr>
13882: <tr>
1.338 nia 13883: <td>UNPRIVILEGED_GROUP</td>
1.340 ! gutterid 13884: <td>UNPRIVILEGED_GROUPS</td>
1.269 leot 13885: </tr>
13886: <tr>
1.338 nia 13887: <td>UNPRIVILEGED_USER</td>
1.340 ! gutterid 13888: <td>UNWRAP_FILES</td>
1.269 leot 13889: </tr>
13890: <tr>
1.338 nia 13891: <td>UNWRAP_PATTERNS</td>
1.340 ! gutterid 13892: <td>UPDATE_GEMSPEC</td>
1.269 leot 13893: </tr>
13894: <tr>
1.338 nia 13895: <td>UPDATE_TARGET</td>
1.340 ! gutterid 13896: <td>URI</td>
1.269 leot 13897: </tr>
13898: <tr>
1.338 nia 13899: <td>USERGROUP_PHASE</td>
1.340 ! gutterid 13900: <td>USERPPP_GROUP</td>
1.269 leot 13901: </tr>
13902: <tr>
1.338 nia 13903: <td>USER_SPECIFIC_PKGS</td>
1.340 ! gutterid 13904: <td>USE_ABI_DEPENDS</td>
1.269 leot 13905: </tr>
13906: <tr>
1.338 nia 13907: <td>USE_APR</td>
1.340 ! gutterid 13908: <td>USE_BSD_MAKEFILE</td>
1.269 leot 13909: </tr>
13910: <tr>
1.338 nia 13911: <td>USE_BUILTIN</td>
1.340 ! gutterid 13912: <td>USE_CROSS_COMPILE</td>
1.269 leot 13913: </tr>
13914: <tr>
1.338 nia 13915: <td>USE_CURSES</td>
1.340 ! gutterid 13916: <td>USE_CWRAPPERS</td>
1.269 leot 13917: </tr>
13918: <tr>
1.338 nia 13919: <td>USE_DB185</td>
1.340 ! gutterid 13920: <td>USE_FEATURES</td>
1.320 wiz 13921: </tr>
13922: <tr>
1.338 nia 13923: <td>USE_GAMESGROUP</td>
1.340 ! gutterid 13924: <td>USE_GCC_RUNTIME</td>
1.269 leot 13925: </tr>
13926: <tr>
1.338 nia 13927: <td>USE_IMAKE</td>
1.340 ! gutterid 13928: <td>USE_JAVA</td>
1.269 leot 13929: </tr>
13930: <tr>
1.338 nia 13931: <td>USE_JAVA2</td>
1.340 ! gutterid 13932: <td>USE_LANGUAGES</td>
1.269 leot 13933: </tr>
13934: <tr>
1.338 nia 13935: <td>USE_LIBTOOL</td>
1.340 ! gutterid 13936: <td>USE_NATIVE_GCC</td>
1.269 leot 13937: </tr>
13938: <tr>
1.338 nia 13939: <td>USE_NETBSD_REPO</td>
1.340 ! gutterid 13940: <td>USE_PKGSRC_GCC</td>
1.269 leot 13941: </tr>
13942: <tr>
1.338 nia 13943: <td>USE_PKGSRC_GCC_RUNTIME</td>
1.340 ! gutterid 13944: <td>USE_PKGTASKS</td>
1.269 leot 13945: </tr>
13946: <tr>
1.338 nia 13947: <td>USE_PKG_ADMIN_DIGEST</td>
1.340 ! gutterid 13948: <td>USE_RUBY_EXTCONF</td>
1.269 leot 13949: </tr>
13950: <tr>
1.338 nia 13951: <td>USE_RUBY_INSTALL</td>
1.340 ! gutterid 13952: <td>USE_RUBY_SETUP</td>
1.269 leot 13953: </tr>
13954: <tr>
1.338 nia 13955: <td>USE_RUBY_SETUP_PKG</td>
1.340 ! gutterid 13956: <td>USE_TOOLS</td>
1.269 leot 13957: </tr>
13958: <tr>
1.338 nia 13959: <td>UUCP_GROUP</td>
1.340 ! gutterid 13960: <td>UUCP_USER</td>
1.269 leot 13961: </tr>
13962: <tr>
1.338 nia 13963: <td>VARBASE</td>
1.340 ! gutterid 13964: <td>VARNAME</td>
1.269 leot 13965: </tr>
13966: <tr>
1.338 nia 13967: <td>VIM_EXTRA_OPTS</td>
1.340 ! gutterid 13968: <td>WARNING_MSG</td>
1.269 leot 13969: </tr>
13970: <tr>
1.338 nia 13971: <td>WCALC_CGIDIR</td>
1.340 ! gutterid 13972: <td>WCALC_CGIPATH</td>
1.269 leot 13973: </tr>
13974: <tr>
1.338 nia 13975: <td>WCALC_HTMLDIR</td>
1.340 ! gutterid 13976: <td>WCALC_HTMLPATH</td>
1.269 leot 13977: </tr>
13978: <tr>
1.338 nia 13979: <td>WDM_MANAGERS</td>
1.340 ! gutterid 13980: <td>WRAPPER_CC</td>
1.269 leot 13981: </tr>
13982: <tr>
1.338 nia 13983: <td>WRAPPER_REORDER_CMDS</td>
1.340 ! gutterid 13984: <td>WRKDIR</td>
1.269 leot 13985: </tr>
13986: <tr>
1.338 nia 13987: <td>WRKDIR_BASENAME</td>
1.340 ! gutterid 13988: <td>WRKDIR_LOCKTYPE</td>
1.269 leot 13989: </tr>
13990: <tr>
1.338 nia 13991: <td>WRKLOG</td>
1.340 ! gutterid 13992: <td>WRKOBJDIR</td>
1.269 leot 13993: </tr>
13994: <tr>
1.338 nia 13995: <td>WRKSRC</td>
1.340 ! gutterid 13996: <td>X10_PORT</td>
1.269 leot 13997: </tr>
13998: <tr>
1.338 nia 13999: <td>X11</td>
1.340 ! gutterid 14000: <td>X11BASE</td>
1.303 bacon 14001: </tr>
14002: <tr>
1.338 nia 14003: <td>X11_PKGSRCDIR</td>
1.340 ! gutterid 14004: <td>X11_TYPE</td>
1.269 leot 14005: </tr>
14006: <tr>
1.338 nia 14007: <td>X509_CERTIFICATE</td>
1.340 ! gutterid 14008: <td>X509_KEY</td>
1.269 leot 14009: </tr>
14010: <tr>
1.338 nia 14011: <td>XAW_TYPE</td>
1.340 ! gutterid 14012: <td>XLOCK_DEFAULT_MODE</td>
1.269 leot 14013: </tr>
14014: <tr>
1.338 nia 14015: <td>XMKMF</td>
1.340 ! gutterid 14016: <td>XMKMF_FLAGS</td>
1.269 leot 14017: </tr>
14018: <tr>
1.338 nia 14019: <td>XXX</td>
1.337 gutterid 14020: <td>YES</td>
1.269 leot 14021: </tr>
14022: <tr>
1.336 nia 14023: <td>ZSH_STATIC</td>
1.337 gutterid 14024: <td>__stdc__</td>
1.274 rillig 14025: </tr>
14026: <tr>
1.336 nia 14027: <td>_vargroups</td>
1.337 gutterid 14028: <td>accept</td>
1.332 rillig 14029: </tr>
14030: <tr>
1.336 nia 14031: <td>acquire-localbase-lock</td>
1.337 gutterid 14032: <td>acquire-lock</td>
1.269 leot 14033: </tr>
14034: <tr>
1.336 nia 14035: <td>add</td>
1.337 gutterid 14036: <td>administrator</td>
1.316 cirnatda 14037: </tr>
14038: <tr>
1.336 nia 14039: <td>alloca</td>
1.337 gutterid 14040: <td>alternatives</td>
1.289 leot 14041: </tr>
14042: <tr>
1.336 nia 14043: <td>aslr</td>
1.337 gutterid 14044: <td>asprintf</td>
1.269 leot 14045: </tr>
14046: <tr>
1.336 nia 14047: <td>atlas</td>
1.337 gutterid 14048: <td>autoconf</td>
1.269 leot 14049: </tr>
14050: <tr>
1.336 nia 14051: <td>automake</td>
1.337 gutterid 14052: <td>autoreconf</td>
1.289 leot 14053: </tr>
14054: <tr>
1.336 nia 14055: <td>awk</td>
1.337 gutterid 14056: <td>bash</td>
1.269 leot 14057: </tr>
14058: <tr>
1.336 nia 14059: <td>big-endian</td>
1.337 gutterid 14060: <td>bin-install</td>
1.269 leot 14061: </tr>
14062: <tr>
1.336 nia 14063: <td>bind</td>
1.337 gutterid 14064: <td>binpkg-list</td>
1.269 leot 14065: </tr>
14066: <tr>
1.336 nia 14067: <td>blas</td>
1.337 gutterid 14068: <td>bootstrap-depends</td>
1.271 brook 14069: </tr>
14070: <tr>
1.336 nia 14071: <td>broken</td>
1.337 gutterid 14072: <td>broken_on_platform</td>
1.269 leot 14073: </tr>
14074: <tr>
1.336 nia 14075: <td>bsd</td>
1.337 gutterid 14076: <td>bsd.prog.mk</td>
1.292 leot 14077: </tr>
14078: <tr>
1.336 nia 14079: <td>build</td>
1.337 gutterid 14080: <td>build-env</td>
1.274 rillig 14081: </tr>
14082: <tr>
1.336 nia 14083: <td>buildlink-directories</td>
1.337 gutterid 14084: <td>buildlink-oss-soundcard-h</td>
1.269 leot 14085: </tr>
14086: <tr>
1.336 nia 14087: <td>c</td>
1.337 gutterid 14088: <td>c++</td>
1.289 leot 14089: </tr>
14090: <tr>
1.336 nia 14091: <td>ccache</td>
1.337 gutterid 14092: <td>cce</td>
1.269 leot 14093: </tr>
14094: <tr>
1.336 nia 14095: <td>cdefs</td>
1.337 gutterid 14096: <td>ceil</td>
1.269 leot 14097: </tr>
14098: <tr>
1.336 nia 14099: <td>changes</td>
1.337 gutterid 14100: <td>changes-entry</td>
1.269 leot 14101: </tr>
14102: <tr>
1.336 nia 14103: <td>changes-entry-noupdate</td>
1.337 gutterid 14104: <td>check</td>
1.269 leot 14105: </tr>
14106: <tr>
1.336 nia 14107: <td>check-clean</td>
1.337 gutterid 14108: <td>check-files</td>
1.289 leot 14109: </tr>
14110: <tr>
1.336 nia 14111: <td>check-files-clean</td>
1.337 gutterid 14112: <td>check-vulnerable</td>
1.269 leot 14113: </tr>
14114: <tr>
1.336 nia 14115: <td>checksum</td>
1.337 gutterid 14116: <td>checksum-phase</td>
1.269 leot 14117: </tr>
14118: <tr>
1.336 nia 14119: <td>clean</td>
1.337 gutterid 14120: <td>clean-depends</td>
1.269 leot 14121: </tr>
14122: <tr>
1.336 nia 14123: <td>cleandir</td>
1.337 gutterid 14124: <td>commit</td>
1.269 leot 14125: </tr>
14126: <tr>
1.336 nia 14127: <td>commit-changes-entry</td>
1.337 gutterid 14128: <td>compact</td>
1.269 leot 14129: </tr>
14130: <tr>
1.336 nia 14131: <td>compiler</td>
1.337 gutterid 14132: <td>conf</td>
1.269 leot 14133: </tr>
14134: <tr>
1.336 nia 14135: <td>config.guess</td>
1.337 gutterid 14136: <td>config.sub</td>
1.269 leot 14137: </tr>
14138: <tr>
1.336 nia 14139: <td>configuration</td>
1.337 gutterid 14140: <td>configure</td>
1.269 leot 14141: </tr>
14142: <tr>
1.336 nia 14143: <td>configure-env</td>
1.337 gutterid 14144: <td>configure-help</td>
1.269 leot 14145: </tr>
14146: <tr>
1.336 nia 14147: <td>configure_args</td>
1.337 gutterid 14148: <td>connect</td>
1.269 leot 14149: </tr>
14150: <tr>
1.336 nia 14151: <td>cos</td>
1.337 gutterid 14152: <td>cputime</td>
1.269 leot 14153: </tr>
14154: <tr>
1.336 nia 14155: <td>create-usergroup</td>
1.337 gutterid 14156: <td>csh</td>
1.269 leot 14157: </tr>
14158: <tr>
1.336 nia 14159: <td>ctf</td>
1.340 ! gutterid 14160: <td>debug</td>
1.338 nia 14161: </tr>
14162: <tr>
14163: <td>declaration</td>
1.340 ! gutterid 14164: <td>declare</td>
1.289 leot 14165: </tr>
14166: <tr>
1.338 nia 14167: <td>defined</td>
1.340 ! gutterid 14168: <td>depend</td>
1.329 leot 14169: </tr>
14170: <tr>
1.338 nia 14171: <td>dependencies</td>
1.340 ! gutterid 14172: <td>depends</td>
1.320 wiz 14173: </tr>
14174: <tr>
1.338 nia 14175: <td>depends-checksum</td>
1.340 ! gutterid 14176: <td>depends-fetch</td>
1.269 leot 14177: </tr>
14178: <tr>
1.338 nia 14179: <td>deps</td>
1.340 ! gutterid 14180: <td>describe</td>
1.311 leot 14181: </tr>
14182: <tr>
1.338 nia 14183: <td>destdir</td>
1.340 ! gutterid 14184: <td>disable</td>
1.269 leot 14185: </tr>
14186: <tr>
1.338 nia 14187: <td>distclean</td>
1.340 ! gutterid 14188: <td>distinfo</td>
1.269 leot 14189: </tr>
14190: <tr>
1.338 nia 14191: <td>dl</td>
1.340 ! gutterid 14192: <td>dlopen</td>
1.269 leot 14193: </tr>
14194: <tr>
1.338 nia 14195: <td>do-buildlink</td>
1.340 ! gutterid 14196: <td>do-clean</td>
1.269 leot 14197: </tr>
14198: <tr>
1.338 nia 14199: <td>do-configure</td>
1.340 ! gutterid 14200: <td>do-configure-post-hook</td>
1.269 leot 14201: </tr>
14202: <tr>
1.338 nia 14203: <td>do-extract</td>
1.340 ! gutterid 14204: <td>do-fetch</td>
1.277 rillig 14205: </tr>
14206: <tr>
1.338 nia 14207: <td>do-install</td>
1.340 ! gutterid 14208: <td>emul</td>
1.269 leot 14209: </tr>
14210: <tr>
1.338 nia 14211: <td>emul-distinfo</td>
1.340 ! gutterid 14212: <td>emul-fetch</td>
1.332 rillig 14213: </tr>
14214: <tr>
1.338 nia 14215: <td>emulation</td>
1.340 ! gutterid 14216: <td>emulator</td>
1.269 leot 14217: </tr>
14218: <tr>
1.338 nia 14219: <td>enable</td>
1.336 nia 14220: <td>endian</td>
1.269 leot 14221: </tr>
14222: <tr>
1.336 nia 14223: <td>enomem</td>
1.337 gutterid 14224: <td>ensurepip</td>
1.329 leot 14225: </tr>
14226: <tr>
1.327 wiz 14227: <td>err</td>
1.337 gutterid 14228: <td>errx</td>
1.269 leot 14229: </tr>
14230: <tr>
1.327 wiz 14231: <td>etc</td>
1.337 gutterid 14232: <td>exp</td>
1.320 wiz 14233: </tr>
14234: <tr>
1.327 wiz 14235: <td>extract-rpm</td>
1.337 gutterid 14236: <td>fabs</td>
1.311 leot 14237: </tr>
14238: <tr>
1.327 wiz 14239: <td>feature</td>
1.337 gutterid 14240: <td>features</td>
1.269 leot 14241: </tr>
14242: <tr>
1.327 wiz 14243: <td>fetch</td>
1.337 gutterid 14244: <td>fetch-list</td>
1.269 leot 14245: </tr>
14246: <tr>
1.327 wiz 14247: <td>follows</td>
1.337 gutterid 14248: <td>forbids</td>
1.289 leot 14249: </tr>
14250: <tr>
1.327 wiz 14251: <td>form</td>
1.337 gutterid 14252: <td>format</td>
1.269 leot 14253: </tr>
14254: <tr>
1.327 wiz 14255: <td>fortify</td>
1.335 nia 14256: <td>fortify_source</td>
1.332 rillig 14257: </tr>
14258: <tr>
1.335 nia 14259: <td>friend</td>
1.340 ! gutterid 14260: <td>fts</td>
1.338 nia 14261: </tr>
14262: <tr>
14263: <td>fts_close</td>
1.340 ! gutterid 14264: <td>fts_open</td>
1.269 leot 14265: </tr>
14266: <tr>
1.338 nia 14267: <td>fts_read</td>
1.340 ! gutterid 14268: <td>fts_set</td>
1.269 leot 14269: </tr>
14270: <tr>
1.338 nia 14271: <td>gcc</td>
1.340 ! gutterid 14272: <td>gethostbyaddr</td>
1.269 leot 14273: </tr>
14274: <tr>
1.338 nia 14275: <td>gethostbyname</td>
1.340 ! gutterid 14276: <td>gethostbyname2</td>
1.269 leot 14277: </tr>
14278: <tr>
1.338 nia 14279: <td>getopt_long</td>
1.340 ! gutterid 14280: <td>getprogname</td>
1.289 leot 14281: </tr>
14282: <tr>
1.338 nia 14283: <td>getservbyname</td>
1.340 ! gutterid 14284: <td>getservbyport</td>
1.269 leot 14285: </tr>
14286: <tr>
1.338 nia 14287: <td>getservent</td>
1.332 rillig 14288: <td>gettext</td>
1.289 leot 14289: </tr>
14290: <tr>
1.324 nia 14291: <td>github</td>
1.338 nia 14292: <td>gitlab</td>
14293: </tr>
14294: <tr>
1.324 nia 14295: <td>glob</td>
1.338 nia 14296: <td>gnu</td>
1.332 rillig 14297: </tr>
14298: <tr>
14299: <td>gnu_configure_strict</td>
1.338 nia 14300: <td>go</td>
1.269 leot 14301: </tr>
14302: <tr>
1.332 rillig 14303: <td>go-deps</td>
1.338 nia 14304: <td>golang</td>
1.274 rillig 14305: </tr>
14306: <tr>
1.332 rillig 14307: <td>guess-license</td>
1.338 nia 14308: <td>hashbang</td>
1.269 leot 14309: </tr>
14310: <tr>
1.332 rillig 14311: <td>heimdal</td>
1.338 nia 14312: <td>help</td>
1.269 leot 14313: </tr>
14314: <tr>
1.337 gutterid 14315: <td>imake</td>
1.340 ! gutterid 14316: <td>increment</td>
1.329 leot 14317: </tr>
14318: <tr>
1.337 gutterid 14319: <td>indirect</td>
1.340 ! gutterid 14320: <td>inet_aton</td>
1.269 leot 14321: </tr>
14322: <tr>
1.327 wiz 14323: <td>interp</td>
1.340 ! gutterid 14324: <td>interpreter</td>
1.320 wiz 14325: </tr>
14326: <tr>
1.327 wiz 14327: <td>intl</td>
1.340 ! gutterid 14328: <td>ip4</td>
1.311 leot 14329: </tr>
14330: <tr>
1.327 wiz 14331: <td>ip6</td>
1.340 ! gutterid 14332: <td>ipv4</td>
1.269 leot 14333: </tr>
14334: <tr>
1.327 wiz 14335: <td>ipv6</td>
1.340 ! gutterid 14336: <td>iso</td>
1.269 leot 14337: </tr>
14338: <tr>
1.327 wiz 14339: <td>kerberos</td>
1.340 ! gutterid 14340: <td>krb</td>
1.269 leot 14341: </tr>
14342: <tr>
1.327 wiz 14343: <td>krb5</td>
1.340 ! gutterid 14344: <td>ksh</td>
1.269 leot 14345: </tr>
14346: <tr>
1.327 wiz 14347: <td>lapack</td>
1.340 ! gutterid 14348: <td>latex</td>
1.303 bacon 14349: </tr>
14350: <tr>
1.327 wiz 14351: <td>libintl_bindtextdomain</td>
1.340 ! gutterid 14352: <td>libintl_gettext</td>
1.303 bacon 14353: </tr>
14354: <tr>
1.327 wiz 14355: <td>libintl_textdomain</td>
1.340 ! gutterid 14356: <td>libnbcompat</td>
1.269 leot 14357: </tr>
14358: <tr>
1.327 wiz 14359: <td>libs</td>
1.340 ! gutterid 14360: <td>libtool</td>
1.292 leot 14361: </tr>
14362: <tr>
1.327 wiz 14363: <td>licence</td>
1.340 ! gutterid 14364: <td>license</td>
1.269 leot 14365: </tr>
14366: <tr>
1.327 wiz 14367: <td>lintl</td>
1.340 ! gutterid 14368: <td>little-endian</td>
1.289 leot 14369: </tr>
14370: <tr>
1.327 wiz 14371: <td>lock</td>
1.340 ! gutterid 14372: <td>locking</td>
1.274 rillig 14373: </tr>
14374: <tr>
1.333 nia 14375: <td>lua</td>
1.340 ! gutterid 14376: <td>lvalue</td>
1.271 brook 14377: </tr>
14378: <tr>
1.330 wiz 14379: <td>make</td>
1.340 ! gutterid 14380: <td>makesum</td>
1.269 leot 14381: </tr>
14382: <tr>
1.330 wiz 14383: <td>memory</td>
14384: <td>meta</td>
1.269 leot 14385: </tr>
14386: <tr>
1.338 nia 14387: <td>meta-package</td>
1.330 wiz 14388: <td>meta_package</td>
1.269 leot 14389: </tr>
14390: <tr>
1.338 nia 14391: <td>mit-krb5</td>
1.330 wiz 14392: <td>mk.conf</td>
1.292 leot 14393: </tr>
14394: <tr>
1.338 nia 14395: <td>mkl</td>
1.330 wiz 14396: <td>mount</td>
1.274 rillig 14397: </tr>
14398: <tr>
1.338 nia 14399: <td>mprotect</td>
1.330 wiz 14400: <td>mremap</td>
1.269 leot 14401: </tr>
14402: <tr>
1.338 nia 14403: <td>nb</td>
1.330 wiz 14404: <td>nbcompat</td>
1.269 leot 14405: </tr>
14406: <tr>
1.338 nia 14407: <td>netlib</td>
1.333 nia 14408: <td>node</td>
14409: </tr>
14410: <tr>
1.338 nia 14411: <td>node.js</td>
1.333 nia 14412: <td>nodejs</td>
14413: </tr>
14414: <tr>
1.338 nia 14415: <td>obstack</td>
1.332 rillig 14416: <td>obstack_ptr_grow</td>
1.320 wiz 14417: </tr>
14418: <tr>
1.338 nia 14419: <td>occurs</td>
1.332 rillig 14420: <td>only</td>
1.269 leot 14421: </tr>
14422: <tr>
1.338 nia 14423: <td>openblas</td>
1.332 rillig 14424: <td>options</td>
1.269 leot 14425: </tr>
14426: <tr>
1.338 nia 14427: <td>options.mk</td>
1.332 rillig 14428: <td>order</td>
1.269 leot 14429: </tr>
14430: <tr>
1.338 nia 14431: <td>override</td>
1.332 rillig 14432: <td>override-intltool</td>
1.271 brook 14433: </tr>
14434: <tr>
1.338 nia 14435: <td>override-message-intltool</td>
1.332 rillig 14436: <td>package</td>
1.269 leot 14437: </tr>
14438: <tr>
1.338 nia 14439: <td>parallel</td>
1.332 rillig 14440: <td>path</td>
1.269 leot 14441: </tr>
14442: <tr>
1.338 nia 14443: <td>pax</td>
1.332 rillig 14444: <td>paxctl</td>
1.269 leot 14445: </tr>
14446: <tr>
1.338 nia 14447: <td>pbulk-index</td>
1.332 rillig 14448: <td>pc</td>
1.269 leot 14449: </tr>
14450: <tr>
1.338 nia 14451: <td>perl</td>
1.332 rillig 14452: <td>perl5</td>
1.269 leot 14453: </tr>
14454: <tr>
1.338 nia 14455: <td>perms</td>
1.332 rillig 14456: <td>php</td>
1.269 leot 14457: </tr>
14458: <tr>
1.338 nia 14459: <td>pkg-build-options</td>
1.332 rillig 14460: <td>pkg-config</td>
1.269 leot 14461: </tr>
14462: <tr>
1.338 nia 14463: <td>pkg_build_options</td>
1.332 rillig 14464: <td>platform</td>
1.269 leot 14465: </tr>
14466: <tr>
1.338 nia 14467: <td>plist</td>
1.332 rillig 14468: <td>post-extract</td>
1.269 leot 14469: </tr>
14470: <tr>
1.338 nia 14471: <td>post-fetch</td>
1.332 rillig 14472: <td>post-wrapper</td>
1.269 leot 14473: </tr>
14474: <tr>
1.338 nia 14475: <td>pre-build-checks-hook</td>
1.332 rillig 14476: <td>pre-configure</td>
1.269 leot 14477: </tr>
14478: <tr>
1.338 nia 14479: <td>pre-configure-checks-hook</td>
1.332 rillig 14480: <td>pre-extract</td>
1.289 leot 14481: </tr>
14482: <tr>
1.338 nia 14483: <td>pre-fetch</td>
1.332 rillig 14484: <td>print-go-deps</td>
1.269 leot 14485: </tr>
14486: <tr>
1.338 nia 14487: <td>print-plist</td>
1.332 rillig 14488: <td>print-summary-data</td>
1.269 leot 14489: </tr>
14490: <tr>
1.338 nia 14491: <td>privileged-install-hook</td>
1.332 rillig 14492: <td>pypi</td>
1.269 leot 14493: </tr>
14494: <tr>
1.338 nia 14495: <td>python</td>
1.332 rillig 14496: <td>r</td>
1.269 leot 14497: </tr>
14498: <tr>
1.338 nia 14499: <td>readme-all</td>
1.337 gutterid 14500: <td>recursive</td>
1.269 leot 14501: </tr>
14502: <tr>
1.338 nia 14503: <td>recv</td>
1.335 nia 14504: <td>recvfrom</td>
1.289 leot 14505: </tr>
14506: <tr>
1.338 nia 14507: <td>regcomp</td>
1.335 nia 14508: <td>release-localbase-lock</td>
1.289 leot 14509: </tr>
14510: <tr>
1.338 nia 14511: <td>release-lock</td>
1.335 nia 14512: <td>relro</td>
1.269 leot 14513: </tr>
14514: <tr>
1.338 nia 14515: <td>rename</td>
1.335 nia 14516: <td>reorder</td>
1.269 leot 14517: </tr>
14518: <tr>
1.338 nia 14519: <td>replace</td>
1.335 nia 14520: <td>replace_interpreter</td>
1.269 leot 14521: </tr>
14522: <tr>
1.338 nia 14523: <td>reproducible</td>
1.335 nia 14524: <td>resolv</td>
1.269 leot 14525: </tr>
14526: <tr>
1.338 nia 14527: <td>root</td>
1.335 nia 14528: <td>ruby</td>
1.289 leot 14529: </tr>
14530: <tr>
1.338 nia 14531: <td>send</td>
1.335 nia 14532: <td>sendfile</td>
1.269 leot 14533: </tr>
14534: <tr>
1.338 nia 14535: <td>sendto</td>
1.335 nia 14536: <td>setenv</td>
1.269 leot 14537: </tr>
14538: <tr>
1.338 nia 14539: <td>setgid</td>
1.335 nia 14540: <td>setprogname</td>
1.269 leot 14541: </tr>
14542: <tr>
1.338 nia 14543: <td>setuid</td>
1.335 nia 14544: <td>sh</td>
1.269 leot 14545: </tr>
14546: <tr>
1.338 nia 14547: <td>shebang</td>
1.335 nia 14548: <td>show</td>
1.296 rillig 14549: </tr>
14550: <tr>
1.338 nia 14551: <td>show-all</td>
1.335 nia 14552: <td>show-build-defs</td>
1.269 leot 14553: </tr>
14554: <tr>
1.338 nia 14555: <td>show-depends</td>
1.337 gutterid 14556: <td>show-depends-dirs</td>
14557: </tr>
14558: <tr>
14559: <td>show-depends-pkgpaths</td>
1.338 nia 14560: <td>show-depends-recursive</td>
14561: </tr>
14562: <tr>
1.335 nia 14563: <td>show-deps</td>
1.338 nia 14564: <td>show-distfiles</td>
1.269 leot 14565: </tr>
14566: <tr>
1.335 nia 14567: <td>show-downlevel</td>
1.338 nia 14568: <td>show-subdir-var</td>
1.269 leot 14569: </tr>
14570: <tr>
1.335 nia 14571: <td>show-tools</td>
1.338 nia 14572: <td>show-var</td>
1.269 leot 14573: </tr>
14574: <tr>
1.335 nia 14575: <td>show-vars</td>
1.338 nia 14576: <td>snprintf</td>
1.269 leot 14577: </tr>
14578: <tr>
1.335 nia 14579: <td>socket</td>
1.338 nia 14580: <td>ssp</td>
1.289 leot 14581: </tr>
14582: <tr>
1.335 nia 14583: <td>st_mode</td>
1.338 nia 14584: <td>stage-install</td>
1.269 leot 14585: </tr>
14586: <tr>
1.335 nia 14587: <td>strcasestr</td>
1.338 nia 14588: <td>strict</td>
1.269 leot 14589: </tr>
14590: <tr>
1.335 nia 14591: <td>strip</td>
1.338 nia 14592: <td>strndup</td>
1.277 rillig 14593: </tr>
14594: <tr>
1.335 nia 14595: <td>strnlen</td>
1.338 nia 14596: <td>strsep</td>
1.269 leot 14597: </tr>
14598: <tr>
1.335 nia 14599: <td>subst</td>
1.338 nia 14600: <td>substitutions</td>
1.329 leot 14601: </tr>
14602: <tr>
1.326 gutterid 14603: <td>sun</td>
1.340 ! gutterid 14604: <td>sunpro</td>
1.327 wiz 14605: </tr>
14606: <tr>
14607: <td>sunwspro</td>
1.276 leot 14608: <td>symlink</td>
1.338 nia 14609: </tr>
14610: <tr>
1.337 gutterid 14611: <td>test</td>
1.338 nia 14612: <td>test-env</td>
1.269 leot 14613: </tr>
14614: <tr>
1.337 gutterid 14615: <td>tex</td>
1.338 nia 14616: <td>texlive</td>
1.269 leot 14617: </tr>
14618: <tr>
1.337 gutterid 14619: <td>tmp</td>
1.338 nia 14620: <td>tool</td>
1.269 leot 14621: </tr>
14622: <tr>
1.337 gutterid 14623: <td>tools</td>
1.338 nia 14624: <td>tools-libtool-m4-override</td>
1.269 leot 14625: </tr>
14626: <tr>
1.338 nia 14627: <td>transitive</td>
1.337 gutterid 14628: <td>type</td>
1.269 leot 14629: </tr>
14630: <tr>
1.289 leot 14631: <td>ulimit</td>
1.337 gutterid 14632: <td>undefined</td>
1.269 leot 14633: </tr>
14634: <tr>
1.289 leot 14635: <td>undo-replace</td>
1.337 gutterid 14636: <td>unlimit</td>
1.269 leot 14637: </tr>
14638: <tr>
1.289 leot 14639: <td>unprivileged</td>
1.337 gutterid 14640: <td>unprivileged-install-hook</td>
1.269 leot 14641: </tr>
14642: <tr>
1.289 leot 14643: <td>unstripped</td>
1.337 gutterid 14644: <td>update</td>
1.269 leot 14645: </tr>
14646: <tr>
1.289 leot 14647: <td>upload</td>
1.337 gutterid 14648: <td>upload-distfiles</td>
1.269 leot 14649: </tr>
14650: <tr>
1.270 leot 14651: <td>use_tools</td>
1.337 gutterid 14652: <td>user</td>
1.269 leot 14653: </tr>
14654: <tr>
1.270 leot 14655: <td>utimes</td>
1.337 gutterid 14656: <td>vasprintf</td>
1.269 leot 14657: </tr>
14658: <tr>
1.270 leot 14659: <td>verbose</td>
1.337 gutterid 14660: <td>vsnprintf</td>
1.269 leot 14661: </tr>
14662: <tr>
1.270 leot 14663: <td>warn</td>
1.337 gutterid 14664: <td>warning</td>
1.269 leot 14665: </tr>
14666: <tr>
1.270 leot 14667: <td>warnings</td>
1.337 gutterid 14668: <td>warnx</td>
1.269 leot 14669: </tr>
14670: <tr>
1.289 leot 14671: <td>wattr_off</td>
1.337 gutterid 14672: <td>wattr_on</td>
1.269 leot 14673: </tr>
14674: <tr>
1.289 leot 14675: <td>work</td>
1.337 gutterid 14676: <td>wrapper</td>
1.269 leot 14677: </tr>
14678: <tr>
1.289 leot 14679: <td>wrkdir</td>
1.337 gutterid 14680: <td> </td>
1.269 leot 14681: </tr>
14682: </table>
1.267 rillig 14683: </div>
14684: <div class="appendix">
14685: <div class="titlepage"><div><div><h1 class="title">
1.322 leot 14686: <a name="editing"></a>Appendix F. Editing guidelines for the pkgsrc guide</h1></div></div></div>
1.75 rillig 14687: <div class="toc">
14688: <p><b>Table of Contents</b></p>
1.210 leot 14689: <dl class="toc">
1.322 leot 14690: <dt><span class="sect1"><a href="#targets">F.1. Make targets</a></span></dt>
14691: <dt><span class="sect1"><a href="#procedure">F.2. Procedure</a></span></dt>
1.75 rillig 14692: </dl>
14693: </div>
1.79 rillig 14694: <p>This section contains information on editing the pkgsrc
14695: guide itself.</p>
1.148 asau 14696: <div class="sect1">
1.75 rillig 14697: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.322 leot 14698: <a name="targets"></a>F.1. Make targets</h2></div></div></div>
1.79 rillig 14699: <p>The pkgsrc guide's source code is stored in
14700: <code class="filename">pkgsrc/doc/guide/files</code>, and several files
14701: are created from it:</p>
1.148 asau 14702: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.128 wiz 14703: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.txt</code></p></li>
14704: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.html</code></p></li>
1.289 leot 14705: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/docs/pkgsrc/" target="_top">https://www.NetBSD.org/docs/pkgsrc/</a></p></li>
14706: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf" target="_top">https://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf</a>:
1.79 rillig 14707: The PDF version of the pkgsrc guide.</p></li>
1.289 leot 14708: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps" target="_top">https://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps</a>:
1.79 rillig 14709: PostScript version of the pkgsrc guide.</p></li>
1.75 rillig 14710: </ul></div>
14711: </div>
1.148 asau 14712: <div class="sect1">
1.75 rillig 14713: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.322 leot 14714: <a name="procedure"></a>F.2. Procedure</h2></div></div></div>
1.79 rillig 14715: <p>The procedure to edit the pkgsrc guide is:</p>
1.128 wiz 14716: <div class="procedure"><ol class="procedure" type="1">
1.304 bacon 14717: <li class="step"><p>Make sure you have checked out the htdocs repository
14718: into a sibling directory of your pkgsrc directory. You will need
14719: the ability to commit from both pkgsrc and htdocs.</p></li>
1.148 asau 14720: <li class="step"><p>Make sure you have the packages needed to
1.83 wiz 14721: regenerate the pkgsrc guide (and other XML-based NetBSD
1.151 obache 14722: documentation) installed. These are automatically installed when
1.322 leot 14723: you install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/pkgsrc-guide-tools/index.html" target="_top"><code class="filename">meta-pkgs/pkgsrc-guide-tools</code></a> package.</p></li>
1.148 asau 14724: <li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the
1.79 rillig 14725: right directory. All further steps will take place
14726: here.</p></li>
1.148 asau 14727: <li class="step"><p>Edit the XML file(s) in
1.79 rillig 14728: <code class="filename">files/</code>.</p></li>
1.148 asau 14729: <li class="step"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc
1.79 rillig 14730: guide for valid XML and to build the final output files. If you
14731: get any errors at this stage, you can just edit the files, as
14732: there are only symbolic links in the working directory, pointing
14733: to the files in <code class="filename">files/</code>.</p></li>
1.148 asau 14734: <li class="step"><p><span class="command"><strong>(cd files && cvs
1.79 rillig 14735: commit)</strong></span></p></li>
1.148 asau 14736: <li class="step"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to
1.79 rillig 14737: regenerate the output files with the proper RCS
14738: Ids.</p></li>
1.148 asau 14739: <li class="step">
1.110 hubertf 14740: <p>Run <span class="command"><strong>bmake regen</strong></span> to install and
1.91 rillig 14741: commit the files in both <code class="filename">pkgsrc/doc</code> and
14742: <code class="filename">htdocs</code>.</p>
1.148 asau 14743: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.91 rillig 14744: <h3 class="title">Note</h3>
14745: <p>If you have added, removed or renamed some chapters,
1.110 hubertf 14746: you need to synchronize them using <span class="command"><strong>cvs add</strong></span> or
14747: <span class="command"><strong>cvs delete</strong></span> in the htdocs
1.91 rillig 14748: directory.</p>
14749: </div>
14750: </li>
1.79 rillig 14751: </ol></div>
1.75 rillig 14752: </div>
14753: </div>
14754: </div></body>
1.1 grant 14755: </html>
CVSweb <webmaster@jp.NetBSD.org>