Annotation of htdocs/docs/pkgsrc/pkgsrc.html, revision 1.252
1.1 dsieger 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5: <title>The pkgsrc guide</title>
1.25 spz 6: <link rel="stylesheet" type="text/css" href="/global.css">
1.1 dsieger 7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
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.">
9: </head>
1.41 asau 10: <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book">
1.1 dsieger 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.10 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.1 dsieger 22: </div>
23: <div class="author">
24: <h3 class="author">
25: <span class="firstname">Hubert</span> <span class="surname">Feyrer</span>
26: </h3>
1.10 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.1 dsieger 28: </div>
29: <h3 class="corpauthor">
30: The pkgsrc Developers
31: </h3>
32: </div></div>
1.252 ! jnemeth 33: <div><p class="copyright">Copyright © 1994-2024 The NetBSD Foundation, Inc</p></div>
! 34: <div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.43 2024/01/02 07:26:32 jnemeth Exp $</p></div>
1.41 asau 35: <div><div class="abstract">
1.1 dsieger 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.100 leot 48: <dl class="toc">
1.1 dsieger 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>
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>
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>
58: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
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.154 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.1 dsieger 65: <dd><dl>
1.154 rillig 66: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.1 dsieger 67: <dd><dl>
1.154 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.1 dsieger 70: </dl></dd>
1.154 rillig 71: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.1 dsieger 72: <dd><dl>
1.154 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.1 dsieger 75: </dl></dd>
76: </dl></dd>
1.154 rillig 77: <dt><span class="chapter"><a href="#platforms">4. Using pkgsrc on systems other than NetBSD</a></span></dt>
1.1 dsieger 78: <dd><dl>
1.154 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.1 dsieger 81: </dl></dd>
1.154 rillig 82: <dt><span class="chapter"><a href="#using">5. Using pkgsrc</a></span></dt>
1.1 dsieger 83: <dd><dl>
1.154 rillig 84: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.1 dsieger 85: <dd><dl>
1.154 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.202 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.1 dsieger 94: </dl></dd>
1.154 rillig 95: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.1 dsieger 96: <dd><dl>
1.154 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.1 dsieger 100: </dl></dd>
101: </dl></dd>
1.154 rillig 102: <dt><span class="chapter"><a href="#configuring">6. Configuring pkgsrc</a></span></dt>
1.1 dsieger 103: <dd><dl>
1.154 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>
1.241 rillig 106: <dt><span class="sect1"><a href="#native-or-pkgsrc-preference">6.3. Preferences for native or pkgsrc software</a></span></dt>
107: <dt><span class="sect1"><a href="#variables-affecting-installation">6.4. Variables affecting the installation process</a></span></dt>
108: <dt><span class="sect1"><a href="#conf.compiler">6.5. Selecting and configuring the compiler</a></span></dt>
109: <dd><dl>
110: <dt><span class="sect2"><a href="#selecting-the-compiler">6.5.1. Selecting the compiler</a></span></dt>
111: <dt><span class="sect2"><a href="#conf.cflags">6.5.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
112: <dt><span class="sect2"><a href="#conf.ldflags">6.5.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 113: </dl></dd>
1.241 rillig 114: <dt><span class="sect1"><a href="#developer-advanced-settings">6.6. Developer/advanced settings</a></span></dt>
115: <dt><span class="sect1"><a href="#selecting-build-options">6.7. Selecting Build Options</a></span></dt>
1.1 dsieger 116: </dl></dd>
1.154 rillig 117: <dt><span class="chapter"><a href="#binary">7. Creating binary packages</a></span></dt>
1.1 dsieger 118: <dd><dl>
1.154 rillig 119: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
120: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.6 rillig 121: </dl></dd>
1.154 rillig 122: <dt><span class="chapter"><a href="#bulk">8. Creating binary packages for everything in pkgsrc (bulk
1.6 rillig 123: builds)</a></span></dt>
1.1 dsieger 124: <dd><dl>
1.154 rillig 125: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.180 rillig 126: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.154 rillig 127: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
128: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.178 rillig 129: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
130: <dd><dl>
1.179 rillig 131: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
132: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.181 rillig 133: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
134: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
135: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
136: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
137: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
138: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
139: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
140: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.178 rillig 141: </dl></dd>
142: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
143: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.154 rillig 144: </dl></dd>
145: <dt><span class="chapter"><a href="#files">9. Directory layout of the installed files</a></span></dt>
146: <dd><dl>
147: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
148: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
149: </dl></dd>
150: <dt><span class="chapter"><a href="#faq">10. Frequently Asked Questions</a></span></dt>
151: <dd><dl>
152: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
153: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
154: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
155: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
156: <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>
157: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
158: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
159: <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>
160: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
161: <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.23 wiz 162: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.154 rillig 163: <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.221 nia 164: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.154 rillig 165: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
166: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
167: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
168: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
169: <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.1 dsieger 170: </dl></dd>
171: </dl></dd>
172: <dt><span class="part"><a href="#developers-guide">II. The pkgsrc developer's guide</a></span></dt>
173: <dd><dl>
1.154 rillig 174: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.184 rillig 175: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.1 dsieger 176: <dd><dl>
1.184 rillig 177: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
178: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
179: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.1 dsieger 180: <dd><dl>
1.184 rillig 181: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
182: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
183: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
184: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
185: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.1 dsieger 186: </dl></dd>
1.184 rillig 187: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
188: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
189: <dd><dl>
190: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
191: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
192: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
193: </dl></dd>
194: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
195: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 196: </dl></dd>
1.184 rillig 197: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.6 rillig 198: <dd><dl>
1.184 rillig 199: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
200: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
201: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
202: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
203: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 204: <dd><dl>
1.184 rillig 205: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
206: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.6 rillig 207: </dl></dd>
1.184 rillig 208: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
209: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
210: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
211: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
212: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
213: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
214: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
215: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
216: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
217: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
218: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
219: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
220: </dl></dd>
221: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
222: <dd><dl>
223: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.6 rillig 224: <dd><dl>
1.219 nia 225: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
226: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
227: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.6 rillig 228: </dl></dd>
1.184 rillig 229: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
230: <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.6 rillig 231: </dl></dd>
1.184 rillig 232: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 233: <dd><dl>
1.184 rillig 234: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
235: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
236: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
237: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.6 rillig 238: <dd><dl>
1.184 rillig 239: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
240: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
241: <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>
242: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 243: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.6 rillig 244: </dl></dd>
245: </dl></dd>
1.184 rillig 246: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.6 rillig 247: <dd><dl>
1.184 rillig 248: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
249: <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>
250: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
251: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 252: </dl></dd>
1.184 rillig 253: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.6 rillig 254: <dd><dl>
1.184 rillig 255: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
256: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
257: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
258: </dl></dd>
259: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
260: <dd><dl>
261: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
262: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 263: <dd><dl>
1.184 rillig 264: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
265: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.26 wiz 266: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
267: and
268: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
269: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 270: </dl></dd>
1.184 rillig 271: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.241 rillig 272: <dd><dl><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></dl></dd>
1.184 rillig 273: </dl></dd>
274: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.6 rillig 275: <dd><dl>
1.184 rillig 276: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
277: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
278: <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>
279: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
280: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
281: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
282: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
283: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
284: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.6 rillig 285: </dl></dd>
1.184 rillig 286: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
287: <dd><dl>
288: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
289: <dd><dl>
290: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
291: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.6 rillig 292: </dl></dd>
1.184 rillig 293: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.6 rillig 294: <dd><dl>
1.184 rillig 295: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
296: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
1.239 dholland 297: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installation</a></span></dt>
298: <dt><span class="sect2"><a href="#conf-files-declare">20.2.4. Declaring configuration files</a></span></dt>
299: <dt><span class="sect2"><a href="#conf-files-disable">20.2.5. Disabling handling of configuration files</a></span></dt>
1.184 rillig 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.154 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.223 nia 336: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 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.205 wiz 342: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 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.154 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.172 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.154 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.203 nia 363: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 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.203 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.1 dsieger 373: emulation</a></span></dt>
1.203 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.1 dsieger 376: </dl></dd>
1.154 rillig 377: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 378: </dl></dd>
1.184 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.154 rillig 386: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.1 dsieger 387: <dd><dl>
1.154 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.1 dsieger 398: </dl></dd>
399: <dt><span class="part"><a href="#infrastructure">III. The pkgsrc infrastructure internals</a></span></dt>
400: <dd><dl>
1.184 rillig 401: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 402: <dd><dl>
1.184 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.1 dsieger 406: <dd><dl>
1.184 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.1 dsieger 409: </dl></dd>
1.184 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.1 dsieger 412: <dd><dl>
1.184 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.1 dsieger 415: </dl></dd>
1.184 rillig 416: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 417: <dd><dl>
1.184 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.1 dsieger 420: </dl></dd>
421: </dl></dd>
1.184 rillig 422: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.1 dsieger 423: <dd><dl>
1.184 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.1 dsieger 426: <dd><dl>
1.184 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.1 dsieger 429: </dl></dd>
430: </dl></dd>
1.184 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.1 dsieger 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.172 rillig 441: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.1 dsieger 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.207 leot 445: <dt><span class="appendix"><a href="#hardening">B. Security hardening</a></span></dt>
1.1 dsieger 446: <dd><dl>
1.207 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.1 dsieger 471: </dl></dd>
1.207 leot 472: <dt><span class="appendix"><a href="#ftp-layout">D. Directory layout of the pkgsrc FTP server</a></span></dt>
1.1 dsieger 473: <dd><dl>
1.207 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.148 leot 479: <code class="filename">stable</code>,
1.23 wiz 480: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 481: source packages</a></span></dt>
482: </dl></dd>
1.207 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.1 dsieger 485: <dd><dl>
1.207 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.1 dsieger 488: </dl></dd>
489: </dl>
490: </div>
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.184 rillig 496: <dt>12.1. <a href="#patch-examples">Patching examples</a>
1.1 dsieger 497: </dt>
1.184 rillig 498: <dt>22.1. <a href="#plist-handling">PLIST handling for GNOME packages</a>
1.1 dsieger 499: </dt>
500: </dl>
501: </div>
1.41 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.1 dsieger 505: <div class="toc">
506: <p><b>Table of Contents</b></p>
1.100 leot 507: <dl class="toc">
1.1 dsieger 508: <dt><span class="sect1"><a href="#introduction-section">1.1. Introduction</a></span></dt>
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>
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>
515: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
516: <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
517: </dl>
518: </div>
1.41 asau 519: <div class="sect1">
1.1 dsieger 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>
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>
529: <p>pkgsrc currently contains several thousand packages,
530: including:</p>
1.41 asau 531: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 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.1 dsieger 533: web server</p></li>
1.207 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.1 dsieger 535: web browser</p></li>
1.207 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.1 dsieger 537: Desktop Environment</p></li>
1.207 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.1 dsieger 539: Desktop Environment</p></li>
540: </ul></div>
1.108 rillig 541: <p>… just to name a few.</p>
1.1 dsieger 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.41 asau 545: <div class="sect2">
1.1 dsieger 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.41 asau 551: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 552: <li class="listitem"><p>Easy building of software from source as well as the creation
1.1 dsieger 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.23 wiz 558: <li class="listitem"><p>All packages are installed in a consistent directory tree,
1.1 dsieger 559: including binaries, libraries, man pages and other
560: documentation.</p></li>
1.104 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.23 wiz 565: <li class="listitem"><p>Like NetBSD, pkgsrc is designed with portability in mind and
1.1 dsieger 566: consists of highly portable code. This allows the greatest speed of
1.25 spz 567: development when porting to a new platform. This portability also
1.1 dsieger 568: ensures that pkgsrc is <span class="emphasis"><em>consistent across all
569: platforms</em></span>.</p></li>
1.23 wiz 570: <li class="listitem"><p>The installation prefix, acceptable software licenses,
1.1 dsieger 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.23 wiz 574: <li class="listitem"><p>The entire source (not including the distribution files) is
1.1 dsieger 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>
580: <p>The following principles are basic to pkgsrc:</p>
1.41 asau 581: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 582: <li class="listitem"><p><span class="quote">“<span class="quote">It should only work if it's right.</span>”</span>
1.14 jmcneill 583: — That means, if a package contains bugs, it's better to find
1.1 dsieger 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.207 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.1 dsieger 587: of shell scripts), and post-installation checks (installed files,
588: references to shared libraries, script interpreters).</p></li>
1.23 wiz 589: <li class="listitem"><p><span class="quote">“<span class="quote">If it works, it should work everywhere</span>”</span>
1.14 jmcneill 590: — Like NetBSD has been ported to many hardware architectures,
1.1 dsieger 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>
594: </div>
1.41 asau 595: <div class="sect2">
1.1 dsieger 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>
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>
605: <div class="table">
606: <a name="supported-platforms"></a><p class="title"><b>Table 1.1. Platforms supported by pkgsrc</b></p>
1.106 tnn 607: <div class="table-contents"><table class="table" summary="Platforms supported by pkgsrc" border="1">
1.1 dsieger 608: <colgroup>
609: <col>
610: <col>
1.92 sevan 611: <col>
1.1 dsieger 612: </colgroup>
613: <thead><tr>
614: <th>Platform</th>
615: <th>Date Support Added</th>
1.92 sevan 616: <th>Notes</th>
1.1 dsieger 617: </tr></thead>
618: <tbody>
619: <tr>
1.174 leot 620: <td><a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a></td>
1.1 dsieger 621: <td align="center">Aug 1997</td>
1.92 sevan 622: <td class="auto-generated"> </td>
1.1 dsieger 623: </tr>
624: <tr>
1.10 hubertf 625: <td><a class="ulink" href="http://wwws.sun.com/software/solaris/" target="_top">Solaris</a></td>
1.1 dsieger 626: <td align="center">Mar 1999</td>
1.151 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.1 dsieger 628: </tr>
629: <tr>
1.174 leot 630: <td><a class="ulink" href="https://www.kernel.org/" target="_top">Linux</a></td>
1.1 dsieger 631: <td align="center">Jun 1999</td>
1.151 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.1 dsieger 633: </tr>
634: <tr>
635: <td>
1.118 sevan 636: <a class="ulink" href="https://developer.apple.com/macos/" target="_top">Darwin / Mac OS X / OS X / macOS</a>
1.1 dsieger 637: </td>
638: <td align="center">Oct 2001</td>
1.191 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.1 dsieger 640: </tr>
641: <tr>
1.174 leot 642: <td><a class="ulink" href="https://www.freebsd.org/" target="_top">FreeBSD</a></td>
1.1 dsieger 643: <td align="center">Nov 2002</td>
1.151 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.1 dsieger 645: </tr>
646: <tr>
1.174 leot 647: <td><a class="ulink" href="https://www.openbsd.org/" target="_top">OpenBSD</a></td>
1.1 dsieger 648: <td align="center">Nov 2002</td>
1.151 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.1 dsieger 650: </tr>
651: <tr>
1.174 leot 652: <td><a class="ulink" href="https://www.sgi.com/software/irix/" target="_top">IRIX</a></td>
1.1 dsieger 653: <td align="center">Dec 2002</td>
1.92 sevan 654: <td>
1.151 sevan 655: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX" target="_top">README.IRIX</a>
1.92 sevan 656: </td>
1.1 dsieger 657: </tr>
658: <tr>
659: <td>BSD/OS</td>
660: <td align="center">Dec 2003</td>
1.92 sevan 661: <td class="auto-generated"> </td>
1.1 dsieger 662: </tr>
663: <tr>
1.174 leot 664: <td><a class="ulink" href="https://www-1.ibm.com/servers/aix/" target="_top">AIX</a></td>
1.1 dsieger 665: <td align="center">Dec 2003</td>
1.151 sevan 666: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.AIX" target="_top">README.AIX</a></td>
1.1 dsieger 667: </tr>
668: <tr>
669: <td>
1.174 leot 670: <a class="ulink" href="https://www.microsoft.com/windows/sfu/" target="_top">Interix</a>
1.1 dsieger 671: (Microsoft Windows Services for Unix)
672: </td>
673: <td align="center">Mar 2004</td>
1.151 sevan 674: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Interix" target="_top">README.Interix</a></td>
1.1 dsieger 675: </tr>
676: <tr>
1.174 leot 677: <td><a class="ulink" href="https://www.dragonflybsd.org/" target="_top">DragonFlyBSD</a></td>
1.1 dsieger 678: <td align="center">Oct 2004</td>
1.92 sevan 679: <td class="auto-generated"> </td>
1.1 dsieger 680: </tr>
681: <tr>
1.10 hubertf 682: <td><a class="ulink" href="http://www.tru64.org/" target="_top">OSF/1</a></td>
1.1 dsieger 683: <td align="center">Nov 2004</td>
1.151 sevan 684: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OSF1" target="_top">README.OSF1</a></td>
1.1 dsieger 685: </tr>
686: <tr>
1.174 leot 687: <td><a class="ulink" href="https://www.hp.com/products1/unix/" target="_top">HP-UX</a></td>
1.1 dsieger 688: <td align="center">Apr 2007</td>
1.151 sevan 689: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.HPUX" target="_top">README.HPUX</a></td>
1.1 dsieger 690: </tr>
1.23 wiz 691: <tr>
1.174 leot 692: <td><a class="ulink" href="https://www.haiku-os.org/" target="_top">Haiku</a></td>
1.23 wiz 693: <td align="center">Sep 2010</td>
1.151 sevan 694: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Haiku" target="_top">README.Haiku</a></td>
1.23 wiz 695: </tr>
1.45 obache 696: <tr>
1.174 leot 697: <td><a class="ulink" href="https://www.mirbsd.org/" target="_top">MirBSD</a></td>
1.57 bsiegert 698: <td align="center">Jan 2011</td>
1.92 sevan 699: <td class="auto-generated"> </td>
1.45 obache 700: </tr>
701: <tr>
1.174 leot 702: <td><a class="ulink" href="https://www.minix3.org/" target="_top">Minix3</a></td>
1.45 obache 703: <td align="center">Nov 2011</td>
1.151 sevan 704: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Minix3" target="_top">README.Minix3</a></td>
1.45 obache 705: </tr>
706: <tr>
1.174 leot 707: <td><a class="ulink" href="https://cygwin.com/" target="_top">Cygwin</a></td>
1.45 obache 708: <td align="center">Mar 2013</td>
1.151 sevan 709: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Cygwin" target="_top">README.Cygwin</a></td>
1.45 obache 710: </tr>
1.58 ryoon 711: <tr>
1.174 leot 712: <td><a class="ulink" href="https://www.debian.org/ports/kfreebsd-gnu/" target="_top">GNU/kFreeBSD</a></td>
1.58 ryoon 713: <td align="center">Jul 2013</td>
1.151 sevan 714: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.GNUkFreeBSD" target="_top">README.GNUkFreeBSD</a></td>
1.58 ryoon 715: </tr>
1.104 sevan 716: <tr>
1.174 leot 717: <td><a class="ulink" href="https://www.bitrig.org/" target="_top">Bitrig</a></td>
1.104 sevan 718: <td align="center">Jun 2014</td>
1.229 gutterid 719: <td>Removed from pkgsrc Sep 2022</td>
1.104 sevan 720: </tr>
1.1 dsieger 721: </tbody>
722: </table></div>
723: </div>
724: <br class="table-break">
725: </div>
726: </div>
1.41 asau 727: <div class="sect1">
1.1 dsieger 728: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
729: <a name="overview"></a>1.2. Overview</h2></div></div></div>
730: <p>This document is divided into three parts. The first,
1.10 hubertf 731: <a class="link" href="#users-guide" title="Part I. The pkgsrc user's guide">The pkgsrc user's guide</a>,
1.1 dsieger 732: describes how one can use one of the packages in the Package
733: Collection, either by installing a precompiled binary package,
734: or by building one's own copy using the NetBSD package system.
1.10 hubertf 735: 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.1 dsieger 736: package so it can be easily built by other NetBSD users without
737: knowing about the package's building details. The third part,
1.10 hubertf 738: <a class="link" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">The pkgsrc infrastructure internals</a>
1.1 dsieger 739: is intended for those who want to understand how pkgsrc is
740: implemented.</p>
741: <p>This document is available in various formats:
1.10 hubertf 742: <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.1 dsieger 743: </div>
1.41 asau 744: <div class="sect1">
1.1 dsieger 745: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
746: <a name="terminology"></a>1.3. Terminology</h2></div></div></div>
1.23 wiz 747: <p>There has been a lot of talk about <span class="quote">“<span class="quote">ports</span>”</span>,
748: <span class="quote">“<span class="quote">packages</span>”</span>, etc. so far. Here is a description of all the
1.1 dsieger 749: terminology used within this document.</p>
1.41 asau 750: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 751: <dt><span class="term">Package</span></dt>
752: <dd><p>A set of files and building instructions
753: that describe what's necessary
754: to build a certain piece of software using
755: pkgsrc. Packages are traditionally stored under
1.123 wiz 756: <code class="filename">/usr/pkgsrc</code>,
757: but may be stored in any location,
758: referred to as <code class="varname">PKGSRCDIR</code>.</p></dd>
1.1 dsieger 759: <dt><span class="term">The NetBSD package system</span></dt>
1.23 wiz 760: <dd><p>This is the former name of <span class="quote">“<span class="quote">pkgsrc</span>”</span>. It
1.1 dsieger 761: is part of the NetBSD operating system and can be bootstrapped
762: to run on non-NetBSD operating systems as well. It handles
763: building (compiling), installing, and removing of
764: packages.</p></dd>
765: <dt><span class="term">Distfile</span></dt>
766: <dd><p>This term describes the file or files that are
767: provided by the author of the piece of software to
768: distribute his work. All the changes necessary to build on
769: NetBSD are reflected in the corresponding package. Usually
770: the distfile is in the form of a compressed tar-archive,
771: but other types are possible, too. Distfiles are usually
772: stored below
773: <code class="filename">/usr/pkgsrc/distfiles</code>.</p></dd>
774: <dt><span class="term">Port</span></dt>
775: <dd><p>This is the term used by FreeBSD and OpenBSD people
776: for what we call a package.
1.23 wiz 777: In NetBSD terminology, <span class="quote">“<span class="quote">port</span>”</span> refers to a different
1.1 dsieger 778: architecture.</p></dd>
779: <dt><span class="term">Precompiled/binary package</span></dt>
780: <dd>
781: <p>A set of binaries built with pkgsrc from a distfile
782: and stuffed together in a single <code class="filename">.tgz</code>
783: file so it can be installed on machines of the same
784: machine architecture without the need to
785: recompile. Packages are usually generated in
786: <code class="filename">/usr/pkgsrc/packages</code>; there is also
1.25 spz 787: an archive on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/" target="_top">ftp.NetBSD.org</a>.</p>
1.23 wiz 788: <p>Sometimes, this is referred to by the term <span class="quote">“<span class="quote">package</span>”</span> too,
1.1 dsieger 789: especially in the context of precompiled packages.</p>
790: </dd>
791: <dt><span class="term">Program</span></dt>
792: <dd><p>The piece of software to be installed which will be
793: constructed from all the files in the distfile by the
794: actions defined in the corresponding package.</p></dd>
795: </dl></div>
1.41 asau 796: <div class="sect2">
1.1 dsieger 797: <div class="titlepage"><div><div><h3 class="title">
798: <a name="term.roles"></a>1.3.1. Roles involved in pkgsrc</h3></div></div></div>
1.41 asau 799: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 800: <dt><span class="term">pkgsrc users</span></dt>
801: <dd>
802: <p>The
803: pkgsrc users are people who use the packages provided by pkgsrc.
804: Typically they are system administrators. The people using the
1.23 wiz 805: software that is inside the packages (maybe called <span class="quote">“<span class="quote">end
806: users</span>”</span>) are not covered by the pkgsrc guide.</p>
1.1 dsieger 807: <p>There are two kinds of pkgsrc users: Some only want to
808: install pre-built binary packages. Others build the pkgsrc
809: packages from source, either for installing them directly or for
1.10 hubertf 810: 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.1 dsieger 811: documentation.</p>
812: </dd>
813: <dt><span class="term">package maintainers</span></dt>
814: <dd><p>A
1.10 hubertf 815: 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.1 dsieger 816: <dt><span class="term">infrastructure developers</span></dt>
817: <dd><p>These people are involved in all those files
818: that live in the <code class="filename">mk/</code> directory and below.
1.10 hubertf 819: 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.1 dsieger 820: too.</p></dd>
821: </dl></div>
822: </div>
823: </div>
1.41 asau 824: <div class="sect1">
1.1 dsieger 825: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
826: <a name="typography"></a>1.4. Typography</h2></div></div></div>
827: <p>When giving examples for commands, shell prompts are used to
828: show if the command should/can be issued as root, or if
1.23 wiz 829: <span class="quote">“<span class="quote">normal</span>”</span> user privileges are sufficient. We use a
1.115 sevan 830: <code class="prompt">#</code> for root's shell prompt, a <code class="prompt">%</code> for users'
831: shell prompt, assuming they use the C-shell or tcsh and a <code class="prompt">$</code> for
1.229 gutterid 832: Bourne shell and derivatives.</p>
1.1 dsieger 833: </div>
834: </div>
1.41 asau 835: <div class="part">
1.1 dsieger 836: <div class="titlepage"><div><div><h1 class="title">
837: <a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div>
838: <div class="toc">
839: <p><b>Table of Contents</b></p>
1.100 leot 840: <dl class="toc">
1.154 rillig 841: <dt><span class="chapter"><a href="#help-user">2. Getting help</a></span></dt>
842: <dt><span class="chapter"><a href="#getting">3. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
1.1 dsieger 843: <dd><dl>
1.154 rillig 844: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.1 dsieger 845: <dd><dl>
1.154 rillig 846: <dt><span class="sect2"><a href="#getting-via-tar">3.1.1. As tar archive</a></span></dt>
847: <dt><span class="sect2"><a href="#getting-via-cvs">3.1.2. Via anonymous CVS</a></span></dt>
1.1 dsieger 848: </dl></dd>
1.154 rillig 849: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.1 dsieger 850: <dd><dl>
1.154 rillig 851: <dt><span class="sect2"><a href="#uptodate-tar">3.2.1. Via tar files</a></span></dt>
852: <dt><span class="sect2"><a href="#uptodate-cvs">3.2.2. Via CVS</a></span></dt>
1.1 dsieger 853: </dl></dd>
854: </dl></dd>
1.154 rillig 855: <dt><span class="chapter"><a href="#platforms">4. Using pkgsrc on systems other than NetBSD</a></span></dt>
1.1 dsieger 856: <dd><dl>
1.154 rillig 857: <dt><span class="sect1"><a href="#binarydist">4.1. Binary distribution</a></span></dt>
858: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">4.2. Bootstrapping pkgsrc</a></span></dt>
1.1 dsieger 859: </dl></dd>
1.154 rillig 860: <dt><span class="chapter"><a href="#using">5. Using pkgsrc</a></span></dt>
1.1 dsieger 861: <dd><dl>
1.154 rillig 862: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.1 dsieger 863: <dd><dl>
1.154 rillig 864: <dt><span class="sect2"><a href="#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
865: <dt><span class="sect2"><a href="#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
1.202 nia 866: <dt><span class="sect2"><a href="#using.pkgin_update">5.1.3. Updating packages</a></span></dt>
867: <dt><span class="sect2"><a href="#using.pkg_delete">5.1.4. Deinstalling packages</a></span></dt>
868: <dt><span class="sect2"><a href="#using.pkg_info">5.1.5. Getting information about installed packages</a></span></dt>
869: <dt><span class="sect2"><a href="#vulnerabilities">5.1.6. Checking for security vulnerabilities in installed packages</a></span></dt>
870: <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>
871: <dt><span class="sect2"><a href="#using.pkg_admin">5.1.8. Other administrative functions</a></span></dt>
1.1 dsieger 872: </dl></dd>
1.154 rillig 873: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.1 dsieger 874: <dd><dl>
1.154 rillig 875: <dt><span class="sect2"><a href="#requirements">5.2.1. Requirements</a></span></dt>
876: <dt><span class="sect2"><a href="#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
877: <dt><span class="sect2"><a href="#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.1 dsieger 878: </dl></dd>
879: </dl></dd>
1.154 rillig 880: <dt><span class="chapter"><a href="#configuring">6. Configuring pkgsrc</a></span></dt>
1.1 dsieger 881: <dd><dl>
1.154 rillig 882: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
883: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
1.241 rillig 884: <dt><span class="sect1"><a href="#native-or-pkgsrc-preference">6.3. Preferences for native or pkgsrc software</a></span></dt>
885: <dt><span class="sect1"><a href="#variables-affecting-installation">6.4. Variables affecting the installation process</a></span></dt>
886: <dt><span class="sect1"><a href="#conf.compiler">6.5. Selecting and configuring the compiler</a></span></dt>
887: <dd><dl>
888: <dt><span class="sect2"><a href="#selecting-the-compiler">6.5.1. Selecting the compiler</a></span></dt>
889: <dt><span class="sect2"><a href="#conf.cflags">6.5.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
890: <dt><span class="sect2"><a href="#conf.ldflags">6.5.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 891: </dl></dd>
1.241 rillig 892: <dt><span class="sect1"><a href="#developer-advanced-settings">6.6. Developer/advanced settings</a></span></dt>
893: <dt><span class="sect1"><a href="#selecting-build-options">6.7. Selecting Build Options</a></span></dt>
1.1 dsieger 894: </dl></dd>
1.154 rillig 895: <dt><span class="chapter"><a href="#binary">7. Creating binary packages</a></span></dt>
1.1 dsieger 896: <dd><dl>
1.154 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.6 rillig 899: </dl></dd>
1.154 rillig 900: <dt><span class="chapter"><a href="#bulk">8. Creating binary packages for everything in pkgsrc (bulk
1.6 rillig 901: builds)</a></span></dt>
1.1 dsieger 902: <dd><dl>
1.154 rillig 903: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.180 rillig 904: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.154 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.178 rillig 907: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
908: <dd><dl>
1.179 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.181 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.178 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.154 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.23 wiz 940: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.154 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.221 nia 942: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.154 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.1 dsieger 948: </dl></dd>
949: </dl>
950: </div>
1.41 asau 951: <div class="chapter">
1.1 dsieger 952: <div class="titlepage"><div><div><h2 class="title">
1.154 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.207 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.154 rillig 969: </li>
970: <li class="listitem"><p>
1.163 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.154 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.1 dsieger 997: <div class="toc">
998: <p><b>Table of Contents</b></p>
1.100 leot 999: <dl class="toc">
1.154 rillig 1000: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.1 dsieger 1001: <dd><dl>
1.154 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.1 dsieger 1004: </dl></dd>
1.154 rillig 1005: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.1 dsieger 1006: <dd><dl>
1.154 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.1 dsieger 1009: </dl></dd>
1010: </dl>
1011: </div>
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.41 asau 1020: <div class="sect1">
1.1 dsieger 1021: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1022: <a name="getting-first"></a>3.1. Getting pkgsrc for the first time</h2></div></div></div>
1.1 dsieger 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.246 leot 1029: <code class="literal">2023Q3</code>.</p>
1.1 dsieger 1030: <p>The second step is to decide <span class="emphasis"><em>how</em></span> you
1.23 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.51 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.41 asau 1035: <div class="sect2">
1.1 dsieger 1036: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1037: <a name="getting-via-tar"></a>3.1.1. As tar archive</h3></div></div></div>
1.1 dsieger 1038: <p>The primary download location for all pkgsrc files is
1.151 sevan 1039: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/" target="_top">https://cdn.NetBSD.org/pub/pkgsrc/</a> or
1.51 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.207 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.51 asau 1044: <p>The tar archive for the current branch is in the directory
1.151 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.118 sevan 1046: It is autogenerated weekly.</p>
1.51 asau 1047: <p>To save download time we provide bzip2- and
1048: xz-compressed archives which are published at
1.151 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.51 asau 1050: and
1.151 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.51 asau 1052: respectively.
1053: </p>
1054: <p>You can fetch the same files using FTP.</p>
1.246 leot 1055: <p>The tar file for the stable branch 2023Q3 is in the
1056: directory <code class="filename">pkgsrc-2023Q3</code> and is also called <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/pkgsrc-2023Q3/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p>
1.136 leot 1057: <p>To download the latest pkgsrc stable tarball, run:</p>
1.12 weinem 1058: <pre class="screen">
1.246 leot 1059: <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2023Q3/pkgsrc.tar.gz</code></strong></pre>
1.78 snj 1060: <p>If you prefer, you can also fetch it using "wget", "curl",
1.51 asau 1061: or your web browser.</p>
1.12 weinem 1062: <p>Then, extract it with:</p>
1.78 snj 1063: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre>
1.12 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.1 dsieger 1069: </div>
1.41 asau 1070: <div class="sect2">
1.1 dsieger 1071: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1072: <a name="getting-via-cvs"></a>3.1.2. Via anonymous CVS</h3></div></div></div>
1.23 wiz 1073: <p>To fetch a specific pkgsrc stable branch, run:</p>
1.246 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-2023Q3 -P pkgsrc</code></strong>
1.23 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.39 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 dsieger 1081: </pre>
1.174 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.23 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.39 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.23 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.2 rillig 1099: <pre class="programlisting">
1100: # recommended CVS configuration file from the pkgsrc guide
1.155 sevan 1101: cvs -q
1.2 rillig 1102: checkout -P
1.4 rillig 1103: update -dP
1104: diff -upN
1.2 rillig 1105: rdiff -u
1.23 wiz 1106: release -d
1.2 rillig 1107: </pre>
1.1 dsieger 1108: </div>
1109: </div>
1.41 asau 1110: <div class="sect1">
1.1 dsieger 1111: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1112: <a name="uptodate"></a>3.2. Keeping pkgsrc up-to-date</h2></div></div></div>
1.1 dsieger 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.41 asau 1117: <div class="sect2">
1.1 dsieger 1118: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1119: <a name="uptodate-tar"></a>3.2.1. Via tar files</h3></div></div></div>
1.41 asau 1120: <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1121: <h3 class="title">Warning</h3>
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>
1129: </div>
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.78 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.1 dsieger 1134: <code class="varname">DISTDIR</code> and <code class="varname">PACKAGES</code>
1.154 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.1 dsieger 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.41 asau 1141: <div class="sect2">
1.1 dsieger 1142: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1143: <a name="uptodate-cvs"></a>3.2.2. Via CVS</h3></div></div></div>
1.25 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.41 asau 1150: <div class="sect3">
1.1 dsieger 1151: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 1152: <a name="uptodate-cvs-switch"></a>3.2.2.1. Switching between different pkgsrc branches</h4></div></div></div>
1.1 dsieger 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.23 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.1 dsieger 1158: back to the stable branch, add the
1.246 leot 1159: <span class="quote">“<span class="quote">-rpkgsrc-2023Q3</span>”</span> option.</p>
1.1 dsieger 1160: </div>
1.41 asau 1161: <div class="sect3">
1.1 dsieger 1162: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 1163: <a name="uptodate-cvs-changes"></a>3.2.2.2. What happens to my changes when updating?</h4></div></div></div>
1.1 dsieger 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.23 wiz 1170: <span class="quote">“<span class="quote">update</span>”</span> for details.</p>
1.1 dsieger 1171: </div>
1172: </div>
1173: </div>
1174: </div>
1.41 asau 1175: <div class="chapter">
1.1 dsieger 1176: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 1177: <a name="platforms"></a>Chapter 4. Using pkgsrc on systems other than NetBSD</h2></div></div></div>
1.1 dsieger 1178: <div class="toc">
1179: <p><b>Table of Contents</b></p>
1.100 leot 1180: <dl class="toc">
1.154 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.1 dsieger 1183: </dl>
1184: </div>
1.41 asau 1185: <div class="sect1">
1.1 dsieger 1186: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 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.1 dsieger 1189: </div>
1.41 asau 1190: <div class="sect1">
1.1 dsieger 1191: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1192: <a name="bootstrapping-pkgsrc"></a>4.2. Bootstrapping pkgsrc</h2></div></div></div>
1.43 asau 1193: <p>pkgsrc can be bootstrapped for use in two different modes:
1194: privileged and unprivileged one. In unprivileged mode in contrast
1.44 asau 1195: to privileged one all programs are installed under one particular user
1.43 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.1 dsieger 1199: <p>Installing the bootstrap kit from source should be as simple as:</p>
1200: <pre class="screen">
1.60 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.1 dsieger 1202: <code class="prompt">#</code> <strong class="userinput"><code>cd pkgsrc/bootstrap</code></strong>
1203: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap</code></strong>
1204: </pre>
1.43 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.118 sevan 1209: and <code class="filename">/usr/pkg/pkgdb</code> for the package database
1.43 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.118 sevan 1215: <code class="filename">~/pkg/pkgdb</code> for the package database,
1.43 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.41 asau 1221: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1222: <h3 class="title">Note</h3>
1.10 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.23 wiz 1226: instead of <span class="quote">“<span class="quote">make</span>”</span>.</p>
1.1 dsieger 1227: </div>
1.43 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.1 dsieger 1236: </div>
1237: </div>
1.41 asau 1238: <div class="chapter">
1.1 dsieger 1239: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 1240: <a name="using"></a>Chapter 5. Using pkgsrc</h2></div></div></div>
1.1 dsieger 1241: <div class="toc">
1242: <p><b>Table of Contents</b></p>
1.100 leot 1243: <dl class="toc">
1.154 rillig 1244: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.1 dsieger 1245: <dd><dl>
1.154 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.202 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.154 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.1 dsieger 1260: </dl></dd>
1261: </dl>
1262: </div>
1263: <p>Basically, there are two ways of using pkgsrc. The first
1264: is to only install the package tools and to use binary packages
1.23 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.1 dsieger 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.41 asau 1269: <div class="sect1">
1.1 dsieger 1270: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1271: <a name="using-pkg"></a>5.1. Using binary packages</h2></div></div></div>
1.202 nia 1272: <p>On the <a class="ulink" href="https://cdn.NetBSD.org/" target="_top">cdn.NetBSD.org</a>
1.151 sevan 1273: site and mirrors, there are collections of binary packages,
1.9 rillig 1274: ready to be installed. These binary packages have been built using the
1275: default settings for the directories, that is:</p>
1.41 asau 1276: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 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.9 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.154 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.41 asau 1284: <div class="sect2">
1.1 dsieger 1285: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1286: <a name="finding-binary-packages"></a>5.1.1. Finding binary packages</h3></div></div></div>
1.5 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.202 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.5 weinem 1290: <p>This directory contains binary packages for multiple
1.226 gutterid 1291: platforms. First, select your operating system. Then, select your
1292: hardware architecture, and in the third step, the OS version and
1293: the <span class="quote">“<span class="quote">version</span>”</span> of pkgsrc.</p>
1294: <p>In this directory, you may find a file called
1.9 rillig 1295: <code class="filename">bootstrap.tar.gz</code> which contains the package
1296: management tools. If the file is missing, it is likely that your
1297: operating system already provides those tools. Download the file and
1298: extract it in the <code class="filename">/</code> directory. It will create
1299: the directories <code class="filename">/usr/pkg</code> (containing the tools
1.118 sevan 1300: for managing binary packages and the database of installed packages).</p>
1.1 dsieger 1301: </div>
1.41 asau 1302: <div class="sect2">
1.1 dsieger 1303: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1304: <a name="installing-binary-packages"></a>5.1.2. Installing binary packages</h3></div></div></div>
1.9 rillig 1305: <p>In the directory from the last section, there is a
1.85 wiz 1306: subdirectory called <code class="filename">All/</code>, which contains all the
1.9 rillig 1307: binary packages that are available for the platform, excluding those
1.202 nia 1308: that may not be distributed via HTTP or FTP.</p>
1.9 rillig 1309: <p>To install packages directly from an FTP or HTTP server, run
1310: the following commands in a Bourne-compatible shell (be sure to
1.10 hubertf 1311: <span class="command"><strong>su</strong></span> to root first):</p>
1.9 rillig 1312: <pre class="screen">
1.202 nia 1313: <code class="prompt">#</code> <strong class="userinput"><code>PATH="/usr/pkg/sbin:/usr/pkg/bin:$PATH"</code></strong>
1314: <code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="https://cdn.NetBSD.org/pub/pkgsrc/packages"</code></strong>
1.169 rillig 1315: <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.9 rillig 1316: <code class="prompt">#</code> <strong class="userinput"><code>export PATH PKG_PATH</code></strong>
1.202 nia 1317: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add pkgin</code></strong>
1.9 rillig 1318: </pre>
1319: <p>Instead of URLs, you can also use local paths, for example if
1320: you are installing from a set of CDROMs, DVDs or an NFS-mounted
1321: repository. If you want to install packages from multiple sources,
1322: you can separate them by a semicolon in
1323: <code class="varname">PKG_PATH</code>.</p>
1324: <p>After these preparations, installing a package is very
1325: easy:</p>
1326: <pre class="screen">
1.202 nia 1327: <code class="prompt">#</code> <strong class="userinput"><code>pkgin search nginx</code></strong>
1328: nginx-1.19.6 Lightweight HTTP server and mail proxy server
1329: nginx-1.18.0nb8 Lightweight HTTP server and mail proxy server
1330: <code class="prompt">#</code> <strong class="userinput"><code>pkgin install zsh nginx-1.19.6 vim</code></strong>
1331: </pre>
1332: <p>Note that <span class="command"><strong>pkgin</strong></span> is a user-friendly frontend
1333: to the <span class="command"><strong>pkg_*</strong></span> tools.</p>
1334: <p>Any prerequisite packages needed to run the
1.1 dsieger 1335: package in question will be installed, too, assuming they are
1.202 nia 1336: present in the repository.</p>
1.1 dsieger 1337: <p>After you've installed packages, be sure to have
1338: <code class="filename">/usr/pkg/bin</code> and <code class="filename">/usr/pkg/sbin</code> in your
1339: <code class="varname">PATH</code> so you can actually start the just
1340: installed program.</p>
1341: </div>
1.41 asau 1342: <div class="sect2">
1.1 dsieger 1343: <div class="titlepage"><div><div><h3 class="title">
1.202 nia 1344: <a name="using.pkgin_update"></a>5.1.3. Updating packages</h3></div></div></div>
1345: <p>To update binary packages, it is recommended that you use
1346: <span class="command"><strong>pkgin upgrade</strong></span>. This will compare the remote
1347: package repository to your locally installed packages and safely
1348: replace any older packages.</p>
1349: <p>Note that pkgsrc is released as quarterly branches.
1350: If you are updating to a newer quarterly branch of pkgsrc, you may
1351: need to adjust the repository in
1352: <code class="filename">/usr/pkg/etc/pkgin/repositories.conf</code>.</p>
1353: </div>
1354: <div class="sect2">
1355: <div class="titlepage"><div><div><h3 class="title">
1356: <a name="using.pkg_delete"></a>5.1.4. Deinstalling packages</h3></div></div></div>
1.1 dsieger 1357: <p>To deinstall a package, it does not matter whether it was
1.202 nia 1358: installed from source code or from a binary package. Neither the
1359: <span class="command"><strong>pkgin</strong></span> or the <span class="command"><strong>pkg_delete</strong></span>
1360: command need to know.</p>
1361: <p>To delete a package, you can just run <span class="command"><strong>pkgin remove
1.1 dsieger 1362: <em class="replaceable"><code>package-name</code></em></strong></span>. The package
1.202 nia 1363: name can be given with or without version number.</p>
1.1 dsieger 1364: </div>
1.41 asau 1365: <div class="sect2">
1.1 dsieger 1366: <div class="titlepage"><div><div><h3 class="title">
1.202 nia 1367: <a name="using.pkg_info"></a>5.1.5. Getting information about installed packages</h3></div></div></div>
1.10 hubertf 1368: <p>The <span class="command"><strong>pkg_info</strong></span> shows information about
1.202 nia 1369: installed packages or binary package files.
1370: As with other management tools, it works with packages installed
1371: from source or binaries.</p>
1.1 dsieger 1372: </div>
1.41 asau 1373: <div class="sect2">
1.1 dsieger 1374: <div class="titlepage"><div><div><h3 class="title">
1.202 nia 1375: <a name="vulnerabilities"></a>5.1.6. Checking for security vulnerabilities in installed packages</h3></div></div></div>
1.1 dsieger 1376: <p>
1.164 leot 1377: The pkgsrc Security Team and Packages Groups maintain a list of
1.202 nia 1378: known vulnerabilities to packages which are (or have been)
1.1 dsieger 1379: included in pkgsrc. The list is available from the NetBSD
1.202 nia 1380: 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>.
1381: </p>
1382: <p>
1383: Please note that not every "vulnerability" with a CVE assignment is
1384: exploitable in every configuration.
1385: Some bugs are marked as active simply because an fix was not
1386: marked as such.
1387: Operating system specific hardening and mitigation features may also
1388: reduce the impact of bugs.
1.1 dsieger 1389: </p>
1390: <p>
1.22 jakllsch 1391: Through <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1.1 dsieger 1392: this list can be downloaded
1393: automatically, and a security audit of all packages installed on a system
1394: can take place.
1395: </p>
1396: <p>
1.22 jakllsch 1397: There are two components to auditing. The first
1398: step, <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1399: is for downloading
1.1 dsieger 1400: the list of vulnerabilities from the NetBSD FTP site. The second
1.22 jakllsch 1401: step, <span class="command"><strong>pkg_admin audit</strong></span>, checks to see if any of your
1.1 dsieger 1402: installed packages are vulnerable. If a package is vulnerable, you
1403: will see output similar to the following:
1404: </p>
1405: <pre class="screen">Package samba-2.0.9 has a local-root-shell vulnerability, see
1.174 leot 1406: https://www.samba.org/samba/whatsnew/macroexploit.html</pre>
1.1 dsieger 1407: <p>
1.22 jakllsch 1408: You may wish to have the
1.202 nia 1409: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities" target="_top">vulnerabilities</a>
1.22 jakllsch 1410: file downloaded daily so that
1411: it remains current. This may be done by adding an appropriate entry
1.246 leot 1412: to the root users <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/crontab.5"><span class="citerefentry"><span class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
1.22 jakllsch 1413: </p>
1414: <pre class="screen">
1.121 sevan 1415: # Download vulnerabilities file
1.118 sevan 1416: 0 3 * * * /usr/pkg/sbin/pkg_admin fetch-pkg-vulnerabilities >/dev/null 2>&1
1.121 sevan 1417: # Audit the installed packages and email results to root
1418: 9 3 * * * /usr/pkg/sbin/pkg_admin audit |mail -s "Installed package audit result" \
1419: root >/dev/null 2>&1
1.22 jakllsch 1420: </pre>
1421: <p>
1.118 sevan 1422: will update the vulnerability list every day at 3AM, followed by an audit
1423: at 3:09AM. The result of the audit are then emailed to root.
1.22 jakllsch 1424:
1.118 sevan 1425: On NetBSD this may be accomplished instead by adding the following
1426: line to <code class="filename">/etc/daily.conf</code>:
1427: </p>
1428: <pre class="screen">
1429: fetch_pkg_vulnerabilities=YES
1430: </pre>
1431: <p>
1432: to fetch the vulnerability list from the daily security script. The system
1433: is set to audit the packages by default but can be set explicitly, if
1.123 wiz 1434: desired (not required), by adding the following line to
1.118 sevan 1435: <code class="filename">/etc/security.conf</code>:
1.22 jakllsch 1436: </p>
1437: <pre class="screen">
1.118 sevan 1438: check_pkg_vulnerabilities=YES
1.22 jakllsch 1439: </pre>
1440: <p>
1.246 leot 1441: see <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/daily.conf.5"><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a> and <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/security.conf.5"><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for more details.
1.1 dsieger 1442: </p>
1443: </div>
1.41 asau 1444: <div class="sect2">
1.1 dsieger 1445: <div class="titlepage"><div><div><h3 class="title">
1.202 nia 1446: <a name="pkg_versions"></a>5.1.7. Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div>
1.1 dsieger 1447: <p>
1.207 leot 1448: 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.23 wiz 1449: <span class="command"><strong>lintpkgsrc</strong></span> with the <span class="quote">“<span class="quote">-i</span>”</span>
1.202 nia 1450: argument to check if any packages are stale, e.g.
1.1 dsieger 1451: </p>
1452: <pre class="screen">
1453: <code class="prompt">%</code> <strong class="userinput"><code>lintpkgsrc -i</code></strong>
1454: ...
1455: Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
1456: </pre>
1457: </div>
1.41 asau 1458: <div class="sect2">
1.1 dsieger 1459: <div class="titlepage"><div><div><h3 class="title">
1.202 nia 1460: <a name="using.pkg_admin"></a>5.1.8. Other administrative functions</h3></div></div></div>
1.10 hubertf 1461: <p>The <span class="command"><strong>pkg_admin</strong></span> executes various
1.1 dsieger 1462: administrative functions on the package system.</p>
1463: </div>
1464: </div>
1.41 asau 1465: <div class="sect1">
1.1 dsieger 1466: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1467: <a name="building-packages-from-source"></a>5.2. Building packages from source</h2></div></div></div>
1.1 dsieger 1468: <p>After obtaining pkgsrc, the <code class="filename">pkgsrc</code>
1469: directory now contains a set of packages, organized into
1470: categories. You can browse the online index of packages, or run
1.10 hubertf 1471: <span class="command"><strong>make readme</strong></span> from the <code class="filename">pkgsrc</code>
1.1 dsieger 1472: directory to build local <code class="filename">README.html</code> files for
1.207 leot 1473: 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.1 dsieger 1474: <p>The default <span class="emphasis"><em>prefix</em></span> for installed packages
1475: is <code class="filename">/usr/pkg</code>. If you wish to change this, you
1476: should do so by setting <code class="varname">LOCALBASE</code> in
1.10 hubertf 1477: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. You should not try to use multiple
1.1 dsieger 1478: different <code class="varname">LOCALBASE</code> definitions on the same
1479: system (inside a chroot is an exception). </p>
1480: <p>The rest of this chapter assumes that the package is already
1.10 hubertf 1481: 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.1 dsieger 1482: instructions how to create your own packages.</p>
1.41 asau 1483: <div class="sect2">
1.1 dsieger 1484: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1485: <a name="requirements"></a>5.2.1. Requirements</h3></div></div></div>
1.1 dsieger 1486: <p>To build packages from source, you need a working C
1487: compiler. On NetBSD, you need to install the
1.23 wiz 1488: <span class="quote">“<span class="quote">comp</span>”</span> and the <span class="quote">“<span class="quote">text</span>”</span> distribution
1.1 dsieger 1489: sets. If you want to build X11-related packages, the
1.23 wiz 1490: <span class="quote">“<span class="quote">xbase</span>”</span> and <span class="quote">“<span class="quote">xcomp</span>”</span> distribution
1.1 dsieger 1491: sets are required, too.</p>
1492: </div>
1.41 asau 1493: <div class="sect2">
1.1 dsieger 1494: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1495: <a name="fetching-distfiles"></a>5.2.2. Fetching distfiles</h3></div></div></div>
1.1 dsieger 1496: <p>The first step for building a package is downloading the
1497: distfiles (i.e. the unmodified source). If they have not yet been
1498: downloaded, pkgsrc will fetch them automatically.</p>
1499: <p>If you have all files that you need in the
1500: <code class="filename">distfiles</code> directory,
1501: you don't need to connect. If the distfiles are on CD-ROM, you can
1502: mount the CD-ROM on <code class="filename">/cdrom</code> and add:
1503: </p>
1504: <pre class="screen">DISTDIR=/cdrom/pkgsrc/distfiles</pre>
1505: <p>
1.10 hubertf 1506: to your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 1507: <p>By default a list of distribution sites will be randomly
1508: intermixed to prevent huge load on servers which holding popular
1509: packages (for example, SourceForge.net mirrors). Thus, every
1510: time when you need to fetch yet another distfile all the mirrors
1511: will be tried in new (random) order. You can turn this feature
1512: off by setting <code class="varname">MASTER_SORT_RANDOM=NO</code> (for
1513: <code class="varname">PKG_DEVELOPER</code>s it's already disabled).</p>
1514: <p>You can overwrite some of the major distribution sites to
1515: fit to sites that are close to your own. By setting one or two
1516: variables you can modify the order in which the master sites are
1517: accessed. <code class="varname">MASTER_SORT</code> contains a whitespace
1518: delimited list of domain suffixes.
1519: <code class="varname">MASTER_SORT_REGEX</code> is even more flexible, it
1520: contains a whitespace delimited list of regular expressions. It
1521: has higher priority than <code class="varname">MASTER_SORT</code>. Have a
1522: look at <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to find
1523: some examples. This may save some of your bandwidth and
1524: time.</p>
1525: <p>You can change these settings either in your shell's environment, or,
1526: if you want to keep the settings, by editing the
1.10 hubertf 1527: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file,
1.1 dsieger 1528: and adding the definitions there.</p>
1529: <p>
1530: If a package depends on many other packages (such as
1.207 leot 1531: <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.1 dsieger 1532: alternate between periods of
1533: downloading source, and compiling. To ensure you have all the source
1534: downloaded initially you can run the command:
1535: </p>
1536: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch-list | sh</code></strong></pre>
1537: <p>
1538: which will output and run a set of shell commands to fetch the
1539: necessary files into the <code class="filename">distfiles</code> directory. You can
1540: also choose to download the files manually.
1541: </p>
1542: </div>
1.41 asau 1543: <div class="sect2">
1.1 dsieger 1544: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1545: <a name="how-to-build-and-install"></a>5.2.3. How to build and install</h3></div></div></div>
1.1 dsieger 1546: <p>
1547: Once the software has downloaded, any patches will be applied, then it
1548: will be compiled for you. This may take some time depending on your
1549: computer, and how many other packages the software depends on and their
1550: compile time.
1551: </p>
1.41 asau 1552: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1553: <h3 class="title">Note</h3>
1554: <p>If using bootstrap or pkgsrc on a non-NetBSD system,
1.10 hubertf 1555: use the pkgsrc <span class="command"><strong>bmake</strong></span> command instead of
1.23 wiz 1556: <span class="quote">“<span class="quote">make</span>”</span> in the examples in this guide.</p>
1.1 dsieger 1557: </div>
1558: <p>For example, type</p>
1559: <pre class="screen">
1560: <code class="prompt">%</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
1561: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
1562: </pre>
1563: <p>at the shell prompt to build the various components of the
1564: package.</p>
1565: <p>The next stage is to actually install the newly compiled
1566: program onto your system. Do this by entering:
1567:
1568: </p>
1569: <pre class="screen">
1570: <code class="prompt">%</code> <strong class="userinput"><code>make install</code></strong>
1571: </pre>
1572: <p>
1573:
1574: while you are still in the directory for whatever package you
1575: are installing.</p>
1576: <p>Installing the package on your system may require you to
1577: be root. However, pkgsrc has a
1578: <span class="emphasis"><em>just-in-time-su</em></span> feature, which allows you
1579: to only become root for the actual installation step.</p>
1580: <p>That's it, the software should now be installed and setup for use.
1581: You can now enter:
1582:
1583: </p>
1584: <pre class="screen">
1585: <code class="prompt">%</code> <strong class="userinput"><code>make clean</code></strong>
1586: </pre>
1587: <p>
1588:
1589: to remove the compiled files in the work directory, as you shouldn't need
1590: them any more. If other packages were also added to your system
1591: (dependencies) to allow your program to compile, you can tidy these up
1592: also with the command:</p>
1593: <pre class="screen">
1594: <code class="prompt">%</code> <strong class="userinput"><code>make clean-depends</code></strong>
1595: </pre>
1596: <p>Taking the figlet utility as an example, we can install it on our
1.207 leot 1597: 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.1 dsieger 1598: <p>The program is installed under the default root of the
1599: packages tree - <code class="filename">/usr/pkg</code>. Should this not
1600: conform to your tastes, set the <code class="varname">LOCALBASE</code>
1601: variable in your environment, and it will use that value as the
1602: root of your packages tree. So, to use
1603: <code class="filename">/usr/local</code>, set
1604: <code class="varname">LOCALBASE=/usr/local</code> in your environment.
1605: Please note that you should use a directory which is dedicated to
1606: packages and not shared with other programs (i.e., do not try and
1607: use <code class="varname">LOCALBASE=/usr</code>). Also, you should not try
1608: to add any of your own files or directories (such as
1609: <code class="filename">src/</code>, <code class="filename">obj/</code>, or
1610: <code class="filename">pkgsrc/</code>) below the
1611: <code class="varname">LOCALBASE</code> tree. This is to prevent possible
1612: conflicts between programs and other files installed by the
1613: package system and whatever else may have been installed
1614: there.</p>
1.10 hubertf 1615: <p>Some packages look in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.1 dsieger 1616: alter some configuration options at build time. Have a look at
1617: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to get an overview
1618: of what will be set there by default. Environment variables such
1619: as <code class="varname">LOCALBASE</code> can be set in
1.10 hubertf 1620: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to save having to remember to
1.1 dsieger 1621: set them each time you want to use pkgsrc.</p>
1.23 wiz 1622: <p>Occasionally, people want to <span class="quote">“<span class="quote">look under the
1623: covers</span>”</span> to see what is going on when a package is building
1.1 dsieger 1624: or being installed. This may be for debugging purposes, or out of
1625: simple curiosity. A number of utility values have been added to
1626: help with this.</p>
1.23 wiz 1627: <div class="orderedlist"><ol class="orderedlist" type="1">
1628: <li class="listitem">
1.246 leot 1629: <p>If you invoke the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> command with
1.1 dsieger 1630: <code class="varname">PKG_DEBUG_LEVEL=2</code>, then a huge amount of
1631: information will be displayed. For example,</p>
1632: <pre class="screen"><strong class="userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong></pre>
1633: <p>will show all the commands that are invoked, up to and
1.23 wiz 1634: including the <span class="quote">“<span class="quote">patch</span>”</span> stage.</p>
1.1 dsieger 1635: </li>
1.23 wiz 1636: <li class="listitem">
1.246 leot 1637: <p>If you want to know the value of a certain <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 1638: definition, then the <code class="varname">VARNAME</code> definition
1639: should be used, in conjunction with the show-var
1.246 leot 1640: target. e.g. to show the expansion of the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 1641: variable <code class="varname">LOCALBASE</code>:</p>
1642: <pre class="screen">
1643: <code class="prompt">%</code> <strong class="userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
1644: /usr/pkg
1645: <code class="prompt">%</code>
1646: </pre>
1647: </li>
1648: </ol></div>
1649: <p>If you want to install a binary package that you've either
1650: created yourself (see next section), that you put into
1651: pkgsrc/packages manually or that is located on a remote FTP
1652: server, you can use the "bin-install" target. This target will
1.246 leot 1653: install a binary package - if available - via <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>,
1.10 hubertf 1654: else do a <span class="command"><strong>make package</strong></span>. The list of remote FTP
1.1 dsieger 1655: sites searched is kept in the variable
1656: <code class="varname">BINPKG_SITES</code>, which defaults to
1.246 leot 1657: ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>
1.1 dsieger 1658: can be put into <code class="varname">BIN_INSTALL_FLAGS</code>. See
1659: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more
1660: details.</p>
1661: <p>A final word of warning: If you set up a system that has a
1662: non-standard setting for <code class="varname">LOCALBASE</code>, be sure to
1663: set that before any packages are installed, as you cannot use
1664: several directories for the same purpose. Doing so will result in
1665: pkgsrc not being able to properly detect your installed packages,
1666: and fail miserably. Note also that precompiled binary packages are
1667: usually built with the default <code class="varname">LOCALBASE</code> of
1668: <code class="filename">/usr/pkg</code>, and that you should
1669: <span class="emphasis"><em>not</em></span> install any if you use a non-standard
1670: <code class="varname">LOCALBASE</code>.</p>
1671: </div>
1672: </div>
1673: </div>
1.41 asau 1674: <div class="chapter">
1.1 dsieger 1675: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 1676: <a name="configuring"></a>Chapter 6. Configuring pkgsrc</h2></div></div></div>
1.1 dsieger 1677: <div class="toc">
1678: <p><b>Table of Contents</b></p>
1.100 leot 1679: <dl class="toc">
1.154 rillig 1680: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
1681: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
1.241 rillig 1682: <dt><span class="sect1"><a href="#native-or-pkgsrc-preference">6.3. Preferences for native or pkgsrc software</a></span></dt>
1683: <dt><span class="sect1"><a href="#variables-affecting-installation">6.4. Variables affecting the installation process</a></span></dt>
1684: <dt><span class="sect1"><a href="#conf.compiler">6.5. Selecting and configuring the compiler</a></span></dt>
1685: <dd><dl>
1686: <dt><span class="sect2"><a href="#selecting-the-compiler">6.5.1. Selecting the compiler</a></span></dt>
1687: <dt><span class="sect2"><a href="#conf.cflags">6.5.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
1688: <dt><span class="sect2"><a href="#conf.ldflags">6.5.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 1689: </dl></dd>
1.241 rillig 1690: <dt><span class="sect1"><a href="#developer-advanced-settings">6.6. Developer/advanced settings</a></span></dt>
1691: <dt><span class="sect1"><a href="#selecting-build-options">6.7. Selecting Build Options</a></span></dt>
1.1 dsieger 1692: </dl>
1693: </div>
1.4 rillig 1694: <a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
1.1 dsieger 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.246 leot 1697: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it is in the directory
1.1 dsieger 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.112 rillig 1705: spelling mistakes) takes place.</p>
1.41 asau 1706: <div class="sect1">
1.1 dsieger 1707: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1708: <a name="general-configuration"></a>6.1. General configuration</h2></div></div></div>
1.112 rillig 1709: <p>The following variables apply to all
1.1 dsieger 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.41 asau 1714: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1715: <li class="listitem"><p><code class="varname">LOCALBASE</code>: Where
1.1 dsieger 1716: packages will be installed. The default is
1717: <code class="filename">/usr/pkg</code>. Do not mix binary packages
1718: with different <code class="varname">LOCALBASE</code>s!</p></li>
1.23 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.1 dsieger 1721: installed. The default is
1722: <code class="filename">${LOCALBASE}/cross</code>.</p></li>
1.23 wiz 1723: <li class="listitem"><p><code class="varname">X11BASE</code>: Where
1.1 dsieger 1724: X11 is installed on the system. The default is
1.84 wiz 1725: <code class="filename">/usr/X11R7</code>.</p></li>
1.23 wiz 1726: <li class="listitem"><p><code class="varname">DISTDIR</code>: Where to store the
1.1 dsieger 1727: downloaded copies of the original source distributions used
1728: for building pkgsrc packages. The default is
1729: <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li>
1.23 wiz 1730: <li class="listitem"><p><code class="varname">PKG_DBDIR</code>: Where the
1.1 dsieger 1731: database about installed packages is stored. The default is
1.118 sevan 1732: <code class="filename">/usr/pkg/pkgdb</code>.</p></li>
1.23 wiz 1733: <li class="listitem"><p><code class="varname">MASTER_SITE_OVERRIDE</code>:
1.1 dsieger 1734: If set, override the packages'
1735: <code class="varname">MASTER_SITES</code> with this value.</p></li>
1.23 wiz 1736: <li class="listitem"><p><code class="varname">MASTER_SITE_BACKUP</code>:
1.1 dsieger 1737: Backup location(s) for distribution files and patch files
1738: if not found locally or in
1739: <code class="filename">${MASTER_SITES}</code> or
1740: <code class="filename">${PATCH_SITES}</code> respectively.
1.118 sevan 1741: The defaults is
1742: <code class="filename">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}/</code>.</p></li>
1.23 wiz 1743: <li class="listitem"><p><code class="varname">BINPKG_SITES</code>:
1.1 dsieger 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.23 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.22 jakllsch 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.1 dsieger 1754: </ul></div>
1755: </div>
1.41 asau 1756: <div class="sect1">
1.1 dsieger 1757: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1758: <a name="variables-affecting-build"></a>6.2. Variables affecting the build process</h2></div></div></div>
1.108 rillig 1759: <p>
1.1 dsieger 1760: </p>
1.41 asau 1761: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1762: <li class="listitem"><p><code class="varname">PACKAGES</code>: The top level
1.1 dsieger 1763: directory for the binary packages. The default is
1764: <code class="filename">${PKGSRCDIR}/packages</code>.</p></li>
1.23 wiz 1765: <li class="listitem"><p><code class="varname">WRKOBJDIR</code>:
1.1 dsieger 1766: The top level directory where, if defined, the separate
1767: working directories will get created, and symbolically
1768: linked to from <code class="filename">${WRKDIR}</code> (see below).
1769: This is useful for building packages on several
1770: architectures, then <code class="filename">${PKGSRCDIR}</code>
1771: can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code>
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.14 jmcneill 1774: — it is an internal definition which refers to the
1.1 dsieger 1775: root of the pkgsrc tree. It is possible to have many
1776: pkgsrc tree instances.)</p></li>
1.23 wiz 1777: <li class="listitem"><p><code class="varname">LOCALPATCHES</code>:
1.1 dsieger 1778: Directory for local patches that aren't part of pkgsrc.
1.184 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.1 dsieger 1780: information.</p></li>
1.23 wiz 1781: <li class="listitem"><p><code class="varname">PKGMAKECONF</code>: Location of
1.10 hubertf 1782: the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file used by a package's
1.1 dsieger 1783: BSD-style Makefile. If this is not set,
1784: <code class="varname">MAKECONF</code> is set to
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>
1787: </ul></div>
1788: </div>
1.41 asau 1789: <div class="sect1">
1.1 dsieger 1790: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.241 rillig 1791: <a name="native-or-pkgsrc-preference"></a>6.3. Preferences for native or pkgsrc software</h2></div></div></div>
1792: <p>Whenever a package depends on a package that has a
1793: <code class="filename">builtin.mk</code> file, the dependent package can
1794: either use the built-in (native) version from the base system or the
1795: pkgsrc-provided version. This only affects dependencies, so it is
1796: still possible to build the pkgsrc package <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/pcre++/index.html" target="_top"><code class="filename">devel/pcre++</code></a> even when other packages depend
1797: on the native pcre++ version instead.</p>
1798: <p>To force using the pkgsrc-provided version for a particular
1799: package, define <span class="quote">“<span class="quote"><code class="varname">PREFER_PKGSRC</code> =
1800: <em class="replaceable"><code>package-ID</code></em></span>”</span> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. To force
1801: using the native package, define
1802: <span class="quote">“<span class="quote"><code class="varname">PREFER_NATIVE</code> =
1803: <em class="replaceable"><code>package-ID</code></em></span>”</span>. In both cases, the
1804: <em class="replaceable"><code>package-ID</code></em> is the one from the
1805: <code class="filename">buildlink3.mk</code> of the package. In most cases,
1806: this ID is the same as the directory name of the package, but for
1807: example, <code class="filename">devel/pcre++</code> has the
1808: package ID <span class="quote">“<span class="quote">pcrexx</span>”</span>.</p>
1809: <p>For the packages that are not listed by their package ID,
1810: pkgsrc uses the pkgsrc-provided version if
1811: <code class="varname">PREFER_PKGSRC</code> contains the word
1812: <span class="quote">“<span class="quote">yes</span>”</span>. Otherwise, if <code class="varname">PREFER_NATIVE</code>
1813: contains the word <span class="quote">“<span class="quote">yes</span>”</span>, pkgsrc uses the native
1814: version. For example, to require using the pkgsrc-provided versions
1815: for all but the most basic bits on a NetBSD system, you can
1816: set:</p>
1817: <pre class="programlisting">
1818: PREFER_PKGSRC= yes
1819: PREFER_NATIVE= getopt skey tcp_wrappers
1820: </pre>
1821: <p>A package <span class="emphasis"><em>must</em></span> have a
1822: <code class="filename">builtin.mk</code> file to be listed in
1823: <code class="varname">PREFER_NATIVE</code>, otherwise it is simply ignored in
1824: that list.</p>
1825: <p><code class="varname">PREFER_PKGSRC</code> and
1826: <code class="varname">PREFER_NATIVE</code> should be set during bootstrap to
1827: ensure that the bootstrap process does not use inapropriate native
1828: tools as dependencies for core packages.</p>
1829: <pre class="screen">
1830: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap --prefer-pkgsrc yes --prefer-native openssl</code></strong>
1831: </pre>
1832: <p>Switching between settings globally at a later date can
1833: introduce complications with dependency resolution. This is caused
1834: by packages built with the opposite preference being installed
1835: alongside each other. Hence, when changing any of these variables
1836: after bootstrap, you need to rebuild all packages depending on those
1837: whose preference has been changed. This is not trivial and should
1838: be avoided.</p>
1839: <p>When using pkgsrc on Linux systems, there is high risk of
1840: <span class="quote">“<span class="quote">leakage</span>”</span>, where programs installed by pkgsrc may
1841: inadvertently use a command or library not installed by pkgsrc, e.g.
1842: those installed by yum or apt. Such foreign dependencies may be
1843: installed, removed, or upgraded to a version incompatible with the
1844: pkgsrc package at any time, causing pkgsrc packages to subsequently
1845: malfunction. Pkgsrc cannot prevent this, as it has no control over
1846: other package managers. Another potential problem is that under
1847: Redhat Enterprise and related Linux systems, yum packages are only
1848: patched and never upgraded, so eventually they may become too
1849: outdated for use by pkgsrc. Even intentionally using foreign
1850: dependencies, not considered leakage, can lead to these problems, so
1851: it is generally discouraged. In order to minimize such problems,
1852: PREFER_PKGSRC defaults to <span class="quote">“<span class="quote">yes</span>”</span> on Linux systems. This ensures that
1853: pkgsrc is aware of any changes to dependency packages and can
1854: rebuild or upgrade the entire dependency tree as needed. This
1855: default can be overridden by setting --prefer-pkgsrc to a
1856: list of packages and --prefer-native to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1857: </div>
1858: <div class="sect1">
1859: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1860: <a name="variables-affecting-installation"></a>6.4. Variables affecting the installation process</h2></div></div></div>
1.198 leot 1861: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><code class="varname">PKGSRC_KEEP_BIN_PKGS</code>:
1.143 maya 1862: By default, binary packages of built packages are
1.150 leot 1863: preserved in <code class="filename">${PACKAGES}/All</code>. Setting
1.143 maya 1864: this variable to "no" prevents this.</p></li></ul></div>
1.107 jnemeth 1865: <p>Packages have to support installation into a
1.4 rillig 1866: subdirectory of <code class="varname">WRKDIR</code>. This allows a package
1867: to be built, before the actual filesystem is touched. DESTDIR
1868: support exists in two variations:</p>
1.41 asau 1869: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1870: <li class="listitem"><p>Basic DESTDIR support means that the package
1.24 wiz 1871: installation and packaging is still run as root.</p></li>
1872: <li class="listitem"><p>Full DESTDIR support can run the complete
1873: build, installation and packaging as normal user. Root
1874: privileges are only needed to add packages.</p></li>
1875: </ul></div>
1.4 rillig 1876: <p>With basic DESTDIR support, <strong class="userinput"><code>make
1877: clean</code></strong> needs to be run as root.</p>
1.17 imil 1878: <p>Considering the <code class="filename">foo/bar</code> package,
1879: DESTDIR full support can be tested using the following commands
1880:
1881: </p>
1882: <pre class="programlisting">
1883: <code class="prompt">$</code> id
1884: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
1885: <code class="prompt">$</code> mkdir $HOME/packages
1886: <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
1887: </pre>
1888: <p>
1889:
1890: Verify <code class="varname">DESTDIR</code> full support, no root privileges
1891: should be needed
1892:
1893: </p>
1894: <pre class="programlisting">
1.66 asau 1895: <code class="prompt">$</code> make stage-install
1.17 imil 1896: </pre>
1897: <p>
1898:
1899: Create a package without root privileges
1900:
1901: </p>
1902: <pre class="programlisting">
1.66 asau 1903: <code class="prompt">$</code> make PACKAGES=$HOME/packages package
1.17 imil 1904: </pre>
1905: <p>
1906:
1907: For the following command, you must be able to gain root
1.246 leot 1908: privileges using <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/su.1"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
1.17 imil 1909:
1910: </p>
1911: <pre class="programlisting">
1.66 asau 1912: <code class="prompt">$</code> make PACKAGES=$HOME/packages install
1.17 imil 1913: </pre>
1914: <p>
1915:
1916: Then, as a simple user
1917:
1918: </p>
1919: <pre class="programlisting">
1920: <code class="prompt">$</code> make clean
1921: </pre>
1922: <p>
1923:
1924: </p>
1.4 rillig 1925: </div>
1.41 asau 1926: <div class="sect1">
1.4 rillig 1927: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.241 rillig 1928: <a name="conf.compiler"></a>6.5. Selecting and configuring the compiler</h2></div></div></div>
1.41 asau 1929: <div class="sect2">
1.1 dsieger 1930: <div class="titlepage"><div><div><h3 class="title">
1.241 rillig 1931: <a name="selecting-the-compiler"></a>6.5.1. Selecting the compiler</h3></div></div></div>
1.1 dsieger 1932: <p>By default, pkgsrc will use GCC to build packages. This may be
1933: overridden by setting the following variables in /etc/mk.conf:</p>
1.41 asau 1934: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 1935: <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
1936: <dd>
1937: <p>This is a list of values specifying the chain of
1938: compilers to invoke when building packages. Valid values
1939: are:</p>
1.41 asau 1940: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.66 asau 1941: <li class="listitem"><p><code class="varname">ccc</code>:
1942: Compaq C Compilers (Tru64)</p></li>
1943: <li class="listitem"><p><code class="varname">ccache</code>:
1944: compiler cache (chainable)</p></li>
1945: <li class="listitem"><p><code class="varname">clang</code>:
1946: Clang C and Objective-C compiler</p></li>
1.23 wiz 1947: <li class="listitem"><p><code class="varname">distcc</code>:
1.1 dsieger 1948: distributed C/C++ (chainable)</p></li>
1.66 asau 1949: <li class="listitem"><p><code class="varname">f2c</code>:
1950: Fortran 77 to C compiler (chainable)</p></li>
1951: <li class="listitem"><p><code class="varname">icc</code>:
1952: Intel C++ Compiler (Linux)</p></li>
1953: <li class="listitem"><p><code class="varname">ido</code>:
1954: SGI IRIS Development Option cc (IRIX 5)</p></li>
1.23 wiz 1955: <li class="listitem"><p><code class="varname">gcc</code>:
1.1 dsieger 1956: GNU C/C++ Compiler</p></li>
1.66 asau 1957: <li class="listitem"><p><code class="varname">hp</code>:
1958: HP-UX C/aC++ compilers</p></li>
1.23 wiz 1959: <li class="listitem"><p><code class="varname">mipspro</code>:
1.1 dsieger 1960: Silicon Graphics, Inc. MIPSpro (n32/n64)</p></li>
1.66 asau 1961: <li class="listitem"><p><code class="varname">mipspro-ucode</code>:
1.1 dsieger 1962: Silicon Graphics, Inc. MIPSpro (o32)</p></li>
1.23 wiz 1963: <li class="listitem"><p><code class="varname">sunpro</code>:
1.1 dsieger 1964: Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio</p></li>
1.66 asau 1965: <li class="listitem"><p><code class="varname">xlc</code>:
1.118 sevan 1966: IBM's XL C/C++ compiler suite</p></li>
1.1 dsieger 1967: </ul></div>
1968: <p>The default is
1.23 wiz 1969: <span class="quote">“<span class="quote"><code class="varname">gcc</code></span>”</span>. You can use
1.1 dsieger 1970: <code class="varname">ccache</code> and/or
1971: <code class="varname">distcc</code> with an appropriate
1972: <code class="varname">PKGSRC_COMPILER</code> setting,
1.23 wiz 1973: e.g. <span class="quote">“<span class="quote"><code class="varname">ccache gcc</code></span>”</span>. This
1.1 dsieger 1974: variable should always be terminated with a value for
1975: a real compiler. Note that only one real compiler
1.23 wiz 1976: should be listed (e.g. <span class="quote">“<span class="quote"><code class="varname">sunpro gcc</code></span>”</span>
1.1 dsieger 1977: is not allowed).</p>
1978: </dd>
1979: <dt><span class="term"><code class="varname">GCC_REQD</code>:</span></dt>
1980: <dd><p>This specifies the minimum version of GCC to use
1981: when building packages. If the system GCC doesn't
1982: satisfy this requirement, then pkgsrc will build and
1983: install one of the GCC packages to use instead.</p></dd>
1.153 leot 1984: <dt><span class="term"><code class="varname">PYTHON_VERSION_DEFAULT</code>:</span></dt>
1.114 maya 1985: <dd><p>Specifies which version of python to use when several
1986: options are available.</p></dd>
1987: <dt><span class="term"><code class="varname">PKGSRC_FORTRAN</code>:</span></dt>
1.176 gutterid 1988: <dd><p>Specifies the Fortran compiler to use.
1989: The default is <code class="varname">gfortran</code>.</p></dd>
1.114 maya 1990: <dt><span class="term"><code class="varname">GFORTRAN_VERSION</code>:</span></dt>
1991: <dd><p>If <code class="varname">PKGSRC_FORTRAN</code><code class="literal">=</code>
1992: <code class="varname">gfortran</code> is used, this option specifies which
1993: version to use.</p></dd>
1.1 dsieger 1994: </dl></div>
1995: </div>
1.41 asau 1996: <div class="sect2">
1.1 dsieger 1997: <div class="titlepage"><div><div><h3 class="title">
1.241 rillig 1998: <a name="conf.cflags"></a>6.5.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div>
1.1 dsieger 1999: <p>If you wish to set the <code class="varname">CFLAGS</code> variable,
2000: please make sure to use the <code class="literal">+=</code> operator
2001: instead of the <code class="literal">=</code> operator:</p>
2002: <pre class="programlisting">
2003: CFLAGS+= -your -flags
2004: </pre>
2005: <p>Using <code class="varname">CFLAGS=</code> (i.e. without the
1.23 wiz 2006: <span class="quote">“<span class="quote">+</span>”</span>) may lead to problems with packages that
1.16 jnemeth 2007: need to add their own flags. You may want to take a look
1.207 leot 2008: 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.23 wiz 2009: package if you're interested in optimization specifically
2010: for the current CPU. </p>
1.1 dsieger 2011: </div>
1.41 asau 2012: <div class="sect2">
1.1 dsieger 2013: <div class="titlepage"><div><div><h3 class="title">
1.241 rillig 2014: <a name="conf.ldflags"></a>6.5.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div>
1.1 dsieger 2015: <p>If you want to pass flags to the linker, both in the configure
2016: step and the build step, you can do this in two ways. Either set
2017: <code class="varname">LDFLAGS</code> or <code class="varname">LIBS</code>. The difference
2018: between the two is that <code class="varname">LIBS</code> will be appended to
2019: the command line, while <code class="varname">LDFLAGS</code> come earlier.
2020: <code class="varname">LDFLAGS</code> is pre-loaded with rpath settings for ELF
2021: machines depending on the setting of <code class="varname">USE_IMAKE</code> or
2022: the inclusion of <code class="filename">mk/x11.buildlink3.mk</code>. As with
2023: <code class="varname">CFLAGS</code>, if you do not wish to override these
2024: settings, use the <code class="literal">+=</code> operator:</p>
2025: <pre class="programlisting">
2026: LDFLAGS+= -your -linkerflags
2027: </pre>
2028: </div>
2029: </div>
1.41 asau 2030: <div class="sect1">
1.1 dsieger 2031: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.241 rillig 2032: <a name="developer-advanced-settings"></a>6.6. Developer/advanced settings</h2></div></div></div>
1.84 wiz 2033: <p>
1.1 dsieger 2034: </p>
1.41 asau 2035: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2036: <li class="listitem">
1.1 dsieger 2037: <p><code class="varname">PKG_DEVELOPER</code>:
1.232 gutterid 2038: Run some sanity checks that package developers want:
2039: </p>
1.41 asau 2040: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
1.23 wiz 2041: <li class="listitem"><p>make sure patches apply with zero
1.232 gutterid 2042: fuzz</p></li>
1.23 wiz 2043: <li class="listitem"><p>run check-shlibs to see that all
1.232 gutterid 2044: binaries will find their shared libs.</p></li>
1.1 dsieger 2045: </ul></div>
2046: </li>
1.232 gutterid 2047: <li class="listitem"><p><code class="varname">CHECK_FILES_STRICT</code>:
2048: Also check <code class="varname">VARBASE</code> and <code class="varname">PKG_SYSCONFDIR
2049: </code> values in PLIST entries.
2050: </p></li>
1.23 wiz 2051: <li class="listitem"><p><code class="varname">PKG_DEBUG_LEVEL</code>: The level
1.232 gutterid 2052: of debugging output which is displayed whilst making and
2053: installing the package. The default value for this is 0,
2054: which will not display the commands as they are executed
2055: (normal, default, quiet operation); the value 1 will display
2056: all shell commands before their invocation, and the value 2
2057: will display both the shell commands before their invocation,
2058: as well as their actual execution progress with <span class="command"><strong>set
2059: -x</strong></span>.</p></li>
1.1 dsieger 2060: </ul></div>
2061: <p>
2062: </p>
2063: </div>
1.41 asau 2064: <div class="sect1">
1.1 dsieger 2065: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.241 rillig 2066: <a name="selecting-build-options"></a>6.7. Selecting Build Options</h2></div></div></div>
1.1 dsieger 2067: <p>Some packages have build time options, usually to select
2068: between different dependencies, enable optional support for big
2069: dependencies or enable experimental features.</p>
2070: <p>To see which options, if any, a package supports, and which
1.10 hubertf 2071: options are mutually exclusive, run <span class="command"><strong>make
1.1 dsieger 2072: show-options</strong></span>, for example:</p>
2073: <pre class="programlisting">
2074: The following options are supported by this package:
2075: ssl Enable SSL support.
2076: Exactly one of the following gecko options is required:
2077: firefox Use firefox as gecko rendering engine.
2078: mozilla Use mozilla as gecko rendering engine.
2079: At most one of the following database options may be selected:
2080: mysql Enable support for MySQL database.
2081: pgsql Enable support for PostgreSQL database.
2082:
2083: These options are enabled by default: firefox
2084: These options are currently enabled: mozilla ssl
2085: </pre>
2086: <p>The following variables can be defined in
1.10 hubertf 2087: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to select which options to
1.1 dsieger 2088: enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>,
2089: which can be used to select or disable options for all packages
2090: that support them, and
2091: <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>,
2092: which can be used to select or disable options specifically for
2093: package <em class="replaceable"><code>pkgbase</code></em>. Options listed in
1.23 wiz 2094: these variables are selected, options preceded by <span class="quote">“<span class="quote">-</span>”</span>
1.1 dsieger 2095: are disabled. A few examples:</p>
2096: <pre class="screen">
1.10 hubertf 2097: <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.1 dsieger 2098: PKG_DEFAULT_OPTIONS= -arts -dvdread -esound
2099: PKG_OPTIONS.kdebase= debug -sasl
2100: PKG_OPTIONS.apache= suexec </pre>
1.11 rillig 2101: <p>It is important to note that options that were specifically
1.18 snj 2102: suggested by the package maintainer must be explicitly removed if
1.11 rillig 2103: you do not wish to include the option. If you are unsure you can view
2104: the current state with <span class="command"><strong>make show-options</strong></span>.</p>
1.1 dsieger 2105: <p>The following settings are consulted in the order given, and
2106: the last setting that selects or disables an option is
2107: used:</p>
1.23 wiz 2108: <div class="orderedlist"><ol class="orderedlist" type="1">
2109: <li class="listitem"><p>the default options as suggested by the package
1.1 dsieger 2110: maintainer</p></li>
1.23 wiz 2111: <li class="listitem"><p>the options implied by the settings of legacy
1.1 dsieger 2112: variables (see below)</p></li>
1.23 wiz 2113: <li class="listitem"><p><code class="varname">PKG_DEFAULT_OPTIONS</code></p></li>
2114: <li class="listitem"><p><code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code></p></li>
1.1 dsieger 2115: </ol></div>
2116: <p>For groups of mutually exclusive options, the last option
2117: selected is used, all others are automatically disabled. If an
2118: option of the group is explicitly disabled, the previously
2119: selected option, if any, is used. It is an error if no option
2120: from a required group of options is selected, and building the
2121: package will fail.</p>
2122: <p>Before the options framework was introduced, build options
2123: were selected by setting a variable (often named
2124: <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in
1.10 hubertf 2125: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> for each option. To ease
1.1 dsieger 2126: transition to the options framework for the user, these legacy
2127: variables are converted to the appropriate options setting
2128: (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>)
2129: automatically. A warning is issued to prompt the user to update
1.10 hubertf 2130: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to use the options framework
1.1 dsieger 2131: directly. Support for the legacy variables will be removed
2132: eventually.</p>
2133: </div>
2134: </div>
1.41 asau 2135: <div class="chapter">
1.1 dsieger 2136: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2137: <a name="binary"></a>Chapter 7. Creating binary packages</h2></div></div></div>
1.1 dsieger 2138: <div class="toc">
2139: <p><b>Table of Contents</b></p>
1.100 leot 2140: <dl class="toc">
1.154 rillig 2141: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
2142: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.1 dsieger 2143: </dl>
2144: </div>
1.41 asau 2145: <div class="sect1">
1.1 dsieger 2146: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2147: <a name="building-a-single-binary-package"></a>7.1. Building a single binary package</h2></div></div></div>
1.1 dsieger 2148: <p>Once you have built and installed a package, you can create
2149: a <span class="emphasis"><em>binary package</em></span> which can be installed on
1.246 leot 2150: another system with <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
1.1 dsieger 2151: the same package on a group of hosts and wasting CPU time. It also
2152: provides a simple means for others to install your package, should
2153: you distribute it.</p>
2154: <p>To create a binary package, change into the appropriate
1.10 hubertf 2155: directory in pkgsrc, and run <span class="command"><strong>make
1.1 dsieger 2156: package</strong></span>:</p>
2157: <pre class="screen">
1.112 rillig 2158: <code class="prompt">$</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
2159: <code class="prompt">$</code> <strong class="userinput"><code>make package</code></strong>
2160: </pre>
1.242 gutterid 2161: <p>This will build your package (if not already done) and package
2162: it into a binary package. You can then use the
2163: <span class="command"><strong>pkg_*</strong></span> tools to manipulate it. Binary packages are
2164: created in <code class="varname">PACKAGES</code>, which defaults to
2165: <code class="filename">/usr/pkgsrc/packages</code>, in the form of a compressed
2166: tar file. See <a class="xref" href="#logs.package" title="C.2. Packaging figlet">Section C.2, “Packaging figlet”</a> for a continuation of
2167: 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>
2168: example.</p>
1.154 rillig 2169: <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.1 dsieger 2170: such a binary package.</p>
2171: </div>
1.41 asau 2172: <div class="sect1">
1.1 dsieger 2173: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2174: <a name="settings-for-creationg-of-binary-packages"></a>7.2. Settings for creation of binary packages</h2></div></div></div>
1.184 rillig 2175: <p>See <a class="xref" href="#build.helpful-targets" title="13.17. Other helpful targets">Section 13.17, “Other helpful targets”</a>.</p>
1.6 rillig 2176: </div>
2177: </div>
1.41 asau 2178: <div class="chapter">
1.6 rillig 2179: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2180: <a name="bulk"></a>Chapter 8. Creating binary packages for everything in pkgsrc (bulk
1.6 rillig 2181: builds)</h2></div></div></div>
2182: <div class="toc">
2183: <p><b>Table of Contents</b></p>
1.100 leot 2184: <dl class="toc">
1.154 rillig 2185: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.180 rillig 2186: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.154 rillig 2187: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
2188: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.178 rillig 2189: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
2190: <dd><dl>
1.179 rillig 2191: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
2192: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.181 rillig 2193: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
2194: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
2195: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
2196: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
2197: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
2198: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
2199: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
2200: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.178 rillig 2201: </dl></dd>
2202: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
2203: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.6 rillig 2204: </dl>
2205: </div>
1.175 gutterid 2206: <p>For a number of reasons, you may want to build binary packages
2207: for a large selected set of packages in pkgsrc, or even for all pkgsrc packages.
1.71 wiz 2208: For instance, when you have multiple machines that should run the same software,
2209: it is wasted time if they all build their packages themselves from source.
2210: Or you may want to build a list of packages you want and check them before
1.175 gutterid 2211: deploying onto production systems.
1.71 wiz 2212: There is a way of getting a set of binary packages:
1.175 gutterid 2213: the bulk build system, or pbulk ("p" stands for "parallel").
1.112 rillig 2214: This chapter describes how to set it up.</p>
1.41 asau 2215: <div class="sect1">
1.6 rillig 2216: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2217: <a name="bulk.pre"></a>8.1. Preparations</h2></div></div></div>
1.71 wiz 2218: <p>First of all, you have to decide whether you build all packages
2219: or a limited set of them. Full bulk builds usually consume a lot more resources,
2220: both space and time, than builds for some practical sets of packages.
1.175 gutterid 2221: A number of particularly heavy packages exist that are not actually
2222: interesting to a wide audience. (The approximate resource consumption for a
2223: 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>.)
2224: For limited bulk builds you need to make a list of packages you want to build.
1.112 rillig 2225: Note that all their dependencies will be built, so you don't need to track them manually.
1.71 wiz 2226: </p>
2227: <p>During bulk builds various packages are installed and deinstalled
2228: in <code class="filename">/usr/pkg</code> (or whatever <code class="filename">LOCALBASE</code> is),
2229: so make sure that you don't need any package during the builds.
1.112 rillig 2230: Essentially, you should provide a fresh system, either a chroot environment
1.71 wiz 2231: or something even more restrictive, depending on what the operating system provides,
2232: or dedicate the whole physical machine.
2233: As a useful side effect this makes sure that bulk builds cannot
2234: break anything in your system. There have been numerous cases where
1.6 rillig 2235: certain packages tried to install files outside the
2236: <code class="filename">LOCALBASE</code> or wanted to edit some files in
1.71 wiz 2237: <code class="filename">/etc</code>.
2238: </p>
1.6 rillig 2239: </div>
1.41 asau 2240: <div class="sect1">
1.6 rillig 2241: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.180 rillig 2242: <a name="bulk.pbulk"></a>8.2. Running a bulk build</h2></div></div></div>
2243: <p>Running a bulk build works roughly as follows:</p>
1.41 asau 2244: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2245: <li class="listitem"><p>First, build the pbulk infrastructure in a fresh pkgsrc location.</p></li>
2246: <li class="listitem"><p>Then, build each of the packages from a clean installation directory using the infrastructure.</p></li>
1.15 rillig 2247: </ul></div>
1.41 asau 2248: <div class="sect2">
1.15 rillig 2249: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 2250: <a name="bulk.pbulk.conf"></a>8.2.1. Configuration</h3></div></div></div>
1.112 rillig 2251: <p>To simplify configuration, we provide the helper script <code class="filename">mk/pbulk/pbulk.sh</code>.</p>
1.68 asau 2252: <p>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
2253: Configure network access to fetch distribution files.
1.112 rillig 2254: Create a user with name "pbulk".</p>
1.68 asau 2255: <p>Fetch and extract pkgsrc. Use a command like one of these:</p>
2256: <pre class="screen">
1.151 sevan 2257: <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>
2258: <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.72 wiz 2259: <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.68 asau 2260: </pre>
2261: <p>Or any other way that fits (e.g., curl, wget).</p>
2262: <p>Deploy and configure pbulk tools, e.g.:</p>
2263: <pre class="screen">
1.118 sevan 2264: <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.68 asau 2265: <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>
2266: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build</code></strong>
2267: </pre>
2268: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2269: <h3 class="title">Note</h3>
2270: <p><code class="filename">mk.conf.frag</code> is a fragment of
2271: <code class="filename">mk.conf</code> that contains settings you want to
2272: apply to packages you build. For instance,</p>
2273: <pre class="programlisting">
1.112 rillig 2274: PKG_DEVELOPER= yes # perform more checks
2275: X11_TYPE= modular # use pkgsrc X11
2276: SKIP_LICENSE_CHECK= yes # accept all licences (useful
2277: # when building all packages)
1.68 asau 2278: </pre>
2279: </div>
2280: <p>If configured for limited list, replace the list in <code class="filename">/usr/pbulk/etc/pbulk.list</code>
1.112 rillig 2281: with your list of packages, one per line without empty lines or comments. E.g.:</p>
1.68 asau 2282: <pre class="programlisting">
2283: www/firefox
2284: mail/thunderbird
2285: misc/libreoffice4
2286: </pre>
1.69 asau 2287: <p>At this point you can also review configuration in <code class="filename">/usr/pbulk/etc</code>
2288: and make final amendments, if wanted.</p>
1.68 asau 2289: <p>Start it:</p>
2290: <pre class="screen">
2291: <code class="prompt">#</code> <strong class="userinput"><code>/usr/pbulk/bin/bulkbuild</code></strong>
2292: </pre>
2293: <p>After it finishes, you'll have <code class="filename">/mnt</code> filled with distribution files, binary packages, and reports,
2294: plain text summary in <code class="filename">/mnt/bulklog/meta/report.txt</code>
2295: </p>
2296: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2297: <h3 class="title">Note</h3>
2298: <p>The <code class="filename">pbulk.sh</code> script does not cover all possible use cases.
2299: While being ready to run, it serves as a good starting point to understand and build more complex setups.
2300: The script is kept small enough for better understanding.</p>
2301: </div>
2302: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2303: <h3 class="title">Note</h3>
2304: <p>The <code class="filename">pbulk.sh</code> script supports running
1.205 wiz 2305: unprivileged bulk build and helps configuring distributed bulk builds.
2306: Distributed bulk builds support either building in worker chroots
2307: (each node is a path to a different chroot)
2308: that replicate the target system, including the pbulk prefix,
2309: or remote machines (each node is
2310: an IP address that must be accessible over SSH without a password).</p>
1.68 asau 2311: </div>
1.6 rillig 2312: </div>
2313: </div>
1.41 asau 2314: <div class="sect1">
1.6 rillig 2315: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2316: <a name="bulk.req"></a>8.3. Requirements of a full bulk build</h2></div></div></div>
1.71 wiz 2317: <p>A complete bulk build requires lots of disk space. Some of the
2318: disk space can be read-only, some other must be writable. Some can be on
2319: remote filesystems (such as NFS) and some should be local. Some can be
2320: temporary filesystems, others must survive a sudden reboot.</p>
2321: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.205 wiz 2322: <li class="listitem"><p>70 GB for the distfiles (read-write, remote, temporary)</p></li>
2323: <li class="listitem"><p>60 GB for the binary packages (read-write, remote, permanent)</p></li>
1.71 wiz 2324: <li class="listitem"><p>1 GB for the pkgsrc tree (read-only, remote, permanent)</p></li>
2325: <li class="listitem"><p>5 GB for <code class="filename">LOCALBASE</code> (read-write, local, temporary)</p></li>
2326: <li class="listitem"><p>10 GB for the log files (read-write, remote, permanent)</p></li>
2327: <li class="listitem"><p>5 GB for temporary files (read-write, local, temporary)</p></li>
2328: </ul></div>
2329: </div>
2330: <div class="sect1">
2331: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.178 rillig 2332: <a name="bulk.var"></a>8.4. Bulk build variants</h2></div></div></div>
2333: <p>To ensure that pkgsrc packages work in different configurations, it
2334: makes sense to run non-default bulk builds from time to time. This
2335: section lists some ideas for bulk builds that intentionally let packages
2336: fail if they don't follow the pkgsrc style.</p>
2337: <div class="sect2">
2338: <div class="titlepage"><div><div><h3 class="title">
1.179 rillig 2339: <a name="bulk.var.confopt"></a>8.4.1. Detect unknown configure options</h3></div></div></div>
1.178 rillig 2340: <p>Add the following line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2341: <pre class="programlisting">
2342: GNU_CONFIGURE_STRICT= yes
2343: </pre>
2344: <p>When a package fails this additional check, the most common cause
2345: is that the configure option was valid for an older version of the
2346: package but does not apply anymore. In that case, just remove it.</p>
2347: </div>
2348: <div class="sect2">
2349: <div class="titlepage"><div><div><h3 class="title">
1.179 rillig 2350: <a name="bulk.var.comperr"></a>8.4.2. Detect classes of bugs by forcing compiler warnings</h3></div></div></div>
1.178 rillig 2351: <p>The job of a compiler is not restricted to producing executable
1.179 rillig 2352: code, most compilers also detect typical programming mistakes. The pkgsrc
2353: compiler wrappers make it easy to force compiler options when the package
2354: is built. This can be used to find typical bugs across all packages that
2355: are in pkgsrc. By reporting these bugs upstream, the packages will be
2356: more reliable with the next updates.</p>
2357: <p>Add some of the following lines to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.178 rillig 2358: <pre class="programlisting">
2359: CFLAGS+= -Werror=char-subscripts
1.179 rillig 2360: CFLAGS+= -Werror=implicit-function-declaration
1.178 rillig 2361: </pre>
1.179 rillig 2362: <p>When a package fails to build using these stricter compiler
2363: options, document the circumstances in which the compiler produced the
2364: error message. This includes:</p>
1.178 rillig 2365: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
2366: <li class="listitem"><p>The platform
2367: (<code class="varname">MACHINE_PLATFORM</code>)</p></li>
2368: <li class="listitem"><p>The source file</p></li>
2369: <li class="listitem"><p>An excerpt of the code. GCC and Clang already do this as
2370: part of the diagnostic.</p></li>
1.179 rillig 2371: <li class="listitem"><p>The exact error message from the compiler.</p></li>
1.178 rillig 2372: </ul></div>
2373: <p>If a package produces these error messages, but the package is
1.179 rillig 2374: 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
2375: in the next builds:</p>
1.178 rillig 2376: <pre class="programlisting">
1.179 rillig 2377: .if ${PKGPATH} == category/package
1.178 rillig 2378: # Version ${VERSION} failed on ${MACHINE_PLATFORM}:
2379: # error message
2380: # code
1.179 rillig 2381: # Reason why the code does not need to be fixed.
1.178 rillig 2382: BUILDLINK_TRANSFORM+= rm:-Werror=char-subscripts
1.179 rillig 2383: .endif
1.178 rillig 2384: </pre>
2385: <p>If the error messages from the compiler are valid and the code
1.179 rillig 2386: needs to be fixed, prepare a local patch (see
2387: <code class="varname">LOCALPATCHES</code>) and report the bug to the upstream
2388: authors of the package, providing them with the information you collected
2389: above.</p>
2390: <p>Patches that are not essential for the package to work should only
2391: be reported upstream but not committed to pkgsrc, to make future updates
2392: easier.</p>
1.178 rillig 2393: </div>
2394: <div class="sect2">
2395: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2396: <a name="bulk.var.builderr"></a>8.4.3. Force compiler options only in the build phase</h3></div></div></div>
2397: <p>When adding custom compiler flags via <code class="varname">CFLAGS</code>,
2398: these apply to all phases of the package build process. Especially in the
2399: configure phase, adding <code class="literal">-Werror</code> leads to wrong
2400: decisions. The GNU configure scripts feed many small test programs to the
2401: C compiler to see whether certain headers are available, functions are
2402: defined in a library and programs can be run. In many cases these
2403: programs would not survive a strict compiler run with <code class="literal">-Wall
2404: -Wextra -Werror</code>.</p>
2405: <p>The pkgsrc infrastructure is flexible enough to support compiler
2406: options being added between the <code class="literal">configure</code> and
2407: <code class="literal">build</code> phases. It's a little more complicated than the
2408: other examples in this section but still easy enough.</p>
2409: <p>The basic idea is to use the pkgsrc compiler wrapper to inject the
2410: desired compiler options. The compiler wrapper's original task is to hide
2411: unwanted directories of include files and to normalize compiler options.
2412: It does this by wrapping the compiler command and rewriting the command
2413: line. To see this in action, run <span class="command"><strong>bmake patch</strong></span> in a
2414: package directory and examine the
2415: <code class="filename">work/.cwrappers/config</code> directory. It contains
2416: individual configurations for the C compiler and the related tools. The
2417: plan is to find a hook between the configure and build phases, and to
2418: modify these configuration files at that point.</p>
2419: <p>To find this hook, have a look at
2420: <code class="filename">mk/build/build.mk</code>, which contains among others the
2421: <code class="literal">pre-build-checks-hook</code>. The word
2422: <code class="literal">checks</code> doesn't quite fit, but the
2423: <code class="literal">pre-build-hook</code> sounds good enough.</p>
2424: <p>The code to be included in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> is:</p>
2425: <pre class="programlisting">
2426: # Just a few example options.
2427: BUILD_ONLY_CFLAGS= -Wall -Werror -O2 -DTEMPDIR='"/tmp"'
2428:
2429: .if ${BUILD_ONLY_CFLAGS:U:M*}
2430: pre-build-checks-hook: add-build-only-cflags
2431:
2432: add-build-only-cflags: .PHONY
2433: ${RUN} cd ${CWRAPPERS_CONFIG_DIR}; \
2434: ${TEST} ! -f ${.TARGET} || exit 0; \
2435: for flag in ${BUILD_ONLY_CFLAGS}; do \
2436: ${ECHO} "append=$$flag" >> cc; \
2437: done; \
2438: > ${.TARGET}
2439: .endif
2440: </pre>
2441: <p>(When editing the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, make sure that the commands of the
2442: <code class="literal">add-build-only-cflags</code> target are indented with a tab,
2443: not with spaces.)</p>
2444: <p>The condition in the <code class="literal">.if</code> statement contains the
2445: <code class="literal">:U</code> modifier to prevent parse errors if the variable
2446: should be undefined, possibly because it is only defined for a subset of
2447: the packages. The <code class="literal">:M*</code> modifier ensures that there is
2448: at least one compiler option, to prevent a syntax error in the shell
2449: parser.</p>
2450: <p>The code around the <code class="literal">${.TARGET}</code> variable ensures
2451: that the additional compiler options are only appended once, even if
2452: <span class="command"><strong>bmake build</strong></span> is run multiple times. To do this, it
2453: creates a marker file.</p>
2454: <p>To verify that this setup works, run <span class="command"><strong>bmake
2455: configure</strong></span> in a package directory. Up to now, everything works
2456: as usual. Examine the directory
2457: <code class="filename">work/.cwrappers/config</code> to see that the compiler
2458: options from <code class="varname">BUILD_ONLY_CFLAGS</code> are not yet added to
2459: the file <code class="filename">cc</code>. Examine the tail of the
2460: <code class="filename">work/.work.log</code> file to see that the normal compiler
2461: options are used.</p>
2462: <p>Now run <span class="command"><strong>bmake build</strong></span>. This will append the
2463: options to the file <code class="filename">cc</code> and will create the marker
2464: file in the same directory. After that, the build starts as usual, but
2465: with the added compiler options. Examine the tail of the file
2466: <code class="filename">work/.work.log</code> to see that the lines starting with
2467: <code class="literal">[*]</code> don't contain the compiler options, but the
2468: corresponding lines starting with <code class="literal"><.></code> do end
2469: with these options.</p>
2470: <p>Building packages using this setup variant and fixing the resulting
2471: 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>
2472: </div>
2473: <div class="sect2">
2474: <div class="titlepage"><div><div><h3 class="title">
2475: <a name="bulk.var.dirs"></a>8.4.4. Use custom directories</h3></div></div></div>
1.178 rillig 2476: <p>Some directories like <code class="varname">PREFIX</code>,
2477: <code class="varname">VARBASE</code>, <code class="varname">PKG_SYSCONFDIR</code>,
2478: <code class="varname">PKGMANDIR</code>, <code class="varname">PKG_INFODIR</code> can be
2479: configured in pkgsrc. Set these to arbitrary paths during bootstrap or
2480: afterwards in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2481: <pre class="programlisting">
2482: PREFIX= /a-random-uuid
2483: PKG_SYSCONFDIR= /a-random-uuid
2484: VARBASE= /a-random-uuid
2485: PKGMANDIR= a-random-uuid
2486: PKG_INFODIR= a-random-uuid
2487: </pre>
2488: </div>
2489: <div class="sect2">
2490: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2491: <a name="bulk.var.warn"></a>8.4.5. Turn warnings into errors</h3></div></div></div>
1.178 rillig 2492: <p>When building a package, warnings are typically ignored since they
2493: just flow by and do not cause the build to fail immediately. To find
2494: these warnings, redefine them to errors in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2495: <pre class="programlisting">
2496: DELAYED_WARNING_MSG= ${DELAYED_ERROR_MSG} "(was warning)"
2497: WARNING_MSG= ${FAIL_MSG} "(was warning)"
2498: </pre>
2499: <p>(There are many more classes of warnings in pkgsrc, and most of
2500: them can be redefined with a simple definition like above.</p>
1.179 rillig 2501: <p>If a package suggests to add <code class="varname">USE_TOOLS+=perl</code> to
1.178 rillig 2502: the package Makefile, research whether the package actually needs Perl.
2503: If it does, add <code class="varname">USE_TOOLS+=perl</code> to the package
2504: Makefile, and if it doesn't, add
2505: <code class="varname">TOOLS_BROKEN+=perl</code>.</p>
2506: </div>
2507: <div class="sect2">
2508: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2509: <a name="bulk.var.pkglint"></a>8.4.6. Reject packages for which pkglint reports errors</h3></div></div></div>
1.178 rillig 2510: <p>Using pkglint as part of the regular build process is mostly a
2511: waste of time. If you want to fix some of the warnings, just run pkglint
2512: recursively on the whole pkgsrc tree. This will take a few minutes (up to
2513: 10), which is much faster than a complete bulk build.</p>
2514: </div>
2515: <div class="sect2">
2516: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2517: <a name="bulk.var.strings"></a>8.4.7. Reject packages that contain forbidden strings</h3></div></div></div>
1.178 rillig 2518: <p>To ensure that the binary packages don't contain references to the
2519: build directory, there is already <code class="varname">CHECK_WRKREF</code>. If
2520: that variable includes the item <code class="literal">extra</code>, it is
2521: possible to define additional patterns that must not appear in any
2522: installed file. This is specified in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2523: <pre class="programlisting">
2524: CHECK_WRKREF= extra
2525: CHECK_WRKREF_EXTRA_DIRS+= /usr/local
2526: CHECK_WRKREF_EXTRA_DIRS+= /usr/pkg
2527: CHECK_WRKREF_EXTRA_DIRS+= @[A-Z][A-Z]*@
2528: </pre>
2529: <p>The above patterns will probably generate many false positives,
2530: therefore the results need to be taken with a grain of salt.</p>
2531: </div>
2532: <div class="sect2">
2533: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2534: <a name="bulk.var.test"></a>8.4.8. Reject packages whose self-test fails</h3></div></div></div>
1.178 rillig 2535: <p>To run the test suites that come with each package, add this line
2536: to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2537: <pre class="programlisting">
2538: PKGSRC_RUN_TEST= yes
2539: </pre>
2540: <p>Be prepared that even the most basic packages fail this test. When
2541: doing a bulk build with this, it will often abort in the early phase
2542: where the packages are scanned for their dependencies since there are
2543: cyclic dependencies. There is still a lot to do in this area.</p>
2544: </div>
2545: <div class="sect2">
2546: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2547: <a name="bulk.var.shvar"></a>8.4.9. Reject packages that use undefined shell variables</h3></div></div></div>
1.178 rillig 2548: <p>To catch typos in the shell snippets from the Makefile fragments,
2549: add the <code class="literal">-u</code> flag to most of the commands by adding this
2550: line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2551: <pre class="programlisting">
2552: RUN= @set -eu;
2553: </pre>
1.181 rillig 2554: <p>After that, ensure that none of the bulk build log files (even
2555: those for successfully built packages) contains the string
2556: <code class="literal">parameter not set</code> or whatever error message the
2557: command <span class="command"><strong>sh -ceu '$undefined'</strong></span> outputs.</p>
1.178 rillig 2558: <p>See <code class="filename">mk/misc/common.mk</code> for the existing
2559: definition.</p>
2560: </div>
2561: <div class="sect2">
2562: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2563: <a name="bulk.var.quiet"></a>8.4.10. Turn off verbose logging</h3></div></div></div>
1.178 rillig 2564: <p>The build logs of a package are often quite long. This allows error
2565: messages or other interesting details to hide between the noise. To make
2566: the actual error message stand out more, add these lines to
2567: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2568: <pre class="programlisting">
2569: GNU_CONFIGURE_QUIET= yes
2570: MAKE_FLAGS+= -s
2571: </pre>
2572: <p>The <code class="literal">-s</code> option works for both GNU Make and BSD
2573: Make. On exotic platforms with their own make, it may be a little
2574: different.</p>
2575: </div>
2576: </div>
2577: <div class="sect1">
2578: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2579: <a name="creating-cdroms"></a>8.5. Creating a multiple CD-ROM packages collection</h2></div></div></div>
1.1 dsieger 2580: <p>After your pkgsrc bulk-build has completed, you may wish to
2581: create a CD-ROM set of the resulting binary packages to assist
2582: in installing packages on other machines. The
1.207 leot 2583: <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.1 dsieger 2584: a simple tool for creating the ISO 9660 images.
1.10 hubertf 2585: <span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a
1.1 dsieger 2586: way that keeps all the dependencies for a given package on the same
2587: CD as that package.</p>
1.41 asau 2588: <div class="sect2">
1.1 dsieger 2589: <div class="titlepage"><div><div><h3 class="title">
1.178 rillig 2590: <a name="cdpack-example"></a>8.5.1. Example of cdpack</h3></div></div></div>
1.1 dsieger 2591: <p>Complete documentation for cdpack is found in the cdpack(1)
2592: man page. The following short example assumes that the binary
2593: packages are left in
2594: <code class="filename">/usr/pkgsrc/packages/All</code> and that
2595: sufficient disk space exists in <code class="filename">/u2</code> to
2596: hold the ISO 9660 images.</p>
2597: <pre class="screen">
2598: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /u2/images</code></strong>
2599: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong>
2600: <code class="prompt">#</code> <strong class="userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong>
2601: </pre>
2602: <p>If you wish to include a common set of files
2603: (<code class="filename">COPYRIGHT</code>, <code class="filename">README</code>,
2604: etc.) on each CD in the collection, then you need to create a
1.175 gutterid 2605: directory which contains these files, e.g.:</p>
1.1 dsieger 2606: <pre class="screen">
2607: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common</code></strong>
2608: <code class="prompt">#</code> <strong class="userinput"><code>echo "This is a README" > /tmp/common/README</code></strong>
2609: <code class="prompt">#</code> <strong class="userinput"><code>echo "Another file" > /tmp/common/COPYING</code></strong>
2610: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common/bin</code></strong>
2611: <code class="prompt">#</code> <strong class="userinput"><code>echo "#!/bin/sh" > /tmp/common/bin/myscript</code></strong>
2612: <code class="prompt">#</code> <strong class="userinput"><code>echo "echo Hello world" >> /tmp/common/bin/myscript</code></strong>
2613: <code class="prompt">#</code> <strong class="userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong>
2614: </pre>
2615: <p>Now create the images:</p>
2616: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong></pre>
2617: <p>Each image will contain <code class="filename">README</code>,
2618: <code class="filename">COPYING</code>, and <code class="filename">bin/myscript</code>
2619: in their root directories.</p>
2620: </div>
2621: </div>
2622: </div>
1.41 asau 2623: <div class="chapter">
1.1 dsieger 2624: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2625: <a name="files"></a>Chapter 9. Directory layout of the installed files</h2></div></div></div>
1.1 dsieger 2626: <div class="toc">
2627: <p><b>Table of Contents</b></p>
1.100 leot 2628: <dl class="toc">
1.154 rillig 2629: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
2630: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
1.1 dsieger 2631: </dl>
2632: </div>
2633: <p>The files that are installed by pkgsrc are organized in a way that
2634: is similar to what you find in the <code class="filename">/usr</code> directory
2635: of the base system. But some details are different. This is because
2636: pkgsrc initially came from FreeBSD and had adopted its file system
2637: hierarchy. Later it was largely influenced by NetBSD. But no matter
2638: which operating system you are using pkgsrc with, you can expect the
2639: same layout for pkgsrc.</p>
2640: <p>There are mainly four root directories for pkgsrc, which are all
2641: configurable in the <code class="filename">bootstrap/bootstrap</code> script.
2642: When pkgsrc has been installed as root, the default locations
2643: are:</p>
2644: <pre class="programlisting">
2645: LOCALBASE= /usr/pkg
2646: PKG_SYSCONFBASE= /usr/pkg/etc
2647: VARBASE= /var
1.119 sevan 2648: PKG_DBDIR= /usr/pkg/pkgdb
1.1 dsieger 2649: </pre>
2650: <p>In unprivileged mode (when pkgsrc has been installed as any other
2651: user), the default locations are:</p>
2652: <pre class="programlisting">
2653: LOCALBASE= ${HOME}/pkg
2654: PKG_SYSCONFBASE= ${HOME}/pkg/etc
2655: VARBASE= ${HOME}/pkg/var
1.119 sevan 2656: PKG_DBDIR= ${HOME}/pkg/pkgdb
1.1 dsieger 2657: </pre>
2658: <p>What these four directories are for, and what they look like is
2659: explained below.</p>
1.41 asau 2660: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2661: <li class="listitem"><p><code class="varname">LOCALBASE</code> corresponds to the
1.1 dsieger 2662: <code class="filename">/usr</code> directory in the base system. It is the
1.23 wiz 2663: <span class="quote">“<span class="quote">main</span>”</span> directory where the files are installed and contains
1.1 dsieger 2664: the well-known subdirectories like <code class="filename">bin</code>,
2665: <code class="filename">include</code>, <code class="filename">lib</code>,
2666: <code class="filename">share</code> and
2667: <code class="filename">sbin</code>.</p></li>
1.23 wiz 2668: <li class="listitem"><p><code class="varname">VARBASE</code> corresponds to
1.1 dsieger 2669: <code class="filename">/var</code> in the base system. Some programs (especially
2670: games, network daemons) need write access to it during normal
2671: operation.</p></li>
1.23 wiz 2672: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR</code> corresponds to
1.1 dsieger 2673: <code class="filename">/etc</code> in the base system. It contains configuration
1.10 hubertf 2674: files of the packages, as well as pkgsrc's <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
1.1 dsieger 2675: itself.</p></li>
2676: </ul></div>
1.41 asau 2677: <div class="sect1">
1.1 dsieger 2678: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2679: <a name="files.localbase"></a>9.1. File system layout in <code class="literal">${LOCALBASE}</code>
1.1 dsieger 2680: </h2></div></div></div>
2681: <p>The following directories exist in a typical pkgsrc installation
2682: in <code class="filename">${LOCALBASE}</code>.</p>
1.41 asau 2683: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2684: <dt><span class="term"><code class="filename">bin</code></span></dt>
2685: <dd><p>Contains executable programs that are intended to be
2686: directly used by the end user.</p></dd>
2687: <dt><span class="term"><code class="filename">emul</code></span></dt>
2688: <dd><p>Contains files for the emulation layers of various other
2689: operating systems, especially for
2690: NetBSD.</p></dd>
2691: <dt><span class="term"><code class="filename">etc</code> (the usual location of
2692: <code class="filename">${PKG_SYSCONFDIR}</code>)</span></dt>
2693: <dd><p>Contains
2694: the configuration files.</p></dd>
2695: <dt><span class="term"><code class="filename">include</code></span></dt>
2696: <dd><p>Contains headers for the C and C++ programming
2697: languages.</p></dd>
2698: <dt><span class="term"><code class="filename">info</code></span></dt>
2699: <dd><p>Contains GNU info files of various
2700: packages.</p></dd>
2701: <dt><span class="term"><code class="filename">lib</code></span></dt>
2702: <dd><p>Contains shared and static
2703: libraries.</p></dd>
2704: <dt><span class="term"><code class="filename">libdata</code></span></dt>
2705: <dd><p>Contains data files that don't change after
2706: installation. Other data files belong into
2707: <code class="filename">${VARBASE}</code>.</p></dd>
2708: <dt><span class="term"><code class="filename">libexec</code></span></dt>
2709: <dd><p>Contains programs that are not intended to be used by
2710: end users, such as helper programs or network
2711: daemons.</p></dd>
2712: <dt><span class="term"><code class="filename">libexec/cgi-bin</code></span></dt>
2713: <dd><p>Contains programs that are intended to be executed as
2714: CGI scripts by a web server.</p></dd>
2715: <dt><span class="term"><code class="filename">man</code> (the usual value of
2716: <code class="filename">${PKGMANDIR}</code>)</span></dt>
2717: <dd><p>Contains brief
2718: documentation in form of manual pages.</p></dd>
2719: <dt><span class="term"><code class="filename">sbin</code></span></dt>
2720: <dd><p>Contains programs that are intended to be used only by
2721: the super-user.</p></dd>
2722: <dt><span class="term"><code class="filename">share</code></span></dt>
2723: <dd><p>Contains platform-independent data files that don't
2724: change after installation.</p></dd>
2725: <dt><span class="term"><code class="filename">share/doc</code></span></dt>
2726: <dd><p>Contains documentation files provided by the
2727: packages.</p></dd>
2728: <dt><span class="term"><code class="filename">share/examples</code></span></dt>
2729: <dd><p>Contains example files provided by the packages. Among
2730: others, the original configuration files are saved here and copied to
2731: <code class="filename">${PKG_SYSCONFDIR}</code> during
2732: installation.</p></dd>
2733: <dt><span class="term"><code class="filename">share/examples/rc.d</code></span></dt>
2734: <dd><p>Contains the original files for rc.d
2735: scripts.</p></dd>
2736: <dt><span class="term"><code class="filename">var</code> (the usual location of
2737: <code class="filename">${VARBASE}</code>)</span></dt>
2738: <dd><p>Contains files
2739: that may be modified after
2740: installation.</p></dd>
2741: </dl></div>
2742: </div>
1.41 asau 2743: <div class="sect1">
1.1 dsieger 2744: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2745: <a name="files.varbase"></a>9.2. File system layout in <code class="literal">${VARBASE}</code>
1.1 dsieger 2746: </h2></div></div></div>
1.41 asau 2747: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2748: <dt><span class="term"><code class="filename">db/pkg</code> (the usual location of
2749: <code class="filename">${PKG_DBDIR}</code>)</span></dt>
2750: <dd><p>Contains
2751: information about the currently installed
2752: packages.</p></dd>
2753: <dt><span class="term"><code class="filename">games</code></span></dt>
2754: <dd><p>Contains highscore
2755: files.</p></dd>
2756: <dt><span class="term"><code class="filename">log</code></span></dt>
2757: <dd><p>Contains log files.</p></dd>
2758: <dt><span class="term"><code class="filename">run</code></span></dt>
2759: <dd><p>Contains informational files about daemons that are
2760: currently running.</p></dd>
2761: </dl></div>
2762: </div>
2763: </div>
1.41 asau 2764: <div class="chapter">
1.1 dsieger 2765: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2766: <a name="faq"></a>Chapter 10. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 2767: <div class="toc">
2768: <p><b>Table of Contents</b></p>
1.100 leot 2769: <dl class="toc">
1.154 rillig 2770: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
2771: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
2772: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
2773: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
2774: <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>
2775: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
2776: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
2777: <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>
2778: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
2779: <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.23 wiz 2780: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.154 rillig 2781: <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.221 nia 2782: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.154 rillig 2783: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
2784: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
2785: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
2786: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
2787: <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.1 dsieger 2788: </dl>
2789: </div>
2790: <p>This section contains hints, tips & tricks on special things in
2791: pkgsrc that we didn't find a better place for in the previous chapters, and
2792: it contains items for both pkgsrc users and developers.</p>
1.41 asau 2793: <div class="sect1">
1.1 dsieger 2794: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2795: <a name="mailing-list-pointers"></a>10.1. Are there any mailing lists for pkg-related discussion?</h2></div></div></div>
1.1 dsieger 2796: <p>The following mailing lists may be of interest to pkgsrc users:</p>
1.41 asau 2797: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2798: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-users" target="_top">pkgsrc-users</a>:
1.1 dsieger 2799: This is a general purpose list for most issues regarding
2800: pkgsrc, regardless of platform, e.g. soliciting user help
2801: for pkgsrc configuration, unexpected build failures, using
2802: particular packages, upgrading pkgsrc installations,
2803: questions regarding the pkgsrc release branches, etc. General announcements or
2804: proposals for changes that impact the pkgsrc user community,
2805: e.g. major infrastructure changes, new features, package
2806: removals, etc., may also be posted.</p></li>
1.174 leot 2807: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-bulk" target="_top">pkgsrc-bulk</a>:
1.1 dsieger 2808: A list where the results of pkgsrc bulk builds are sent and
2809: discussed.</p></li>
1.174 leot 2810: <li class="listitem"><p><a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#pkgsrc-changes" target="_top">pkgsrc-changes</a>:
1.1 dsieger 2811: This list is for those who are interested in getting a
2812: commit message for every change committed to pkgsrc. It is
2813: also available in digest form, meaning one daily message
2814: containing all commit messages for changes to the package
2815: source tree in that 24 hour period.</p></li>
2816: </ul></div>
2817: <p>To subscribe, do:</p>
2818: <pre class="programlisting">
2819: <code class="prompt">%</code> echo subscribe <em class="replaceable"><code>listname</code></em> | mail majordomo@NetBSD.org
2820: </pre>
2821: <p>Archives for all these mailing lists are available from
1.174 leot 2822: <a class="ulink" href="https://mail-index.NetBSD.org/" target="_top">https://mail-index.NetBSD.org/</a>.</p>
1.1 dsieger 2823: </div>
1.41 asau 2824: <div class="sect1">
1.1 dsieger 2825: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2826: <a name="faq-pkgtools"></a>10.2. Utilities for package management (pkgtools)</h2></div></div></div>
1.1 dsieger 2827: <p>The directory <code class="filename">pkgsrc/pkgtools</code> contains
2828: a number of useful utilities for both users and developers of pkgsrc. This
1.121 sevan 2829: section attempts only to make the reader aware of some of the utilities and when
1.1 dsieger 2830: they might be useful, and not to duplicate the documentation that comes
2831: with each package.</p>
2832: <p>Utilities used by pkgsrc (automatically installed when needed):</p>
1.207 leot 2833: <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.1 dsieger 2834: Symlinks for use by buildlink.</p></li></ul></div>
2835: <p>OS tool augmentation (automatically installed when needed):</p>
1.41 asau 2836: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2837: <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.121 sevan 2838: Calculates various kinds of checksums (including SHA3).</p></li>
1.207 leot 2839: <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.1 dsieger 2840: Compatibility library for pkgsrc tools.</p></li>
1.207 leot 2841: <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.1 dsieger 2842: non-BSD systems due to lack of native mtree.</p></li>
1.207 leot 2843: <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.1 dsieger 2844: Up-to-date replacement for
2845: <code class="filename">/usr/sbin/pkg_install</code>, or for use on operating
2846: systems where pkg_install is not present.</p></li>
2847: </ul></div>
2848: <p>Utilities used by pkgsrc (not automatically installed):</p>
1.41 asau 2849: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2850: <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.1 dsieger 2851: Create a binary package from an
1.10 hubertf 2852: already-installed package. Used by <span class="command"><strong>make replace</strong></span> to
1.1 dsieger 2853: save the old package.</p></li>
1.207 leot 2854: <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.1 dsieger 2855: Adds extra functionality to pkgsrc, allowing it to fetch distfiles
2856: from multiple locations. It currently supports the following
2857: methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li>
1.207 leot 2858: <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.16 jnemeth 2859: the best compiler flags to optimise code for your current
1.23 wiz 2860: CPU and compiler. </p></li>
1.1 dsieger 2861: </ul></div>
2862: <p>Utilities for keeping track of installed packages, being up to date,
2863: etc:</p>
1.41 asau 2864: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2865: <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.65 wiz 2866: update tool similar to apt(1). Download, install, and upgrade
2867: binary packages easily.</p></li>
1.207 leot 2868: <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.1 dsieger 2869: packages whose installed versions do not match the latest pkgsrc
2870: entries.</p></li>
1.207 leot 2871: <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.1 dsieger 2872: dependency graphs of packages, to aid in choosing a strategy for
2873: updating.</p></li>
1.207 leot 2874: <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
2875: 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>
2876: <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.12 weinem 2877: pkglint(1) program checks a pkgsrc entry for errors.</p></li>
1.207 leot 2878: <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.1 dsieger 2879: does various checks on the complete pkgsrc system.</p></li>
1.207 leot 2880: <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.1 dsieger 2881: packages you have installed.</p></li>
2882: </ul></div>
2883: <p>Utilities for people maintaining or creating individual packages:</p>
1.41 asau 2884: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2885: <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.1 dsieger 2886: making and maintaining patches for a package (includes pkgdiff,
2887: pkgvi, mkpatches, etc.).</p></li>
1.207 leot 2888: <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.1 dsieger 2889: converting to pkgsrc.</p></li>
2890: </ul></div>
2891: <p>Utilities for people maintaining pkgsrc (or: more obscure pkg
2892: utilities)</p>
1.41 asau 2893: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2894: <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.1 dsieger 2895: packages in a chrooted area.</p></li>
1.207 leot 2896: <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.1 dsieger 2897: kernel version for chrooted cross builds.</p></li>
2898: </ul></div>
2899: </div>
1.41 asau 2900: <div class="sect1">
1.1 dsieger 2901: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2902: <a name="non-root-pkgsrc"></a>10.3. How to use pkgsrc as non-root</h2></div></div></div>
1.108 rillig 2903: <p>To install packages from source as a non-root user, download
1.154 rillig 2904: 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.108 rillig 2905: directory and run the command <span class="command"><strong>./bootstrap/bootstrap
2906: --unprivileged</strong></span>.</p>
2907: <p>This will install the binary part of pkgsrc to
2908: <code class="filename">~/pkg</code> and put the pkgsrc configuration <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
2909: into <code class="filename">~/pkg/etc</code>.</p>
2910: <p>For more details, see <code class="filename">mk/unprivileged.mk</code>.</p>
1.1 dsieger 2911: </div>
1.41 asau 2912: <div class="sect1">
1.1 dsieger 2913: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2914: <a name="resume-transfers"></a>10.4. How to resume transfers when fetching distfiles?</h2></div></div></div>
1.1 dsieger 2915: <p>By default, resuming transfers in pkgsrc is disabled, but you can
2916: enable this feature by adding the option
2917: <code class="varname">PKG_RESUME_TRANSFERS=YES</code> into
1.10 hubertf 2918: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. If, during a fetch step, an incomplete
1.1 dsieger 2919: distfile is found, pkgsrc will try to resume it.</p>
2920: <p>You can also
1.61 wiz 2921: use a different program than the platform default program by changing the
1.16 jnemeth 2922: <code class="varname">FETCH_USING</code> variable. You can specify the program by
2923: using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
2924: by using the value manual. A value of custom disables the system defaults
2925: and dependency tracking for the fetch program. In that case you have to
2926: provide <code class="varname">FETCH_CMD</code>, <code class="varname">FETCH_BEFORE_ARGS</code>,
2927: <code class="varname">FETCH_RESUME_ARGS</code>, <code class="varname">FETCH_OUTPUT_ARGS</code>,
2928: <code class="varname">FETCH_AFTER_ARGS</code>.</p>
1.1 dsieger 2929: <p>For example, if you want to use
1.16 jnemeth 2930: <code class="filename">wget</code> to download, you'll have to use something
1.1 dsieger 2931: like:</p>
2932: <pre class="programlisting">
1.112 rillig 2933: FETCH_USING= wget
1.1 dsieger 2934: </pre>
2935: </div>
1.41 asau 2936: <div class="sect1">
1.1 dsieger 2937: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2938: <a name="x.org-from-pkgsrc"></a>10.5. How can I install/use modular X.org from pkgsrc?</h2></div></div></div>
1.4 rillig 2939: <p>If you want to use modular X.org from pkgsrc instead of your system's own X11
1.1 dsieger 2940: (<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...)
2941: you will have to add the following line into
1.10 hubertf 2942: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 2943: <pre class="programlisting">
1.4 rillig 2944: X11_TYPE=modular
1.1 dsieger 2945: </pre>
2946: </div>
1.41 asau 2947: <div class="sect1">
1.1 dsieger 2948: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2949: <a name="fetch-behind-firewall"></a>10.6. How to fetch files from behind a firewall</h2></div></div></div>
1.1 dsieger 2950: <p>If you are sitting behind a firewall which does not allow direct
2951: connections to Internet hosts (i.e. non-NAT), you may specify the
2952: relevant proxy hosts. This is done using an environment variable in the
2953: form of a URL, e.g. in Amdahl, the machine
1.23 wiz 2954: <span class="quote">“<span class="quote">orpheus.amdahl.com</span>”</span> is one of the firewalls, and it uses
1.1 dsieger 2955: port 80 as the proxy port number. So the proxy environment variables
2956: are:</p>
2957: <pre class="programlisting">
2958: ftp_proxy=ftp://orpheus.amdahl.com:80/
2959: http_proxy=http://orpheus.amdahl.com:80/
2960: </pre>
2961: </div>
1.41 asau 2962: <div class="sect1">
1.1 dsieger 2963: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2964: <a name="fetch-https"></a>10.7. How to fetch files from HTTPS sites</h2></div></div></div>
1.65 wiz 2965: <p>Some fetch tools are not prepared to support HTTPS by default
2966: (for example, the one in NetBSD 6.0), or the one installed by the
2967: pkgsrc bootstrap (to avoid an openssl dependency that low in the
2968: dependency graph).</p>
2969: <p>Usually you won't notice, because distribution files are
2970: mirrored weekly to <span class="quote">“<span class="quote">ftp.NetBSD.org</span>”</span>, but that might not
2971: be often enough if you are following pkgsrc-current. In that case, set
2972: <code class="varname">FETCH_USING</code> in your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file to
2973: <span class="quote">“<span class="quote">curl</span>”</span> or <span class="quote">“<span class="quote">wget</span>”</span>, which are both compiled
2974: with HTTPS support by default. Of course, these tools need to be
2975: installed before you can use them this way.</p>
2976: </div>
2977: <div class="sect1">
2978: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2979: <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.1 dsieger 2980: <p>This depends on which utility is used to retrieve distfiles. From
2981: <code class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned
2982: the first available command from the following list:</p>
1.41 asau 2983: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2984: <li class="listitem"><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li>
2985: <li class="listitem"><p><code class="filename">/usr/bin/ftp</code></p></li>
1.1 dsieger 2986: </ul></div>
2987: <p>On a default NetBSD installation, this will be
2988: <code class="filename">/usr/bin/ftp</code>, which automatically tries passive
2989: connections first, and falls back to active connections if the server
2990: refuses to do passive. For the other tools, add the following to your
1.10 hubertf 2991: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:
1.1 dsieger 2992: <code class="varname">PASSIVE_FETCH=1</code>.</p>
2993: <p>Having that option present will prevent
2994: <code class="filename">/usr/bin/ftp</code> from falling back to active
2995: transfers.</p>
2996: </div>
1.41 asau 2997: <div class="sect1">
1.1 dsieger 2998: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2999: <a name="fetching-all-distfiles"></a>10.9. How to fetch all distfiles at once</h2></div></div></div>
1.1 dsieger 3000: <p>You would like to download all the distfiles in a single batch
1.10 hubertf 3001: from work or university, where you can't run a <span class="command"><strong>make
1.25 spz 3002: 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.1 dsieger 3003: but downloading the entire directory may not be appropriate.</p>
1.10 hubertf 3004: <p>The answer here is to do a <span class="command"><strong>make fetch-list</strong></span> in
1.1 dsieger 3005: <code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the
3006: resulting list to your machine at work/school and use it there. If you
1.246 leot 3007: don't have a NetBSD-compatible <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/ftp.1"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
1.1 dsieger 3008: forget to set <code class="varname">FETCH_CMD</code> to something that fetches a
3009: URL:</p>
3010: <p>At home:</p>
3011: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
3012: <code class="prompt">%</code> <strong class="userinput"><code>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</code></strong>
3013: <code class="prompt">%</code> <strong class="userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong></pre>
3014: <p>At work:</p>
3015: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>sh /tmp/fetch.sh</code></strong></pre>
3016: <p>then tar up <code class="filename">/tmp/distfiles</code> and take it
3017: home.</p>
3018: <p>If you have a machine running NetBSD, and you want to get
3019: <span class="emphasis"><em>all</em></span> distfiles (even ones that aren't for your
3020: machine architecture), you can do so by using the above-mentioned
1.10 hubertf 3021: <span class="command"><strong>make fetch-list</strong></span> approach, or fetch the distfiles
1.1 dsieger 3022: directly by running:</p>
3023: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make mirror-distfiles</code></strong></pre>
3024: <p>If you even decide to ignore
3025: <code class="varname">NO_{SRC,BIN}_ON_{FTP,CDROM}</code>, then you can get everything
3026: by running:</p>
3027: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch NO_SKIP=yes</code></strong></pre>
3028: </div>
1.41 asau 3029: <div class="sect1">
1.1 dsieger 3030: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3031: <a name="tmac.andoc-missing"></a>10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 3032: /usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div>
1.207 leot 3033: <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.1 dsieger 3034: package, you get the error from make that it doesn't know how to make
3035: <code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that
1.23 wiz 3036: you don't have installed the <span class="quote">“<span class="quote">text</span>”</span> set (nroff, ...) from
1.1 dsieger 3037: the NetBSD base distribution on your machine. It is recommended to do
3038: that to format man pages.</p>
1.207 leot 3039: <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.1 dsieger 3040: can get away with setting <code class="varname">NOMAN=YES</code> either in the
1.10 hubertf 3041: environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 3042: </div>
1.41 asau 3043: <div class="sect1">
1.1 dsieger 3044: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3045: <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.1 dsieger 3046: <p>You didn't install the compiler set, <code class="filename">comp.tgz</code>,
3047: when you installed your NetBSD machine. Please get and install it, by
3048: extracting it in <code class="filename">/</code>:</p>
3049: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong>
3050: <code class="prompt">#</code> <strong class="userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong></pre>
3051: <p><code class="filename">comp.tgz</code> is part of every NetBSD release. Get
1.10 hubertf 3052: the one that corresponds to your release (determine via <span class="command"><strong>uname
1.1 dsieger 3053: -r</strong></span>).</p>
3054: </div>
1.41 asau 3055: <div class="sect1">
1.1 dsieger 3056: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.221 nia 3057: <a name="using-sudo-with-pkgsrc"></a>10.12. Using 'sudo' or `priv` with pkgsrc</h2></div></div></div>
1.1 dsieger 3058: <p>When installing packages as non-root user and using the just-in-time
1.246 leot 3059: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/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.1 dsieger 3060: password for each required package installed. To avoid this, the sudo
3061: package can be used, which does password caching over a limited time. To
1.221 nia 3062: use it, install <span class="command"><strong>sudo</strong></span> or
3063: <span class="command"><strong>priv</strong></span> (either as binary package, from
3064: <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.207 leot 3065: <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.10 hubertf 3066: following into your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, somewhere
1.1 dsieger 3067: <span class="emphasis"><em>after</em></span> the definition of the
3068: <code class="varname">LOCALBASE</code> variable:</p>
3069: <pre class="programlisting">
3070: .if exists(${LOCALBASE}/bin/sudo)
3071: SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
3072: .endif
3073: </pre>
3074: </div>
1.41 asau 3075: <div class="sect1">
1.1 dsieger 3076: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3077: <a name="faq.conf"></a>10.13. How do I change the location of configuration files?</h2></div></div></div>
1.1 dsieger 3078: <p>As the system administrator, you can choose where configuration files
3079: are installed. The default settings make all these files go into
3080: <code class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may
3081: be suboptimal depending on your expectations (e.g., a read-only,
3082: NFS-exported <code class="varname">PREFIX</code> with a need of per-machine
3083: configuration of the provided packages).</p>
3084: <p>In order to change the defaults, you can modify the
3085: <code class="varname">PKG_SYSCONFBASE</code> variable (in
1.10 hubertf 3086: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>) to point to your preferred configuration
1.1 dsieger 3087: directory; some common examples include <code class="filename">/etc</code> or
3088: <code class="filename">/etc/pkg</code>.</p>
3089: <p>Furthermore, you can change this value on a per-package basis by
3090: setting the <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> variable.
3091: <code class="varname">PKG_SYSCONFVAR</code>'s value usually matches the name of the
3092: package you would like to modify, that is, the contents of
3093: <code class="varname">PKGBASE</code>.</p>
3094: <p>Note that after changing these settings, you must rebuild and
3095: reinstall any affected packages.</p>
3096: </div>
1.41 asau 3097: <div class="sect1">
1.1 dsieger 3098: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3099: <a name="audit-packages"></a>10.14. Automated security checks</h2></div></div></div>
1.1 dsieger 3100: <p>Please be aware that there can often be bugs in third-party software,
3101: and some of these bugs can leave a machine vulnerable to exploitation by
3102: attackers. In an effort to lessen the exposure, the NetBSD packages team
3103: maintains a database of known-exploits to packages which have at one time
3104: been included in pkgsrc. The database can be downloaded automatically, and
3105: a security audit of all packages installed on a system can take place. To
1.14 jmcneill 3106: do this, refer to the following two tools (installed as part of the
1.207 leot 3107: <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.23 wiz 3108: <div class="orderedlist"><ol class="orderedlist" type="1">
3109: <li class="listitem">
1.20 snj 3110: <p><span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>, an easy way to
1.1 dsieger 3111: download a list of the security vulnerabilities information. This list
1.25 spz 3112: is kept up to date by the pkgsrc security team, and is distributed
3113: from the NetBSD ftp server:</p>
1.177 leot 3114: <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.1 dsieger 3115: </li>
1.23 wiz 3116: <li class="listitem"><p><span class="command"><strong>pkg_admin audit</strong></span>, an easy way to audit the
3117: current machine, checking each known vulnerability. If a
1.1 dsieger 3118: vulnerable package is installed, it will be shown by output to stdout,
3119: including a description of the type of vulnerability, and a URL
3120: containing more information.</p></li>
3121: </ol></div>
1.121 sevan 3122: <p>Use of these tools is strongly recommended!
1.202 nia 3123: 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.121 sevan 3124: reporting.</p>
3125: <p>If this database is installed, pkgsrc builds will use it to
3126: perform a security check before building any package.</p>
1.1 dsieger 3127: </div>
1.41 asau 3128: <div class="sect1">
1.1 dsieger 3129: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3130: <a name="ufaq-cflags"></a>10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</h2></div></div></div>
1.1 dsieger 3131: <p>When you add your own preferences to the
3132: <code class="varname">CFLAGS</code> variable in your
1.10 hubertf 3133: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, these flags are passed in
1.1 dsieger 3134: environment variables to the <code class="filename">./configure</code>
1.246 leot 3135: scripts and to <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>. Some package authors ignore the
1.1 dsieger 3136: <code class="varname">CFLAGS</code> from the environment variable by
3137: overriding them in the <code class="filename">Makefile</code>s of their
3138: package.</p>
3139: <p>Currently there is no solution to this problem. If you
3140: really need the package to use your <code class="varname">CFLAGS</code>
1.10 hubertf 3141: you should run <span class="command"><strong>make patch</strong></span> in the package
1.1 dsieger 3142: directory and then inspect any <code class="filename">Makefile</code> and
3143: <code class="filename">Makefile.in</code> for whether they define
3144: <code class="varname">CFLAGS</code> explicitly. Usually you can remove
1.23 wiz 3145: these lines. But be aware that some <span class="quote">“<span class="quote">smart</span>”</span>
1.1 dsieger 3146: programmers write so bad code that it only works for the
3147: specific combination of <code class="varname">CFLAGS</code> they have
3148: chosen.</p>
1.172 rillig 3149: <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>
3150: <pre class="programlisting">
3151: CPPFLAGS+= -Dpkgsrc___CPPFLAGS
3152: CFLAGS+= -Dpkgsrc___CFLAGS
3153: CXXFLAGS+= -Dpkgsrc___CXXFLAGS
3154: </pre>
3155: <p>Then run <span class="command"><strong>bmake show-all-configure show-all-build</strong></span>
3156: to see whether the above flags are passed to the actual build
3157: commands in general.</p>
3158: <p>To find out whether the flags are passed to individual compiler
3159: commands, have a look at the file <code class="filename">work/.work.log</code>. In
3160: most cases, the flags from the original command lines (the lines starting
3161: with <code class="literal">[*]</code>) are passed unmodified to the actual compiler
3162: (the lines starting with <code class="literal"><.></code>). If the flag is
3163: missing from the actual compiler command, it must have been removed by
1.184 rillig 3164: the <a class="link" href="#build.wrapper" title="13.10. The wrapper phase">pkgsrc compiler wrappers</a>.</p>
1.1 dsieger 3165: </div>
1.41 asau 3166: <div class="sect1">
1.1 dsieger 3167: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3168: <a name="ufaq-fail"></a>10.16. A package does not build. What shall I do?</h2></div></div></div>
1.23 wiz 3169: <div class="procedure"><ol class="procedure" type="1">
1.41 asau 3170: <li class="step"><p>Make sure that your copy of pkgsrc is consistent. A
1.1 dsieger 3171: case that occurs often is that people only update pkgsrc in
3172: parts, because of performance reasons. Since pkgsrc is one large
3173: system, not a collection of many small systems, there are
3174: sometimes changes that only work when the whole pkgsrc tree is
3175: updated.</p></li>
1.41 asau 3176: <li class="step"><p>Make sure that you don't have any CVS conflicts.
1.23 wiz 3177: Search for <span class="quote">“<span class="quote"><<<<<<</span>”</span> or
3178: <span class="quote">“<span class="quote">>>>>>></span>”</span> in all your pkgsrc
1.1 dsieger 3179: files.</p></li>
1.41 asau 3180: <li class="step"><p>Make sure that you don't have old copies of the packages
1.10 hubertf 3181: extracted. Run <span class="command"><strong>make clean clean-depends</strong></span> to
1.1 dsieger 3182: verify this.</p></li>
1.108 rillig 3183: <li class="step"><p>If you are a package developer who wants to invest
1.154 rillig 3184: 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.41 asau 3185: <li class="step"><p>If the problem still exists, write a mail to the
1.1 dsieger 3186: <code class="literal">pkgsrc-users</code> mailing list.</p></li>
3187: </ol></div>
3188: </div>
1.41 asau 3189: <div class="sect1">
1.1 dsieger 3190: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3191: <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.1 dsieger 3192: <p>You have modified a file from pkgsrc, and someone else has
3193: modified that same file afterwards in the CVS repository. Both changes
3194: are in the same region of the file, so when you updated pkgsrc, the
3195: <code class="literal">cvs</code> command marked the conflicting changes in the
3196: file. Because of these markers, the file is no longer a valid
3197: <code class="filename">Makefile</code>.</p>
3198: <p>Have a look at that file, and if you don't need your local changes
1.10 hubertf 3199: anymore, you can remove that file and run <span class="command"><strong>cvs -q update
1.1 dsieger 3200: -dP</strong></span> in that directory to download the current version.</p>
3201: </div>
3202: </div>
3203: </div>
1.41 asau 3204: <div class="part">
1.1 dsieger 3205: <div class="titlepage"><div><div><h1 class="title">
3206: <a name="developers-guide"></a>Part II. The pkgsrc developer's guide</h1></div></div></div>
1.41 asau 3207: <div class="partintro">
1.1 dsieger 3208: <div></div>
3209: <p>This part of the book deals with creating and
1.23 wiz 3210: modifying packages. It starts with a <span class="quote">“<span class="quote">HOWTO</span>”</span>-like
1.1 dsieger 3211: guide on creating a new package. The remaining chapters are more
3212: like a reference manual for pkgsrc.</p>
3213: <div class="toc">
3214: <p><b>Table of Contents</b></p>
1.100 leot 3215: <dl class="toc">
1.154 rillig 3216: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.184 rillig 3217: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.1 dsieger 3218: <dd><dl>
1.184 rillig 3219: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3220: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3221: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.1 dsieger 3222: <dd><dl>
1.184 rillig 3223: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3224: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3225: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3226: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3227: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.1 dsieger 3228: </dl></dd>
1.184 rillig 3229: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3230: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3231: <dd><dl>
3232: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3233: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3234: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
3235: </dl></dd>
3236: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3237: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 3238: </dl></dd>
1.184 rillig 3239: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.6 rillig 3240: <dd><dl>
1.184 rillig 3241: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
3242: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
3243: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
3244: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
3245: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 3246: <dd><dl>
1.184 rillig 3247: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
3248: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.6 rillig 3249: </dl></dd>
1.184 rillig 3250: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
3251: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
3252: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
3253: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
3254: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
3255: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3256: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3257: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
3258: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3259: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
3260: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
3261: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
3262: </dl></dd>
3263: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
3264: <dd><dl>
3265: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.6 rillig 3266: <dd><dl>
1.219 nia 3267: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
3268: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
3269: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.6 rillig 3270: </dl></dd>
1.184 rillig 3271: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
3272: <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.6 rillig 3273: </dl></dd>
1.184 rillig 3274: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 3275: <dd><dl>
1.184 rillig 3276: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
3277: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
3278: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
3279: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.6 rillig 3280: <dd><dl>
1.184 rillig 3281: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
3282: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
3283: <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>
3284: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 3285: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.6 rillig 3286: </dl></dd>
3287: </dl></dd>
1.184 rillig 3288: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.6 rillig 3289: <dd><dl>
1.184 rillig 3290: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
3291: <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>
3292: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
3293: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 3294: </dl></dd>
1.184 rillig 3295: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.6 rillig 3296: <dd><dl>
1.184 rillig 3297: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
3298: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
3299: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
3300: </dl></dd>
3301: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
3302: <dd><dl>
3303: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
3304: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3305: <dd><dl>
1.184 rillig 3306: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
3307: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.26 wiz 3308: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3309: and
3310: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3311: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3312: </dl></dd>
1.184 rillig 3313: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.241 rillig 3314: <dd><dl><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></dl></dd>
1.184 rillig 3315: </dl></dd>
3316: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.6 rillig 3317: <dd><dl>
1.184 rillig 3318: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
3319: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
3320: <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>
3321: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
3322: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
3323: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
3324: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
3325: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
3326: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.6 rillig 3327: </dl></dd>
1.184 rillig 3328: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
3329: <dd><dl>
3330: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
3331: <dd><dl>
3332: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
3333: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.6 rillig 3334: </dl></dd>
1.184 rillig 3335: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.6 rillig 3336: <dd><dl>
1.184 rillig 3337: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
3338: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
1.239 dholland 3339: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installation</a></span></dt>
3340: <dt><span class="sect2"><a href="#conf-files-declare">20.2.4. Declaring configuration files</a></span></dt>
3341: <dt><span class="sect2"><a href="#conf-files-disable">20.2.5. Disabling handling of configuration files</a></span></dt>
1.184 rillig 3342: </dl></dd>
3343: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
3344: <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>
3345: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
3346: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
3347: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
3348: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
3349: <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.154 rillig 3350: </dl></dd>
3351: <dt><span class="chapter"><a href="#fixes">21. Making your package work</a></span></dt>
3352: <dd><dl>
3353: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
3354: <dd><dl>
3355: <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>
3356: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
3357: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
3358: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
3359: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
3360: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
3361: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
3362: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
3363: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
3364: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
3365: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
3366: </dl></dd>
3367: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
3368: <dd><dl>
3369: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
3370: <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>
3371: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
3372: </dl></dd>
3373: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3374: <dd><dl>
3375: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
3376: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
3377: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.223 nia 3378: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 rillig 3379: </dl></dd>
3380: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
3381: <dd><dl>
3382: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
3383: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.205 wiz 3384: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 nia 3385: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
3386: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
3387: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
3388: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.154 rillig 3389: </dl></dd>
3390: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3391: <dd><dl>
3392: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
3393: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.172 rillig 3394: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
3395: <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>
3396: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.154 rillig 3397: </dl></dd>
3398: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3399: <dd><dl>
3400: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
3401: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
3402: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
3403: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
3404: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.203 nia 3405: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 rillig 3406: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
3407: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.203 nia 3408: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
3409: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
3410: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
3411: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
3412: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
3413: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
3414: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.1 dsieger 3415: emulation</a></span></dt>
1.203 nia 3416: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
3417: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.1 dsieger 3418: </dl></dd>
1.154 rillig 3419: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 3420: </dl></dd>
1.184 rillig 3421: <dt><span class="chapter"><a href="#gnome">22. GNOME packaging and porting</a></span></dt>
3422: <dd><dl>
3423: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
3424: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
3425: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
3426: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
3427: </dl></dd>
1.154 rillig 3428: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.1 dsieger 3429: <dd><dl>
1.154 rillig 3430: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
3431: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
3432: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
3433: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
3434: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
3435: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
3436: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
3437: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
3438: </dl></dd>
3439: <dt><span class="chapter"><a href="#devfaq">24. Frequently Asked Questions</a></span></dt>
1.1 dsieger 3440: </dl>
3441: </div>
3442: </div>
1.41 asau 3443: <div class="chapter">
1.1 dsieger 3444: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 3445: <a name="help-devel"></a>Chapter 11. Getting help</h2></div></div></div>
3446: <p>
3447: To get help when developing pkgsrc, the definitive source is this
3448: document, the pkgsrc guide. If you don't find anything here,
3449: there are alternatives:
3450: </p>
3451: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3452: <li class="listitem">
3453: <p>
3454: The built-in pkgsrc help, which is available after bootstrapping
3455: pkgsrc. Run <span class="command"><strong>bmake help topic=…</strong></span> to get
3456: help for any topic, such as a variable name like
3457: <code class="varname">BUILD_DEFS</code>, a make target like
3458: <span class="command"><strong>do-build</strong></span>, a missing C or C++ function like
3459: <span class="command"><strong>strcasecmp</strong></span> or any other topic.</p>
1.207 leot 3460: <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.154 rillig 3461: </li>
3462: <li class="listitem"><p>
1.163 rillig 3463: To see the value of a single variable, run <span class="command"><strong>bmake
3464: show-var VARNAME=<em class="replaceable"><code>X</code></em></strong></span>.
3465: </p></li>
3466: <li class="listitem"><p>
3467: To see the values of the most common variables, run
3468: <span class="command"><strong>bmake show-all</strong></span>. These variables are grouped by
3469: topic. To see the variables for a single topic, run
3470: <span class="command"><strong>bmake
3471: show-all-<em class="replaceable"><code>topic</code></em></strong></span>, for example
3472: <span class="command"><strong>bmake show-all-fetch</strong></span>.
3473: </p></li>
3474: <li class="listitem"><p>
1.154 rillig 3475: The tech-pkg mailing list, to which
3476: <a class="ulink" href="https://www.NetBSD.org/mailinglists/#tech-pkg" target="_top">you
3477: can subscribe</a> and then <a class="ulink" href="mailto:tech-pkg@NetBSD.org" target="_top">ask your
3478: questions</a>.</p></li>
3479: <li class="listitem"><p>The #pkgsrc IRC channel, which is accessible
3480: <a class="ulink" href="https://webchat.freenode.net/" target="_top">via a web browser</a>
3481: or by using a specialized chat program such as
3482: <a class="ulink" href="http://xchat.org/" target="_top">XChat</a>.
3483: Pick any user name and join the channel #pkgsrc.</p></li>
3484: </ul></div>
3485: </div>
3486: <div class="chapter">
3487: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 3488: <a name="components"></a>Chapter 12. Package components - files, directories and contents</h2></div></div></div>
1.1 dsieger 3489: <div class="toc">
3490: <p><b>Table of Contents</b></p>
1.100 leot 3491: <dl class="toc">
1.184 rillig 3492: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3493: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3494: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
3495: <dd><dl>
3496: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3497: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3498: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3499: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3500: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
3501: </dl></dd>
3502: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3503: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3504: <dd><dl>
3505: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3506: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3507: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
1.1 dsieger 3508: </dl></dd>
1.184 rillig 3509: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3510: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.1 dsieger 3511: </dl>
3512: </div>
1.184 rillig 3513: <p>Whenever you're preparing a package, there are a number of
3514: files involved which are described in the following
3515: sections.</p>
3516: <div class="sect1">
3517: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3518: <a name="components.Makefile"></a>12.1. <code class="filename">Makefile</code>
3519: </h2></div></div></div>
3520: <p>Building, installation and creation of a binary package are all
3521: controlled by the package's <code class="filename">Makefile</code>.
3522: The <code class="filename">Makefile</code> describes various things about
3523: a package, for example from where to get it, how to configure,
3524: build, and install it.</p>
3525: <p>A package <code class="filename">Makefile</code> contains several
3526: sections that describe the package.</p>
3527: <p>In the first section there are the following variables, which
3528: should appear exactly in the order given here. The order and
3529: grouping of the variables is mostly historical and has no further
3530: meaning.</p>
3531: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3532: <li class="listitem"><p><code class="varname">DISTNAME</code> is the basename of the
3533: distribution file to be downloaded from the package's
3534: website.</p></li>
3535: <li class="listitem"><p><code class="varname">PKGNAME</code> is the name of the
3536: package, as used by pkgsrc. You need to provide it if
3537: <code class="varname">DISTNAME</code> (which is the default) is not a good
3538: name for the package in pkgsrc or <code class="varname">DISTNAME</code> is not
3539: provided (no distribution file is required). Usually it is the pkgsrc
3540: directory name together with the version number. It must match the
3541: regular expression
3542: <code class="varname">^[A-Za-z0-9][A-Za-z0-9-_.+]*$</code>, that is, it
3543: starts with a letter or digit, and contains only letters, digits,
1.204 nia 3544: dashes, underscores, dots and plus signs.
3545: New packages should have entirely lower-case names, with the exception
3546: of some that must follow pre-existing conventions
3547: (e.g. R packages begin with <code class="varname">R-</code>).
3548: You can use the <code class="code">:tl</code> variable modifier to lower-case
3549: the package name.</p></li>
1.184 rillig 3550: <li class="listitem">
3551: <p><code class="varname">CATEGORIES</code> is a list of categories
3552: which the package fits in. You can choose any of the top-level
3553: directories of pkgsrc for it.</p>
3554: <p>Currently the following values are available for
3555: <code class="varname">CATEGORIES</code>. If more than
3556: one is used, they need to be separated by spaces:</p>
1.1 dsieger 3557: <pre class="programlisting">
1.184 rillig 3558: archivers cross geography meta-pkgs security
3559: audio databases graphics misc shells
3560: benchmarks devel ham multimedia sysutils
3561: biology editors inputmethod net textproc
3562: cad emulators lang news time
3563: chat finance mail parallel wm
3564: comms fonts math pkgtools www
3565: converters games mbone print x11
1.1 dsieger 3566: </pre>
3567: </li>
1.184 rillig 3568: <li class="listitem"><p><code class="varname">MASTER_SITES</code>,
3569: <code class="varname">DYNAMIC_MASTER_SITES</code>,
3570: <code class="varname">DIST_SUBDIR</code>, <code class="varname">EXTRACT_SUFX</code>
3571: and <code class="varname">DISTFILES</code> are discussed in detail in
3572: <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>
3573: </ul></div>
3574: <p>The second section contains information about separately
3575: downloaded patches, if any.
3576: </p>
3577: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3578: <li class="listitem"><p><code class="varname">PATCHFILES</code>:
3579: Name(s) of additional files that contain distribution patches.
3580: There is no default. pkgsrc will look for them at
3581: <code class="varname">PATCH_SITES</code>.
3582: They will automatically be uncompressed before patching if
3583: the names end with <code class="filename">.gz</code> or
3584: <code class="filename">.Z</code>.</p></li>
3585: <li class="listitem"><p><code class="varname">PATCH_SITES</code>:
3586: Primary location(s) for distribution patch files (see
3587: <code class="varname">PATCHFILES</code> above) if not found locally.</p></li>
3588: <li class="listitem"><p><code class="varname">PATCH_DIST_STRIP</code>:
1.246 leot 3589: an argument to <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> that sets the pathname strip count to
1.184 rillig 3590: help find the correct files to patch. It defaults to
3591: <span class="command"><strong>-p0</strong></span>.</p></li>
3592: </ul></div>
3593: <p>The third section contains the following variables.
3594: </p>
3595: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3596: <li class="listitem"><p><code class="varname">MAINTAINER</code> is the email
3597: address of the person who feels responsible for this package,
3598: and who is most likely to look at problems or questions regarding
1.246 leot 3599: this package which have been reported with <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a>.
1.184 rillig 3600: Other developers may contact the <code class="varname">MAINTAINER</code>
3601: before making changes to the package, but are not required to
3602: do so. When packaging a new program, set <code class="varname">MAINTAINER</code>
3603: to yourself. If you really can't maintain the package for future
3604: updates, set it to
3605: <code class="email"><<a class="email" href="mailto:pkgsrc-users@NetBSD.org">pkgsrc-users@NetBSD.org</a>></code>.</p></li>
3606: <li class="listitem"><p><code class="varname">OWNER</code> should be used instead
3607: of <code class="varname">MAINTAINER</code> when you do not want other
3608: developers to update or change the package without contacting
3609: you first. A package Makefile should contain one of
3610: <code class="varname">MAINTAINER</code> or <code class="varname">OWNER</code>, but
1.243 gutterid 3611: not both.</p></li>
1.184 rillig 3612: <li class="listitem"><p><code class="varname">HOMEPAGE</code> is a URL where users can
3613: find more information about the package.</p></li>
3614: <li class="listitem"><p><code class="varname">COMMENT</code> is a one-line
3615: description of the package (should not include the package
3616: name).</p></li>
3617: <li class="listitem"><p><code class="varname">LICENSE</code> indicates the license(s)
3618: 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>
3619: </ul></div>
3620: <p>Other variables that affect the build:
3621: </p>
3622: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3623: <p><code class="varname">WRKSRC</code>: The directory where the
3624: interesting distribution files of the package are found. The
3625: default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which
3626: works for most packages.</p>
3627: <p>If a package doesn't create a subdirectory for itself
3628: (most GNU software does, for instance), but extracts itself in
3629: the current directory, you should set
3630: <code class="varname">WRKSRC=${WRKDIR}</code>.</p>
3631: <p>If a package doesn't create a subdirectory with the
3632: name of <code class="varname">DISTNAME</code> but some different name,
3633: set <code class="varname">WRKSRC</code> to point to the proper name in
3634: <code class="filename">${WRKDIR}</code>, for example
3635: <code class="varname">WRKSRC=${WRKDIR}/${DISTNAME}/unix</code>. See
1.207 leot 3636: <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.184 rillig 3637: <p>The name of the working directory created by pkgsrc is
3638: taken from the <code class="varname">WRKDIR_BASENAME</code>
3639: variable. By default, its value is
3640: <code class="filename">work</code>. If you want to use the same
3641: pkgsrc tree for building different kinds of binary packages,
3642: you can change the variable according to your needs. Two
3643: other variables handle common cases of setting
3644: <code class="varname">WRKDIR_BASENAME</code> individually. If
3645: <code class="varname">OBJHOSTNAME</code> is defined in
3646: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the first component of
3647: the host's name is attached to the directory name. If
3648: <code class="varname">OBJMACHINE</code> is defined, the platform name
3649: is attached, which might look like
3650: <code class="filename">work.i386</code> or
3651: <code class="filename">work.sparc</code>.</p>
3652: </li></ul></div>
3653: <p>Please pay attention to the following gotchas:</p>
3654: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3655: <li class="listitem"><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are
3656: installed in compressed form by the package. For packages using
3657: BSD-style makefiles which honor MANZ, there is
3658: <code class="varname">MANCOMPRESSED_IF_MANZ</code>.</p></li>
3659: <li class="listitem"><p>Replace <code class="filename">/usr/local</code> with
3660: <span class="quote">“<span class="quote">${PREFIX}</span>”</span> in all files (see patches,
3661: below).</p></li>
3662: <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>
3663: </ul></div>
3664: </div>
1.41 asau 3665: <div class="sect1">
1.1 dsieger 3666: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 3667: <a name="components.distinfo"></a>12.2. <code class="filename">distinfo</code>
3668: </h2></div></div></div>
3669: <p>The <code class="filename">distinfo</code> file contains the message
3670: digest, or checksum, of each distfile needed for the package. This
3671: ensures that the distfiles retrieved from the Internet have not been
3672: corrupted during transfer or altered by a malign force to introduce
3673: a security hole. To provide maximum security, all distfiles are
1.243 gutterid 3674: protected using two different message digest algorithms (BLAKE2s
3675: and SHA512), as well as the file size.</p>
1.184 rillig 3676: <p>The <code class="filename">distinfo</code> file also contains the
3677: checksums for all the patches found in the
3678: <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
3679: are only applied intentionally and that they don't accidentally change,
3680: e.g. when merging different changes together. They also make sure that
3681: new patches are actually added to CVS and old ones are removed.
3682: Too see whether the patches and the <code class="filename">distinfo</code> file
3683: match, run <span class="command"><strong>pkglint</strong></span> after changing the patches.</p>
3684: <p>To regenerate the <code class="filename">distinfo</code> file, use the
3685: <span class="command"><strong>make distinfo</strong></span> command.</p>
3686: <p>Some packages have different sets of distfiles depending on
1.207 leot 3687: 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.184 rillig 3688: <code class="filename">distinfo</code> file and care should be taken when
3689: upgrading such a package to ensure distfile information is not
3690: lost.</p>
3691: </div>
3692: <div class="sect1">
3693: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3694: <a name="components.patches"></a>12.3. <code class="filename">patches/*</code>
3695: </h2></div></div></div>
3696: <p>Some packages don't work out-of-the box on the various
3697: platforms that are supported by pkgsrc. These packages need
3698: to be patched to make them work. The patch files can be
3699: found in the <code class="filename">patches/</code> directory.</p>
3700: <p>In the <span class="emphasis"><em>patch</em></span> phase, these patches are
3701: applied to the files in <code class="varname">WRKSRC</code> directory after
3702: extracting them, in alphabetic order.</p>
1.41 asau 3703: <div class="sect2">
1.1 dsieger 3704: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3705: <a name="components.patch.structure"></a>12.3.1. Structure of a single patch file</h3></div></div></div>
3706: <p>The <code class="filename">patch-*</code> files should be in
3707: <span class="command"><strong>diff -bu</strong></span> format, and apply without a fuzz to avoid
3708: problems. (To force patches to apply with fuzz you can set
3709: <code class="varname">PATCH_FUZZ_FACTOR=-F2</code>). Furthermore, each patch
3710: should contain only changes for a single file, and no file should be
3711: patched by more than one patch file. This helps to keep future
3712: modifications simple.</p>
3713: <p>Each patch file is structured as follows: In the first line,
3714: there is the RCS Id of the patch itself. The second line should be
3715: empty for aesthetic reasons. After that, there should be a comment for
3716: each change that the patch does. There are a number of standard
3717: cases:</p>
3718: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3719: <li class="listitem"><p>Patches for commonly known vulnerabilities should
3720: mention the vulnerability ID (CAN, CVE).</p></li>
3721: <li class="listitem"><p>Patches that change source code should mention the
3722: platform and other environment (for example, the compiler) that the
3723: patch is needed for.</p></li>
3724: </ul></div>
3725: <p>The patch should be commented so that any
3726: developer who knows the code of the application can make some use of
3727: the patch. Special care should be taken for the upstream developers,
3728: since we generally want that they accept our patches, so we have less
3729: work in the future.</p>
1.1 dsieger 3730: </div>
1.41 asau 3731: <div class="sect2">
1.1 dsieger 3732: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3733: <a name="components.patches.caveats"></a>12.3.2. Creating patch files</h3></div></div></div>
3734: <p>One important thing to mention is to pay attention that no RCS
3735: IDs get stored in the patch files, as these will cause problems when
3736: later checked into the NetBSD CVS tree. Use the
1.207 leot 3737: <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.184 rillig 3738: problems.</p>
3739: <p>For even more automation, we recommend using
3740: <span class="command"><strong>mkpatches</strong></span> from the same package to make a
1.222 gutterid 3741: whole set of patches. You just have to back up files before you
3742: edit them to <code class="filename">filename.orig</code>, e.g., with
1.184 rillig 3743: <span class="command"><strong>cp -p filename filename.orig</strong></span> or, easier, by
3744: using <span class="command"><strong>pkgvi</strong></span> again from the same package. If
3745: you upgrade a package this way, you can easily compare the new
3746: set of patches with the previously existing one with
3747: <span class="command"><strong>patchdiff</strong></span>. The files in <code class="filename">patches</code>
3748: are replaced by new files, so carefully check if you want to take all
3749: the changes.</p>
3750: <p>When you have finished a package, remember to generate
3751: the checksums for the patch files by using the <span class="command"><strong>make
3752: 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>
3753: <p>When adding a patch that corrects a problem in the
3754: distfile (rather than e.g. enforcing pkgsrc's view of where
3755: man pages should go), send the patch as a bug report to the
3756: maintainer. This benefits non-pkgsrc users of the package,
3757: and usually makes it possible to remove the patch in future
3758: version.</p>
3759: <p>The file names of the patch files are usually of the form
3760: <code class="filename">patch-<em class="replaceable"><code>path_to_file__with__underscores.c</code></em></code>.
3761: Many packages still use the previous convention
3762: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>,
3763: but new patches should be of the form containing the filename.
1.207 leot 3764: <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.184 rillig 3765: automatically.</p>
1.222 gutterid 3766: <p>When updating pre-existing patch files, if a file uses the old
3767: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>
3768: convention, it's best not to change it to the new form, as that will
3769: just cause churn that makes it harder to track changes to patching
3770: over time. Similarly, if a patch now applies at different line offsets,
3771: but still applies cleanly as-is, there's no need to update it, as that
3772: also unnecessarily complicates the patch history.</p>
1.17 imil 3773: </div>
1.160 brook 3774: <div class="sect2">
3775: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3776: <a name="components.patches.sources"></a>12.3.3. Sources where the patch files come from</h3></div></div></div>
3777: <p>If you want to share patches between multiple packages
3778: in pkgsrc, e.g. because they use the same distfiles, set
3779: <code class="varname">PATCHDIR</code> to the path where the patch files
3780: can be found, e.g.:</p>
3781: <pre class="programlisting">
3782: PATCHDIR= ../../editors/xemacs/patches
3783: </pre>
3784: <p>Patch files that are distributed by the author or other
3785: maintainers can be listed in
3786: <code class="varname">PATCHFILES</code>.</p>
3787: <p>If it is desired to store any patches that should not be
3788: committed into pkgsrc, they can be kept outside the pkgsrc
3789: tree in the <code class="filename">$LOCALPATCHES</code> directory. The
3790: directory tree there is expected to have the same
3791: <span class="quote">“<span class="quote">category/package</span>”</span> structure as pkgsrc, and
3792: patches are expected to be stored inside these dirs (also
3793: known as <code class="filename">$LOCALPATCHES/$PKGPATH</code>). For
3794: example, if you want to keep a private patch for
3795: <code class="filename">pkgsrc/graphics/png</code>, keep it in
3796: <code class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All
3797: files in the named directory are expected to be patch files,
3798: and <span class="emphasis"><em>they are applied after pkgsrc patches are
3799: applied</em></span>.</p>
1.160 brook 3800: </div>
3801: <div class="sect2">
3802: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3803: <a name="components.patches.guidelines"></a>12.3.4. Patching guidelines</h3></div></div></div>
3804: <p>When fixing a portability issue in the code do not use
3805: preprocessor magic to check for the current operating system nor
3806: platform. Doing so hurts portability to other platforms because
3807: the OS-specific details are not abstracted appropriately.</p>
3808: <p>The general rule to follow is: instead of checking for the
3809: operating system the application is being built on, check for the
3810: specific <span class="emphasis"><em>features</em></span> you need. For example,
3811: instead of assuming that kqueue is available under NetBSD and
3812: using the <code class="varname">__NetBSD__</code> macro to conditionalize
3813: kqueue support, add a check that detects kqueue itself —
3814: yes, this generally involves patching the
3815: <span class="command"><strong>configure</strong></span> script. There is absolutely nothing
3816: that prevents some OSes from adopting interfaces from other OSes
3817: (e.g. Linux implementing kqueue), something that the above checks
3818: cannot take into account.</p>
3819: <p>Of course, checking for features generally involves more
3820: work on the developer's side, but the resulting changes are
3821: cleaner and there are chances they will work on many other
3822: platforms. Not to mention that there are higher chances of being
3823: later integrated into the mainstream sources. Remember:
3824: <span class="emphasis"><em>It doesn't work unless it is right!</em></span></p>
3825: <p>Some typical examples:</p>
3826: <div class="table">
3827: <a name="patch-examples"></a><p class="title"><b>Table 12.1. Patching examples</b></p>
3828: <div class="table-contents"><table class="table" summary="Patching examples" border="1">
3829: <colgroup>
3830: <col>
3831: <col>
3832: <col>
3833: </colgroup>
3834: <thead><tr>
3835: <th>Where</th>
3836: <th>Incorrect</th>
3837: <th>Correct</th>
3838: </tr></thead>
3839: <tbody>
3840: <tr>
3841: <td>configure script</td>
3842: <td>
1.160 brook 3843: <pre class="programlisting">
1.184 rillig 3844: case ${target_os} in
3845: netbsd*) have_kvm=yes ;;
3846: *) have_kvm=no ;;
3847: esac
1.160 brook 3848: </pre>
1.184 rillig 3849: </td>
3850: <td>
1.160 brook 3851: <pre class="programlisting">
1.184 rillig 3852: AC_CHECK_LIB(kvm, kvm_open, have_kvm=yes, have_kvm=no)
1.160 brook 3853: </pre>
1.184 rillig 3854: </td>
3855: </tr>
3856: <tr>
3857: <td>C source file</td>
3858: <td>
1.1 dsieger 3859: <pre class="programlisting">
1.184 rillig 3860: #if defined(__NetBSD__)
3861: # include <sys/event.h>
3862: #endif
1.1 dsieger 3863: </pre>
1.184 rillig 3864: </td>
3865: <td>
1.1 dsieger 3866: <pre class="programlisting">
1.184 rillig 3867: #if defined(HAVE_SYS_EVENT_H)
3868: # include <sys/event.h>
3869: #endif
1.1 dsieger 3870: </pre>
1.184 rillig 3871: </td>
3872: </tr>
3873: <tr>
3874: <td>C source file</td>
3875: <td>
1.1 dsieger 3876: <pre class="programlisting">
1.184 rillig 3877: int
3878: monitor_file(...)
3879: {
3880: #if defined(__NetBSD__)
3881: int fd = kqueue();
3882: ...
3883: #else
3884: ...
3885: #endif
3886: }
1.1 dsieger 3887: </pre>
1.184 rillig 3888: </td>
3889: <td>
1.1 dsieger 3890: <pre class="programlisting">
1.184 rillig 3891: int
3892: monitor_file(...)
3893: {
3894: #if defined(HAVE_KQUEUE)
3895: int fd = kqueue();
3896: ...
3897: #else
3898: ...
3899: #endif
3900: }
1.1 dsieger 3901: </pre>
1.184 rillig 3902: </td>
3903: </tr>
3904: </tbody>
3905: </table></div>
3906: </div>
3907: <br class="table-break">
3908: </div>
3909: <div class="sect2">
3910: <div class="titlepage"><div><div><h3 class="title">
3911: <a name="components.patches.feedback"></a>12.3.5. Feedback to the author</h3></div></div></div>
3912: <p>Always, always, <span class="strong"><strong>always</strong></span>
3913: feed back any <span class="emphasis"><em>portability fixes</em></span> or
3914: improvements you do to a package to the mainstream developers.
3915: This is the only way to get their attention on portability issues
3916: and to ensure that future versions can be built out-of-the box on
3917: NetBSD. Furthermore, any user that gets newer distfiles will get
3918: the fixes straight from the packaged code.</p>
3919: <p>This generally involves cleaning up the patches
3920: (because sometimes the patches that are
3921: added to pkgsrc are quick hacks), filing bug reports in the
3922: appropriate trackers for the projects and working with the
3923: mainstream authors to accept your changes. It is
3924: <span class="emphasis"><em>extremely important</em></span> that you do it so that
3925: the packages in pkgsrc are kept simple and thus further changes
3926: can be done without much hassle.</p>
3927: <p>When you have done this, please add a URL to the upstream
3928: bug report to the patch comment.</p>
3929: <p>Support the idea of free software!</p>
3930: </div>
1.1 dsieger 3931: </div>
1.184 rillig 3932: <div class="sect1">
3933: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3934: <a name="other-mandatory-files"></a>12.4. Other mandatory files</h2></div></div></div>
3935: <div class="variablelist"><dl class="variablelist">
3936: <dt><span class="term"><code class="filename">DESCR</code></span></dt>
3937: <dd><p>A multi-line description of the piece of software. This should include
3938: any credits where they are due. Please bear in mind that others do not
3939: share your sense of humour (or spelling idiosyncrasies), and that others
3940: will read everything that you write here.</p></dd>
3941: <dt><span class="term"><code class="filename">PLIST</code></span></dt>
3942: <dd><p>This file governs the files that are installed on your
3943: system: all the binaries, manual pages, etc. There are other
3944: directives which may be entered in this file, to control the
3945: creation and deletion of directories, and the location of
3946: inserted files. See <a class="xref" href="#plist" title="Chapter 19. PLIST issues">Chapter 19, <i>PLIST issues</i></a> for more
3947: information.</p></dd>
3948: </dl></div>
3949: </div>
3950: <div class="sect1">
3951: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3952: <a name="components.optional"></a>12.5. Optional files</h2></div></div></div>
3953: <div class="sect2">
3954: <div class="titlepage"><div><div><h3 class="title">
3955: <a name="components.optional.bin"></a>12.5.1. Files affecting the binary package</h3></div></div></div>
3956: <div class="variablelist"><dl class="variablelist">
3957: <dt><span class="term"><code class="filename">INSTALL</code></span></dt>
3958: <dd>
1.246 leot 3959: <p>This shell script is invoked twice by <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>.
1.184 rillig 3960: First time after package extraction and before files are
3961: moved in place, the second time after the files to install
3962: are moved in place. This can be used to do any custom
3963: procedures not possible with @exec commands in
1.246 leot 3964: <code class="filename">PLIST</code>. See <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> and
3965: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/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.184 rillig 3966: Please note that you can modify variables in it easily by using
3967: <code class="varname">FILES_SUBST</code> in the package's
3968: <code class="filename">Makefile</code>:</p>
1.1 dsieger 3969: <pre class="programlisting">
1.184 rillig 3970: FILES_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 3971: </pre>
1.184 rillig 3972: <p>replaces "@SOMEVAR@" with <span class="quote">“<span class="quote">somevalue</span>”</span> in the
3973: <code class="filename">INSTALL</code>. By default, substitution is
3974: performed for <code class="varname">PREFIX</code>,
3975: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
3976: <code class="varname">VARBASE</code>, and a few others, type
3977: <span class="command"><strong>make help topic=FILES_SUBST</strong></span> for a
3978: complete list.</p>
3979: </dd>
3980: <dt><span class="term"><code class="filename">DEINSTALL</code></span></dt>
3981: <dd><p>This script is executed before and after any files are removed. It is
3982: this script's responsibility to clean up any additional messy details
3983: around the package's installation, since all pkg_delete knows is how to
3984: delete the files created in the original distribution.
1.246 leot 3985: See <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
3986: and <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.
1.184 rillig 3987: The same methods to replace variables can be used as for
3988: the <code class="filename">INSTALL</code> file.</p></dd>
3989: <dt><span class="term"><code class="filename">MESSAGE</code></span></dt>
3990: <dd>
3991: <p>This file is displayed after installation of the package.
1.198 leot 3992: While this was used often in the past, it has two
3993: problems: the display will be missed if many packages are
3994: intalled at once, and the person installing the package
3995: and the one using or configuring it may be different. It
3996: should therefore be used only in exceptional circumstances
3997: where lasting negative consequences would result from
3998: someone not reading it.</p>
3999: <p>MESSAGE should not be used for:</p>
4000: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
4001: <li class="listitem"><p>exhortations to read the documentation</p></li>
4002: <li class="listitem"><p>reminders to install rc.d files and set variables</p></li>
4003: <li class="listitem"><p>anything that should be explained in the
4004: installation/configuration documentation that should
4005: come with the package</p></li>
4006: </ul></div>
4007: <p>If the documentation provided by upstream needs
4008: enhancing, create e.g. files/README.pkgsrc and install it
4009: in the package's documentation directory.
4010: </p>
4011: <p>Note that MESSAGE is shown for all operating
4012: systems and all init systems. If a MESSAGE is necessary,
4013: it should be narrowed to only those operating systems and
4014: init systems to which it applies.</p>
4015: <p>Note that you can modify variables in it easily by using
1.184 rillig 4016: <code class="varname">MESSAGE_SUBST</code> in the package's
4017: <code class="filename">Makefile</code>:</p>
1.1 dsieger 4018: <pre class="programlisting">
1.184 rillig 4019: MESSAGE_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 4020: </pre>
1.184 rillig 4021: <p>replaces "${SOMEVAR}" with <span class="quote">“<span class="quote">somevalue</span>”</span> in
4022: <code class="filename">MESSAGE</code>. By default, substitution is
4023: performed for <code class="varname">PKGNAME</code>,
4024: <code class="varname">PKGBASE</code>, <code class="varname">PREFIX</code>,
4025: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
4026: <code class="varname">PKG_SYSCONFDIR</code>,
4027: <code class="varname">ROOT_GROUP</code>, and
4028: <code class="varname">ROOT_USER</code>.</p>
4029: <p>You can display a different or additional files by
4030: setting the <code class="varname">MESSAGE_SRC</code> variable. Its
4031: default is <code class="filename">MESSAGE</code>, if the file
4032: exists.</p>
4033: </dd>
4034: <dt><span class="term"><code class="filename">ALTERNATIVES</code></span></dt>
4035: <dd>
4036: <p>This file is used by the alternatives framework.
4037: It creates, configures, and destroys generic wrappers used to
4038: run programs with similar interfaces.
4039: See pkg_alternatives(8) from pkgtools/pkg_alternatives
4040: for more information.</p>
4041: <p>Each line of the file contains two filenames, first
4042: the wrapper and then the alternative provided by the package.
4043: Both paths are relative to <code class="varname">PREFIX</code>.</p>
4044: </dd>
4045: </dl></div>
4046: </div>
4047: <div class="sect2">
4048: <div class="titlepage"><div><div><h3 class="title">
4049: <a name="components.optional.build"></a>12.5.2. Files affecting the build process</h3></div></div></div>
4050: <div class="variablelist"><dl class="variablelist">
4051: <dt><span class="term"><code class="filename">Makefile.common</code></span></dt>
4052: <dd><p>This file contains arbitrary things that could
4053: also go into a <code class="filename">Makefile</code>, but its purpose is
4054: to be used by more than one package. This file should only be
4055: used when the packages that will use the file are known in
4056: advance. For other purposes it is often better to write a
4057: <code class="filename">*.mk</code> file and give it a good name that
4058: describes what it does.</p></dd>
4059: <dt><span class="term"><code class="filename">buildlink3.mk</code></span></dt>
4060: <dd><p>This file contains the dependency information
4061: for the buildlink3 framework (see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p></dd>
4062: <dt><span class="term"><code class="filename">hacks.mk</code></span></dt>
4063: <dd><p>This file contains workarounds for compiler bugs
4064: and similar things. It is included automatically by the pkgsrc
4065: infrastructure, so you don't need an extra
4066: <code class="literal">.include</code> line for
4067: it.</p></dd>
4068: <dt><span class="term"><code class="filename">options.mk</code></span></dt>
4069: <dd><p>This file contains the code for the
4070: package-specific options (see <a class="xref" href="#options" title="Chapter 16. Options handling">Chapter 16, <i>Options handling</i></a>) that can be
4071: selected by the user. If a package has only one or two options,
4072: it is equally acceptable to put the code directly into the
4073: <code class="filename">Makefile</code>.</p></dd>
4074: </dl></div>
4075: </div>
4076: <div class="sect2">
4077: <div class="titlepage"><div><div><h3 class="title">
4078: <a name="components.optional.none"></a>12.5.3. Files affecting nothing at all</h3></div></div></div>
4079: <div class="variablelist"><dl class="variablelist">
4080: <dt><span class="term"><code class="filename">README*</code></span></dt>
4081: <dd><p>These files do not take place in the creation of
4082: a package and thus are purely informative to the package
4083: developer.</p></dd>
4084: <dt><span class="term"><code class="filename">TODO</code></span></dt>
4085: <dd><p>This file contains things that need to be done
4086: to make the package even
4087: better.</p></dd>
4088: </dl></div>
4089: </div>
4090: </div>
4091: <div class="sect1">
4092: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4093: <a name="work-dir"></a>12.6. <code class="filename">work*</code>
4094: </h2></div></div></div>
4095: <p>When you type <span class="command"><strong>make</strong></span>, the distribution files are
4096: unpacked into the directory denoted by
4097: <code class="varname">WRKDIR</code>. It can be removed by running
4098: <span class="command"><strong>make clean</strong></span>. Besides the sources, this
4099: directory is also used to keep various timestamp files.
4100: The directory gets <span class="emphasis"><em>removed completely</em></span> on clean.
4101: The default is <code class="filename">${.CURDIR}/work</code>
4102: or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code>
4103: if <code class="varname">OBJMACHINE</code> is set.</p>
1.1 dsieger 4104: </div>
1.184 rillig 4105: <div class="sect1">
4106: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4107: <a name="files-dir"></a>12.7. <code class="filename">files/*</code>
4108: </h2></div></div></div>
4109: <p>If you have any files that you wish to be placed in the package
4110: prior to configuration or building, you can place these files here
4111: and use a <span class="command"><strong>${CP}</strong></span> command in the
4112: <span class="quote">“<span class="quote">post-extract</span>”</span> target to achieve this.</p>
4113: <p>If you want to share files in this way with other
4114: packages, set the <code class="varname">FILESDIR</code> variable to point
4115: to the other package's <code class="filename">files</code> directory,
4116: e.g.:</p>
1.1 dsieger 4117: <pre class="programlisting">
1.184 rillig 4118: FILESDIR= ../../editors/xemacs/files
1.1 dsieger 4119: </pre>
4120: </div>
4121: </div>
1.41 asau 4122: <div class="chapter">
1.1 dsieger 4123: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 4124: <a name="build"></a>Chapter 13. The build process</h2></div></div></div>
1.1 dsieger 4125: <div class="toc">
4126: <p><b>Table of Contents</b></p>
1.100 leot 4127: <dl class="toc">
1.184 rillig 4128: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
4129: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
4130: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
4131: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
4132: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
4133: <dd><dl>
4134: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
4135: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
4136: </dl></dd>
4137: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
4138: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
4139: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
4140: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
4141: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
4142: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
4143: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
4144: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
4145: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
4146: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
4147: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
4148: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
1.1 dsieger 4149: </dl>
4150: </div>
1.41 asau 4151: <div class="sect1">
1.1 dsieger 4152: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4153: <a name="build.intro"></a>13.1. Introduction</h2></div></div></div>
4154: <p>This chapter gives a detailed description on how a package is
4155: built. Building a package is separated into different
4156: <span class="emphasis"><em>phases</em></span> (for example <code class="varname">fetch</code>,
4157: <code class="varname">build</code>, <code class="varname">install</code>), all of which are
4158: described in the following sections. Each phase is split into
4159: so-called <span class="emphasis"><em>stages</em></span>, which take the name of the
4160: containing phase, prefixed by one of <code class="varname">pre-</code>,
4161: <code class="varname">do-</code> or <code class="varname">post-</code>. (Examples are
4162: <code class="varname">pre-configure</code>, <code class="varname">post-build</code>.) Most
4163: of the actual work is done in the <code class="varname">do-*</code> stages.</p>
4164: <p>Never override the regular targets (like
4165: <code class="varname">fetch</code>), if you have to, override the
4166: <code class="varname">do-*</code> ones instead.</p>
4167: <p>The basic steps for building a program are always the same. First
4168: the program's source (<span class="emphasis"><em>distfile</em></span>) must be brought to
4169: the local system and then extracted. After any pkgsrc-specific patches
4170: to compile properly are applied, the software can be configured, then
4171: built (usually by compiling), and finally the generated binaries, etc.
4172: can be put into place on the system.</p>
4173: <p>To get more details about what is happening at each step,
4174: you can set the <code class="varname">PKG_VERBOSE</code> variable, or the
4175: <code class="varname">PATCH_DEBUG</code> variable if you are just interested
4176: in more details about the <span class="emphasis"><em>patch</em></span> step.</p>
4177: </div>
4178: <div class="sect1">
4179: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4180: <a name="build.prefix"></a>13.2. Program location</h2></div></div></div>
4181: <p>Before outlining the process performed by the NetBSD package system in
4182: the next section, here's a brief discussion on where programs are
4183: installed, and which variables influence this.</p>
4184: <p>The automatic variable <code class="varname">PREFIX</code> indicates
4185: where all files of the final program shall be installed. It is
4186: usually set to <code class="varname">LOCALBASE</code>
4187: (<code class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code>
4188: for pkgs in the <code class="filename">cross</code> category. The value of
4189: <code class="varname">PREFIX</code> needs to be put
4190: into the various places in the program's source where paths to
4191: 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>
4192: <p>When choosing which of these variables to use,
4193: follow the following rules:</p>
1.41 asau 4194: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.184 rillig 4195: <li class="listitem"><p><code class="varname">PREFIX</code> always points to the location
4196: where the current pkg will be installed. When referring to a
4197: pkg's own installation path, use
4198: <span class="quote">“<span class="quote">${PREFIX}</span>”</span>.</p></li>
1.223 nia 4199: <li class="listitem"><p><code class="varname">LOCALBASE</code> is where all pkgs
1.184 rillig 4200: are installed. If you need to construct a -I or -L argument
4201: to the compiler to find includes and libraries installed by
1.223 nia 4202: another pkg, use <span class="quote">“<span class="quote">${LOCALBASE}</span>”</span>. The name
1.184 rillig 4203: <code class="varname">LOCALBASE</code> stems from FreeBSD, which
4204: installed all packages in <code class="filename">/usr/local</code>. As
4205: pkgsrc leaves <code class="filename">/usr/local</code> for the system
4206: administrator, this variable is a misnomer.</p></li>
4207: <li class="listitem"><p><code class="varname">X11BASE</code> is where the actual X11
4208: distribution (from xsrc, etc.) is installed. When looking for
4209: <span class="emphasis"><em>standard</em></span> X11 includes (not those
4210: installed by a package), use <span class="quote">“<span class="quote">${X11BASE}</span>”</span>.</p></li>
4211: <li class="listitem"><p>X11-based packages using imake must set
4212: <code class="varname">USE_IMAKE</code> to be installed correctly under
4213: <code class="varname">LOCALBASE</code>.</p></li>
4214: <li class="listitem"><p>Within <code class="filename">${PREFIX}</code>, packages should
1.246 leot 4215: install files according to <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/hier.7"><span class="citerefentry"><span class="refentrytitle">hier</span>(7)</span></a>, with the exception that
1.184 rillig 4216: manual pages go into <code class="filename">${PREFIX}/man</code>, not
4217: <code class="filename">${PREFIX}/share/man</code>.</p></li>
4218: </ul></div>
4219: </div>
4220: <div class="sect1">
4221: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4222: <a name="build.builddirs"></a>13.3. Directories used during the build process</h2></div></div></div>
4223: <p>When building a package, various directories are used to store
4224: source files, temporary files, pkgsrc-internal files, and so on. These
4225: directories are explained here.</p>
4226: <p>Some of the directory variables contain relative pathnames. There
4227: are two common base directories for these relative directories:
4228: <code class="varname">PKGSRCDIR/PKGPATH</code> is used for directories that are
4229: pkgsrc-specific. <code class="varname">WRKSRC</code> is used for directories
4230: inside the package itself.</p>
4231: <div class="variablelist"><dl class="variablelist">
4232: <dt><span class="term"><code class="varname">PKGSRCDIR</code></span></dt>
4233: <dd><p>This is an absolute pathname that points to the pkgsrc
4234: root directory. Generally, you don't need
4235: it.</p></dd>
4236: <dt><span class="term"><code class="varname">PKGDIR</code></span></dt>
4237: <dd><p>This is an absolute pathname that points to the
4238: current package.</p></dd>
4239: <dt><span class="term"><code class="varname">PKGPATH</code></span></dt>
1.228 gutterid 4240: <dd>
4241: <p>This is a pathname relative to
4242: <code class="varname">PKGSRCDIR</code> that points to the current package.
4243: It is defined after including <code class="filename">bsd.prefs.mk</code>
4244: and can be used in makefile fragments that are used by several
4245: packages to distinguish between these packages. Other variables
4246: that would serve the same purpose are <code class="varname">PKGBASE</code>
4247: and <code class="varname">PKGNAME</code>, but these are only defined after
4248: including <code class="filename">bsd.pkg.mk</code>, which is too
4249: late.</p>
4250: <p>In <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the pkgsrc user can use
4251: <code class="varname">PKGPATH</code> to tweak variables like
4252: <code class="varname">MAKE_JOBS</code> and
4253: <code class="varname">CFLAGS</code>.</p>
4254: </dd>
1.184 rillig 4255: <dt><span class="term"><code class="varname">WRKDIR</code></span></dt>
4256: <dd><p>This is an absolute pathname pointing to the directory
4257: where all work takes place. The distfiles are extracted to this
4258: directory. It also contains temporary directories and log files used by
4259: the various pkgsrc frameworks, like <span class="emphasis"><em>buildlink</em></span> or
4260: the <span class="emphasis"><em>wrappers</em></span>.</p></dd>
4261: <dt><span class="term"><code class="varname">WRKSRC</code></span></dt>
4262: <dd><p>This is an absolute pathname pointing to the directory
4263: where the distfiles are extracted. It is usually a direct subdirectory
4264: of <code class="varname">WRKDIR</code>, and often it's the only directory entry
4265: that isn't hidden. This variable may be changed by a package
4266: <code class="filename">Makefile</code>.</p></dd>
4267: </dl></div>
4268: <p>The <code class="varname">CREATE_WRKDIR_SYMLINK</code> definition takes either
4269: the value <span class="emphasis"><em>yes</em></span> or <span class="emphasis"><em>no</em></span> and defaults
4270: to <span class="emphasis"><em>no</em></span>. It indicates whether a symbolic link to the
4271: <code class="varname">WRKDIR</code> is to be created in the pkgsrc entry's directory.
4272: If users would like to have their pkgsrc trees behave in a
4273: read-only manner, then the value of
4274: <code class="varname">CREATE_WRKDIR_SYMLINK</code> should be set to
4275: <span class="emphasis"><em>no</em></span>.</p>
1.1 dsieger 4276: </div>
1.41 asau 4277: <div class="sect1">
1.1 dsieger 4278: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4279: <a name="build.running"></a>13.4. Running a phase</h2></div></div></div>
4280: <p>You can run a particular phase by typing <span class="command"><strong>make
1.228 gutterid 4281: <em class="replaceable"><code>phase</code></em></strong></span>, where
4282: <em class="replaceable"><code>phase</code></em> is the name of the phase. This will
4283: automatically run all phases that are required for this phase. The
4284: default phase is <code class="varname">build</code>, that is, when you run
4285: <span class="command"><strong>make</strong></span> without parameters in a package directory,
1.184 rillig 4286: the package will be built, but not installed.</p>
1.1 dsieger 4287: </div>
1.41 asau 4288: <div class="sect1">
1.1 dsieger 4289: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4290: <a name="build.fetch"></a>13.5. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
4291: <p>The first step in building a package is to fetch the
4292: distribution files (distfiles) from the sites that are providing
4293: them. This is the task of the <span class="emphasis"><em>fetch</em></span>
4294: phase.</p>
1.41 asau 4295: <div class="sect2">
1.1 dsieger 4296: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 4297: <a name="build.fetch.what"></a>13.5.1. What to fetch and where to get it from</h3></div></div></div>
4298: <p>In simple cases, <code class="varname">MASTER_SITES</code>
4299: defines all URLs from where the distfile, whose name is
4300: derived from the <code class="varname">DISTNAME</code> variable, is
4301: fetched. The more complicated cases are described
4302: below.</p>
4303: <p>The variable <code class="varname">DISTFILES</code> specifies
4304: the list of distfiles that have to be fetched. Its value
4305: defaults to <code class="literal">${DEFAULT_DISTFILES}</code> and
4306: its value is <code class="literal">${DISTNAME}${EXTRACT_SUFX}</code>,
4307: so that most packages don't need to define it at all.
4308: <code class="varname">EXTRACT_SUFX</code> is
4309: <code class="literal">.tar.gz</code> by default, but can be changed
4310: freely. Note that if your package requires additional
4311: distfiles to the default one, you cannot just append the
4312: additional filenames using the <code class="literal">+=</code>
4313: operator, but you have write for example:</p>
4314: <pre class="programlisting">
4315: DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
4316: </pre>
4317: <p>Each distfile is fetched from a list of sites, usually
4318: <code class="varname">MASTER_SITES</code>. If the package has multiple
4319: <code class="varname">DISTFILES</code> or multiple
4320: <code class="varname">PATCHFILES</code> from different sites, you can
4321: set
4322: <code class="varname">SITES.<em class="replaceable"><code>distfile</code></em></code>
4323: to the list of URLs where the file
4324: <code class="filename"><em class="replaceable"><code>distfile</code></em></code>
4325: (including the suffix) can be found.</p>
4326: <pre class="programlisting">
4327: DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
4328: DISTFILES+= foo-file.tar.gz
4329: SITES.foo-file.tar.gz= \
4330: https://www.somewhere.com/somehow/ \
4331: https://www.somewhereelse.com/mirror/somehow/
4332: </pre>
4333: <p>When actually fetching the distfiles, each item from
4334: <code class="varname">MASTER_SITES</code> or
4335: <code class="varname">SITES.*</code> gets the name of each distfile
4336: appended to it, without an intermediate slash. Therefore,
4337: all site values have to end with a slash or other separator
4338: character. This allows for example to set
4339: <code class="varname">MASTER_SITES</code> to a URL of a CGI script
4340: that gets the name of the distfile as a parameter. In this
4341: case, the definition would look like:</p>
4342: <pre class="programlisting">
4343: MASTER_SITES= https://www.example.com/download.cgi?file=
4344: </pre>
4345: <p> The exception to this rule are URLs starting with a dash.
4346: In that case the URL is taken as is, fetched and the result
4347: stored under the name of the distfile. You can use this style
4348: for the case when the download URL style does not match the
4349: above common case. For example, if permanent download URL is a
4350: redirector to the real download URL, or the download file name
4351: is offered by an HTTP Content-Disposition header. In the
4352: following example, <code class="filename">foo-1.0.0.tar.gz</code> will be
4353: created instead of the default
4354: <code class="filename">v1.0.0.tar.gz</code>.</p>
4355: <pre class="programlisting">
4356: DISTNAME= foo-1.0.0
4357: MASTER_SITES= -https://www.example.com/archive/v1.0.0.tar.gz
4358: </pre>
4359: <p>There are some predefined values for
4360: <code class="varname">MASTER_SITES</code>, which can be used in
4361: packages. The names of the variables should speak for
4362: themselves.</p>
4363: <table border="0" summary="Simple list" class="simplelist">
4364: <tr>
4365: <td>MASTER_SITE_APACHE</td>
4366: <td>MASTER_SITE_BACKUP</td>
4367: </tr>
4368: <tr>
4369: <td>MASTER_SITE_CRATESIO</td>
4370: <td>MASTER_SITE_CYGWIN</td>
4371: </tr>
4372: <tr>
4373: <td>MASTER_SITE_DEBIAN</td>
4374: <td>MASTER_SITE_FREEBSD</td>
4375: </tr>
4376: <tr>
4377: <td>MASTER_SITE_FREEBSD_LOCAL</td>
4378: <td>MASTER_SITE_GENTOO</td>
4379: </tr>
4380: <tr>
4381: <td>MASTER_SITE_GITHUB</td>
1.225 gutterid 4382: <td>MASTER_SITE_GITLAB</td>
4383: </tr>
4384: <tr>
1.184 rillig 4385: <td>MASTER_SITE_GNOME</td>
1.225 gutterid 4386: <td>MASTER_SITE_GNU</td>
1.184 rillig 4387: </tr>
4388: <tr>
4389: <td>MASTER_SITE_GNUSTEP</td>
1.225 gutterid 4390: <td>MASTER_SITE_HASKELL_HACKAGE</td>
1.184 rillig 4391: </tr>
4392: <tr>
4393: <td>MASTER_SITE_IFARCHIVE</td>
1.225 gutterid 4394: <td>MASTER_SITE_KDE</td>
1.184 rillig 4395: </tr>
4396: <tr>
4397: <td>MASTER_SITE_MOZILLA</td>
1.225 gutterid 4398: <td>MASTER_SITE_MOZILLA_ALL</td>
1.184 rillig 4399: </tr>
4400: <tr>
4401: <td>MASTER_SITE_MYSQL</td>
1.225 gutterid 4402: <td>MASTER_SITE_NETLIB</td>
1.184 rillig 4403: </tr>
4404: <tr>
4405: <td>MASTER_SITE_OPENBSD</td>
1.225 gutterid 4406: <td>MASTER_SITE_OPENOFFICE</td>
1.184 rillig 4407: </tr>
4408: <tr>
4409: <td>MASTER_SITE_OSDN</td>
1.225 gutterid 4410: <td>MASTER_SITE_PERL_CPAN</td>
1.184 rillig 4411: </tr>
4412: <tr>
4413: <td>MASTER_SITE_PGSQL</td>
1.225 gutterid 4414: <td>MASTER_SITE_PYPI</td>
1.184 rillig 4415: </tr>
4416: <tr>
4417: <td>MASTER_SITE_RUBYGEMS</td>
1.225 gutterid 4418: <td>MASTER_SITE_R_CRAN</td>
1.184 rillig 4419: </tr>
4420: <tr>
4421: <td>MASTER_SITE_SOURCEFORGE</td>
1.225 gutterid 4422: <td>MASTER_SITE_SUNSITE</td>
1.184 rillig 4423: </tr>
1.1 dsieger 4424: <tr>
1.184 rillig 4425: <td>MASTER_SITE_SUSE</td>
1.225 gutterid 4426: <td>MASTER_SITE_TEX_CTAN</td>
1.1 dsieger 4427: </tr>
4428: <tr>
1.184 rillig 4429: <td>MASTER_SITE_XCONTRIB</td>
1.225 gutterid 4430: <td>MASTER_SITE_XEMACS</td>
1.1 dsieger 4431: </tr>
4432: <tr>
1.184 rillig 4433: <td>MASTER_SITE_XORG</td>
1.225 gutterid 4434: <td> </td>
1.184 rillig 4435: </tr>
4436: </table>
4437: <p>Some explanations for the less self-explaining ones:
4438: <code class="varname">MASTER_SITE_BACKUP</code> contains backup sites
4439: 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
4440: 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>
4441: <p>If you choose one of these predefined sites, you may
4442: want to specify a subdirectory of that site. Since these
4443: macros may expand to more than one actual site, you
4444: <span class="emphasis"><em>must</em></span> use the following construct to
4445: specify a subdirectory:</p>
1.1 dsieger 4446: <pre class="programlisting">
1.184 rillig 4447: MASTER_SITES= ${MASTER_SITE_GNU:=subdirectory/name/}
4448: MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/}
1.1 dsieger 4449: </pre>
1.184 rillig 4450: <p>Note the trailing slash after the subdirectory
4451: name.</p>
4452: </div>
4453: <div class="sect2">
4454: <div class="titlepage"><div><div><h3 class="title">
4455: <a name="build.fetch.how"></a>13.5.2. How are the files fetched?</h3></div></div></div>
4456: <p>The <span class="emphasis"><em>fetch</em></span> phase makes sure that
4457: all the distfiles exist in a local directory
4458: (<code class="varname">DISTDIR</code>, which can be set by the pkgsrc
4459: user). If the files do not exist, they are fetched using
4460: commands of the form</p>
1.1 dsieger 4461: <pre class="programlisting">
1.184 rillig 4462: ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
4463: </pre>
4464: <p>where <code class="literal">${site}</code> varies through
4465: several possibilities in turn: first,
4466: <code class="varname">MASTER_SITE_OVERRIDE</code> is tried, then the
4467: sites specified in either <code class="varname">SITES.file</code> if
4468: defined, else <code class="varname">MASTER_SITES</code> or
4469: <code class="varname">PATCH_SITES</code>, as applies, then finally the
4470: value of <code class="varname">MASTER_SITE_BACKUP</code>. The order of
4471: all except the first and the last can be optionally sorted
4472: by the user, via setting either
4473: <code class="varname">MASTER_SORT_RANDOM</code>, and
4474: <code class="varname">MASTER_SORT_AWK</code> or
4475: <code class="varname">MASTER_SORT_REGEX</code>.</p>
4476: <p> The specific command and arguments used depend on the
4477: <code class="varname">FETCH_USING</code> parameter. The example above is
4478: for <code class="literal">FETCH_USING=custom</code>.</p>
4479: <p>The distfiles mirror run by the NetBSD Foundation uses the
4480: <span class="emphasis"><em>mirror-distfiles</em></span> target to mirror the
4481: distfiles, if they are freely distributable. Packages setting
4482: <code class="varname">NO_SRC_ON_FTP</code> (usually to
4483: <span class="quote">“<span class="quote">${RESTRICTED}</span>”</span>) will not have their distfiles
4484: mirrored.</p>
1.1 dsieger 4485: </div>
4486: </div>
1.184 rillig 4487: <div class="sect1">
4488: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4489: <a name="build.checksum"></a>13.6. The <span class="emphasis"><em>checksum</em></span> phase</h2></div></div></div>
4490: <p>After the distfile(s) are fetched, their checksum is
4491: generated and compared with the checksums stored in the
4492: distinfo file. If the checksums don't match, the build is
4493: aborted. This is to ensure the same distfile is used for
4494: building, and that the distfile wasn't changed, e.g. by some
4495: malign force, deliberately changed distfiles on the master
4496: distribution site or network lossage.</p>
1.1 dsieger 4497: </div>
1.41 asau 4498: <div class="sect1">
1.1 dsieger 4499: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4500: <a name="build.extract"></a>13.7. The <span class="emphasis"><em>extract</em></span> phase</h2></div></div></div>
4501: <p>When the distfiles are present on the local system, they
4502: need to be extracted, as they usually come in the form of some
4503: compressed archive format.</p>
4504: <p>By default, all <code class="varname">DISTFILES</code> are
4505: extracted. If you only need some of them, you can set the
4506: <code class="varname">EXTRACT_ONLY</code> variable to the list of those
4507: files.</p>
4508: <p>Extracting the files is usually done by a little
4509: program, <code class="filename">mk/extract/extract</code>, which
4510: already knows how to extract various archive formats, so most
4511: likely you will not need to change anything here. But if you
4512: need, the following variables may help you:</p>
1.41 asau 4513: <div class="variablelist"><dl class="variablelist">
1.184 rillig 4514: <dt><span class="term"><code class="varname">EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}</code></span></dt>
4515: <dd><p>Use these variables to override the default
4516: options for an extract command, which are defined in
4517: <code class="filename">mk/extract/extract</code>.</p></dd>
4518: <dt><span class="term"><code class="varname">EXTRACT_USING</code></span></dt>
4519: <dd><p>This variable can be set to
4520: <code class="literal">bsdtar</code>, <code class="literal">gtar</code>, <code class="literal">nbtar</code>
4521: (which is the default value), <code class="literal">pax</code>, or an
4522: absolute pathname pointing to the command with which tar
4523: archives should be extracted. It is preferred to choose bsdtar over gtar
4524: if NetBSD's pax-as-tar is not good enough.</p></dd>
1.1 dsieger 4525: </dl></div>
1.184 rillig 4526: <p>If the <code class="filename">extract</code> program doesn't
4527: serve your needs, you can also override the
4528: <code class="varname">EXTRACT_CMD</code> variable, which holds the
4529: command used for extracting the files. This command is
4530: executed in the <code class="filename">${WRKSRC}</code>
4531: directory. During execution of this command, the shell
4532: variable <code class="varname">extract_file</code> holds the absolute
4533: pathname of the file that is going to be extracted.</p>
4534: <p>And if that still does not suffice, you can override the
4535: <code class="varname">do-extract</code> target in the package
4536: Makefile.</p>
1.1 dsieger 4537: </div>
1.41 asau 4538: <div class="sect1">
1.1 dsieger 4539: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4540: <a name="build.patch"></a>13.8. The <span class="emphasis"><em>patch</em></span> phase</h2></div></div></div>
4541: <p>After extraction, all the patches named by the
4542: <code class="varname">PATCHFILES</code>, those present in the patches
4543: subdirectory of the package as well as in
4544: $LOCALPATCHES/$PKGPATH (e.g.
4545: <code class="filename">/usr/local/patches/graphics/png</code>) are
4546: applied. Patchfiles ending in <code class="filename">.Z</code> or
4547: <code class="filename">.gz</code> are uncompressed before they are
4548: applied, files ending in <code class="filename">.orig</code> or
4549: <code class="filename">.rej</code> are ignored. Any special options to
1.246 leot 4550: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
1.184 rillig 4551: <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.246 leot 4552: <p>By default <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given special arguments to make it
1.184 rillig 4553: fail if the expected text from the patch context is not found in the
4554: patched file. If that happens, fix the patch file by comparing it
4555: with the actual text in the file to be patched.</p>
1.1 dsieger 4556: </div>
1.41 asau 4557: <div class="sect1">
1.1 dsieger 4558: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4559: <a name="build.tools"></a>13.9. The <span class="emphasis"><em>tools</em></span> phase</h2></div></div></div>
4560: <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>.
4561: </p>
1.1 dsieger 4562: </div>
1.41 asau 4563: <div class="sect1">
1.1 dsieger 4564: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4565: <a name="build.wrapper"></a>13.10. The <span class="emphasis"><em>wrapper</em></span> phase</h2></div></div></div>
4566: <p>This phase creates wrapper programs for the compilers and
4567: linkers. The following variables can be used to tweak the
4568: wrappers.</p>
4569: <div class="variablelist"><dl class="variablelist">
4570: <dt><span class="term"><code class="varname">ECHO_WRAPPER_MSG</code></span></dt>
4571: <dd><p>The command used to print progress
4572: messages. Does nothing by default. Set to
4573: <code class="literal">${ECHO}</code> to see the progress
4574: messages.</p></dd>
4575: <dt><span class="term"><code class="varname">WRAPPER_DEBUG</code></span></dt>
4576: <dd><p>This variable can be set to
4577: <code class="literal">yes</code> (default) or <code class="literal">no</code>,
4578: depending on whether you want additional information in the
4579: wrapper log file.</p></dd>
4580: <dt><span class="term"><code class="varname">WRAPPER_UPDATE_CACHE</code></span></dt>
4581: <dd><p>This variable can be set to
4582: <code class="literal">yes</code> or <code class="literal">no</code>, depending
4583: on whether the wrapper should use its cache, which will
4584: improve the speed. The default value is
4585: <code class="literal">yes</code>, but is forced to
4586: <code class="literal">no</code> if the platform does not support
4587: it.</p></dd>
4588: <dt><span class="term"><code class="varname">WRAPPER_REORDER_CMDS</code></span></dt>
4589: <dd><p>A list of reordering commands. A reordering
4590: command has the form
4591: <code class="literal">reorder:l:<em class="replaceable"><code>lib1</code></em>:<em class="replaceable"><code>lib2</code></em></code>.
4592: It ensures that that
4593: <code class="literal">-l<em class="replaceable"><code>lib1</code></em></code> occurs
4594: before <code class="literal">-l<em class="replaceable"><code>lib2</code></em></code>.
4595: </p></dd>
4596: </dl></div>
4597: </div>
4598: <div class="sect1">
4599: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4600: <a name="build.configure"></a>13.11. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
4601: <p>Most pieces of software need information on the header
4602: files, system calls, and library routines which are available
4603: on the platform they run on. The process of determining this
4604: information is known as configuration, and is usually
4605: automated. In most cases, a script is supplied with the
4606: distfiles, and its invocation results in generation of header
4607: files, Makefiles, etc.</p>
4608: <p>If the package contains a configure script, this can be
4609: invoked by setting <code class="varname">HAS_CONFIGURE</code> to
4610: <span class="quote">“<span class="quote">yes</span>”</span>. If the configure script is a GNU autoconf
4611: script, you should set <code class="varname">GNU_CONFIGURE</code> to
1.187 rillig 4612: <span class="quote">“<span class="quote">yes</span>”</span> instead.</p>
4613: <p>In the <code class="literal">do-configure</code> stage, a rough
4614: equivalent of the following command is run. See
4615: <code class="filename">mk/configure/configure.mk</code>, target
4616: <code class="literal">do-configure-script</code> for the exact
4617: definition.</p>
4618: <pre class="programlisting">
4619: .for dir in ${CONFIGURE_DIRS}
4620: cd ${WRKSRC} && cd ${dir} \
4621: && env ${CONFIGURE_ENV} \
4622: ${CONFIG_SHELL} ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
1.184 rillig 4623: .endfor
1.1 dsieger 4624: </pre>
1.184 rillig 4625: <p><code class="varname">CONFIGURE_DIRS</code> (default:
4626: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4627: <code class="varname">WRKSRC</code>. In each of these directories, the
4628: configure script is run with the environment
4629: <code class="varname">CONFIGURE_ENV</code> and arguments
4630: <code class="varname">CONFIGURE_ARGS</code>. The variables
4631: <code class="varname">CONFIGURE_ENV</code>,
4632: <code class="varname">CONFIGURE_SCRIPT</code> (default:
4633: <span class="quote">“<span class="quote">./configure</span>”</span>) and
4634: <code class="varname">CONFIGURE_ARGS</code> may all be changed by the
4635: package.</p>
4636: <p>If the program uses the Perl way of configuration (mainly Perl
4637: modules, but not only), i.e. a file called
4638: <code class="filename">Makefile.PL</code>, it should include
4639: <code class="filename">../../lang/perl5/module.mk</code>. To set any parameter for
4640: <code class="filename">Makefile.PL</code> use the <code class="varname">MAKE_PARAMS</code>
4641: variable (e.g., <code class="literal">MAKE_PARAMS+=foo=bar</code></p>
4642: <p>If the program uses an <code class="filename">Imakefile</code>
4643: for configuration, the appropriate steps can be invoked by
4644: setting <code class="varname">USE_IMAKE</code> to
4645: <span class="quote">“<span class="quote">yes</span>”</span>. If you only need xmkmf, add it to <code class="varname">USE_TOOLS</code>.
4646: You can add variables to xmkmf's environment by adding them to the
4647: <code class="varname">SCRIPTS_ENV</code> variable.</p>
4648: <p>If the program uses <code class="filename">cmake</code>
4649: for configuration, the appropriate steps can be invoked by
1.233 wiz 4650: including <code class="filename">../../devel/cmake/build.mk</code>.
1.184 rillig 4651: You can add variables to cmake's environment by adding them to the
4652: <code class="varname">CONFIGURE_ENV</code> variable and arguments to cmake
4653: by adding them to the <code class="varname">CMAKE_ARGS</code> variable.
1.233 wiz 4654: If you want to add arguments only for particular stages, you can use the
4655: <code class="varname">CMAKE_CONFIGURE_ARGS</code>,
4656: <code class="varname">CMAKE_BUILD_ARGS</code>, and
4657: <code class="varname">CMAKE_INSTALL_ARGS</code> variables.
4658: You can set the <code class="varname">CONFIGURE_DIRS</code> variable to the
4659: directories in which CMake should be run, relative to
4660: <code class="varname">WRKSRC</code>. This defaults to to <span class="quote">“<span class="quote">.</span>”</span>.
4661: </p>
1.184 rillig 4662: <p>If there is no configure step at all, set
4663: <code class="varname">NO_CONFIGURE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 4664: </div>
1.41 asau 4665: <div class="sect1">
1.1 dsieger 4666: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4667: <a name="build.build"></a>13.12. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.187 rillig 4668: <p>For building a package, a rough equivalent of the following
4669: code is executed; see <code class="filename">mk/build/build.mk</code>, target
4670: <code class="literal">do-build</code> for the exact definition.</p>
1.1 dsieger 4671: <pre class="programlisting">
1.187 rillig 4672: .for dir in ${BUILD_DIRS}
4673: cd ${WRKSRC} && cd ${dir} \
1.184 rillig 4674: && env ${MAKE_ENV} \
1.187 rillig 4675: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${BUILD_MAKE_FLAGS} \
1.184 rillig 4676: -f ${MAKE_FILE} \
4677: ${BUILD_TARGET}
4678: .endfor
1.1 dsieger 4679: </pre>
1.184 rillig 4680: <p><code class="varname">BUILD_DIRS</code> (default:
4681: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4682: <code class="varname">WRKSRC</code>. In each of these directories,
4683: <code class="varname">MAKE_PROGRAM</code> is run with the environment
4684: <code class="varname">MAKE_ENV</code> and arguments
4685: <code class="varname">BUILD_MAKE_FLAGS</code>. The variables
4686: <code class="varname">MAKE_ENV</code>,
4687: <code class="varname">BUILD_MAKE_FLAGS</code>,
4688: <code class="varname">MAKE_FILE</code> and
4689: <code class="varname">BUILD_TARGET</code> may all be changed by the
4690: package.</p>
4691: <p>The default value of <code class="varname">MAKE_PROGRAM</code> is
4692: <span class="quote">“<span class="quote">gmake</span>”</span> if <code class="varname">USE_TOOLS</code> contains
4693: <span class="quote">“<span class="quote">gmake</span>”</span>, <span class="quote">“<span class="quote">make</span>”</span> otherwise. The
4694: default value of <code class="varname">MAKE_FILE</code> is
4695: <span class="quote">“<span class="quote">Makefile</span>”</span>, and <code class="varname">BUILD_TARGET</code>
4696: defaults to <span class="quote">“<span class="quote">all</span>”</span>.</p>
4697: <p>If there is no build step at all, set
4698: <code class="varname">NO_BUILD</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 4699: </div>
1.41 asau 4700: <div class="sect1">
1.1 dsieger 4701: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4702: <a name="build.test"></a>13.13. The <span class="emphasis"><em>test</em></span> phase</h2></div></div></div>
4703: <p>[TODO]</p>
1.1 dsieger 4704: </div>
1.41 asau 4705: <div class="sect1">
1.1 dsieger 4706: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4707: <a name="build.install"></a>13.14. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
4708: <p>Once the build stage has completed, the final step is to
4709: install the software in public directories, so users can
4710: access the programs and files.</p>
1.187 rillig 4711: <p>In the <span class="emphasis"><em>install</em></span> phase, a rough equivalent
4712: of the following code is executed; see
4713: <code class="filename">mk/install/install.mk</code>, target
4714: <code class="literal">do-install</code> for the exact definition. Additionally,
4715: before and after this code, several consistency checks are run
4716: against the files-to-be-installed, see
4717: <code class="filename">mk/check/*.mk</code> for details.</p>
4718: <pre class="programlisting">
4719: .for dir in ${INSTALL_DIRS}
4720: cd ${WRKSRC} && cd ${dir} \
4721: && env ${INSTALL_ENV} ${MAKE_ENV} \
4722: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${INSTALL_MAKE_FLAGS} \
4723: -f ${MAKE_FILE} ${INSTALL_TARGET}
1.184 rillig 4724: .endfor
1.1 dsieger 4725: </pre>
1.184 rillig 4726: <p>The variable's meanings are analogous to the ones in the
4727: <span class="emphasis"><em>build</em></span> phase.
4728: <code class="varname">INSTALL_DIRS</code> defaults to
4729: <code class="varname">BUILD_DIRS</code>. <code class="varname">INSTALL_TARGET</code>
4730: is <span class="quote">“<span class="quote">install</span>”</span> by default, plus
4731: <span class="quote">“<span class="quote">install.man</span>”</span> if <code class="varname">USE_IMAKE</code> is
4732: defined and <code class="varname">NO_INSTALL_MANPAGES</code> is not
4733: defined.</p>
4734: <p>In the <span class="emphasis"><em>install</em></span> phase, the following
4735: variables are useful. They are all variations of the
1.246 leot 4736: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that have the owner, group and
1.184 rillig 4737: permissions preset. <code class="varname">INSTALL</code> is the plain
4738: install command. The specialized variants, together with their
4739: intended use, are:</p>
4740: <div class="variablelist"><dl class="variablelist">
4741: <dt><span class="term"><code class="varname">INSTALL_PROGRAM_DIR</code></span></dt>
4742: <dd><p>directories that contain
4743: binaries</p></dd>
4744: <dt><span class="term"><code class="varname">INSTALL_SCRIPT_DIR</code></span></dt>
4745: <dd><p>directories that contain
4746: scripts</p></dd>
4747: <dt><span class="term"><code class="varname">INSTALL_LIB_DIR</code></span></dt>
4748: <dd><p>directories that contain shared and static
4749: libraries</p></dd>
4750: <dt><span class="term"><code class="varname">INSTALL_DATA_DIR</code></span></dt>
4751: <dd><p>directories that contain data
4752: files</p></dd>
4753: <dt><span class="term"><code class="varname">INSTALL_MAN_DIR</code></span></dt>
4754: <dd><p>directories that contain man
4755: pages</p></dd>
4756: <dt><span class="term"><code class="varname">INSTALL_GAME_DIR</code></span></dt>
4757: <dd><p>directories that contain data files for games
4758: </p></dd>
4759: <dt><span class="term"><code class="varname">INSTALL_PROGRAM</code></span></dt>
4760: <dd><p>binaries that can be stripped from debugging
4761: symbols</p></dd>
4762: <dt><span class="term"><code class="varname">INSTALL_SCRIPT</code></span></dt>
4763: <dd><p>binaries that cannot be
4764: stripped</p></dd>
4765: <dt><span class="term"><code class="varname">INSTALL_GAME</code></span></dt>
4766: <dd><p>game
4767: binaries</p></dd>
4768: <dt><span class="term"><code class="varname">INSTALL_LIB</code></span></dt>
4769: <dd><p>shared and static
4770: libraries</p></dd>
4771: <dt><span class="term"><code class="varname">INSTALL_DATA</code></span></dt>
4772: <dd><p>data files</p></dd>
4773: <dt><span class="term"><code class="varname">INSTALL_GAME_DATA</code></span></dt>
4774: <dd><p>data files for
4775: games</p></dd>
4776: <dt><span class="term"><code class="varname">INSTALL_MAN</code></span></dt>
4777: <dd><p>man pages</p></dd>
4778: </dl></div>
4779: <p>Some other variables are:</p>
4780: <div class="variablelist"><dl class="variablelist">
4781: <dt><span class="term"><code class="varname">INSTALL_UNSTRIPPED</code></span></dt>
1.246 leot 4782: <dd><p>If set to <code class="literal">yes</code>, do not run <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/strip.1"><span class="citerefentry"><span class="refentrytitle">strip</span>(1)</span></a>
1.184 rillig 4783: when installing binaries. Any debugging sections and symbols present in
4784: binaries will be preserved.
4785: </p></dd>
4786: <dt><span class="term"><code class="varname">INSTALLATION_DIRS</code></span></dt>
4787: <dd><p>A list of directories relative to
4788: <code class="varname">PREFIX</code> that are created by pkgsrc at the
4789: beginning of the <span class="emphasis"><em>install</em></span> phase.
4790: The package is supposed to create all needed directories itself
4791: before installing files to it and list all other directories here.
4792: </p></dd>
4793: </dl></div>
4794: <p>In the rare cases that a package shouldn't install anything,
4795: set <code class="varname">NO_INSTALL</code> to <span class="quote">“<span class="quote">yes</span>”</span>. This is
4796: mostly relevant for packages in the <code class="filename">regress</code>
4797: category.</p>
1.1 dsieger 4798: </div>
1.41 asau 4799: <div class="sect1">
1.1 dsieger 4800: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4801: <a name="build.package"></a>13.15. The <span class="emphasis"><em>package</em></span> phase</h2></div></div></div>
4802: <p>Once the install stage has completed, a binary package of
4803: the installed files can be built. These binary packages can be
4804: used for quick installation without previous compilation, e.g. by
4805: the <span class="command"><strong>make bin-install</strong></span> or by using
4806: <span class="command"><strong>pkg_add</strong></span>.</p>
4807: <p>By default, the binary packages are created in
4808: <code class="filename">${PACKAGES}/All</code> and symlinks are created in
4809: <code class="filename">${PACKAGES}/<em class="replaceable"><code>category</code></em></code>,
4810: one for each category in the <code class="varname">CATEGORIES</code>
4811: variable. <code class="varname">PACKAGES</code> defaults to
4812: <code class="filename">pkgsrc/packages</code>.</p>
1.1 dsieger 4813: </div>
1.41 asau 4814: <div class="sect1">
1.1 dsieger 4815: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4816: <a name="build.clean"></a>13.16. Cleaning up</h2></div></div></div>
4817: <p>Once you're finished with a package, you can clean the work
4818: directory by running <span class="command"><strong>make clean</strong></span>. If you want
4819: to clean the work directories of all dependencies too, use
4820: <span class="command"><strong>make clean-depends</strong></span>.</p>
1.1 dsieger 4821: </div>
1.41 asau 4822: <div class="sect1">
1.1 dsieger 4823: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4824: <a name="build.helpful-targets"></a>13.17. Other helpful targets</h2></div></div></div>
1.41 asau 4825: <div class="variablelist"><dl class="variablelist">
1.184 rillig 4826: <dt><span class="term">pre/post-*</span></dt>
4827: <dd>
4828: <p>For any of the main targets described in the previous
4829: section (configure, build, install, etc.), two auxiliary
4830: targets exist with
4831: <span class="quote">“<span class="quote">pre-</span>”</span> and <span class="quote">“<span class="quote">post-</span>”</span> used as a
4832: prefix for the main target's name. These targets are
4833: invoked before and after the main target is called,
4834: allowing extra configuration or installation steps be
4835: performed from a package's Makefile, for example, which
4836: a program's configure script or install target
4837: omitted.</p>
4838: <p>About 5% of the pkgsrc packages define their custom
4839: post-extract target, another 5% define pre-configure, and 10%
4840: define post-install. The other pre/post-* targets are defined
4841: even less often.</p>
4842: </dd>
4843: <dt><span class="term">do-*</span></dt>
1.1 dsieger 4844: <dd>
1.184 rillig 4845: <p>Should one of the main targets do the wrong thing,
4846: and should there be no variable to fix this, you can
4847: redefine it with the do-* target. (Note that redefining
4848: the target itself instead of the do-* target is a bad
4849: idea, as the pre-* and post-* targets won't be called
4850: anymore, etc.)</p>
4851: <p>About 15% of the pkgsrc packages override the default
4852: do-install, the other do-* targets are overridden even less
4853: often.</p>
1.1 dsieger 4854: </dd>
1.184 rillig 4855: <dt><span class="term">reinstall</span></dt>
1.1 dsieger 4856: <dd>
1.184 rillig 4857: <p>If you did a <span class="command"><strong>make install</strong></span> and
4858: you noticed some file was not installed properly, you
4859: can repeat the installation with this target, which will
4860: ignore the <span class="quote">“<span class="quote">already installed</span>”</span> flag.</p>
4861: <p>This is the default value of
4862: <code class="varname">DEPENDS_TARGET</code> except in the case of
4863: <span class="command"><strong>make update</strong></span> and <span class="command"><strong>make
4864: package</strong></span>, where the defaults are
4865: <span class="quote">“<span class="quote">package</span>”</span> and <span class="quote">“<span class="quote">update</span>”</span>,
4866: respectively.</p>
1.1 dsieger 4867: </dd>
1.184 rillig 4868: <dt><span class="term">deinstall</span></dt>
4869: <dd>
1.246 leot 4870: <p>This target does a <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> in the
1.184 rillig 4871: current directory, effectively de-installing the
4872: package. The following variables can be used to tune the
4873: behaviour:</p>
4874: <div class="variablelist"><dl class="variablelist">
4875: <dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt>
1.246 leot 4876: <dd><p>Add a "-v" to the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
1.184 rillig 4877: <dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt>
4878: <dd><p>Remove all packages that require (depend on)
4879: the given package. This can be used to remove any
4880: packages that may have been pulled in by a given
4881: package, e.g. if <span class="command"><strong>make deinstall
4882: DEINSTALLDEPENDS=1</strong></span> is done in
4883: <code class="filename">pkgsrc/x11/kde</code>, this is
4884: likely to remove whole KDE. Works by adding
1.246 leot 4885: <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
1.184 rillig 4886: command line.</p></dd>
4887: </dl></div>
4888: </dd>
4889: <dt><span class="term">bin-install</span></dt>
4890: <dd><p>Install a binary package from local disk and via FTP
4891: from a list of sites (see the
4892: <code class="varname">BINPKG_SITES</code> variable), and do a
4893: <span class="command"><strong>make package</strong></span> if no binary package is
4894: available anywhere. The arguments given to
4895: <span class="command"><strong>pkg_add</strong></span> can be set via
4896: <code class="varname">BIN_INSTALL_FLAGS</code> e.g., to do verbose
4897: operation, etc.</p></dd>
4898: <dt><span class="term">install-clean</span></dt>
4899: <dd><p>This target removes the state files for the "install" and later
4900: phases so that the "install" target may be re-invoked. This can be
4901: used after editing the PLIST to install the package without
4902: rebuilding it.</p></dd>
4903: <dt><span class="term">build-clean</span></dt>
4904: <dd><p>This target removes the state files for the "build" and later
4905: phases so that the "build" target may be re-invoked.</p></dd>
4906: <dt><span class="term">update</span></dt>
4907: <dd>
4908: <p>This target causes the current package to be
4909: updated to the latest version. The package and all
4910: depending packages first get de-installed, then current
4911: versions of the corresponding packages get compiled and
4912: installed. This is similar to manually noting which
4913: packages are currently installed, then performing a
4914: series of <span class="command"><strong>make deinstall</strong></span> and
4915: <span class="command"><strong>make install</strong></span> (or whatever
4916: <code class="varname">UPDATE_TARGET</code> is set to) for these
4917: packages.</p>
4918: <p>You can use the <span class="quote">“<span class="quote">update</span>”</span> target to
4919: resume package updating in case a previous <span class="command"><strong>make
4920: update</strong></span> was interrupted for some reason.
4921: However, in this case, make sure you don't call
4922: <span class="command"><strong>make clean</strong></span> or otherwise remove the
4923: list of dependent packages in <code class="varname">WRKDIR</code>.
4924: Otherwise, you lose the ability to automatically update
4925: the current package along with the dependent packages
4926: you have installed.</p>
4927: <p>Resuming an interrupted <span class="command"><strong>make
4928: update</strong></span> will only work as long as the package
4929: tree remains unchanged. If the source code for one of
4930: the packages to be updated has been changed, resuming
4931: <span class="command"><strong>make update</strong></span> will most certainly
4932: fail!</p>
4933: <p>The following variables can be used either on the
4934: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
4935: alter the behaviour of <span class="command"><strong>make
4936: update</strong></span>:</p>
4937: <div class="variablelist"><dl class="variablelist">
4938: <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt>
4939: <dd><p>Install target to recursively use for the
4940: updated package and the dependent packages.
4941: Defaults to <code class="varname">DEPENDS_TARGET</code> if
4942: set, <span class="quote">“<span class="quote">install</span>”</span> otherwise for
4943: <span class="command"><strong>make update</strong></span>. Other good
4944: targets are <span class="quote">“<span class="quote">package</span>”</span> or
4945: <span class="quote">“<span class="quote">bin-install</span>”</span>. Do not set this to
4946: <span class="quote">“<span class="quote">update</span>”</span> or you will get stuck in an
4947: endless loop!</p></dd>
4948: <dt><span class="term"><code class="varname">NOCLEAN</code></span></dt>
4949: <dd><p>Don't clean up after updating. Useful if
4950: you want to leave the work sources of the updated
4951: packages around for inspection or other purposes.
4952: Be sure you eventually clean up the source tree
4953: (see the <span class="quote">“<span class="quote">clean-update</span>”</span> target below)
4954: or you may run into troubles with old source code
4955: still lying around on your next
4956: <span class="command"><strong>make</strong></span> or <span class="command"><strong>make
4957: update</strong></span>.</p></dd>
4958: <dt><span class="term"><code class="varname">REINSTALL</code></span></dt>
4959: <dd><p>Deinstall each package before installing
4960: (making <code class="varname">DEPENDS_TARGET</code>). This
4961: may be necessary if the
4962: <span class="quote">“<span class="quote">clean-update</span>”</span> target (see below) was
4963: called after interrupting a running <span class="command"><strong>make
4964: update</strong></span>.</p></dd>
4965: <dt><span class="term"><code class="varname">DEPENDS_TARGET</code></span></dt>
4966: <dd><p>Allows you to disable recursion and hardcode
4967: the target for packages. The default is
4968: <span class="quote">“<span class="quote">update</span>”</span> for the update target,
4969: facilitating a recursive update of prerequisite
4970: packages. Only set
4971: <code class="varname">DEPENDS_TARGET</code> if you want to
4972: disable recursive updates. Use
4973: <code class="varname">UPDATE_TARGET</code> instead to just
4974: set a specific target for each package to be
4975: installed during <span class="command"><strong>make update</strong></span>
4976: (see above).</p></dd>
4977: </dl></div>
4978: </dd>
4979: <dt><span class="term">clean-update</span></dt>
4980: <dd>
4981: <p>Clean the source tree for all packages that would
4982: get updated if <span class="command"><strong>make update</strong></span> was called
4983: from the current directory. This target should not be
4984: used if the current package (or any of its depending
4985: packages) have already been de-installed (e.g., after
4986: calling <span class="command"><strong>make update</strong></span>) or you may lose
4987: some packages you intended to update. As a rule of
4988: thumb: only use this target <span class="emphasis"><em>before</em></span>
4989: the first time you run <span class="command"><strong>make update</strong></span>
4990: and only if you have a dirty package tree (e.g., if you
4991: used <code class="varname">NOCLEAN</code>).</p>
4992: <p>If you are unsure about whether your tree is
4993: clean, you can either perform a <span class="command"><strong>make
4994: clean</strong></span> at the top of the tree, or use the
4995: following sequence of commands from the directory of the
4996: package you want to update (<span class="emphasis"><em>before</em></span>
4997: running <span class="command"><strong>make update</strong></span> for the first
4998: time, otherwise you lose all the packages you wanted to
4999: update!):</p>
5000: <pre class="screen">
5001: <code class="prompt">#</code> <strong class="userinput"><code>make clean-update</code></strong>
5002: <code class="prompt">#</code> <strong class="userinput"><code>make clean CLEANDEPENDS=YES</code></strong>
5003: <code class="prompt">#</code> <strong class="userinput"><code>make update</code></strong>
5004: </pre>
5005: <p>The following variables can be used either on the
5006: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of
5007: <span class="command"><strong>make clean-update</strong></span>:</p>
5008: <div class="variablelist"><dl class="variablelist">
5009: <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt>
5010: <dd><p>After <span class="command"><strong>make clean</strong></span>, do not
5011: reconstruct the list of directories to update for
5012: this package. Only use this if <span class="command"><strong>make
5013: update</strong></span> successfully installed all
5014: packages you wanted to update. Normally, this is
5015: done automatically on <span class="command"><strong>make
5016: update</strong></span>, but may have been suppressed by
5017: the <code class="varname">NOCLEAN</code> variable (see
5018: above).</p></dd>
5019: </dl></div>
5020: </dd>
5021: <dt><span class="term">replace</span></dt>
5022: <dd>
5023: <p>Update the installation of the current package. This
5024: differs from update in that it does not replace dependent
1.207 leot 5025: 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.184 rillig 5026: target to work.</p>
5027: <p><span class="emphasis"><em>Be careful when using this
5028: target!</em></span> There are no guarantees that dependent
5029: packages will still work, in particular they will most
5030: certainly break if you <span class="command"><strong>make replace</strong></span> a
5031: library package whose shared library major version changed
5032: between your installed version and the new one. For this
5033: reason, this target is not officially supported and only
5034: recommended for advanced users.</p>
5035: </dd>
5036: <dt><span class="term">info</span></dt>
1.246 leot 5037: <dd><p>This target invokes <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a> for the current
1.184 rillig 5038: package. You can use this to check which version of a
5039: package is installed.</p></dd>
5040: <dt><span class="term">index</span></dt>
5041: <dd>
5042: <p>This is a top-level command, i.e. it should be used in
5043: the <code class="filename">pkgsrc</code> directory. It creates a
5044: database of all packages in the local pkgsrc tree, including
5045: dependencies, comment, maintainer, and some other useful
5046: information. Individual entries are created by running
5047: <span class="command"><strong>make describe</strong></span> in the packages'
5048: directories. This index file is saved as
5049: <code class="filename">pkgsrc/INDEX</code>. It can be displayed in
5050: verbose format by running <span class="command"><strong>make
5051: print-index</strong></span>. You can search in it with
5052: <span class="command"><strong>make search
5053: key=<em class="replaceable"><code>something</code></em></strong></span>. You can
5054: extract a list of all packages that depend on a particular
5055: one by running <span class="command"><strong>make show-deps
5056: PKG=<em class="replaceable"><code>somepackage</code></em></strong></span>.</p>
5057: <p>Running this command takes a very long time, some
5058: hours even on fast machines!</p>
5059: </dd>
5060: <dt><span class="term">readme</span></dt>
5061: <dd>
5062: <p>This target generates a
1.199 nia 5063: <code class="filename">index.html</code> file, which can be
1.207 leot 5064: 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.184 rillig 5065: contain references to any packages which are in the
5066: <code class="varname">PACKAGES</code> directory on the local
5067: host. The generated files can be made to refer to URLs
5068: based on <code class="varname">FTP_PKG_URL_HOST</code> and
5069: <code class="varname">FTP_PKG_URL_DIR</code>. For example, if I
1.199 nia 5070: wanted to generate <code class="filename">index.html</code>
1.184 rillig 5071: files which pointed to binary packages on the local
5072: machine, in the directory
5073: <code class="filename">/usr/packages</code>, set
5074: <code class="varname">FTP_PKG_URL_HOST=file://localhost</code> and
5075: <code class="varname">FTP_PKG_URL_DIR=/usr/packages</code>. The
5076: <code class="varname">${PACKAGES}</code> directory and its
5077: subdirectories will be searched for all the binary
5078: packages.</p>
5079: <p>The target can be run at the toplevel or in category
5080: directories, in which case it descends recursively.</p>
5081: </dd>
5082: <dt><span class="term">readme-all</span></dt>
5083: <dd><p>This is a top-level command, run it in
5084: <code class="filename">pkgsrc</code>. Use this target to create a
5085: file <code class="filename">README-all.html</code> which contains a
5086: list of all packages currently available in the NetBSD
5087: Packages Collection, together with the category they belong
5088: to and a short description. This file is compiled from the
1.199 nia 5089: <code class="filename">pkgsrc/*/index.html</code> files, so be sure
1.184 rillig 5090: to run this <span class="emphasis"><em>after</em></span> a <span class="command"><strong>make
5091: readme</strong></span>.</p></dd>
5092: <dt><span class="term">cdrom-readme</span></dt>
5093: <dd><p>This is very much the same as the
5094: <span class="quote">“<span class="quote">readme</span>”</span> target (see above), but is to be
5095: used when generating a pkgsrc tree to be written to a
5096: CD-ROM. This target also produces
1.199 nia 5097: <code class="filename">index.html</code> files, and can be made
1.184 rillig 5098: to refer to URLs based on
5099: <code class="varname">CDROM_PKG_URL_HOST</code> and
5100: <code class="varname">CDROM_PKG_URL_DIR</code>.</p></dd>
5101: <dt><span class="term">show-distfiles</span></dt>
5102: <dd><p>This target shows which distfiles and patchfiles
5103: are needed to build the package
5104: (<code class="varname">ALLFILES</code>, which contains all
5105: <code class="varname">DISTFILES</code> and
5106: <code class="varname">PATCHFILES</code>, but not
5107: <code class="filename">patches/*</code>).</p></dd>
5108: <dt><span class="term">show-downlevel</span></dt>
5109: <dd><p>This target shows nothing if the package is not
5110: installed. If a version of this package is installed,
5111: but is not the version provided in this version of
5112: pkgsrc, then a warning message is displayed. This target
5113: can be used to show which of your installed packages are
5114: downlevel, and so the old versions can be deleted, and
5115: the current ones added.</p></dd>
5116: <dt><span class="term">show-pkgsrc-dir</span></dt>
5117: <dd><p>This target shows the directory in the pkgsrc
5118: hierarchy from which the package can be built and
5119: installed. This may not be the same directory as the one
5120: from which the package was installed. This target is
5121: intended to be used by people who may wish to upgrade
5122: many packages on a single host, and can be invoked from
5123: the top-level pkgsrc Makefile by using the
5124: <span class="quote">“<span class="quote">show-host-specific-pkgs</span>”</span> target.</p></dd>
5125: <dt><span class="term">show-installed-depends</span></dt>
5126: <dd><p>This target shows which installed packages match
5127: the current package's <code class="varname">DEPENDS</code>. Useful
5128: if out of date dependencies are causing build
5129: problems.</p></dd>
5130: <dt><span class="term">print-build-depends-list</span></dt>
5131: <dd><p>This target shows the list of packages that the current package
5132: depends on for building.</p></dd>
5133: <dt><span class="term">print-run-depends-list</span></dt>
5134: <dd><p>This target shows the list of packages that the current package
5135: depends on for running.</p></dd>
5136: <dt><span class="term">check-shlibs</span></dt>
5137: <dd><p>After a package is installed, check all its
5138: binaries and (on ELF platforms) shared libraries to see
5139: if they find the shared libs they need. Run by default
5140: 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>
5141: <dt><span class="term">print-PLIST</span></dt>
5142: <dd>
5143: <p>After a <span class="quote">“<span class="quote">make install</span>”</span> from a new or
5144: upgraded pkg, this prints out an attempt to generate a
5145: new <code class="filename">PLIST</code> from a <span class="command"><strong>find
5146: -newer work/.extract_done</strong></span>. An attempt is made
5147: to care for shared libs etc., but it is
5148: <span class="emphasis"><em>strongly</em></span> recommended to review the
5149: result before putting it into
5150: <code class="filename">PLIST</code>. On upgrades, it's useful to
5151: diff the output of this command against an already
5152: existing <code class="filename">PLIST</code> file.</p>
1.246 leot 5153: <p>If the package installs files via <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/tar.1"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a> or
1.184 rillig 5154: other methods that don't update file access times, be
5155: sure to add these files manually to your
5156: <code class="filename">PLIST</code>, as the <span class="quote">“<span class="quote">find
5157: -newer</span>”</span> command used by this target won't catch
5158: them!</p>
5159: <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
5160: information on this target.</p>
5161: </dd>
5162: </dl></div>
5163: </div>
5164: </div>
5165: <div class="chapter">
5166: <div class="titlepage"><div><div><h2 class="title">
5167: <a name="creating"></a>Chapter 14. Creating a new pkgsrc package from scratch</h2></div></div></div>
5168: <div class="toc">
5169: <p><b>Table of Contents</b></p>
5170: <dl class="toc">
5171: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
5172: <dd><dl>
1.219 nia 5173: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
5174: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
5175: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.184 rillig 5176: </dl></dd>
5177: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
5178: <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>
5179: </dl>
5180: </div>
5181: <p>When you find a package that is not yet in pkgsrc, you
5182: most likely have a URL from where you can download the source
5183: code. Starting with this URL, creating a package involves only a
5184: few steps.</p>
5185: <div class="procedure"><ol class="procedure" type="1">
5186: <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
5187: enable the basic quality checks.</p></li>
5188: <li class="step">
1.207 leot 5189: <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.184 rillig 5190: install the utilities <span class="command"><strong>url2pkg</strong></span>,
5191: <span class="command"><strong>pkglint</strong></span>, <span class="command"><strong>pkgvi</strong></span> and
5192: <span class="command"><strong>mkpatches</strong></span>:</p>
5193: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
5194: <code class="prompt">$</code> <strong class="userinput"><code>(cd meta-pkgs/pkg_developer && bmake update)</code></strong></pre>
5195: </li>
5196: <li class="step">
5197: <p>Choose one of the top-level directories as the category in
5198: which you want to place your package. You can also create a directory of
1.219 nia 5199: your own (maybe called <code class="filename">local</code>). Change into that
5200: category directory:</p>
5201: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd <em class="replaceable"><code>category</code></em></code></strong></pre>
1.184 rillig 5202: </li>
5203: <li class="step">
1.219 nia 5204: <p>Run the program <span class="command"><strong>url2pkg</strong></span>, passing as
5205: argument the URL of the distribution file (in most cases a
5206: <code class="filename">.tar.gz</code> file). This will download the distribution
5207: file and create the necessary files of the package, based on what's in
5208: the distribution file:</p>
1.184 rillig 5209: <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>
5210: </li>
5211: <li class="step">
5212: <p>Examine the extracted files to determine the dependencies of
5213: your package. Ideally, this is mentioned in some
5214: <code class="filename">README</code> file, but things may differ. For each of
5215: these dependencies, look where it exists in pkgsrc, and if there is a
5216: file called <code class="filename">buildlink3.mk</code> in that directory, add a
5217: line to your package <code class="filename">Makefile</code> which includes that
5218: file just before the last line. If the
5219: <code class="filename">buildlink3.mk</code> file does not exist, it must be
5220: created first. The <code class="filename">buildlink3.mk</code> file makes sure
5221: that the package's include files and libraries are provided.</p>
1.219 nia 5222: <p>If you just need binaries from a dependent package, add a
1.184 rillig 5223: <code class="varname">DEPENDS</code> line to the Makefile, which specifies the
5224: version of the dependency and where it can be found in pkgsrc. This line
5225: should be placed in the third paragraph. If the dependency is only
5226: needed for building the package, but not when using it, use
5227: <code class="varname">TOOL_DEPENDS</code> or <code class="varname">BUILD_DEPENDS</code>
5228: instead of <code class="varname">DEPENDS</code>.
5229: The difference between <code class="varname">TOOL_DEPENDS</code> and
5230: <code class="varname">BUILD_DEPENDS</code> occurs when cross-compiling:
5231: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
1.219 nia 5232: packages, i.e. packages for the platform where the package is built;
1.184 rillig 5233: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.219 nia 5234: packages, i.e. packages for the platform for which the package
5235: is built. There is also <code class="varname">TEST_DEPENDS</code>, which
5236: specifies a dependency used only for testing the resulting package
5237: built, using the upstream project's included test suite, on the native
5238: platform.
1.184 rillig 5239: Your package may then look like this:</p>
5240: <pre class="programlisting">
5241: [...]
5242:
5243: TOOL_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
5244: DEPENDS+= screen-[0-9]*:../../misc/screen
5245: DEPENDS+= screen>=4.0:../../misc/screen
5246:
5247: [...]
5248:
5249: .include "../../<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>package</code></em>/buildlink3.mk"
5250: .include "../../devel/glib2/buildlink3.mk"
5251: .include "../../mk/bsd.pkg.mk"
5252: </pre>
5253: </li>
5254: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need
5255: to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't
5256: know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint
5257: --explain</strong></span> or <span class="command"><strong>pkglint -e</strong></span>, which outputs
5258: additional explanations.</p></li>
5259: <li class="step"><p>In many cases the package is not yet ready to build. You can
5260: 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
5261: over there, you can hopefully continue here.</p></li>
5262: <li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working
5263: directory from the extracted files. Besides these files, a lot of cache
1.219 nia 5264: files and other system information have been saved in the working
5265: directory, which may have become outdated after you edited the
1.184 rillig 5266: <code class="filename">Makefile</code>.</p></li>
5267: <li class="step">
5268: <p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For
5269: 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.219 nia 5270: <p>If the extracted files from the package need to be fixed, run
5271: multiple rounds of these commands:</p>
5272: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>bmake</code></strong>
1.184 rillig 5273: <code class="prompt">$</code> <strong class="userinput"><code>pkgvi ${WRKSRC}/some/file/that/does/not/compile</code></strong>
5274: <code class="prompt">$</code> <strong class="userinput"><code>mkpatches</code></strong>
1.219 nia 5275: <code class="prompt">$</code> <strong class="userinput"><code>bmake mps</code></strong>
5276: <code class="prompt">$</code> <strong class="userinput"><code>bmake clean</code></strong></pre>
1.184 rillig 5277: </li>
5278: <li class="step"><p>When the package builds fine, the next step is to install
5279: the package. Run <span class="command"><strong>bmake install</strong></span> and hope that
5280: everything works.</p></li>
5281: <li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which
5282: contains a list of the files that are installed by the package, is
5283: nearly empty. Run <span class="command"><strong>bmake print-PLIST
5284: >PLIST</strong></span> to generate a probably correct list. Check
5285: the file using your preferred text editor to see if the list of
5286: files looks plausible.</p></li>
5287: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated
5288: <code class="filename">PLIST</code> contains garbage or not.</p></li>
5289: <li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package
5290: had been registered in the database of installed files, but with an
5291: empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span>
5292: and <span class="command"><strong>bmake install</strong></span> again. Now the package is
5293: registered with the list of files from
5294: <code class="filename">PLIST</code>.</p></li>
5295: <li class="step"><p>Run <span class="command"><strong>bmake clean update</strong></span> to run everything
5296: from above again in a single step, making sure that the PLIST is correct
5297: and the whole package is created as intended.</p></li>
1.219 nia 5298: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see if there's anything
5299: left to do.</p></li>
1.184 rillig 5300: <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>
5301: </ol></div>
5302: <div class="sect1">
5303: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5304: <a name="creating.common"></a>14.1. Common types of packages</h2></div></div></div>
5305: <div class="sect2">
5306: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5307: <a name="creating.python-module"></a>14.1.1. Python modules and programs</h3></div></div></div>
1.184 rillig 5308: <p>Python modules and programs packages are easily created using a
5309: set of predefined variables.</p>
5310: <p>
5311: If some Python versions are not supported by the software, set the
5312: <code class="varname">PYTHON_VERSIONS_INCOMPATIBLE</code> variable to the Python versions
5313: that are not supported, e.g.
5314: </p>
5315: <pre class="programlisting">
5316: PYTHON_VERSIONS_INCOMPATIBLE= 27
5317: </pre>
5318: <p>
1.249 gutterid 5319: If the packaged software is a Python module, include
1.248 wiz 5320: <code class="filename">../../lang/python/wheel.mk</code>.
1.215 wiz 5321: </p>
1.248 wiz 5322: <p>The package directory should be called
1.184 rillig 5323: <span class="quote">“<span class="quote">py-software</span>”</span> and <code class="varname">PKGNAME</code> should be set to
5324: <span class="quote">“<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>”</span>, e.g.
5325: </p>
5326: <pre class="programlisting">
5327: DISTNAME= foopymodule-1.2.10
5328: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
5329: </pre>
1.226 gutterid 5330: <p>
5331: For software in PyPi, the name should match what PyPi specifies for
5332: "pip install software".
5333: </p>
1.184 rillig 5334: <p>If it is an application, include
5335: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>”</span>.
5336: In order to correctly set the path to the Python interpreter, use the
5337: <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
5338: (paths relative to <code class="varname">WRKSRC</code>) that must be corrected.
5339: For example:
5340: </p>
5341: <pre class="programlisting">
5342: REPLACE_PYTHON= *.py
5343: </pre>
5344: <p>Some Python modules have separate distributions for Python-2.x
5345: and Python-3.x support. In pkgsrc this is handled by the
5346: <code class="filename">versioned_dependencies.mk</code> file. Set
5347: <code class="varname">PYTHON_VERSIONED_DEPENDENCIES</code> to the list of
5348: packages that should be depended upon and include
5349: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/versioned_dependencies.mk</code></span>”</span>,
5350: then the pkgsrc infrastructure will depend on the appropriate package
5351: version. For example:
5352: </p>
5353: <pre class="programlisting">
5354: PYTHON_VERSIONED_DEPENDENCIES=dialog
5355: </pre>
5356: <p>
5357: Look inside <code class="filename">versioned_dependencies.mk</code> for a list
5358: of supported packages.</p>
5359: </div>
5360: <div class="sect2">
5361: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5362: <a name="creating.R-package"></a>14.1.2. R packages</h3></div></div></div>
1.184 rillig 5363: <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>
5364: are handled automatically by <span class="command"><strong>R2pkg</strong></span>, which is
1.207 leot 5365: 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.184 rillig 5366: Individual packages (and optionally their dependencies) may be created
5367: and updated. R packages generally follow the same form, and most of
5368: the relevant information needed is contained in a
5369: <code class="filename">DESCRIPTION</code> file as part of each R package on
5370: <a class="ulink" href="https://cran.r-project.org/web/packages/available_packages_by_name.html" target="_top">CRAN</a>.
5371: Consequently, <span class="command"><strong>R2pkg</strong></span> downloads that information and
5372: creates or updates a package in the canonical form. The resulting
5373: package should be reviewed for correctness.</p>
5374: </div>
5375: <div class="sect2">
5376: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5377: <a name="creating.TeX-package"></a>14.1.3. TeXlive packages</h3></div></div></div>
1.184 rillig 5378: <p>TeXlive packages from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> are handled automatically by
1.207 leot 5379: <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.184 rillig 5380: <p>If the TeXlive package name is not known, it may be useful to
5381: search <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>. A
5382: <span class="quote">“<span class="quote">Contained in</span>”</span> field on the package page typically
5383: 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
5384: archive</a>.</p>
5385: <p>If the TeXlive package name is known, download the files from
5386: the <a class="ulink" href="https://www.ctan.org/tex-archive/systems/texlive/tlnet/archive" target="_top">TeXlive
5387: archive</a>. For package <code class="filename">foo</code>, you will need
5388: to download <code class="filename">foo.tar.xz</code>. Most TeXlive packages
5389: also have associated documentation packages, so download
5390: <code class="filename">foo.doc.tar.xz</code> at the same time. These files
5391: should be placed in the appropriate category directory, which is often
5392: but not always <code class="filename">print</code>. Then run the following
5393: command in the category directory.</p>
5394: <pre class="programlisting">
5395: texlive2pkg foo.tar.xz foo.doc.tar.xz
5396: </pre>
5397: <p>This will create two packages, <code class="filename">tex-foo</code> and
5398: <code class="filename">tex-foo-doc</code>. Be sure to check that both packages
5399: are correct.</p>
5400: <p>Finally, <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>
5401: currently does not include version information in package filenames
5402: and changes their contents periodically when updates occur.
5403: Consequently, pkgsrc avoids downloading distfiles directly from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> and instead relies on the
5404: pkgsrc archives. For each new or updated TeXlive package, e.g., the
5405: main one and the corresponding documentation, upload the distfiles
5406: with the following command in each package directory.</p>
5407: <pre class="programlisting">
5408: make upload-distfiles
5409: </pre>
5410: </div>
5411: </div>
5412: <div class="sect1">
5413: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5414: <a name="creating.examples"></a>14.2. Examples</h2></div></div></div>
5415: <div class="sect2">
5416: <div class="titlepage"><div><div><h3 class="title">
5417: <a name="creating.nvu"></a>14.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div>
5418: <div class="sect3">
5419: <div class="titlepage"><div><div><h4 class="title">
5420: <a name="creating.nvu.init"></a>14.2.1.1. The initial package</h4></div></div></div>
5421: <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
5422: that the <span class="quote">“<span class="quote">nvu</span>”</span> package has not yet been imported into
5423: pkgsrc. As the description says it has to do with the web, the obvious
5424: choice for the category is <span class="quote">“<span class="quote">www</span>”</span>.</p>
5425: <pre class="programlisting">
5426: <code class="prompt">$</code> mkdir www/nvu
5427: <code class="prompt">$</code> cd www/nvu
5428: </pre>
5429: <p>The web site says that the sources are available as a tar file, so
5430: I fed that URL to the <span class="command"><strong>url2pkg</strong></span> program:</p>
5431: <pre class="programlisting">
5432: <code class="prompt">$</code> url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5433: </pre>
5434: <p>My editor popped up, and I added a <code class="varname">PKGNAME</code> line
5435: below the <code class="varname">DISTNAME</code> line, as the package name should
5436: not have the word <span class="quote">“<span class="quote">sources</span>”</span> in it. I also filled in the
5437: <code class="varname">MAINTAINER</code>, <code class="varname">HOMEPAGE</code> and
5438: <code class="varname">COMMENT</code> fields. Then the package
5439: <code class="filename">Makefile</code> looked like that:</p>
5440: <pre class="programlisting">
5441: # $NetBSD $
5442: #
5443:
5444: DISTNAME= nvu-1.0-sources
5445: PKGNAME= nvu-1.0
5446: CATEGORIES= www
5447: MASTER_SITES= http://cvs.nvu.com/download/
5448: EXTRACT_SUFX= .tar.bz2
5449:
5450: MAINTAINER= rillig@NetBSD.org
5451: HOMEPAGE= http://cvs.nvu.com/
5452: COMMENT= Web Authoring System
5453:
5454: # url2pkg-marker (please do not remove this line.)
5455: .include "../../mk/bsd.pkg.mk"
5456: </pre>
5457: <p>On the first line of output above, an artificial space has been added between NetBSD and $,
5458: this is a workaround to prevent CVS expanding to the filename of the
5459: guide.</p>
5460: <p>Then, I quit the editor and watched pkgsrc downloading a large
5461: source archive:</p>
5462: <pre class="programlisting">
5463: url2pkg> Running "make makesum" ...
5464: => Required installed package digest>=20010302: digest-20060826 found
5465: => Fetching nvu-1.0-sources.tar.bz2
5466: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5467: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
5468: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
5469: url2pkg> Running "make extract" ...
5470: => Required installed package digest>=20010302: digest-20060826 found
5471: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5472: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5473: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
5474: ===> Installing dependencies for nvu-1.0
5475: ===> Overriding tools for nvu-1.0
5476: ===> Extracting for nvu-1.0
5477: url2pkg> Adjusting the Makefile.
5478:
5479: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
5480:
5481: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
5482: </pre>
5483: </div>
5484: <div class="sect3">
5485: <div class="titlepage"><div><div><h4 class="title">
5486: <a name="creating.nvu.problems"></a>14.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div>
5487: <p>Now that the package has been extracted, let's see what's inside
5488: it. The package has a <code class="filename">README.txt</code>, but that only
5489: says something about mozilla, so it's probably useless for seeing what
5490: dependencies this package has. But since there is a GNU configure script
5491: in the package, let's hope that it will complain about everything it
5492: needs.</p>
5493: <pre class="programlisting">
5494: <code class="prompt">$</code> bmake
5495: => Required installed package digest>=20010302: digest-20060826 found
5496: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5497: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5498: ===> Patching for nvu-1.0
5499: ===> Creating toolchain wrappers for nvu-1.0
5500: ===> Configuring for nvu-1.0
5501: [...]
5502: configure: error: Perl 5.004 or higher is required.
5503: [...]
5504: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
5505: [...]
5506: </pre>
5507: <p>That worked quite well. So I opened the package Makefile in my
5508: editor, and since it already has a <code class="varname">USE_TOOLS</code> line, I
5509: just appended <span class="quote">“<span class="quote">perl</span>”</span> to it. Since the dependencies of the
5510: package have changed now, and since a perl wrapper is automatically
5511: installed in the <span class="quote">“<span class="quote">tools</span>”</span> phase, I need to build the package
5512: from scratch.</p>
5513: <pre class="programlisting">
5514: <code class="prompt">$</code> bmake clean
5515: ===> Cleaning for nvu-1.0
5516: <code class="prompt">$</code> bmake
5517: [...]
5518: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
5519: GNU Make. You will not be able to build Mozilla without GNU Make.
5520: [...]
5521: </pre>
5522: <p>So I added <span class="quote">“<span class="quote">gmake</span>”</span> to the
5523: <code class="varname">USE_TOOLS</code> line and tried again (from scratch).</p>
5524: <pre class="programlisting">
5525: [...]
5526: checking for GTK - version >= 1.2.0... no
5527: *** Could not run GTK test program, checking why...
5528: [...]
5529: </pre>
5530: <p>Now to the other dependencies. The first question is: Where is the
5531: GTK package hidden in pkgsrc?</p>
5532: <pre class="programlisting">
5533: <code class="prompt">$</code> echo ../../*/gtk*
5534: [many packages ...]
5535: <code class="prompt">$</code> echo ../../*/gtk
5536: ../../x11/gtk
5537: <code class="prompt">$</code> echo ../../*/gtk2
5538: ../../x11/gtk2
5539: <code class="prompt">$</code> echo ../../*/gtk2/bui*
5540: ../../x11/gtk2/buildlink3.mk
5541: </pre>
5542: <p>The first try was definitely too broad. The second one had exactly
5543: one result, which is very good. But there is one pitfall with GNOME
5544: packages. Before GNOME 2 had been released, there were already many
5545: GNOME 1 packages in pkgsrc. To be able to continue to use these
5546: packages, the GNOME 2 packages were imported as separate packages, and
5547: their names usually have a <span class="quote">“<span class="quote">2</span>”</span> appended. So I checked
5548: whether this was the case here, and indeed it was.</p>
5549: <p>Since the GTK2 package has a <code class="filename">buildlink3.mk</code>
5550: file, adding the dependency is very easy. I just inserted an
5551: <code class="literal">.include</code> line before the last line of the package
5552: <code class="filename">Makefile</code>, so that it now looks like this:</p>
5553: <pre class="programlisting">
5554: [...]
5555: .include "../../x11/gtk2/buildlink3.mk"
5556: .include "../../mk/bsd.pkg.mk
5557: </pre>
5558: <p>After another <span class="command"><strong>bmake clean && bmake</strong></span>, the answer
5559: was:</p>
1.1 dsieger 5560: <pre class="programlisting">
1.184 rillig 5561: [...]
5562: checking for gtk-config... /home/roland/pkg/bin/gtk-config
5563: checking for GTK - version >= 1.2.0... no
5564: *** Could not run GTK test program, checking why...
5565: *** The test program failed to compile or link. See the file config.log for the
5566: *** exact error that occured. This usually means GTK was incorrectly installed
5567: *** or that you have moved GTK since it was installed. In the latter case, you
5568: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
5569: configure: error: Test for GTK failed.
5570: [...]
1.111 sevan 5571: </pre>
1.184 rillig 5572: <p>In this particular case, the assumption that <span class="quote">“<span class="quote">every package
5573: prefers GNOME 2</span>”</span> had been wrong. The first of the lines above
5574: told me that this package really wanted to have the GNOME 1 version of
5575: GTK. If the package had looked for GTK2, it would have looked for
5576: <span class="command"><strong>pkg-config</strong></span> instead of <span class="command"><strong>gtk-config</strong></span>.
5577: So I changed the <code class="literal">x11/gtk2</code> to
5578: <code class="literal">x11/gtk</code> in the package <code class="filename">Makefile</code>,
5579: and tried again.</p>
1.18 snj 5580: <pre class="programlisting">
1.184 rillig 5581: [...]
5582: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
5583: In file included from xpidl.c:42:
5584: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
5585: In file included from xpidl.c:42:
5586: xpidl.h:132: error: parse error before "IDL_ns"
5587: [...]
1.111 sevan 5588: </pre>
1.184 rillig 5589: <p>The package still does not find all of its dependencies. Now the
5590: question is: Which package provides the
5591: <code class="filename">libIDL/IDL.h</code> header file?</p>
1.18 snj 5592: <pre class="programlisting">
1.184 rillig 5593: <code class="prompt">$</code> echo ../../*/*idl*
5594: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
5595: <code class="prompt">$</code> echo ../../*/*IDL*
5596: ../../net/libIDL
1.111 sevan 5597: </pre>
1.184 rillig 5598: <p>Let's take the one from the second try. So I included the
5599: <code class="filename">../../net/libIDL/buildlink3.mk</code> file and tried
5600: again. But the error didn't change. After digging through some of the
5601: code, I concluded that the build process of the package was broken and
5602: couldn't have ever worked, but since the Mozilla source tree is quite
5603: large, I didn't want to fix it. So I added the following to the package
5604: <code class="filename">Makefile</code> and tried again:</p>
1.86 wiz 5605: <pre class="programlisting">
1.184 rillig 5606: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
5607: BUILDLINK_TRANSFORM+= l:IDL:IDL-2
1.111 sevan 5608: </pre>
1.184 rillig 5609: <p>The latter line is needed because the package expects the library
5610: <code class="filename">libIDL.so</code>, but only
5611: <code class="filename">libIDL-2.so</code> is available. So I told the compiler
5612: wrapper to rewrite that on the fly.</p>
5613: <p>The next problem was related to a recent change of the FreeType
1.207 leot 5614: 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.184 rillig 5615: which patch files were relevant for this issue and copied them to the
5616: <code class="filename">patches</code> directory. Then I retried, fixed the
5617: patches so that they applied cleanly and retried again. This time,
5618: everything worked.</p>
1.86 wiz 5619: </div>
1.184 rillig 5620: <div class="sect3">
5621: <div class="titlepage"><div><div><h4 class="title">
5622: <a name="creating.nvu.inst"></a>14.2.1.3. Installing the package</h4></div></div></div>
1.1 dsieger 5623: <pre class="programlisting">
1.184 rillig 5624: <code class="prompt">$</code> bmake CHECK_FILES=no install
5625: [...]
5626: <code class="prompt">$</code> bmake print-PLIST >PLIST
5627: <code class="prompt">$</code> bmake deinstall
5628: <code class="prompt">$</code> bmake install
1.111 sevan 5629: </pre>
1.184 rillig 5630: </div>
5631: </div>
1.1 dsieger 5632: </div>
5633: </div>
1.41 asau 5634: <div class="chapter">
1.1 dsieger 5635: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 5636: <a name="makefile"></a>Chapter 15. Programming in <code class="filename">Makefile</code>s</h2></div></div></div>
1.1 dsieger 5637: <div class="toc">
5638: <p><b>Table of Contents</b></p>
1.100 leot 5639: <dl class="toc">
1.184 rillig 5640: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
5641: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
5642: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
5643: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
5644: <dd><dl>
5645: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
5646: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
5647: <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>
5648: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 5649: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.1 dsieger 5650: </dl></dd>
5651: </dl>
5652: </div>
1.184 rillig 5653: <p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments,
5654: each of which forms a well-defined part of the pkgsrc system. Using
1.246 leot 5655: the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a programming language for a big system
1.184 rillig 5656: like pkgsrc requires some discipline to keep the code correct and
5657: understandable.</p>
5658: <p>The basic ingredients for <code class="filename">Makefile</code>
5659: programming are variables and shell
5660: commands. Among these shell commands may even be more complex ones
1.246 leot 5661: like <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/awk.1"><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make sure that every shell command runs
1.184 rillig 5662: as intended it is necessary to quote all variables correctly when they
5663: are used.</p>
5664: <p>This chapter describes some patterns that appear quite often in
5665: <code class="filename">Makefile</code>s, including the pitfalls that come along
5666: with them.</p>
1.41 asau 5667: <div class="sect1">
1.1 dsieger 5668: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 5669: <a name="makefile.style"></a>15.1. Caveats</h2></div></div></div>
5670: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
5671: <p>When you are creating a file as a
5672: target of a rule, always write the data to a temporary file first
5673: and finally rename that file. Otherwise there might occur an error
5674: in the middle of generating the file, and when the user runs
1.246 leot 5675: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/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.184 rillig 5676: regenerated properly. Example:</p>
1.1 dsieger 5677: <pre class="programlisting">
1.184 rillig 5678: wrong:
5679: @echo "line 1" > ${.TARGET}
5680: @echo "line 2" >> ${.TARGET}
5681: @false
5682:
5683: correct:
5684: @echo "line 1" > ${.TARGET}.tmp
5685: @echo "line 2" >> ${.TARGET}.tmp
5686: @false
5687: @mv ${.TARGET}.tmp ${.TARGET}
1.1 dsieger 5688: </pre>
1.184 rillig 5689: <p>When you run <span class="command"><strong>make wrong</strong></span> twice, the file
5690: <code class="filename">wrong</code> will exist, although there was an error
5691: message in the first run. On the other hand, running <span class="command"><strong>make
5692: correct</strong></span> gives an error message twice, as expected.</p>
1.246 leot 5693: <p>You might remember that <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> sometimes removes
1.184 rillig 5694: <code class="literal">${.TARGET}</code> in case of error, but this only
5695: happens when it is interrupted, for example by pressing
5696: <code class="literal">Ctrl+C</code>. This does <span class="emphasis"><em>not</em></span> happen
1.246 leot 5697: when one of the commands fails (like <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/false.1"><span class="citerefentry"><span class="refentrytitle">false</span>(1)</span></a> above).</p>
1.184 rillig 5698: </li></ul></div>
5699: </div>
5700: <div class="sect1">
5701: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5702: <a name="makefile.variables"></a>15.2. <code class="filename">Makefile</code> variables</h2></div></div></div>
5703: <p><code class="filename">Makefile</code> variables contain strings that
5704: can be processed using the five operators <code class="code">=</code>,
5705: <code class="code">+=</code>, <code class="code">?=</code>, <code class="code">:=</code> and
1.246 leot 5706: <code class="code">!=</code>, which are described in the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man
1.184 rillig 5707: page.</p>
5708: <p>When a variable's value is parsed from a
5709: <code class="filename">Makefile</code>, the hash character <code class="code">#</code> and
5710: the backslash character <code class="code">\</code> are handled specially. If a
5711: backslash is the last character in a line, that backslash is removed
5712: from the line and the line continues with the next line of the file.</p>
5713: <p>The <code class="code">#</code> character starts a comment that reaches
5714: until the end of the line. To get an actual <code class="code">#</code> character,
5715: such as in a URL, write <code class="code">\#</code> instead.</p>
5716: <p>The evaluation of variables either happens immediately or lazy.
5717: It happens immediately when the variable occurs on the right-hand
5718: side of the <code class="code">:=</code> or the <code class="code">!=</code> operator, in a
5719: <code class="varname">.if</code> condition or a <code class="varname">.for</code> loop.
5720: In the other cases, it is evaluated lazily.</p>
5721: <p>Some of the modifiers split the string into words and then
5722: operate on the words, others operate on the string as a whole. When a
5723: string is split into words, double quotes and single quotes are
1.246 leot 5724: interpreted as delimiters, just like in <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/sh.1"><span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span></a>.</p>
1.184 rillig 5725: <div class="sect2">
5726: <div class="titlepage"><div><div><h3 class="title">
5727: <a name="makefile.variables.names"></a>15.2.1. Naming conventions</h3></div></div></div>
5728: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
5729: <li class="listitem"><p>All variable names starting with an underscore
5730: are reserved for use by the pkgsrc infrastructure. They shall
5731: not be used by packages.</p></li>
5732: <li class="listitem"><p>In <span class="command"><strong>.for</strong></span> loops you should use
5733: lowercase variable names for the iteration
5734: variables.</p></li>
5735: <li class="listitem"><p>All list variables should have a plural name,
5736: such as <code class="varname">PKG_OPTIONS</code> or
5737: <code class="varname">DISTFILES</code>.</p></li>
5738: </ul></div>
5739: </div>
5740: </div>
5741: <div class="sect1">
5742: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5743: <a name="makefile.code"></a>15.3. Code snippets</h2></div></div></div>
5744: <div class="sect2">
5745: <div class="titlepage"><div><div><h3 class="title">
5746: <a name="adding-to-list"></a>15.3.1. Adding things to a list</h3></div></div></div>
5747: <p>When adding a string that possibly contains whitespace or quotes to
5748: a list (example 1), it must be quoted using the <code class="code">:Q</code>
5749: modifier.</p>
5750: <p>When adding another list to a list (example 2), it must not be
5751: quoted, since its elements are already quoted.</p>
1.1 dsieger 5752: <pre class="programlisting">
1.184 rillig 5753: STRING= foo * bar `date`
5754: LIST= # empty
5755: ANOTHER_LIST= a=b c=d
5756:
5757: LIST+= ${STRING:Q} # 1
5758: LIST+= ${ANOTHER_LIST} # 2
1.1 dsieger 5759: </pre>
1.184 rillig 5760: </div>
5761: <div class="sect2">
5762: <div class="titlepage"><div><div><h3 class="title">
5763: <a name="echo-literal"></a>15.3.2. Echoing a string exactly as-is</h3></div></div></div>
5764: <p>Echoing a string containing special characters needs special
5765: work.</p>
1.1 dsieger 5766: <pre class="programlisting">
1.184 rillig 5767: STRING= foo bar < > * `date` $$HOME ' "
5768: EXAMPLE_ENV= string=${STRING:Q} x=multiple\ quoted\ words
5769:
5770: all:
5771: echo ${STRING} # 1
5772: echo ${STRING:Q} # 2
5773: printf '%s\n' ${STRING:Q}'' # 3
5774: env ${EXAMPLE_ENV} sh -c 'echo "$$string"; echo "$$x"' # 4
1.1 dsieger 5775: </pre>
1.184 rillig 5776: <p>Example 1 leads to a syntax error in the shell, as the characters
5777: are just copied.</p>
5778: <p>Example 2 quotes the string so that the shell interprets it
5779: correctly. But the echo command may additionally interpret strings with a
5780: leading dash or those containing backslashes.</p>
1.246 leot 5781: <p>Example 3 can handle arbitrary strings, since <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> only
1.184 rillig 5782: interprets the format string, but not the next argument. The trailing
5783: single quotes handle the case when the string is empty. In that case, the
5784: :Q modifier would result in an empty string too, which would then be
1.246 leot 5785: skipped by the shell. For <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> this doesn't make a difference,
1.184 rillig 5786: but other programs may care.</p>
5787: <p>In example 4, the <code class="varname">EXAMPLE_ENV</code> does not
5788: need to be quoted because the quoting has already been done
5789: when adding elements to the list.</p>
1.1 dsieger 5790: </div>
1.41 asau 5791: <div class="sect2">
1.1 dsieger 5792: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 5793: <a name="cflags-gnu-configure"></a>15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</h3></div></div></div>
5794: <p>When passing <code class="varname">CFLAGS</code> or similar variables to a
5795: GNU-style configure script (especially those that call other configure
5796: scripts), it must not have leading or trailing whitespace, since
5797: otherwise the configure script gets confused. To trim leading and
5798: trailing whitespace, use the <code class="code">:M</code> modifier, as in the
5799: following example:</p>
1.1 dsieger 5800: <pre class="programlisting">
1.184 rillig 5801: CPPFLAGS= # empty
5802: CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX}\"
5803: CPPFLAGS+= ${MY_CPPFLAGS}
1.1 dsieger 5804:
1.184 rillig 5805: CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
1.1 dsieger 5806:
1.184 rillig 5807: all:
5808: echo x${CPPFLAGS:Q}x # leading and trailing whitespace
5809: echo x${CONFIGURE_ARGS:Q}x # properly trimmed
5810: </pre>
5811: <p>In this example, <code class="varname">CPPFLAGS</code> has both leading and
5812: trailing whitespace because the <code class="code">+=</code> operator always adds a
5813: space.</p>
5814: </div>
5815: <div class="sect2">
5816: <div class="titlepage"><div><div><h3 class="title">
5817: <a name="empty-variables"></a>15.3.4. Handling possibly empty variables</h3></div></div></div>
5818: <p>When a possibly empty variable is used in a shell program, it may
5819: lead to a syntax error.</p>
5820: <pre class="programlisting">
5821: EGFILES= # empty
1.1 dsieger 5822:
1.184 rillig 5823: install-examples: # produces a syntax error in the shell
5824: for egfile in ${EGFILES}; do \
5825: echo "Installing $$egfile"; \
5826: done
5827: </pre>
5828: <p>The shell only sees the text <code class="code">for egfile in ; do</code>, since
1.246 leot 5829: <code class="code">${EGFILES}</code> is replaced with an empty string by <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.
1.184 rillig 5830: To fix this syntax error, use one of the snippets below.</p>
5831: <pre class="programlisting">
1.229 gutterid 5832: EGFILES= # empty
1.1 dsieger 5833:
1.184 rillig 5834: install-examples:
5835: for egfile in ${EGFILES} ""; do \
5836: [ -n "$$egfile" ] || continue; \
5837: echo "Installing $$egfile"; \
5838: done
5839: </pre>
5840: <p>In this case, an empty string is appended to the iteration list (to
5841: prevent the syntax error) and filtered out later.</p>
5842: <pre class="programlisting">
5843: EGFILES= # empty
1.1 dsieger 5844:
1.184 rillig 5845: install-examples:
5846: .for egfile in ${EGFILES}
5847: echo "Installing ${egfile}"
5848: .endfor
1.1 dsieger 5849: </pre>
1.184 rillig 5850: <p>If one of the filenames contains special characters, it should be
5851: enclosed in single or double quotes.</p>
5852: <p>To have a shell command test whether a make variable is empty, use
5853: the following code: <code class="code">${TEST} -z ${POSSIBLY_EMPTY:Q}""</code>.</p>
5854: </div>
1.229 gutterid 5855: <div class="sect2">
5856: <div class="titlepage"><div><div><h3 class="title">
5857: <a name="makefile.yesno"></a>15.3.5. Testing yes/no variables in conditions</h3></div></div></div>
5858: <p>When a variable can have the values <code class="literal">yes</code> or
5859: <code class="literal">no</code>, use the following pattern to test the variable:</p>
5860: <pre class="programlisting">
5861: .if ${VAR:U:tl} == "yes"
5862: # do something
5863: .endif
5864: </pre>
5865: <p>The <code class="literal">:U</code> modifier is only necessary if the variable
5866: can be undefined. If the variable is guaranteed to be defined, the
5867: <code class="literal">:U</code> can be omitted.</p>
5868: <p>The <code class="literal">:tl</code> modifier converts the variable value to
5869: lowercase, allowing for the values <code class="literal">yes</code>,
5870: <code class="literal">Yes</code>, <code class="literal">YES</code>.</p>
5871: </div>
1.184 rillig 5872: </div>
5873: </div>
5874: <div class="chapter">
5875: <div class="titlepage"><div><div><h2 class="title">
5876: <a name="options"></a>Chapter 16. Options handling</h2></div></div></div>
5877: <div class="toc">
5878: <p><b>Table of Contents</b></p>
5879: <dl class="toc">
5880: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
5881: <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>
5882: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
5883: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
5884: </dl>
1.1 dsieger 5885: </div>
1.184 rillig 5886: <p>Many packages have the ability to be built to support different
5887: sets of features. <code class="filename">bsd.options.mk</code> is a framework
5888: in pkgsrc that provides generic handling of those options that
5889: determine different ways in which the packages can be built. It's
5890: possible for the user to specify exactly which sets of options will be
5891: built into a package or to allow a set of global default options
5892: apply.</p>
5893: <p>There are two broad classes of behaviors that one might want to
5894: control via options. One is whether some particular feature is
5895: enabled in a program that will be built anyway, often by including or
5896: not including a dependency on some other package. The other is
5897: whether or not an additional program will be built as part of the
5898: package. Generally, it is better to make a split package for such
5899: additional programs instead of using options, because it enables
5900: binary packages to be built which can then be added separately. For
5901: example, the foo package might have minimal dependencies (those
5902: packages without which foo doesn't make sense), and then the foo-gfoo
5903: package might include the GTK frontend program gfoo. This is better
5904: than including a gtk option to foo that adds gfoo, because either that
5905: option is default, in which case binary users can't get foo without
5906: gfoo, or not default, in which case they can't get gfoo. With split
5907: packages, they can install foo without having GTK, and later decide to
5908: install gfoo (pulling in GTK at that time). This is an advantage to
5909: source users too, avoiding the need for rebuilds.</p>
5910: <p>Plugins with widely varying dependencies should usually be split
5911: instead of options.</p>
5912: <p>It is often more work to maintain split packages, especially if
5913: the upstream package does not support this. The decision of split
5914: vs. option should be made based on the likelihood that users will want
5915: or object to the various pieces, the size of the dependencies that are
5916: included, and the amount of work.</p>
5917: <p>A further consideration is licensing. Non-free parts, or parts
5918: that depend on non-free dependencies (especially plugins) should
5919: almost always be split if feasible.</p>
5920: <div class="sect1">
5921: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5922: <a name="global-default-options"></a>16.1. Global default options</h2></div></div></div>
5923: <p>Global default options are listed in
5924: <code class="varname">PKG_DEFAULT_OPTIONS</code>, which is a list of the options
5925: that should be built into every package if that option is supported.
5926: This variable should be set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 5927: </div>
1.41 asau 5928: <div class="sect1">
1.1 dsieger 5929: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 5930: <a name="converting-to-options"></a>16.2. Converting packages to use <code class="filename">bsd.options.mk</code>
5931: </h2></div></div></div>
5932: <p>The following example shows how
5933: <code class="filename">bsd.options.mk</code> should be used
5934: by the hypothetical ``wibble'' package, either in the package
5935: <code class="filename">Makefile</code>, or in a file,
5936: e.g. <code class="filename">options.mk</code>, that is included by the
5937: main package <code class="filename">Makefile</code>.</p>
1.1 dsieger 5938: <pre class="programlisting">
1.184 rillig 5939: PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
5940: PKG_SUPPORTED_OPTIONS= wibble-foo ldap
5941: PKG_OPTIONS_OPTIONAL_GROUPS= database
5942: PKG_OPTIONS_GROUP.database= mysql pgsql
5943: PKG_SUGGESTED_OPTIONS= wibble-foo
5944: PKG_OPTIONS_LEGACY_VARS+= WIBBLE_USE_OPENLDAP:ldap
5945: PKG_OPTIONS_LEGACY_OPTS+= foo:wibble-foo
5946:
5947: .include "../../mk/bsd.prefs.mk"
5948:
5949: # this package was previously named wibble2
5950: .if defined(PKG_OPTIONS.wibble2)
5951: PKG_LEGACY_OPTIONS+= ${PKG_OPTIONS.wibble2}
5952: PKG_OPTIONS_DEPRECATED_WARNINGS+= \
5953: "Deprecated variable PKG_OPTIONS.wibble2 used, use ${PKG_OPTIONS_VAR} instead."
5954: .endif
5955:
5956: .include "../../mk/bsd.options.mk"
5957:
5958: # Package-specific option-handling
1.1 dsieger 5959:
1.184 rillig 5960: ###
5961: ### FOO support
5962: ###
5963: .if !empty(PKG_OPTIONS:Mwibble-foo)
5964: CONFIGURE_ARGS+= --enable-foo
5965: .endif
1.1 dsieger 5966:
1.184 rillig 5967: ###
5968: ### LDAP support
5969: ###
5970: .if !empty(PKG_OPTIONS:Mldap)
5971: . include "../../databases/openldap-client/buildlink3.mk"
5972: CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap-client}
5973: .endif
1.1 dsieger 5974:
1.184 rillig 5975: ###
5976: ### database support
5977: ###
5978: .if !empty(PKG_OPTIONS:Mmysql)
5979: . include "../../mk/mysql.buildlink3.mk"
5980: .endif
5981: .if !empty(PKG_OPTIONS:Mpgsql)
5982: . include "../../mk/pgsql.buildlink3.mk"
5983: .endif
5984: </pre>
5985: <p>The first section contains the information about which build
5986: options are supported by the package, and any default options settings
5987: if needed.</p>
5988: <div class="orderedlist"><ol class="orderedlist" type="1">
5989: <li class="listitem"><p><code class="varname">PKG_OPTIONS_VAR</code> is the name of the
1.246 leot 5990: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> variable that the user can set to override the default
1.184 rillig 5991: options. It should be set to
5992: PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em>. Do not set it to
5993: PKG_OPTIONS.${PKGBASE}, since <code class="varname">PKGBASE</code> is not defined
5994: at the point where the options are processed.</p></li>
5995: <li class="listitem"><p><code class="varname">PKG_SUPPORTED_OPTIONS</code> is a list of
5996: build options supported by the package.</p></li>
5997: <li class="listitem"><p><code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code> is a
5998: list of names of groups of mutually exclusive options. The options in
5999: each group are listed in
6000: <code class="varname">PKG_OPTIONS_GROUP.<em class="replaceable"><code>groupname</code></em></code>.
6001: The most specific setting of any option from the group takes
6002: precedence over all other options in the group. Options from the
6003: groups will be automatically added to
6004: <code class="varname">PKG_SUPPORTED_OPTIONS</code>.</p></li>
6005: <li class="listitem"><p><code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> is like
6006: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, but building the
6007: packages will fail if no option from the group is
6008: selected.</p></li>
6009: <li class="listitem"><p><code class="varname">PKG_OPTIONS_NONEMPTY_SETS</code> is a list
6010: of names of sets of options. At least one option from each set must
6011: be selected. The options in each set are listed in
6012: <code class="varname">PKG_OPTIONS_SET.<em class="replaceable"><code>setname</code></em></code>.
6013: Options from the sets will be automatically added to
6014: <code class="varname">PKG_SUPPORTED_OPTIONS</code>. Building the package will
6015: fail if no option from the set is selected.</p></li>
6016: <li class="listitem"><p><code class="varname">PKG_SUGGESTED_OPTIONS</code> is a list of
6017: build options which are enabled by default.</p></li>
6018: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_VARS</code> is a list
6019: of
6020: <span class="quote">“<span class="quote"><em class="replaceable"><code>USE_VARIABLE</code></em>:<em class="replaceable"><code>option</code></em></span>”</span>
6021: pairs that map legacy <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> variables to
6022: their option counterparts. Pairs should be added with
6023: <span class="quote">“<span class="quote">+=</span>”</span> to keep the listing of global legacy variables. A
6024: warning will be issued if the user uses a legacy
6025: variable.</p></li>
6026: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> is a list
6027: of
6028: <span class="quote">“<span class="quote"><em class="replaceable"><code>old-option</code></em>:<em class="replaceable"><code>new-option</code></em></span>”</span>
6029: pairs that map options that have been renamed to their new
6030: counterparts. Pairs should be added with <span class="quote">“<span class="quote">+=</span>”</span> to keep
6031: the listing of global legacy options. A warning will be issued if
6032: the user uses a legacy option.</p></li>
6033: <li class="listitem"><p><code class="varname">PKG_LEGACY_OPTIONS</code> is a list of
6034: options implied by deprecated variables used. This can be used for
6035: cases that neither <code class="varname">PKG_OPTIONS_LEGACY_VARS</code> nor
6036: <code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> can handle, e. g. when
6037: <code class="varname">PKG_OPTIONS_VAR</code> is renamed.</p></li>
6038: <li class="listitem"><p><code class="varname">PKG_OPTIONS_DEPRECATED_WARNINGS</code> is
6039: a list of warnings about deprecated variables or options used, and
6040: what to use instead.</p></li>
6041: </ol></div>
6042: <p>A package should never modify
6043: <code class="varname">PKG_DEFAULT_OPTIONS</code> or the variable named in
6044: <code class="varname">PKG_OPTIONS_VAR</code>. These are strictly user-settable.
6045: To suggest a default set of options, use
6046: <code class="varname">PKG_SUGGESTED_OPTIONS</code>.</p>
6047: <p><code class="varname">PKG_OPTIONS_VAR</code> must be defined before
6048: including <code class="filename">bsd.options.mk</code>. If none of
6049: <code class="varname">PKG_SUPPORTED_OPTIONS</code>,
6050: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, and
6051: <code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> are defined (as can
6052: happen with platform-specific options if none of them is supported on
6053: the current platform), <code class="varname">PKG_OPTIONS</code> is set to the
6054: empty list and the package is otherwise treated as not using the
6055: options framework.</p>
6056: <p>After the inclusion of <code class="filename">bsd.options.mk</code>, the
6057: variable <code class="varname">PKG_OPTIONS</code> contains the list of selected
6058: build options, properly filtered to remove unsupported and duplicate
6059: options.</p>
6060: <p>The remaining sections contain the logic that is specific to
6061: each option. The correct way to check for an option is to check
6062: whether it is listed in <code class="varname">PKG_OPTIONS</code>:</p>
6063: <pre class="programlisting">
6064: .if !empty(PKG_OPTIONS:M<em class="replaceable"><code>option</code></em>)
1.1 dsieger 6065: </pre>
6066: </div>
1.184 rillig 6067: <div class="sect1">
6068: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6069: <a name="option-names"></a>16.3. Option Names</h2></div></div></div>
6070: <p>Options that enable similar features in different packages (like
6071: optional support for a library) should use a common name in all
6072: packages that support it (like the name of the library). If another
6073: package already has an option with the same meaning, use the same
6074: name.</p>
6075: <p>Options that enable features specific to one package, where it's
6076: unlikely that another (unrelated) package has the same (or a similar)
6077: optional feature, should use a name prefixed with
6078: <code class="varname"><em class="replaceable"><code>pkgname</code></em>-</code>.</p>
6079: <p>If a group of related packages share an optional feature
6080: specific to that group, prefix it with the name of the
6081: <span class="quote">“<span class="quote">main</span>”</span> package
6082: (e. g. <code class="varname">djbware-errno-hack</code>).</p>
6083: <p>For new options, add a line to
6084: <code class="filename">mk/defaults/options.description</code>. Lines have two
6085: fields, separated by tab. The first field is the option name, the
6086: second its description. The description should be a whole sentence
6087: (starting with an uppercase letter and ending with a period) that
6088: describes what enabling the option does. E. g. <span class="quote">“<span class="quote">Enable ispell
6089: support.</span>”</span> The file is sorted by option names.</p>
6090: </div>
6091: <div class="sect1">
6092: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6093: <a name="option-build"></a>16.4. Determining the options of dependencies</h2></div></div></div>
6094: <p>When writing <a class="link" href="#buildlink3.mk"><code class="filename">buildlink3.mk</code></a> files, it is often necessary to list
6095: different dependencies based on the options with which the package was
6096: built. For querying these options, the file
6097: <code class="filename">pkgsrc/mk/pkg-build-options.mk</code> should be used. A
6098: typical example looks like this:</p>
1.1 dsieger 6099: <pre class="programlisting">
1.184 rillig 6100: pkgbase := libpurple
6101: .include "../../mk/pkg-build-options.mk"
6102:
6103: .if !empty(PKG_BUILD_OPTIONS.libpurple:Mdbus)
6104: ...
6105: .endif
1.117 sevan 6106: </pre>
1.184 rillig 6107: <p>Including <code class="filename">pkg-build-options.mk</code> here will set
6108: the variable <code class="varname">PKG_BUILD_OPTIONS.libpurple</code> to the build
6109: options of the libpurple package, which can then be queried like
6110: <code class="varname">PKG_OPTIONS</code> in the <code class="filename">options.mk</code>
6111: file. See the file <code class="filename">pkg-build-options.mk</code> for more
6112: details.</p>
1.1 dsieger 6113: </div>
6114: </div>
1.41 asau 6115: <div class="chapter">
1.1 dsieger 6116: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 6117: <a name="tools"></a>Chapter 17. Tools needed for building or running</h2></div></div></div>
1.1 dsieger 6118: <div class="toc">
6119: <p><b>Table of Contents</b></p>
1.100 leot 6120: <dl class="toc">
1.184 rillig 6121: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
6122: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
6123: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
1.1 dsieger 6124: </dl>
6125: </div>
1.184 rillig 6126: <p>The <code class="varname">USE_TOOLS</code> definition is used both internally
6127: by pkgsrc and also for individual packages to define what commands
6128: are needed for building a package (like <code class="varname">TOOL_DEPENDS</code>)
6129: or for later run-time of an installed packaged (such as
6130: <code class="varname">DEPENDS</code>).
6131: If the native system provides an adequate tool, then in many cases, a pkgsrc
6132: package will not be used.</p>
6133: <p>When building a package, the replacement tools are
6134: made available in a directory (as symlinks or wrapper scripts)
6135: that is early in the executable search path. Just like the buildlink
6136: system, this helps with consistent builds.</p>
6137: <p>A tool may be needed to help build a specific package. For example,
6138: perl, GNU make (gmake) or yacc may be needed.</p>
6139: <p>Also a tool may be needed, for example, because the native system's supplied
6140: tool may be inefficient for building a package with pkgsrc.
6141: For example, a package may need GNU awk, bison (instead of
6142: yacc) or a better sed.</p>
6143: <p>The tools used by a package can be listed by running
6144: <span class="command"><strong>make show-tools</strong></span>.</p>
1.41 asau 6145: <div class="sect1">
1.1 dsieger 6146: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6147: <a name="pkgsrc-tools"></a>17.1. Tools for pkgsrc builds</h2></div></div></div>
6148: <p>The default set of tools used by pkgsrc is defined in
6149: <code class="filename">bsd.pkg.mk</code>. This includes standard Unix tools,
6150: such as: <span class="command"><strong>cat</strong></span>, <span class="command"><strong>awk</strong></span>,
6151: <span class="command"><strong>chmod</strong></span>, <span class="command"><strong>test</strong></span>, and so on.
6152: These can be seen by running:
6153: <span class="command"><strong>make show-var VARNAME=USE_TOOLS</strong></span>.</p>
6154: <p>If a package needs a specific program to build
6155: then the <code class="varname">USE_TOOLS</code> variable can be used
6156: to define the tools needed.</p>
1.1 dsieger 6157: </div>
1.184 rillig 6158: <div class="sect1">
6159: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6160: <a name="package-tools"></a>17.2. Tools needed by packages</h2></div></div></div>
6161: <p>In the following examples, the :run means that it is needed at
6162: run-time (and becomes a DEPENDS).
6163: The default is a build dependency which can be set with
6164: :build. (So in this example, it is the same as gmake:build
6165: and pkg-config:build.)</p>
1.1 dsieger 6166: <pre class="programlisting">
1.184 rillig 6167: USE_TOOLS+= gmake perl:run pkg-config
1.1 dsieger 6168: </pre>
1.184 rillig 6169: <p>When using the tools framework, a
6170: <code class="varname">TOOLS_PATH.foo</code> variable is defined
6171: which contains the full path to the appropriate tool. For example,
6172: <code class="varname">TOOLS_PATH.bash</code> could be <span class="quote">“<span class="quote">/bin/bash</span>”</span>
6173: on Linux systems.</p>
6174: <p>If you always need a pkgsrc version of the
6175: tool at run-time, then just use <code class="varname">DEPENDS</code> instead.
6176: </p>
1.1 dsieger 6177: </div>
1.184 rillig 6178: <div class="sect1">
6179: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6180: <a name="platform-tools"></a>17.3. Tools provided by platforms</h2></div></div></div>
6181: <p>When improving or porting pkgsrc to a new platform, have a look
6182: at (or create) the corresponding platform specific make file fragment under
6183: <code class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines
6184: the name of the common tools. For example:</p>
1.1 dsieger 6185: <pre class="programlisting">
1.184 rillig 6186: .if exists(/usr/bin/bzcat)
6187: TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
6188: .elif exists(/usr/bin/bzip2)
6189: TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
6190: .endif
6191:
6192: TOOLS_PLATFORM.true?= true # shell builtin
1.1 dsieger 6193: </pre>
6194: </div>
6195: </div>
1.184 rillig 6196: <div class="chapter">
6197: <div class="titlepage"><div><div><h2 class="title">
6198: <a name="buildlink"></a>Chapter 18. Buildlink methodology</h2></div></div></div>
6199: <div class="toc">
6200: <p><b>Table of Contents</b></p>
6201: <dl class="toc">
6202: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
6203: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
6204: <dd><dl>
6205: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
6206: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
6207: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6208: and
6209: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6210: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
6211: </dl></dd>
6212: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.241 rillig 6213: <dd><dl><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></dl></dd>
1.184 rillig 6214: </dl>
1.1 dsieger 6215: </div>
1.184 rillig 6216: <p>Buildlink is a framework in pkgsrc that controls what headers and libraries
6217: are seen by a package's configure and build processes. This is implemented
6218: in a two step process:</p>
6219: <div class="orderedlist"><ol class="orderedlist" type="1">
6220: <li class="listitem"><p>Symlink headers and libraries for dependencies into
6221: <code class="varname">BUILDLINK_DIR</code>, which by default is a subdirectory
6222: of <code class="varname">WRKDIR</code>.</p></li>
6223: <li class="listitem"><p>Create wrapper scripts that are used in place of the normal compiler
6224: tools that translate <code class="option">-I${LOCALBASE}/include</code> and
6225: <code class="option">-L${LOCALBASE}/lib</code> into references to
6226: <code class="varname">BUILDLINK_DIR</code>. The wrapper scripts also make
6227: native compiler on some operating systems look like GCC, so that
6228: packages that expect GCC won't require modifications to build with
6229: those native compilers.</p></li>
6230: </ol></div>
6231: <p>This normalizes the environment in which a package is built so that the
6232: package may be built consistently despite what other software may be
6233: installed. Please note that the normal system header and library paths,
6234: e.g. <code class="filename">/usr/include</code>,
6235: <code class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is
6236: designed to insulate the package build from non-system-supplied
6237: software.</p>
1.41 asau 6238: <div class="sect1">
1.1 dsieger 6239: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6240: <a name="converting-to-buildlink3"></a>18.1. Converting packages to use buildlink3</h2></div></div></div>
6241: <p>The process of converting packages to use the buildlink3
6242: framework (<span class="quote">“<span class="quote">bl3ifying</span>”</span>) is fairly straightforward.
6243: The things to keep in mind are:</p>
1.23 wiz 6244: <div class="orderedlist"><ol class="orderedlist" type="1">
1.184 rillig 6245: <li class="listitem"><p>Ensure that the build always calls the wrapper scripts
6246: instead of the actual toolchain. Some packages are tricky,
6247: and the only way to know for sure is the check
6248: <code class="filename">${WRKDIR}/.work.log</code> to see if the
6249: wrappers are being invoked.</p></li>
6250: <li class="listitem"><p>Don't override <code class="varname">PREFIX</code> from within
6251: the package Makefile, e.g. Java VMs, standalone shells,
6252: etc., because the code to symlink files into
6253: <code class="filename">${BUILDLINK_DIR}</code> looks for files
6254: relative to <span class="quote">“<span class="quote">pkg_info -qp <em class="replaceable"><code>pkgname</code></em></span>”</span>.
6255: </p></li>
6256: <li class="listitem"><p>Remember that <span class="emphasis"><em>only</em></span> the
6257: <code class="filename">buildlink3.mk</code> files that you list in a
6258: package's Makefile are added as dependencies for that package.
6259: </p></li>
6260: </ol></div>
6261: <p>If a dependency on a particular package is required for its libraries and
6262: headers, then we replace:</p>
6263: <pre class="programlisting">
6264: DEPENDS+= foo>=1.1.0:../../category/foo
6265: </pre>
6266: <p>with</p>
6267: <pre class="programlisting">
6268: .include "../../category/foo/buildlink3.mk"
6269: </pre>
6270: <p>The buildlink3.mk files usually define the required dependencies.
6271: If you need a newer version of the dependency when using buildlink3.mk
6272: files, then you can define it in your Makefile; for example:</p>
1.1 dsieger 6273: <pre class="programlisting">
1.184 rillig 6274: BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
6275: .include "../../category/foo/buildlink3.mk"
1.1 dsieger 6276: </pre>
1.184 rillig 6277: <p>There are several <code class="filename">buildlink3.mk</code>
6278: files in <code class="filename">pkgsrc/mk</code>
6279: that handle special package issues:</p>
6280: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6281: <li class="listitem"><p><code class="filename">bdb.buildlink3.mk</code> chooses either
6282: the native or a pkgsrc Berkeley DB implementation based on
6283: the values of <code class="varname">BDB_ACCEPTED</code> and
6284: <code class="varname">BDB_DEFAULT</code>.</p></li>
6285: <li class="listitem"><p><code class="filename">curses.buildlink3.mk</code>: If the system
6286: comes with neither Curses nor NCurses, this will take care
1.207 leot 6287: 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.184 rillig 6288: <li class="listitem"><p><code class="filename">krb5.buildlink3.mk</code> uses the value
6289: of <code class="varname">KRB5_ACCEPTED</code> to choose between
6290: adding a dependency on Heimdal or MIT-krb5 for packages that
6291: require a Kerberos 5 implementation.</p></li>
6292: <li class="listitem"><p><code class="filename">motif.buildlink3.mk</code> checks for a
6293: system-provided Motif installation or adds a dependency on
1.207 leot 6294: <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.184 rillig 6295: <code class="varname">MOTIF_TYPE</code> to <span class="quote">“<span class="quote">dt</span>”</span>,
6296: <span class="quote">“<span class="quote">lesstif</span>”</span> or <span class="quote">“<span class="quote">motif</span>”</span>
6297: to choose which Motif version will be used.</p></li>
6298: <li class="listitem"><p><code class="filename">readline.buildlink3.mk</code> checks for a
6299: system-provided GNU readline or editline (libedit) installation,
1.207 leot 6300: 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>,
6301: <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.184 rillig 6302: <code class="varname">READLINE_DEFAULT</code> to choose readline implementation.
6303: If your package really needs GNU readline library, its Makefile
6304: should include <code class="filename">devel/readline/buildlink3.mk</code>
6305: instead of <code class="filename">readline.buildlink3.mk</code>.</p></li>
6306: <li class="listitem"><p><code class="filename">oss.buildlink3.mk</code> defines several
6307: variables that may be used by packages that use the
6308: Open Sound System (OSS) API.</p></li>
6309: <li class="listitem"><p><code class="filename">pgsql.buildlink3.mk</code> will accept
6310: any of the Postgres versions in the variable
6311: <code class="varname">PGSQL_VERSIONS_ACCEPTED</code> and default to
6312: the version <code class="varname">PGSQL_VERSION_DEFAULT</code>. See
6313: the file for more information.</p></li>
6314: <li class="listitem"><p><code class="filename">pthread.buildlink3.mk</code> uses the value of
6315: <code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds
1.207 leot 6316: 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.184 rillig 6317: <li class="listitem"><p><code class="filename">xaw.buildlink3.mk</code> uses the value of
6318: <code class="varname">XAW_TYPE</code> to choose a particular Athena widgets
6319: library.</p></li>
6320: </ul></div>
6321: <p>The comments in those <code class="filename">buildlink3.mk</code>
6322: files provide a more complete
6323: description of how to use them properly.</p>
1.1 dsieger 6324: </div>
1.41 asau 6325: <div class="sect1">
1.1 dsieger 6326: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6327: <a name="creating-buildlink3.mk"></a>18.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div>
6328: <a name="buildlink3.mk"></a><p>A package's <code class="filename">buildlink3.mk</code> file is
6329: included by Makefiles to indicate the need to compile and link
6330: against header files and libraries provided by the package. A
6331: <code class="filename">buildlink3.mk</code> file should always provide
6332: enough information to add the correct type of dependency
6333: relationship and include any other
6334: <code class="filename">buildlink3.mk</code> files that it needs to find
6335: headers and libraries that it needs in turn.</p>
6336: <p>To generate an initial <code class="filename">buildlink3.mk</code>
1.207 leot 6337: 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.184 rillig 6338: package is highly recommended. For most packages, the following
6339: command will generate a good starting point for
6340: <code class="filename">buildlink3.mk</code> files:</p>
6341: <pre class="screen">
6342: <code class="prompt">%</code> <strong class="userinput"><code>cd pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>pkgdir</code></em>
6343: <code class="prompt">%</code> createbuildlink >buildlink3.mk</code></strong>
6344: </pre>
1.41 asau 6345: <div class="sect2">
1.1 dsieger 6346: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 6347: <a name="anatomy-of-bl3"></a>18.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div>
6348: <p>The following real-life example
6349: <code class="filename">buildlink3.mk</code> is taken
6350: from <code class="filename">pkgsrc/graphics/tiff</code>:</p>
1.1 dsieger 6351: <pre class="programlisting">
1.184 rillig 6352: BUILDLINK_TREE+= tiff
6353:
6354: .if !defined(TIFF_BUILDLINK3_MK)
6355: TIFF_BUILDLINK3_MK:=
6356:
6357: BUILDLINK_API_DEPENDS.tiff+= tiff>=3.6.1
6358: BUILDLINK_ABI_DEPENDS.tiff+= tiff>=3.7.2nb1
6359: BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
6360:
6361: .include "../../devel/zlib/buildlink3.mk"
6362: .include "../../graphics/jpeg/buildlink3.mk"
6363: .endif # TIFF_BUILDLINK3_MK
6364:
6365: BUILDLINK_TREE+= -tiff
1.1 dsieger 6366: </pre>
1.184 rillig 6367: <p>The header and footer manipulate
6368: <code class="varname">BUILDLINK_TREE</code>, which is common across all
6369: <code class="filename">buildlink3.mk</code> files and is used to track
6370: the dependency tree.</p>
6371: <p>The main section is protected from multiple inclusion
6372: and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is
6373: added. Several important variables are set in the section:</p>
6374: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6375: <li class="listitem"><p><code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6376: is the dependency version recorded in the installed
1.184 rillig 6377: package; this should always be set using
6378: <span class="command"><strong>+=</strong></span> to ensure that
6379: we're appending to any pre-existing list of values. This
1.185 wiz 6380: variable should be set to the last version of the
1.184 rillig 6381: package that had an backwards-incompatible API change.
6382: </p></li>
6383: <li class="listitem"><p><code class="varname">BUILDLINK_PKGSRCDIR.<em class="replaceable"><code>pkg</code></em></code>
6384: is the location of the <em class="replaceable"><code>pkg</code></em>
6385: pkgsrc directory.</p></li>
6386: <li class="listitem"><p><code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
6387: (not shown above) controls whether we use
1.236 gutterid 6388: <code class="varname">BUILD_DEPENDS</code> or
1.184 rillig 6389: <code class="varname">DEPENDS</code> to add the dependency on
6390: <em class="replaceable"><code>pkg</code></em>. The build dependency is
6391: selected by setting
6392: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
1.236 gutterid 6393: to <span class="quote">“<span class="quote">build</span>”</span>. By default, the full dependency is
1.184 rillig 6394: used.</p></li>
6395: <li class="listitem"><p><code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code>
6396: and
6397: <code class="varname">BUILDLINK_LIBDIRS.<em class="replaceable"><code>pkg</code></em></code>
6398: (not shown above) are lists of subdirectories of
6399: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6400: to add to the header and library search paths. These
6401: default to <span class="quote">“<span class="quote">include</span>”</span> and <span class="quote">“<span class="quote">lib</span>”</span>
6402: respectively.</p></li>
6403: <li class="listitem"><p><code class="varname">BUILDLINK_CPPFLAGS.<em class="replaceable"><code>pkg</code></em></code>
6404: (not shown above) is the list of preprocessor flags to add
6405: to <code class="varname">CPPFLAGS</code>, which are passed on to the
6406: configure and build phases. The <span class="quote">“<span class="quote">-I</span>”</span> option
6407: should be avoided and instead be handled using
6408: <code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code> as
6409: above.</p></li>
6410: </ul></div>
6411: <p>The following variables are all optionally defined within
6412: this second section (protected against multiple inclusion) and
6413: control which package files are symlinked into
6414: <code class="filename">${BUILDLINK_DIR}</code> and how their names are
6415: transformed during the symlinking:</p>
6416: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6417: <li class="listitem"><p><code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>
6418: (not shown above) is a shell glob pattern relative to
6419: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6420: to be symlinked into
6421: <code class="filename">${BUILDLINK_DIR}</code>,
6422: e.g. <code class="filename">include/*.h</code>.</p></li>
6423: <li class="listitem"><p><code class="varname">BUILDLINK_FILES_CMD.<em class="replaceable"><code>pkg</code></em></code>
6424: (not shown above) is a shell pipeline that
6425: outputs to stdout a list of files relative to
6426: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>.
6427: The resulting files are to be symlinked
6428: into <code class="filename">${BUILDLINK_DIR}</code>. By default,
6429: this takes the <code class="filename">+CONTENTS</code> of a
6430: <em class="replaceable"><code>pkg</code></em> and filters it through
6431: <code class="varname">${BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em>}</code>.</p></li>
6432: <li class="listitem"><p><code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6433: (not shown above) is a filter command that filters
6434: <code class="filename">+CONTENTS</code> input into a list of files
6435: relative to
6436: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6437: on stdout. By default,
6438: <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6439: outputs the contents of the <code class="filename">include</code>
6440: and <code class="filename">lib</code> directories in the package
6441: <code class="filename">+CONTENTS</code>.</p></li>
6442: <li class="listitem"><p><code class="varname">BUILDLINK_FNAME_TRANSFORM.<em class="replaceable"><code>pkg</code></em></code>
6443: (not shown above) is a list of sed arguments used to
6444: transform the name of the source filename into a
6445: destination filename, e.g. <span class="command"><strong>-e
6446: "s|/curses.h|/ncurses.h|g"</strong></span>.</p></li>
6447: </ul></div>
6448: <p>This section can additionally include any
6449: <code class="filename">buildlink3.mk</code> needed for
6450: <em class="replaceable"><code>pkg</code></em>'s library dependencies.
6451: Including these <code class="filename">buildlink3.mk</code> files
6452: means that the headers and libraries for these
6453: dependencies are also symlinked into
6454: <code class="filename">${BUILDLINK_DIR}</code>
6455: whenever the <em class="replaceable"><code>pkg</code></em>
6456: <code class="filename">buildlink3.mk</code>
6457: file is included. Dependencies are only added for directly
6458: include <code class="filename">buildlink3.mk</code> files.</p>
6459: <p>When providing a <code class="filename">buildlink3.mk</code> and
6460: including other <code class="filename">buildlink3.mk</code> files in it,
6461: please only add necessary ones, i.e., those whose libraries or
6462: header files are automatically exposed when the package is
6463: use.</p>
6464: <p>In particular, if only an executable
6465: (<code class="filename">bin/foo</code>) is linked against a library, that
6466: library does not need to be propagated in the
6467: <code class="filename">buildlink3.mk</code> file.</p>
6468: <p>The following steps should help you decide if a
6469: <code class="filename">buildlink3.mk</code> file needs to be included:
6470: </p>
6471: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6472: <li class="listitem"><p>Look at the installed header files: What
6473: headers do they include? The packages providing these files
6474: must be buildlinked.</p></li>
6475: <li class="listitem"><p>Run <code class="filename">ldd</code> on all installed
6476: libraries and look against what other libraries they link.
6477: Some of the packages providing these probably need to be
6478: buildlinked; however, it's not automatic, since e.g. GTK on
6479: some systems pulls in the X libraries, so they will show up in
6480: the <code class="filename">ldd</code> output, while on others (like OS
6481: X) it won't. <code class="filename">ldd</code> output can thus only be
6482: used as a hint.</p></li>
6483: </ul></div>
6484: <p>
6485: </p>
6486: </div>
1.41 asau 6487: <div class="sect2">
1.1 dsieger 6488: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 6489: <a name="updating-buildlink-depends"></a>18.2.2. Updating
6490: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6491: and
6492: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6493: in <code class="filename">buildlink3.mk</code> files</h3></div></div></div>
1.185 wiz 6494: <p>Both variables set lower bounds for a version of this package.
6495: The two variables differ in that one describes source
1.184 rillig 6496: compatibility (API) and the other binary compatibility (ABI).
6497: The difference is that a change in the API breaks compilation of
6498: programs while changes in the ABI stop compiled programs from
6499: running.</p>
1.185 wiz 6500: <p>The
6501: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6502: variable in a <code class="filename">buildlink3.mk</code> should be
6503: changed very rarely. (One possible scenario: If all packages
6504: using this package need a higher version than defined in the
6505: <code class="filename">buildlink3.mk</code>,
1.184 rillig 6506: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6507: could be updated to that higher version.)</p>
6508: <p>On the other hand, changes to
1.184 rillig 6509: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6510: are more common. The variable will need to be updated every
6511: time the major version of one of its shared libraries is changed,
6512: or any other change where a binary built against the previous
6513: version of the package will not run against the new version any
6514: longer.</p>
6515: <p>In such a case, the package's
1.184 rillig 6516: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6517: must be increased to require the new package version. Then the
6518: <code class="varname">PKGREVISION</code> of all packages
6519: <em class="replaceable"><code>foo</code></em> that depend on this package need
6520: to be increased, and if they have
6521: <code class="filename">buildlink3.mk</code> files,
6522: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>foo</code></em></code>
6523: in their <code class="filename">buildlink3.mk</code> files must be
6524: increased to the new version as well. This is required so that a
6525: package will pull in the versions of the packages that use the
6526: new ABI and that the packages' <code class="varname">PKGREVISION</code>s
6527: uniquely identify the packages built against the new ABI. The
1.207 leot 6528: <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.185 wiz 6529: help with these updates.</p>
6530: <p>See <a class="xref" href="#dependencies" title="21.1.5. Handling dependencies">Section 21.1.5, “Handling dependencies”</a> for more information
6531: about dependencies on other packages, including the
6532: <code class="varname">BUILDLINK_API_DEPENDS</code> definitions.</p>
1.184 rillig 6533: <p>Please take careful consideration before adjusting
6534: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6535: or
6536: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6537: in a <code class="filename">buildlink3.mk</code> file as we don't want to
6538: cause unneeded package deletions and rebuilds. In many cases,
6539: new versions of packages work just fine with older
6540: dependencies.</p>
1.211 gutterid 6541: <p>Also, it is not needed to set
1.184 rillig 6542: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6543: when it is identical to
1.211 gutterid 6544: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.</p>
6545: <p>Note there is also the distinction that users are able to disable
6546: enforcement of ABI dependencies using the <code class="varname">USE_ABI_DEPENDS</code>
6547: variable, but there is no equivalent option for API dependencies.</p>
1.1 dsieger 6548: </div>
6549: </div>
1.41 asau 6550: <div class="sect1">
1.1 dsieger 6551: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6552: <a name="writing-builtin.mk"></a>18.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div>
6553: <p>Some packages in pkgsrc install headers and libraries that
6554: coincide with headers and libraries present in the base system.
6555: Aside from a <code class="filename">buildlink3.mk</code> file, these
6556: packages should also include a <code class="filename">builtin.mk</code>
6557: file that includes the necessary checks to decide whether using
6558: the built-in software or the pkgsrc software is
6559: appropriate.</p>
6560: <p>The only requirements of a builtin.mk file for
6561: <em class="replaceable"><code>pkg</code></em> are:</p>
6562: <div class="orderedlist"><ol class="orderedlist" type="1">
6563: <li class="listitem"><p>It should set
6564: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6565: to either <span class="quote">“<span class="quote">yes</span>”</span> or <span class="quote">“<span class="quote">no</span>”</span>
6566: after it is included.</p></li>
6567: <li class="listitem"><p>It should <span class="emphasis"><em>not</em></span> override any
6568: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6569: which is already set before the
6570: <code class="filename">builtin.mk</code> file is included.</p></li>
6571: <li class="listitem"><p>It should be written to allow multiple inclusion. This
6572: is <span class="emphasis"><em>very</em></span> important and takes careful
6573: attention to <code class="filename">Makefile</code> coding.</p></li>
6574: </ol></div>
6575: <div class="sect2">
6576: <div class="titlepage"><div><div><h3 class="title">
6577: <a name="anatomy-of-builtin.mk"></a>18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</h3></div></div></div>
6578: <p>The following is the recommended template for builtin.mk
6579: files:</p>
1.1 dsieger 6580: <pre class="programlisting">
1.184 rillig 6581: .if !defined(IS_BUILTIN.foo)
6582: #
6583: # IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
6584: # genuinely exists in the system or not.
6585: #
6586: IS_BUILTIN.foo?= no
1.1 dsieger 6587:
1.184 rillig 6588: # BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
6589: # version can be determined.
6590: #
6591: . if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
6592: BUILTIN_PKG.foo?= foo-1.0
6593: . endif
6594: .endif # IS_BUILTIN.foo
1.1 dsieger 6595:
1.184 rillig 6596: .if !defined(USE_BUILTIN.foo)
6597: USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
6598: . if defined(BUILTIN_PKG.foo)
6599: . for _depend_ in ${BUILDLINK_API_DEPENDS.foo}
6600: . if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
6601: USE_BUILTIN.foo!= \
6602: ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo} \
6603: && ${ECHO} "yes" || ${ECHO} "no"
6604: . endif
6605: . endfor
6606: . endif
6607: .endif # USE_BUILTIN.foo
1.1 dsieger 6608:
1.184 rillig 6609: CHECK_BUILTIN.foo?= no
6610: .if !empty(CHECK_BUILTIN.foo:M[nN][oO])
6611: #
6612: # Here we place code that depends on whether USE_BUILTIN.foo is set to
6613: # "yes" or "no".
6614: #
6615: .endif # CHECK_BUILTIN.foo
1.1 dsieger 6616: </pre>
1.184 rillig 6617: <p>The first section sets
6618: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6619: depending on if <em class="replaceable"><code>pkg</code></em> really exists
6620: in the base system. This should not be a base system software
6621: with similar functionality to <em class="replaceable"><code>pkg</code></em>;
6622: it should only be <span class="quote">“<span class="quote">yes</span>”</span> if the actual package is
6623: included as part of the base system. This variable is only
6624: used internally within the <code class="filename">builtin.mk</code>
6625: file.</p>
6626: <p>The second section sets
6627: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6628: to the version of <em class="replaceable"><code>pkg</code></em> in the base
6629: system if it exists (if
6630: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6631: is <span class="quote">“<span class="quote">yes</span>”</span>). This variable is only used internally
6632: within the <code class="filename">builtin.mk</code> file.</p>
6633: <p>The third section sets
6634: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6635: and is <span class="emphasis"><em>required</em></span> in all
6636: <code class="filename">builtin.mk</code> files. The code in this
6637: section must make the determination whether the built-in
6638: software is adequate to satisfy the dependencies listed in
6639: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6640: This is typically done by comparing
6641: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6642: against each of the dependencies in
6643: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6644: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6645: <span class="emphasis"><em>must</em></span> be set to the correct value by the
6646: end of the <code class="filename">builtin.mk</code> file. Note that
6647: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6648: may be <span class="quote">“<span class="quote">yes</span>”</span> even if
6649: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6650: is <span class="quote">“<span class="quote">no</span>”</span> because we may make the determination
6651: that the built-in version of the software is similar enough to
6652: be used as a replacement.</p>
6653: <p>The last section is guarded by
6654: <code class="varname">CHECK_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>,
6655: and includes code that uses the value of
6656: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6657: set in the previous section. This typically includes, e.g.,
6658: adding additional dependency restrictions and listing additional
6659: files to symlink into <code class="filename">${BUILDLINK_DIR}</code> (via
6660: <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>).</p>
6661: </div>
1.7 rillig 6662: </div>
1.1 dsieger 6663: </div>
1.41 asau 6664: <div class="chapter">
1.1 dsieger 6665: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 6666: <a name="plist"></a>Chapter 19. PLIST issues</h2></div></div></div>
1.1 dsieger 6667: <div class="toc">
6668: <p><b>Table of Contents</b></p>
1.100 leot 6669: <dl class="toc">
1.184 rillig 6670: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
6671: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
6672: <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>
6673: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
6674: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
6675: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
6676: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
6677: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
6678: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.1 dsieger 6679: </dl>
6680: </div>
1.184 rillig 6681: <p>The <code class="filename">PLIST</code> file contains a package's
6682: <span class="quote">“<span class="quote">packing list</span>”</span>, i.e. a list of files that belong to
6683: the package (relative to the <code class="filename">${PREFIX}</code>
6684: directory it's been installed in) plus some additional statements
1.246 leot 6685: - see the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> man page for a full list.
1.184 rillig 6686: This chapter addresses some issues that need attention when
6687: dealing with the <code class="filename">PLIST</code> file (or files, see
6688: below!).</p>
1.41 asau 6689: <div class="sect1">
1.1 dsieger 6690: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6691: <a name="rcs-id"></a>19.1. RCS ID</h2></div></div></div>
6692: <p>Be sure to add a RCS ID line as the first thing in any
6693: <code class="filename">PLIST</code> file you write:</p>
6694: <pre class="programlisting">
6695: @comment $NetBSD $
6696: </pre>
6697: <p>An artificial space has been added between NetBSD and $, this is a
6698: workaround here to prevent CVS expanding to the filename of the guide. When
6699: adding the RCS ID the space should be omitted.</p>
1.1 dsieger 6700: </div>
1.41 asau 6701: <div class="sect1">
1.1 dsieger 6702: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6703: <a name="automatic-plist-generation"></a>19.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div>
6704: <p>You can use the <span class="command"><strong>make print-PLIST</strong></span> command
6705: to output a PLIST that matches any new files since the package
6706: was extracted. See <a class="xref" href="#build.helpful-targets" title="13.17. Other helpful targets">Section 13.17, “Other helpful targets”</a> for
6707: more information on this target.</p>
1.1 dsieger 6708: </div>
1.41 asau 6709: <div class="sect1">
1.1 dsieger 6710: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6711: <a name="print-PLIST"></a>19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>
6712: </h2></div></div></div>
6713: <p>The <code class="varname">PRINT_PLIST_AWK</code> variable takes a set
6714: of AWK patterns and actions that are used to filter the output of
6715: print-PLIST. You can <span class="emphasis"><em>append</em></span> any chunk of AWK
6716: scripting you like to it, but be careful with quoting.</p>
6717: <p>For example, to get all files inside the
6718: <code class="filename">libdata/foo</code> directory removed from the
6719: resulting PLIST:</p>
1.1 dsieger 6720: <pre class="programlisting">
1.184 rillig 6721: PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
1.1 dsieger 6722: </pre>
1.185 wiz 6723: <p>The <code class="varname">PRINT_PLIST_AWK</code> transformations are
6724: evaluated after the file list and directory list are sorted.
6725: <code class="varname">EARLY_PRINT_PLIST_AWK</code> is like
6726: <code class="varname">PRINT_PLIST_AWK</code> except it operates before the file
6727: list and directory list are sorted.</p>
1.184 rillig 6728: </div>
6729: <div class="sect1">
6730: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6731: <a name="plist.misc"></a>19.4. Variable substitution in PLIST</h2></div></div></div>
6732: <p>A number of variables are substituted automatically in
6733: PLISTs when a package is installed on a system. This includes the
6734: following variables:</p>
6735: <div class="variablelist"><dl class="variablelist">
6736: <dt><span class="term"><code class="varname">${MACHINE_ARCH}</code>, <code class="varname">${MACHINE_GNU_ARCH}</code></span></dt>
6737: <dd>
6738: <p>Some packages like emacs and perl embed information
6739: about which architecture they were built on into the
6740: pathnames where they install their files. To handle this
6741: case, PLIST will be preprocessed before actually used, and
6742: the symbol
6743: <span class="quote">“<span class="quote"><code class="varname">${MACHINE_ARCH}</code></span>”</span> will be
6744: replaced by what <span class="command"><strong>uname -p</strong></span> gives. The
6745: same is done if the string
6746: <code class="varname">${MACHINE_GNU_ARCH}</code> is embedded in
6747: PLIST somewhere - use this on packages that have GNU
6748: autoconf-created configure scripts.</p>
6749: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
6750: <h3 class="title">Legacy note</h3>
6751: <p>There used to be a symbol
6752: <span class="quote">“<span class="quote"><code class="varname">$ARCH</code></span>”</span> that
6753: was replaced by the output of <span class="command"><strong>uname
6754: -m</strong></span>, but that's no longer supported and has
6755: been removed.</p>
6756: </div>
6757: </dd>
6758: <dt><span class="term"><code class="varname">${OPSYS}</code>, <code class="varname">${LOWER_OPSYS}</code>, <code class="varname">${OS_VERSION}</code></span></dt>
6759: <dd>
6760: <p>Some packages want to embed the OS name and version
6761: into some paths. To do this, use these variables in the
6762: <code class="filename">PLIST</code>:
6763: </p>
6764: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6765: <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>
6766: <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>
6767: <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>
6768: </ul></div>
6769: </dd>
6770: </dl></div>
6771: <p>For a list of values which are replaced by
6772: default, the output of <span class="command"><strong>make help topic=PLIST_SUBST</strong></span> as
6773: well as searching the <code class="filename">pkgsrc/mk</code> directory with <span class="command"><strong>grep</strong></span> for
6774: <code class="varname">PLIST_SUBST</code> should help.</p>
6775: <p>If you want to change other variables not listed above, you
6776: can add variables and their expansions to this variable in the
6777: 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.1 dsieger 6778: <pre class="programlisting">
1.184 rillig 6779: PLIST_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 6780: </pre>
1.184 rillig 6781: <p>This replaces all occurrences of <span class="quote">“<span class="quote">${SOMEVAR}</span>”</span>
6782: in the <code class="filename">PLIST</code> with
6783: <span class="quote">“<span class="quote">somevalue</span>”</span>.</p>
6784: <p>The <code class="varname">PLIST_VARS</code> variable can be used to simplify
6785: the common case of conditionally including some
6786: <code class="filename">PLIST</code> entries. It can be done by adding
6787: <code class="literal"><code class="varname">PLIST_VARS</code>+=foo</code> and
6788: setting the corresponding <code class="varname">PLIST.foo</code> variable
6789: to <code class="literal">yes</code> if the entry should be included.
6790: This will substitute <span class="quote">“<span class="quote"><code class="varname">${PLIST.foo}</code></span>”</span>
6791: in the <code class="filename">PLIST</code> with either
6792: <span class="quote">“<span class="quote"><code class="literal">""</code></span>”</span> or
6793: <span class="quote">“<span class="quote"><code class="literal">"@comment "</code></span>”</span>.
6794: For example, in <code class="filename">Makefile</code>:</p>
1.66 asau 6795: <pre class="programlisting">
1.184 rillig 6796: PLIST_VARS+= foo
6797: .if <em class="replaceable"><code>condition</code></em>
6798: PLIST.foo= yes
6799: .else
1.66 asau 6800: </pre>
1.184 rillig 6801: <p>And then in <code class="filename">PLIST</code>:</p>
1.1 dsieger 6802: <pre class="programlisting">
1.184 rillig 6803: @comment $NetBSD $
6804: bin/bar
6805: man/man1/bar.1
6806: ${PLIST.foo}bin/foo
6807: ${PLIST.foo}man/man1/foo.1
6808: ${PLIST.foo}share/bar/foo.data
1.1 dsieger 6809: </pre>
1.184 rillig 6810: <p>An artificial space has been added between NetBSD and $, this is a
6811: workaround here to prevent CVS expanding to the filename of the guide. When
1.195 gutterid 6812: adding the RCS ID the space should be omitted.</p>
1.1 dsieger 6813: </div>
1.184 rillig 6814: <div class="sect1">
6815: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6816: <a name="manpage-compression"></a>19.5. Man page compression</h2></div></div></div>
6817: <p>Man pages should be installed in compressed form if
6818: <code class="varname">MANZ</code> is set (in <code class="filename">bsd.own.mk</code>),
6819: and uncompressed otherwise. To handle this in the
6820: <code class="filename">PLIST</code> file, the suffix <span class="quote">“<span class="quote">.gz</span>”</span> is
6821: appended/removed automatically for man pages according to
6822: <code class="varname">MANZ</code> and <code class="varname">MANCOMPRESSED</code> being set
6823: or not, see above for details. This modification of the
6824: <code class="filename">PLIST</code> file is done on a copy of it, not
6825: <code class="filename">PLIST</code> itself.</p>
1.1 dsieger 6826: </div>
1.41 asau 6827: <div class="sect1">
1.1 dsieger 6828: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6829: <a name="using-PLIST_SRC"></a>19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code>
6830: </h2></div></div></div>
6831: <p>To use one or more files as source for the <code class="filename">PLIST</code> used
6832: in generating the binary package, set the variable
6833: <code class="varname">PLIST_SRC</code> to the names of that file(s).
1.246 leot 6834: The files are later concatenated using <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/cat.1"><span class="citerefentry"><span class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
1.184 rillig 6835: important. The default for <code class="varname">PLIST_SRC</code> is
6836: <code class="filename">${PKGDIR}/PLIST</code>.</p>
1.1 dsieger 6837: </div>
1.41 asau 6838: <div class="sect1">
1.1 dsieger 6839: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6840: <a name="platform-specific-plist"></a>19.7. Platform-specific and differing PLISTs</h2></div></div></div>
6841: <p>Some packages decide to install a different set of files based on
6842: the operating system being used. These differences can be
6843: automatically handled by using the following files:</p>
6844: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6845: <li class="listitem"><p><code class="filename">PLIST.common</code></p></li>
6846: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}</code></p></li>
6847: <li class="listitem"><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li>
6848: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li>
6849: <li class="listitem"><p><code class="filename">PLIST.common_end</code></p></li>
6850: </ul></div>
1.1 dsieger 6851: </div>
1.41 asau 6852: <div class="sect1">
1.1 dsieger 6853: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6854: <a name="build-plist"></a>19.8. Build-specific PLISTs</h2></div></div></div>
6855: <p>Some packages decide to generate hard-to-guess file names
6856: during installation that are hard to wire down.</p>
6857: <p>In such cases, you can set the
6858: <code class="varname">GENERATE_PLIST</code> variable to shell code
6859: terminated (with a semicolon) that will output PLIST entries which
6860: will be appended to the PLIST</p>
6861: <p>You can find one example in editors/xemacs:</p>
6862: <pre class="programlisting">
6863: GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ;
6864: </pre>
6865: <p>which will append something like
6866: <code class="filename">bin/xemacs-21.4.23-54e8ea71.dmp</code> to the
6867: <code class="filename">PLIST</code>.
6868: </p>
1.1 dsieger 6869: </div>
1.41 asau 6870: <div class="sect1">
1.1 dsieger 6871: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6872: <a name="faq.common-dirs"></a>19.9. Sharing directories between packages</h2></div></div></div>
6873: <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where
6874: multiple (and unrelated) packages install files. These
6875: directories were problematic because you had to add special
6876: tricks in the PLIST to conditionally remove them, or have some
6877: centralized package handle them.</p>
6878: <p>In pkgsrc, it is now easy: Each package should create
6879: directories and install files as needed; <span class="command"><strong>pkg_delete</strong></span>
6880: will remove any directories left empty after uninstalling a
6881: package.</p>
6882: <p>If a package needs an empty directory to work, create
6883: the directory during installation as usual, and also add an
6884: entry to the PLIST:
6885:
6886: </p>
6887: <pre class="programlisting">
6888: @pkgdir path/to/empty/directory
6889: </pre>
6890: <p>
6891:
6892: or take a look at <code class="varname">MAKE_DIRS</code> and
6893: <code class="varname">OWN_DIRS</code>.
1.1 dsieger 6894: </p>
6895: </div>
1.184 rillig 6896: </div>
6897: <div class="chapter">
6898: <div class="titlepage"><div><div><h2 class="title">
6899: <a name="pkginstall"></a>Chapter 20. The pkginstall framework</h2></div></div></div>
6900: <div class="toc">
6901: <p><b>Table of Contents</b></p>
6902: <dl class="toc">
6903: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
6904: <dd><dl>
6905: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
6906: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
6907: </dl></dd>
6908: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
6909: <dd><dl>
6910: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
6911: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
1.239 dholland 6912: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installation</a></span></dt>
6913: <dt><span class="sect2"><a href="#conf-files-declare">20.2.4. Declaring configuration files</a></span></dt>
6914: <dt><span class="sect2"><a href="#conf-files-disable">20.2.5. Disabling handling of configuration files</a></span></dt>
1.184 rillig 6915: </dl></dd>
6916: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
6917: <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>
6918: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
6919: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
6920: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
6921: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
6922: <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>
6923: </dl>
6924: </div>
6925: <p>This chapter describes the framework known as
6926: <code class="literal">pkginstall</code>, whose key features are:</p>
6927: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6928: <li class="listitem"><p>Generic installation and manipulation of directories and files
6929: outside the pkgsrc-handled tree, <code class="varname">LOCALBASE</code>.</p></li>
6930: <li class="listitem"><p>Automatic handling of configuration files during installation,
6931: provided that packages are correctly designed.</p></li>
6932: <li class="listitem"><p>Generation and installation of system startup scripts.</p></li>
6933: <li class="listitem"><p>Registration of system users and groups.</p></li>
6934: <li class="listitem"><p>Registration of system shells.</p></li>
6935: <li class="listitem"><p>Automatic updating of fonts databases.</p></li>
6936: </ul></div>
6937: <p>The following sections inspect each of the above points in detail.</p>
6938: <p>You may be thinking that many of the things described here could be
6939: easily done with simple code in the package's post-installation target
6940: (<code class="literal">post-install</code>). <span class="emphasis"><em>This is incorrect</em></span>,
6941: as the code in them is only executed when building from source. Machines
6942: using binary packages could not benefit from it at all (as the code itself
6943: could be unavailable). Therefore, the only way to achieve any of the items
6944: described above is by means of the installation scripts, which are
6945: automatically generated by pkginstall.</p>
1.41 asau 6946: <div class="sect1">
1.1 dsieger 6947: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6948: <a name="files-and-dirs-outside-prefix"></a>20.1. Files and directories outside the installation prefix</h2></div></div></div>
6949: <p>As you already know, the <code class="filename">PLIST</code> file holds a list
6950: of files and directories that belong to a package. The names used in it
6951: are relative to the installation prefix (<code class="filename">${PREFIX}</code>),
6952: which means that it cannot register files outside this directory (absolute
6953: path names are not allowed). Despite this restriction, some packages need
6954: to install files outside this location; e.g., under
6955: <code class="filename">${VARBASE}</code> or
6956: <code class="filename">${PKG_SYSCONFDIR}</code>. The only way to achieve this
6957: is to create such files during installation time by using
6958: installation scripts.</p>
6959: <p>The generic installation scripts are shell scripts that can
6960: contain arbitrary code. The list of scripts to execute is taken from
6961: the <code class="varname">INSTALL_FILE</code> variable, which defaults to
6962: <code class="filename">INSTALL</code>. A similar variable exists for package
6963: removal (<code class="varname">DEINSTALL_FILE</code>, whose default is
6964: <code class="filename">DEINSTALL</code>). These scripts can run arbitrary
6965: commands, so they have the potential to create and manage files
6966: anywhere in the file system.</p>
6967: <p>Using these general installation files is not recommended, but
6968: may be needed in some special cases. One reason for avoiding them is
6969: that the user has to trust the packager that there is no unwanted or
6970: simply erroneous code included in the installation script. Also,
6971: previously there were many similar scripts for the same functionality,
6972: and fixing a common error involved finding and changing all of
6973: them.</p>
6974: <p>The pkginstall framework offers another, standardized way. It
6975: provides generic scripts to abstract the manipulation of such files
6976: and directories based on variables set in the package's
6977: <code class="filename">Makefile</code>. The rest of this section describes
6978: these variables.</p>
6979: <div class="sect2">
6980: <div class="titlepage"><div><div><h3 class="title">
6981: <a name="dirs-outside-prefix"></a>20.1.1. Directory manipulation</h3></div></div></div>
6982: <p>The following variables can be set to request the creation of
6983: directories anywhere in the file system:</p>
6984: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6985: <li class="listitem">
6986: <p><code class="varname">MAKE_DIRS</code> and <code class="varname">OWN_DIRS</code>
6987: contain a list of directories that should be created and should attempt
6988: to be destroyed by the installation scripts. The difference between
6989: the two is that the latter prompts the administrator to remove any
6990: directories that may be left after deinstallation (because they were
6991: not empty), while the former does not. Example:</p>
6992: <pre class="programlisting">
6993: MAKE_DIRS+= ${VARBASE}/foo/private
6994: </pre>
6995: </li>
6996: <li class="listitem">
6997: <p><code class="varname">MAKE_DIRS_PERMS</code> and
6998: <code class="varname">OWN_DIRS_PERMS</code> contain a list of tuples describing
6999: which directories should be created and should attempt to be destroyed
7000: by the installation scripts. Each tuple holds the following values,
7001: separated by spaces: the directory name, its owner, its group and its
7002: numerical mode. For example:</p>
7003: <pre class="programlisting">
7004: MAKE_DIRS_PERMS+= ${VARBASE}/foo/private \
7005: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
7006: </pre>
7007: <p>The difference between the two is exactly the same as their
7008: non-<code class="varname">PERMS</code> counterparts.</p>
7009: </li>
7010: </ul></div>
1.1 dsieger 7011: </div>
1.184 rillig 7012: <div class="sect2">
7013: <div class="titlepage"><div><div><h3 class="title">
7014: <a name="files-outside-prefix"></a>20.1.2. File manipulation</h3></div></div></div>
7015: <p>Creating non-empty files outside the installation prefix is tricky
7016: because the <code class="filename">PLIST</code> forces all files to be inside it.
1.239 dholland 7017: To overcome this problem, the only solution is to extract the file in a
1.184 rillig 7018: known place (i.e., inside the installation prefix) and copy it to the
7019: appropriate location during installation (done by the installation scripts
1.239 dholland 7020: generated by pkginstall). We will call the former the <span class="emphasis"><em>reference
1.184 rillig 7021: file</em></span> in the following paragraphs, which describe the variables
7022: that can be used to automatically and consistently handle files outside the
7023: installation prefix:</p>
7024: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.239 dholland 7025: <li class="listitem"><p><code class="varname">REQD_FILES</code> is a list of pairs of reference
7026: and target files. At installation time, the reference file is copied
7027: to the target if and only if the latter does not exist. Upon
7028: deinstallation, the reference file is removed provided that it was
7029: not modified by the installation.</p></li>
1.184 rillig 7030: <li class="listitem">
1.239 dholland 7031: <p><code class="varname">REQD_FILES_PERMS</code> contains tuples describing
7032: reference files and targets, including owner, group, and numeric
7033: permissions that should be set. For example:</p>
1.1 dsieger 7034: <pre class="programlisting">
1.184 rillig 7035: REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile \
7036: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
1.1 dsieger 7037: </pre>
1.184 rillig 7038: </li>
1.239 dholland 7039: <li class="listitem"><p><code class="varname">CONF_FILES</code> and
7040: <code class="varname">CONF_FILES_PERMS</code> have the same syntax as
7041: <code class="varname">REQD_FILES</code> and
7042: <code class="varname">REQD_FILES_PERMS</code> respectively. The difference
7043: is that these variables are specifically intended for handling
7044: configuration files, for which additional conventions and
7045: constraints apply. See <a class="xref" href="#conf-files" title="20.2. Configuration files">Section 20.2, “Configuration files”</a> for further
7046: discussion. Note in particular that while handling of
7047: configuration files can be disabled by the user (see <a class="xref" href="#conf-files-disable" title="20.2.5. Disabling handling of configuration files">Section 20.2.5, “Disabling handling of configuration files”</a>), this setting does not affect
7048: <code class="varname">REQD_FILES</code> and
7049: <code class="varname">REQD_FILES_PERMS</code>.</p></li>
1.184 rillig 7050: </ul></div>
1.239 dholland 7051: <p>To install an empty file, one can use these macros and
7052: <code class="filename">/dev/null</code> as the reference file.</p>
1.184 rillig 7053: </div>
1.1 dsieger 7054: </div>
1.41 asau 7055: <div class="sect1">
1.1 dsieger 7056: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7057: <a name="conf-files"></a>20.2. Configuration files</h2></div></div></div>
1.239 dholland 7058: <p>There are two principles that govern the handling of
7059: configuration files in pkgsrc: first, the user's configuration must
7060: not be lost or overwritten by upgrades or reinstallations; and second,
7061: the default configuration should always be available for reference.
7062: To that end, pkgsrc has a framework specifically for handling
7063: configuration files. In general, configuration files are installed
7064: into <code class="filename">${PREFIX}/share/examples</code>, and copied from
7065: there to the pertinent <code class="filename">etc</code> directory as a
7066: separate step and only as needed.</p>
7067: <p>To make this work, there are three things that need to happen,
7068: any of which may require patching. First, the package must be told to
7069: read its configuration from the correct place at runtime; this place
7070: is <code class="filename">${PKG_SYSCONFDIR}</code> (or possibly a subdirectory
7071: of it) which is often but not always
7072: <code class="filename">${PREFIX}/etc</code>. Second, the package must be
7073: taught to install its default configuration files in
7074: <code class="filename">${PREFIX}/share/examples/${PKGBASE}</code>; this is the
7075: point at which patching often becomes required because it is not the
7076: same place as the runtime location. Third, the configuration files
7077: need to be declared in the package makefile; this is the easy part.
7078: </p>
7079: <p>With those elements in place, the right things will happen: the
7080: package install phase and resulting binary package will not touch
7081: <code class="filename">${PKG_SYSCONFDIR}</code>, and the default configuration
7082: will be copied into place by the pkgsrc framework only if not already
7083: present. Similarly, upon deinstall the configuration will not be
7084: removed if it has been modified. (This means that in the case of
7085: reinstallation and upgrades, unmodified configuration files are
7086: updated but modifications are never discarded.)</p>
7087: <p>The following sections describe how to make these things happen
7088: and document other relevant knobs available in the pkgsrc
7089: infrastructure.</p>
1.184 rillig 7090: <div class="sect2">
7091: <div class="titlepage"><div><div><h3 class="title">
7092: <a name="conf-files-sysconfdir"></a>20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</h3></div></div></div>
7093: <p>As said before, the <code class="varname">PKG_SYSCONFDIR</code> variable
7094: specifies where configuration files shall be installed. Its contents are
7095: set based upon the following variables:</p>
7096: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7097: <li class="listitem"><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root
7098: directory. Defaults to <code class="filename">${PREFIX}/etc</code> although it may
1.239 dholland 7099: be overridden by the user to point to their preferred location (e.g.,
1.184 rillig 7100: <code class="filename">/etc</code>, <code class="filename">/etc/pkg</code>, etc.).
7101: Packages must not use it directly.</p></li>
7102: <li class="listitem">
7103: <p><code class="varname">PKG_SYSCONFSUBDIR</code>: A subdirectory of
7104: <code class="varname">PKG_SYSCONFBASE</code> under which the configuration files
7105: for the package being built shall be installed. The definition of this
7106: variable only makes sense in the package's
7107: <code class="filename">Makefile</code> (i.e., it is not user-customizable).</p>
7108: <p>As an example, consider the Apache package,
1.207 leot 7109: <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.184 rillig 7110: configuration files under the
7111: <code class="filename">httpd/</code> subdirectory of
7112: <code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package
7113: Makefile.</p>
7114: </li>
7115: <li class="listitem"><p><code class="varname">PKG_SYSCONFVAR</code>: Specifies the name of the
7116: variable that holds this package's configuration directory (if
7117: different from <code class="varname">PKG_SYSCONFBASE</code>). It defaults to
7118: <code class="varname">PKGBASE</code>'s value, and is always prefixed with
7119: <code class="literal">PKG_SYSCONFDIR</code>.</p></li>
7120: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>: Holds the
7121: directory where the configuration files for the package identified by
7122: <code class="varname">PKG_SYSCONFVAR</code>'s shall be placed.</p></li>
7123: </ul></div>
7124: <p>Based on the above variables, pkginstall determines the value of
7125: <code class="varname">PKG_SYSCONFDIR</code>, which is the <span class="emphasis"><em>only</em></span>
1.239 dholland 7126: variable that may be used within a package to refer to its configuration
1.184 rillig 7127: directory. The algorithm used to set its value is basically the
7128: following:</p>
7129: <div class="orderedlist"><ol class="orderedlist" type="1">
7130: <li class="listitem"><p>If <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> is set,
7131: its value is used.</p></li>
7132: <li class="listitem"><p>If the previous variable is not defined but
7133: <code class="varname">PKG_SYSCONFSUBDIR</code> is set in the package's
7134: <code class="filename">Makefile</code>, the resulting value is
7135: <code class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li>
7136: <li class="listitem"><p>Otherwise, it is set to
7137: <code class="filename">${PKG_SYSCONFBASE}</code>.</p></li>
7138: </ol></div>
7139: <p>It is worth mentioning that <code class="filename">${PKG_SYSCONFDIR}</code> is
1.239 dholland 7140: automatically added to <code class="filename">OWN_DIRS</code>. This causes it
7141: to be automatically created if needed. See <a class="xref" href="#dirs-outside-prefix" title="20.1.1. Directory manipulation">Section 20.1.1, “Directory manipulation”</a> for further details. This does not apply to
7142: subdirectories of <code class="filename">${PKG_SYSCONFDIR}</code>; they must be manually
7143: created with <code class="varname">OWN_DIRS</code> or
7144: <code class="varname">MAKE_DIRS</code>.</p>
1.184 rillig 7145: </div>
7146: <div class="sect2">
7147: <div class="titlepage"><div><div><h3 class="title">
7148: <a name="conf-files-configure"></a>20.2.2. Telling the software where configuration files are</h3></div></div></div>
7149: <p>Given that pkgsrc (and users!) expect configuration files to be in a
1.239 dholland 7150: known place, you need to teach each package where to install its files. In
7151: some cases you will have to patch the package Makefiles to achieve it. If
7152: you are lucky, though, it may be as easy as passing an extra flag to the
7153: configuration script. This is the case for packages using GNU
7154: autoconf:</p>
1.1 dsieger 7155: <pre class="programlisting">
1.184 rillig 7156: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
1.1 dsieger 7157: </pre>
1.184 rillig 7158: <p>Note that this specifies where the package has to <span class="emphasis"><em>look
1.239 dholland 7159: for</em></span> its configuration files, not where they will be installed.
7160: Fortunately, there is a different way to specify the latter, as seen
1.240 gutterid 7161: in the next section, although the combination is rather confusing at
1.239 dholland 7162: first glance.</p>
1.1 dsieger 7163: </div>
1.184 rillig 7164: <div class="sect2">
7165: <div class="titlepage"><div><div><h3 class="title">
1.239 dholland 7166: <a name="conf-files-patching"></a>20.2.3. Patching installation</h3></div></div></div>
7167: <p>As discussed above, <span class="strong"><strong>packages themselves must not
1.184 rillig 7168: touch the contents of <code class="filename">${PKG_SYSCONFDIR}</code>
7169: directly</strong></span>. Bad news is that many software installation scripts
7170: will, out of the box, mess with the contents of that directory. So what is
7171: the correct procedure to fix this issue?</p>
7172: <p>You must teach the package (usually by manually patching it) to
7173: install any configuration files under the examples hierarchy,
7174: <code class="filename">share/examples/${PKGBASE}/</code>. This way, the
7175: <code class="filename">PLIST</code> registers them and the administrator always
7176: has the original copies available.</p>
1.239 dholland 7177: <p>It turns out that for packages using GNU autoconf it is possible
7178: to create the desired effect by setting <code class="varname">sysconfdir</code>
7179: on the make command line at install time. Consider this example taken
7180: from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/index.html" target="_top"><code class="filename">mail/mutt</code></a>:</p>
7181: <pre class="programlisting">
7182: EGDIR= ${PREFIX}/share/examples/mutt
7183: INSTALL_MAKE_FLAGS= ${MAKE_FLAGS} sysconfdir=${EGDIR}
7184: </pre>
7185: <p>Note that the <code class="varname">EGDIR</code> variable, though commonly
7186: used for this purpose, is local to that package and has no meaning
7187: outside it.</p>
7188: </div>
7189: <div class="sect2">
7190: <div class="titlepage"><div><div><h3 class="title">
7191: <a name="conf-files-declare"></a>20.2.4. Declaring configuration files</h3></div></div></div>
1.184 rillig 7192: <p>Once the required configuration files are in place (i.e., under the
1.239 dholland 7193: examples hierarchy), the pkginstall framework can use them as reference copies
1.184 rillig 7194: during the package installation to update what is in
7195: <code class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables
7196: <code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are
1.239 dholland 7197: used. Check out <a class="xref" href="#files-outside-prefix" title="20.1.2. File manipulation">Section 20.1.2, “File manipulation”</a> for further
7198: information about their syntax and their purpose. Here is an example,
7199: taken from the <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>
7200: <pre class="programlisting">
7201: EGDIR= ${PREFIX}/share/examples/mutt
7202: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
7203: </pre>
7204: <p>Note that (as in the previous section's example) the
7205: <code class="varname">EGDIR</code> variable is specific to the package and has
7206: no meaning outside it.</p>
7207: <p>For reference, the complete example from Mutt is as follows:</p>
1.1 dsieger 7208: <pre class="programlisting">
1.239 dholland 7209: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
7210: EGDIR= ${PREFIX}/share/examples/mutt
7211: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
7212: INSTALLATION_DIRS+= ${EGDIR}
7213: INSTALL_MAKE_FLAGS= ${MAKE_FLAGS} sysconfdir=${EGDIR}
1.1 dsieger 7214: </pre>
7215: </div>
1.184 rillig 7216: <div class="sect2">
7217: <div class="titlepage"><div><div><h3 class="title">
1.239 dholland 7218: <a name="conf-files-disable"></a>20.2.5. Disabling handling of configuration files</h3></div></div></div>
1.184 rillig 7219: <p>The automatic copying of config files can be toggled by setting the
7220: environment variable <code class="varname">PKG_CONFIG</code> prior to package
7221: installation.</p>
1.1 dsieger 7222: </div>
7223: </div>
1.41 asau 7224: <div class="sect1">
1.1 dsieger 7225: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7226: <a name="rcd-scripts"></a>20.3. System startup scripts</h2></div></div></div>
7227: <p>System startup scripts are special files because they must be
7228: installed in a place known by the underlying OS, usually outside the
7229: 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
7230: can be used. However, pkginstall provides a special mechanism to handle
7231: these files.</p>
7232: <p>In order to provide system startup scripts, the package has
7233: to:</p>
7234: <div class="orderedlist"><ol class="orderedlist" type="1">
7235: <li class="listitem"><p>Store the script inside <code class="filename">${FILESDIR}</code>, with
7236: the <code class="literal">.sh</code> suffix appended. Considering the
1.223 nia 7237: <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
7238: has a <code class="filename">cupsd.sh</code> in its files directory.</p></li>
1.184 rillig 7239: <li class="listitem">
7240: <p>Tell pkginstall to handle it, appending the name of the script,
7241: without its extension, to the <code class="varname">RCD_SCRIPTS</code> variable.
7242: Continuing the previous example:</p>
7243: <pre class="programlisting">
7244: RCD_SCRIPTS+= cupsd
7245: </pre>
7246: </li>
7247: </ol></div>
7248: <p>Once this is done, pkginstall will do the following steps for each
7249: script in an automated fashion:</p>
7250: <div class="orderedlist"><ol class="orderedlist" type="1">
7251: <li class="listitem"><p>Process the file found in the files directory applying all the
7252: substitutions described in the <code class="filename">FILES_SUBST</code>
7253: variable.</p></li>
7254: <li class="listitem"><p>Copy the script from the files directory to the examples
7255: hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>. Note
1.239 dholland 7256: that this reference file must be explicitly registered in the
1.184 rillig 7257: <code class="filename">PLIST</code>.</p></li>
7258: <li class="listitem"><p>Add code to the installation scripts to copy the startup script
7259: from the examples hierarchy into the system-wide startup scripts
7260: directory.</p></li>
7261: </ol></div>
7262: <div class="sect2">
7263: <div class="titlepage"><div><div><h3 class="title">
7264: <a name="rcd-scripts-disable"></a>20.3.1. Disabling handling of system startup scripts</h3></div></div></div>
7265: <p>The automatic copying of config files can be toggled by setting the
7266: environment variable <code class="varname">PKG_RCD_SCRIPTS</code> prior to package
7267: installation. Note that the scripts will be always copied inside the
7268: examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>, no
7269: matter what the value of this variable is.</p>
1.1 dsieger 7270: </div>
7271: </div>
1.184 rillig 7272: <div class="sect1">
7273: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
7274: <a name="users-and-groups"></a>20.4. System users and groups</h2></div></div></div>
7275: <p>If a package needs to create special users and/or groups during
7276: installation, it can do so by using the pkginstall framework.</p>
7277: <p>Users can be created by adding entries to the
7278: <code class="varname">PKG_USERS</code> variable. Each entry has the following
7279: syntax:</p>
7280: <pre class="programlisting">
7281: user:group
7282: </pre>
7283: <p>Further specification of user details may be done by setting
7284: per-user variables.
7285: <code class="varname">PKG_UID.<em class="replaceable"><code>user</code></em></code> is the
7286: numeric UID for the user.
7287: <code class="varname">PKG_GECOS.<em class="replaceable"><code>user</code></em></code> is the
7288: user's description or comment.
7289: <code class="varname">PKG_HOME.<em class="replaceable"><code>user</code></em></code> is the
7290: user's home directory, and defaults to
7291: <code class="filename">/nonexistent</code> if not specified.
7292: <code class="varname">PKG_SHELL.<em class="replaceable"><code>user</code></em></code> is the
7293: user's shell, and defaults to <code class="filename">/sbin/nologin</code> if
7294: not specified.</p>
7295: <p>Similarly, groups can be created by adding entries to the
7296: <code class="varname">PKG_GROUPS</code> variable, whose syntax is:</p>
7297: <pre class="programlisting">
7298: group
7299: </pre>
7300: <p>The numeric GID of the group may be set by defining
7301: <code class="varname">PKG_GID.<em class="replaceable"><code>group</code></em></code>.</p>
7302: <p>If a package needs to create the users and groups at an earlier
7303: stage, then it can set <code class="varname">USERGROUP_PHASE</code> to either
7304: <code class="literal">configure</code>,<code class="literal">build</code>, or
7305: <code class="literal">pre-install</code> to indicate the phase before which the
7306: users and groups are created. In this case, the numeric UIDs and GIDs
7307: of the created users and groups are automatically hardcoded into the
7308: final installation scripts.</p>
1.1 dsieger 7309: </div>
1.41 asau 7310: <div class="sect1">
1.1 dsieger 7311: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7312: <a name="shells"></a>20.5. System shells</h2></div></div></div>
7313: <p>Packages that install system shells should register them in the shell
7314: database, <code class="filename">/etc/shells</code>, to make things easier to the
7315: administrator. This must be done from the installation scripts to keep
7316: binary packages working on any system. pkginstall provides an easy way to
7317: accomplish this task.</p>
7318: <p>When a package provides a shell interpreter, it has to set the
7319: <code class="varname">PKG_SHELL</code> variable to its absolute file name. This will
7320: add some hooks to the installation scripts to handle it. Consider the
1.207 leot 7321: 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.184 rillig 7322: <pre class="programlisting">
7323: PKG_SHELL= ${PREFIX}/bin/zsh
7324: </pre>
7325: <div class="sect2">
7326: <div class="titlepage"><div><div><h3 class="title">
7327: <a name="shells-disable"></a>20.5.1. Disabling shell registration</h3></div></div></div>
7328: <p>The automatic registration of shell interpreters can be disabled by
7329: the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</code>
7330: environment variable to <code class="literal">NO</code>.</p>
7331: </div>
1.1 dsieger 7332: </div>
1.41 asau 7333: <div class="sect1">
1.1 dsieger 7334: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7335: <a name="fonts"></a>20.6. Fonts</h2></div></div></div>
7336: <p>Packages that install X11 fonts should update the database files
7337: that index the fonts within each fonts directory. This can easily be
7338: accomplished within the pkginstall framework.</p>
7339: <p>When a package installs X11 fonts, it must list the directories in
7340: which fonts are installed in the
7341: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code> variables,
7342: where <em class="replaceable"><code>type</code></em> can be one of <span class="quote">“<span class="quote">ttf</span>”</span>,
7343: <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
7344: installation scripts to run the appropriate commands to update the fonts
7345: database files within each of those directories. For convenience, if the
7346: directory path is relative, it is taken to be relative to the package's
1.207 leot 7347: 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.1 dsieger 7348: <pre class="programlisting">
1.184 rillig 7349: FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
1.1 dsieger 7350: </pre>
1.184 rillig 7351: <div class="sect2">
7352: <div class="titlepage"><div><div><h3 class="title">
7353: <a name="fonts-disable"></a>20.6.1. Disabling automatic update of the fonts databases</h3></div></div></div>
7354: <p>The automatic update of fonts databases can be disabled by
7355: the administrator by setting the <code class="filename">PKG_UPDATE_FONTS_DB</code>
7356: environment variable to <code class="literal">NO</code>.</p>
1.1 dsieger 7357: </div>
7358: </div>
7359: </div>
1.41 asau 7360: <div class="chapter">
1.1 dsieger 7361: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 7362: <a name="fixes"></a>Chapter 21. Making your package work</h2></div></div></div>
1.1 dsieger 7363: <div class="toc">
7364: <p><b>Table of Contents</b></p>
1.100 leot 7365: <dl class="toc">
1.154 rillig 7366: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
1.1 dsieger 7367: <dd><dl>
1.154 rillig 7368: <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>
7369: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
7370: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
7371: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
7372: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
7373: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
7374: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
7375: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
7376: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
7377: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
7378: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
7379: </dl></dd>
7380: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
7381: <dd><dl>
7382: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
7383: <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>
7384: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
7385: </dl></dd>
7386: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
7387: <dd><dl>
7388: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
7389: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
7390: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.223 nia 7391: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 rillig 7392: </dl></dd>
7393: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
7394: <dd><dl>
7395: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
7396: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.205 wiz 7397: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 nia 7398: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
7399: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
7400: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
7401: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.154 rillig 7402: </dl></dd>
7403: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
7404: <dd><dl>
7405: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
7406: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.172 rillig 7407: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
7408: <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>
7409: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.154 rillig 7410: </dl></dd>
7411: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
7412: <dd><dl>
7413: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
7414: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
7415: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
7416: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
7417: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.203 nia 7418: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 rillig 7419: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
7420: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.203 nia 7421: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
7422: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
7423: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
7424: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
7425: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
7426: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
7427: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.1 dsieger 7428: emulation</a></span></dt>
1.203 nia 7429: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
7430: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.1 dsieger 7431: </dl></dd>
1.154 rillig 7432: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 7433: </dl>
7434: </div>
1.41 asau 7435: <div class="sect1">
1.1 dsieger 7436: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 7437: <a name="general-operation"></a>21.1. General operation</h2></div></div></div>
1.1 dsieger 7438: <p>One appealing feature of pkgsrc is that it runs on many
1.108 rillig 7439: different platforms. As a result, it is important to ensure,
7440: where possible, that packages in pkgsrc are portable. This
7441: chapter mentions some particular details you should pay
7442: attention to while working on pkgsrc.</p>
1.41 asau 7443: <div class="sect2">
1.1 dsieger 7444: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7445: <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.1 dsieger 7446: </h3></div></div></div>
7447: <p>The pkgsrc user can configure pkgsrc by overriding several
7448: variables in the file pointed to by <code class="varname">MAKECONF</code>,
1.10 hubertf 7449: which is <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> by default. When you
1.1 dsieger 7450: want to use those variables in the preprocessor directives of
1.246 leot 7451: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> (for example <code class="literal">.if</code> or
1.1 dsieger 7452: <code class="literal">.for</code>), you need to include the file
7453: <code class="filename">../../mk/bsd.prefs.mk</code> before, which in turn
7454: loads the user preferences.</p>
7455: <p>But note that some variables may not be completely defined
7456: after <code class="filename">../../mk/bsd.prefs.mk</code> has been
7457: included, as they may contain references to variables that are
1.108 rillig 7458: not yet defined. In shell commands (the lines in
7459: <code class="filename">Makefile</code> that are indented with a tab) this
7460: is no problem, since variables are only expanded when they are
7461: used. But in the preprocessor directives mentioned above and in
7462: dependency lines (of the form <code class="literal">target:
1.1 dsieger 7463: dependencies</code>) the variables are expanded at load
7464: time.</p>
1.41 asau 7465: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 7466: <h3 class="title">Note</h3>
1.108 rillig 7467: <p>To check whether a variable can be used at load time,
7468: run <span class="command"><strong>pkglint -Wall</strong></span> on your package.</p>
1.1 dsieger 7469: </div>
7470: </div>
1.41 asau 7471: <div class="sect2">
1.1 dsieger 7472: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7473: <a name="user-interaction"></a>21.1.2. User interaction</h3></div></div></div>
1.1 dsieger 7474: <p>Occasionally, packages require interaction from the user,
7475: and this can be in a number of ways:</p>
1.41 asau 7476: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7477: <li class="listitem"><p>When fetching the distfiles, some packages require user
1.1 dsieger 7478: interaction such as entering username/password or accepting a
7479: license on a web page.</p></li>
1.23 wiz 7480: <li class="listitem"><p>When extracting the distfiles, some packages may ask for
1.1 dsieger 7481: passwords.</p></li>
1.23 wiz 7482: <li class="listitem"><p>help to configure the package before it is built</p></li>
7483: <li class="listitem"><p>help during the build process</p></li>
7484: <li class="listitem"><p>help during the installation of a package</p></li>
1.1 dsieger 7485: </ul></div>
1.108 rillig 7486: <p>A package can set the <code class="varname">INTERACTIVE_STAGE</code>
7487: variable to define which stages need interaction. This should be
7488: done in the package's <code class="filename">Makefile</code>, e.g.:</p>
1.1 dsieger 7489: <pre class="programlisting">
7490: INTERACTIVE_STAGE= configure install
1.111 sevan 7491: </pre>
1.1 dsieger 7492: <p>The user can then decide to skip this package by setting the
1.108 rillig 7493: <code class="varname">BATCH</code> variable. Packages that require interaction
7494: are also excluded from bulk builds.</p>
1.1 dsieger 7495: </div>
1.41 asau 7496: <div class="sect2">
1.1 dsieger 7497: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7498: <a name="handling-licenses"></a>21.1.3. Handling licenses</h3></div></div></div>
1.111 sevan 7499: <p>Authors of software can choose the licence under which software
7500: can be copied. The Free Software Foundation has declared some
7501: licenses "Free", and the Open Source Initiative has a definition of
7502: "Open Source".</p>
7503: <p>By default, pkgsrc allows packages with Free or Open Source
7504: licenses to be built. To allow packages with other licenses to be
7505: built as well, the pkgsrc user needs to add these licenses to the
7506: <code class="varname">ACCEPTABLE_LICENSES</code> variable in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. Note
7507: that this variable only affects which packages may be
7508: <span class="emphasis"><em>built</em></span>, while the license terms often also
7509: restrict the actual use of the package and its redistribution.</p>
1.1 dsieger 7510: <p>One might want to only install packages with a BSD license,
1.108 rillig 7511: or the GPL, and not the other. The free licenses are added to the
1.111 sevan 7512: default <code class="varname">ACCEPTABLE_LICENSES</code> variable. The pkgsrc
1.19 jnemeth 7513: user can override the default by setting the
7514: <code class="varname">ACCEPTABLE_LICENSES</code> variable with "=" instead
1.111 sevan 7515: of "+=". The licenses accepted by default are defined in the
7516: <code class="varname">DEFAULT_ACCEPTABLE_LICENSES</code> variable in the file
7517: <code class="filename">pkgsrc/mk/license.mk</code>.</p>
1.1 dsieger 7518: <p>The license tag mechanism is intended to address
7519: copyright-related issues surrounding building, installing and
7520: using a package, and not to address redistribution issues (see
7521: <code class="varname">RESTRICTED</code> and
1.111 sevan 7522: <code class="varname">NO_SRC_ON_FTP</code>, etc.).
1.19 jnemeth 7523: Packages with redistribution restrictions should set these
7524: tags.</p>
1.1 dsieger 7525: <p>Denoting that a package may be copied according to a
7526: particular license is done by placing the license in
7527: <code class="filename">pkgsrc/licenses</code> and setting the
7528: <code class="varname">LICENSE</code> variable to a string identifying the
1.207 leot 7529: 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.1 dsieger 7530: <pre class="programlisting">
7531: LICENSE= xv-license
1.111 sevan 7532: </pre>
1.1 dsieger 7533: <p>When trying to build, the user will get a notice that the
7534: package is covered by a license which has not been placed in the
7535: <code class="varname">ACCEPTABLE_LICENSES</code> variable:</p>
7536: <pre class="programlisting">
7537: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
7538: ===> xv-3.10anb9 has an unacceptable license: xv-license.
7539: ===> To view the license, enter "/usr/bin/make show-license".
7540: ===> To indicate acceptance, add this line to your /etc/mk.conf:
7541: ===> ACCEPTABLE_LICENSES+=xv-license
7542: *** Error code 1
1.111 sevan 7543: </pre>
1.10 hubertf 7544: <p>The license can be viewed with <span class="command"><strong>make
1.1 dsieger 7545: show-license</strong></span>, and if the user so chooses, the line
1.10 hubertf 7546: printed above can be added to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.1 dsieger 7547: convey to pkgsrc that it should not in the future fail because of
7548: that license:</p>
7549: <pre class="programlisting">
7550: ACCEPTABLE_LICENSES+=xv-license
1.111 sevan 7551: </pre>
7552: <p>The use of <code class="varname">LICENSE=shareware</code>,
7553: <code class="varname">LICENSE=no-commercial-use</code>, and similar language
7554: is deprecated because it does not crisply refer to a particular
7555: license text. Another problem with such usage is that it does not
7556: enable a user to tell pkgsrc to proceed for a single package
7557: without also telling pkgsrc to proceed for all packages with that
7558: tag.</p>
7559: <div class="sect3">
7560: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 7561: <a name="new-license"></a>21.1.3.1. Adding a package with a new license</h4></div></div></div>
1.48 rodent 7562: <p>When adding a package with a new license, the following steps
7563: are required:</p>
7564: <div class="orderedlist"><ol class="orderedlist" type="1">
7565: <li class="listitem">
1.169 rillig 7566: <p>Check whether the license qualifies as Free or Open Source by
7567: referencing <a class="ulink" href="https://www.gnu.org/licenses/license-list.en.html" target="_top">Various
7568: Licenses and Comments about Them</a> and <a class="ulink" href="https://opensource.org/licenses/alphabetical" target="_top">Licenses by Name |
1.111 sevan 7569: Open Source Initiative</a>. If this is the case, the filename in
7570: <code class="filename">pkgsrc/licenses/</code> does not need the
7571: <code class="filename">-license</code> suffix, and the license name should be
7572: added to:</p>
1.48 rodent 7573: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.169 rillig 7574: <li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in
7575: <code class="filename">pkgsrc/mk/license.mk</code></p></li>
7576: <li class="listitem"><p>default_acceptable_licenses in
7577: <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
1.48 rodent 7578: </ul></div>
7579: </li>
1.169 rillig 7580: <li class="listitem"><p>The license text should be added to
7581: <code class="filename">pkgsrc/licenses</code> for displaying. A list of known
7582: licenses can be seen in this directory.</p></li>
1.48 rodent 7583: </ol></div>
1.111 sevan 7584: </div>
7585: <div class="sect3">
7586: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 7587: <a name="change-license"></a>21.1.3.2. Change to the license</h4></div></div></div>
1.1 dsieger 7588: <p>When the license changes (in a way other than formatting),
1.111 sevan 7589: make sure that the new license has a different name (e.g.,
1.1 dsieger 7590: append the version number if it exists, or the date). Just
7591: because a user told pkgsrc to build programs under a previous
7592: version of a license does not mean that pkgsrc should build
7593: programs under the new licenses. The higher-level point is that
7594: pkgsrc does not evaluate licenses for reasonableness; the only
7595: test is a mechanistic test of whether a particular text has been
1.111 sevan 7596: approved by either of two bodies (FSF or OSI).</p>
7597: </div>
1.1 dsieger 7598: </div>
1.41 asau 7599: <div class="sect2">
1.1 dsieger 7600: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7601: <a name="restricted-packages"></a>21.1.4. Restricted packages</h3></div></div></div>
1.1 dsieger 7602: <p>Some licenses restrict how software may be re-distributed.
1.111 sevan 7603: By declaring the restrictions, package tools can
1.1 dsieger 7604: automatically refrain from e.g. placing binary packages on FTP
7605: sites.</p>
1.111 sevan 7606: <p>There are four possible restrictions, which are
1.1 dsieger 7607: the cross product of sources (distfiles) and binaries not being
7608: placed on FTP sites and CD-ROMs. Because this is rarely the exact
7609: language in any license, and because non-Free licenses tend to be
7610: different from each other, pkgsrc adopts a definition of FTP and
1.111 sevan 7611: CD-ROM.
7612:
7613: "FTP" means making the source or binary file available over the
7614: Internet at no charge.
7615:
7616: "CD-ROM" means making the source or binary available on some kind of
7617: media, together with other source and binary packages, which is sold
7618: for a distribution charge.
1.1 dsieger 7619: </p>
7620: <p>In order to encode these restrictions, the package system
7621: defines five make variables that can be set to note these
7622: restrictions:</p>
1.41 asau 7623: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7624: <li class="listitem">
1.1 dsieger 7625: <p><code class="varname">RESTRICTED</code></p>
7626: <p>This variable should be set whenever a restriction
7627: exists (regardless of its kind). Set this variable to a
7628: string containing the reason for the restriction. It should
7629: be understood that those wanting to understand the restriction
7630: will have to read the license, and perhaps seek advice of
7631: counsel.</p>
7632: </li>
1.23 wiz 7633: <li class="listitem">
1.1 dsieger 7634: <p><code class="varname">NO_BIN_ON_CDROM</code></p>
7635: <p>Binaries may not be placed on CD-ROM containing other
7636: binary packages, for which a distribution charge may be made.
7637: In this case, set this variable to
7638: <code class="varname">${RESTRICTED}</code>.</p>
7639: </li>
1.23 wiz 7640: <li class="listitem">
1.1 dsieger 7641: <p><code class="varname">NO_BIN_ON_FTP</code></p>
7642: <p>Binaries may not made available on the Internet without
7643: charge. In this case, set this variable to
7644: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7645: binary packages will not be included on ftp.NetBSD.org.</p>
7646: </li>
1.23 wiz 7647: <li class="listitem">
1.1 dsieger 7648: <p><code class="varname">NO_SRC_ON_CDROM</code></p>
7649: <p>Distfiles may not be placed on CD-ROM, together with
7650: other distfiles, for which a fee may be charged. In this
7651: case, set this variable to <code class="varname">${RESTRICTED}</code>.
7652: </p>
7653: </li>
1.23 wiz 7654: <li class="listitem">
1.1 dsieger 7655: <p><code class="varname">NO_SRC_ON_FTP</code></p>
7656: <p>Distfiles may not made available via FTP at no charge.
7657: In this case, set this variable to
7658: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7659: the distfile(s) will not be mirrored on ftp.NetBSD.org.</p>
7660: </li>
7661: </ul></div>
1.111 sevan 7662: <p>Please note that packages will be removed from pkgsrc when the
7663: distfiles are not distributable and cannot be obtained for a period
7664: of one full quarter branch. Packages with manual/interactive fetch
7665: must have a maintainer and it is his/her responsibility to ensure
7666: this.</p>
1.1 dsieger 7667: </div>
1.41 asau 7668: <div class="sect2">
1.1 dsieger 7669: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7670: <a name="dependencies"></a>21.1.5. Handling dependencies</h3></div></div></div>
1.175 gutterid 7671: <p>Your package may depend on some other package being present,
7672: and there are various ways of expressing this dependency.
7673: pkgsrc supports the <code class="varname">DEPENDS</code>,
7674: <code class="varname">BUILD_DEPENDS</code>,
7675: <code class="varname">TOOL_DEPENDS</code>, and
7676: <code class="varname">TEST_DEPENDS</code> definitions, the
1.1 dsieger 7677: <code class="varname">USE_TOOLS</code> definition, as well as dependencies
7678: via <code class="filename">buildlink3.mk</code>, which is the preferred way
7679: to handle dependencies, and which uses the variables named above.
1.184 rillig 7680: See <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a> for more information.</p>
1.175 gutterid 7681: <p>The basic difference is that the <code class="varname">DEPENDS</code>
7682: definition registers that pre-requisite in the binary package so it
7683: will be pulled in when the binary package is later installed, whilst
7684: the <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7685: and <code class="varname">TEST_DEPENDS</code> definitions do not, marking a
7686: dependency that is only needed for building or testing the resulting
1.184 rillig 7687: 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.1 dsieger 7688: <p>This means that if you only need a package present whilst
1.175 gutterid 7689: you are building or testing, it should be noted as a
7690: <code class="varname">TOOL_DEPENDS</code>,
7691: <code class="varname">BUILD_DEPENDS</code>, or
7692: <code class="varname">TEST_DEPENDS</code>. When cross-compiling,
1.156 leot 7693: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
7694: packages, i.e. packages for the architecture where the package
7695: is built;
7696: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.175 gutterid 7697: packages, i.e., packages for the architecture for which the package
1.156 leot 7698: is built.</p>
1.175 gutterid 7699: <p>The format for a <code class="varname">DEPENDS</code>,
7700: <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7701: and <code class="varname">TEST_DEPENDS</code> definition is:</p>
1.1 dsieger 7702: <pre class="programlisting">
7703: <pre-req-package-name>:../../<category>/<pre-req-package>
1.111 sevan 7704: </pre>
1.23 wiz 7705: <p>Please note that the <span class="quote">“<span class="quote">pre-req-package-name</span>”</span>
1.1 dsieger 7706: may include any of the wildcard version numbers recognized by
1.246 leot 7707: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
1.23 wiz 7708: <div class="orderedlist"><ol class="orderedlist" type="1">
7709: <li class="listitem">
1.1 dsieger 7710: <p>If your package needs another package's binaries or
1.54 wiz 7711: libraries to build and run, and if that package has a
1.1 dsieger 7712: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7713: <pre class="programlisting">
7714: .include "../../graphics/jpeg/buildlink3.mk"
1.111 sevan 7715: </pre>
1.1 dsieger 7716: </li>
1.23 wiz 7717: <li class="listitem">
1.54 wiz 7718: <p>If your package needs another package's binaries or
7719: libraries only for building, and if that package has a
7720: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7721: <pre class="programlisting">
7722: .include "../../graphics/jpeg/buildlink3.mk"
1.111 sevan 7723: </pre>
1.54 wiz 7724: <p>but set
7725: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>jpeg</code></em>?=build</code>
7726: to make it a build dependency only. This case is rather
7727: rare.</p>
7728: </li>
7729: <li class="listitem">
1.25 spz 7730: <p>If your package needs binaries from another package to build,
1.156 leot 7731: use the <code class="varname">TOOL_DEPENDS</code> definition:</p>
1.1 dsieger 7732: <pre class="programlisting">
1.156 leot 7733: TOOL_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
1.111 sevan 7734: </pre>
1.1 dsieger 7735: </li>
1.156 leot 7736: <li class="listitem"><p>If your package needs static libraries to link against, header
7737: files to include, etc. from another package to build,
7738: use the <code class="varname">BUILD_DEPENDS</code> definition.</p></li>
1.25 spz 7739: <li class="listitem"><p>If your package needs a library with which to link and
7740: there is no <code class="filename">buildlink3.mk</code> file
7741: available, create one. Using
7742: <code class="varname">DEPENDS</code> won't be sufficient because the
7743: include files and libraries will be hidden from the compiler.</p></li>
1.23 wiz 7744: <li class="listitem">
1.25 spz 7745: <p>If your package needs some executable to be able to run
7746: correctly and if there's no
7747: <code class="filename">buildlink3.mk</code> file, this is specified
7748: using the <code class="varname">DEPENDS</code> variable. The
1.207 leot 7749: <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.129 wiz 7750: be able to execute the latex binary from the tex-latex-bin package
1.25 spz 7751: when it runs, and that is specified:</p>
1.1 dsieger 7752: <pre class="programlisting">
1.129 wiz 7753: DEPENDS+= tex-latex-bin-[0-9]*:../../print/tex-latex-bin
1.111 sevan 7754: </pre>
1.25 spz 7755: </li>
1.175 gutterid 7756: <li class="listitem"><p>If your package includes a test suite that has extra
7757: dependencies only required for this purpose (frequently this
7758: can be run as a <span class="quote">“<span class="quote">make test</span>”</span> target), use the
7759: <code class="varname">TEST_DEPENDS</code> variable.</p></li>
1.25 spz 7760: <li class="listitem">
7761: <p>You can use wildcards in package dependencies. Note that
7762: such wildcard dependencies are retained when creating binary
7763: packages. The dependency is checked when installing the binary
7764: package and any package which matches the pattern will be
7765: used. Wildcard dependencies should be used with care.</p>
1.23 wiz 7766: <p>The <span class="quote">“<span class="quote">-[0-9]*</span>”</span> should be used instead of
7767: <span class="quote">“<span class="quote">-*</span>”</span> to avoid potentially ambiguous matches
7768: such as <span class="quote">“<span class="quote">tk-postgresql</span>”</span> matching a
7769: <span class="quote">“<span class="quote">tk-*</span>”</span> <code class="varname">DEPENDS</code>.</p>
1.1 dsieger 7770: <p>Wildcards can also be used to specify that a package
7771: will only build against a certain minimum version of a
7772: pre-requisite:</p>
7773: <pre class="programlisting">
1.25 spz 7774: DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
1.111 sevan 7775: </pre>
1.25 spz 7776: <p>This means that the package will build using version 6.0
7777: of ImageMagick or newer. Such a dependency may be warranted
7778: if, for example, the command line options of an executable
7779: have changed.</p>
7780: <p>If you need to depend on minimum versions of libraries,
1.183 wiz 7781: set
7782: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
7783: to the appropriate pattern before including its
7784: <code class="filename">buildlink3.mk</code> file, e.g.</p>
7785: <pre class="programlisting">
7786: BUILDLINK_API_DEPENDS.jpeg+= jpeg>=9.0
7787: .include "../../graphics/jpeg/buildlink3.mk"
7788: </pre>
1.1 dsieger 7789: <p>For security fixes, please update the package
1.154 rillig 7790: 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.1 dsieger 7791: information.</p>
7792: </li>
7793: </ol></div>
7794: <p>If your package needs files from another package to build,
7795: add the relevant distribution files to
7796: <code class="varname">DISTFILES</code>, so they will be extracted
1.207 leot 7797: 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.1 dsieger 7798: (It relies on the jpeg sources being present in source form
7799: during the build.)</p>
7800: </div>
1.41 asau 7801: <div class="sect2">
1.1 dsieger 7802: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7803: <a name="conflicts"></a>21.1.6. Handling conflicts with other packages</h3></div></div></div>
1.226 gutterid 7804: <p>Your package may conflict with other packages users might
7805: already have installed on their system, e.g., if your package
1.1 dsieger 7806: installs the same set of files as another package in the pkgsrc
1.227 wiz 7807: tree.</p>
1.207 leot 7808: <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>
7809: 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.142 leot 7810: install the same shared library, thus you set in
7811: <code class="filename">pkgsrc/x11/libXaw3d/Makefile</code>:</p>
7812: <pre class="programlisting">
7813: CONFLICTS= Xaw-Xpm-[0-9]*
1.238 wiz 7814: </pre>
1.142 leot 7815: <p>and in <code class="filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>:</p>
7816: <pre class="programlisting">
7817: CONFLICTS= libXaw3d-[0-9]*
1.238 wiz 7818: </pre>
1.246 leot 7819: <p><a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> is able to detect attempts to install packages
1.142 leot 7820: that conflict with existing packages and abort. However, in many
7821: situations this is too late in the process. Binary package managers
7822: will not know about the conflict until they attempt to install the
7823: package after already downloading it and all its dependencies.
7824: Users may also waste time building a package and its dependencies
7825: only to find out at the end that it conflicts with another package
7826: they have installed.</p>
7827: <p>To avoid these issues <code class="varname">CONFLICTS</code> entries
7828: should be added in all cases where it is known that packages conflict
7829: with each other. These <code class="varname">CONFLICTS</code> entries are
1.246 leot 7830: exported in <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> files and consumed by binary package
1.142 leot 7831: managers to inform users that packages cannot be installed onto
7832: the target system.</p>
1.1 dsieger 7833: </div>
1.41 asau 7834: <div class="sect2">
1.1 dsieger 7835: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7836: <a name="not-building-packages"></a>21.1.7. Packages that cannot or should not be built</h3></div></div></div>
1.1 dsieger 7837: <p>There are several reasons why a package might be
7838: instructed to not build under certain circumstances. If the
7839: package builds and runs on most platforms, the exceptions
1.83 dholland 7840: should be noted with <code class="varname">BROKEN_ON_PLATFORM</code>. If
7841: the package builds and runs on a small handful of platforms,
7842: set <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> instead.
7843: Both <code class="varname">BROKEN_ON_PLATFORM</code> and
7844: <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> are OS triples
7845: (OS-version-platform) that can use glob-style
7846: wildcards.</p>
7847: <p>If a package is not appropriate for some platforms (as
1.114 maya 7848: opposed to merely broken), a different set of variables should be
1.83 dholland 7849: used as this affects failure reporting and statistics.
7850: If the package is appropriate for most platforms, the exceptions
1.1 dsieger 7851: should be noted with <code class="varname">NOT_FOR_PLATFORM</code>. If
1.83 dholland 7852: the package is appropriate for only a small handful of platforms
7853: (often exactly one), set <code class="varname">ONLY_FOR_PLATFORM</code> instead.
1.1 dsieger 7854: Both <code class="varname">ONLY_FOR_PLATFORM</code> and
7855: <code class="varname">NOT_FOR_PLATFORM</code> are OS triples
7856: (OS-version-platform) that can use glob-style
7857: wildcards.</p>
7858: <p>Some packages are tightly bound to a specific version of an
1.207 leot 7859: 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.1 dsieger 7860: backwards compatible with other versions of the OS, and should be
7861: uploaded to a version specific directory on the FTP server. Mark
7862: these packages by setting <code class="varname">OSVERSION_SPECIFIC</code> to
1.23 wiz 7863: <span class="quote">“<span class="quote">yes</span>”</span>. This variable is not currently used by any of
1.1 dsieger 7864: the package system internals, but may be used in the
7865: future.</p>
7866: <p>If the package should be skipped (for example, because it
7867: provides functionality already provided by the system), set
7868: <code class="varname">PKG_SKIP_REASON</code> to a descriptive message. If
7869: the package should fail because some preconditions are not met,
7870: set <code class="varname">PKG_FAIL_REASON</code> to a descriptive
7871: message.</p>
7872: </div>
1.41 asau 7873: <div class="sect2">
1.1 dsieger 7874: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7875: <a name="undeletable-packages"></a>21.1.8. Packages which should not be deleted, once installed</h3></div></div></div>
1.1 dsieger 7876: <p>To ensure that a package may not be deleted, once it has been
7877: installed, the <code class="varname">PKG_PRESERVE</code> definition should
7878: be set in the package Makefile. This will be carried into any
7879: binary package that is made from this pkgsrc entry. A
1.23 wiz 7880: <span class="quote">“<span class="quote">preserved</span>”</span> package will
1.246 leot 7881: not be deleted using <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
1.23 wiz 7882: <span class="quote">“<span class="quote">-f</span>”</span> option is used.</p>
1.1 dsieger 7883: </div>
1.41 asau 7884: <div class="sect2">
1.1 dsieger 7885: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7886: <a name="security-handling"></a>21.1.9. Handling packages with security problems</h3></div></div></div>
1.1 dsieger 7887: <p>When a vulnerability is found, this should be noted in
1.247 wiz 7888: <code class="filename">pkgsrc/doc/pkg-vulnerabilities</code>.
1.205 wiz 7889: Entries in that file consist of three parts:</p>
7890: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7891: <li class="listitem"><p>package version pattern</p></li>
7892: <li class="listitem"><p>type of vulnerability (please cut'n'paste an existing one where possible)</p></li>
7893: <li class="listitem"><p>URL providing additional information about the issue</p></li>
7894: </ul></div>
7895: <p>For the package version pattern please always use `<' to
7896: mark an upper bound (not `<='!). This will avoid possible
7897: problems due unrelated <code class="varname">PKGREVISION</code> bumps not
7898: related to security fixes. Lower bounds can be added too, using
7899: '>' or '>='. For example,
1.206 wiz 7900: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.2</code></span>”</span> would mark
1.205 wiz 7901: versions 1.0 (included) to 1.2 (excluded) of
7902: <span class="quote">“<span class="quote"><code class="literal">foo</code></span>”</span> as affected by the security
7903: issue.</p>
7904: <p>Entries should always be added at the bottom of the file.</p>
7905: <p>When fixing packages, please modify the upper bound of the
7906: corresponding entry. To continue the previous example, if a fix
7907: was backported to version 1.1nb2, change the previous pattern to
1.206 wiz 7908: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.1nb2</code></span>”</span>.</p>
1.205 wiz 7909: <p>To locally test a package version pattern against a
7910: <code class="varname">PKGNAME</code> you can use the <span class="command"><strong>pkg_admin
7911: pmatch</strong></span> command.</p>
7912: <p>The URL should be as permanent as possible and provide as
7913: much information about the issue as possible. CVE entries are
7914: preferred.</p>
7915: <p>After committing that file, ask pkgsrc-security@NetBSD.org to
1.31 wiz 7916: update the file on ftp.NetBSD.org.</p>
1.1 dsieger 7917: <p>After fixing the vulnerability by a patch, its
1.31 wiz 7918: <code class="varname">PKGREVISION</code> should be increased (this is of
7919: course not necessary if the problem is fixed by using a newer
7920: release of the software), and the pattern in the
7921: pkg-vulnerabilities file must be updated.</p>
1.1 dsieger 7922: <p>Also, if the fix should be applied to the stable pkgsrc
7923: branch, be sure to submit a pullup request!</p>
7924: <p>Binary packages already on ftp.NetBSD.org will be handled
7925: semi-automatically by a weekly cron job.</p>
1.205 wiz 7926: <p>In case a security issue is disputed, please contact
7927: pkgsrc-security@NetBSD.org.</p>
1.1 dsieger 7928: </div>
1.41 asau 7929: <div class="sect2">
1.1 dsieger 7930: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7931: <a name="bumping-pkgrevision"></a>21.1.10. How to handle incrementing versions when fixing an existing package</h3></div></div></div>
1.1 dsieger 7932: <p>When making fixes to an existing package it can be useful
7933: to change the version number in <code class="varname">PKGNAME</code>. To
7934: avoid conflicting with future versions by the original author, a
1.23 wiz 7935: <span class="quote">“<span class="quote">nb1</span>”</span>, <span class="quote">“<span class="quote">nb2</span>”</span>, ... suffix can be used
1.1 dsieger 7936: on package versions by setting <code class="varname">PKGREVISION=1</code>
1.23 wiz 7937: (2, ...). The <span class="quote">“<span class="quote">nb</span>”</span> is treated like a
7938: <span class="quote">“<span class="quote">.</span>”</span> by the package tools. e.g.</p>
1.1 dsieger 7939: <pre class="programlisting">
7940: DISTNAME= foo-17.42
7941: PKGREVISION= 9
1.111 sevan 7942: </pre>
1.1 dsieger 7943: <p>will result in a <code class="varname">PKGNAME</code> of
1.23 wiz 7944: <span class="quote">“<span class="quote">foo-17.42nb9</span>”</span>. If you want to use the original
7945: value of <code class="varname">PKGNAME</code> without the <span class="quote">“<span class="quote">nbX</span>”</span>
1.1 dsieger 7946: suffix, e.g. for setting <code class="varname">DIST_SUBDIR</code>, use
7947: <code class="varname">PKGNAME_NOREV</code>.</p>
7948: <p>When a new release of the package is released, the
7949: <code class="varname">PKGREVISION</code> should be removed, e.g. on a new
7950: minor release of the above package, things should be like:</p>
7951: <pre class="programlisting">
7952: DISTNAME= foo-17.43
1.111 sevan 7953: </pre>
1.1 dsieger 7954: <p><code class="varname">PKGREVISION</code> should be incremented for any
7955: non-trivial change in the resulting binary package. Without a
7956: <code class="varname">PKGREVISION</code> bump, someone with the previous
7957: version installed has no way of knowing that their package is out
7958: of date. Thus, changes without increasing
7959: <code class="varname">PKGREVISION</code> are essentially labeled "this is so
7960: trivial that no reasonable person would want to upgrade", and this
7961: is the rough test for when increasing
7962: <code class="varname">PKGREVISION</code> is appropriate. Examples of
7963: changes that do not merit increasing
7964: <code class="varname">PKGREVISION</code> are:</p>
1.41 asau 7965: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7966: <li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>,
1.169 rillig 7967: <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>, or
7968: comments in Makefile.</p></li>
7969: <li class="listitem"><p>Changing build variables if the resulting binary
7970: package is the same.</p></li>
7971: <li class="listitem"><p>Changing
7972: <code class="filename">DESCR</code>.</p></li>
7973: <li class="listitem"><p>Adding <code class="varname">PKG_OPTIONS</code> if the
7974: default options don't change.</p></li>
1.1 dsieger 7975: </ul></div>
7976: <p>Examples of changes that do merit an increase to
7977: <code class="varname">PKGREVISION</code> include:</p>
1.41 asau 7978: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.169 rillig 7979: <li class="listitem"><p>Security fixes</p></li>
7980: <li class="listitem"><p>Changes or additions to a patch
7981: file</p></li>
7982: <li class="listitem"><p>Changes to the
7983: <code class="filename">PLIST</code></p></li>
7984: <li class="listitem"><p>A dependency is changed or
7985: renamed.</p></li>
1.1 dsieger 7986: </ul></div>
7987: <p>PKGREVISION must also be incremented when dependencies have ABI
7988: changes.</p>
7989: </div>
1.41 asau 7990: <div class="sect2">
1.1 dsieger 7991: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7992: <a name="fixes.subst"></a>21.1.11. Substituting variable text in the package files (the SUBST framework)</h3></div></div></div>
1.180 rillig 7993: <p>When you want to replace the same text in multiple files, or
7994: multiple times in the same file, it is cumbersome to maintain a patch
7995: file for this. This is where the SUBST framework steps in. It provides an
7996: easy-to-use interface for replacing text in files. It just needs the
7997: following information:</p>
7998: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7999: <li class="listitem"><p>In which phase of the package build cycle should the
8000: replacement happen?</p></li>
8001: <li class="listitem"><p>In which files should the replacement
1.172 rillig 8002: happen?</p></li>
1.180 rillig 8003: <li class="listitem"><p>Which text should be replaced with
8004: what?</p></li>
1.172 rillig 8005: </ul></div>
8006: <p>This information is encoded in a block of <code class="varname">SUBST</code>
1.180 rillig 8007: variables. A minimal example is:</p>
8008: <pre class="programlisting">
8009: SUBST_CLASSES+= paths
8010: SUBST_STAGE.paths= pre-configure
8011: SUBST_FILES.paths= src/*.c
8012: SUBST_SED.paths= -e 's,/usr/local,${PREFIX},g'
8013: </pre>
8014: <p>Translated into English, it means: In the pre-configure stage (that
8015: is, after applying the patches from the patches/ directory and before
8016: running the configure script and the portability check), replace the text
8017: <code class="literal">/usr/local</code> with the content of the variable
8018: <code class="varname">PREFIX</code>.</p>
8019: <p>Each SUBST block starts by appending an identifier to
8020: <code class="varname">SUBST_CLASSES</code> (note the <code class="literal">+=</code>). This
8021: identifier can be chosen freely by the package. If there should ever be
8022: duplicate identifiers, the pkgsrc infrastructure will catch this and fail
8023: early, so don't worry about name collisions.</p>
8024: <p>Except for <code class="varname">SUBST_CLASSES</code>, all variables in a
8025: SUBST block are parameterized using this identifier. In the remainder of
8026: this section, these parameterized variables are written as
8027: <code class="varname">SUBST_STAGE.*</code>.</p>
8028: <pre class="programlisting">
8029: SUBST_CLASSES+= paths
8030: SUBST_STAGE.paths= pre-configure
8031: SUBST_MESSAGE.paths= Fixing absolute paths.
8032: SUBST_FILES.paths= src/*.c
8033: SUBST_FILES.paths+= scripts/*.sh
8034: SUBST_SED.paths= -e 's,"/usr/local,"${PREFIX},g'
8035: SUBST_SED.paths+= -e 's,"/var/log,"${VARBASE}/log,g'
8036: SUBST_VARS.paths= LOCALBASE PREFIX PKGVERSION
8037: </pre>
8038: <p>To get a complete picture about the SUBST substitutions, run
8039: <span class="command"><strong>bmake show-all-subst</strong></span>. If something doesn't work as
8040: expected, run pkglint on the package, which detects several typical
8041: mistakes surrounding the SUBST blocks. For any questions that might
8042: remain after this, have a look at
8043: <code class="filename">mk/subst.mk</code>.</p>
8044: <div class="sect3">
8045: <div class="titlepage"><div><div><h4 class="title">
8046: <a name="fixes.subst.when"></a>21.1.11.1. Choosing the time where the substitutions happen</h4></div></div></div>
8047: <p>The <code class="varname">SUBST_STAGE.*</code> is one of
8048: {pre,do,post}-{extract,patch,configure,build,test,install}. Of these,
8049: <code class="literal">pre-configure</code> is used most often, by far. The most
8050: popular stages are, in chronological order:</p>
8051: <div class="variablelist"><dl class="variablelist">
8052: <dt><span class="term"><code class="literal">post-extract</code></span></dt>
8053: <dd>
8054: <p>The substitutions are applied immediately after the
8055: distfiles are extracted. Running <span class="command"><strong>bmake extract</strong></span> on the
8056: package will leave no traces of the original files.</p>
8057: <p>When the substitution applies to files for which there is also a
8058: patch in the <code class="filename">patches/</code> directory, this means that the
8059: patches will be computed based on the result of the substitution. When
8060: these patches are sent to the upstream maintainer later, to be fixed in
8061: the upstream package, these patches may no longer match what the upstream
8062: author is used to. Because of this, <code class="literal">pre-configure</code> is
8063: often a better choice.</p>
8064: </dd>
8065: <dt><span class="term"><code class="literal">pre-configure</code></span></dt>
8066: <dd>
8067: <p>The substitutions are applied after the patches from the
8068: <code class="filename">patches/</code> directory. This makes it possible to run
8069: <span class="command"><strong>bmake patch</strong></span> on the package, after which the patches
1.207 leot 8070: 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.180 rillig 8071: <p>When updating the patches, it is helpful to explicitly separate the
8072: <span class="command"><strong>bmake patch</strong></span> from the <span class="command"><strong>bmake
8073: configure</strong></span>, and to only edit the patches between these commands.
8074: Otherwise the substitutions from the SUBST block will end up in the patch
8075: file. When this happens in really obvious ways, pkglint will complain
8076: about patches that contain a hard-coded <code class="literal">/usr/pkg</code>
8077: instead of the correct and intended <code class="literal">@PREFIX@</code>, but it
8078: can only detect these really obvious
8079: cases.</p>
8080: </dd>
8081: <dt><span class="term"><code class="literal">do-configure</code></span></dt>
8082: <dd><p>This stage should only be used if the package defines a
8083: <code class="literal">pre-configure</code> action itself, and the substitution must
8084: happen after that. Typical examples are packages that use the
8085: <code class="literal">pre-configure</code> stage to regenerate the GNU configure
8086: script from
8087: <code class="filename">configure.ac</code>.</p></dd>
8088: <dt><span class="term"><code class="literal">post-configure</code></span></dt>
8089: <dd><p>This stage is used to fix up any mistakes by the
8090: configure stage.</p></dd>
8091: <dt><span class="term"><code class="literal">pre-build</code></span></dt>
8092: <dd><p>This stage should only be used for substitutions that are
8093: clearly related to building the package, not for fixing the
8094: configuration. Substitutions for pathnames (such as replacing
8095: <code class="filename">/usr/local</code> with <code class="literal">${PREFIX}</code>) or
8096: user names (such as replacing <code class="literal">@MY_USER@</code> with the
8097: actual username) belong in pre-configure or post-configure
8098: instead.</p></dd>
8099: <dt><span class="term"><code class="literal">post-build</code></span></dt>
8100: <dd>
8101: <p>Just as with pre-build, this stage should only be used
8102: for substitutions that are clearly related to building the package, not
8103: for fixing the configuration. Substitutions for pathnames (such as
8104: replacing <code class="filename">/usr/local</code> with
8105: <code class="literal">${PREFIX}</code>) or user names (such as replacing
8106: <code class="literal">@MY_USER@</code> with the actual username) belong in
8107: pre-configure or post-configure instead.</p>
8108: <p>A typical use is to update pkg-config files to include the rpath
8109: compiler options.</p>
8110: </dd>
8111: <dt><span class="term"><code class="literal">pre-install</code></span></dt>
8112: <dd><p>In general, the install phase should be as simple as
8113: possible. As with the pre-build and post-build stages, it should not be
8114: used to fix pathnames or user names, these belong in pre-configure
8115: instead. There are only few legitimate use cases for applying
8116: substitutions in this stage.</p></dd>
8117: </dl></div>
8118: </div>
8119: <div class="sect3">
8120: <div class="titlepage"><div><div><h4 class="title">
1.181 rillig 8121: <a name="fixes.subst.where"></a>21.1.11.2. Choosing the files where the substitutions happen</h4></div></div></div>
1.180 rillig 8122: <p>The <code class="varname">SUBST_FILES.*</code> variable contains a list of
8123: filename patterns. These patterns are relative to
8124: <code class="varname">WRKSRC</code> since that is where most substitutions happen.
8125: A typical example is:</p>
8126: <pre class="programlisting">
8127: SUBST_FILES.path= Makefile */Makefile */*/Makefile *.[ch]
8128: </pre>
8129: <p>The above patterns, especially the last, are quite broad. The SUBST
8130: implementation checks that each filename pattern that is mentioned here
8131: has an effect. For example, if none of the
8132: <code class="filename">*/*/Makefile</code> files contains the patterns to be found
8133: and substituted, that filename pattern is redundant and should be left
1.181 rillig 8134: out. By default, the SUBST framework will complain with an error message.
8135: If the text to be substituted occurs in some of the files from a single
8136: pattern, but not in all of them, that is totally ok, and the SUBST
1.180 rillig 8137: framework will only print an INFO message for those files.</p>
8138: <p>If there is a good reason for having redundant filename patterns,
1.181 rillig 8139: set <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
1.180 rillig 8140: <p>Another popular way of choosing the files for the substitutions is
8141: via a shell command, like this:</p>
8142: <pre class="programlisting">
1.181 rillig 8143: C_FILES_CMD= cd ${WRKSRC} && ${FIND} . -name '*.c'
1.180 rillig 8144: SUBST_FILES.path= ${C_FILES_CMD:sh}
8145: </pre>
8146: <p>The variable name <code class="varname">C_FILES_CMD</code> in this example is
8147: freely chosen and independent of the SUBST framework.</p>
8148: <p>In this variant, the <code class="varname">SUBST_FILES.*</code> variable
8149: lists each file individually. Thereby chances are higher that there are
8150: filename patterns in which no substitution happens. Since the SUBST
8151: framework cannot know whether the filename patterns in
8152: <code class="varname">SUBST_FILES.*</code> have been explicitly listed in the
8153: Makefile (where any redundant filename pattern would be suspicious) or
8154: been generated by a shell command (in which redundant filename patterns
8155: are more likely and to be expected), it will complain about these
8156: redundant filename patterns. Therefore, SUBST blocks that use a shell
8157: command to generate the list of filename patterns often need to set
8158: <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
8159: </div>
8160: <div class="sect3">
8161: <div class="titlepage"><div><div><h4 class="title">
8162: <a name="fixes.subst.what"></a>21.1.11.3. Choosing what to substitute</h4></div></div></div>
8163: <p>In most cases, the substitutions are given using one or more
1.246 leot 8164: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/sed.1"><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> commands, like this:</p>
1.180 rillig 8165: <pre class="programlisting">
8166: SUBST_SED.path= -e 's|/usr/local|${PREFIX}|g'
8167: </pre>
8168: <p>Each of the sed commands needs to be preceded by the
8169: <code class="literal">-e</code> option and should be specified on a line of its
8170: own, to avoid hiding short sed commands at the end of a line.</p>
8171: <p>Since the sed commands often contain shell metacharacters as the
8172: separator (the <code class="literal">|</code> in the above example), it is common
8173: to enclose them in single quotes.</p>
8174: <p>A common substitution is to replace placeholders of the form
8175: <code class="literal">@VARNAME@</code> with their pkgsrc counterpart variable
8176: <code class="literal">${VARNAME}</code>. A typical example is:</p>
8177: <pre class="programlisting">
8178: SUBST_VARS.path= PREFIX
8179: </pre>
8180: <p>This type of substitutions is typically done by the GNU configure
1.181 rillig 8181: scripts during the do-configure stage, but in some cases these need to be
8182: overridden. The same pattern is also used when a package defines patches
8183: that replace previously hard-coded paths like
8184: <code class="literal">/usr/local</code> with a <code class="literal">@PREFIX@</code>
8185: placeholder first, which then gets substituted by the actual
8186: <code class="literal">${PREFIX}</code> in the pre-configure stage. In many of these
8187: cases, it works equally well to just use the SUBST framework to directly
8188: replace <code class="literal">/usr/local</code> with <code class="literal">${PREFIX}</code>,
8189: thereby omitting the intermediate patch file.</p>
1.180 rillig 8190: <p>If the above is not flexible enough, it is possible to not use sed
8191: at all for the substitution but to specify an entirely different command,
8192: like this:</p>
1.1 dsieger 8193: <pre class="programlisting">
1.180 rillig 8194: SUBST_FILTER_CMD.path= LC_ALL=C ${TR} -d '\r'
8195: </pre>
8196: <p>This is used for the few remaining packages in which the
8197: distributed files use Windows-style line endings that need to be
8198: converted to UNIX-style line endings.</p>
8199: </div>
8200: <div class="sect3">
8201: <div class="titlepage"><div><div><h4 class="title">
8202: <a name="fixes.subst.other"></a>21.1.11.4. Other SUBST variables</h4></div></div></div>
8203: <p>When a SUBST block is applied during a package build, a message is
8204: logged. The default message is fine for most purposes but can be
8205: overridden by setting <code class="literal">SUBST_MESSAGE.*</code> to an individual
8206: message.</p>
8207: </div>
1.1 dsieger 8208: </div>
8209: </div>
1.41 asau 8210: <div class="sect1">
1.1 dsieger 8211: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8212: <a name="fixes.fetch"></a>21.2. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
1.41 asau 8213: <div class="sect2">
1.1 dsieger 8214: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8215: <a name="no-plain-download"></a>21.2.1. Packages whose distfiles aren't available for plain downloading</h3></div></div></div>
1.1 dsieger 8216: <p>If you need to download from a dynamic URL you can set
1.10 hubertf 8217: <code class="varname">DYNAMIC_MASTER_SITES</code> and a <span class="command"><strong>make
1.1 dsieger 8218: fetch</strong></span> will call <code class="filename">files/getsite.sh</code>
8219: with the name of each file to download as an argument, expecting
8220: it to output the URL of the directory from which to download
1.207 leot 8221: 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.1 dsieger 8222: example of this usage.</p>
8223: <p>If the download can't be automated, because the user must
8224: submit personal information to apply for a password, or must pay
8225: for the source, or whatever, you can set
8226: <code class="varname">FETCH_MESSAGE</code> to a list of lines that are
8227: displayed to the user before aborting the build. Example:</p>
8228: <pre class="programlisting">
8229: FETCH_MESSAGE= "Please download the files"
8230: FETCH_MESSAGE+= " "${DISTFILES:Q}
8231: FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
1.111 sevan 8232: </pre>
1.1 dsieger 8233: </div>
1.41 asau 8234: <div class="sect2">
1.1 dsieger 8235: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8236: <a name="modified-distfiles-same-name"></a>21.2.2. How to handle modified distfiles with the 'old' name</h3></div></div></div>
1.1 dsieger 8237: <p>Sometimes authors of a software package make some
8238: modifications after the software was released, and they put up a
8239: new distfile without changing the package's version number. If a
8240: package is already in pkgsrc at that time, the checksum will
8241: no longer match. The contents of the new distfile should be
8242: compared against the old one before changing anything, to make
8243: sure the distfile was really updated on purpose, and that
8244: no trojan horse or so crept in.
8245: Please mention that the distfiles were compared and what was found
1.53 rodent 8246: in your commit message.</p>
1.109 wiz 8247: <p>Then, the correct way to work around this is to set
8248: <code class="varname">DIST_SUBDIR</code> to a unique directory name, usually
8249: based on <code class="varname">PKGNAME_NOREV</code> (but take care with
8250: python or ruby packages, where <code class="varname">PKGNAME</code> includes
8251: a variable prefix). All <code class="varname">DISTFILES</code> and
1.1 dsieger 8252: <code class="varname">PATCHFILES</code> for this package will be put in that
1.154 rillig 8253: 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.1 dsieger 8254: happens more often, <code class="varname">PKGNAME</code> can be used (thus
1.109 wiz 8255: including the <code class="filename">nbX</code> suffix) or a date stamp can
8256: be appended, like
8257: <code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>.</p>
1.169 rillig 8258: <p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's
8259: name does not contain a version and the distfile is apt to change. In
8260: cases where the likelihood of this is very small,
8261: <code class="varname">DIST_SUBDIR</code> might not be required. Additionally,
8262: <code class="varname">DIST_SUBDIR</code> must not be removed unless the
8263: distfile name changes, even if a package is being moved or
8264: renamed.</p>
1.53 rodent 8265: <p>Do not forget regenerating the <code class="filename">distinfo</code> file
1.1 dsieger 8266: after that, since it contains the <code class="varname">DIST_SUBDIR</code>
8267: path in the filenames.
1.53 rodent 8268: Also, increase the PKGREVISION if the installed package is different.
1.1 dsieger 8269: Furthermore, a mail to the package's authors seems appropriate
8270: telling them that changing distfiles after releases without
8271: changing the file names is not good practice.</p>
8272: </div>
1.88 tnn 8273: <div class="sect2">
8274: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8275: <a name="build.fetch.github"></a>21.2.3. Packages hosted on github.com</h3></div></div></div>
1.169 rillig 8276: <p>Helper methods exist for packages hosted on github.com which
8277: will often have distfile names that clash with other packages, for
8278: example <code class="filename">1.0.tar.gz</code>. Use one of the three recipes
8279: from below:</p>
1.88 tnn 8280: <div class="sect3">
8281: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8282: <a name="build.fetch.github.tag"></a>21.2.3.1. Fetch based on a tagged release</h4></div></div></div>
1.169 rillig 8283: <p>If your distfile URL looks similar to
1.189 bacon 8284: <code class="literal">https://github.com/username/example/archive/v1.0.zip</code>,
1.169 rillig 8285: then you are packaging a tagged release.</p>
1.88 tnn 8286: <pre class="programlisting">
1.189 bacon 8287: DISTNAME= example-1.0
1.90 tnn 8288: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.189 bacon 8289: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.90 tnn 8290: GITHUB_TAG= v${PKGVERSION_NOREV}
1.88 tnn 8291: EXTRACT_SUFX= .zip
8292: </pre>
1.230 gutterid 8293: <p>Here, DISTNAME combined with use of GITHUB_TAG leads the
8294: file fetching infrastructure to save the resulting file locally as
8295: <code class="literal">example-1.0.zip</code>.</p>
1.88 tnn 8296: </div>
8297: <div class="sect3">
8298: <div class="titlepage"><div><div><h4 class="title">
1.189 bacon 8299: <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>
8300: <p>If your distfile looks similar to
8301: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit before the first
8302: release, then set the package version to 0.0.0.N, where N is the number
8303: of commits to the repository, and set GITHUB_TAG to the commit hash.
8304: This will (almost) ensure that the first tagged release will have a
8305: version greater than this one so that package upgrades will function
8306: properly.</p>
8307: <pre class="programlisting">
8308: DISTNAME= example-0.0.0.347
8309: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8310: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
8311: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
8312: </pre>
8313: </div>
8314: <div class="sect3">
8315: <div class="titlepage"><div><div><h4 class="title">
8316: <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>
8317: <p>If your distfile looks similar to
8318: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit after a release,
8319: then include the last release version and the commit count since that
8320: release in the package version and set GITHUB_TAG to the commit hash.
8321: The latest release and commit count are shown in the output of
8322: "git describe --tags":
8323: </p>
8324: <pre class="screen">
8325: # git clone https://github.com/username/example
8326: # cd example
8327: # git describe --tags
8328: 1.2.3-5-g988881a
8329: </pre>
1.88 tnn 8330: <pre class="programlisting">
1.189 bacon 8331: DISTNAME= example-1.2.3.5
8332: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8333: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.90 tnn 8334: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
1.111 sevan 8335: </pre>
1.88 tnn 8336: </div>
8337: <div class="sect3">
8338: <div class="titlepage"><div><div><h4 class="title">
1.189 bacon 8339: <a name="build.fetch.github.release"></a>21.2.3.4. Fetch based on release</h4></div></div></div>
1.169 rillig 8340: <p>If your distfile URL looks similar to
1.189 bacon 8341: <code class="literal">https://github.com/username/example/releases/download/rel-1.6/offensive-1.6.zip</code>,
1.169 rillig 8342: then you are packaging a release.</p>
1.88 tnn 8343: <pre class="programlisting">
8344: DISTNAME= offensive-1.6
1.90 tnn 8345: PKGNAME= ${DISTNAME:S/offensive/proper/}
8346: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.189 bacon 8347: GITHUB_PROJECT= example
1.90 tnn 8348: GITHUB_RELEASE= rel-${PKGVERSION_NOREV} # usually just set this to ${DISTNAME}
8349: EXTRACT_SUFX= .zip
1.111 sevan 8350: </pre>
1.88 tnn 8351: </div>
8352: </div>
1.1 dsieger 8353: </div>
1.41 asau 8354: <div class="sect1">
1.1 dsieger 8355: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8356: <a name="fixes.configure"></a>21.3. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
1.41 asau 8357: <div class="sect2">
1.1 dsieger 8358: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8359: <a name="fixes.libtool"></a>21.3.1. Shared libraries - libtool</h3></div></div></div>
1.1 dsieger 8360: <p>pkgsrc supports many different machines, with different
8361: object formats like a.out and ELF, and varying abilities to do
8362: shared library and dynamic loading at all. To accompany this,
8363: varying commands and options have to be passed to the
8364: compiler, linker, etc. to get the Right Thing, which can be
8365: pretty annoying especially if you don't have all the machines
8366: at your hand to test things. The
1.207 leot 8367: <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.23 wiz 8368: can help here, as it just <span class="quote">“<span class="quote">knows</span>”</span> how to build
1.1 dsieger 8369: both static and dynamic libraries from a set of source files,
8370: thus being platform-independent.</p>
8371: <p>Here's how to use libtool in a package in seven simple
8372: steps:</p>
1.23 wiz 8373: <div class="orderedlist"><ol class="orderedlist" type="1">
8374: <li class="listitem"><p>Add <code class="varname">USE_LIBTOOL=yes</code> to the package
1.1 dsieger 8375: Makefile.</p></li>
1.23 wiz 8376: <li class="listitem"><p>For library objects, use <span class="quote">“<span class="quote">${LIBTOOL} --mode=compile
8377: ${CC}</span>”</span> in place of <span class="quote">“<span class="quote">${CC}</span>”</span>. You could even
1.1 dsieger 8378: add it to the definition of <code class="varname">CC</code>, if only
8379: libraries are being built in a given Makefile. This one command
8380: will build both PIC and non-PIC library objects, so you need not
8381: have separate shared and non-shared library rules.</p></li>
1.23 wiz 8382: <li class="listitem">
1.1 dsieger 8383: <p>For the linking of the library, remove any
1.23 wiz 8384: <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
8385: -Bshareable</span>”</span> commands, and instead use:</p>
1.1 dsieger 8386: <pre class="programlisting">
8387: ${LIBTOOL} --mode=link \
8388: ${CC} -o ${.TARGET:.a=.la} \
8389: ${OBJS:.o=.lo} \
8390: -rpath ${PREFIX}/lib \
8391: -version-info major:minor
1.111 sevan 8392: </pre>
1.1 dsieger 8393: <p>Note that the library is changed to have a
8394: <code class="filename">.la</code> extension, and the objects are
8395: changed to have a <code class="filename">.lo</code>
8396: extension. Change <code class="varname">OBJS</code> as
8397: necessary. This automatically creates all of the
8398: <code class="filename">.a</code>,
8399: <code class="filename">.so.major.minor</code>, and ELF symlinks (if
8400: necessary) in the build directory. Be sure to include
1.23 wiz 8401: <span class="quote">“<span class="quote">-version-info</span>”</span>, especially when major and
1.1 dsieger 8402: minor are zero, as libtool will otherwise strip off the
8403: shared library version.</p>
8404: <p>From the libtool manual:</p>
8405: <pre class="programlisting">
8406: So, libtool library versions are described by three integers:
8407:
8408: CURRENT
8409: The most recent interface number that this library implements.
8410:
8411: REVISION
8412: The implementation number of the CURRENT interface.
8413:
8414: AGE
8415: The difference between the newest and oldest interfaces that
8416: this library implements. In other words, the library implements
8417: all the interface numbers in the range from number `CURRENT -
8418: AGE' to `CURRENT'.
8419:
8420: If two libraries have identical CURRENT and AGE numbers, then the
8421: dynamic linker chooses the library with the greater REVISION number.
1.111 sevan 8422: </pre>
1.23 wiz 8423: <p>The <span class="quote">“<span class="quote">-release</span>”</span> option will produce
1.1 dsieger 8424: different results for a.out and ELF (excluding symlinks)
8425: in only one case. An ELF library of the form
1.23 wiz 8426: <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.1 dsieger 8427: will have a symlink of
1.23 wiz 8428: <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.1 dsieger 8429: on an a.out platform. This is handled
8430: automatically.</p>
1.23 wiz 8431: <p>The <span class="quote">“<span class="quote">-rpath argument</span>”</span> is the install
1.1 dsieger 8432: directory of the library being built.</p>
8433: <p>In the <code class="filename">PLIST</code>, include only the
8434: <code class="filename">.la</code> file, the other files will be
8435: added automatically.</p>
8436: </li>
1.23 wiz 8437: <li class="listitem">
1.1 dsieger 8438: <p>When linking shared object (<code class="filename">.so</code>)
1.246 leot 8439: files, i.e. files that are loaded via <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/dlopen.3"><span class="citerefentry"><span class="refentrytitle">dlopen</span>(3)</span></a>, NOT
1.23 wiz 8440: shared libraries, use <span class="quote">“<span class="quote">-module
8441: -avoid-version</span>”</span> to prevent them getting version
1.1 dsieger 8442: tacked on.</p>
8443: <p>The <code class="filename">PLIST</code> file gets the
8444: <code class="filename">foo.so</code> entry.</p>
8445: </li>
1.23 wiz 8446: <li class="listitem">
1.1 dsieger 8447: <p>When linking programs that depend on these libraries
8448: <span class="emphasis"><em>before</em></span> they are installed, preface
1.246 leot 8449: the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/cc.1"><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/ld.1"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8450: --mode=link</span>”</span>, and it will find the correct
1.1 dsieger 8451: libraries (static or shared), but please be aware that
8452: libtool will not allow you to specify a relative path in
1.23 wiz 8453: -L (such as <span class="quote">“<span class="quote">-L../somelib</span>”</span>), because it
1.1 dsieger 8454: expects you to change that argument to be the
8455: <code class="filename">.la</code> file. e.g.</p>
8456: <pre class="programlisting">
8457: ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
1.111 sevan 8458: </pre>
1.1 dsieger 8459: <p>should be changed to:</p>
8460: <pre class="programlisting">
8461: ${LIBTOOL} --mode=link ${CC} -o <em class="replaceable"><code>someprog</code></em> <em class="replaceable"><code>../somelib/somelib.la</code></em>
1.111 sevan 8462: </pre>
1.1 dsieger 8463: <p>and it will do the right thing with the libraries.</p>
8464: </li>
1.23 wiz 8465: <li class="listitem">
1.246 leot 8466: <p>When installing libraries, preface the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a>
8467: or <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/cp.1"><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8468: --mode=install</span>”</span>, and change the library name to
1.1 dsieger 8469: <code class="filename">.la</code>. e.g.</p>
8470: <pre class="programlisting">
1.22 jakllsch 8471: ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib
1.111 sevan 8472: </pre>
1.1 dsieger 8473: <p>This will install the static <code class="filename">.a</code>,
8474: shared library, any needed symlinks, and run
1.246 leot 8475: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/ldconfig.8"><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
1.1 dsieger 8476: </li>
1.23 wiz 8477: <li class="listitem"><p>In your <code class="filename">PLIST</code>, include only
1.1 dsieger 8478: the <code class="filename">.la</code>
8479: file (this is a change from previous behaviour).</p></li>
8480: </ol></div>
8481: </div>
1.41 asau 8482: <div class="sect2">
1.1 dsieger 8483: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8484: <a name="using-libtool"></a>21.3.2. Using libtool on GNU packages that already support libtool</h3></div></div></div>
1.1 dsieger 8485: <p>Add <code class="varname">USE_LIBTOOL=yes</code> to the
8486: package Makefile. This will override the package's own libtool
8487: in most cases. For older libtool using packages, libtool is
8488: made by ltconfig script during the do-configure step; you can
1.10 hubertf 8489: check the libtool script location by doing <span class="command"><strong>make
1.1 dsieger 8490: configure; find work*/ -name libtool</strong></span>.</p>
8491: <p><code class="varname">LIBTOOL_OVERRIDE</code> specifies which libtool
8492: scripts, relative to <code class="varname">WRKSRC</code>, to override. By
1.23 wiz 8493: default, it is set to <span class="quote">“<span class="quote">libtool */libtool
8494: */*/libtool</span>”</span>. If this does not match the location of the
1.1 dsieger 8495: package's libtool script(s), set it as appropriate.</p>
8496: <p>If you do not need <code class="filename">*.a</code> static
8497: libraries built and installed, then use
8498: <code class="varname">SHLIBTOOL_OVERRIDE</code> instead.</p>
8499: <p>If your package makes use of the platform-independent library
8500: for loading dynamic shared objects, that comes with libtool
8501: (libltdl), you should include devel/libltdl/buildlink3.mk.</p>
8502: <p>Some packages use libtool incorrectly so that the package
8503: may not work or build in some circumstances. Some of the more
8504: common errors are:</p>
1.41 asau 8505: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8506: <li class="listitem">
1.1 dsieger 8507: <p>The inclusion of a shared object (-module) as a dependent library in an
8508: executable or library. This in itself isn't a problem if one of two things
8509: has been done:</p>
1.23 wiz 8510: <div class="orderedlist"><ol class="orderedlist" type="1">
8511: <li class="listitem"><p>The shared object is named correctly, i.e.
1.1 dsieger 8512: <code class="filename">libfoo.la</code>, not
8513: <code class="filename">foo.la</code></p></li>
1.23 wiz 8514: <li class="listitem"><p>The -dlopen option is used when linking an executable.</p></li>
1.1 dsieger 8515: </ol></div>
8516: </li>
1.23 wiz 8517: <li class="listitem"><p>The use of libltdl without the correct calls to initialisation routines.
1.1 dsieger 8518: The function lt_dlinit() should be called and the macro
8519: <code class="varname">LTDL_SET_PRELOADED_SYMBOLS</code> included in
8520: executables.</p></li>
8521: </ul></div>
8522: </div>
1.41 asau 8523: <div class="sect2">
1.1 dsieger 8524: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8525: <a name="autoconf-automake"></a>21.3.3. GNU Autoconf/Automake</h3></div></div></div>
1.1 dsieger 8526: <p>If a package needs GNU autoconf or automake to be executed
1.223 nia 8527: to regenerate the
8528: <code class="filename">configure</code>
8529: script and <code class="filename">Makefile.in</code> makefile
8530: templates from <code class="filename">configure.ac</code> and
8531: <code class="filename">Makefile.am</code>,
8532: then they should be executed in a pre-configure target:</p>
1.1 dsieger 8533: <pre class="programlisting">
1.223 nia 8534: USE_TOOLS+= autoconf automake autoreconf
8535: GNU_CONFIGURE= yes
1.1 dsieger 8536: ...
8537:
8538: pre-configure:
1.223 nia 8539: set -e; cd ${WRKSRC} && autoreconf -fi
1.1 dsieger 8540: ...
1.111 sevan 8541: </pre>
1.223 nia 8542: <p>Packages which use GNU Automake will sometimes
8543: require GNU Make (<code class="literal">gmake</code> in
8544: <code class="varname">USE_TOOLS</code>),
8545: but not always. Note that autoreconf
8546: only needs to be executed if <code class="filename">configure.ac</code>
8547: or Makefiles are modified, or <code class="filename">configure</code>
8548: is not present.</p>
1.1 dsieger 8549: <p>There are times when the configure process makes
8550: additional changes to the generated files, which then causes
8551: the build process to try to re-execute the automake sequence.
8552: This is prevented by touching various files in the configure
8553: stage. If this causes problems with your package you can set
8554: <code class="varname">AUTOMAKE_OVERRIDE=NO</code> in the package
8555: Makefile.</p>
8556: </div>
1.223 nia 8557: <div class="sect2">
8558: <div class="titlepage"><div><div><h3 class="title">
8559: <a name="meson"></a>21.3.4. Meson / ninja</h3></div></div></div>
8560: <p>Packages using Meson to configure need to include:
8561:
8562: </p>
8563: <pre class="programlisting">
8564: .include "../../devel/meson/build.mk"
8565: </pre>
8566: <p>In nearly all cases (any program with dependencies),
8567: pkg-config needs to be added to
8568: <code class="varname">USE_TOOLS</code>. If the package installs
8569: translation files for non-English languages, also
8570: add msgfmt and xgettext:
8571:
8572: </p>
8573: <pre class="programlisting">
8574: USE_TOOLS+= pkg-config msgfmt xgettext
8575: </pre>
8576: <p>If any options need to be passed to Meson, use
8577: <code class="varname">MESON_ARGS</code> instead of
8578: <code class="varname">CONFIGURE_ARGS</code>:
8579:
8580: </p>
8581: <pre class="programlisting">
8582: MESON_ARGS+= -Dx11=false
8583: </pre>
8584: </div>
1.1 dsieger 8585: </div>
1.41 asau 8586: <div class="sect1">
1.1 dsieger 8587: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8588: <a name="programming-languages"></a>21.4. Programming languages</h2></div></div></div>
1.41 asau 8589: <div class="sect2">
1.1 dsieger 8590: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8591: <a name="basic-programming-languages"></a>21.4.1. C, C++, and Fortran</h3></div></div></div>
1.244 gutterid 8592: <p>Compilers for the C and C++ languages come with
1.1 dsieger 8593: the NetBSD base system. By default, pkgsrc assumes that a package
8594: is written in C and will hide all other compilers (via the wrapper
1.184 rillig 8595: framework, see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p>
1.243 gutterid 8596: <p>To declare which languages should be made available through
8597: pkgsrc's compiler wrappers, use
1.1 dsieger 8598: the <code class="varname">USE_LANGUAGES</code> variable. Allowed values
1.212 wiz 8599: currently are:
1.238 wiz 8600: </p>
1.212 wiz 8601: <pre class="programlisting">
1.244 gutterid 8602: c, c++, fortran, fortran77, java, objc, obj-c++, and ada.
1.238 wiz 8603: </pre>
1.212 wiz 8604: <p>
8605: (and any combination). The default is
1.23 wiz 8606: <span class="quote">“<span class="quote">c</span>”</span>. Packages using GNU configure scripts, even if
1.1 dsieger 8607: written in C++, usually need a C compiler for the configure
1.244 gutterid 8608: phase.</p>
1.250 jnemeth 8609: <p>To declare which features a package requires from the
1.243 gutterid 8610: compiler, set either <code class="varname">USE_CC_FEATURES</code>
8611: or <code class="varname">USE_CXX_FEATURES</code>. Allowed values for
8612: <code class="varname">USE_CC_FEATURES</code> are currently:
8613: </p>
8614: <pre class="programlisting">
8615: c11, c99, has_include
8616: </pre>
8617: <p>
8618: Allowed values for <code class="varname">USE_CXX_FEATURES</code> are
8619: currently:
8620: </p>
8621: <pre class="programlisting">
8622: c++11, c++14, c++17, c++20, has_include, regex, filesystem,
8623: charconv, parallelism_ts, unique_ptr, put_time,
8624: is_trivially_copy_constructible
8625: </pre>
8626: <p>
1.251 gutterid 8627: Note at present these variables only affect use of GCC, not other
8628: compilers.
1.243 gutterid 8629: </p>
1.244 gutterid 8630: <p>Language variants like <code class="literal">gnu99</code> and
8631: <code class="literal">c++11</code> can be specified in <code class="varname">FORCE_C_STD</code>
8632: and <code class="varname">FORCE_CXX_STD</code> if the package does not explicitly set
8633: <code class="literal">-std=...</code> when compiling (i.e. the package
8634: assumes the compiler defaults to C++11 or some other standard).
8635: This is a common bug in upstream build systems.</p>
8636: <p>Allowed values for <code class="varname">FORCE_C_STD</code> are
8637: currently:
8638: </p>
8639: <pre class="programlisting">
8640: c90, c99, c11, gnu90, gnu99, gnu11
8641: </pre>
8642: <p>
8643: </p>
8644: <p>Allowed values for <code class="varname">FORCE_CXX_STD</code> are
8645: currently:
8646: </p>
8647: <pre class="programlisting">
8648: c++03, c++11, c++14, c++17, c++20,
8649: gnu++03, gnu++11, gnu++14, gnu++17, gnu++20
8650: </pre>
8651: <p>
1.251 gutterid 8652: Note at present these variables only affect use of GCC and Clang.
1.244 gutterid 8653: </p>
1.1 dsieger 8654: </div>
1.41 asau 8655: <div class="sect2">
1.1 dsieger 8656: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8657: <a name="java-programming-language"></a>21.4.2. Java</h3></div></div></div>
1.1 dsieger 8658: <p>If a program is written in Java, use the Java framework in
8659: pkgsrc. The package must include
8660: <code class="filename">../../mk/java-vm.mk</code>. This Makefile fragment
8661: provides the following variables:</p>
1.41 asau 8662: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8663: <li class="listitem"><p><code class="varname">USE_JAVA</code> defines if a build
1.1 dsieger 8664: dependency on the JDK is added. If
1.23 wiz 8665: <code class="varname">USE_JAVA</code> is set to <span class="quote">“<span class="quote">run</span>”</span>, then
1.1 dsieger 8666: there is only a runtime dependency on the JDK. The default is
1.23 wiz 8667: <span class="quote">“<span class="quote">yes</span>”</span>, which also adds a build dependency on the
1.1 dsieger 8668: JDK.</p></li>
1.23 wiz 8669: <li class="listitem"><p>Set <code class="varname">USE_JAVA2</code> to declare that
1.1 dsieger 8670: a package needs a Java2 implementation. The supported values
1.23 wiz 8671: are <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">1.4</span>”</span>, and
8672: <span class="quote">“<span class="quote">1.5</span>”</span>. <span class="quote">“<span class="quote">yes</span>”</span> accepts any Java2
8673: implementation, <span class="quote">“<span class="quote">1.4</span>”</span> insists on versions 1.4 or
8674: above, and <span class="quote">“<span class="quote">1.5</span>”</span> only accepts versions 1.5 or
1.1 dsieger 8675: above. This variable is not set by default.</p></li>
1.24 wiz 8676: <li class="listitem"><p><code class="varname">PKG_JAVA_HOME</code> is
8677: automatically set to the runtime location of the used Java
8678: implementation dependency. It may be used to set
8679: <code class="varname">JAVA_HOME</code> to a good value if the program
8680: needs this variable to be defined.
8681: </p></li>
1.1 dsieger 8682: </ul></div>
8683: </div>
1.41 asau 8684: <div class="sect2">
1.1 dsieger 8685: <div class="titlepage"><div><div><h3 class="title">
1.205 wiz 8686: <a name="go-programming-language"></a>21.4.3. Go</h3></div></div></div>
8687: <p>If a program is written in Go and has any dependencies on
8688: other Go modules, have the package include
8689: <code class="filename">../../lang/go/go-module.mk</code>.</p>
8690: <div class="orderedlist"><ol class="orderedlist" type="1">
8691: <li class="listitem"><p>Generate a list of those dependencies with
8692: <span class="command"><strong>make clean && make patch && make show-go-modules >
8693: go-modules.mk</strong></span>.</p></li>
1.223 nia 8694: <li class="listitem"><p>Prepend
8695: <code class="literal">.include "go-modules.mk"</code> to any other
8696: <code class="literal">.include</code>s.</p></li>
8697: <li class="listitem"><p>Incorporate these modules in
8698: <code class="filename">distinfo</code> with <span class="command"><strong>make
8699: makesum</strong></span>.</p></li>
8700: </ol></div>
8701: </div>
8702: <div class="sect2">
8703: <div class="titlepage"><div><div><h3 class="title">
8704: <a name="rust-programming-language"></a>21.4.4. Rust</h3></div></div></div>
8705: <p>If a program is written in Rust and uses Cargo to build,
8706: have the package include
8707: <code class="filename">../../lang/rust/cargo.mk</code>.</p>
8708: <div class="orderedlist"><ol class="orderedlist" type="1">
8709: <li class="listitem"><p>Generate a list of those dependencies with
8710: <span class="command"><strong>make CARGO_ARGS="build --release" build &&
8711: make print-cargo-depends > cargo-depends.mk</strong></span>.</p></li>
8712: <li class="listitem"><p>Prepend
8713: <code class="literal">.include "cargo-depends.mk"</code> to any other
8714: <code class="literal">.include</code>s.</p></li>
1.205 wiz 8715: <li class="listitem"><p>Incorporate these modules in
8716: <code class="filename">distinfo</code> with <span class="command"><strong>make
8717: makesum</strong></span>.</p></li>
8718: </ol></div>
8719: </div>
8720: <div class="sect2">
8721: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8722: <a name="perl-scripts"></a>21.4.5. Packages containing Perl scripts</h3></div></div></div>
1.203 nia 8723: <p>If your package contains interpreted Perl scripts, add
1.23 wiz 8724: <span class="quote">“<span class="quote">perl</span>”</span> to the <code class="varname">USE_TOOLS</code> variable
1.1 dsieger 8725: and set <code class="varname">REPLACE_PERL</code> to ensure that the proper
8726: interpreter path is set. <code class="varname">REPLACE_PERL</code> should
8727: contain a list of scripts, relative to <code class="varname">WRKSRC</code>,
1.74 wiz 8728: that you want adjusted. Every occurrence of
8729: <code class="filename">*/bin/perl</code> in a she-bang line will be
1.210 gutterid 8730: replaced with the full path to the Perl executable.</p>
8731: <p>If a particular version of Perl is needed, set the
1.1 dsieger 8732: <code class="varname">PERL5_REQD</code> variable to the version number. The
1.23 wiz 8733: default is <span class="quote">“<span class="quote">5.0</span>”</span>.</p>
1.203 nia 8734: <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.210 gutterid 8735: about handling Perl modules.</p>
8736: <p>There is also the <code class="varname">REPLACE_PERL6</code> variable
8737: for the language now known as Raku.</p>
1.1 dsieger 8738: </div>
1.41 asau 8739: <div class="sect2">
1.1 dsieger 8740: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8741: <a name="shell-scripts"></a>21.4.6. Packages containing shell scripts</h3></div></div></div>
1.40 wiz 8742: <p><code class="varname">REPLACE_SH</code>,
8743: <code class="varname">REPLACE_BASH</code>, <code class="varname">REPLACE_CSH</code>,
8744: and <code class="varname">REPLACE_KSH</code> can be used to replace shell
1.225 gutterid 8745: she-bangs in files. Please use the appropriate one, preferring
8746: <code class="varname">REPLACE_SH</code> when this shell is sufficient.
1.74 wiz 8747: Each should contain a list of scripts, relative to
8748: <code class="varname">WRKSRC</code>, that you want adjusted. Every
8749: occurrence of the matching shell in a she-bang line will be
8750: replaced with the full path to the shell executable.
1.40 wiz 8751: When using <code class="varname">REPLACE_BASH</code>, don't forget to add
8752: <code class="filename">bash</code> to <code class="varname">USE_TOOLS</code>.</p>
8753: </div>
1.41 asau 8754: <div class="sect2">
1.40 wiz 8755: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8756: <a name="other-programming-languages"></a>21.4.7. Other programming languages</h3></div></div></div>
1.210 gutterid 8757: <p>There are further similar REPLACE variables available, e.g.,
8758: <code class="varname">REPLACE_AWK</code> for packages containing awk scripts,
8759: and <code class="varname">REPLACE_R</code> for R. These two, like the others
1.211 gutterid 8760: noted above, have their actions defined centrally in
1.210 gutterid 8761: <code class="filename">mk/configure/replace-interpreter.mk</code>. Other
1.211 gutterid 8762: languages define the actions of these variables within their own
8763: dedicated part of the tree, e.g., <code class="varname">REPLACE_PHP</code> is
1.245 gutterid 8764: actioned in <code class="filename">lang/php/replace.mk</code>, and
1.211 gutterid 8765: <code class="varname">REPLACE_PYTHON</code> is actioned in
1.210 gutterid 8766: <code class="filename">lang/python/application.mk</code>. For other languages,
8767: consult the mk files found within their specific directories (the
1.216 gutterid 8768: naming convention varies), or check the list found in
8769: <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.210 gutterid 8770: <p>Currently, special handling for other languages varies
1.1 dsieger 8771: in pkgsrc. If a compiler package provides a
8772: <code class="filename">buildlink3.mk</code> file, include that, otherwise
8773: just add a (build) dependency on the appropriate compiler
8774: package.</p>
8775: </div>
8776: </div>
1.41 asau 8777: <div class="sect1">
1.1 dsieger 8778: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8779: <a name="fixes.build"></a>21.5. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.1 dsieger 8780: <p>The most common failures when building a package are that
8781: some platforms do not provide certain header files, functions or
8782: libraries, or they provide the functions in a library that the
8783: original package author didn't know. To work around this, you
8784: can rewrite the source code in most cases so that it does not
8785: use the missing functions or provides a replacement function.</p>
1.41 asau 8786: <div class="sect2">
1.1 dsieger 8787: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8788: <a name="fixes.build.cpp"></a>21.5.1. Compiling C and C++ code conditionally</h3></div></div></div>
1.1 dsieger 8789: <p>If a package already comes with a GNU configure script, the
8790: preferred way to fix the build failure is to change the
8791: configure script, not the code. In the other cases, you can
8792: utilize the C preprocessor, which defines certain macros
8793: depending on the operating system and hardware architecture it
8794: compiles for. These macros can be queried using for example
8795: <code class="varname">#if defined(__i386)</code>. Almost every operating
8796: system, hardware architecture and compiler has its own macro.
8797: For example, if the macros <code class="varname">__GNUC__</code>,
8798: <code class="varname">__i386__</code> and <code class="varname">__NetBSD__</code>
8799: are all defined, you know that you are using NetBSD on an i386
8800: compatible CPU, and your compiler is GCC.</p>
8801: <p>The list of the following macros for hardware and
8802: operating system depends on the compiler that is used. For
8803: example, if you want to conditionally compile code on Solaris,
8804: don't use <code class="varname">__sun__</code>, as the SunPro compiler
8805: does not define it. Use <code class="varname">__sun</code> instead.</p>
1.41 asau 8806: <div class="sect3">
1.1 dsieger 8807: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8808: <a name="fixes.build.cpp.os"></a>21.5.1.1. C preprocessor macros to identify the operating system</h4></div></div></div>
1.223 nia 8809: <p>To distinguish between specific NetBSD versions,
8810: you should use the following code.</p>
8811: <pre class="programlisting">
8812: #ifdef __NetBSD__
8813: #include <sys/param.h>
8814: #if __NetBSD_Prereq__(9,99,17)
8815: /* use a newer feature */
8816: #else
8817: /* older code */
8818: #endif
8819: #endif
8820:
8821: #ifndef _WIN32
8822: /* Unix-like specific code */
8823: #endif
8824: </pre>
1.1 dsieger 8825: <p>To distinguish between 4.4 BSD-derived systems and the
8826: rest of the world, you should use the following code.</p>
8827: <pre class="programlisting">
8828: #include <sys/param.h>
8829: #if (defined(BSD) && BSD >= 199306)
8830: /* BSD-specific code goes here */
8831: #else
8832: /* non-BSD-specific code goes here */
8833: #endif
8834: </pre>
1.223 nia 8835: <p>You can also test for the following macros:</p>
1.1 dsieger 8836: <pre class="programlisting">
1.45 obache 8837: Cygwin __CYGWIN__
8838: DragonFly __DragonFly__
1.1 dsieger 8839: FreeBSD __FreeBSD__
1.45 obache 8840: Haiku __HAIKU__
1.1 dsieger 8841: Interix __INTERIX
8842: IRIX __sgi (TODO: get a definite source for this)
1.223 nia 8843: Linux __linux
1.83 dholland 8844: Mac OS X __APPLE__
1.45 obache 8845: MirBSD __MirBSD__ (__OpenBSD__ is also defined)
8846: Minix3 __minix
1.1 dsieger 8847: NetBSD __NetBSD__
8848: OpenBSD __OpenBSD__
8849: Solaris sun, __sun
8850: </pre>
8851: </div>
1.41 asau 8852: <div class="sect3">
1.1 dsieger 8853: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8854: <a name="fixes.build.cpp.arch"></a>21.5.1.2. C preprocessor macros to identify the hardware architecture</h4></div></div></div>
1.1 dsieger 8855: <pre class="programlisting">
8856: i386 i386, __i386, __i386__
1.223 nia 8857: x86-64 __amd64__, __x86_64__
8858: ARM __arm__
1.1 dsieger 8859: MIPS __mips
8860: SPARC sparc, __sparc
1.223 nia 8861: PowerPC __powerpc
1.1 dsieger 8862: </pre>
8863: </div>
1.41 asau 8864: <div class="sect3">
1.1 dsieger 8865: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8866: <a name="fixes.build.cpp.compiler"></a>21.5.1.3. C preprocessor macros to identify the compiler</h4></div></div></div>
1.1 dsieger 8867: <pre class="programlisting">
8868: GCC __GNUC__ (major version), __GNUC_MINOR__
8869: MIPSpro _COMPILER_VERSION (0x741 for MIPSpro 7.41)
8870: SunPro __SUNPRO_C (0x570 for Sun C 5.7)
8871: SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8)
8872: </pre>
8873: </div>
8874: </div>
1.41 asau 8875: <div class="sect2">
1.1 dsieger 8876: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8877: <a name="compiler-bugs"></a>21.5.2. How to handle compiler bugs</h3></div></div></div>
1.1 dsieger 8878: <p>Some source files trigger bugs in the compiler, based on
8879: combinations of compiler version and architecture and almost
8880: always relation to optimisation being enabled. Common symptoms
8881: are gcc internal errors or never finishing compiling a
8882: file.</p>
8883: <p>Typically, a workaround involves testing the
8884: <code class="varname">MACHINE_ARCH</code> and compiler version, disabling
8885: optimisation for that combination of file,
1.87 tnn 8886: <code class="varname">MACHINE_ARCH</code> and compiler.</p>
8887: <p>This used to be a big problem in the past, but is rarely
8888: needed now as compiler technology has matured. If you still need
8889: to add a compiler specific workaround, please do so in the file
8890: <code class="filename">hacks.mk</code> and describe the symptom and
8891: compiler version as detailed as possible.</p>
1.1 dsieger 8892: </div>
1.41 asau 8893: <div class="sect2">
1.1 dsieger 8894: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 8895: <a name="fixes.build.header"></a>21.5.3. No such file or directory</h3></div></div></div>
8896: <p>Compilation sometimes fails with an error message like this:</p>
8897: <pre class="programlisting">
8898: .../x11/gtk3/work/gtk+-3.24.12/gdk/gdktypes.h:35:10:
8899: fatal error: pango/pango.h: No such file or directory
8900: </pre>
8901: <p>The proper way to fix this problem depends on the type of the
8902: header, which is described in the following sections.</p>
8903: <div class="sect3">
8904: <div class="titlepage"><div><div><h4 class="title">
8905: <a name="fixes.build.header.bl3"></a>21.5.3.1. Headers from other packages</h4></div></div></div>
8906: <p>If the header name looks like it comes from a different package,
8907: that other package should be included via the buildlink3
8908: framework.</p>
8909: <p>First, look whether the header is somewhere in the buildlink3
8910: directory below <code class="varname">WRKDIR</code>. In the above case of
8911: the missing Pango header:</p>
8912: <pre class="programlisting">
8913: <code class="prompt">$</code> find work/.buildlink/ -print | grep -F pango/pango.h
8914: </pre>
8915: <p>In the case of Pango, the output is:</p>
8916: <pre class="programlisting">
8917: work/.buildlink/include/pango-1.0/pango/pango.h
8918: </pre>
8919: <p>If the <code class="filename">pango/pango.h</code> file were placed directly
8920: in the <code class="filename">.buildlink</code> directory, it would have been
8921: found automatically. There is an extra <code class="filename">pango-1.0</code>
8922: path component though, which means that the compiler command line must
8923: contain an option of the form
8924: <code class="literal">-I${BUILDLINK3_PREFIX.pango}/include/pango-1.0</code>. In
8925: most cases this option is generated by the configure script, which can be examined using:</p>
8926: <pre class="programlisting">
8927: <code class="prompt">$</code> $ grep -o '[-]I[^[:space:]]*/pango[^[:space:]]*' work/*/Makefile
8928: -I/usr/pkg/include/pango-1.0
8929: -I/usr/pkg/include/pango-1.0
8930: -I/usr/pkg/include/pango-1.0
8931: -I/usr/pkg/include/pango-1.0
8932: -I/usr/pkg/include/pango-1.0
8933: </pre>
8934: <p>This looks good. These options are transformed by the buildlink
8935: wrapper to refer to the correct path inside
8936: <code class="filename">work/.buildlink</code>.</p>
8937: <p>Since the compilation fails though, examine the compiler command
8938: lines in <code class="filename">work/.work.log</code> to see whether the
8939: <code class="literal">-I</code> option is included in the particular command
8940: line.</p>
8941: <p>To further analyze the situation, run <span class="command"><strong>bmake
8942: build-env</strong></span>, which sets up an interactive, realistic environment
8943: including all the pkgsrc wrapper commands and environment variables. From
8944: there, try to compile some simple example programs that use the
8945: header.</p>
8946: </div>
8947: <div class="sect3">
8948: <div class="titlepage"><div><div><h4 class="title">
8949: <a name="fixes.build.header.gen"></a>21.5.3.2. Headers generated during the build</h4></div></div></div>
8950: <p>If the name of the header seems to come from the package itself,
8951: and if the build is run with parallel jobs, the package may have some
8952: undeclared dependencies between the <code class="filename">.c</code> and the
8953: <code class="filename">.h</code> files, and a C file is compiled before its
8954: required header is generated.</p>
8955: <p>To see whether the build runs with parallel jobs, run
8956: <span class="command"><strong>bmake show-all-build | grep JOBS</strong></span>. Its output looks
8957: like this:</p>
8958: <pre class="programlisting">
8959: usr MAKE_JOBS= 7
8960: pkg MAKE_JOBS_SAFE # undefined
8961: def _MAKE_JOBS_N= 7
8962: </pre>
8963: <p>In this case the pkgsrc user has asked pkgsrc to build packages
8964: with 7 jobs in parallel (<code class="varname">MAKE_JOBS</code>). The
8965: package could have disabled parallel builds by setting
8966: <code class="varname">MAKE_JOBS_SAFE</code> to <code class="literal">no</code>, but
8967: in this case it hasn't.</p>
8968: <p>To see whether the build failure is caused by parallel builds,
8969: first save the exact error message and a bit of context, maybe you need
8970: it later for reporting a bug. Next, run:</p>
8971: <pre class="programlisting">
8972: MAKE_JOBS_SAFE=no bmake clean build
8973: </pre>
8974: <p>If that succeeds, <a class="ulink" href="https://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd" target="_top">file a bug
8975: report</a> against the pkgsrc package, including the exact error
8976: message and the contents of your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file.</p>
8977: </div>
1.173 rillig 8978: <div class="sect3">
8979: <div class="titlepage"><div><div><h4 class="title">
8980: <a name="fixes.build.header.symlink"></a>21.5.3.3. Symlinks</h4></div></div></div>
8981: <p>Pkgsrc does not work reliably if any of
8982: <code class="varname">LOCALBASE</code>, <code class="varname">VARBASE</code> or
8983: <code class="varname">WRKDIR</code> contains a symlink. Since 2019Q2, the pkgsrc
8984: bootstrap program prevents installing pkgsrc in symlink-based
8985: directories. Existing pkgsrc installations are not checked for symlinks
8986: though.</p>
8987: <p>The "No such file or directory" error messages are a typical
8988: symptom of symlinks, and it's quite difficult to find out that this is
8989: the actual cause.</p>
8990: </div>
8991: <div class="sect3">
8992: <div class="titlepage"><div><div><h4 class="title">
8993: <a name="fixes.build.header.stale"></a>21.5.3.4. Stale working directories</h4></div></div></div>
8994: <p>When building a hierarchy of packages, it may happen that one
8995: package is built and then pkgsrc is updated. This situation can provoke
8996: various hard to diagnose build errors. To clean up the situation:</p>
8997: <pre class="programlisting">
1.223 nia 8998: <code class="prompt">$</code> (cd ../../ && cat mk/bsd.pkg.mk >/dev/null && rm -rf */*/work)
1.173 rillig 8999: </pre>
1.223 nia 9000: <p>(The only purpose of the <code class="filename">bsd.pkg.mk</code> is to
9001: prevent running this command in the wrong directory.)</p>
1.173 rillig 9002: <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
9003: that directory as well.</p>
9004: </div>
9005: <div class="sect3">
9006: <div class="titlepage"><div><div><h4 class="title">
9007: <a name="fixes.build.header.misc"></a>21.5.3.5. Other possible reasons</h4></div></div></div>
9008: <p>On platforms other than BSD, third-party packages are installed in
9009: <code class="filename">/usr/include</code>, together with the base system. This
9010: means that pkgsrc cannot distinguish between headers provided by the base
9011: system (which it needs) and headers from third-party packages (which are
9012: often included in pkgsrc as well). This can lead to subtle version
9013: mismatches.</p>
9014: <p>In pkgsrc installations that have been active for several years, it
9015: may happen that some files are manually deleted. To exclude this unlikely
9016: reason, run <span class="command"><strong>pkg_admin check</strong></span>.</p>
9017: <p>It may help to run <span class="command"><strong>pkg_admin rebuild-tree</strong></span> to
9018: check/fix dependencies.</p>
9019: <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>
9020: for contact information. Be prepared to describe what you have tried so
9021: far and what any error messages were.</p>
9022: </div>
1.172 rillig 9023: </div>
9024: <div class="sect2">
9025: <div class="titlepage"><div><div><h3 class="title">
9026: <a name="undefined-reference"></a>21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span>
1.23 wiz 9027: </h3></div></div></div>
1.1 dsieger 9028: <p>This error message often means that a package did not
9029: link to a shared library it needs. The following functions are
9030: known to cause this error message over and over.</p>
9031: <div class="informaltable">
1.106 tnn 9032: <a name="undefined-reference-functions"></a><table class="informaltable" border="1">
1.1 dsieger 9033: <colgroup>
9034: <col>
9035: <col>
9036: <col>
9037: </colgroup>
9038: <thead><tr>
9039: <th>Function</th>
9040: <th>Library</th>
9041: <th>Affected platforms</th>
9042: </tr></thead>
9043: <tbody>
9044: <tr>
9045: <td>accept, bind, connect</td>
9046: <td>-lsocket</td>
9047: <td>Solaris</td>
9048: </tr>
9049: <tr>
9050: <td>crypt</td>
9051: <td>-lcrypt</td>
9052: <td>DragonFly, NetBSD</td>
9053: </tr>
9054: <tr>
9055: <td>dlopen, dlsym</td>
9056: <td>-ldl</td>
9057: <td>Linux</td>
9058: </tr>
9059: <tr>
9060: <td>gethost*</td>
9061: <td>-lnsl</td>
9062: <td>Solaris</td>
9063: </tr>
9064: <tr>
9065: <td>inet_aton</td>
9066: <td>-lresolv</td>
9067: <td>Solaris</td>
9068: </tr>
9069: <tr>
9070: <td>nanosleep, sem_*, timer_*</td>
9071: <td>-lrt</td>
9072: <td>Solaris</td>
9073: </tr>
9074: <tr>
9075: <td>openpty</td>
9076: <td>-lutil</td>
9077: <td>Linux</td>
9078: </tr>
9079: </tbody>
9080: </table>
9081: </div>
1.223 nia 9082: <p>To fix these linker errors, it is often sufficient to add
1.1 dsieger 9083: <code class="literal">LIBS.<em class="replaceable"><code>OperatingSystem</code></em>+=
9084: -l<em class="replaceable"><code>foo</code></em></code> to the package
1.223 nia 9085: <code class="filename">Makefile</code> and then run <span class="command"><strong>bmake clean;
1.1 dsieger 9086: bmake</strong></span>.</p>
1.41 asau 9087: <div class="sect3">
1.1 dsieger 9088: <div class="titlepage"><div><div><h4 class="title">
1.223 nia 9089: <a name="undefined-reference-sunpro"></a>21.5.4.1. The SunPro compiler and inline functions</h4></div></div></div>
1.1 dsieger 9090: <p>When you are using the SunPro compiler, there is another
9091: possibility. That compiler cannot handle the following code:</p>
9092: <pre class="programlisting">
9093: extern int extern_func(int);
9094:
9095: static inline int
9096: inline_func(int x)
9097: {
9098: return extern_func(x);
9099: }
9100:
9101: int main(void)
9102: {
9103: return 0;
9104: }
9105: </pre>
9106: <p>It generates the code for <code class="function">inline_func</code> even if
9107: that function is never used. This code then refers to
9108: <code class="function">extern_func</code>, which can usually not be resolved. To
9109: solve this problem you can try to tell the package to disable inlining
9110: of functions.</p>
9111: </div>
1.228 gutterid 9112: <div class="sect3">
9113: <div class="titlepage"><div><div><h4 class="title">
9114: <a name="undefined-reference-atomic"></a>21.5.4.2. Missing atomic functions</h4></div></div></div>
9115: <p>When building for older machine architectures (e.g., i386, PowerPC),
9116: builds may fail because the package expects modern 64-bit atomic functions
9117: which the underlying hardware either doesn't support, or will only support
9118: with specific compiler flags. This is generally handled via inclusion of
9119: mk/atomic64.mk.</p>
9120: </div>
1.1 dsieger 9121: </div>
1.41 asau 9122: <div class="sect2">
1.1 dsieger 9123: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 9124: <a name="out-of-memory"></a>21.5.5. Running out of memory</h3></div></div></div>
1.1 dsieger 9125: <p>Sometimes packages fail to build because the compiler runs
9126: into an operating system specific soft limit. With the
9127: <code class="varname">UNLIMIT_RESOURCES</code> variable pkgsrc can be told
1.223 nia 9128: to unlimit the resources. The allowed values are any combination of
9129: <span class="quote">“<span class="quote">cputime</span>”</span>,
9130: <span class="quote">“<span class="quote">datasize</span>”</span>,
9131: <span class="quote">“<span class="quote">memorysize</span>”</span>,
9132: <span class="quote">“<span class="quote">stacksize</span>”</span> and
9133: <span class="quote">“<span class="quote">virtualsize</span>”</span>.
1.1 dsieger 9134: Setting this variable is similar to running the shell builtin
1.10 hubertf 9135: <span class="command"><strong>ulimit</strong></span> command to raise the maximum data
1.1 dsieger 9136: segment size or maximum stack size of a process, respectively, to
9137: their hard limits.</p>
9138: </div>
9139: </div>
1.41 asau 9140: <div class="sect1">
1.1 dsieger 9141: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9142: <a name="fixes.install"></a>21.6. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
1.41 asau 9143: <div class="sect2">
1.1 dsieger 9144: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9145: <a name="install-scripts"></a>21.6.1. Creating needed directories</h3></div></div></div>
1.10 hubertf 9146: <p>The BSD-compatible <span class="command"><strong>install</strong></span> supplied
1.1 dsieger 9147: with some operating systems cannot create more than one
9148: directory at a time. As such, you should call
9149: <code class="literal">${INSTALL_*_DIR}</code> like this:</p>
9150: <pre class="programlisting">
9151: ${INSTALL_DATA_DIR} ${PREFIX}/dir1
9152: ${INSTALL_DATA_DIR} ${PREFIX}/dir2
1.111 sevan 9153: </pre>
1.223 nia 9154: <p>Instead of running the <span class="command"><strong>install</strong></span> commands
9155: directly, you can also append <span class="quote">“<span class="quote"><code class="literal">dir1
9156: dir2</code></span>”</span> to the <code class="varname">INSTALLATION_DIRS</code>
9157: variable, which will automatically do the right thing.</p>
1.1 dsieger 9158: </div>
1.41 asau 9159: <div class="sect2">
1.1 dsieger 9160: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9161: <a name="where-to-install-documentation"></a>21.6.2. Where to install documentation</h3></div></div></div>
1.1 dsieger 9162: <p>In general, documentation should be installed into
9163: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
1.223 nia 9164: <code class="filename">${PREFIX}/share/doc/${PKGNAME_NOREV}</code> (the latter
1.1 dsieger 9165: includes the version number of the package).</p>
9166: <p>Many modern packages using GNU autoconf allow to set the
9167: directory where HTML documentation is installed with the
1.223 nia 9168: <span class="quote">“<span class="quote">--with-html-dir</span>”</span> option. Sometimes using this flag is
9169: needed because otherwise the documentation ends up in
9170: <code class="filename">${PREFIX}/share/doc/html</code> or other places. In
9171: pkgsrc, the HTML documentation should go into the package-specific
9172: directory, just like any other documentation.</p>
1.1 dsieger 9173: <p>An exception to the above is that library API documentation
1.207 leot 9174: 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.1 dsieger 9175: browsers (devhelp) should be left at their default location, which
9176: is <code class="filename">${PREFIX}/share/gtk-doc</code>. Such
9177: documentation can be recognized from files ending in
9178: <code class="filename">.devhelp</code> or <code class="filename">.devhelp2</code>.
9179: (It is also acceptable to install such files in
9180: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
9181: <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code>; the
9182: <code class="filename">.devhelp*</code> file must be directly in that
9183: directory then, no additional subdirectory level is allowed in
9184: this case. This is usually achieved by using
1.23 wiz 9185: <span class="quote">“<span class="quote">--with-html-dir=${PREFIX}/share/doc</span>”</span>.
1.1 dsieger 9186: <code class="filename">${PREFIX}/share/gtk-doc</code> is preferred
9187: though.)</p>
9188: </div>
1.41 asau 9189: <div class="sect2">
1.1 dsieger 9190: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9191: <a name="installing-score-files"></a>21.6.3. Installing highscore files</h3></div></div></div>
1.1 dsieger 9192: <p>Certain packages, most of them in the games category, install
9193: a score file that allows all users on the system to record their
9194: highscores. In order for this to work, the binaries need to be
9195: installed setgid and the score files owned by the appropriate
1.35 wiz 9196: group and/or owner (traditionally the "games" user/group). Set
9197: <code class="varname">USE_GAMESGROUP</code> to yes to support this. The
1.1 dsieger 9198: following variables, documented in more detail in
9199: <code class="filename">mk/defaults/mk.conf</code>, control this
1.35 wiz 9200: behaviour: <code class="varname">GAMEDATAMODE</code>,
9201: <code class="varname">GAMEDIRMODE</code>, <code class="varname">GAMES_GROUP</code>,
1.100 leot 9202: <code class="varname">GAMEMODE</code>, <code class="varname">GAME_USER</code>.
9203: Other useful variables are: <code class="varname">GAMEDIR_PERMS</code>,
9204: <code class="varname">GAMEDATA_PERMS</code> and
9205: <code class="varname">SETGID_GAMES_PERMS</code>.</p>
9206: <p>An example that illustrates some of the variables described above is
9207: <code class="filename">games/moon-buggy</code>. <code class="varname">OWN_DIRS_PERMS</code> is
9208: used to properly set directory permissions of the directory where the
9209: scorefile is saved, <code class="varname">REQD_FILES_PERMS</code> is used to create a
9210: dummy scorefile (<code class="filename">mbscore</code>) with the proper permissions
9211: and <code class="varname">SPECIAL_PERMS</code> is used to install setgid the game
9212: binary:</p>
9213: <pre class="programlisting">
1.112 rillig 9214: USE_GAMESGROUP= yes
1.100 leot 9215:
1.112 rillig 9216: BUILD_DEFS+= VARBASE
1.100 leot 9217:
1.112 rillig 9218: OWN_DIRS_PERMS+= ${VARBASE}/games/moon-buggy ${GAMEDIR_PERMS}
9219: REQD_FILES_PERMS+= /dev/null ${VARBASE}/games/moon-buggy/mbscore ${GAMEDATA_PERMS}
9220: SPECIAL_PERMS+= ${PREFIX}/bin/moon-buggy ${SETGID_GAMES_PERMS}
1.111 sevan 9221: </pre>
1.100 leot 9222: <p>Various <code class="varname">INSTALL_*</code> variables are also available:
9223: <code class="varname">INSTALL_GAME</code> to install setgid game binaries,
9224: <code class="varname">INSTALL_GAME_DIR</code> to install game directories that are
9225: needed to be accessed by setgid games and
9226: <code class="varname">INSTALL_GAME_DATA</code> to install scorefiles.</p>
1.14 jmcneill 9227: <p>A package should therefore never hard code file ownership or
1.100 leot 9228: access permissions but rely on <code class="varname">*_PERMS</code> as described above
9229: or alternatively on <code class="varname">INSTALL_GAME</code>,
9230: <code class="varname">INSTALL_GAME_DATA</code> and
9231: <code class="varname">INSTALL_GAME_DIR</code> to set these correctly.</p>
1.1 dsieger 9232: </div>
1.41 asau 9233: <div class="sect2">
1.1 dsieger 9234: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9235: <a name="destdir-support"></a>21.6.4. Adding DESTDIR support to packages</h3></div></div></div>
1.14 jmcneill 9236: <p><code class="varname">DESTDIR</code> support means that a package
9237: installs into a staging directory, not the final location of the
9238: files. Then a binary package is created which can be used for
9239: installation as usual. There are two ways: Either the package must
1.23 wiz 9240: install as root (<span class="quote">“<span class="quote">destdir</span>”</span>) or the package can
9241: install as non-root user (<span class="quote">“<span class="quote">user-destdir</span>”</span>).</p>
1.41 asau 9242: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9243: <li class="listitem"><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be
1.113 leot 9244: set to <span class="quote">“<span class="quote">destdir</span>”</span> or <span class="quote">“<span class="quote">user-destdir</span>”</span>.
9245: By default <code class="varname">PKG_DESTDIR_SUPPORT</code>
1.38 wiz 9246: is set to <span class="quote">“<span class="quote">user-destdir</span>”</span> to help catching more
9247: potential packaging problems. If bsd.prefs.mk is included in the Makefile,
1.14 jmcneill 9248: <code class="varname">PKG_DESTDIR_SUPPORT</code> needs to be set before
9249: the inclusion.</p></li>
1.23 wiz 9250: <li class="listitem"><p>All installation operations have to be prefixed with
1.4 rillig 9251: <code class="filename">${DESTDIR}</code>.</p></li>
1.23 wiz 9252: <li class="listitem"><p>automake gets this DESTDIR mostly right
1.4 rillig 9253: automatically. Many manual rules and pre/post-install often are
9254: incorrect; fix them.</p></li>
1.23 wiz 9255: <li class="listitem"><p>If files are installed with special owner/group
1.17 imil 9256: use <code class="varname">SPECIAL_PERMS</code>.</p></li>
1.23 wiz 9257: <li class="listitem"><p>In general, packages should support
1.4 rillig 9258: <code class="varname">UNPRIVILEGED</code> to be able to use
9259: DESTDIR.</p></li>
9260: </ul></div>
9261: </div>
1.41 asau 9262: <div class="sect2">
1.4 rillig 9263: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9264: <a name="hardcoded-paths"></a>21.6.5. Packages with hardcoded paths to other interpreters</h3></div></div></div>
1.1 dsieger 9265: <p>Your package may also contain scripts with hardcoded paths to
1.203 nia 9266: other interpreters besides (or as well as) Perl. To correct the
1.1 dsieger 9267: full pathname to the script interpreter, you need to set the
9268: following definitions in your <code class="filename">Makefile</code> (we
1.10 hubertf 9269: shall use <span class="command"><strong>tclsh</strong></span> in this example):</p>
1.1 dsieger 9270: <pre class="programlisting">
9271: REPLACE_INTERPRETER+= tcl
9272: REPLACE.tcl.old= .*/bin/tclsh
9273: REPLACE.tcl.new= ${PREFIX}/bin/tclsh
9274: REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed,
9275: # relative to ${WRKSRC}, just as in REPLACE_PERL
1.111 sevan 9276: </pre>
1.1 dsieger 9277: </div>
1.41 asau 9278: <div class="sect2">
1.1 dsieger 9279: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9280: <a name="perl-modules"></a>21.6.6. Packages installing Perl modules</h3></div></div></div>
1.1 dsieger 9281: <p>Makefiles of packages providing perl5 modules should include
9282: the Makefile fragment
9283: <code class="filename">../../lang/perl5/module.mk</code>. It provides a
1.10 hubertf 9284: <span class="command"><strong>do-configure</strong></span> target for the standard perl
1.1 dsieger 9285: configuration for such modules as well as various hooks to tune
9286: this configuration. See comments in this file for
9287: details.</p>
9288: <p>Perl5 modules will install into different places depending
9289: on the version of perl used during the build process. To
9290: address this, pkgsrc will append lines to the
9291: <code class="filename">PLIST</code> corresponding to the files listed in
9292: the installed <code class="filename">.packlist</code> file generated by
9293: most perl5 modules. This is invoked by defining
9294: <code class="varname">PERL5_PACKLIST</code> to a space-separated list of
1.47 wiz 9295: packlist files relative to <code class="varname">PERL5_PACKLIST_DIR</code>
9296: (<code class="varname">PERL5_INSTALLVENDORARCH</code> by default),
9297: e.g.:</p>
1.1 dsieger 9298: <pre class="programlisting">
1.47 wiz 9299: PERL5_PACKLIST= auto/Pg/.packlist
1.111 sevan 9300: </pre>
1.47 wiz 9301: <p>The perl5 config variables
9302: <code class="varname">installarchlib</code>,
9303: <code class="varname">installscript</code>,
9304: <code class="varname">installvendorbin</code>,
9305: <code class="varname">installvendorscript</code>,
9306: <code class="varname">installvendorarch</code>,
9307: <code class="varname">installvendorlib</code>,
9308: <code class="varname">installvendorman1dir</code>, and
9309: <code class="varname">installvendorman3dir</code> represent those
9310: locations in which components of perl5 modules may be installed,
9311: provided as variable with uppercase and prefixed with
9312: <code class="varname">PERL5_</code>, e.g. <code class="varname">PERL5_INSTALLARCHLIB</code>
9313: and may be used by perl5 packages that don't have a packlist.
9314: These variables are also substituted for in the
9315: <code class="filename">PLIST</code> as uppercase prefixed with
9316: <code class="varname">PERL5_SUB_</code>.</p>
1.1 dsieger 9317: </div>
1.41 asau 9318: <div class="sect2">
1.1 dsieger 9319: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9320: <a name="faq.info-files"></a>21.6.7. Packages installing info files</h3></div></div></div>
1.1 dsieger 9321: <p>Some packages install info files or use the
1.23 wiz 9322: <span class="quote">“<span class="quote">makeinfo</span>”</span> or <span class="quote">“<span class="quote">install-info</span>”</span>
1.1 dsieger 9323: commands. <code class="varname">INFO_FILES</code> should be defined in
9324: the package Makefile so that <code class="filename">INSTALL</code> and
9325: <code class="filename">DEINSTALL</code> scripts will be generated to
9326: handle registration of the info files in the Info directory
1.23 wiz 9327: file. The <span class="quote">“<span class="quote">install-info</span>”</span> command used for the info
1.1 dsieger 9328: files registration is either provided by the system, or by a
9329: special purpose package automatically added as dependency if
9330: needed.</p>
9331: <p><code class="varname">PKGINFODIR</code> is the directory under
9332: <code class="filename">${PREFIX}</code> where info files are primarily
9333: located. <code class="varname">PKGINFODIR</code> defaults to
1.23 wiz 9334: <span class="quote">“<span class="quote">info</span>”</span> and can be overridden by the user.</p>
1.1 dsieger 9335: <p>The info files for the package should be listed in the
9336: package <code class="filename">PLIST</code>; however any split info files
9337: need not be listed.</p>
1.23 wiz 9338: <p>A package which needs the <span class="quote">“<span class="quote">makeinfo</span>”</span> command
9339: at build time must add <span class="quote">“<span class="quote">makeinfo</span>”</span> to
1.1 dsieger 9340: <code class="varname">USE_TOOLS</code> in its Makefile. If a minimum
1.23 wiz 9341: version of the <span class="quote">“<span class="quote">makeinfo</span>”</span> command is needed it
1.1 dsieger 9342: should be noted with the <code class="varname">TEXINFO_REQD</code>
9343: variable in the package <code class="filename">Makefile</code>. By
9344: default, a minimum version of 3.12 is required. If the system
1.10 hubertf 9345: does not provide a <span class="command"><strong>makeinfo</strong></span> command or if it
1.1 dsieger 9346: does not match the required minimum, a build dependency on the
1.207 leot 9347: <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.1 dsieger 9348: be added automatically.</p>
9349: <p>The build and installation process of the software provided
9350: by the package should not use the
1.10 hubertf 9351: <span class="command"><strong>install-info</strong></span> command as the registration of
1.1 dsieger 9352: info files is the task of the package
9353: <code class="filename">INSTALL</code> script, and it must use the
1.10 hubertf 9354: appropriate <span class="command"><strong>makeinfo</strong></span> command.</p>
1.1 dsieger 9355: <p>To achieve this goal, the pkgsrc infrastructure creates
1.10 hubertf 9356: overriding scripts for the <span class="command"><strong>install-info</strong></span> and
9357: <span class="command"><strong>makeinfo</strong></span> commands in a directory listed early
1.1 dsieger 9358: in <code class="varname">PATH</code>.</p>
1.10 hubertf 9359: <p>The script overriding <span class="command"><strong>install-info</strong></span> has
1.1 dsieger 9360: no effect except the logging of a message. The script overriding
1.10 hubertf 9361: <span class="command"><strong>makeinfo</strong></span> logs a message and according to the
1.1 dsieger 9362: value of <code class="varname">TEXINFO_REQD</code> either runs the appropriate
1.10 hubertf 9363: <span class="command"><strong>makeinfo</strong></span> command or exit on error.</p>
1.1 dsieger 9364: </div>
1.41 asau 9365: <div class="sect2">
1.1 dsieger 9366: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9367: <a name="manpages"></a>21.6.8. Packages installing man pages</h3></div></div></div>
1.1 dsieger 9368: <p>All packages that install manual pages should install them
9369: into the same directory, so that there is one common place to look
9370: for them. In pkgsrc, this place is
9371: <code class="literal">${PREFIX}/${PKGMANDIR}</code>, and this expression
9372: should be used in packages. The default for
9373: <code class="varname">PKGMANDIR</code> is
1.23 wiz 9374: <span class="quote">“<span class="quote"><code class="filename">man</code></span>”</span>. Another often-used value
9375: is <span class="quote">“<span class="quote"><code class="filename">share/man</code></span>”</span>.</p>
1.41 asau 9376: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9377: <h3 class="title">Note</h3>
9378: <p>The support for a custom <code class="varname">PKGMANDIR</code>
9379: is far from complete.</p>
9380: </div>
9381: <p>The <code class="filename">PLIST</code> files can just use
9382: <code class="filename">man/</code> as the top level directory for the man
9383: page file entries, and the pkgsrc framework will convert as
9384: needed. In all other places, the correct
9385: <code class="varname">PKGMANDIR</code> must be used.</p>
9386: <p>Packages that are
9387: configured with <code class="varname">GNU_CONFIGURE</code> set as
1.23 wiz 9388: <span class="quote">“<span class="quote">yes</span>”</span>, by default will use the
1.1 dsieger 9389: <code class="filename">./configure</code>
9390: --mandir switch to set where the man pages should be installed.
9391: The path is <code class="varname">GNU_CONFIGURE_MANDIR</code> which defaults
9392: to <code class="varname">${PREFIX}/${PKGMANDIR}</code>.</p>
9393: <p>Packages that use <code class="varname">GNU_CONFIGURE</code> but do not
9394: use --mandir, can set <code class="varname">CONFIGURE_HAS_MANDIR</code>
1.23 wiz 9395: to <span class="quote">“<span class="quote">no</span>”</span>.
1.1 dsieger 9396: Or if the <code class="filename">./configure</code> script uses
9397: a non-standard use of --mandir, you can set
9398: <code class="varname">GNU_CONFIGURE_MANDIR</code> as needed.</p>
1.184 rillig 9399: <p>See <a class="xref" href="#manpage-compression" title="19.5. Man page compression">Section 19.5, “Man page compression”</a> for
1.1 dsieger 9400: information on installation of compressed manual pages.</p>
9401: </div>
1.41 asau 9402: <div class="sect2">
1.1 dsieger 9403: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9404: <a name="x11-fonts"></a>21.6.9. Packages installing X11 fonts</h3></div></div></div>
1.1 dsieger 9405: <p>If a package installs font files, you will need to rebuild
9406: the fonts database in the directory where they get installed at
9407: installation and deinstallation time. This can be automatically
9408: done by using the pkginstall framework.</p>
9409: <p>You can list the directories where fonts are installed in the
9410: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code>
9411: variables, where <em class="replaceable"><code>type</code></em> can be one of
1.23 wiz 9412: <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.1 dsieger 9413: Also make sure that the database file
9414: <code class="filename">fonts.dir</code> is not listed in the PLIST.</p>
9415: <p>Note that you should not create new directories for fonts;
9416: instead use the standard ones to avoid that the user needs to
9417: manually configure his X server to find them.</p>
9418: </div>
1.41 asau 9419: <div class="sect2">
1.1 dsieger 9420: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9421: <a name="sgml-xml-data"></a>21.6.10. Packages installing SGML or XML data</h3></div></div></div>
1.1 dsieger 9422: <p>If a package installs SGML or XML data files that need to be
9423: registered in system-wide catalogs (like DTDs, sub-catalogs,
9424: etc.), you need to take some extra steps:</p>
1.23 wiz 9425: <div class="orderedlist"><ol class="orderedlist" type="1">
9426: <li class="listitem"><p>Include
1.1 dsieger 9427: <code class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in
9428: your <code class="filename">Makefile</code>, which takes care of
9429: registering those files in system-wide catalogs at
9430: installation and deinstallation time.</p></li>
1.23 wiz 9431: <li class="listitem"><p>Set <code class="varname">SGML_CATALOGS</code> to the full path of
1.1 dsieger 9432: any SGML catalogs installed by the package.</p></li>
1.23 wiz 9433: <li class="listitem"><p>Set <code class="varname">XML_CATALOGS</code> to the full path of
1.1 dsieger 9434: any XML catalogs installed by the package.</p></li>
1.23 wiz 9435: <li class="listitem"><p>Set <code class="varname">SGML_ENTRIES</code> to individual entries
1.1 dsieger 9436: to be added to the SGML catalog. These come in groups of
9437: three strings; see xmlcatmgr(1) for more information
9438: (specifically, arguments recognized by the 'add' action).
9439: Note that you will normally not use this variable.</p></li>
1.23 wiz 9440: <li class="listitem"><p>Set <code class="varname">XML_ENTRIES</code> to individual entries
1.1 dsieger 9441: to be added to the XML catalog. These come in groups of three
9442: strings; see xmlcatmgr(1) for more information (specifically,
9443: arguments recognized by the 'add' action). Note that you will
9444: normally not use this variable.</p></li>
9445: </ol></div>
9446: </div>
1.41 asau 9447: <div class="sect2">
1.1 dsieger 9448: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9449: <a name="mime-database"></a>21.6.11. Packages installing extensions to the MIME database</h3></div></div></div>
1.1 dsieger 9450: <p>If a package provides extensions to the MIME database by
9451: installing <code class="filename">.xml</code> files inside
9452: <code class="filename">${PREFIX}/share/mime/packages</code>, you
9453: need to take some extra steps to ensure that the database is kept
9454: consistent with respect to these new files:</p>
1.23 wiz 9455: <div class="orderedlist"><ol class="orderedlist" type="1">
9456: <li class="listitem"><p>Include
1.1 dsieger 9457: <code class="filename">../../databases/shared-mime-info/mimedb.mk</code>
9458: (avoid using the <code class="filename">buildlink3.mk</code> file from
9459: this same directory, which is reserved for inclusion from
9460: other <code class="filename">buildlink3.mk</code> files). It takes
9461: care of rebuilding the MIME database at installation and
9462: deinstallation time, and disallows any access to it directly
9463: from the package.</p></li>
1.23 wiz 9464: <li class="listitem"><p>Check the PLIST and remove any entries under the
1.1 dsieger 9465: <code class="filename">share/mime</code> directory,
9466: <span class="emphasis"><em>except</em></span> for files saved under
9467: <code class="filename">share/mime/packages</code>. The former are
9468: handled automatically by
9469: the update-mime-database program, but the latter are
9470: package-dependent and must be removed by the package that
9471: installed them in the first place.</p></li>
1.23 wiz 9472: <li class="listitem"><p>Remove any <code class="filename">share/mime/*</code> directories
1.1 dsieger 9473: from the PLIST. They will be handled by the shared-mime-info
9474: package.</p></li>
9475: </ol></div>
9476: </div>
1.41 asau 9477: <div class="sect2">
1.1 dsieger 9478: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9479: <a name="intltool"></a>21.6.12. Packages using intltool</h3></div></div></div>
1.1 dsieger 9480: <p>If a package uses intltool during its build, add
9481: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>,
9482: which forces it to use the intltool package provided by pkgsrc,
9483: instead of the one bundled with the distribution file.</p>
9484: <p>This tracks intltool's build-time dependencies and uses the
9485: latest available version; this way, the package benefits of any
9486: bug fixes that may have appeared since it was released.</p>
9487: </div>
1.41 asau 9488: <div class="sect2">
1.1 dsieger 9489: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9490: <a name="startup-scripts"></a>21.6.13. Packages installing startup scripts</h3></div></div></div>
1.1 dsieger 9491: <p>If a package contains a rc.d script, it won't be copied into
9492: the startup directory by default, but you can enable it, by adding
9493: the option <code class="varname">PKG_RCD_SCRIPTS=YES</code> in
1.10 hubertf 9494: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. This option will copy the scripts
1.1 dsieger 9495: into <code class="filename">/etc/rc.d</code> when a package is installed, and
9496: it will automatically remove the scripts when the package is
9497: deinstalled.</p>
9498: </div>
1.41 asau 9499: <div class="sect2">
1.1 dsieger 9500: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9501: <a name="tex-packages"></a>21.6.14. Packages installing TeX modules</h3></div></div></div>
1.1 dsieger 9502: <p>If a package installs TeX packages into the texmf tree,
9503: the <code class="filename">ls-R</code> database of the tree needs to be
9504: updated.</p>
1.41 asau 9505: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9506: <h3 class="title">Note</h3>
1.22 jakllsch 9507: <p>Except the main TeX packages such as kpathsea,
1.1 dsieger 9508: packages should install files
1.22 jakllsch 9509: into <code class="filename">${PREFIX}/share/texmf-dist</code>,
9510: not <code class="filename">${PREFIX}/share/texmf</code>.</p>
1.1 dsieger 9511: </div>
1.23 wiz 9512: <div class="orderedlist"><ol class="orderedlist" type="1">
9513: <li class="listitem"><p>Include
1.22 jakllsch 9514: <code class="filename">../../print/kpathsea/texmf.mk</code>. This
1.1 dsieger 9515: takes care of rebuilding the <code class="filename">ls-R</code>
9516: database at installation and deinstallation time.</p></li>
1.23 wiz 9517: <li class="listitem">
1.1 dsieger 9518: <p>If your package installs files into a texmf
9519: tree other than the one
1.22 jakllsch 9520: at <code class="filename">${PREFIX}/share/texmf-dist</code>,
9521: set <code class="varname">TEX_TEXMF_DIRS</code> to the list of all texmf
1.1 dsieger 9522: trees that need database update.</p>
9523: <p>If your package also installs font map files that need
1.10 hubertf 9524: to be registered using <span class="command"><strong>updmap</strong></span>,
1.29 dholland 9525: include <code class="filename">../../print/tex-tetex/map.mk</code> and
1.22 jakllsch 9526: set <code class="varname">TEX_MAP_FILES</code> and/or
9527: <code class="varname">TEX_MIXEDMAP_FILES</code> to the list of all
1.10 hubertf 9528: such font map files. Then <span class="command"><strong>updmap</strong></span> will
1.1 dsieger 9529: be run automatically at installation/deinstallation to
9530: enable/disable font map files for TeX output
9531: drivers.</p>
9532: </li>
1.23 wiz 9533: <li class="listitem"><p>Make sure that none of <code class="filename">ls-R</code>
1.1 dsieger 9534: databases are included in <code class="filename">PLIST</code>, as
1.29 dholland 9535: they will be removed only by the kpathsea package.</p></li>
1.1 dsieger 9536: </ol></div>
9537: </div>
1.41 asau 9538: <div class="sect2">
1.1 dsieger 9539: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9540: <a name="emulation-packages"></a>21.6.15. Packages supporting running binaries in
1.1 dsieger 9541: emulation</h3></div></div></div>
9542: <p>There are some packages that provide libraries and
9543: executables for running binaries from a one operating system
9544: on a different one (if the latter supports it). One example
9545: is running Linux binaries on NetBSD.</p>
1.207 leot 9546: <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.1 dsieger 9547: helps in extracting and packaging Linux rpm packages.</p>
9548: <p>The <code class="varname">CHECK_SHLIBS</code> can be set to no to
1.10 hubertf 9549: avoid the <span class="command"><strong>check-shlibs</strong></span> target, which tests
1.1 dsieger 9550: if all libraries for each installed executable can be found by
9551: the dynamic linker. Since the standard dynamic linker is run,
9552: this fails for emulation packages, because the libraries used
9553: by the emulation are not in the standard directories.</p>
9554: </div>
1.184 rillig 9555: <div class="sect2">
9556: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9557: <a name="hicolor-theme"></a>21.6.16. Packages installing hicolor icons</h3></div></div></div>
1.184 rillig 9558: <p>If a package installs images under the
9559: <code class="filename">share/icons/hicolor</code> and/or updates the
9560: <code class="filename">share/icons/hicolor/icon-theme.cache</code>
9561: database, you need to take some extra steps to make sure that the
9562: shared theme directory is handled appropriately and that the cache
9563: database is rebuilt:</p>
9564: <div class="orderedlist"><ol class="orderedlist" type="1">
9565: <li class="listitem"><p>Include
9566: <code class="filename">../../graphics/hicolor-icon-theme/buildlink3.mk</code>.</p></li>
9567: <li class="listitem"><p>Check the <code class="filename">PLIST</code> and remove the
9568: entry that refers to the theme cache.</p></li>
9569: <li class="listitem"><p>Ensure that the PLIST does not remove the shared icon
9570: directories from the <code class="filename">share/icons/hicolor</code>
9571: hierarchy because they will be handled automatically.</p></li>
9572: </ol></div>
9573: <p>The best way to verify that the PLIST is correct with
9574: respect to the last two points is to regenerate it using
9575: <span class="command"><strong>make print-PLIST</strong></span>.</p>
9576: </div>
9577: <div class="sect2">
9578: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9579: <a name="desktop-files"></a>21.6.17. Packages installing desktop files</h3></div></div></div>
1.184 rillig 9580: <p>If a package installs <code class="filename">.desktop</code> files
9581: under <code class="filename">share/applications</code> and these include
9582: MIME information (MimeType key), you need to take extra steps to
9583: ensure that they are registered into the MIME database:</p>
9584: <div class="orderedlist"><ol class="orderedlist" type="1">
9585: <li class="listitem"><p>Include
9586: <code class="filename">../../sysutils/desktop-file-utils/desktopdb.mk</code>.</p></li>
9587: <li class="listitem"><p>Check the PLIST and remove the entry that refers to the
9588: <code class="filename">share/applications/mimeinfo.cache</code> file.
9589: It will be handled automatically.</p></li>
9590: </ol></div>
9591: <p>The best way to verify that the PLIST is correct with
9592: respect to the last point is to regenerate it using <span class="command"><strong>make
9593: print-PLIST</strong></span>.</p>
9594: </div>
9595: </div>
9596: <div class="sect1">
9597: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9598: <a name="punting"></a>21.7. Marking packages as having problems</h2></div></div></div>
9599: <p>In some cases one does not have the time to solve a problem
9600: immediately. In this case, one can plainly mark a package as broken. For
9601: this, one just sets the variable <code class="varname">BROKEN</code> to the
9602: reason why the package is broken (similar to the
9603: <code class="varname">PKG_FAIL_REASON</code> variable). A user trying to build
9604: the package will immediately be shown this message, and the build
9605: will not be even tried.</p>
9606: <p><code class="varname">BROKEN</code> packages are removed from pkgsrc in irregular
9607: intervals.</p>
9608: </div>
9609: </div>
9610: <div class="chapter">
9611: <div class="titlepage"><div><div><h2 class="title">
9612: <a name="gnome"></a>Chapter 22. GNOME packaging and porting</h2></div></div></div>
9613: <div class="toc">
9614: <p><b>Table of Contents</b></p>
9615: <dl class="toc">
9616: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
9617: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
9618: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
9619: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
9620: </dl>
9621: </div>
9622: <p>Quoting <a class="ulink" href="https://www.gnome.org/" target="_top">GNOME's web
9623: site</a>:</p>
9624: <div class="blockquote"><blockquote class="blockquote"><p>The GNOME project provides two things: The GNOME desktop
9625: environment, an intuitive and attractive desktop for users, and the
9626: GNOME development platform, an extensive framework for building
9627: applications that integrate into the rest of the desktop.</p></blockquote></div>
9628: <p>pkgsrc provides a seamless way to automatically build and install
9629: a complete GNOME environment <span class="emphasis"><em>under many different
9630: platforms</em></span>. We can say with confidence that pkgsrc is one of
9631: the most advanced build and packaging systems for GNOME due to its
9632: included technologies buildlink3, the wrappers and tools framework and
9633: automatic configuration file management. Lots of efforts are put into
9634: achieving a completely clean deinstallation of installed software
9635: components.</p>
9636: <p>Given that pkgsrc is <a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a>'s official packaging system,
9637: the above also means that great efforts are put into making GNOME work
1.201 cirnatda 9638: under this operating system.</p>
1.184 rillig 9639: <p>This chapter is aimed at pkgsrc developers and other people
9640: interested in helping our GNOME porting and packaging efforts. It
9641: provides instructions on how to manage the existing packages and some
9642: important information regarding their internals.</p>
9643: <div class="sect1">
9644: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9645: <a name="meta-packages"></a>22.1. Meta packages</h2></div></div></div>
9646: <p>pkgsrc includes three GNOME-related meta packages:</p>
9647: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 9648: <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.184 rillig 9649: the core GNOME desktop environment. It only includes the necessary
9650: bits to get it to boot correctly, although it may lack important
9651: functionality for daily operation. The idea behind this package is
9652: to let end users build their own configurations on top of this one,
9653: first installing this meta package to achieve a functional setup and
9654: then adding individual applications.</p></li>
1.207 leot 9655: <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.184 rillig 9656: complete installation of the GNOME platform and desktop as defined
9657: by the GNOME project; this is based on the components distributed in
9658: the <code class="filename">platform/x.y/x.y.z/sources</code> and
9659: <code class="filename">desktop/x.y/x.y.z/sources</code> directories of the
9660: official FTP server. Developer-only tools found in those
9661: directories are not installed unless required by some other
9662: component to work properly. Similarly, packages from the bindings
9663: set (<code class="filename">bindings/x.y/x.y.z/sources</code>) are not pulled
9664: in unless required as a dependency for an end-user component. This
1.207 leot 9665: 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>
9666: <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.184 rillig 9667: Installs all the tools required to build a GNOME component when
9668: fetched from the CVS repository. These are required to let the
9669: <span class="command"><strong>autogen.sh</strong></span> scripts work appropriately.</p></li>
9670: </ul></div>
9671: <p>In all these packages, the <code class="varname">DEPENDS</code> lines are
9672: sorted in a way that eases updates: a package may depend on other
9673: packages listed before it but not on any listed after it. It is very
9674: important to keep this order to ease updates so... <span class="emphasis"><em>do not
9675: change it to alphabetical sorting!</em></span></p>
9676: </div>
9677: <div class="sect1">
9678: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9679: <a name="new-package"></a>22.2. Packaging a GNOME application</h2></div></div></div>
9680: <p>Almost all GNOME applications are written in C and use a common
9681: set of tools as their build system. Things get different with the new
9682: bindings to other languages (such as Python), but the following will
9683: give you a general idea on the minimum required tools:</p>
9684: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9685: <li class="listitem">
9686: <p>Almost all GNOME applications use the GNU Autotools as their
9687: build system. As a general rule you will need to tell this to your
9688: package:</p>
9689: <pre class="programlisting">
1.223 nia 9690: GNU_CONFIGURE= yes
9691: USE_LIBTOOL= yes
9692: USE_TOOLS+= gmake
1.184 rillig 9693: </pre>
9694: </li>
9695: <li class="listitem">
9696: <p>If the package uses pkg-config to detect dependencies, add this
9697: tool to the list of required utilities:</p>
9698: <pre class="programlisting">
1.223 nia 9699: USE_TOOLS+= pkg-config
1.184 rillig 9700: </pre>
1.207 leot 9701: <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.184 rillig 9702: the end of the build process to ensure that you did not miss to
9703: specify any dependency in your package and that the version
9704: requirements are all correct.</p>
9705: </li>
9706: <li class="listitem"><p>If the package uses intltool, be sure to add
9707: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>
9708: to handle dependencies and to force the package to use the latest
9709: available version.</p></li>
9710: <li class="listitem">
9711: <p>If the package uses gtk-doc (a documentation generation
9712: utility), do <span class="emphasis"><em>not</em></span> add a dependency on it. The
9713: tool is rather big and the distfile should come with pregenerated
9714: documentation anyway; if it does not, it is a bug that you ought to
9715: report. For such packages you should disable gtk-doc (unless it is
9716: the default):</p>
9717: <pre class="programlisting">
1.223 nia 9718: CONFIGURE_ARGS+= --disable-gtk-doc
1.184 rillig 9719: </pre>
9720: <p>The default location of installed HTML files
9721: (<code class="filename">share/gtk-doc/<package-name></code>) is correct
9722: and should not be changed unless the package insists on installing
9723: them somewhere else. Otherwise programs as
9724: <span class="command"><strong>devhelp</strong></span> will not be able to open them. You can
9725: do that with an entry similar to:</p>
9726: <pre class="programlisting">
1.223 nia 9727: CONFIGURE_ARGS+= --with-html-dir=${PREFIX}/share/gtk-doc/...
1.184 rillig 9728: </pre>
9729: </li>
9730: </ul></div>
9731: <p>GNOME uses multiple <span class="emphasis"><em>shared</em></span> directories and
9732: files under the installation prefix to maintain databases. In this
9733: context, shared means that those exact same directories and files are
9734: used among several different packages, leading to conflicts in the
9735: <code class="filename">PLIST</code>. pkgsrc currently includes functionality to
9736: handle the most common cases, so you have to forget about using
9737: <code class="literal">@unexec ${RMDIR}</code> lines in your file lists and
9738: omitting shared files from them. If you find yourself doing those,
9739: <span class="emphasis"><em>your package is most likely incorrect</em></span>.</p>
9740: <p>The following table lists the common situations that result in
9741: using shared directories or files. For each of them, the appropriate
9742: solution is given. After applying the solution be sure to
9743: <span class="emphasis"><em>regenerate the package's file list</em></span> with
9744: <span class="command"><strong>make print-PLIST</strong></span> and ensure it is correct.</p>
9745: <div class="table">
9746: <a name="plist-handling"></a><p class="title"><b>Table 22.1. PLIST handling for GNOME packages</b></p>
9747: <div class="table-contents"><table class="table" summary="PLIST handling for GNOME packages" border="1">
9748: <colgroup>
9749: <col>
9750: <col>
9751: </colgroup>
9752: <thead><tr>
9753: <th>If the package...</th>
9754: <th>Then...</th>
9755: </tr></thead>
9756: <tbody>
9757: <tr>
9758: <td>Installs icons under the
9759: <code class="filename">share/icons/hicolor</code> hierarchy or updates
9760: <code class="filename">share/icons/hicolor/icon-theme.cache</code>.</td>
1.203 nia 9761: <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.184 rillig 9762: </tr>
9763: <tr>
9764: <td>Installs files under
9765: <code class="filename">share/mime/packages</code>.</td>
1.203 nia 9766: <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.184 rillig 9767: </tr>
9768: <tr>
9769: <td>Installs <code class="filename">.desktop</code> files under
9770: <code class="filename">share/applications</code> and these include MIME
9771: information.</td>
1.203 nia 9772: <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.184 rillig 9773: </tr>
9774: </tbody>
9775: </table></div>
1.1 dsieger 9776: </div>
1.184 rillig 9777: <br class="table-break">
1.1 dsieger 9778: </div>
1.41 asau 9779: <div class="sect1">
1.1 dsieger 9780: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 9781: <a name="full-update"></a>22.3. Updating GNOME to a newer version</h2></div></div></div>
9782: <p>When seeing GNOME as a whole, there are two kinds of
9783: updates:</p>
9784: <div class="variablelist"><dl class="variablelist">
9785: <dt><span class="term">Major update</span></dt>
9786: <dd>
9787: <p>Given that there is still a very long way for GNOME 3 (if it
9788: ever appears), we consider a major update one that goes from a
9789: <code class="literal">2.X</code> version to a <code class="literal">2.Y</code> one,
9790: where <code class="literal">Y</code> is even and greater than
9791: <code class="literal">X</code>. These are hard to achieve because they
9792: introduce lots of changes in the components' code and almost all
9793: GNOME distfiles are updated to newer versions. Some of them can
9794: even break API and ABI compatibility with the previous major
9795: version series. As a result, the update needs to be done all at
9796: once to minimize breakage.</p>
9797: <p>A major update typically consists of around 80 package
9798: updates and the addition of some new ones.</p>
9799: </dd>
9800: <dt><span class="term">Minor update</span></dt>
9801: <dd>
9802: <p>We consider a minor update one that goes from a
9803: <code class="literal">2.A.X</code> version to a <code class="literal">2.A.Y</code>
9804: one where <code class="literal">Y</code> is greater than
9805: <code class="literal">X</code>. These are easy to achieve because they do
9806: not update all GNOME components, can be done in an incremental way
9807: and do not break API nor ABI compatibility.</p>
9808: <p>A minor update typically consists of around 50 package
9809: updates, although the numbers here may vary a lot.</p>
9810: </dd>
9811: </dl></div>
9812: <p>In order to update the GNOME components in pkgsrc to a new stable
9813: release (either major or minor), the following steps should be
9814: followed:</p>
9815: <div class="orderedlist"><ol class="orderedlist" type="1">
1.23 wiz 9816: <li class="listitem">
1.184 rillig 9817: <p>Get a list of all the tarballs that form the new release by
9818: using the following commands. These will leave the full list of the
9819: components' distfiles into the <code class="filename">list.txt</code>
9820: file:</p>
9821: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9822: ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
9823: awk '{ print $9 }' >list.txt</code></strong>
9824: <code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9825: ftp -V ftp://ftp.gnome.org/pub/gnome/desktop/x.y/x.y.z/sources/ | \
9826: awk '{ print $9 }' >>list.txt</code></strong></pre>
1.1 dsieger 9827: </li>
1.184 rillig 9828: <li class="listitem"><p>Open each meta package's <code class="filename">Makefile</code> and
9829: bump their version to the release you are updating them to. The
9830: three meta packages should be always consistent with versioning.
9831: Obviously remove any <code class="varname">PKGREVISION</code>s that might be
9832: in them.</p></li>
1.23 wiz 9833: <li class="listitem">
1.184 rillig 9834: <p>For each meta package, update all its
9835: <code class="varname">DEPENDS</code> lines to match the latest versions as
9836: shown by the above commands. Do <span class="emphasis"><em>not</em></span> list any
9837: newer version (even if found in the FTP) because the meta packages
9838: are supposed to list the exact versions that form a specific GNOME
9839: release. Exceptions are permitted here if a newer version solves a
9840: serious issue in the overall desktop experience; these typically
9841: come in the form of a revision bump in pkgsrc, not in newer versions
9842: from the developers.</p>
9843: <p>Packages not listed in the <code class="filename">list.txt</code> file
9844: should be updated to the latest version available (if found in
9845: pkgsrc). This is the case, for example, of the dependencies on the
1.207 leot 9846: 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.1 dsieger 9847: </li>
1.23 wiz 9848: <li class="listitem">
1.184 rillig 9849: <p>Generate a patch from the modified meta packages and extract the
9850: list of "new" lines. This will provide you an outline on what
9851: packages need to be updated in pkgsrc and in what order:</p>
9852: <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.1 dsieger 9853: </li>
1.184 rillig 9854: <li class="listitem"><p>For major desktop updates it is recommended to zap all your
9855: installed packages and start over from scratch at this point.</p></li>
9856: <li class="listitem"><p>Now comes the longest step by far: iterate over the contents
9857: of <code class="filename">todo.txt</code> and update the packages listed in
9858: it in order. For major desktop updates none of these should be
9859: committed until the entire set is completed because there are chances
9860: of breaking not-yet-updated packages.</p></li>
9861: <li class="listitem"><p>Once the packages are up to date and working, commit them to
9862: the tree one by one with appropriate log messages. At the end,
9863: commit the three meta package updates and all the corresponding
9864: changes to the <code class="filename">doc/CHANGES-<YEAR></code> and
9865: <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>
9866: </ol></div>
9867: </div>
9868: <div class="sect1">
9869: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9870: <a name="patching"></a>22.4. Patching guidelines</h2></div></div></div>
9871: <p>GNOME is a very big component in pkgsrc which approaches 100
9872: packages. Please, it is very important that you always, always,
9873: <span class="strong"><strong>always</strong></span> feed back any portability
9874: 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
9875: their attention on portability issues and to ensure that future versions
9876: can be built out-of-the box on NetBSD. The less custom patches in
9877: pkgsrc, the easier further updates are. Those developers in charge of
9878: issuing major GNOME updates will be grateful if you do that.</p>
1.200 cirnatda 9879: <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
9880: GitLab</a>. Not all components use these to track bugs, but most
1.184 rillig 9881: of them do. Do not be short on your reports: always provide detailed
9882: explanations of the current failure, how it can be improved to achieve
1.200 cirnatda 9883: maximum portability and, if at all possible, provide a patch against the
9884: main Git branch. The more verbose you are, the higher chances of your
9885: patch being accepted.</p>
1.184 rillig 9886: <p>Also, please avoid using preprocessor magic to fix portability
9887: issues. While the FreeBSD GNOME people are doing a great job in porting
9888: GNOME to their operating system, the official GNOME sources are now
9889: plagued by conditionals that check for <code class="varname">__FreeBSD__</code>
9890: and similar macros. This hurts portability. Please see our patching
9891: guidelines (<a class="xref" href="#components.patches.guidelines" title="12.3.4. Patching guidelines">Section 12.3.4, “Patching guidelines”</a>) for more
9892: details.</p>
9893: </div>
1.1 dsieger 9894: </div>
1.41 asau 9895: <div class="chapter">
1.1 dsieger 9896: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 9897: <a name="submit"></a>Chapter 23. Submitting and Committing</h2></div></div></div>
1.1 dsieger 9898: <div class="toc">
9899: <p><b>Table of Contents</b></p>
1.100 leot 9900: <dl class="toc">
1.154 rillig 9901: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
9902: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
9903: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
9904: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
9905: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
9906: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
9907: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
9908: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
1.1 dsieger 9909: </dl>
9910: </div>
1.41 asau 9911: <div class="sect1">
1.1 dsieger 9912: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9913: <a name="submitting-binary-packages"></a>23.1. Submitting binary packages</h2></div></div></div>
1.1 dsieger 9914: <p>Our policy is that we accept binaries only from pkgsrc
9915: developers to guarantee that the packages don't contain any
9916: trojan horses etc. This is not to annoy anyone but rather to
9917: protect our users! You're still free to put up your home-made
9918: binary packages and tell the world where to get them. NetBSD
9919: developers doing bulk builds and wanting to upload them please
1.154 rillig 9920: 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.66 asau 9921: builds)</i></a>.</p>
1.1 dsieger 9922: </div>
1.41 asau 9923: <div class="sect1">
1.1 dsieger 9924: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9925: <a name="submitting-your-package"></a>23.2. Submitting source packages (for non-NetBSD-developers)</h2></div></div></div>
1.218 nia 9926: <p>Firstly, you can import new packages into
9927: pkgsrc-wip (<span class="quote">“<span class="quote">pkgsrc work-in-progress</span>”</span>); see the
9928: homepage at <a class="ulink" href="https://pkgsrc.org/wip/" target="_top">https://pkgsrc.org/wip/</a>
9929: for details.</p>
9930: <p>Next, check that your package is complete, compiles and
1.184 rillig 9931: 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.218 nia 9932: 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>
9933: tool and fix any errors that appear.</p>
9934: <p>Finally, send a report to the pkgsrc bug tracking system,
1.246 leot 9935: either with the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> command, or if you don't have
1.1 dsieger 9936: that, go to the web page
1.174 leot 9937: <a class="ulink" href="https://www.NetBSD.org/support/send-pr.html" target="_top">https://www.NetBSD.org/support/send-pr.html</a>,
1.21 snj 9938: which contains some instructions and a link to a form where you
9939: can submit packages. The
1.207 leot 9940: <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.21 snj 9941: also available as a substitute for either of the above two tools.
9942: </p>
1.1 dsieger 9943: <p>In the form of the problem report, the category should be
1.23 wiz 9944: <span class="quote">“<span class="quote">pkg</span>”</span>, the synopsis should include the package name
1.1 dsieger 9945: and version number, and the description field should contain a
9946: short description of your package (contents of the COMMENT
1.218 nia 9947: variable or DESCR file are OK).</p>
1.1 dsieger 9948: </div>
1.41 asau 9949: <div class="sect1">
1.1 dsieger 9950: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9951: <a name="general-notes-for-changes"></a>23.3. General notes when adding, updating, or removing packages</h2></div></div></div>
1.1 dsieger 9952: <p>Please note all package additions, updates, moves, and
9953: removals in <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code>. It's very
9954: important to keep this file up to date and conforming to the
9955: existing format, because it will be used by scripts to
1.174 leot 9956: automatically update pages on <a class="ulink" href="https://www.NetBSD.org/" target="_top">www.NetBSD.org</a> and other
1.1 dsieger 9957: sites. Additionally, check the
9958: <code class="filename">pkgsrc/doc/TODO</code> file and remove the entry
9959: for the package you updated or removed, in case it was mentioned
9960: there.</p>
9961: <p>When the <code class="varname">PKGREVISION</code> of a package is
9962: bumped, the change should appear in
9963: <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code> if it is security
9964: related or otherwise relevant. Mass bumps that result from a
9965: dependency being updated should not be mentioned. In all other
9966: cases it's the developer's decision.</p>
9967: <p>There is a make target that helps in creating proper
1.10 hubertf 9968: <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code> entries: <span class="command"><strong>make
1.1 dsieger 9969: changes-entry</strong></span>. It uses the optional <code class="varname">CTYPE</code>
9970: and <code class="varname">NETBSD_LOGIN_NAME</code> variables. The general
9971: usage is to first make sure that your <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code>
9972: file is up-to-date (to avoid having to resolve conflicts later-on)
1.10 hubertf 9973: and then to <span class="command"><strong>cd</strong></span> to the package directory. For
9974: package updates, <span class="command"><strong>make changes-entry</strong></span> is enough.
1.1 dsieger 9975: For new packages, or package moves or removals, set the
9976: <code class="varname">CTYPE</code> variable on the command line to "Added",
9977: "Moved", or "Removed". You can set <code class="varname">NETBSD_LOGIN_NAME</code>
1.10 hubertf 9978: in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> if your local login name is
1.22 jakllsch 9979: not the same as your NetBSD login name. The target also automatically
9980: removes possibly existing entries for the package in the
9981: <code class="filename">TODO</code> file. Don't forget to commit
1.66 asau 9982: the changes, e.g. by using <span class="command"><strong>make commit-changes-entry</strong></span>!
1.22 jakllsch 9983: If you are not using a checkout directly from cvs.NetBSD.org, but e.g.
9984: a local copy of the repository, you can set USE_NETBSD_REPO=yes. This
9985: makes the cvs commands use the main repository.
9986: </p>
1.1 dsieger 9987: </div>
1.41 asau 9988: <div class="sect1">
1.1 dsieger 9989: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9990: <a name="commit-messages"></a>23.4. Commit Messages</h2></div></div></div>
1.130 wiz 9991: <p>For several years, there have been mirrors of pkgsrc in
9992: fossil, git, and hg. Standard practise when using these tools is to
9993: make the first line of a commit message function as a summary that
9994: can be read without the rest, such as is commonly done with "git log
9995: --oneline". For this reason, we have the following guidelines for
9996: pkgsrc commit messages:</p>
9997: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9998: <li class="listitem"><p>Start the commit message with a line that explains the
1.131 wiz 9999: big picture in 65 characters or less. When a commit is for one
1.130 wiz 10000: package, include the name of the package. For updates, include the
10001: version to which it is updated.</p></li>
10002: <li class="listitem"><p>Leave the next line empty.</p></li>
10003: <li class="listitem"><p>Then come the details for the commit (changes in that
10004: package, reason for a change) and any relevant PRs. Wrap this
10005: section.</p></li>
10006: </ul></div>
10007: <p>Here is an example:
1.238 wiz 10008: </p>
1.130 wiz 10009: <pre class="programlisting">
1.238 wiz 10010: libxslt: update to 1.0.30
1.130 wiz 10011:
1.238 wiz 10012: Changes since 1.0.29:
10013: ...
10014: </pre>
1.130 wiz 10015: <p>
10016: </p>
10017: <p>Here is another example:
1.238 wiz 10018: </p>
1.130 wiz 10019: <pre class="programlisting">
1.238 wiz 10020: mk/bsd.pkg.mk: enable SSP by default on NetBSD
1.130 wiz 10021:
1.238 wiz 10022: (rationale)
10023: </pre>
1.130 wiz 10024: <p>
10025: </p>
10026: <p>Commit messages are final: no <span class="quote">“<span class="quote">cvs admin</span>”</span> is
10027: allowed on the pkgsrc repository to change commit messages.</p>
10028: </div>
10029: <div class="sect1">
10030: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10031: <a name="committing-importing"></a>23.5. Committing: Adding a package to CVS</h2></div></div></div>
1.1 dsieger 10032: <p>This section is only of interest for pkgsrc developers with write
1.33 wiz 10033: access to the pkgsrc repository.</p>
10034: <p>When the package is finished, <span class="quote">“<span class="quote">cvs add</span>”</span> the files.
10035: Start by adding the directory and then files in the directory. Don't
10036: forget to add the new package to the category's
10037: <code class="filename">Makefile</code>. Make sure you don't forget any files;
10038: you can check by running <span class="quote">“<span class="quote">cvs status</span>”</span>. An example:</p>
10039: <pre class="programlisting">
10040: <code class="prompt">$</code> cd .../pkgsrc/category
10041: <code class="prompt">$</code> cvs add pkgname
10042: <code class="prompt">$</code> cd pkgname
10043: <code class="prompt">$</code> cvs add DESCR Makefile PLIST distinfo buildlink3.mk patches
10044: <code class="prompt">$</code> cvs add patches/p*
10045: <code class="prompt">$</code> cvs status | less
1.34 wiz 10046: <code class="prompt">$</code> cvs commit
1.33 wiz 10047: <code class="prompt">$</code> cd ..
1.236 gutterid 10048: <code class="prompt">$</code> vi Makefile # add SUBDIR+=pkgname line
1.34 wiz 10049: <code class="prompt">$</code> cvs commit Makefile
1.66 asau 10050: <code class="prompt">$</code> cd pkgname
1.73 jnemeth 10051: <code class="prompt">$</code> make CTYPE=Added commit-changes-entry
1.33 wiz 10052: </pre>
1.1 dsieger 10053: <p>The commit message of the initial import should include part of the
10054: <code class="filename">DESCR</code> file, so people reading the mailing lists know
10055: what the package is/does.</p>
1.33 wiz 10056: <p>Also mention the new package in
10057: <code class="filename">pkgsrc/doc/CHANGES-20xx</code>.</p>
10058: <p>Previously, <span class="quote">“<span class="quote">cvs import</span>”</span> was suggested, but it was
10059: much easier to get wrong than <span class="quote">“<span class="quote">cvs add</span>”</span>.</p>
1.1 dsieger 10060: </div>
1.41 asau 10061: <div class="sect1">
1.1 dsieger 10062: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10063: <a name="updating-package"></a>23.6. Updating a package to a newer version</h2></div></div></div>
1.1 dsieger 10064: <p>Please always put a concise, appropriate and relevant summary of the
10065: changes between old and new versions into the commit log when updating
10066: a package. There are various reasons for this:</p>
1.41 asau 10067: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10068: <li class="listitem"><p>A URL is volatile, and can change over time. It may go away completely
1.1 dsieger 10069: or its information may be overwritten by newer information.</p></li>
1.23 wiz 10070: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 10071: repository is very useful for people who use either cvs or anoncvs.</p></li>
1.23 wiz 10072: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 10073: repository is very useful for people who read the pkgsrc-changes mailing
10074: list, so that they can make tactical decisions about when to upgrade
10075: the package.</p></li>
10076: </ul></div>
10077: <p>Please also recognize that, just because a new version of a package
10078: has been released, it should not automatically be upgraded in the CVS
10079: repository. We prefer to be conservative in the packages that are
10080: included in pkgsrc - development or beta packages are not really the
10081: best thing for most places in which pkgsrc is used. Please use your
10082: judgement about what should go into pkgsrc, and bear in mind that
10083: stability is to be preferred above new and possibly untested features.</p>
10084: </div>
1.41 asau 10085: <div class="sect1">
1.1 dsieger 10086: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10087: <a name="renaming-package"></a>23.7. Renaming a package in pkgsrc</h2></div></div></div>
1.20 snj 10088: <p>Renaming packages is not recommended.</p>
1.175 gutterid 10089: <p>When renaming packages, be sure to fix any references to the old name
1.20 snj 10090: in other Makefiles, options, buildlink files, etc.</p>
1.167 leot 10091: <p>
1.175 gutterid 10092: Also, when renaming a package, please add
1.167 leot 10093: the package name and version pattern(s) of the previous package
10094: to <code class="varname">SUPERSEDES</code>.
1.20 snj 10095: This may be repeated for multiple renames.
10096: The new package would be an exact replacement.
1.167 leot 10097: Example:
1.20 snj 10098: </p>
1.167 leot 10099: <pre class="programlisting">
10100: SUPERSEDES+= p5-IO-Compress-Zlib<2.017
10101: SUPERSEDES+= optcomp-[0-9]*
10102: </pre>
1.23 wiz 10103: <p>Note that <span class="quote">“<span class="quote">successor</span>”</span> in the
1.20 snj 10104: CHANGES-<em class="replaceable"><code>YYYY</code></em> file doesn't necessarily
10105: mean that it <span class="emphasis"><em>supersedes</em></span>, as that successor may
10106: not be an exact replacement but is a suggestion for the replaced
10107: functionality.</p>
10108: </div>
1.41 asau 10109: <div class="sect1">
1.20 snj 10110: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10111: <a name="moving-package"></a>23.8. Moving a package in pkgsrc</h2></div></div></div>
1.20 snj 10112: <p>It is preferred that packages are not renamed or moved, but if needed
10113: please follow these steps.
10114: </p>
1.23 wiz 10115: <div class="orderedlist"><ol class="orderedlist" type="1">
10116: <li class="listitem"><p>Make a copy of the directory somewhere else.</p></li>
10117: <li class="listitem">
1.1 dsieger 10118: <p>Remove all CVS dirs.</p>
10119: <p>Alternatively to the first two steps you can also do:</p>
10120: <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>
10121: <p>and use that for further work.</p>
10122: </li>
1.23 wiz 10123: <li class="listitem"><p>Fix <code class="varname">CATEGORIES</code> and any
10124: <code class="varname">DEPENDS</code> paths that just did <span class="quote">“<span class="quote">../package</span>”</span>
10125: instead of <span class="quote">“<span class="quote">../../category/package</span>”</span>.</p></li>
10126: <li class="listitem"><p>In the modified package's Makefile, consider setting
1.20 snj 10127: <code class="varname">PREV_PKGPATH</code> to the previous category/package
10128: pathname. The <code class="varname">PREV_PKGPATH</code> can be used by tools
10129: for doing an update using pkgsrc building; for example, it can
1.246 leot 10130: search the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> database for <code class="varname">PREV_PKGPATH</code>
1.20 snj 10131: (if no <code class="varname">SUPERSEDES</code>) and then use the corresponding
10132: new <code class="varname">PKGPATH</code> for that moved package. Note that
10133: it may have multiple matches, so the tool should also check on the
10134: <code class="varname">PKGBASE</code> too. The <code class="varname">PREV_PKGPATH</code>
10135: probably has no value unless <code class="varname">SUPERSEDES</code> is not
10136: set, i.e. <code class="varname">PKGBASE</code> stays the same. </p></li>
1.237 gutterid 10137: <li class="listitem"><p><span class="command"><strong>cvs add</strong></span> the modified package in the new
1.1 dsieger 10138: place.</p></li>
1.23 wiz 10139: <li class="listitem">
1.1 dsieger 10140: <p>Check if any package depends on it:
10141: </p>
10142: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
10143: <code class="prompt">%</code> <strong class="userinput"><code>grep /package */*/Makefile* */*/buildlink*</code></strong></pre>
10144: </li>
1.23 wiz 10145: <li class="listitem"><p>Fix paths in packages from step 5 to point to new location.</p></li>
10146: <li class="listitem"><p><span class="command"><strong>cvs rm (-f)</strong></span> the package at the old location.</p></li>
10147: <li class="listitem"><p>Remove from <code class="filename">oldcategory/Makefile</code>.</p></li>
10148: <li class="listitem"><p>Add to <code class="filename">newcategory/Makefile</code>.</p></li>
10149: <li class="listitem">
1.1 dsieger 10150: <p>Commit the changed and removed files:</p>
10151: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong></pre>
10152: <p>(and any packages from step 5, of course).</p>
10153: </li>
10154: </ol></div>
10155: </div>
10156: </div>
1.41 asau 10157: <div class="chapter">
1.1 dsieger 10158: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 10159: <a name="devfaq"></a>Chapter 24. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 10160: <p>This section contains the answers to questions that may
10161: arise when you are writing a package. If you don't find your
10162: question answered here, first have a look in the other chapters,
10163: and if you still don't have the answer, ask on the
10164: <code class="literal">pkgsrc-users</code> mailing list.</p>
1.41 asau 10165: <div class="qandaset">
1.174 leot 10166: <a name="devfaq.qandaset"></a><dl>
1.154 rillig 10167: <dt>24.1. <a href="#devfaq.makeflags">What is the difference between
1.1 dsieger 10168: MAKEFLAGS, .MAKEFLAGS and
10169: MAKE_FLAGS?</a>
10170: </dt>
1.154 rillig 10171: <dt>24.2. <a href="#devfaq.make">What is the difference between
1.1 dsieger 10172: MAKE, GMAKE and
10173: MAKE_PROGRAM?</a>
10174: </dt>
1.154 rillig 10175: <dt>24.3. <a href="#devfaq.cc">What is the difference between
1.1 dsieger 10176: CC, PKG_CC and
10177: PKGSRC_COMPILER?</a>
10178: </dt>
1.223 nia 10179: <dt>24.4. <a href="#devfaq.bl3prefix">Why does make show-var
1.1 dsieger 10180: VARNAME=BUILDLINK_PREFIX.foo
10181: say it's empty?</a>
10182: </dt>
1.223 nia 10183: <dt>24.5. <a href="#devfaq.master_sites">What does
1.1 dsieger 10184: ${MASTER_SITE_SOURCEFORGE:=package/} mean? I
10185: don't understand the := inside
10186: it.</a>
10187: </dt>
1.223 nia 10188: <dt>24.6. <a href="#devfaq.mailinglists">Which mailing lists are there for package
1.1 dsieger 10189: developers?</a>
10190: </dt>
1.223 nia 10191: <dt>24.7. <a href="#devfaq.documentation">Where is the pkgsrc
1.1 dsieger 10192: documentation?</a>
10193: </dt>
1.223 nia 10194: <dt>24.8. <a href="#devfaq.too-much-time">I have a little time to kill.
1.174 leot 10195: What shall I do?</a>
1.1 dsieger 10196: </dt>
10197: </dl>
1.41 asau 10198: <table border="0" style="width: 100%;">
10199: <colgroup>
1.1 dsieger 10200: <col align="left" width="1%">
1.23 wiz 10201: <col>
1.41 asau 10202: </colgroup>
1.1 dsieger 10203: <tbody>
1.41 asau 10204: <tr class="question">
1.1 dsieger 10205: <td align="left" valign="top">
1.174 leot 10206: <a name="devfaq.makeflags"></a><a name="devfaq.makeflags.q"></a><p><b>24.1.</b></p>
1.1 dsieger 10207: </td>
10208: <td align="left" valign="top"><p>What is the difference between
10209: <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
10210: <code class="varname">MAKE_FLAGS</code>?</p></td>
10211: </tr>
10212: <tr class="answer">
10213: <td align="left" valign="top"></td>
1.223 nia 10214: <td align="left" valign="top">
10215: <p><code class="varname">MAKEFLAGS</code> are the flags passed
1.246 leot 10216: to the pkgsrc-internal invocations of <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.</p>
1.223 nia 10217: <p><code class="varname">MAKE_FLAGS</code> are the flags that are
10218: passed to the <code class="varname">MAKE_PROGRAM</code> when building the
10219: package.</p>
10220: <p><code class="varname">.MAKEFLAGS</code> is an internal variable of
10221: <span class="command"><strong>bmake</strong></span> and should not be used by
10222: packages.</p>
10223: </td>
1.1 dsieger 10224: </tr>
1.41 asau 10225: <tr class="question">
1.1 dsieger 10226: <td align="left" valign="top">
1.174 leot 10227: <a name="devfaq.make"></a><a name="devfaq.make.q"></a><p><b>24.2.</b></p>
1.1 dsieger 10228: </td>
10229: <td align="left" valign="top"><p>What is the difference between
10230: <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
10231: <code class="varname">MAKE_PROGRAM</code>?</p></td>
10232: </tr>
10233: <tr class="answer">
10234: <td align="left" valign="top"></td>
1.223 nia 10235: <td align="left" valign="top">
10236: <p><code class="varname">MAKE</code> is the path to the
1.246 leot 10237: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
1.223 nia 10238: infrastructure.</p>
10239: <p><code class="varname">GMAKE</code> is the path to GNU Make, but you
10240: need to say <code class="varname">USE_TOOLS+=gmake</code> to use
10241: that.</p>
10242: <p><code class="varname">MAKE_PROGRAM</code> is the path to the Make
10243: program that is used for building the package.</p>
10244: </td>
1.1 dsieger 10245: </tr>
1.41 asau 10246: <tr class="question">
1.1 dsieger 10247: <td align="left" valign="top">
1.174 leot 10248: <a name="devfaq.cc"></a><a name="devfaq.cc.q"></a><p><b>24.3.</b></p>
1.1 dsieger 10249: </td>
10250: <td align="left" valign="top"><p>What is the difference between
10251: <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
10252: <code class="varname">PKGSRC_COMPILER</code>?</p></td>
10253: </tr>
10254: <tr class="answer">
10255: <td align="left" valign="top"></td>
10256: <td align="left" valign="top">
1.223 nia 10257: <p><code class="varname">CC</code> is the path to the real C
10258: compiler, which can be configured by the pkgsrc user.</p>
10259: <p><code class="varname">PKG_CC</code> is the path to the compiler
10260: wrapper.</p>
10261: <p><code class="varname">PKGSRC_COMPILER</code> is
10262: <span class="emphasis"><em>not</em></span> a path to a compiler, but the type of
10263: compiler that should be used. See
10264: <code class="filename">mk/compiler.mk</code> for more information about
10265: the latter variable.</p>
1.1 dsieger 10266: </td>
10267: </tr>
1.41 asau 10268: <tr class="question">
1.1 dsieger 10269: <td align="left" valign="top">
1.223 nia 10270: <a name="devfaq.bl3prefix"></a><a name="devfaq.bl3prefix.q"></a><p><b>24.4.</b></p>
1.1 dsieger 10271: </td>
1.10 hubertf 10272: <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
1.1 dsieger 10273: VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
10274: say it's empty?</p></td>
10275: </tr>
10276: <tr class="answer">
10277: <td align="left" valign="top"></td>
10278: <td align="left" valign="top"><p>For optimization reasons, some variables are only
1.23 wiz 10279: available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To
10280: <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append
1.10 hubertf 10281: <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
1.1 dsieger 10282: command.</p></td>
10283: </tr>
1.41 asau 10284: <tr class="question">
1.1 dsieger 10285: <td align="left" valign="top">
1.223 nia 10286: <a name="devfaq.master_sites"></a><a name="devfaq.master_sites.q"></a><p><b>24.5.</b></p>
1.1 dsieger 10287: </td>
10288: <td align="left" valign="top"><p>What does
1.108 rillig 10289: <code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
10290: don't understand the <code class="code">:=</code> inside
1.1 dsieger 10291: it.</p></td>
10292: </tr>
10293: <tr class="answer">
10294: <td align="left" valign="top"></td>
1.223 nia 10295: <td align="left" valign="top"><p>The <code class="code">:=</code> is not an
10296: assignment operator, even though it may look like one.
1.1 dsieger 10297: Instead, it is a degenerate form of
1.108 rillig 10298: <code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
1.246 leot 10299: which is documented in the <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which is
1.108 rillig 10300: commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the
1.1 dsieger 10301: case of <code class="varname">MASTER_SITE_*</code>,
10302: <em class="replaceable"><code>old_string</code></em> is the empty string and
10303: <em class="replaceable"><code>new_string</code></em> is
1.108 rillig 10304: <code class="code">package/</code>. That's where the
10305: <code class="code">:</code> and the <code class="code">=</code> fall
1.1 dsieger 10306: together.</p></td>
10307: </tr>
1.41 asau 10308: <tr class="question">
1.1 dsieger 10309: <td align="left" valign="top">
1.223 nia 10310: <a name="devfaq.mailinglists"></a><a name="devfaq.mailinglists.q"></a><p><b>24.6.</b></p>
1.1 dsieger 10311: </td>
10312: <td align="left" valign="top"><p>Which mailing lists are there for package
10313: developers?</p></td>
10314: </tr>
10315: <tr class="answer">
10316: <td align="left" valign="top"></td>
1.41 asau 10317: <td align="left" valign="top"><div class="variablelist"><dl class="variablelist">
1.174 leot 10318: <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.1 dsieger 10319: <dd><p>This is a list for technical discussions related
10320: to pkgsrc development, e.g. soliciting feedback for changes to
10321: pkgsrc infrastructure, proposed new features, questions related
10322: to porting pkgsrc to a new platform, advice for maintaining a
10323: package, patches that affect many packages, help requests moved
10324: from pkgsrc-users when an infrastructure bug is found,
10325: etc.</p></dd>
1.174 leot 10326: <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.1 dsieger 10327: <dd><p>All bug reports in category "pkg" sent with
1.246 leot 10328: <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/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.1 dsieger 10329: directly; use one of the other mailing
10330: lists.</p></dd>
10331: </dl></div></td>
10332: </tr>
1.41 asau 10333: <tr class="question">
1.1 dsieger 10334: <td align="left" valign="top">
1.223 nia 10335: <a name="devfaq.documentation"></a><a name="devfaq.documentation.q"></a><p><b>24.7.</b></p>
1.1 dsieger 10336: </td>
10337: <td align="left" valign="top"><p>Where is the pkgsrc
10338: documentation?</p></td>
10339: </tr>
10340: <tr class="answer">
10341: <td align="left" valign="top"></td>
10342: <td align="left" valign="top">
10343: <p>There are many places where you can find
10344: documentation about pkgsrc:</p>
1.41 asau 10345: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10346: <li class="listitem"><p>The pkgsrc guide (this document) is a collection
1.1 dsieger 10347: of chapters that explain large parts of pkgsrc, but some
10348: chapters tend to be outdated. Which ones they are is hard to
10349: say.</p></li>
1.174 leot 10350: <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.1 dsieger 10351: about certain features, announcements of new parts of the pkgsrc
10352: infrastructure and sometimes even announcements that a certain
10353: feature has been marked as obsolete. The benefit here is that
10354: each message has a date appended to it.</p></li>
1.23 wiz 10355: <li class="listitem"><p>Many of the files in the
1.1 dsieger 10356: <code class="filename">mk/</code> directory start with a comment that
10357: describes the purpose of the file and how it can be used by the
10358: pkgsrc user and package authors. An easy way to find this
1.10 hubertf 10359: documentation is to run <span class="command"><strong>bmake
1.1 dsieger 10360: help</strong></span>.</p></li>
1.23 wiz 10361: <li class="listitem"><p>The CVS log messages are a rich source of
1.1 dsieger 10362: information, but they tend to be highly abbreviated, especially
10363: for actions that occur often. Some contain a detailed
10364: description of what has changed, but they are geared towards the
10365: other pkgsrc developers, not towards an average pkgsrc user.
10366: They also only document <span class="emphasis"><em>changes</em></span>, so if you
10367: don't know what has been before, these messages may not be worth
10368: too much to you.</p></li>
1.23 wiz 10369: <li class="listitem"><p>Some parts of pkgsrc are only <span class="quote">“<span class="quote">implicitly
10370: documented</span>”</span>, that is the documentation exists only in the
1.1 dsieger 10371: mind of the developer who wrote the code. To get this
1.10 hubertf 10372: information, use the <span class="command"><strong>cvs annotate</strong></span> command
1.1 dsieger 10373: to see who has written it and ask on the
10374: <code class="literal">tech-pkg</code> mailing list, so that others can
10375: find your questions later (see above). To be sure that the
10376: developer in charge reads the mail, you may CC him or
10377: her.</p></li>
10378: </ul></div>
1.184 rillig 10379: </td>
10380: </tr>
10381: <tr class="question">
10382: <td align="left" valign="top">
1.223 nia 10383: <a name="devfaq.too-much-time"></a><a name="devfaq.too-much-time.q"></a><p><b>24.8.</b></p>
1.184 rillig 10384: </td>
1.223 nia 10385: <td align="left" valign="top"><p>I have a little time to kill.
1.184 rillig 10386: What shall I do?</p></td>
10387: </tr>
10388: <tr class="answer">
10389: <td align="left" valign="top"></td>
10390: <td align="left" valign="top">
10391: <p>This is not really an FAQ yet, but here's the answer
10392: anyway.</p>
1.41 asau 10393: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.184 rillig 10394: <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
1.207 leot 10395: <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.184 rillig 10396: will tell you about newer versions of installed packages that are
10397: available, but not yet updated in pkgsrc.</p></li>
10398: <li class="listitem"><p>Browse <code class="filename">pkgsrc/doc/TODO</code>
10399: — it contains a list of suggested new packages and a list of
10400: cleanups and enhancements for pkgsrc that would be nice to
10401: have.</p></li>
10402: <li class="listitem"><p>Review packages for which review was requested on
10403: the <a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a>
10404: mailing list.</p></li>
1.1 dsieger 10405: </ul></div>
1.184 rillig 10406: </td>
1.1 dsieger 10407: </tr>
10408: </tbody>
1.184 rillig 10409: </table>
1.1 dsieger 10410: </div>
10411: </div>
10412: </div>
1.41 asau 10413: <div class="part">
1.1 dsieger 10414: <div class="titlepage"><div><div><h1 class="title">
10415: <a name="infrastructure"></a>Part III. The pkgsrc infrastructure internals</h1></div></div></div>
1.41 asau 10416: <div class="partintro">
1.1 dsieger 10417: <div></div>
10418: <p>This part of the guide deals with everything
10419: from the infrastructure that is behind the interfaces described
10420: in the developer's guide. A casual package maintainer should not
10421: need anything from this part.</p>
10422: <div class="toc">
10423: <p><b>Table of Contents</b></p>
1.100 leot 10424: <dl class="toc">
1.184 rillig 10425: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 10426: <dd><dl>
1.184 rillig 10427: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10428: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10429: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.1 dsieger 10430: <dd><dl>
1.184 rillig 10431: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10432: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.1 dsieger 10433: </dl></dd>
1.184 rillig 10434: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10435: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10436: <dd><dl>
1.184 rillig 10437: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10438: <dt><span class="sect2"><a href="#infr.design.intf.action">25.5.2. Actions taken on behalf of parameters</a></span></dt>
1.1 dsieger 10439: </dl></dd>
1.184 rillig 10440: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10441: <dd><dl>
1.184 rillig 10442: <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>
10443: <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.1 dsieger 10444: </dl></dd>
10445: </dl></dd>
1.184 rillig 10446: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.1 dsieger 10447: <dd><dl>
1.184 rillig 10448: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10449: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.1 dsieger 10450: <dd><dl>
1.184 rillig 10451: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10452: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.1 dsieger 10453: </dl></dd>
10454: </dl></dd>
1.184 rillig 10455: <dt><span class="chapter"><a href="#porting">27. Porting pkgsrc</a></span></dt>
10456: <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.1 dsieger 10457: </dl>
10458: </div>
10459: </div>
1.41 asau 10460: <div class="chapter">
1.1 dsieger 10461: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10462: <a name="infr.design"></a>Chapter 25. Design of the pkgsrc infrastructure</h2></div></div></div>
1.1 dsieger 10463: <div class="toc">
10464: <p><b>Table of Contents</b></p>
1.100 leot 10465: <dl class="toc">
1.184 rillig 10466: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10467: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10468: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.1 dsieger 10469: <dd><dl>
1.184 rillig 10470: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10471: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.1 dsieger 10472: </dl></dd>
1.184 rillig 10473: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10474: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10475: <dd><dl>
1.184 rillig 10476: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10477: <dt><span class="sect2"><a href="#infr.design.intf.action">25.5.2. Actions taken on behalf of parameters</a></span></dt>
1.1 dsieger 10478: </dl></dd>
1.184 rillig 10479: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10480: <dd><dl>
1.184 rillig 10481: <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>
10482: <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.1 dsieger 10483: </dl></dd>
10484: </dl>
10485: </div>
10486: <p>The pkgsrc infrastructure consists of many small Makefile
10487: fragments. Each such fragment needs a properly specified
10488: interface. This chapter explains how such an interface looks
10489: like.</p>
1.41 asau 10490: <div class="sect1">
1.1 dsieger 10491: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10492: <a name="infr.vardef"></a>25.1. The meaning of variable definitions</h2></div></div></div>
1.1 dsieger 10493: <p>Whenever a variable is defined in the pkgsrc
10494: infrastructure, the location and the way of definition provide
10495: much information about the intended use of that variable.
10496: Additionally, more documentation may be found in a header
10497: comment or in this pkgsrc guide.</p>
10498: <p>A special file is
10499: <code class="filename">mk/defaults/mk.conf</code>, which lists all
10500: variables that are intended to be user-defined. They are either
10501: defined using the <code class="literal">?=</code> operator or they are
10502: left undefined because defining them to anything would
1.23 wiz 10503: effectively mean <span class="quote">“<span class="quote">yes</span>”</span>. All these variables may be
1.1 dsieger 10504: overridden by the pkgsrc user in the <code class="varname">MAKECONF</code>
10505: file.</p>
10506: <p>Outside this file, the following conventions apply:
10507: Variables that are defined using the <code class="literal">?=</code>
10508: operator may be overridden by a package.</p>
10509: <p>Variables that are defined using the <code class="literal">=</code>
10510: operator may be used read-only at run-time.</p>
10511: <p>Variables whose name starts with an underscore must not be
10512: accessed outside the pkgsrc infrastructure at all. They may
10513: change without further notice.</p>
1.41 asau 10514: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 10515: <h3 class="title">Note</h3>
10516: <p>These conventions are currently not applied
10517: consistently to the complete pkgsrc
10518: infrastructure.</p>
10519: </div>
10520: </div>
1.41 asau 10521: <div class="sect1">
1.1 dsieger 10522: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10523: <a name="infr.vardef.problems"></a>25.2. Avoiding problems before they arise</h2></div></div></div>
1.1 dsieger 10524: <p>All variables that contain lists of things should default
10525: to being empty. Two examples that do not follow this rule are
10526: <code class="varname">USE_LANGUAGES</code> and
10527: <code class="varname">DISTFILES</code>. These variables cannot simply be
10528: modified using the <code class="literal">+=</code> operator in package
10529: <code class="filename">Makefile</code>s (or other files included by
10530: them), since there is no guarantee whether the variable is
10531: already set or not, and what its value is. In the case of
1.23 wiz 10532: <code class="varname">DISTFILES</code>, the packages <span class="quote">“<span class="quote">know</span>”</span>
1.1 dsieger 10533: the default value and just define it as in the following
10534: example.</p>
10535: <pre class="programlisting">
10536: DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz
10537: </pre>
10538: <p>Because of the selection of this default value, the same
10539: value appears in many package Makefiles. Similarly for
10540: <code class="varname">USE_LANGUAGES</code>, but in this case the default
1.23 wiz 10541: value (<span class="quote">“<span class="quote"><code class="literal">c</code></span>”</span>) is so short that it
1.1 dsieger 10542: doesn't stand out. Nevertheless it is mentioned in many
10543: files.</p>
10544: </div>
1.41 asau 10545: <div class="sect1">
1.1 dsieger 10546: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10547: <a name="infr.var"></a>25.3. Variable evaluation</h2></div></div></div>
1.41 asau 10548: <div class="sect2">
1.1 dsieger 10549: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10550: <a name="infr.var.load"></a>25.3.1. At load time</h3></div></div></div>
1.1 dsieger 10551: <p>Variable evaluation takes place either at load time or at
10552: runtime, depending on the context in which they occur. The
10553: contexts where variables are evaluated at load time are:</p>
1.41 asau 10554: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10555: <li class="listitem"><p>The right hand side of the <code class="literal">:=</code>
1.1 dsieger 10556: and <code class="literal">!=</code> operators,</p></li>
1.23 wiz 10557: <li class="listitem"><p>Make directives like <code class="literal">.if</code> or
1.1 dsieger 10558: <code class="literal">.for</code>,</p></li>
1.23 wiz 10559: <li class="listitem"><p>Dependency lines.</p></li>
1.1 dsieger 10560: </ul></div>
10561: <p>A special exception are references to the iteration
10562: variables of <code class="literal">.for</code> loops, which are expanded
10563: inline, no matter in which context they appear.</p>
10564: <p>As the values of variables may change during load time,
10565: care must be taken not to evaluate them by accident. Typical
10566: examples for variables that should not be evaluated at load time
10567: are <code class="varname">DEPENDS</code> and
10568: <code class="varname">CONFIGURE_ARGS</code>. To make the effect more
10569: clear, here is an example:</p>
10570: <pre class="programlisting">
10571: CONFIGURE_ARGS= # none
10572: CFLAGS= -O
10573: CONFIGURE_ARGS+= CFLAGS=${CFLAGS:Q}
10574:
10575: CONFIGURE_ARGS:= ${CONFIGURE_ARGS}
10576:
10577: CFLAGS+= -Wall
1.111 sevan 10578: </pre>
1.1 dsieger 10579: <p>This code shows how the use of the <code class="literal">:=</code>
10580: operator can quickly lead to unexpected results. The first
10581: paragraph is fairly common code. The second paragraph evaluates
10582: the <code class="varname">CONFIGURE_ARGS</code> variable, which results in
10583: <code class="literal">CFLAGS=-O</code>. In the third paragraph, the
10584: <code class="literal">-Wall</code> is appended to the
10585: <code class="varname">CFLAGS</code>, but this addition will not appear in
10586: <code class="varname">CONFIGURE_ARGS</code>. In actual code, the three
10587: paragraphs from above typically occur in completely unrelated
10588: files.</p>
10589: </div>
1.41 asau 10590: <div class="sect2">
1.1 dsieger 10591: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10592: <a name="infr.var.run"></a>25.3.2. At runtime</h3></div></div></div>
1.1 dsieger 10593: <p>After all the files have been loaded, the values of the
10594: variables cannot be changed anymore. Variables that are used in
10595: the shell commands are expanded at this point.</p>
10596: </div>
10597: </div>
1.41 asau 10598: <div class="sect1">
1.1 dsieger 10599: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10600: <a name="infr.varspec"></a>25.4. How can variables be specified?</h2></div></div></div>
1.1 dsieger 10601: <p>There are many ways in which the definition and use of a
1.108 rillig 10602: variable can be restricted in order to detect bugs and violations
10603: of the (mostly unwritten) policies. A package can be checked with
10604: <code class="literal">pkglint -Wall</code> to see whether it meets these
10605: rules.</p>
1.1 dsieger 10606: </div>
1.41 asau 10607: <div class="sect1">
1.1 dsieger 10608: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10609: <a name="infr.design.intf"></a>25.5. Designing interfaces for Makefile fragments</h2></div></div></div>
1.1 dsieger 10610: <p>Most of the <code class="filename">.mk</code> files fall into one
10611: of the following classes. Cases where a file falls into more
10612: than one class should be avoided as it often leads to subtle
10613: bugs.</p>
1.41 asau 10614: <div class="sect2">
1.1 dsieger 10615: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10616: <a name="infr.design.intf.proc"></a>25.5.1. Procedures with parameters</h3></div></div></div>
1.1 dsieger 10617: <p>In a traditional imperative programming language some of
10618: the <code class="filename">.mk</code> files could be described as
1.14 jmcneill 10619: procedures. They take some input parameters and—after
10620: inclusion—provide a result in output parameters. Since all
1.1 dsieger 10621: variables in <code class="filename">Makefile</code>s have global scope
10622: care must be taken not to use parameter names that have already
10623: another meaning. For example, <code class="varname">PKGNAME</code> is a
10624: bad choice for a parameter name.</p>
10625: <p>Procedures are completely evaluated at preprocessing time.
10626: That is, when calling a procedure all input parameters must be
10627: completely resolvable. For example,
10628: <code class="varname">CONFIGURE_ARGS</code> should never be an input
10629: parameter since it is very likely that further text will be
10630: added after calling the procedure, which would effectively apply
10631: the procedure to only a part of the variable. Also, references
1.108 rillig 10632: to other variables will be modified after calling the
1.1 dsieger 10633: procedure.</p>
10634: <p>A procedure can declare its output parameters either as
10635: suitable for use in preprocessing directives or as only
10636: available at runtime. The latter alternative is for variables
10637: that contain references to other runtime variables.</p>
10638: <p>Procedures shall be written such that it is possible to
10639: call the procedure more than once. That is, the file must not
10640: contain multiple-inclusion guards.</p>
10641: <p>Examples for procedures are
10642: <code class="filename">mk/bsd.options.mk</code> and
10643: <code class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express
10644: that the parameters are evaluated at load time, they should be
10645: assigned using the <code class="literal">:=</code> operator, which should
10646: be used only for this purpose.</p>
10647: </div>
1.41 asau 10648: <div class="sect2">
1.1 dsieger 10649: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10650: <a name="infr.design.intf.action"></a>25.5.2. Actions taken on behalf of parameters</h3></div></div></div>
1.1 dsieger 10651: <p>Action files take some input parameters and may define
10652: runtime variables. They shall not define loadtime variables.
10653: There are action files that are included implicitly by the
10654: pkgsrc infrastructure, while other must be included
10655: explicitly.</p>
10656: <p>An example for action files is
10657: <code class="filename">mk/subst.mk</code>.</p>
10658: </div>
10659: </div>
1.41 asau 10660: <div class="sect1">
1.1 dsieger 10661: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10662: <a name="infr.order"></a>25.6. The order in which files are loaded</h2></div></div></div>
1.1 dsieger 10663: <p>Package <code class="filename">Makefile</code>s usually consist of
10664: a set of variable definitions, and include the file
10665: <code class="filename">../../mk/bsd.pkg.mk</code> in the very last line.
10666: Before that, they may also include various other
10667: <code class="filename">*.mk</code> files if they need to query the
10668: availability of certain features like the type of compiler or
10669: the X11 implementation. Due to the heavy use of preprocessor
10670: directives like <code class="literal">.if</code> and
10671: <code class="literal">.for</code>, the order in which the files are loaded
10672: matters.</p>
10673: <p>This section describes at which point the various files
10674: are loaded and gives reasons for that order.</p>
1.41 asau 10675: <div class="sect2">
1.1 dsieger 10676: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10677: <a name="infr.order.prefs"></a>25.6.1. The order in <code class="filename">bsd.prefs.mk</code>
1.1 dsieger 10678: </h3></div></div></div>
10679: <p>The very first action in <code class="filename">bsd.prefs.mk</code>
10680: is to define some essential variables like
10681: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code> and
10682: <code class="varname">MACHINE_ARCH</code>.</p>
10683: <p>Then, the user settings are loaded from the file specified
1.10 hubertf 10684: in <code class="varname">MAKECONF</code>, which is usually <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.
1.4 rillig 10685: After that, those variables
1.1 dsieger 10686: that have not been overridden by the user are loaded from
10687: <code class="filename">mk/defaults/mk.conf</code>.</p>
10688: <p>After the user settings, the system settings and platform
10689: settings are loaded, which may override the user
10690: settings.</p>
10691: <p>Then, the tool definitions are loaded. The tool wrappers
10692: are not yet in effect. This only happens when building a
10693: package, so the proper variables must be used instead of the
10694: direct tool names.</p>
10695: <p>As the last steps, some essential variables from the
10696: wrapper and the package system flavor are loaded, as well as the
10697: variables that have been cached in earlier phases of a package
10698: build.</p>
10699: </div>
1.41 asau 10700: <div class="sect2">
1.1 dsieger 10701: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10702: <a name="infr.order.pkg"></a>25.6.2. The order in <code class="filename">bsd.pkg.mk</code>
1.1 dsieger 10703: </h3></div></div></div>
10704: <p>First, <code class="filename">bsd.prefs.mk</code> is loaded.</p>
10705: <p>Then, the various <code class="filename">*-vars.mk</code> files are
10706: loaded, which fill default values for those variables that have
10707: not been defined by the package. These variables may later
10708: be used even in unrelated files.</p>
10709: <p>Then, the file <code class="filename">bsd.pkg.error.mk</code>
10710: provides the target <code class="literal">error-check</code> that is added
10711: as a special dependency to all other targets that use
10712: <code class="varname">DELAYED_ERROR_MSG</code> or
10713: <code class="varname">DELAYED_WARNING_MSG</code>.</p>
10714: <p>Then, the package-specific hacks from
10715: <code class="filename">hacks.mk</code> are included.</p>
10716: <p>Then, various other files follow. Most of them don't have
10717: any dependencies on what they need to have included before or
10718: after them, though some do.</p>
10719: <p>The code to check <code class="varname">PKG_FAIL_REASON</code> and
10720: <code class="varname">PKG_SKIP_REASON</code> is then executed, which
10721: restricts the use of these variables to all the files that have
10722: been included before. Appearances in later files will be
10723: silently ignored.</p>
10724: <p>Then, the files for the main targets are included, in the
10725: order of later execution, though the actual order should not
10726: matter.</p>
10727: <p>At last, some more files are included that don't set any
10728: interesting variables but rather just define make targets to be
10729: executed.</p>
10730: </div>
10731: </div>
10732: </div>
1.41 asau 10733: <div class="chapter">
1.1 dsieger 10734: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10735: <a name="regression"></a>Chapter 26. Regression tests</h2></div></div></div>
1.1 dsieger 10736: <div class="toc">
10737: <p><b>Table of Contents</b></p>
1.100 leot 10738: <dl class="toc">
1.184 rillig 10739: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10740: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.1 dsieger 10741: <dd><dl>
1.184 rillig 10742: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10743: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.1 dsieger 10744: </dl></dd>
10745: </dl>
10746: </div>
10747: <p>The pkgsrc infrastructure consists of a large codebase,
10748: and there are many corners where every little bit of a file is
10749: well thought out, making pkgsrc likely to fail as soon as
10750: anything is changed near those parts. To prevent most changes
10751: from breaking anything, a suite of regression tests should go
10752: along with every important part of the pkgsrc infrastructure.
10753: This chapter describes how regression tests work in pkgsrc and
10754: how you can add new tests.</p>
1.41 asau 10755: <div class="sect1">
1.1 dsieger 10756: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10757: <a name="regression.run"></a>26.1. Running the regression tests</h2></div></div></div>
1.207 leot 10758: <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.10 hubertf 10759: provides the <span class="command"><strong>pkg_regress</strong></span> command. Then you
1.1 dsieger 10760: can simply run that command, which will run all tests in the
1.168 rillig 10761: <code class="filename">regress/</code> directory.</p>
1.1 dsieger 10762: </div>
1.41 asau 10763: <div class="sect1">
1.1 dsieger 10764: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10765: <a name="regression.new"></a>26.2. Adding a new regression test</h2></div></div></div>
1.168 rillig 10766: <p>Every directory in the <code class="filename">regress/</code>
10767: directory that contains a file called <code class="filename">spec</code>
1.1 dsieger 10768: is considered a regression test. This file is a shell program
1.10 hubertf 10769: that is included by the <span class="command"><strong>pkg_regress</strong></span> command.
1.1 dsieger 10770: The following functions can be overridden to suit your
10771: needs.</p>
1.41 asau 10772: <div class="sect2">
1.1 dsieger 10773: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10774: <a name="regression.fun.override"></a>26.2.1. Overridable functions</h3></div></div></div>
1.108 rillig 10775: <p>These functions do not take any parameters. Although they
10776: are called in <span class="quote">“<span class="quote">set -e</span>”</span> mode, they don't stop at the
1.174 leot 10777: first failing command. See <a class="ulink" href="https://stackoverflow.com/q/4072984" target="_top">this Stack Overflow
1.108 rillig 10778: question</a> for details.</p>
1.41 asau 10779: <div class="variablelist"><dl class="variablelist">
1.108 rillig 10780: <dt><span class="term"><code class="varname">do_setup</code></span></dt>
1.1 dsieger 10781: <dd><p>This function prepares the environment for the
10782: test. By default it does nothing.</p></dd>
1.108 rillig 10783: <dt><span class="term"><code class="varname">do_test</code></span></dt>
10784: <dd>
10785: <p>This function runs the actual test. By default,
1.1 dsieger 10786: it calls <code class="varname">TEST_MAKE</code> with the arguments
10787: <code class="varname">MAKEARGS_TEST</code> and writes its output including
10788: error messages into the file
1.108 rillig 10789: <code class="varname">TEST_OUTFILE</code>.</p>
10790: <p>When defining this function, make sure that all output that
10791: needs to be checked is written to the correct output file.
10792: Example:</p>
10793: <pre class="programlisting">
10794: do_test() {
1.112 rillig 10795: echo "Example output"
1.108 rillig 10796: } 1>$TEST_OUTFILE 2>&1
10797: </pre>
10798: </dd>
10799: <dt><span class="term"><code class="varname">check_result</code></span></dt>
10800: <dd>
10801: <p>This function is run after the test and is
1.1 dsieger 10802: typically used to compare the actual output from the one that is
10803: expected. It can make use of the various helper functions from
1.108 rillig 10804: the next section. Example:</p>
10805: <pre class="programlisting">
10806: check_result() {
1.112 rillig 10807: exit_status 0
10808: output_require "Example"
10809: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
10810: output_prohibit "no such file or directory"
1.168 rillig 10811: regress_fail "expected $expected but got $actual for input $input"
1.108 rillig 10812: }
10813: </pre>
10814: </dd>
10815: <dt><span class="term"><code class="varname">do_cleanup</code></span></dt>
1.1 dsieger 10816: <dd><p>This function cleans everything up after the
10817: test has been run. By default it does nothing.</p></dd>
10818: </dl></div>
10819: </div>
1.41 asau 10820: <div class="sect2">
1.1 dsieger 10821: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10822: <a name="regression.fun.helper"></a>26.2.2. Helper functions</h3></div></div></div>
1.41 asau 10823: <div class="variablelist"><dl class="variablelist">
1.168 rillig 10824: <dt><span class="term"><code class="varname">regress_fail <em class="replaceable"><code>message...</code></em></code></span></dt>
10825: <dd><p>This function makes the test fail with the given error message.</p></dd>
1.108 rillig 10826: <dt><span class="term"><code class="varname">exit_status expected</code></span></dt>
1.1 dsieger 10827: <dd><p>This function compares the exitcode of the
1.108 rillig 10828: <span class="command"><strong>do_test</strong></span> function with its first parameter.
1.1 dsieger 10829: If they differ, the test will fail.</p></dd>
1.108 rillig 10830: <dt><span class="term"><code class="varname">output_require regex...</code></span></dt>
10831: <dd>
10832: <p>This function checks for each of its parameters
10833: if the output from <span class="command"><strong>do_test</strong></span> matches the
1.1 dsieger 10834: extended regular expression. If it does not, the test will
1.108 rillig 10835: fail. Example:</p>
10836: <pre class="programlisting">
10837: output_require "looks fine"
10838: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
10839: </pre>
10840: </dd>
1.177 leot 10841: <dt><span class="term"><code class="varname">output_prohibit regex...</code></span></dt>
1.1 dsieger 10842: <dd><p>This function checks for each of its parameters
1.10 hubertf 10843: if the output from <span class="command"><strong>do_test()</strong></span> does
1.1 dsieger 10844: <span class="emphasis"><em>not</em></span> match the extended regular expression.
10845: If any of the regular expressions matches, the test will
10846: fail.</p></dd>
10847: </dl></div>
10848: </div>
10849: </div>
10850: </div>
1.41 asau 10851: <div class="chapter">
1.1 dsieger 10852: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10853: <a name="porting"></a>Chapter 27. Porting pkgsrc</h2></div></div></div>
1.1 dsieger 10854: <div class="toc">
10855: <p><b>Table of Contents</b></p>
1.184 rillig 10856: <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.1 dsieger 10857: </div>
10858: <p>The pkgsrc system has already been ported to many
10859: operating systems, hardware architectures and compilers. This
10860: chapter explains the necessary steps to make pkgsrc even more
10861: portable.</p>
1.41 asau 10862: <div class="sect1">
1.1 dsieger 10863: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10864: <a name="porting.opsys"></a>27.1. Porting pkgsrc to a new operating system</h2></div></div></div>
1.1 dsieger 10865: <p>To port pkgsrc to a new operating system (called
10866: <code class="literal">MyOS</code> in this example), you need to touch the
10867: following files:</p>
1.41 asau 10868: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 10869: <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>
10870: <dd><p>This file contains some basic definitions, for
10871: example the name of the C
10872: compiler.</p></dd>
10873: <dt><span class="term"><code class="filename">mk/bsd.prefs.mk</code></span></dt>
10874: <dd><p>Insert code that defines the variables
10875: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code>,
1.212 wiz 10876: <code class="varname">OPSYS_VERSION</code>, <code class="varname">LOWER_VENDOR</code>,
1.1 dsieger 10877: <code class="varname">MACHINE_ARCH</code>, <code class="varname">OBJECT_FMT</code>,
10878: <code class="varname">APPEND_ELF</code>, and the other variables that
10879: appear in this file.</p></dd>
10880: <dt><span class="term"><code class="filename">mk/platform/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10881: <dd><p>This file contains the platform-specific
10882: definitions that are used by pkgsrc. Start by copying one of the
10883: other files and edit it to your
10884: needs.</p></dd>
10885: <dt><span class="term"><code class="filename">mk/tools/tools.<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10886: <dd><p>This file defines the paths to all the tools
10887: that are needed by one or the other package in pkgsrc, as well
10888: as by pkgsrc itself. Find out where these tools are on your
10889: platform and add them.</p></dd>
10890: </dl></div>
10891: <p>Now, you should be able to build some basic packages, like
1.207 leot 10892: <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.1 dsieger 10893: </div>
10894: </div>
10895: </div>
1.41 asau 10896: <div class="appendix">
10897: <div class="titlepage"><div><div><h1 class="title">
10898: <a name="examples"></a>Appendix A. A simple example package: bison</h1></div></div></div>
1.1 dsieger 10899: <div class="toc">
10900: <p><b>Table of Contents</b></p>
1.100 leot 10901: <dl class="toc">
1.1 dsieger 10902: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
10903: <dd><dl>
10904: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
10905: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
10906: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.172 rillig 10907: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.1 dsieger 10908: </dl></dd>
10909: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
10910: </dl>
10911: </div>
10912: <p>We checked to find a piece of software that wasn't in the packages
10913: collection, and picked GNU bison. Quite why someone would want to have
1.10 hubertf 10914: <span class="command"><strong>bison</strong></span> when Berkeley <span class="command"><strong>yacc</strong></span> is already
1.1 dsieger 10915: present in the tree is beyond us, but it's useful for the purposes of
10916: this exercise.</p>
1.41 asau 10917: <div class="sect1">
1.1 dsieger 10918: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10919: <a name="example-files"></a>A.1. files</h2></div></div></div>
1.41 asau 10920: <div class="sect2">
1.1 dsieger 10921: <div class="titlepage"><div><div><h3 class="title">
10922: <a name="example-Makefile"></a>A.1.1. Makefile</h3></div></div></div>
10923: <pre class="programlisting">
10924: # $NetBSD$
10925: #
10926:
10927: DISTNAME= bison-1.25
10928: CATEGORIES= devel
1.171 rillig 10929: MASTER_SITES= ${MASTER_SITE_GNU:=bison/}
1.1 dsieger 10930:
1.29 dholland 10931: MAINTAINER= pkgsrc-users@NetBSD.org
1.174 leot 10932: HOMEPAGE= https://www.gnu.org/software/bison/bison.html
1.1 dsieger 10933: COMMENT= GNU yacc clone
10934:
10935: GNU_CONFIGURE= yes
1.46 wiz 10936: INFO_FILES= yes
1.1 dsieger 10937:
10938: .include "../../mk/bsd.pkg.mk"
10939: </pre>
10940: </div>
1.41 asau 10941: <div class="sect2">
1.1 dsieger 10942: <div class="titlepage"><div><div><h3 class="title">
10943: <a name="example-descr"></a>A.1.2. DESCR</h3></div></div></div>
10944: <pre class="programlisting">
10945: GNU version of yacc. Can make re-entrant parsers, and numerous other
1.246 leot 10946: improvements. Why you would want this when Berkeley <a class="citerefentry" href="//man.NetBSD.org/NetBSD-9.3/yacc.1"><span class="citerefentry"><span class="refentrytitle">yacc</span>(1)</span></a> is part
1.1 dsieger 10947: of the NetBSD source tree is beyond me.
10948: </pre>
10949: </div>
1.41 asau 10950: <div class="sect2">
1.1 dsieger 10951: <div class="titlepage"><div><div><h3 class="title">
10952: <a name="example-plist"></a>A.1.3. PLIST</h3></div></div></div>
10953: <pre class="programlisting">
10954: @comment $NetBSD$
10955: bin/bison
10956: man/man1/bison.1.gz
10957: share/bison.simple
10958: share/bison.hairy
10959: </pre>
10960: </div>
1.41 asau 10961: <div class="sect2">
1.1 dsieger 10962: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 10963: <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with pkglint</h3></div></div></div>
1.1 dsieger 10964: <p>The NetBSD package system comes with
1.207 leot 10965: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/index.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>
1.1 dsieger 10966: which helps to check the contents of these
10967: files. After installation it is quite easy to use, just change to the
1.171 rillig 10968: directory of the package you wish to examine and run
1.10 hubertf 10969: <span class="command"><strong>pkglint</strong></span>:</p>
1.1 dsieger 10970: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>pkglint</code></strong>
1.171 rillig 10971: ERROR: Makefile: Each package must define its LICENSE.
10972: WARN: Makefile:9: HOMEPAGE should migrate from http to https.
10973: NOTE: PLIST:3: The .gz extension is unnecessary for manual pages.
10974: WARN: PLIST:5: "share/bison.hairy" should be sorted before "share/bison.simple".
10975: 1 error, 2 warnings and 1 note found.
10976: (Run "pkglint -e" to show explanations.)
10977: (Run "pkglint -fs" to show what can be fixed automatically.)
1.172 rillig 10978: (Run "pkglint -F" to automatically fix some issues.)</pre>
1.1 dsieger 10979: <p>Depending on the supplied command line arguments (see pkglint(1)),
1.170 rillig 10980: more checks will be performed. Use e.g. <span class="command"><strong>pkglint
1.1 dsieger 10981: -Wall</strong></span> for a very thorough check.</p>
10982: </div>
10983: </div>
1.41 asau 10984: <div class="sect1">
1.1 dsieger 10985: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10986: <a name="steps-for-b-i-p"></a>A.2. Steps for building, installing, packaging</h2></div></div></div>
10987: <p>Create the directory where the package lives,
10988: plus any auxiliary directories:</p>
10989: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/pkgsrc/lang</code></strong>
10990: <code class="prompt">#</code> <strong class="userinput"><code>mkdir bison</code></strong>
10991: <code class="prompt">#</code> <strong class="userinput"><code>cd bison</code></strong>
10992: <code class="prompt">#</code> <strong class="userinput"><code>mkdir patches</code></strong></pre>
10993: <p>Create <code class="filename">Makefile</code>, <code class="filename">DESCR</code> and
1.184 rillig 10994: <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.1 dsieger 10995: then continue with fetching the distfile:</p>
10996: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make fetch</code></strong>
10997: >> bison-1.25.tar.gz doesn't seem to exist on this system.
10998: >> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
10999: Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
11000: ftp: Error retrieving file: 500 Internal error
11001:
11002: >> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
11003: Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
11004: ftp: Error retrieving file: 500 Internal error
11005:
11006: >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
11007: Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
11008: Successfully retrieved file.</pre>
11009: <p>Generate the checksum of the distfile into
11010: <code class="filename">distinfo</code>:</p>
11011: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make makedistinfo</code></strong></pre>
11012: <p>Now compile:</p>
11013: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
11014: >> Checksum OK for bison-1.25.tar.gz.
11015: ===> Extracting for bison-1.25
11016: ===> Patching for bison-1.25
11017: ===> Ignoring empty patch directory
11018: ===> Configuring for bison-1.25
11019: creating cache ./config.cache
11020: checking for gcc... cc
11021: checking whether we are using GNU C... yes
11022: checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
11023: checking how to run the C preprocessor... cc -E
11024: checking for minix/config.h... no
11025: checking for POSIXized ISC... no
11026: checking whether cross-compiling... no
11027: checking for ANSI C header files... yes
11028: checking for string.h... yes
11029: checking for stdlib.h... yes
11030: checking for memory.h... yes
11031: checking for working const... yes
11032: checking for working alloca.h... no
11033: checking for alloca... yes
11034: checking for strerror... yes
11035: updating cache ./config.cache
11036: creating ./config.status
11037: creating Makefile
11038: ===> Building for bison-1.25
11039: 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
11040: 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
11041: 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
11042: 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
11043: 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
11044: 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
11045: 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
11046: 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
11047: 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
11048: 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
11049: 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
11050: 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
11051: 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
11052: 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
11053: 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
11054: 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
11055: 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
11056: 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
11057: 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
11058: 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
11059: 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
11060: 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
11061: ./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
11062: rm -f bison.s1
11063: sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1</pre>
11064: <p>Everything seems OK, so install the files:</p>
11065: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
11066: >> Checksum OK for bison-1.25.tar.gz.
11067: ===> Installing for bison-1.25
11068: sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
11069: rm -f /usr/pkg/bin/bison
11070: cd /usr/pkg/share; rm -f bison.simple bison.hairy
11071: rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
11072: install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
11073: /usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
11074: /usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
11075: cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
11076: /usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
11077: ===> Registering installation for bison-1.25</pre>
11078: <p>You can now use bison, and also - if you decide so - remove it with
1.10 hubertf 11079: <span class="command"><strong>pkg_delete bison</strong></span>. Should you decide that you want a
1.1 dsieger 11080: binary package, do this now:</p>
11081: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
11082: >> Checksum OK for bison-1.25.tar.gz.
11083: ===> Building package for bison-1.25
11084: Creating package bison-1.25.tgz
11085: Registering depends:.
11086: Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre>
11087: <p>Now that you don't need the source and object files
11088: any more, clean up:</p>
11089: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make clean</code></strong>
11090: ===> Cleaning for bison-1.25</pre>
11091: </div>
11092: </div>
1.41 asau 11093: <div class="appendix">
11094: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 11095: <a name="hardening"></a>Appendix B. Security hardening</h1></div></div></div>
1.1 dsieger 11096: <div class="toc">
11097: <p><b>Table of Contents</b></p>
1.100 leot 11098: <dl class="toc">
1.207 leot 11099: <dt><span class="sect1"><a href="#hardening.mechanisms">B.1. Mechanisms</a></span></dt>
11100: <dd><dl>
11101: <dt><span class="sect2"><a href="#hardening.mechanisms.enabled">B.1.1. Enabled by default</a></span></dt>
11102: <dt><span class="sect2"><a href="#hardening.mechanisms.disabled">B.1.2. Not enabled by default</a></span></dt>
11103: </dl></dd>
11104: <dt><span class="sect1"><a href="#hardening.caveats">B.2. Caveats</a></span></dt>
11105: <dd><dl>
11106: <dt><span class="sect2"><a href="#hardening.caveats.pie">B.2.1. Problems with PKGSRC_MKPIE</a></span></dt>
11107: <dt><span class="sect2"><a href="#hardening.caveats.fortify">B.2.2. Problems with PKGSRC_USE_FORTIFY</a></span></dt>
11108: <dt><span class="sect2"><a href="#hardening.caveats.relro">B.2.3. Problems with PKGSRC_USE_RELRO</a></span></dt>
11109: <dt><span class="sect2"><a href="#hardening.caveats.ssp">B.2.4. Problems with PKGSRC_USE_SSP</a></span></dt>
11110: </dl></dd>
11111: <dt><span class="sect1"><a href="#hardening.audit">B.3. Auditing the system</a></span></dt>
11112: <dd><dl>
11113: <dt><span class="sect2"><a href="#hardening.audit.pie">B.3.1. Checking for PIE</a></span></dt>
11114: <dt><span class="sect2"><a href="#hardening.audit.relropartial">B.3.2. Checking for partial RELRO</a></span></dt>
11115: <dt><span class="sect2"><a href="#hardening.audit.relrofull">B.3.3. Checking for full RELRO</a></span></dt>
11116: <dt><span class="sect2"><a href="#hardening.audit.ssp">B.3.4. Checking for SSP</a></span></dt>
11117: </dl></dd>
1.1 dsieger 11118: </dl>
11119: </div>
1.207 leot 11120: <p>
11121: A number of mechanisms are available in pkgsrc to improve the security of the
11122: resulting system. This page describes the mechanisms, and gives hints
11123: about detecting and fixing problems.
11124: </p>
11125: <p>
11126: Mechanisms can be enabled individually in
11127: <code class="filename">mk.conf</code>, and are
11128: individually described below.
11129: </p>
11130: <p>
11131: Typically, a feature will cause some programs to fail to build or work
11132: when first enabled. This can be due to latent problems in the
11133: program, and can be due to other reasons. After enough testing to
11134: have confidence that user problems will be quite rare, individual
11135: mechanisms will be enabled by default.
11136: </p>
11137: <p>
11138: For each mechanism, see the Caveats section below for an explanation
11139: of what might go wrong at compile time and at run time, and how to
11140: notice and address these problems.
11141: </p>
1.41 asau 11142: <div class="sect1">
1.1 dsieger 11143: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11144: <a name="hardening.mechanisms"></a>B.1. Mechanisms</h2></div></div></div>
11145: <div class="sect2">
11146: <div class="titlepage"><div><div><h3 class="title">
11147: <a name="hardening.mechanisms.enabled"></a>B.1.1. Enabled by default</h3></div></div></div>
11148: <div class="sect3">
11149: <div class="titlepage"><div><div><h4 class="title">
11150: <a name="hardening.mechanisms.enabled.fortify"></a>B.1.1.1. PKGSRC_USE_FORTIFY</h4></div></div></div>
11151: <p>
11152: This allows substitute wrappers to be used for some commonly used
11153: library functions that do not have built-in bounds checking - but
11154: could in some cases.
11155: </p>
11156: <p>
11157: Two mitigation levels are available:
11158: </p>
11159: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11160: <li class="listitem"><p>"weak" only enables checks at compile-time.</p></li>
11161: <li class="listitem"><p>"strong" enables checks at compile-time and runtime.</p></li>
11162: </ul></div>
11163: <p>
11164: "strong" has been enabled by default since pkgsrc-2017Q3.
11165: </p>
11166: </div>
11167: <div class="sect3">
11168: <div class="titlepage"><div><div><h4 class="title">
11169: <a name="hardening.mechanisms.enabled.ssp"></a>B.1.1.2. PKGSRC_USE_SSP</h4></div></div></div>
11170: <p>
11171: This enables a stack-smashing protection mitigation. It is done by adding a
11172: guard variable to functions with vulnerable objects. The guards are initialized
11173: when a function is entered and then checked when the function exits. The guard
11174: check will fail and the program forcibly exited if the variable was modified in
11175: the meantime. This can happen in case of buffer overflows or memory corruption,
11176: and therefore exposing these bugs.
11177: </p>
11178: <p>
11179: Different mitigation levels are available:
11180: </p>
11181: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11182: <li class="listitem"><p>"yes", which will only protect functions considered vulnerable
11183: by the compiler;</p></li>
11184: <li class="listitem"><p>"all", which will protect every function;</p></li>
11185: <li class="listitem"><p>"strong", the default, which will apply a better balance between the
11186: two settings above.</p></li>
11187: </ul></div>
11188: <p>
11189: This mitigation is supported by both GCC and clang. It may be supported in
11190: additional compilers, possibly under a different name. It is particularly useful
11191: for unsafe programming languages, such as C/C++.
11192: </p>
11193: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11194: <li class="listitem"><p>"yes" is enabled by default where known supported since pkgsrc-2017Q3.</p></li>
11195: <li class="listitem"><p>"strong" is enabled by default where known supported since pkgsrc-2021Q4.</p></li>
11196: </ul></div>
11197: <p>More details can be found here:</p>
11198: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11199: <a class="ulink" href="https://en.wikipedia.org/wiki/Buffer_overflow_protection" target="_top">Buffer overflow protection on Wikipedia</a>
11200: </p></li></ul></div>
11201: </div>
11202: <div class="sect3">
11203: <div class="titlepage"><div><div><h4 class="title">
11204: <a name="hardening.mechanisms.enabled.pie"></a>B.1.1.3. PKGSRC_MKPIE</h4></div></div></div>
11205: <p>
11206: This requests the creation of PIE (Position Independent Executables) for all
11207: executables. The PIE mechanism is normally used for shared libraries, so that
11208: they can be loaded at differing addresses at runtime. PIE itself does not have
11209: useful security properties; however, it is necessary to fully leverage some,
11210: such as ASLR. Some operating systems support Address Space Layout Randomization
11211: (ASLR), which causes different addresses to be used each time a program is run.
11212: This makes it more difficult for an attacker to guess addresses and thus makes
11213: exploits harder to construct. With PIE, ASLR can really be applied to the entire
11214: program, instead of the stack and heap only.
11215: </p>
11216: <p>
11217: PIE executables will only be built for toolchains that are known to support PIE.
11218: Currently, this means NetBSD on x86, ARM, SPARC64, m68k, and MIPS.
11219: </p>
11220: <p>
11221: <code class="varname">PKGSRC_MKPIE</code> was enabled by default after the pkgsrc-2021Q3 branch.
11222: </p>
1.1 dsieger 11223: </div>
1.210 gutterid 11224: <div class="sect3">
11225: <div class="titlepage"><div><div><h4 class="title">
1.219 nia 11226: <a name="hardening.mechanisms.enabled.relro"></a>B.1.1.4. PKGSRC_USE_RELRO</h4></div></div></div>
1.207 leot 11227: <p>
11228: This also makes the exploitation of some security vulnerabilities more
11229: difficult in some cases.
11230: </p>
11231: <p>Two different mitigation levels are available:</p>
11232: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11233: <li class="listitem"><p>
1.219 nia 11234: partial (the default): the ELF sections are reordered so that internal data sections
1.207 leot 11235: precede the program's own data sections, and non-PLT GOT is read-only;
11236: </p></li>
11237: <li class="listitem"><p>
11238: full: in addition to partial RELRO, every relocation is performed immediately
1.218 nia 11239: when starting the program, allowing the entire GOT to be read-only. This
11240: can greatly slow down startup of large programs.
1.207 leot 11241: </p></li>
11242: </ul></div>
11243: <p>
11244: This is currently supported by GCC. Many software distributions now enable this
1.220 nia 11245: feature by default, at the "partial" level.
1.207 leot 11246: </p>
11247: <p>
11248: More details can be found here:
11249: </p>
11250: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11251: <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>
11252: </p></li></ul></div>
1.1 dsieger 11253: </div>
1.219 nia 11254: </div>
11255: <div class="sect2">
11256: <div class="titlepage"><div><div><h3 class="title">
11257: <a name="hardening.mechanisms.disabled"></a>B.1.2. Not enabled by default</h3></div></div></div>
11258: <div class="sect3">
11259: <div class="titlepage"><div><div><h4 class="title">
11260: <a name="hardening.mechanisms.disabled.repro"></a>B.1.2.1. PKGSRC_MKREPRO</h4></div></div></div>
11261: <p>
11262: With this option, pkgsrc will try to build packages reproducibly. This allows
11263: packages built from the same tree and with the same options, to produce
11264: identical results bit by bit. This option should be combined with ASLR and
11265: <code class="varname">PKGSRC_MKPIE</code> to avoid predictable address offsets for
11266: attackers attempting to exploit security vulnerabilities.
11267: </p>
11268: <p>
11269: More details can be found here:
11270: </p>
11271: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11272: <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>
11273: </p></li></ul></div>
11274: <p>
11275: More work likely needs to be done before pkgsrc is fully reproducible.
11276: </p>
11277: </div>
1.207 leot 11278: <div class="sect3">
11279: <div class="titlepage"><div><div><h4 class="title">
1.219 nia 11280: <a name="hardening.mechanisms.disabled.stackcheck"></a>B.1.2.2. PKGSRC_USE_STACK_CHECK</h4></div></div></div>
1.207 leot 11281: <p>
11282: This uses <code class="literal">-fstack-check</code> with GCC for
11283: another stack protection mitigation.
11284: </p>
11285: <p>
11286: It asks the compiler to generate code verifying that it does not corrupt the
11287: stack. According to GCC's manual page, this is really only useful for
11288: multi-threaded programs.
11289: </p>
1.1 dsieger 11290: </div>
11291: </div>
11292: </div>
1.41 asau 11293: <div class="sect1">
1.1 dsieger 11294: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11295: <a name="hardening.caveats"></a>B.2. Caveats</h2></div></div></div>
11296: <div class="sect2">
11297: <div class="titlepage"><div><div><h3 class="title">
11298: <a name="hardening.caveats.pie"></a>B.2.1. Problems with PKGSRC_MKPIE</h3></div></div></div>
11299: <div class="sect3">
11300: <div class="titlepage"><div><div><h4 class="title">
11301: <a name="hardening.caveats.pie.build"></a>B.2.1.1. Packages failing to build</h4></div></div></div>
11302: <p>
11303: A number of packages may fail to build with this option enabled. The
11304: failures are often related to the absence of the <code class="literal">-fPIC</code>
11305: compilation flag when building libraries or executables (or ideally
11306: <code class="literal">-fPIE</code> in the latter case). This flag is added to the
11307: <code class="varname">CFLAGS</code> already, but requires the package to
11308: actually support it.
11309: </p>
11310: <div class="sect4">
11311: <div class="titlepage"><div><div><h5 class="title">
11312: <a name="hardening.caveats.pie.build.fix"></a>B.2.1.1.1. How to fix</h5></div></div></div>
11313: <p>
11314: These instructions are meant as a reference only; they likely need to be adapted
11315: for many packages individually.
11316: </p>
11317: <p>
11318: For packages using <code class="filename">Makefiles</code>:
11319: </p>
11320: <pre class="programlisting">
11321: MAKE_FLAGS+= CFLAGS=${CFLAGS:Q}
11322: MAKE_FLAGS+= LDFLAGS=${LDFLAGS:Q}
11323: </pre>
11324: <p>
11325: For packages using <code class="filename">Imakefiles</code>:
11326: </p>
11327: <pre class="programlisting">
11328: MAKE_FLAGS+= CCOPTIONS=${CFLAGS:Q}
11329: MAKE_FLAGS+= LOCAL_LDFLAGS=${LDFLAGS:Q}
11330: </pre>
11331: </div>
11332: </div>
11333: <div class="sect3">
11334: <div class="titlepage"><div><div><h4 class="title">
11335: <a name="hardening.caveats.pie.crash"></a>B.2.1.2. Run-time crashes</h4></div></div></div>
11336: <p>
11337: Some programs may fail to run, or crash at random times once built as PIE. Two
11338: scenarios are essentially possible. This is nearly always due to a bug in
11339: the program being exposed due to ASLR.
11340: </p>
11341: </div>
11342: <div class="sect3">
11343: <div class="titlepage"><div><div><h4 class="title">
11344: <a name="hardening.caveats.pie.disable"></a>B.2.1.3. Disabling PKGSRC_MKPIE on a per-package basis</h4></div></div></div>
11345: <p>
11346: Ideally, packages should be fixed for compatibility with MKPIE.
11347: However, in some cases this is very difficult, due to complex build systems,
11348: packages using non-standard toolchains, or programming languages with odd
11349: bootstrapping mechanisms.
11350: </p>
11351: <p>
11352: To disable <code class="varname">PKGSRC_MKPIE</code> on a per-package basis, set
11353: <code class="varname">MKPIE_SUPPORTED= no</code> in the package's Makefile before
11354: <code class="filename">bsd.prefs.mk</code> is included.
11355: </p>
11356: </div>
11357: </div>
11358: <div class="sect2">
11359: <div class="titlepage"><div><div><h3 class="title">
11360: <a name="hardening.caveats.fortify"></a>B.2.2. Problems with PKGSRC_USE_FORTIFY</h3></div></div></div>
11361: <div class="sect3">
11362: <div class="titlepage"><div><div><h4 class="title">
11363: <a name="hardening.caveats.fortify.build"></a>B.2.2.1. Packages failing to build</h4></div></div></div>
11364: <p>
11365: This feature makes use of pre-processing directives to look for hardened,
11366: alternative implementations of essential library calls. Some programs may fail
11367: to build as a result; this usually happens for those trying too hard to be
11368: portable, or otherwise abusing definitions in the standard library.
11369: </p>
11370: </div>
11371: <div class="sect3">
11372: <div class="titlepage"><div><div><h4 class="title">
11373: <a name="hardening.caveats.fortify.crash"></a>B.2.2.2. Run-time crashes</h4></div></div></div>
11374: <p>
11375: This feature may cause some programs to crash, usually indicating an
11376: actual bug in the program. The fix will typically involve patching the
11377: original program's source code.
11378: </p>
11379: </div>
11380: <div class="sect3">
11381: <div class="titlepage"><div><div><h4 class="title">
11382: <a name="hardening.caveats.fortify.opt"></a>B.2.2.3. Optimization is required</h4></div></div></div>
11383: <p>
11384: At least in the case of GCC, FORTIFY will only be applied if optimization is
11385: applied while compiling. This means that the <code class="varname">CFLAGS</code> should
11386: also contain <code class="literal">-O</code>, <code class="literal">-O2</code> or another
11387: optimization level. This cannot easily be applied globally, as some packages
11388: may require specific optimization levels.
11389: </p>
11390: </div>
11391: <div class="sect3">
11392: <div class="titlepage"><div><div><h4 class="title">
11393: <a name="hardening.caveats.fortify.disable"></a>B.2.2.4. Disabling FORTIFY on a per-package basis</h4></div></div></div>
11394: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11395: <h3 class="title">Note</h3>
11396: <p>FORTIFY should not be disabled to work around runtime crashes in
11397: the program! This is a very bad idea and will expose you to security
11398: vulnerabilities.
11399: </p>
11400: </div>
11401: <p>
11402: To disable FORTIFY on a per-package basis, set the following
11403: in the package's <code class="filename">Makefile</code>
11404: before <code class="filename">bsd.prefs.mk</code> is included:
11405: </p>
11406: <pre class="programlisting">
11407: FORTIFY_SUPPORTED= no
11408: </pre>
11409: </div>
11410: </div>
11411: <div class="sect2">
11412: <div class="titlepage"><div><div><h3 class="title">
11413: <a name="hardening.caveats.relro"></a>B.2.3. Problems with PKGSRC_USE_RELRO</h3></div></div></div>
11414: <div class="sect3">
11415: <div class="titlepage"><div><div><h4 class="title">
11416: <a name="hardening.caveats.relro.performance"></a>B.2.3.1. Performance impact</h4></div></div></div>
11417: <p>
11418: For better protection, full RELRO requires every symbol to be resolved when the
11419: program starts, rather than simply when required at run-time. This will have
11420: more impact on programs using a lot of symbols, or linked to libraries exposing
11421: a lot of symbols. Therefore, daemons or programs otherwise running in
11422: background are affected only when started. Programs loading plug-ins at
11423: run-time are affected when loading the plug-ins.
11424: </p>
11425: <p>
11426: The impact is not expected to be noticeable on modern hardware, except in some
11427: cases for big programs.
11428: </p>
11429: </div>
11430: <div class="sect3">
11431: <div class="titlepage"><div><div><h4 class="title">
11432: <a name="hardening.caveats.relro.crash"></a>B.2.3.2. Run-time crashes</h4></div></div></div>
11433: <p>
11434: Some programs handle plug-ins and dependencies in a way that conflicts with
11435: RELRO: for instance, with an initialization routine listing any other plug-in
11436: required. With full RELRO, the missing symbols are resolved before the
11437: initialization routine can run, and the dynamic loader will not be able to find
11438: them directly and abort as a result. Unfortunately, this is how Xorg loads its
11439: drivers. Partial RELRO can be applied instead in this case.
11440: </p>
11441: </div>
11442: <div class="sect3">
11443: <div class="titlepage"><div><div><h4 class="title">
11444: <a name="hardening.caveats.relro.disable"></a>B.2.3.3. Disabling RELRO on a per-package basis</h4></div></div></div>
11445: <p>
11446: To disable RELRO on a per-package basis, set the following
11447: in the package's <code class="filename">Makefile</code>
11448: before <code class="filename">bsd.prefs.mk</code> is included:
11449: </p>
11450: <pre class="programlisting">
11451: RELRO_SUPPORTED= no
11452: </pre>
1.209 nia 11453: <p>
11454: It is also possible to at most enable partial RELRO, by
11455: setting <code class="varname">RELRO_SUPPORTED</code> to <code class="literal">partial</code>.
11456: </p>
1.207 leot 11457: </div>
11458: </div>
11459: <div class="sect2">
11460: <div class="titlepage"><div><div><h3 class="title">
11461: <a name="hardening.caveats.ssp"></a>B.2.4. Problems with PKGSRC_USE_SSP</h3></div></div></div>
11462: <div class="sect3">
11463: <div class="titlepage"><div><div><h4 class="title">
11464: <a name="hardening.caveats.ssp.build"></a>B.2.4.1. Packages failing to build</h4></div></div></div>
11465: <p>
11466: The stack-smashing protection provided by this option does not work for some
11467: programs. The most common situation in which this happens is when the program
11468: allocates variables on the stack, with the size determined at run-time.
11469: </p>
11470: </div>
11471: <div class="sect3">
11472: <div class="titlepage"><div><div><h4 class="title">
11473: <a name="hardening.caveats.ssp.crash"></a>B.2.4.2. Run-time crashes</h4></div></div></div>
11474: <p>
11475: Again, this feature may cause some programs to crash via a
11476: <code class="varname">SIGABRT</code>, usually indicating an actual bug in the program.
11477: </p>
11478: <p>
11479: On NetBSD <code class="varname">LOG_CRIT</code> level syslog
11480: messages are sent and - by default -
11481: appended to <code class="filename">/var/log/messages</code>, e.g.:
11482: </p>
11483: <pre class="programlisting">
11484: Jan 6 15:42:51 hostname -: hostname program - - - buffer overflow detected; terminated
11485: </pre>
11486: <p>
11487: (where <code class="literal">hostname</code> is the hostname(1) and
11488: <code class="literal">program</code> is the basename(1) of the program crashed).
11489: </p>
11490: <p>
11491: Patching the original program is then required.
11492: </p>
11493: <p>
11494: Rebuilding the package via:
11495: </p>
11496: <pre class="programlisting">
11497: <strong class="userinput"><code>% env CFLAGS=-g INSTALL_UNSTRIPPED=yes make replace</code></strong>
11498: </pre>
11499: <p>
11500: and inspecting the backtrace of the coredump via the debugger
11501: should point out the problematic call by inspecting the frame
11502: calling the _chk() (SSP) function.
11503: </p>
11504: </div>
11505: <div class="sect3">
11506: <div class="titlepage"><div><div><h4 class="title">
11507: <a name="hardening.caveats.ssp.performance"></a>B.2.4.3. Performance impact</h4></div></div></div>
11508: <p>
11509: The compiler emits extra code when using this feature: a check for buffer
11510: overflows is performed when entering and exiting functions, requiring an extra
11511: variable on the stack. The level of protection can otherwise be adjusted to
11512: affect only those functions considered more sensitive by the compiler (with
11513: -fstack-protector instead of -fstack-protector-all).
11514: </p>
11515: <p>
11516: The impact is not expected to be noticeable on modern hardware. However,
11517: programs with a hard requirement to run at the fastest possible speed should
11518: avoid using this feature, or using libraries built with this feature.
11519: </p>
11520: </div>
11521: <div class="sect3">
11522: <div class="titlepage"><div><div><h4 class="title">
11523: <a name="hardening.caveats.ssp.disable"></a>B.2.4.4. Disabling SSP on a per-package basis</h4></div></div></div>
11524: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11525: <h3 class="title">Note</h3>
11526: <p>SSP should not be disabled to work around runtime crashes in
11527: the program! This is a very bad idea and will expose you to security
11528: vulnerabilities.</p>
11529: </div>
11530: <p>
11531: To disable SSP on a per-package basis, set the following
11532: in the package's <code class="filename">Makefile</code>
11533: before <code class="filename">bsd.prefs.mk</code> is included:
11534: </p>
11535: <pre class="programlisting">
11536: SSP_SUPPORTED= no
11537: </pre>
11538: </div>
11539: </div>
11540: </div>
11541: <div class="sect1">
11542: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11543: <a name="hardening.audit"></a>B.3. Auditing the system</h2></div></div></div>
11544: <p>
11545: The illusion of security is worse than having no security at all. This section
11546: lists a number of ways to ensure the security features requested are actually
11547: effective.
11548: </p>
11549: <p>
11550: These instructions were obtained and tested on a system derived from NetBSD 7
11551: (amd64). YMMV.
11552: </p>
11553: <div class="sect2">
11554: <div class="titlepage"><div><div><h3 class="title">
11555: <a name="hardening.audit.pie"></a>B.3.1. Checking for PIE</h3></div></div></div>
11556: <p>
11557: The ELF executable type in use changes for binaries built as PIE; without:
11558: </p>
11559: <pre class="programlisting">
11560: <strong class="userinput"><code>$ file /path/to/bin/ary</code></strong>
11561: /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
11562: </pre>
11563: <p>as opposed to the following binary, built as PIE:</p>
11564: <pre class="programlisting">
11565: <strong class="userinput"><code>$ file /path/to/pie/bin/ary</code></strong>
11566: /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
11567: </pre>
11568: <p>
11569: The latter result is then what is expected.
11570: </p>
11571: </div>
11572: <div class="sect2">
11573: <div class="titlepage"><div><div><h3 class="title">
11574: <a name="hardening.audit.relropartial"></a>B.3.2. Checking for partial RELRO</h3></div></div></div>
11575: <p>
11576: The following command should list a section called RELRO:
11577: </p>
11578: <pre class="programlisting">
11579: <strong class="userinput"><code>$ objdump -p /path/to/bin/ary</code></strong>
11580:
11581: /path/to/bin/ary: file format elf64-x86-64
11582:
11583: Program Header:
11584: [...]
11585: RELRO off 0x0000000000000d78 vaddr 0x0000000000600d78 paddr 0x0000000000600d78 align 2**0
11586: </pre>
11587: <p>
11588: This check is now performed automatically if
11589: <code class="varname">PKG_DEVELOPER</code> is set and RELRO is enabled.
11590: </p>
11591: </div>
11592: <div class="sect2">
11593: <div class="titlepage"><div><div><h3 class="title">
11594: <a name="hardening.audit.relrofull"></a>B.3.3. Checking for full RELRO</h3></div></div></div>
11595: <p>
11596: The dynamic loader will apply RELRO immediately when detecting the presence of
11597: the <code class="varname">BIND_NOW</code> flag:
11598: </p>
11599: <pre class="programlisting">
11600: <strong class="userinput"><code>$ objdump -x /path/to/bin/ary</code></strong>
11601:
11602: /path/to/bin/ary: file format elf64-x86-64
11603:
11604: Dynamic Section:
11605: [...]
11606: BIND_NOW 0x0000000000000000
11607: </pre>
11608: <p>
11609: This has to be combined with partial RELRO (see above) to be fully efficient.
11610: </p>
11611: <p>
11612: This check is now performed automatically (where supported) if
11613: <code class="varname">PKG_DEVELOPER</code> is set.
11614: </p>
11615: </div>
11616: <div class="sect2">
11617: <div class="titlepage"><div><div><h3 class="title">
11618: <a name="hardening.audit.ssp"></a>B.3.4. Checking for SSP</h3></div></div></div>
1.208 nia 11619: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11620: <h3 class="title">Note</h3>
11621: <p>
11622: Checking for SSP using this method only works where the operating system
11623: uses <code class="literal">libssp</code>. <code class="literal">libssp</code> is not used
11624: on recent NetBSD/FreeBSD/Linux versions.
11625: </p>
11626: </div>
1.207 leot 11627: <p>
11628: Building objects, binaries and libraries with SSP will affect the presence of
11629: additional symbols in the resulting file:
11630: </p>
11631: <pre class="programlisting">
11632: <strong class="userinput"><code>$ nm /path/to/bin/ary</code></strong>
11633: [...]
11634: U __stack_chk_fail
11635: 0000000000600ea0 B __stack_chk_guard
11636: </pre>
11637: <p>
11638: This is an indicator that the program was indeed built with support for SSP.
11639: </p>
11640: <p>
11641: This check is now performed automatically (where supported) if
11642: <code class="varname">PKG_DEVELOPER</code> is set and SSP is enabled.
11643: </p>
11644: </div>
11645: </div>
11646: </div>
11647: <div class="appendix">
11648: <div class="titlepage"><div><div><h1 class="title">
11649: <a name="logs"></a>Appendix C. Build logs</h1></div></div></div>
11650: <div class="toc">
11651: <p><b>Table of Contents</b></p>
11652: <dl class="toc">
11653: <dt><span class="sect1"><a href="#logs.building">C.1. Building figlet</a></span></dt>
11654: <dt><span class="sect1"><a href="#logs.package">C.2. Packaging figlet</a></span></dt>
11655: </dl>
11656: </div>
11657: <div class="sect1">
11658: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11659: <a name="logs.building"></a>C.1. Building figlet</h2></div></div></div>
11660: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
11661: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11662: => figlet221.tar.gz doesn't seem to exist on this system.
11663: => Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
11664: => [172219 bytes]
11665: Connected to ftp.plig.net.
11666: 220 ftp.plig.org NcFTPd Server (licensed copy) ready.
11667: 331 Guest login ok, send your complete e-mail address as password.
11668: 230-You are user #5 of 500 simultaneous users allowed.
11669: 230-
11670: 230- ___ _ _ _
11671: 230- | _| |_ ___ ___| |_|___ ___ ___ ___
11672: 230- | _| _| . |_| . | | | . |_| . | _| . |
11673: 230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
11674: 230- |_| |_| |___| |___|
11675: 230-
11676: 230-** Welcome to ftp.plig.org **
11677: 230-
11678: 230-Please note that all transfers from this FTP site are logged. If you
11679: 230-do not like this, please disconnect now.
11680: 230-
11681: 230-This archive is available via
11682: 230-
11683: 230-HTTP: http://ftp.plig.org/
11684: 230-FTP: ftp://ftp.plig.org/ (max 500 connections)
11685: 230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
11686: 230-
11687: 230-Please email comments, bug reports and requests for packages to be
11688: 230-mirrored to ftp-admin@plig.org.
11689: 230-
11690: 230-
11691: 230 Logged in anonymously.
11692: Remote system type is UNIX.
11693: Using binary mode to transfer files.
11694: 200 Type okay.
11695: 250 "/pub" is new cwd.
11696: 250-"/pub/figlet" is new cwd.
11697: 250-
11698: 250-Welcome to the figlet archive at ftp.figlet.org
11699: 250-
11700: 250- ftp://ftp.figlet.org/pub/figlet/
11701: 250-
11702: 250-The official FIGlet web page is:
11703: 250- http://www.figlet.org/
11704: 250-
11705: 250-If you have questions, please mailto:info@figlet.org. If you want to
11706: 250-contribute a font or something else, you can email us.
11707: 250
11708: 250 "/pub/figlet/program" is new cwd.
11709: 250 "/pub/figlet/program/unix" is new cwd.
11710: local: figlet221.tar.gz remote: figlet221.tar.gz
11711: 502 Unimplemented command.
11712: 227 Entering Passive Mode (195,40,6,41,246,104)
11713: 150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
11714: 38% |************** | 65800 64.16 KB/s 00:01 ETA
11715: 226 Transfer completed.
11716: 172219 bytes received in 00:02 (75.99 KB/s)
11717: 221 Goodbye.
11718: => Checksum OK for figlet221.tar.gz.
11719: ===> Extracting for figlet-2.2.1nb2
11720: ===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
11721: ===> Patching for figlet-2.2.1nb2
11722: ===> Applying pkgsrc patches for figlet-2.2.1nb2
11723: ===> Overriding tools for figlet-2.2.1nb2
11724: ===> Creating toolchain wrappers for figlet-2.2.1nb2
11725: ===> Configuring for figlet-2.2.1nb2
11726: ===> Building for figlet-2.2.1nb2
11727: gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
11728: chmod a+x figlet
11729: gcc -O2 -o chkfont chkfont.c
11730: => Unwrapping files-to-be-installed.
11731: <code class="prompt">#</code>
11732: <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
11733: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11734: ===> Installing for figlet-2.2.1nb2
11735: install -d -o root -g wheel -m 755 /usr/pkg/bin
11736: install -d -o root -g wheel -m 755 /usr/pkg/man/man6
11737: mkdir -p /usr/pkg/share/figlet
11738: cp figlet /usr/pkg/bin
11739: cp chkfont /usr/pkg/bin
11740: chmod 555 figlist showfigfonts
11741: cp figlist /usr/pkg/bin
11742: cp showfigfonts /usr/pkg/bin
11743: cp fonts/*.flf /usr/pkg/share/figlet
11744: cp fonts/*.flc /usr/pkg/share/figlet
11745: cp figlet.6 /usr/pkg/man/man6
11746: ===> Registering installation for figlet-2.2.1nb2
11747: <code class="prompt">#</code></pre>
11748: </div>
11749: <div class="sect1">
11750: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11751: <a name="logs.package"></a>C.2. Packaging figlet</h2></div></div></div>
11752: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
11753: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11754: ===> Packaging figlet-2.2.1nb2
11755: ===> Building binary package for figlet-2.2.1nb2
11756: Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
11757: Using SrcDir value of /usr/pkg
11758: Registering depends:.
11759: <code class="prompt">#</code></pre>
11760: </div>
11761: </div>
11762: <div class="appendix">
11763: <div class="titlepage"><div><div><h1 class="title">
11764: <a name="ftp-layout"></a>Appendix D. Directory layout of the pkgsrc FTP server</h1></div></div></div>
11765: <div class="toc">
11766: <p><b>Table of Contents</b></p>
11767: <dl class="toc">
11768: <dt><span class="sect1"><a href="#ftp-distfiles">D.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
11769: <dt><span class="sect1"><a href="#ftp-misc">D.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
11770: <dt><span class="sect1"><a href="#ftp-packages">D.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
11771: <dt><span class="sect1"><a href="#ftp-reports">D.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
11772: <dt><span class="sect1"><a href="#ftp-source">D.5. <code class="filename">current</code>,
11773: <code class="filename">stable</code>,
11774: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
11775: source packages</a></span></dt>
11776: </dl>
11777: </div>
11778: <p>As in other big projects, the directory layout of pkgsrc
11779: is quite complex for newbies. This chapter explains where you
11780: find things on the FTP server. The base directory on
11781: <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>.
11782: On other servers it may be different, but inside this directory,
11783: everything should look the same, no matter on which server you
11784: are. This directory contains some subdirectories, which are
11785: explained below.</p>
11786: <div class="sect1">
11787: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11788: <a name="ftp-distfiles"></a>D.1. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div>
11789: <p>The directory <code class="filename">distfiles</code> contains lots
11790: of archive files from all pkgsrc packages, which are mirrored
11791: here. The subdirectories are called after their package names
11792: and are used when the distributed files have names that don't
11793: explicitly contain a version number or are otherwise too generic
11794: (for example <code class="filename">release.tar.gz</code>).</p>
11795: </div>
11796: <div class="sect1">
11797: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11798: <a name="ftp-misc"></a>D.2. <code class="filename">misc</code>: Miscellaneous things</h2></div></div></div>
11799: <p>This directory contains things that individual pkgsrc
11800: developers find worth publishing.</p>
11801: </div>
11802: <div class="sect1">
11803: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11804: <a name="ftp-packages"></a>D.3. <code class="filename">packages</code>: Binary packages</h2></div></div></div>
11805: <p>This directory contains binary packages for the various
11806: platforms that are supported by pkgsrc.
11807: 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>
11808: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11809: <li class="listitem"><p><code class="varname">OPSYS</code> is the name of the
11810: operating system for which the packages have been built. The
11811: name is taken from the output of the <span class="command"><strong>uname</strong></span>
11812: command, so it may differ from the one you are used to
11813: hear.</p></li>
11814: <li class="listitem"><p><code class="varname">ARCH</code> is the hardware
11815: architecture of the platform for which the packages have been
11816: built. It also includes the <code class="varname">ABI</code> (Application
11817: Binary Interface) for platforms that have several of
11818: them.</p></li>
11819: <li class="listitem"><p><code class="varname">OSVERSION</code> is the version of
11820: the operating system. For version numbers that change often (for
11821: example NetBSD-current), the often-changing part should be
11822: replaced with an <code class="literal">x</code>, for example
11823: <code class="literal">4.99.x</code>.</p></li>
11824: <li class="listitem"><p><code class="varname">TAG</code> is either
11825: <code class="literal">20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11826: for a stable branch, or <code class="literal">head</code> for packages
11827: built from the HEAD branch. The latter should only be used when
11828: the packages are updated on a regular basis. Otherwise the date
11829: from checking out pkgsrc should be appended, for example
11830: <code class="literal">head_20071015</code>.</p></li>
11831: </ul></div>
11832: <p>The rationale for exactly this scheme is that the pkgsrc users looking for binary packages
11833: can quickly click through the directories on the
11834: server and find the best binary packages for their machines. Since they
11835: usually know the operating system and the hardware architecture, OPSYS
11836: and ARCH are placed first. After these choices, they can select the
11837: best combination of OSVERSION and TAG together, since it is usually the
11838: case that packages stay compatible between different version of the
11839: operating system.</p>
11840: <p>In each of these directories, there is a
11841: whole binary packages collection for a specific platform. It has a directory called
11842: <code class="filename">All</code> which contains all binary packages.
11843: Besides that, there are various category directories that
11844: contain symbolic links to the real binary packages.</p>
11845: </div>
11846: <div class="sect1">
11847: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11848: <a name="ftp-reports"></a>D.4. <code class="filename">reports</code>: Bulk build reports</h2></div></div></div>
1.8 rillig 11849: <p>Here are the reports from bulk builds, for those who want
11850: to fix packages that didn't build on some of the platforms. The
1.207 leot 11851: 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.8 rillig 11852: </div>
1.41 asau 11853: <div class="sect1">
1.8 rillig 11854: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11855: <a name="ftp-source"></a>D.5. <code class="filename">current</code>,
1.148 leot 11856: <code class="filename">stable</code>,
1.22 jakllsch 11857: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 11858: source packages</h2></div></div></div>
1.23 wiz 11859: <p>These directories contain the <span class="quote">“<span class="quote">real</span>”</span> pkgsrc,
1.1 dsieger 11860: that is the files that define how to create binary packages from
11861: source archives.</p>
1.149 leot 11862: <p>Each of the <code class="filename">current</code>,
11863: <code class="filename">stable</code> and
11864: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11865: directories share the same structure. They each contain a
11866: <code class="filename">pkgsrc</code> directory and
11867: <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> file.</p>
1.1 dsieger 11868: <p>The directory <code class="filename">pkgsrc</code> contains a
11869: snapshot of the CVS repository, which is updated regularly. The
1.149 leot 11870: file <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> contains the same
11871: as the directory, ready to be downloaded as a whole.</p>
11872: <p>The <code class="filename">current</code> directory contains files
11873: related to the HEAD branch of the CVS repository.
11874: In this directory there is an additional file called
11875: <code class="filename">pkgsrc-readmes.tar.{bz,gz,xz}</code> that contains
11876: all pkgsrc <code class="filename">README</code>s with information about
11877: categories and packages.
11878: </p>
11879: <p>The <code class="filename">stable</code> directory is a symlink to
11880: the latest
11881: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11882: </p>
11883: <p>The
11884: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11885: directories contain files related to the
11886: <code class="filename">-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11887: stable branch of the CVS repository. In these directories there is
11888: an additional file called
11889: <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.1 dsieger 11890: which contains the state of pkgsrc when it was branched.</p>
11891: </div>
11892: </div>
1.41 asau 11893: <div class="appendix">
11894: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 11895: <a name="help-topics"></a>Appendix E. Help topics</h1></div></div></div>
1.154 rillig 11896: <p>
11897: The following list contains all help topics that are available
11898: when running <span class="command"><strong>bmake help topic=:index</strong></span>.
11899: </p>
1.156 leot 11900: <table border="0" summary="Simple list" class="simplelist">
11901: <tr>
11902: <td>#!</td>
11903: <td>-lintl</td>
11904: </tr>
11905: <tr>
1.205 wiz 11906: <td>32bit</td>
1.156 leot 11907: <td>64bit</td>
1.205 wiz 11908: </tr>
11909: <tr>
1.156 leot 11910: <td>ABI</td>
1.205 wiz 11911: <td>ACCEPTABLE_LICENSES</td>
1.156 leot 11912: </tr>
11913: <tr>
11914: <td>ACROREAD_FONTPATH</td>
1.205 wiz 11915: <td>ADDITIONAL</td>
1.156 leot 11916: </tr>
11917: <tr>
11918: <td>AFAIK</td>
1.205 wiz 11919: <td>AIX</td>
1.156 leot 11920: </tr>
11921: <tr>
1.243 gutterid 11922: <td>ALLOW_NEWER_COMPILER</td>
1.156 leot 11923: <td>ALLOW_VULNERABLE_PACKAGES</td>
11924: </tr>
11925: <tr>
1.243 gutterid 11926: <td>ALL_ENV</td>
1.249 gutterid 11927: <td>ALTERNATIVES_SRC</td>
1.246 leot 11928: </tr>
11929: <tr>
11930: <td>AMANDA_TMP</td>
1.249 gutterid 11931: <td>AMANDA_USER</td>
1.241 rillig 11932: </tr>
11933: <tr>
1.246 leot 11934: <td>AMANDA_VAR</td>
1.249 gutterid 11935: <td>APACHE_GROUP</td>
1.238 wiz 11936: </tr>
11937: <tr>
1.246 leot 11938: <td>APACHE_MODULE_NAME</td>
1.249 gutterid 11939: <td>APACHE_MODULE_SRC</td>
1.233 wiz 11940: </tr>
11941: <tr>
1.246 leot 11942: <td>APACHE_MODULE_SRCDIR</td>
1.249 gutterid 11943: <td>APACHE_PKG_PREFIX</td>
1.227 wiz 11944: </tr>
11945: <tr>
1.246 leot 11946: <td>APACHE_SUEXEC_CONFIGURE_ARGS</td>
1.249 gutterid 11947: <td>APACHE_SUEXEC_DOCROOT</td>
1.223 nia 11948: </tr>
11949: <tr>
1.246 leot 11950: <td>APACHE_USER</td>
1.249 gutterid 11951: <td>APPEND_ABI</td>
1.217 rillig 11952: </tr>
11953: <tr>
1.246 leot 11954: <td>APPEND_ELF</td>
1.249 gutterid 11955: <td>ARLA_CACHE</td>
1.214 leot 11956: </tr>
11957: <tr>
1.246 leot 11958: <td>AUDIT_PACKAGES_FLAGS</td>
1.249 gutterid 11959: <td>AUTOCONF_REQD</td>
1.212 wiz 11960: </tr>
11961: <tr>
1.246 leot 11962: <td>AUTOMAKE_OVERRIDE</td>
1.249 gutterid 11963: <td>AUTOMAKE_REQD</td>
1.197 leot 11964: </tr>
11965: <tr>
1.246 leot 11966: <td>AUTO_MKDIRS</td>
1.249 gutterid 11967: <td>BDB185_DEFAULT</td>
1.177 leot 11968: </tr>
11969: <tr>
1.246 leot 11970: <td>BDBBASE</td>
1.249 gutterid 11971: <td>BDB_ACCEPTED</td>
1.161 leot 11972: </tr>
11973: <tr>
1.246 leot 11974: <td>BDB_DEFAULT</td>
1.249 gutterid 11975: <td>BDB_LIBS</td>
1.159 rillig 11976: </tr>
11977: <tr>
1.246 leot 11978: <td>BDB_TYPE</td>
1.249 gutterid 11979: <td>BINCIMAP_GROUP</td>
1.156 leot 11980: </tr>
11981: <tr>
1.246 leot 11982: <td>BINCIMAP_USER</td>
1.249 gutterid 11983: <td>BIND_DIR</td>
1.156 leot 11984: </tr>
11985: <tr>
1.246 leot 11986: <td>BIND_GROUP</td>
1.249 gutterid 11987: <td>BIND_USER</td>
1.156 leot 11988: </tr>
11989: <tr>
1.246 leot 11990: <td>BINOWN</td>
1.249 gutterid 11991: <td>BINPKG_SITES</td>
1.156 leot 11992: </tr>
11993: <tr>
1.246 leot 11994: <td>BIN_INSTALL_FLAGS</td>
1.249 gutterid 11995: <td>BISON_PKGDATADIR</td>
1.156 leot 11996: </tr>
11997: <tr>
1.246 leot 11998: <td>BLAS</td>
1.249 gutterid 11999: <td>BLAS_ACCEPTED</td>
1.156 leot 12000: </tr>
12001: <tr>
1.246 leot 12002: <td>BLAS_C_INTERFACE</td>
1.249 gutterid 12003: <td>BLAS_INCLUDES</td>
1.156 leot 12004: </tr>
12005: <tr>
1.246 leot 12006: <td>BLAS_INDEX64</td>
1.249 gutterid 12007: <td>BLAS_LIBS</td>
1.156 leot 12008: </tr>
12009: <tr>
1.246 leot 12010: <td>BLAS_PC</td>
1.249 gutterid 12011: <td>BLAS_TYPE</td>
1.156 leot 12012: </tr>
12013: <tr>
1.246 leot 12014: <td>BOOTSTRAP_DEPENDS</td>
1.249 gutterid 12015: <td>BROKEN</td>
1.156 leot 12016: </tr>
12017: <tr>
1.246 leot 12018: <td>BROKEN_EXCEPT_ON_PLATFORM</td>
1.249 gutterid 12019: <td>BROKEN_ON_PLATFORM</td>
1.198 leot 12020: </tr>
12021: <tr>
1.246 leot 12022: <td>BSDSRCDIR</td>
1.249 gutterid 12023: <td>BSDXSRCDIR</td>
1.229 gutterid 12024: </tr>
12025: <tr>
1.246 leot 12026: <td>BSD_MAKE_ENV</td>
1.249 gutterid 12027: <td>BUILDLINK_AUTO_DIRS</td>
1.156 leot 12028: </tr>
12029: <tr>
1.246 leot 12030: <td>BUILDLINK_AUTO_VARS</td>
1.249 gutterid 12031: <td>BUILDLINK_CFLAGS</td>
1.156 leot 12032: </tr>
12033: <tr>
1.246 leot 12034: <td>BUILDLINK_CONTENTS_FILTER</td>
1.241 rillig 12035: <td>BUILDLINK_CPPFLAGS</td>
1.156 leot 12036: </tr>
12037: <tr>
1.243 gutterid 12038: <td>BUILDLINK_FILES</td>
1.216 gutterid 12039: <td>BUILDLINK_FILES_CMD</td>
1.205 wiz 12040: </tr>
12041: <tr>
1.243 gutterid 12042: <td>BUILDLINK_FNAME_TRANSFORM</td>
1.216 gutterid 12043: <td>BUILDLINK_LDFLAGS</td>
1.156 leot 12044: </tr>
12045: <tr>
1.243 gutterid 12046: <td>BUILDLINK_LIBS</td>
1.216 gutterid 12047: <td>BUILDLINK_OPSYS_SUPPORT_PTHREAD</td>
1.156 leot 12048: </tr>
12049: <tr>
1.243 gutterid 12050: <td>BUILDLINK_PKGNAME</td>
1.216 gutterid 12051: <td>BUILDLINK_PREFIX</td>
1.156 leot 12052: </tr>
12053: <tr>
1.243 gutterid 12054: <td>BUILDLINK_RPATHDIRS</td>
1.216 gutterid 12055: <td>BUILDLINK_TREE</td>
1.156 leot 12056: </tr>
12057: <tr>
1.243 gutterid 12058: <td>BUILD_DEFS</td>
1.216 gutterid 12059: <td>BUILD_DEFS_EFFECTS</td>
1.156 leot 12060: </tr>
12061: <tr>
1.243 gutterid 12062: <td>BUILD_DEPENDS</td>
1.216 gutterid 12063: <td>BUILD_DIRS</td>
1.156 leot 12064: </tr>
12065: <tr>
1.243 gutterid 12066: <td>BUILD_ENV_SHELL</td>
1.216 gutterid 12067: <td>BUILD_MAKE_CMD</td>
1.156 leot 12068: </tr>
12069: <tr>
1.243 gutterid 12070: <td>BUILD_MAKE_FLAGS</td>
1.216 gutterid 12071: <td>BUILD_TARGET</td>
1.156 leot 12072: </tr>
12073: <tr>
1.243 gutterid 12074: <td>BUILTIN_FIND_FILES</td>
1.216 gutterid 12075: <td>BUILTIN_FIND_FILES_VAR</td>
1.156 leot 12076: </tr>
12077: <tr>
1.243 gutterid 12078: <td>BUILTIN_FIND_GREP</td>
1.216 gutterid 12079: <td>BUILTIN_FIND_HEADERS</td>
1.156 leot 12080: </tr>
12081: <tr>
1.243 gutterid 12082: <td>BUILTIN_FIND_HEADERS_VAR</td>
1.216 gutterid 12083: <td>BUILTIN_FIND_PKGCONFIG</td>
1.156 leot 12084: </tr>
12085: <tr>
1.243 gutterid 12086: <td>BUILTIN_FIND_PKGCONFIG_VAR</td>
1.216 gutterid 12087: <td>BUILTIN_PKG</td>
1.195 gutterid 12088: </tr>
12089: <tr>
1.243 gutterid 12090: <td>BUILTIN_TEST_CURSES_DEFINES</td>
1.216 gutterid 12091: <td>BUILTIN_TEST_CURSES_FUNCS</td>
1.156 leot 12092: </tr>
12093: <tr>
1.243 gutterid 12094: <td>BUILTIN_VERSION_SCRIPT</td>
1.216 gutterid 12095: <td>BUILTIN_X11_TYPE</td>
1.156 leot 12096: </tr>
12097: <tr>
1.243 gutterid 12098: <td>BUILTIN_X11_VERSION</td>
1.216 gutterid 12099: <td>CACTI_GROUP</td>
1.156 leot 12100: </tr>
12101: <tr>
1.243 gutterid 12102: <td>CACTI_USER</td>
1.216 gutterid 12103: <td>CANNA_GROUP</td>
1.156 leot 12104: </tr>
12105: <tr>
1.243 gutterid 12106: <td>CANNA_USER</td>
1.216 gutterid 12107: <td>CAT</td>
1.156 leot 12108: </tr>
12109: <tr>
1.243 gutterid 12110: <td>CBLAS_LIBS</td>
1.229 gutterid 12111: <td>CBLAS_PC</td>
1.156 leot 12112: </tr>
12113: <tr>
1.243 gutterid 12114: <td>CCACHE_BASE</td>
1.189 bacon 12115: <td>CCACHE_DIR</td>
1.156 leot 12116: </tr>
12117: <tr>
1.243 gutterid 12118: <td>CCACHE_LOGFILE</td>
1.189 bacon 12119: <td>CC_VERSION</td>
1.156 leot 12120: </tr>
12121: <tr>
1.243 gutterid 12122: <td>CC_VERSION_STRING</td>
1.189 bacon 12123: <td>CDRECORD_CONF</td>
1.156 leot 12124: </tr>
12125: <tr>
1.243 gutterid 12126: <td>CDROM_PKG_URL_DIR</td>
1.189 bacon 12127: <td>CDROM_PKG_URL_HOST</td>
1.223 nia 12128: </tr>
12129: <tr>
1.243 gutterid 12130: <td>CHANGES</td>
1.249 gutterid 12131: <td>CHECK_COMPILER</td>
1.246 leot 12132: </tr>
12133: <tr>
12134: <td>CHECK_FAKEHOME</td>
1.249 gutterid 12135: <td>CHECK_FILES</td>
1.241 rillig 12136: </tr>
12137: <tr>
1.246 leot 12138: <td>CHECK_FILES_SKIP</td>
1.249 gutterid 12139: <td>CHECK_FILES_STRICT</td>
1.238 wiz 12140: </tr>
12141: <tr>
1.246 leot 12142: <td>CHECK_HEADERS</td>
1.249 gutterid 12143: <td>CHECK_HEADERS_SKIP</td>
1.233 wiz 12144: </tr>
12145: <tr>
1.246 leot 12146: <td>CHECK_INTERPRETER</td>
1.249 gutterid 12147: <td>CHECK_INTERPRETER_SKIP</td>
1.227 wiz 12148: </tr>
12149: <tr>
1.246 leot 12150: <td>CHECK_PERMS</td>
1.249 gutterid 12151: <td>CHECK_PERMS_AUTOFIX</td>
1.217 rillig 12152: </tr>
12153: <tr>
1.246 leot 12154: <td>CHECK_PERMS_SKIP</td>
1.249 gutterid 12155: <td>CHECK_PIE</td>
1.214 leot 12156: </tr>
12157: <tr>
1.246 leot 12158: <td>CHECK_PIE_SKIP</td>
1.249 gutterid 12159: <td>CHECK_PIE_SUPPORTED</td>
1.212 wiz 12160: </tr>
12161: <tr>
1.246 leot 12162: <td>CHECK_PORTABILITY</td>
1.249 gutterid 12163: <td>CHECK_PORTABILITY_EXPERIMENTAL</td>
1.205 wiz 12164: </tr>
12165: <tr>
1.246 leot 12166: <td>CHECK_PORTABILITY_SKIP</td>
1.249 gutterid 12167: <td>CHECK_RELRO</td>
1.197 leot 12168: </tr>
12169: <tr>
1.246 leot 12170: <td>CHECK_RELRO_SKIP</td>
1.249 gutterid 12171: <td>CHECK_RELRO_SUPPORTED</td>
1.177 leot 12172: </tr>
12173: <tr>
1.246 leot 12174: <td>CHECK_SHLIBS</td>
1.249 gutterid 12175: <td>CHECK_SHLIBS_SKIP</td>
1.161 leot 12176: </tr>
12177: <tr>
1.246 leot 12178: <td>CHECK_SHLIBS_SUPPORTED</td>
1.249 gutterid 12179: <td>CHECK_SHLIBS_TOXIC</td>
1.216 gutterid 12180: </tr>
12181: <tr>
1.246 leot 12182: <td>CHECK_SSP</td>
1.249 gutterid 12183: <td>CHECK_SSP_SKIP</td>
1.159 rillig 12184: </tr>
12185: <tr>
1.246 leot 12186: <td>CHECK_SSP_SUPPORTED</td>
1.249 gutterid 12187: <td>CHECK_STRIPPED</td>
1.156 leot 12188: </tr>
12189: <tr>
1.246 leot 12190: <td>CHECK_STRIPPED_SKIP</td>
1.249 gutterid 12191: <td>CHECK_WRKREF</td>
1.156 leot 12192: </tr>
12193: <tr>
1.246 leot 12194: <td>CHECK_WRKREF_EXTRA_DIRS</td>
1.249 gutterid 12195: <td>CHECK_WRKREF_SKIP</td>
1.156 leot 12196: </tr>
12197: <tr>
1.246 leot 12198: <td>CLAMAV_DBDIR</td>
1.249 gutterid 12199: <td>CLAMAV_GROUP</td>
1.156 leot 12200: </tr>
12201: <tr>
1.246 leot 12202: <td>CLAMAV_USER</td>
1.249 gutterid 12203: <td>CLANGBASE</td>
1.156 leot 12204: </tr>
12205: <tr>
1.246 leot 12206: <td>CLEANDEPENDS</td>
1.249 gutterid 12207: <td>CMAKE_DEPENDENCIES_REWRITE</td>
1.156 leot 12208: </tr>
12209: <tr>
1.246 leot 12210: <td>CMAKE_INSTALL_NAME_DIR</td>
1.249 gutterid 12211: <td>CMAKE_INSTALL_PREFIX</td>
1.156 leot 12212: </tr>
12213: <tr>
1.246 leot 12214: <td>CMAKE_MODULE_PATH_OVERRIDE</td>
1.249 gutterid 12215: <td>CMAKE_PKGSRC_BUILD_FLAGS</td>
1.156 leot 12216: </tr>
12217: <tr>
1.246 leot 12218: <td>CMAKE_PREFIX_PATH</td>
1.241 rillig 12219: <td>CMAKE_USE_GNU_INSTALL_DIRS</td>
1.156 leot 12220: </tr>
12221: <tr>
1.243 gutterid 12222: <td>COMPILER_RPATH_FLAG</td>
1.226 gutterid 12223: <td>COMPILER_USE_SYMLINKS</td>
1.156 leot 12224: </tr>
12225: <tr>
1.243 gutterid 12226: <td>CONFIGURE_ARGS</td>
1.226 gutterid 12227: <td>CONFIGURE_DIRS</td>
1.156 leot 12228: </tr>
12229: <tr>
1.243 gutterid 12230: <td>CONFIGURE_ENV</td>
1.226 gutterid 12231: <td>CONFIGURE_ENV_SHELL</td>
1.156 leot 12232: </tr>
12233: <tr>
1.243 gutterid 12234: <td>CONFIGURE_HAS_INFODIR</td>
1.226 gutterid 12235: <td>CONFIGURE_HAS_MANDIR</td>
1.156 leot 12236: </tr>
12237: <tr>
1.243 gutterid 12238: <td>CONFIGURE_SCRIPT</td>
1.226 gutterid 12239: <td>CONFIG_SHELL</td>
1.156 leot 12240: </tr>
12241: <tr>
1.243 gutterid 12242: <td>CONFIG_SHELL_FLAGS</td>
1.226 gutterid 12243: <td>CONF_FILES</td>
1.156 leot 12244: </tr>
12245: <tr>
1.243 gutterid 12246: <td>CONF_FILES_MODE</td>
1.226 gutterid 12247: <td>CONF_FILES_PERMS</td>
1.156 leot 12248: </tr>
12249: <tr>
1.243 gutterid 12250: <td>CONSERVER_DEFAULTHOST</td>
1.226 gutterid 12251: <td>CONSERVER_DEFAULTPORT</td>
1.156 leot 12252: </tr>
12253: <tr>
1.243 gutterid 12254: <td>CP</td>
1.232 gutterid 12255: <td>CPE</td>
12256: </tr>
12257: <tr>
1.243 gutterid 12258: <td>CPE_EDITION</td>
1.232 gutterid 12259: <td>CPE_LANG</td>
12260: </tr>
12261: <tr>
1.243 gutterid 12262: <td>CPE_OTHER</td>
1.232 gutterid 12263: <td>CPE_PART</td>
12264: </tr>
12265: <tr>
1.243 gutterid 12266: <td>CPE_PRODUCT</td>
1.232 gutterid 12267: <td>CPE_SW_EDITION</td>
12268: </tr>
12269: <tr>
1.243 gutterid 12270: <td>CPE_TARGET_HW</td>
1.232 gutterid 12271: <td>CPE_TARGET_SW</td>
12272: </tr>
12273: <tr>
1.243 gutterid 12274: <td>CPE_UPDATE</td>
1.232 gutterid 12275: <td>CPE_URI</td>
12276: </tr>
12277: <tr>
1.243 gutterid 12278: <td>CPE_VENDOR</td>
1.232 gutterid 12279: <td>CPE_VERSION</td>
1.156 leot 12280: </tr>
12281: <tr>
1.243 gutterid 12282: <td>CPP</td>
1.232 gutterid 12283: <td>CPP_PRECOMP_FLAGS</td>
1.156 leot 12284: </tr>
12285: <tr>
1.243 gutterid 12286: <td>CREATE_WRKDIR_SYMLINK</td>
1.232 gutterid 12287: <td>CROSSBASE</td>
1.156 leot 12288: </tr>
12289: <tr>
1.243 gutterid 12290: <td>CTFCONVERT</td>
1.232 gutterid 12291: <td>CTF_FILES_SKIP</td>
1.156 leot 12292: </tr>
12293: <tr>
1.243 gutterid 12294: <td>CTF_SUPPORTED</td>
1.232 gutterid 12295: <td>CTYPE</td>
1.156 leot 12296: </tr>
12297: <tr>
1.243 gutterid 12298: <td>CUPS_GROUP</td>
1.232 gutterid 12299: <td>CUPS_SYSTEM_GROUPS</td>
1.177 leot 12300: </tr>
12301: <tr>
1.243 gutterid 12302: <td>CUPS_USER</td>
1.232 gutterid 12303: <td>CURSES_DEFAULT</td>
1.227 wiz 12304: </tr>
12305: <tr>
1.243 gutterid 12306: <td>CURSES_TYPE</td>
1.249 gutterid 12307: <td>CXX</td>
1.246 leot 12308: </tr>
12309: <tr>
12310: <td>CYRUS_GROUP</td>
1.249 gutterid 12311: <td>CYRUS_IDLE</td>
1.238 wiz 12312: </tr>
12313: <tr>
1.246 leot 12314: <td>CYRUS_USER</td>
1.249 gutterid 12315: <td>DAEMONTOOLS_GROUP</td>
1.233 wiz 12316: </tr>
12317: <tr>
1.246 leot 12318: <td>DAEMONTOOLS_LOG_USER</td>
1.249 gutterid 12319: <td>DARWIN_NO_SYSTEM_LIBS</td>
1.217 rillig 12320: </tr>
12321: <tr>
1.246 leot 12322: <td>DARWIN_REQUIRES_FILTER</td>
1.249 gutterid 12323: <td>DBUS_GROUP</td>
1.214 leot 12324: </tr>
12325: <tr>
1.246 leot 12326: <td>DBUS_USER</td>
1.249 gutterid 12327: <td>DEFANG_GROUP</td>
1.212 wiz 12328: </tr>
12329: <tr>
1.246 leot 12330: <td>DEFANG_USER</td>
1.249 gutterid 12331: <td>DEFAULT_ACCEPTABLE_LICENSES</td>
1.205 wiz 12332: </tr>
12333: <tr>
1.246 leot 12334: <td>DEFAULT_DISTFILES</td>
1.249 gutterid 12335: <td>DEFAULT_IRC_SERVER</td>
1.197 leot 12336: </tr>
12337: <tr>
1.246 leot 12338: <td>DEFAULT_SERIAL_DEVICE</td>
1.249 gutterid 12339: <td>DEF_UMASK</td>
1.159 rillig 12340: </tr>
12341: <tr>
1.246 leot 12342: <td>DEINSTALLDEPENDS</td>
1.249 gutterid 12343: <td>DEINSTALL_SRC</td>
1.156 leot 12344: </tr>
12345: <tr>
1.246 leot 12346: <td>DEINSTALL_TEMPLATES</td>
1.249 gutterid 12347: <td>DELAYED_ERROR_MSG</td>
1.156 leot 12348: </tr>
12349: <tr>
1.246 leot 12350: <td>DELAYED_WARNING_MSG</td>
1.249 gutterid 12351: <td>DEPENDS</td>
1.195 gutterid 12352: </tr>
12353: <tr>
1.246 leot 12354: <td>DEPENDS_TARGET</td>
1.249 gutterid 12355: <td>DEPENDS_TYPE</td>
1.156 leot 12356: </tr>
12357: <tr>
1.246 leot 12358: <td>DESTDIR</td>
1.249 gutterid 12359: <td>DESTDIR_VARNAME</td>
1.156 leot 12360: </tr>
12361: <tr>
1.246 leot 12362: <td>DIALER_GROUP</td>
1.249 gutterid 12363: <td>DIGEST_REQD</td>
1.156 leot 12364: </tr>
12365: <tr>
1.246 leot 12366: <td>DISTDIR</td>
1.249 gutterid 12367: <td>DISTFILES</td>
1.156 leot 12368: </tr>
12369: <tr>
1.246 leot 12370: <td>DISTINFO_FILE</td>
1.249 gutterid 12371: <td>DISTNAME</td>
1.156 leot 12372: </tr>
12373: <tr>
1.246 leot 12374: <td>DIST_PATH</td>
1.249 gutterid 12375: <td>DIST_SUBDIR</td>
1.156 leot 12376: </tr>
12377: <tr>
1.246 leot 12378: <td>DJBDNS_AXFR_USER</td>
1.249 gutterid 12379: <td>DJBDNS_CACHE_USER</td>
1.156 leot 12380: </tr>
12381: <tr>
1.246 leot 12382: <td>DJBDNS_DJBDNS_GROUP</td>
1.249 gutterid 12383: <td>DJBDNS_LOG_USER</td>
1.156 leot 12384: </tr>
12385: <tr>
1.246 leot 12386: <td>DJBDNS_RBL_USER</td>
1.249 gutterid 12387: <td>DJBDNS_TINY_USER</td>
1.156 leot 12388: </tr>
12389: <tr>
1.246 leot 12390: <td>DLOPEN_REQUIRE_PTHREADS</td>
1.249 gutterid 12391: <td>DL_AUTO_VARS</td>
1.156 leot 12392: </tr>
12393: <tr>
1.246 leot 12394: <td>DL_CFLAGS</td>
1.249 gutterid 12395: <td>DL_LDFLAGS</td>
1.156 leot 12396: </tr>
12397: <tr>
1.246 leot 12398: <td>DL_LIBS</td>
1.249 gutterid 12399: <td>DNS</td>
1.156 leot 12400: </tr>
12401: <tr>
1.246 leot 12402: <td>DOCOWN</td>
1.249 gutterid 12403: <td>DOWNLOADED_DISTFILE</td>
1.156 leot 12404: </tr>
12405: <tr>
1.246 leot 12406: <td>DQCACHE_GROUP</td>
1.249 gutterid 12407: <td>DQCACHE_USER</td>
1.156 leot 12408: </tr>
12409: <tr>
1.246 leot 12410: <td>DT_LAYOUT</td>
1.249 gutterid 12411: <td>DYNAMIC_SITES_CMD</td>
1.156 leot 12412: </tr>
12413: <tr>
1.246 leot 12414: <td>DYNAMIC_SITES_SCRIPT</td>
1.249 gutterid 12415: <td>ECHO</td>
1.156 leot 12416: </tr>
12417: <tr>
1.246 leot 12418: <td>ECHO_N</td>
1.249 gutterid 12419: <td>ELK_GUI</td>
1.243 gutterid 12420: </tr>
12421: <tr>
1.246 leot 12422: <td>EMACS_TYPE</td>
1.249 gutterid 12423: <td>EMULDIR</td>
1.218 nia 12424: </tr>
12425: <tr>
1.246 leot 12426: <td>EMULSUBDIR</td>
1.249 gutterid 12427: <td>EMULSUBDIRSLASH</td>
1.156 leot 12428: </tr>
12429: <tr>
1.246 leot 12430: <td>EMUL_ARCH</td>
1.249 gutterid 12431: <td>EMUL_DISTRO</td>
1.156 leot 12432: </tr>
12433: <tr>
1.246 leot 12434: <td>EMUL_EXEC_FMT</td>
1.249 gutterid 12435: <td>EMUL_IS_NATIVE</td>
1.156 leot 12436: </tr>
12437: <tr>
1.246 leot 12438: <td>EMUL_MODULES</td>
1.249 gutterid 12439: <td>EMUL_OPSYS</td>
1.156 leot 12440: </tr>
12441: <tr>
1.246 leot 12442: <td>EMUL_PKG_FMT</td>
1.249 gutterid 12443: <td>EMUL_PLATFORM</td>
1.156 leot 12444: </tr>
12445: <tr>
1.246 leot 12446: <td>EMUL_PLATFORMS</td>
1.249 gutterid 12447: <td>EMUL_PREFER</td>
1.156 leot 12448: </tr>
12449: <tr>
1.246 leot 12450: <td>EMUL_REQD</td>
1.249 gutterid 12451: <td>EMUL_TYPE</td>
1.156 leot 12452: </tr>
12453: <tr>
1.246 leot 12454: <td>ERROR_MSG</td>
1.249 gutterid 12455: <td>EXIM_GROUP</td>
1.156 leot 12456: </tr>
12457: <tr>
1.246 leot 12458: <td>EXIM_USER</td>
1.249 gutterid 12459: <td>EXPORT_SYMBOLS_LDFLAGS</td>
1.156 leot 12460: </tr>
12461: <tr>
1.246 leot 12462: <td>EXTRACTOR</td>
1.249 gutterid 12463: <td>EXTRACT_CMD</td>
1.156 leot 12464: </tr>
12465: <tr>
1.246 leot 12466: <td>EXTRACT_CMD_DEFAULT</td>
1.249 gutterid 12467: <td>EXTRACT_DIR</td>
1.156 leot 12468: </tr>
12469: <tr>
1.246 leot 12470: <td>EXTRACT_ELEMENTS</td>
1.249 gutterid 12471: <td>EXTRACT_ENV</td>
1.156 leot 12472: </tr>
12473: <tr>
1.246 leot 12474: <td>EXTRACT_ONLY</td>
1.249 gutterid 12475: <td>EXTRACT_OPTS</td>
1.156 leot 12476: </tr>
12477: <tr>
1.246 leot 12478: <td>EXTRACT_SUFX</td>
1.249 gutterid 12479: <td>EXTRACT_USING</td>
1.223 nia 12480: </tr>
12481: <tr>
1.246 leot 12482: <td>FAIL</td>
1.249 gutterid 12483: <td>FAILOVER_FETCH</td>
1.156 leot 12484: </tr>
12485: <tr>
1.246 leot 12486: <td>FAIL_MSG</td>
1.249 gutterid 12487: <td>FAKE_NCURSES</td>
1.156 leot 12488: </tr>
12489: <tr>
1.246 leot 12490: <td>FAM</td>
1.249 gutterid 12491: <td>FAM_ACCEPTED</td>
1.156 leot 12492: </tr>
12493: <tr>
1.246 leot 12494: <td>FAM_DEFAULT</td>
1.249 gutterid 12495: <td>FAM_SERVER</td>
1.156 leot 12496: </tr>
12497: <tr>
1.246 leot 12498: <td>FCPATH</td>
1.249 gutterid 12499: <td>FEATURE_CPPFLAGS</td>
1.156 leot 12500: </tr>
12501: <tr>
1.246 leot 12502: <td>FEATURE_LDFLAGS</td>
1.249 gutterid 12503: <td>FEATURE_LIBS</td>
1.156 leot 12504: </tr>
12505: <tr>
1.246 leot 12506: <td>FETCH_AFTER_ARGS</td>
1.249 gutterid 12507: <td>FETCH_BEFORE_ARGS</td>
1.156 leot 12508: </tr>
12509: <tr>
1.246 leot 12510: <td>FETCH_CMD</td>
1.249 gutterid 12511: <td>FETCH_OUTPUT_ARGS</td>
1.156 leot 12512: </tr>
12513: <tr>
1.246 leot 12514: <td>FETCH_PROXY</td>
1.249 gutterid 12515: <td>FETCH_RESUME_ARGS</td>
1.156 leot 12516: </tr>
12517: <tr>
1.246 leot 12518: <td>FETCH_TIMEOUT</td>
1.249 gutterid 12519: <td>FETCH_USE_IPV4_ONLY</td>
1.177 leot 12520: </tr>
12521: <tr>
1.246 leot 12522: <td>FETCH_USING</td>
1.249 gutterid 12523: <td>FILES_SUBST</td>
1.241 rillig 12524: </tr>
12525: <tr>
1.246 leot 12526: <td>FILES_SUBST_SED</td>
1.243 gutterid 12527: <td>FIX_SYSTEM_HEADERS</td>
1.156 leot 12528: </tr>
12529: <tr>
1.226 gutterid 12530: <td>FONTS_DIRS</td>
1.243 gutterid 12531: <td>FONTS_VERBOSE</td>
1.177 leot 12532: </tr>
12533: <tr>
1.226 gutterid 12534: <td>FOO_HACKS_MK</td>
1.244 gutterid 12535: <td>FORCE_CXX_STD</td>
12536: </tr>
12537: <tr>
12538: <td>FORCE_C_STD</td>
1.243 gutterid 12539: <td>FOX_USE_XUNICODE</td>
1.156 leot 12540: </tr>
12541: <tr>
1.226 gutterid 12542: <td>FREEWNN_GROUP</td>
1.243 gutterid 12543: <td>FREEWNN_USER</td>
1.156 leot 12544: </tr>
12545: <tr>
1.226 gutterid 12546: <td>FTP_PKG_URL_DIR</td>
1.243 gutterid 12547: <td>FTP_PKG_URL_HOST</td>
1.156 leot 12548: </tr>
12549: <tr>
1.226 gutterid 12550: <td>GAMEDATAMODE</td>
1.243 gutterid 12551: <td>GAMEDATA_PERMS</td>
1.156 leot 12552: </tr>
12553: <tr>
1.226 gutterid 12554: <td>GAMEDIRMODE</td>
1.243 gutterid 12555: <td>GAMEDIR_PERMS</td>
1.156 leot 12556: </tr>
12557: <tr>
1.226 gutterid 12558: <td>GAMEGRP</td>
1.243 gutterid 12559: <td>GAMEMODE</td>
1.156 leot 12560: </tr>
12561: <tr>
1.226 gutterid 12562: <td>GAMEOWN</td>
1.243 gutterid 12563: <td>GAMES_GROUP</td>
1.156 leot 12564: </tr>
12565: <tr>
1.226 gutterid 12566: <td>GAMES_USER</td>
1.243 gutterid 12567: <td>GCC</td>
1.156 leot 12568: </tr>
12569: <tr>
1.226 gutterid 12570: <td>GCCBASE</td>
1.243 gutterid 12571: <td>GCC_REQD</td>
1.156 leot 12572: </tr>
12573: <tr>
1.226 gutterid 12574: <td>GCC_VERSION_SUFFIX</td>
1.243 gutterid 12575: <td>GEM_BUILD</td>
1.156 leot 12576: </tr>
12577: <tr>
1.226 gutterid 12578: <td>GEM_CLEANBUILD</td>
1.243 gutterid 12579: <td>GEM_CLEANBUILD_EXTENSIONS</td>
1.156 leot 12580: </tr>
12581: <tr>
1.226 gutterid 12582: <td>GEM_DOCDIR</td>
1.243 gutterid 12583: <td>GEM_EXTSDIR</td>
1.177 leot 12584: </tr>
12585: <tr>
1.226 gutterid 12586: <td>GEM_HOME</td>
1.243 gutterid 12587: <td>GEM_KEEPBUILD</td>
1.156 leot 12588: </tr>
12589: <tr>
1.226 gutterid 12590: <td>GEM_LIBDIR</td>
1.243 gutterid 12591: <td>GEM_NAME</td>
1.156 leot 12592: </tr>
12593: <tr>
1.226 gutterid 12594: <td>GEM_PATH</td>
1.243 gutterid 12595: <td>GEM_PLUGINSDIR</td>
1.198 leot 12596: </tr>
12597: <tr>
1.226 gutterid 12598: <td>GEM_SPECFILE</td>
1.243 gutterid 12599: <td>GENERATE_PLIST</td>
1.156 leot 12600: </tr>
12601: <tr>
1.226 gutterid 12602: <td>GHC</td>
1.243 gutterid 12603: <td>GHOSTSCRIPT_REQD</td>
1.156 leot 12604: </tr>
12605: <tr>
1.226 gutterid 12606: <td>GITHUB_PROJECT</td>
1.243 gutterid 12607: <td>GITHUB_RELEASE</td>
1.177 leot 12608: </tr>
12609: <tr>
1.226 gutterid 12610: <td>GITHUB_SUBMODULES</td>
1.243 gutterid 12611: <td>GITHUB_TAG</td>
1.159 rillig 12612: </tr>
12613: <tr>
1.226 gutterid 12614: <td>GITHUB_TYPE</td>
1.243 gutterid 12615: <td>GITLAB_PROJECT</td>
1.223 nia 12616: </tr>
12617: <tr>
1.226 gutterid 12618: <td>GITLAB_RELEASE</td>
1.243 gutterid 12619: <td>GITLAB_SUBMODULES</td>
1.223 nia 12620: </tr>
12621: <tr>
1.226 gutterid 12622: <td>GITLAB_TAG</td>
1.243 gutterid 12623: <td>GITLAB_TYPE</td>
1.223 nia 12624: </tr>
12625: <tr>
1.242 gutterid 12626: <td>GNU</td>
1.249 gutterid 12627: <td>GNU_CONFIGURE</td>
1.246 leot 12628: </tr>
12629: <tr>
12630: <td>GNU_CONFIGURE_INFODIR</td>
1.249 gutterid 12631: <td>GNU_CONFIGURE_MANDIR</td>
1.241 rillig 12632: </tr>
12633: <tr>
1.246 leot 12634: <td>GNU_CONFIGURE_QUIET</td>
1.249 gutterid 12635: <td>GNU_CONFIGURE_STRICT</td>
1.233 wiz 12636: </tr>
12637: <tr>
1.246 leot 12638: <td>GODEP_REDIRECTS</td>
1.249 gutterid 12639: <td>GO_BUILD_PATTERN</td>
1.156 leot 12640: </tr>
12641: <tr>
1.246 leot 12642: <td>GO_DEPS</td>
1.249 gutterid 12643: <td>GO_DIST_BASE</td>
1.156 leot 12644: </tr>
12645: <tr>
1.246 leot 12646: <td>GO_EXTRA_MOD_DIRS</td>
1.249 gutterid 12647: <td>GO_MODULE_FILES</td>
1.156 leot 12648: </tr>
12649: <tr>
1.246 leot 12650: <td>GO_SRCPATH</td>
1.249 gutterid 12651: <td>GROUP_SPECIFIC_PKGS</td>
1.238 wiz 12652: </tr>
12653: <tr>
1.246 leot 12654: <td>GRUB_NETWORK_CARDS</td>
1.249 gutterid 12655: <td>GRUB_PRESET_COMMAND</td>
1.156 leot 12656: </tr>
12657: <tr>
1.246 leot 12658: <td>GRUB_SCAN_ARGS</td>
1.243 gutterid 12659: <td>GZIP</td>
1.156 leot 12660: </tr>
12661: <tr>
1.233 wiz 12662: <td>HASKELL_ENABLE_DYNAMIC_EXECUTABLE</td>
1.243 gutterid 12663: <td>HASKELL_ENABLE_HADDOCK_DOCUMENTATION</td>
1.217 rillig 12664: </tr>
12665: <tr>
1.222 gutterid 12666: <td>HASKELL_ENABLE_LIBRARY_PROFILING</td>
1.243 gutterid 12667: <td>HASKELL_ENABLE_SHARED_LIBRARY</td>
1.226 gutterid 12668: </tr>
12669: <tr>
1.236 gutterid 12670: <td>HASKELL_ENABLE_TESTS</td>
1.243 gutterid 12671: <td>HASKELL_OPTIMIZATION_LEVEL</td>
1.220 nia 12672: </tr>
12673: <tr>
1.232 gutterid 12674: <td>HASKELL_PKG_NAME</td>
1.243 gutterid 12675: <td>HASKELL_UNRESTRICT_DEPENDENCIES</td>
1.229 gutterid 12676: </tr>
12677: <tr>
1.226 gutterid 12678: <td>HEADER_TEMPLATES</td>
1.249 gutterid 12679: <td>HOMEPAGE</td>
1.214 leot 12680: </tr>
12681: <tr>
1.249 gutterid 12682: <td>HOST_PKGTOOLS_ARGS</td>
12683: <td>HOST_SPECIFIC_PKGS</td>
1.246 leot 12684: </tr>
12685: <tr>
12686: <td>HOWL_GROUP</td>
1.249 gutterid 12687: <td>HOWL_USER</td>
1.241 rillig 12688: </tr>
12689: <tr>
1.246 leot 12690: <td>ICCBASE</td>
1.249 gutterid 12691: <td>ICECAST_CHROOTDIR</td>
1.233 wiz 12692: </tr>
12693: <tr>
1.246 leot 12694: <td>ICON_THEMES</td>
1.249 gutterid 12695: <td>IDOBASE</td>
1.227 wiz 12696: </tr>
12697: <tr>
1.246 leot 12698: <td>IGNORE_CCACHE</td>
1.249 gutterid 12699: <td>IGNORE_INFO_DIRS</td>
1.223 nia 12700: </tr>
12701: <tr>
1.246 leot 12702: <td>IGNORE_INTERACTIVE_FETCH</td>
1.249 gutterid 12703: <td>IMAKE</td>
1.156 leot 12704: </tr>
12705: <tr>
1.246 leot 12706: <td>IMAKEOPTS</td>
1.249 gutterid 12707: <td>IMAKE_MAKE</td>
1.156 leot 12708: </tr>
12709: <tr>
1.246 leot 12710: <td>IMAKE_MANINSTALL</td>
1.249 gutterid 12711: <td>IMAP_UW_CCLIENT_MBOX_FMT</td>
1.191 bacon 12712: </tr>
12713: <tr>
1.246 leot 12714: <td>IMDICTDIR</td>
1.249 gutterid 12715: <td>INCOMPAT_CURSES</td>
1.156 leot 12716: </tr>
12717: <tr>
1.246 leot 12718: <td>INFO_DIR</td>
1.249 gutterid 12719: <td>INFO_FILES</td>
1.156 leot 12720: </tr>
12721: <tr>
1.246 leot 12722: <td>INFO_MSG</td>
1.249 gutterid 12723: <td>INIT_SYSTEM</td>
1.156 leot 12724: </tr>
12725: <tr>
1.246 leot 12726: <td>INN_DATA_DIR</td>
1.249 gutterid 12727: <td>INN_GROUP</td>
1.156 leot 12728: </tr>
12729: <tr>
1.246 leot 12730: <td>INN_USER</td>
1.249 gutterid 12731: <td>INSTALLATION_DIRS</td>
1.156 leot 12732: </tr>
12733: <tr>
1.246 leot 12734: <td>INSTALLATION_DIRS_FROM_PLIST</td>
1.249 gutterid 12735: <td>INSTALL_ENV</td>
1.156 leot 12736: </tr>
12737: <tr>
1.246 leot 12738: <td>INSTALL_SH_OVERRIDE</td>
1.249 gutterid 12739: <td>INSTALL_SRC</td>
1.156 leot 12740: </tr>
12741: <tr>
1.246 leot 12742: <td>INSTALL_TEMPLATES</td>
1.249 gutterid 12743: <td>INSTALL_UNSTRIPPED</td>
1.156 leot 12744: </tr>
12745: <tr>
1.246 leot 12746: <td>IRCD_HYBRID_IRC_GROUP</td>
1.249 gutterid 12747: <td>IRCD_HYBRID_IRC_USER</td>
1.172 rillig 12748: </tr>
12749: <tr>
1.246 leot 12750: <td>IRCD_HYBRID_MAXCONN</td>
1.249 gutterid 12751: <td>IRCD_HYBRID_NICLEN</td>
1.156 leot 12752: </tr>
12753: <tr>
1.246 leot 12754: <td>IRCD_HYBRID_SYSLOG_EVENTS</td>
1.249 gutterid 12755: <td>IRCD_HYBRID_SYSLOG_FACILITY</td>
1.156 leot 12756: </tr>
12757: <tr>
1.246 leot 12758: <td>IRCD_HYBRID_TOPICLEN</td>
1.249 gutterid 12759: <td>IRIX</td>
1.156 leot 12760: </tr>
12761: <tr>
1.246 leot 12762: <td>IRRD_USE_PGP</td>
1.249 gutterid 12763: <td>JABBERD_GROUP</td>
1.156 leot 12764: </tr>
12765: <tr>
1.246 leot 12766: <td>JABBERD_LOGDIR</td>
1.249 gutterid 12767: <td>JABBERD_PIDDIR</td>
1.156 leot 12768: </tr>
12769: <tr>
1.246 leot 12770: <td>JABBERD_SPOOLDIR</td>
1.243 gutterid 12771: <td>JABBERD_USER</td>
1.156 leot 12772: </tr>
12773: <tr>
1.240 gutterid 12774: <td>JAVA_BINPREFIX</td>
1.249 gutterid 12775: <td>JAVA_CLASSPATH</td>
1.246 leot 12776: </tr>
12777: <tr>
12778: <td>JAVA_HOME</td>
1.249 gutterid 12779: <td>JAVA_LD_LIBRARY_PATH</td>
1.156 leot 12780: </tr>
12781: <tr>
1.246 leot 12782: <td>JAVA_NAME</td>
1.249 gutterid 12783: <td>JAVA_UNLIMIT</td>
1.233 wiz 12784: </tr>
12785: <tr>
1.246 leot 12786: <td>JAVA_WRAPPERS</td>
1.249 gutterid 12787: <td>JPEG_ACCEPTED</td>
1.156 leot 12788: </tr>
12789: <tr>
1.246 leot 12790: <td>JPEG_DEFAULT</td>
1.249 gutterid 12791: <td>KERBEROS</td>
1.227 wiz 12792: </tr>
12793: <tr>
1.246 leot 12794: <td>KERMIT_SUID_UUCP</td>
1.249 gutterid 12795: <td>KJS_USE_PCRE</td>
1.177 leot 12796: </tr>
12797: <tr>
1.246 leot 12798: <td>KNEWS_DOMAIN_FILE</td>
1.249 gutterid 12799: <td>KNEWS_DOMAIN_NAME</td>
1.156 leot 12800: </tr>
12801: <tr>
1.246 leot 12802: <td>KRB5_ACCEPTED</td>
1.249 gutterid 12803: <td>KRB5_DEFAULT</td>
1.217 rillig 12804: </tr>
12805: <tr>
1.246 leot 12806: <td>LANGUAGES</td>
1.249 gutterid 12807: <td>LAPACKE_LIBS</td>
1.156 leot 12808: </tr>
12809: <tr>
1.246 leot 12810: <td>LAPACKE_PC</td>
1.249 gutterid 12811: <td>LAPACK_LIBS</td>
1.156 leot 12812: </tr>
12813: <tr>
1.246 leot 12814: <td>LAPACK_PC</td>
1.249 gutterid 12815: <td>LATEX2HTML_ICONPATH</td>
1.156 leot 12816: </tr>
12817: <tr>
1.246 leot 12818: <td>LDCONFIG_ADD_CMD</td>
1.249 gutterid 12819: <td>LDCONFIG_REMOVE_CMD</td>
1.156 leot 12820: </tr>
12821: <tr>
1.246 leot 12822: <td>LDD</td>
1.249 gutterid 12823: <td>LEAFNODE_DATA_DIR</td>
1.156 leot 12824: </tr>
12825: <tr>
1.246 leot 12826: <td>LEAFNODE_GROUP</td>
1.249 gutterid 12827: <td>LEAFNODE_USER</td>
1.177 leot 12828: </tr>
12829: <tr>
1.246 leot 12830: <td>LIBDVDCSS_HOMEPAGE</td>
1.249 gutterid 12831: <td>LIBDVDCSS_MASTER_SITES</td>
1.156 leot 12832: </tr>
12833: <tr>
1.246 leot 12834: <td>LIBIMAGEQUANT_TYPE</td>
1.249 gutterid 12835: <td>LIBRSVG_TYPE</td>
1.156 leot 12836: </tr>
12837: <tr>
1.246 leot 12838: <td>LIBTOOL</td>
1.249 gutterid 12839: <td>LIBTOOLIZE_PLIST</td>
1.156 leot 12840: </tr>
12841: <tr>
1.246 leot 12842: <td>LIBTOOL_M4_OVERRIDE</td>
1.249 gutterid 12843: <td>LIBUSB_TYPE</td>
1.156 leot 12844: </tr>
12845: <tr>
1.246 leot 12846: <td>LICENSE</td>
1.249 gutterid 12847: <td>LINKER_RPATH_FLAG</td>
1.205 wiz 12848: </tr>
12849: <tr>
1.246 leot 12850: <td>LINK_RPATH_FLAG</td>
1.242 gutterid 12851: <td>LINUX_LOCALES</td>
1.241 rillig 12852: </tr>
12853: <tr>
1.244 gutterid 12854: <td>LOCALBASE</td>
1.242 gutterid 12855: <td>LOCALBASE_LOCKTYPE</td>
1.156 leot 12856: </tr>
12857: <tr>
1.244 gutterid 12858: <td>LOCALPATCHES</td>
1.242 gutterid 12859: <td>LOVE_DATA</td>
1.238 wiz 12860: </tr>
12861: <tr>
1.244 gutterid 12862: <td>LOVE_GAME</td>
1.242 gutterid 12863: <td>LOVE_VERSION</td>
1.223 nia 12864: </tr>
12865: <tr>
1.244 gutterid 12866: <td>LP32PLATFORMS</td>
1.242 gutterid 12867: <td>LP64PLATFORMS</td>
1.177 leot 12868: </tr>
12869: <tr>
1.244 gutterid 12870: <td>LUA_BUSTED_ARGS</td>
1.242 gutterid 12871: <td>LUA_CDIR</td>
1.214 leot 12872: </tr>
12873: <tr>
1.244 gutterid 12874: <td>LUA_COMPILER</td>
1.242 gutterid 12875: <td>LUA_DOCDIR</td>
1.197 leot 12876: </tr>
12877: <tr>
1.244 gutterid 12878: <td>LUA_EXAMPLESDIR</td>
1.242 gutterid 12879: <td>LUA_INCDIR</td>
1.156 leot 12880: </tr>
12881: <tr>
1.244 gutterid 12882: <td>LUA_INTERPRETER</td>
1.242 gutterid 12883: <td>LUA_LDIR</td>
1.156 leot 12884: </tr>
12885: <tr>
1.244 gutterid 12886: <td>LUA_LINKER_MAGIC</td>
1.242 gutterid 12887: <td>LUA_PKGPREFIX</td>
1.221 nia 12888: </tr>
12889: <tr>
1.244 gutterid 12890: <td>LUA_SELF_CONFLICT</td>
1.242 gutterid 12891: <td>LUA_USE_BUSTED</td>
1.218 nia 12892: </tr>
12893: <tr>
1.244 gutterid 12894: <td>LUA_VERSIONS_ACCEPTED</td>
1.242 gutterid 12895: <td>LUA_VERSIONS_INCOMPATIBLE</td>
1.218 nia 12896: </tr>
12897: <tr>
1.244 gutterid 12898: <td>LUA_VERSION_DEFAULT</td>
1.242 gutterid 12899: <td>LUA_VERSION_REQD</td>
1.218 nia 12900: </tr>
12901: <tr>
1.244 gutterid 12902: <td>Lua</td>
1.242 gutterid 12903: <td>MACHINE_PLATFORM</td>
1.218 nia 12904: </tr>
12905: <tr>
1.244 gutterid 12906: <td>MAILAGENT_DOMAIN</td>
1.242 gutterid 12907: <td>MAILAGENT_EMAIL</td>
1.218 nia 12908: </tr>
12909: <tr>
1.244 gutterid 12910: <td>MAILAGENT_FQDN</td>
1.242 gutterid 12911: <td>MAILAGENT_ORGANIZATION</td>
1.218 nia 12912: </tr>
12913: <tr>
1.244 gutterid 12914: <td>MAJORDOMO_HOMEDIR</td>
1.249 gutterid 12915: <td>MAKEINFO_ARGS</td>
1.246 leot 12916: </tr>
12917: <tr>
12918: <td>MAKE_DIRS</td>
1.249 gutterid 12919: <td>MAKE_DIRS_PERMS</td>
1.205 wiz 12920: </tr>
12921: <tr>
1.246 leot 12922: <td>MAKE_ENV</td>
1.249 gutterid 12923: <td>MAKE_FILE</td>
1.233 wiz 12924: </tr>
12925: <tr>
1.246 leot 12926: <td>MAKE_FLAGS</td>
1.249 gutterid 12927: <td>MAKE_JOBS</td>
1.227 wiz 12928: </tr>
12929: <tr>
1.246 leot 12930: <td>MAKE_JOBS_SAFE</td>
1.249 gutterid 12931: <td>MAKE_PROGRAM</td>
1.156 leot 12932: </tr>
12933: <tr>
1.246 leot 12934: <td>MANCOMPRESSED_IF_MANZ</td>
1.249 gutterid 12935: <td>MANINSTALL</td>
1.212 wiz 12936: </tr>
12937: <tr>
1.246 leot 12938: <td>MANZ</td>
1.249 gutterid 12939: <td>MARIADB_VERSIONS_ALL</td>
1.156 leot 12940: </tr>
12941: <tr>
1.246 leot 12942: <td>MASTER_SITES</td>
1.249 gutterid 12943: <td>MASTER_SITE_BACKUP</td>
1.156 leot 12944: </tr>
12945: <tr>
1.246 leot 12946: <td>MASTER_SITE_LOCAL</td>
1.249 gutterid 12947: <td>MASTER_SITE_MOZILLA</td>
1.156 leot 12948: </tr>
12949: <tr>
1.246 leot 12950: <td>MASTER_SITE_OVERRIDE</td>
1.249 gutterid 12951: <td>MASTER_SITE_PERL_CPAN</td>
1.156 leot 12952: </tr>
12953: <tr>
1.246 leot 12954: <td>MASTER_SORT</td>
1.249 gutterid 12955: <td>MASTER_SORT_RANDOM</td>
1.189 bacon 12956: </tr>
12957: <tr>
1.246 leot 12958: <td>MASTER_SORT_REGEX</td>
1.249 gutterid 12959: <td>MECAB_CHARSET</td>
1.156 leot 12960: </tr>
12961: <tr>
1.246 leot 12962: <td>MEDIATOMB_GROUP</td>
1.249 gutterid 12963: <td>MEDIATOMB_USER</td>
1.156 leot 12964: </tr>
12965: <tr>
1.246 leot 12966: <td>MIPSPROBASE</td>
1.249 gutterid 12967: <td>MIREDO_GROUP</td>
1.156 leot 12968: </tr>
12969: <tr>
1.246 leot 12970: <td>MIREDO_USER</td>
1.249 gutterid 12971: <td>MISSING_FEATURES</td>
1.156 leot 12972: </tr>
12973: <tr>
1.246 leot 12974: <td>MKDIR</td>
1.249 gutterid 12975: <td>MKPIE_SUPPORTED</td>
1.156 leot 12976: </tr>
12977: <tr>
1.246 leot 12978: <td>MLDONKEY_GROUP</td>
1.249 gutterid 12979: <td>MLDONKEY_HOME</td>
1.156 leot 12980: </tr>
12981: <tr>
1.246 leot 12982: <td>MLDONKEY_USER</td>
1.249 gutterid 12983: <td>MONOTONE_GROUP</td>
1.156 leot 12984: </tr>
12985: <tr>
1.246 leot 12986: <td>MONOTONE_USER</td>
1.249 gutterid 12987: <td>MOTIFBASE</td>
1.156 leot 12988: </tr>
12989: <tr>
1.246 leot 12990: <td>MOTIF_TYPE</td>
1.249 gutterid 12991: <td>MOTIF_TYPE_DEFAULT</td>
1.156 leot 12992: </tr>
12993: <tr>
1.246 leot 12994: <td>MPI_TYPE</td>
1.249 gutterid 12995: <td>MSGFMT_STRIP_MSGCTXT</td>
1.207 leot 12996: </tr>
12997: <tr>
1.246 leot 12998: <td>MSGFMT_STRIP_MSGID_PLURAL</td>
1.232 gutterid 12999: <td>MTOOLS_ENABLE_FLOPPYD</td>
1.241 rillig 13000: </tr>
13001: <tr>
1.244 gutterid 13002: <td>MV</td>
1.241 rillig 13003: <td>MYSQL_CHARSET</td>
1.156 leot 13004: </tr>
13005: <tr>
1.244 gutterid 13006: <td>MYSQL_DATADIR</td>
1.241 rillig 13007: <td>MYSQL_EXTRA_CHARSET</td>
1.238 wiz 13008: </tr>
13009: <tr>
1.244 gutterid 13010: <td>MYSQL_GROUP</td>
1.241 rillig 13011: <td>MYSQL_USER</td>
1.223 nia 13012: </tr>
13013: <tr>
1.244 gutterid 13014: <td>MYSQL_VERSION</td>
1.241 rillig 13015: <td>MYSQL_VERSIONS_ACCEPTED</td>
1.214 leot 13016: </tr>
13017: <tr>
1.244 gutterid 13018: <td>MYSQL_VERSION_DEFAULT</td>
1.242 gutterid 13019: <td>NAGIOSCMD_GROUP</td>
1.197 leot 13020: </tr>
13021: <tr>
1.244 gutterid 13022: <td>NAGIOSDIR</td>
1.242 gutterid 13023: <td>NAGIOS_GROUP</td>
1.205 wiz 13024: </tr>
13025: <tr>
1.244 gutterid 13026: <td>NAGIOS_USER</td>
1.242 gutterid 13027: <td>NATIVE_APPEND_ABI</td>
1.156 leot 13028: </tr>
13029: <tr>
1.244 gutterid 13030: <td>NATIVE_APPEND_ELF</td>
1.242 gutterid 13031: <td>NATIVE_EXEC_FMT</td>
1.156 leot 13032: </tr>
13033: <tr>
1.244 gutterid 13034: <td>NATIVE_MACHINE_PLATFORM</td>
1.242 gutterid 13035: <td>NATIVE_OBJECT_FMT</td>
1.156 leot 13036: </tr>
13037: <tr>
1.244 gutterid 13038: <td>NBPAX_PROGRAM_PREFIX</td>
1.242 gutterid 13039: <td>NETBSD_LOGIN_NAME</td>
1.156 leot 13040: </tr>
13041: <tr>
1.244 gutterid 13042: <td>NMH_EDITOR</td>
1.242 gutterid 13043: <td>NMH_MTA</td>
1.195 gutterid 13044: </tr>
13045: <tr>
1.244 gutterid 13046: <td>NMH_PAGER</td>
1.242 gutterid 13047: <td>NODE_VERSIONS_ACCEPTED</td>
1.156 leot 13048: </tr>
13049: <tr>
1.244 gutterid 13050: <td>NODE_VERSIONS_INCOMPATIBLE</td>
1.242 gutterid 13051: <td>NODE_VERSION_DEFAULT</td>
1.156 leot 13052: </tr>
13053: <tr>
1.244 gutterid 13054: <td>NODE_VERSION_REQD</td>
1.242 gutterid 13055: <td>NOLOGIN</td>
1.156 leot 13056: </tr>
13057: <tr>
1.244 gutterid 13058: <td>NOTE</td>
1.242 gutterid 13059: <td>NOT_FOR_PLATFORM</td>
1.156 leot 13060: </tr>
13061: <tr>
1.244 gutterid 13062: <td>NOT_PAX_ASLR_SAFE</td>
1.242 gutterid 13063: <td>NOT_PAX_MPROTECT_SAFE</td>
1.156 leot 13064: </tr>
13065: <tr>
1.244 gutterid 13066: <td>NO_BUILD</td>
1.242 gutterid 13067: <td>NO_CHECKSUM</td>
1.229 gutterid 13068: </tr>
13069: <tr>
1.244 gutterid 13070: <td>NO_CONFIGURE</td>
1.242 gutterid 13071: <td>NO_SKIP</td>
1.218 nia 13072: </tr>
13073: <tr>
1.244 gutterid 13074: <td>NS_PREFERRED</td>
1.242 gutterid 13075: <td>NULLMAILER_GROUP</td>
1.218 nia 13076: </tr>
13077: <tr>
1.244 gutterid 13078: <td>NULLMAILER_USER</td>
1.242 gutterid 13079: <td>OBJHOSTNAME</td>
1.156 leot 13080: </tr>
13081: <tr>
1.244 gutterid 13082: <td>OBJMACHINE</td>
1.242 gutterid 13083: <td>OCAML_FINDLIB_DIRS</td>
1.178 rillig 13084: </tr>
13085: <tr>
1.244 gutterid 13086: <td>OCAML_FINDLIB_REGISTER</td>
1.242 gutterid 13087: <td>OCAML_FINDLIB_REGISTER_VERBOSE</td>
1.156 leot 13088: </tr>
13089: <tr>
1.244 gutterid 13090: <td>OCAML_SITELIBDIR</td>
1.242 gutterid 13091: <td>OMF</td>
1.156 leot 13092: </tr>
13093: <tr>
1.244 gutterid 13094: <td>ONLY_FOR_COMPILER</td>
1.242 gutterid 13095: <td>ONLY_FOR_PLATFORM</td>
1.156 leot 13096: </tr>
13097: <tr>
1.244 gutterid 13098: <td>OPENSSH_CHROOT</td>
1.242 gutterid 13099: <td>OPENSSH_GROUP</td>
1.156 leot 13100: </tr>
13101: <tr>
1.244 gutterid 13102: <td>OPENSSH_USER</td>
1.242 gutterid 13103: <td>OPSYS</td>
1.156 leot 13104: </tr>
13105: <tr>
1.244 gutterid 13106: <td>OPSYS_EMULDIR</td>
1.242 gutterid 13107: <td>OPSYS_VERSION</td>
1.156 leot 13108: </tr>
13109: <tr>
1.244 gutterid 13110: <td>OS</td>
1.242 gutterid 13111: <td>OSS_TYPE</td>
1.156 leot 13112: </tr>
13113: <tr>
1.244 gutterid 13114: <td>OSX</td>
1.239 dholland 13115: <td>OS_VARIANT</td>
1.241 rillig 13116: </tr>
13117: <tr>
1.244 gutterid 13118: <td>OS_VERSION</td>
1.241 rillig 13119: <td>OTF_FONTS_DIR</td>
1.238 wiz 13120: </tr>
13121: <tr>
1.244 gutterid 13122: <td>OVERRIDE_DIRDEPTH</td>
1.241 rillig 13123: <td>OVERRIDE_GEMSPEC</td>
1.156 leot 13124: </tr>
13125: <tr>
1.244 gutterid 13126: <td>OVERRIDE_GNU_CONFIG_SCRIPTS</td>
1.249 gutterid 13127: <td>OWN_DIRS</td>
1.246 leot 13128: </tr>
13129: <tr>
13130: <td>OWN_DIRS_PERMS</td>
1.249 gutterid 13131: <td>P4GROUP</td>
1.233 wiz 13132: </tr>
13133: <tr>
1.246 leot 13134: <td>P4PORT</td>
1.249 gutterid 13135: <td>P4ROOT</td>
1.214 leot 13136: </tr>
13137: <tr>
1.246 leot 13138: <td>P4USER</td>
1.249 gutterid 13139: <td>PACKAGES</td>
1.227 wiz 13140: </tr>
13141: <tr>
1.246 leot 13142: <td>PALMOS_DEFAULT_SDK</td>
1.249 gutterid 13143: <td>PAMBASE</td>
1.205 wiz 13144: </tr>
13145: <tr>
1.246 leot 13146: <td>PAM_DEFAULT</td>
1.249 gutterid 13147: <td>PAPERSIZE</td>
1.161 leot 13148: </tr>
13149: <tr>
1.246 leot 13150: <td>PASSIVE_FETCH</td>
1.249 gutterid 13151: <td>PATCHDIR</td>
1.156 leot 13152: </tr>
13153: <tr>
1.246 leot 13154: <td>PATCHFILES</td>
1.249 gutterid 13155: <td>PATCH_ARGS</td>
1.156 leot 13156: </tr>
13157: <tr>
1.246 leot 13158: <td>PATCH_DEBUG</td>
1.249 gutterid 13159: <td>PATCH_DIST_ARGS</td>
1.156 leot 13160: </tr>
13161: <tr>
1.246 leot 13162: <td>PATCH_DIST_CAT</td>
1.249 gutterid 13163: <td>PATCH_DIST_STRIP</td>
1.156 leot 13164: </tr>
13165: <tr>
1.246 leot 13166: <td>PATCH_FUZZ_FACTOR</td>
1.249 gutterid 13167: <td>PATCH_STRIP</td>
1.156 leot 13168: </tr>
13169: <tr>
1.246 leot 13170: <td>PATH</td>
1.233 wiz 13171: <td>PCCBASE</td>
1.246 leot 13172: </tr>
13173: <tr>
1.244 gutterid 13174: <td>PEAR_CMD</td>
1.249 gutterid 13175: <td>PEAR_LIB</td>
1.227 wiz 13176: </tr>
13177: <tr>
1.244 gutterid 13178: <td>PEAR_PACKAGE_XML</td>
1.249 gutterid 13179: <td>PERL5</td>
1.156 leot 13180: </tr>
13181: <tr>
1.244 gutterid 13182: <td>PERL5_CONFIGURE</td>
1.249 gutterid 13183: <td>PERL5_CONFIGURE_DIRS</td>
1.217 rillig 13184: </tr>
13185: <tr>
1.244 gutterid 13186: <td>PERL5_LDFLAGS</td>
1.249 gutterid 13187: <td>PERL5_LICENSE</td>
1.205 wiz 13188: </tr>
13189: <tr>
1.244 gutterid 13190: <td>PERL5_MODULE_TYPE</td>
1.249 gutterid 13191: <td>PERL5_PACKLIST</td>
1.177 leot 13192: </tr>
13193: <tr>
1.244 gutterid 13194: <td>PERL5_PACKLIST_DIR</td>
1.249 gutterid 13195: <td>PERL5_PERLBASE</td>
1.161 leot 13196: </tr>
13197: <tr>
1.244 gutterid 13198: <td>PERL5_SITEBASE</td>
1.249 gutterid 13199: <td>PERL5_USE_PACKLIST</td>
1.161 leot 13200: </tr>
13201: <tr>
1.244 gutterid 13202: <td>PERL5_VENDORBASE</td>
1.249 gutterid 13203: <td>PFCTL</td>
1.156 leot 13204: </tr>
13205: <tr>
1.244 gutterid 13206: <td>PFVAR_H</td>
1.249 gutterid 13207: <td>PF_VERSION</td>
1.156 leot 13208: </tr>
13209: <tr>
1.244 gutterid 13210: <td>PGGROUP</td>
1.249 gutterid 13211: <td>PGHOME</td>
1.156 leot 13212: </tr>
13213: <tr>
1.244 gutterid 13214: <td>PGPKGSRCDIR</td>
1.249 gutterid 13215: <td>PGSQL_TYPE</td>
1.156 leot 13216: </tr>
13217: <tr>
1.244 gutterid 13218: <td>PGSQL_VERSION</td>
1.249 gutterid 13219: <td>PGSQL_VERSIONS_ACCEPTED</td>
1.156 leot 13220: </tr>
13221: <tr>
1.244 gutterid 13222: <td>PGSQL_VERSION_DEFAULT</td>
1.249 gutterid 13223: <td>PGUSER</td>
1.156 leot 13224: </tr>
13225: <tr>
1.244 gutterid 13226: <td>PG_LIB_EXT</td>
1.249 gutterid 13227: <td>PHP</td>
1.156 leot 13228: </tr>
13229: <tr>
1.244 gutterid 13230: <td>PHPCOMMON_MK</td>
1.249 gutterid 13231: <td>PHPPKGSRCDIR</td>
1.156 leot 13232: </tr>
13233: <tr>
1.244 gutterid 13234: <td>PHP_BASE_VERS</td>
1.249 gutterid 13235: <td>PHP_CHECK_INSTALLED</td>
1.156 leot 13236: </tr>
13237: <tr>
1.244 gutterid 13238: <td>PHP_EXTENSION_DIR</td>
1.249 gutterid 13239: <td>PHP_INITIAL_TEENY</td>
1.156 leot 13240: </tr>
13241: <tr>
1.244 gutterid 13242: <td>PHP_PKG_PREFIX</td>
1.249 gutterid 13243: <td>PHP_VERSION</td>
1.156 leot 13244: </tr>
13245: <tr>
1.244 gutterid 13246: <td>PHP_VERSIONS_ACCEPTED</td>
1.249 gutterid 13247: <td>PHP_VERSIONS_INCOMPATIBLE</td>
1.156 leot 13248: </tr>
13249: <tr>
1.244 gutterid 13250: <td>PHP_VERSION_DEFAULT</td>
1.249 gutterid 13251: <td>PHP_VERSION_REQD</td>
1.156 leot 13252: </tr>
13253: <tr>
1.244 gutterid 13254: <td>PILRC_USE_GTK</td>
1.249 gutterid 13255: <td>PKGCONFIG_BASE</td>
1.156 leot 13256: </tr>
13257: <tr>
1.244 gutterid 13258: <td>PKGCONFIG_FILE</td>
1.249 gutterid 13259: <td>PKGCONFIG_OVERRIDE</td>
1.156 leot 13260: </tr>
13261: <tr>
1.244 gutterid 13262: <td>PKGCONFIG_OVERRIDE_STAGE</td>
1.249 gutterid 13263: <td>PKGDIR</td>
1.156 leot 13264: </tr>
13265: <tr>
1.244 gutterid 13266: <td>PKGGNUDIR</td>
1.249 gutterid 13267: <td>PKGINFODIR</td>
1.156 leot 13268: </tr>
13269: <tr>
1.244 gutterid 13270: <td>PKGLOCALEDIR</td>
1.249 gutterid 13271: <td>PKGMANDIR</td>
1.156 leot 13272: </tr>
13273: <tr>
1.244 gutterid 13274: <td>PKGNAME</td>
1.249 gutterid 13275: <td>PKGNAME_REQD</td>
1.156 leot 13276: </tr>
13277: <tr>
1.244 gutterid 13278: <td>PKGPATH</td>
1.249 gutterid 13279: <td>PKGREVISION</td>
1.156 leot 13280: </tr>
13281: <tr>
1.244 gutterid 13282: <td>PKGSRC_BLAS_TYPES</td>
1.249 gutterid 13283: <td>PKGSRC_CHANGES</td>
1.156 leot 13284: </tr>
13285: <tr>
1.244 gutterid 13286: <td>PKGSRC_COMPILER</td>
1.249 gutterid 13287: <td>PKGSRC_KEEP_BIN_PKGS</td>
1.156 leot 13288: </tr>
13289: <tr>
1.244 gutterid 13290: <td>PKGSRC_LOCKTYPE</td>
1.249 gutterid 13291: <td>PKGSRC_MAKE_ENV</td>
1.156 leot 13292: </tr>
13293: <tr>
1.244 gutterid 13294: <td>PKGSRC_MESSAGE_RECIPIENTS</td>
1.249 gutterid 13295: <td>PKGSRC_MKPIE</td>
1.156 leot 13296: </tr>
13297: <tr>
1.244 gutterid 13298: <td>PKGSRC_MKREPRO</td>
1.249 gutterid 13299: <td>PKGSRC_OVERRIDE_MKPIE</td>
1.177 leot 13300: </tr>
13301: <tr>
1.244 gutterid 13302: <td>PKGSRC_RUN_TEST</td>
1.249 gutterid 13303: <td>PKGSRC_SETENV</td>
1.156 leot 13304: </tr>
13305: <tr>
1.244 gutterid 13306: <td>PKGSRC_SLEEPSECS</td>
1.249 gutterid 13307: <td>PKGSRC_TODO</td>
1.159 rillig 13308: </tr>
13309: <tr>
1.244 gutterid 13310: <td>PKGSRC_USE_CTF</td>
1.249 gutterid 13311: <td>PKGSRC_USE_FORTIFY</td>
1.156 leot 13312: </tr>
13313: <tr>
1.244 gutterid 13314: <td>PKGSRC_USE_MKTOOLS</td>
1.249 gutterid 13315: <td>PKGSRC_USE_RELRO</td>
1.156 leot 13316: </tr>
13317: <tr>
1.244 gutterid 13318: <td>PKGSRC_USE_SSP</td>
1.249 gutterid 13319: <td>PKGSRC_USE_STACK_CHECK</td>
1.156 leot 13320: </tr>
13321: <tr>
1.244 gutterid 13322: <td>PKGTASKS_DATAFILE</td>
1.249 gutterid 13323: <td>PKGTOOLS_ARGS</td>
1.156 leot 13324: </tr>
13325: <tr>
1.244 gutterid 13326: <td>PKGTOOLS_ENV</td>
1.249 gutterid 13327: <td>PKG_ALTERNATIVES</td>
1.156 leot 13328: </tr>
13329: <tr>
1.244 gutterid 13330: <td>PKG_APACHE</td>
1.249 gutterid 13331: <td>PKG_APACHE_ACCEPTED</td>
1.156 leot 13332: </tr>
13333: <tr>
1.244 gutterid 13334: <td>PKG_APACHE_DEFAULT</td>
1.249 gutterid 13335: <td>PKG_BEST_EXISTS</td>
1.156 leot 13336: </tr>
13337: <tr>
1.244 gutterid 13338: <td>PKG_BUILD_OPTIONS</td>
1.249 gutterid 13339: <td>PKG_COMPRESSION</td>
1.156 leot 13340: </tr>
13341: <tr>
1.244 gutterid 13342: <td>PKG_CONFIG</td>
1.249 gutterid 13343: <td>PKG_CONFIG_PERMS</td>
1.156 leot 13344: </tr>
13345: <tr>
1.244 gutterid 13346: <td>PKG_CREATE_USERGROUP</td>
1.249 gutterid 13347: <td>PKG_DB_TMPDIR</td>
1.156 leot 13348: </tr>
13349: <tr>
1.244 gutterid 13350: <td>PKG_DEBUG_LEVEL</td>
1.249 gutterid 13351: <td>PKG_DEFAULT_OPTIONS</td>
1.156 leot 13352: </tr>
13353: <tr>
1.244 gutterid 13354: <td>PKG_DESTDIR_SUPPORT</td>
1.249 gutterid 13355: <td>PKG_DEVELOPER</td>
1.156 leot 13356: </tr>
13357: <tr>
1.244 gutterid 13358: <td>PKG_DISABLED_OPTIONS</td>
1.249 gutterid 13359: <td>PKG_FATAL_ERRORS</td>
1.233 wiz 13360: </tr>
13361: <tr>
1.244 gutterid 13362: <td>PKG_FC</td>
1.249 gutterid 13363: <td>PKG_FILELIST_CMD</td>
1.246 leot 13364: </tr>
13365: <tr>
13366: <td>PKG_GECOS</td>
1.249 gutterid 13367: <td>PKG_GID</td>
1.156 leot 13368: </tr>
13369: <tr>
1.246 leot 13370: <td>PKG_GROUPS</td>
1.249 gutterid 13371: <td>PKG_GROUPS_VARS</td>
1.156 leot 13372: </tr>
13373: <tr>
1.246 leot 13374: <td>PKG_HOME</td>
1.249 gutterid 13375: <td>PKG_INIT_SCRIPTS</td>
1.156 leot 13376: </tr>
13377: <tr>
1.246 leot 13378: <td>PKG_JAVA_HOME</td>
1.249 gutterid 13379: <td>PKG_JVM</td>
1.156 leot 13380: </tr>
13381: <tr>
1.246 leot 13382: <td>PKG_JVMS_ACCEPTED</td>
1.249 gutterid 13383: <td>PKG_JVM_DEFAULT</td>
1.156 leot 13384: </tr>
13385: <tr>
1.246 leot 13386: <td>PKG_LEGACY_OPTIONS</td>
1.249 gutterid 13387: <td>PKG_LIBTOOL</td>
1.156 leot 13388: </tr>
13389: <tr>
1.246 leot 13390: <td>PKG_MKSYMLINKS</td>
1.249 gutterid 13391: <td>PKG_OPTIONS</td>
1.156 leot 13392: </tr>
13393: <tr>
1.246 leot 13394: <td>PKG_OPTIONS_DEPRECATED_WARNINGS</td>
1.249 gutterid 13395: <td>PKG_OPTIONS_LEGACY_OPTS</td>
1.156 leot 13396: </tr>
13397: <tr>
1.246 leot 13398: <td>PKG_OPTIONS_LEGACY_VARS</td>
1.249 gutterid 13399: <td>PKG_OPTIONS_NONEMPTY_SETS</td>
1.156 leot 13400: </tr>
13401: <tr>
1.246 leot 13402: <td>PKG_OPTIONS_OPTIONAL_GROUPS</td>
1.249 gutterid 13403: <td>PKG_OPTIONS_REQUIRED_GROUPS</td>
1.226 gutterid 13404: </tr>
13405: <tr>
1.246 leot 13406: <td>PKG_OPTIONS_VAR</td>
1.249 gutterid 13407: <td>PKG_PHP</td>
1.156 leot 13408: </tr>
13409: <tr>
1.246 leot 13410: <td>PKG_PHP_MAJOR_VERS</td>
1.249 gutterid 13411: <td>PKG_PHP_VERSION</td>
1.156 leot 13412: </tr>
13413: <tr>
1.246 leot 13414: <td>PKG_RCD_SCRIPTS</td>
1.249 gutterid 13415: <td>PKG_REFCOUNT_DBDIR</td>
1.156 leot 13416: </tr>
13417: <tr>
1.246 leot 13418: <td>PKG_REGISTER_SHELLS</td>
1.249 gutterid 13419: <td>PKG_RESUME_TRANSFERS</td>
1.156 leot 13420: </tr>
13421: <tr>
1.246 leot 13422: <td>PKG_SHELL</td>
1.249 gutterid 13423: <td>PKG_SUGGESTED_OPTIONS</td>
1.156 leot 13424: </tr>
13425: <tr>
1.246 leot 13426: <td>PKG_SUPPORTED_OPTIONS</td>
1.249 gutterid 13427: <td>PKG_SYSCONFBASE</td>
1.156 leot 13428: </tr>
13429: <tr>
1.246 leot 13430: <td>PKG_SYSCONFBASEDIR</td>
1.249 gutterid 13431: <td>PKG_SYSCONFDIR</td>
1.156 leot 13432: </tr>
13433: <tr>
1.246 leot 13434: <td>PKG_SYSCONFDIR_PERMS</td>
1.249 gutterid 13435: <td>PKG_SYSCONFSUBDIR</td>
1.156 leot 13436: </tr>
13437: <tr>
1.246 leot 13438: <td>PKG_SYSCONFVAR</td>
1.249 gutterid 13439: <td>PKG_TOOLS_BIN</td>
1.156 leot 13440: </tr>
13441: <tr>
1.246 leot 13442: <td>PKG_UID</td>
1.249 gutterid 13443: <td>PKG_UPDATE_FONTS_DB</td>
1.156 leot 13444: </tr>
13445: <tr>
1.246 leot 13446: <td>PKG_USERS</td>
1.249 gutterid 13447: <td>PKG_USERS_VARS</td>
1.156 leot 13448: </tr>
13449: <tr>
1.246 leot 13450: <td>PKG_VERBOSE</td>
1.249 gutterid 13451: <td>PLEASE</td>
1.156 leot 13452: </tr>
13453: <tr>
1.246 leot 13454: <td>PLIST</td>
1.249 gutterid 13455: <td>PLIST_AWK</td>
1.156 leot 13456: </tr>
13457: <tr>
1.246 leot 13458: <td>PLIST_AWK_ENV</td>
1.249 gutterid 13459: <td>PLIST_SRC</td>
1.156 leot 13460: </tr>
13461: <tr>
1.246 leot 13462: <td>PLIST_SUBST</td>
1.249 gutterid 13463: <td>PLIST_TYPE</td>
1.156 leot 13464: </tr>
13465: <tr>
1.246 leot 13466: <td>PLIST_VARS</td>
1.249 gutterid 13467: <td>POPTOP_USE_MPPE</td>
1.156 leot 13468: </tr>
13469: <tr>
1.246 leot 13470: <td>POSSIBLE_GFORTRAN_VERSION</td>
1.249 gutterid 13471: <td>POST_FETCH_HOOK</td>
1.156 leot 13472: </tr>
13473: <tr>
1.246 leot 13474: <td>PREFER</td>
1.249 gutterid 13475: <td>PREFER_NATIVE</td>
1.156 leot 13476: </tr>
13477: <tr>
1.246 leot 13478: <td>PREFER_NATIVE_PTHREADS</td>
1.249 gutterid 13479: <td>PREFER_PKGSRC</td>
1.156 leot 13480: </tr>
13481: <tr>
1.246 leot 13482: <td>PREFIX</td>
1.249 gutterid 13483: <td>PREPEND_PATH</td>
1.156 leot 13484: </tr>
13485: <tr>
1.246 leot 13486: <td>PRE_ROOT_CMD</td>
1.249 gutterid 13487: <td>PRIVILEGED_STAGES</td>
1.156 leot 13488: </tr>
13489: <tr>
1.246 leot 13490: <td>PS</td>
1.249 gutterid 13491: <td>PTHREAD_AUTO_VARS</td>
1.156 leot 13492: </tr>
13493: <tr>
1.246 leot 13494: <td>PTHREAD_CFLAGS</td>
1.249 gutterid 13495: <td>PTHREAD_LDFLAGS</td>
1.156 leot 13496: </tr>
13497: <tr>
1.246 leot 13498: <td>PTHREAD_LIBS</td>
1.249 gutterid 13499: <td>PTHREAD_OPTS</td>
1.156 leot 13500: </tr>
13501: <tr>
1.246 leot 13502: <td>PTHREAD_TYPE</td>
1.249 gutterid 13503: <td>PVM_SSH</td>
1.156 leot 13504: </tr>
13505: <tr>
1.246 leot 13506: <td>PYPKGPREFIX</td>
1.249 gutterid 13507: <td>PYTHON_FOR_BUILD_ONLY</td>
1.156 leot 13508: </tr>
13509: <tr>
1.246 leot 13510: <td>PYTHON_SELF_CONFLICT</td>
1.249 gutterid 13511: <td>PYTHON_VERSION</td>
1.156 leot 13512: </tr>
13513: <tr>
1.246 leot 13514: <td>PYTHON_VERSIONED_DEPENDENCIES</td>
1.249 gutterid 13515: <td>PYTHON_VERSIONS_ACCEPTED</td>
1.156 leot 13516: </tr>
13517: <tr>
1.246 leot 13518: <td>PYTHON_VERSIONS_INCOMPATIBLE</td>
1.249 gutterid 13519: <td>PYTHON_VERSION_DEFAULT</td>
1.156 leot 13520: </tr>
13521: <tr>
1.246 leot 13522: <td>PYTHON_VERSION_REQD</td>
1.249 gutterid 13523: <td>PYVERSSUFFIX</td>
1.156 leot 13524: </tr>
13525: <tr>
1.246 leot 13526: <td>QMAILDIR</td>
1.249 gutterid 13527: <td>QMAIL_ALIAS_USER</td>
1.156 leot 13528: </tr>
13529: <tr>
1.246 leot 13530: <td>QMAIL_DAEMON_USER</td>
1.249 gutterid 13531: <td>QMAIL_LOG_USER</td>
1.156 leot 13532: </tr>
13533: <tr>
1.246 leot 13534: <td>QMAIL_NOFILES_GROUP</td>
1.249 gutterid 13535: <td>QMAIL_PASSWD_USER</td>
1.156 leot 13536: </tr>
13537: <tr>
1.246 leot 13538: <td>QMAIL_QMAIL_GROUP</td>
1.249 gutterid 13539: <td>QMAIL_QUEUE_DIR</td>
1.156 leot 13540: </tr>
13541: <tr>
1.246 leot 13542: <td>QMAIL_QUEUE_EXTRA</td>
1.249 gutterid 13543: <td>QMAIL_QUEUE_USER</td>
1.156 leot 13544: </tr>
13545: <tr>
1.246 leot 13546: <td>QMAIL_REMOTE_USER</td>
1.249 gutterid 13547: <td>QMAIL_ROOT_USER</td>
1.156 leot 13548: </tr>
13549: <tr>
1.246 leot 13550: <td>QMAIL_SEND_USER</td>
1.249 gutterid 13551: <td>QORE_LATEST_MODULE_API</td>
1.156 leot 13552: </tr>
13553: <tr>
1.246 leot 13554: <td>QORE_MODULE_API</td>
1.249 gutterid 13555: <td>QORE_MODULE_DIR</td>
1.156 leot 13556: </tr>
13557: <tr>
1.246 leot 13558: <td>QORE_USER_MODULE_DIR</td>
1.249 gutterid 13559: <td>QORE_VERSION</td>
1.156 leot 13560: </tr>
13561: <tr>
1.246 leot 13562: <td>QPOPPER_FAC</td>
1.249 gutterid 13563: <td>QPOPPER_SPOOL_DIR</td>
1.156 leot 13564: </tr>
13565: <tr>
1.246 leot 13566: <td>QPOPPER_USER</td>
1.249 gutterid 13567: <td>RAKE_NAME</td>
1.156 leot 13568: </tr>
13569: <tr>
1.246 leot 13570: <td>RASMOL_DEPTH</td>
1.249 gutterid 13571: <td>RCD_SCRIPTS</td>
1.246 leot 13572: </tr>
13573: <tr>
13574: <td>RCD_SCRIPTS_DIR</td>
1.249 gutterid 13575: <td>RCD_SCRIPTS_EXAMPLEDIR</td>
1.218 nia 13576: </tr>
13577: <tr>
1.246 leot 13578: <td>RCD_SCRIPTS_MODE</td>
1.249 gutterid 13579: <td>RCD_SCRIPTS_SHELL</td>
1.227 wiz 13580: </tr>
13581: <tr>
1.246 leot 13582: <td>RCD_SCRIPT_SRC</td>
1.239 dholland 13583: <td>RDOC</td>
1.241 rillig 13584: </tr>
13585: <tr>
1.244 gutterid 13586: <td>READLINE_DEFAULT</td>
1.241 rillig 13587: <td>READLINE_TYPE</td>
1.214 leot 13588: </tr>
13589: <tr>
1.244 gutterid 13590: <td>REAL_ROOT_GROUP</td>
1.241 rillig 13591: <td>REAL_ROOT_USER</td>
1.205 wiz 13592: </tr>
13593: <tr>
1.244 gutterid 13594: <td>RECURSIVE_MAKE</td>
1.241 rillig 13595: <td>RELAY_CTRL_DIR</td>
1.223 nia 13596: </tr>
13597: <tr>
1.244 gutterid 13598: <td>RELRO_SUPPORTED</td>
1.241 rillig 13599: <td>REPLACE_AWK</td>
1.177 leot 13600: </tr>
13601: <tr>
1.244 gutterid 13602: <td>REPLACE_BASH</td>
1.241 rillig 13603: <td>REPLACE_CSH</td>
1.214 leot 13604: </tr>
13605: <tr>
1.244 gutterid 13606: <td>REPLACE_KSH</td>
1.241 rillig 13607: <td>REPLACE_LUA</td>
1.212 wiz 13608: </tr>
13609: <tr>
1.244 gutterid 13610: <td>REPLACE_NODEJS</td>
1.241 rillig 13611: <td>REPLACE_OCTAVE</td>
1.156 leot 13612: </tr>
13613: <tr>
1.244 gutterid 13614: <td>REPLACE_PERL</td>
1.241 rillig 13615: <td>REPLACE_PERL6</td>
1.205 wiz 13616: </tr>
13617: <tr>
1.244 gutterid 13618: <td>REPLACE_PHP</td>
1.241 rillig 13619: <td>REPLACE_PYTHON</td>
1.197 leot 13620: </tr>
13621: <tr>
1.244 gutterid 13622: <td>REPLACE_QORE</td>
1.241 rillig 13623: <td>REPLACE_R</td>
1.156 leot 13624: </tr>
13625: <tr>
1.244 gutterid 13626: <td>REPLACE_RUBY</td>
1.241 rillig 13627: <td>REPLACE_RUBY_DIRS</td>
1.218 nia 13628: </tr>
13629: <tr>
1.244 gutterid 13630: <td>REPLACE_RUBY_PAT</td>
1.241 rillig 13631: <td>REPLACE_SH</td>
1.161 leot 13632: </tr>
13633: <tr>
1.244 gutterid 13634: <td>REPLACE_TEXLUA</td>
1.241 rillig 13635: <td>REPLACE_WISH</td>
1.216 gutterid 13636: </tr>
13637: <tr>
1.244 gutterid 13638: <td>REQD_DIRS</td>
1.241 rillig 13639: <td>REQD_DIRS_PERMS</td>
1.156 leot 13640: </tr>
13641: <tr>
1.244 gutterid 13642: <td>REQD_FILES</td>
1.241 rillig 13643: <td>REQD_FILES_MODE</td>
1.218 nia 13644: </tr>
13645: <tr>
1.244 gutterid 13646: <td>REQD_FILES_PERMS</td>
1.241 rillig 13647: <td>RESOLV_AUTO_VARS</td>
1.156 leot 13648: </tr>
13649: <tr>
1.244 gutterid 13650: <td>RESOLV_LDFLAGS</td>
1.241 rillig 13651: <td>RESOLV_LIBS</td>
1.238 wiz 13652: </tr>
13653: <tr>
1.244 gutterid 13654: <td>RM</td>
1.232 gutterid 13655: <td>ROOT_CMD</td>
1.241 rillig 13656: </tr>
13657: <tr>
1.244 gutterid 13658: <td>ROOT_GROUP</td>
1.241 rillig 13659: <td>ROOT_USER</td>
1.156 leot 13660: </tr>
13661: <tr>
1.244 gutterid 13662: <td>RPCGEN</td>
1.241 rillig 13663: <td>RPM</td>
1.156 leot 13664: </tr>
13665: <tr>
1.244 gutterid 13666: <td>RPM2PKG_PLIST</td>
1.241 rillig 13667: <td>RPM2PKG_PREFIX</td>
1.205 wiz 13668: </tr>
13669: <tr>
1.244 gutterid 13670: <td>RPM2PKG_STAGE</td>
1.241 rillig 13671: <td>RPM2PKG_STRIP</td>
1.217 rillig 13672: </tr>
13673: <tr>
1.244 gutterid 13674: <td>RPM2PKG_SUBPREFIX</td>
1.241 rillig 13675: <td>RPMFILES</td>
1.214 leot 13676: </tr>
13677: <tr>
1.244 gutterid 13678: <td>RPMIGNOREPATH</td>
1.241 rillig 13679: <td>RPM_DB_PREFIX</td>
1.212 wiz 13680: </tr>
13681: <tr>
1.244 gutterid 13682: <td>RSSH_CVS_PATH</td>
1.241 rillig 13683: <td>RSSH_RDIST_PATH</td>
1.156 leot 13684: </tr>
13685: <tr>
1.244 gutterid 13686: <td>RSSH_RSYNC_PATH</td>
1.241 rillig 13687: <td>RSSH_SCP_PATH</td>
1.197 leot 13688: </tr>
13689: <tr>
1.244 gutterid 13690: <td>RSSH_SFTP_SERVER_PATH</td>
1.241 rillig 13691: <td>RUBY</td>
1.156 leot 13692: </tr>
13693: <tr>
1.244 gutterid 13694: <td>RUBYGEM</td>
1.241 rillig 13695: <td>RUBYGEM_MANPAGES</td>
1.156 leot 13696: </tr>
13697: <tr>
1.244 gutterid 13698: <td>RUBYGEM_NAME</td>
1.241 rillig 13699: <td>RUBYGEM_OPTIONS</td>
1.156 leot 13700: </tr>
13701: <tr>
1.244 gutterid 13702: <td>RUBYGEM_USE_MANPAGES</td>
1.241 rillig 13703: <td>RUBYGEM_VERBOSE</td>
1.231 jnemeth 13704: </tr>
13705: <tr>
1.244 gutterid 13706: <td>RUBY_ABI_VERSION</td>
1.241 rillig 13707: <td>RUBY_ARCH</td>
1.156 leot 13708: </tr>
13709: <tr>
1.244 gutterid 13710: <td>RUBY_ARCHINC</td>
1.241 rillig 13711: <td>RUBY_ARCHLIB</td>
1.156 leot 13712: </tr>
13713: <tr>
1.244 gutterid 13714: <td>RUBY_BASE</td>
1.241 rillig 13715: <td>RUBY_BASERIDIR</td>
1.156 leot 13716: </tr>
13717: <tr>
1.244 gutterid 13718: <td>RUBY_BUILD_DOCUMENT</td>
1.241 rillig 13719: <td>RUBY_DLEXT</td>
1.156 leot 13720: </tr>
13721: <tr>
1.244 gutterid 13722: <td>RUBY_DOC</td>
1.241 rillig 13723: <td>RUBY_DYNAMIC_DIRS</td>
1.156 leot 13724: </tr>
13725: <tr>
1.244 gutterid 13726: <td>RUBY_EG</td>
1.241 rillig 13727: <td>RUBY_ENCODING_ARG</td>
1.156 leot 13728: </tr>
13729: <tr>
1.244 gutterid 13730: <td>RUBY_EXTCONF</td>
1.241 rillig 13731: <td>RUBY_EXTCONF_CHECK</td>
1.156 leot 13732: </tr>
13733: <tr>
1.244 gutterid 13734: <td>RUBY_EXTCONF_DEBUG</td>
1.241 rillig 13735: <td>RUBY_EXTCONF_MAKEFILE</td>
1.198 leot 13736: </tr>
13737: <tr>
1.244 gutterid 13738: <td>RUBY_GEM_ARCH</td>
1.241 rillig 13739: <td>RUBY_GEM_BASE</td>
1.156 leot 13740: </tr>
13741: <tr>
1.244 gutterid 13742: <td>RUBY_INC</td>
1.241 rillig 13743: <td>RUBY_LIB</td>
1.156 leot 13744: </tr>
13745: <tr>
1.244 gutterid 13746: <td>RUBY_LIB_BASE</td>
1.241 rillig 13747: <td>RUBY_NAME</td>
1.156 leot 13748: </tr>
13749: <tr>
1.244 gutterid 13750: <td>RUBY_NOVERSION</td>
1.241 rillig 13751: <td>RUBY_PKGPREFIX</td>
1.156 leot 13752: </tr>
13753: <tr>
1.244 gutterid 13754: <td>RUBY_RAILS</td>
13755: <td>RUBY_RAILS61_VERSION</td>
1.223 nia 13756: </tr>
13757: <tr>
1.242 gutterid 13758: <td>RUBY_RAILS70_VERSION</td>
1.251 gutterid 13759: <td>RUBY_RAILS71_VERSION</td>
1.156 leot 13760: </tr>
13761: <tr>
1.251 gutterid 13762: <td>RUBY_RAILS_ACCEPTED</td>
1.242 gutterid 13763: <td>RUBY_RAILS_DEFAULT</td>
1.156 leot 13764: </tr>
13765: <tr>
1.251 gutterid 13766: <td>RUBY_RAILS_REQD</td>
1.242 gutterid 13767: <td>RUBY_RAILS_STRICT_DEP</td>
1.156 leot 13768: </tr>
13769: <tr>
1.251 gutterid 13770: <td>RUBY_RIDIR</td>
1.242 gutterid 13771: <td>RUBY_SETUP</td>
1.156 leot 13772: </tr>
13773: <tr>
1.251 gutterid 13774: <td>RUBY_SHLIB</td>
1.242 gutterid 13775: <td>RUBY_SHLIBALIAS</td>
1.156 leot 13776: </tr>
13777: <tr>
1.251 gutterid 13778: <td>RUBY_SHLIBVER</td>
1.242 gutterid 13779: <td>RUBY_SIMPLE_INSTALL</td>
1.156 leot 13780: </tr>
13781: <tr>
1.251 gutterid 13782: <td>RUBY_SITEARCHLIB</td>
1.242 gutterid 13783: <td>RUBY_SITELIB</td>
1.156 leot 13784: </tr>
13785: <tr>
1.251 gutterid 13786: <td>RUBY_SITELIB_BASE</td>
1.242 gutterid 13787: <td>RUBY_SITERIDIR</td>
1.156 leot 13788: </tr>
13789: <tr>
1.251 gutterid 13790: <td>RUBY_SLEXT</td>
1.242 gutterid 13791: <td>RUBY_SRCDIR</td>
1.156 leot 13792: </tr>
13793: <tr>
1.251 gutterid 13794: <td>RUBY_STATICLIB</td>
1.242 gutterid 13795: <td>RUBY_SUFFIX</td>
1.174 leot 13796: </tr>
13797: <tr>
1.251 gutterid 13798: <td>RUBY_SYSRIDIR</td>
1.242 gutterid 13799: <td>RUBY_USE_PTHREAD</td>
1.156 leot 13800: </tr>
13801: <tr>
1.251 gutterid 13802: <td>RUBY_VENDORARCHLIB</td>
1.242 gutterid 13803: <td>RUBY_VENDORLIB</td>
1.156 leot 13804: </tr>
13805: <tr>
1.251 gutterid 13806: <td>RUBY_VENDORLIB_BASE</td>
1.242 gutterid 13807: <td>RUBY_VER</td>
1.156 leot 13808: </tr>
13809: <tr>
1.251 gutterid 13810: <td>RUBY_VERSION</td>
1.242 gutterid 13811: <td>RUBY_VERSIONS_ACCEPTED</td>
1.156 leot 13812: </tr>
13813: <tr>
1.251 gutterid 13814: <td>RUBY_VERSIONS_INCOMPATIBLE</td>
1.242 gutterid 13815: <td>RUBY_VERSION_DEFAULT</td>
1.156 leot 13816: </tr>
13817: <tr>
1.251 gutterid 13818: <td>RUBY_VERSION_REQD</td>
1.242 gutterid 13819: <td>RUBY_VER_DIR</td>
1.156 leot 13820: </tr>
13821: <tr>
1.251 gutterid 13822: <td>RUN</td>
1.242 gutterid 13823: <td>RUN_LDCONFIG</td>
1.156 leot 13824: </tr>
13825: <tr>
1.251 gutterid 13826: <td>RUST_TYPE</td>
1.242 gutterid 13827: <td>SCO</td>
1.156 leot 13828: </tr>
13829: <tr>
1.251 gutterid 13830: <td>SCREWS_GROUP</td>
1.242 gutterid 13831: <td>SCREWS_USER</td>
1.156 leot 13832: </tr>
13833: <tr>
1.251 gutterid 13834: <td>SCRIPTS_ENV</td>
1.242 gutterid 13835: <td>SCROLLKEEPER_DATADIR</td>
1.156 leot 13836: </tr>
13837: <tr>
1.251 gutterid 13838: <td>SCROLLKEEPER_REBUILDDB</td>
1.242 gutterid 13839: <td>SCROLLKEEPER_UPDATEDB</td>
1.156 leot 13840: </tr>
13841: <tr>
1.251 gutterid 13842: <td>SDIST_PAWD</td>
1.242 gutterid 13843: <td>SDL12_TYPE</td>
1.156 leot 13844: </tr>
13845: <tr>
1.251 gutterid 13846: <td>SERIAL_DEVICES</td>
1.242 gutterid 13847: <td>SETGIDGAME</td>
1.156 leot 13848: </tr>
13849: <tr>
1.251 gutterid 13850: <td>SETGID_GAMES_PERMS</td>
1.242 gutterid 13851: <td>SETUID_ROOT_PERMS</td>
1.156 leot 13852: </tr>
13853: <tr>
1.251 gutterid 13854: <td>SH</td>
1.238 wiz 13855: <td>SHLIB</td>
1.246 leot 13856: </tr>
13857: <tr>
1.251 gutterid 13858: <td>SIGN_PACKAGES</td>
1.246 leot 13859: <td>SILC_CLIENT_WITH_PERL</td>
1.233 wiz 13860: </tr>
13861: <tr>
1.251 gutterid 13862: <td>SITE_SPECIFIC_PKGS</td>
1.246 leot 13863: <td>SKIP_DEPENDS</td>
1.156 leot 13864: </tr>
13865: <tr>
1.251 gutterid 13866: <td>SMF_INSTANCES</td>
1.246 leot 13867: <td>SMF_MANIFEST</td>
1.227 wiz 13868: </tr>
13869: <tr>
1.251 gutterid 13870: <td>SMF_METHODS</td>
1.246 leot 13871: <td>SMF_METHOD_SHELL</td>
1.156 leot 13872: </tr>
13873: <tr>
1.251 gutterid 13874: <td>SMF_METHOD_SRC</td>
1.246 leot 13875: <td>SMF_NAME</td>
1.156 leot 13876: </tr>
13877: <tr>
1.251 gutterid 13878: <td>SMF_PREFIX</td>
1.246 leot 13879: <td>SMF_SRCDIR</td>
1.177 leot 13880: </tr>
13881: <tr>
1.251 gutterid 13882: <td>SNIPROXY_GROUP</td>
1.246 leot 13883: <td>SNIPROXY_USER</td>
1.156 leot 13884: </tr>
13885: <tr>
1.251 gutterid 13886: <td>SOURCE_BUFFSIZE</td>
1.246 leot 13887: <td>SPECIAL_PERMS</td>
1.217 rillig 13888: </tr>
13889: <tr>
1.251 gutterid 13890: <td>SPECIFIC_PKGS</td>
1.246 leot 13891: <td>SSH_SUID</td>
1.156 leot 13892: </tr>
13893: <tr>
1.251 gutterid 13894: <td>SSP_SUPPORTED</td>
1.246 leot 13895: <td>SSYNC_PAWD</td>
1.159 rillig 13896: </tr>
13897: <tr>
1.251 gutterid 13898: <td>STEP_MSG</td>
1.246 leot 13899: <td>STRIP</td>
1.156 leot 13900: </tr>
13901: <tr>
1.251 gutterid 13902: <td>STRIP_DBG</td>
1.246 leot 13903: <td>STRIP_DEBUG</td>
1.156 leot 13904: </tr>
13905: <tr>
1.251 gutterid 13906: <td>STRIP_DEBUG_SUPPORTED</td>
1.246 leot 13907: <td>STRIP_FILES_SKIP</td>
1.156 leot 13908: </tr>
13909: <tr>
1.251 gutterid 13910: <td>SU</td>
1.246 leot 13911: <td>SUBDIR</td>
1.156 leot 13912: </tr>
13913: <tr>
1.251 gutterid 13914: <td>SUBST</td>
1.246 leot 13915: <td>SUBST_CLASSES</td>
1.156 leot 13916: </tr>
13917: <tr>
1.251 gutterid 13918: <td>SUBST_FILES</td>
1.246 leot 13919: <td>SUBST_FILTER_CMD</td>
1.156 leot 13920: </tr>
13921: <tr>
1.251 gutterid 13922: <td>SUBST_MESSAGE</td>
1.246 leot 13923: <td>SUBST_NOOP_OK</td>
1.156 leot 13924: </tr>
13925: <tr>
1.251 gutterid 13926: <td>SUBST_SED</td>
1.246 leot 13927: <td>SUBST_SHOW_DIFF</td>
1.156 leot 13928: </tr>
13929: <tr>
1.251 gutterid 13930: <td>SUBST_SKIP_TEXT_CHECK</td>
1.246 leot 13931: <td>SUBST_STAGE</td>
1.156 leot 13932: </tr>
13933: <tr>
1.251 gutterid 13934: <td>SUBST_VARS</td>
1.246 leot 13935: <td>SUNWSPROBASE</td>
1.156 leot 13936: </tr>
13937: <tr>
1.251 gutterid 13938: <td>SUSE_PREFER</td>
1.246 leot 13939: <td>SU_CMD</td>
13940: </tr>
13941: <tr>
1.251 gutterid 13942: <td>SYSCONFBASE</td>
1.246 leot 13943: <td>TARGET_ARCH</td>
1.238 wiz 13944: </tr>
13945: <tr>
1.251 gutterid 13946: <td>TBL</td>
1.246 leot 13947: <td>TERMCAP_TYPE</td>
1.156 leot 13948: </tr>
13949: <tr>
1.251 gutterid 13950: <td>TERMINFO_DEFAULT</td>
1.246 leot 13951: <td>TERMINFO_TYPE</td>
1.227 wiz 13952: </tr>
13953: <tr>
1.251 gutterid 13954: <td>TEST</td>
1.246 leot 13955: <td>TEST_DEPENDS</td>
1.156 leot 13956: </tr>
13957: <tr>
1.251 gutterid 13958: <td>TEST_DIRS</td>
1.246 leot 13959: <td>TEST_ENV</td>
1.217 rillig 13960: </tr>
13961: <tr>
1.251 gutterid 13962: <td>TEST_ENV_SHELL</td>
1.246 leot 13963: <td>TEST_MAKE_CMD</td>
1.212 wiz 13964: </tr>
13965: <tr>
1.251 gutterid 13966: <td>TEST_MAKE_FLAGS</td>
1.246 leot 13967: <td>TEST_TARGET</td>
1.217 rillig 13968: </tr>
13969: <tr>
1.251 gutterid 13970: <td>TEXLIVE_IGNORE_PATTERNS</td>
1.246 leot 13971: <td>TEXLIVE_REV</td>
1.205 wiz 13972: </tr>
13973: <tr>
1.251 gutterid 13974: <td>TEXLIVE_UNVERSIONED</td>
1.246 leot 13975: <td>TEXMFSITE</td>
1.189 bacon 13976: </tr>
13977: <tr>
1.251 gutterid 13978: <td>TEX_FORMATS</td>
1.246 leot 13979: <td>TEX_HYPHEN_DAT</td>
1.161 leot 13980: </tr>
13981: <tr>
1.251 gutterid 13982: <td>TEX_HYPHEN_DEF</td>
1.246 leot 13983: <td>TEX_TEXMF_DIRS</td>
1.159 rillig 13984: </tr>
13985: <tr>
1.251 gutterid 13986: <td>THTTPD_LOG_FACILITY</td>
1.246 leot 13987: <td>TINYDYN_USER</td>
1.156 leot 13988: </tr>
13989: <tr>
1.251 gutterid 13990: <td>TLSWRAPPER_CHROOT</td>
1.246 leot 13991: <td>TO</td>
1.156 leot 13992: </tr>
13993: <tr>
1.251 gutterid 13994: <td>TOOLS_ALIASES</td>
1.246 leot 13995: <td>TOOLS_ALWAYS_WRAP</td>
1.156 leot 13996: </tr>
13997: <tr>
1.251 gutterid 13998: <td>TOOLS_ARGS</td>
1.246 leot 13999: <td>TOOLS_BROKEN</td>
1.156 leot 14000: </tr>
14001: <tr>
1.251 gutterid 14002: <td>TOOLS_CMD</td>
1.246 leot 14003: <td>TOOLS_CMDLINE_SED</td>
1.156 leot 14004: </tr>
14005: <tr>
1.251 gutterid 14006: <td>TOOLS_CREATE</td>
1.246 leot 14007: <td>TOOLS_CROSS_DESTDIR</td>
1.156 leot 14008: </tr>
14009: <tr>
1.251 gutterid 14010: <td>TOOLS_DIR</td>
1.246 leot 14011: <td>TOOLS_FAIL</td>
1.156 leot 14012: </tr>
14013: <tr>
1.251 gutterid 14014: <td>TOOLS_GNU_MISSING</td>
1.246 leot 14015: <td>TOOLS_LDCONFIG</td>
1.156 leot 14016: </tr>
14017: <tr>
1.251 gutterid 14018: <td>TOOLS_NOOP</td>
1.246 leot 14019: <td>TOOLS_PATH</td>
1.156 leot 14020: </tr>
14021: <tr>
1.251 gutterid 14022: <td>TOOLS_SCRIPT</td>
1.246 leot 14023: <td>TOOLS_USE_CROSS_COMPILE</td>
1.156 leot 14024: </tr>
14025: <tr>
1.251 gutterid 14026: <td>TOOL_DEPENDS</td>
1.242 gutterid 14027: <td>TTF_FONTS_DIR</td>
1.241 rillig 14028: </tr>
14029: <tr>
1.251 gutterid 14030: <td>TYPE</td>
1.242 gutterid 14031: <td>UAC_REQD_EXECS</td>
1.238 wiz 14032: </tr>
14033: <tr>
1.251 gutterid 14034: <td>UCSPI_SSL_GROUP</td>
1.242 gutterid 14035: <td>UCSPI_SSL_USER</td>
1.156 leot 14036: </tr>
14037: <tr>
1.251 gutterid 14038: <td>UNLIMIT_RESOURCES</td>
1.242 gutterid 14039: <td>UNPRIVILEGED</td>
1.223 nia 14040: </tr>
14041: <tr>
1.251 gutterid 14042: <td>UNPRIVILEGED_GROUP</td>
1.242 gutterid 14043: <td>UNPRIVILEGED_GROUPS</td>
1.156 leot 14044: </tr>
14045: <tr>
1.251 gutterid 14046: <td>UNPRIVILEGED_USER</td>
1.242 gutterid 14047: <td>UNWRAP_FILES</td>
1.212 wiz 14048: </tr>
14049: <tr>
1.251 gutterid 14050: <td>UNWRAP_PATTERNS</td>
1.242 gutterid 14051: <td>UPDATE_GEMSPEC</td>
1.156 leot 14052: </tr>
14053: <tr>
1.251 gutterid 14054: <td>UPDATE_TARGET</td>
1.242 gutterid 14055: <td>URI</td>
1.156 leot 14056: </tr>
14057: <tr>
1.251 gutterid 14058: <td>USERGROUP_PHASE</td>
1.242 gutterid 14059: <td>USERPPP_GROUP</td>
1.156 leot 14060: </tr>
14061: <tr>
1.251 gutterid 14062: <td>USER_SPECIFIC_PKGS</td>
1.242 gutterid 14063: <td>USE_ABI_DEPENDS</td>
1.156 leot 14064: </tr>
14065: <tr>
1.251 gutterid 14066: <td>USE_APR</td>
1.242 gutterid 14067: <td>USE_BSD_MAKEFILE</td>
1.156 leot 14068: </tr>
14069: <tr>
1.251 gutterid 14070: <td>USE_BUILTIN</td>
1.243 gutterid 14071: <td>USE_CC_FEATURES</td>
14072: </tr>
14073: <tr>
1.251 gutterid 14074: <td>USE_CROSS_COMPILE</td>
1.243 gutterid 14075: <td>USE_CURSES</td>
1.156 leot 14076: </tr>
14077: <tr>
1.251 gutterid 14078: <td>USE_CWRAPPERS</td>
1.243 gutterid 14079: <td>USE_CXX_FEATURES</td>
1.156 leot 14080: </tr>
14081: <tr>
1.251 gutterid 14082: <td>USE_DB185</td>
1.242 gutterid 14083: <td>USE_FEATURES</td>
1.156 leot 14084: </tr>
14085: <tr>
1.251 gutterid 14086: <td>USE_GAMESGROUP</td>
1.242 gutterid 14087: <td>USE_GCC_RUNTIME</td>
1.156 leot 14088: </tr>
14089: <tr>
1.251 gutterid 14090: <td>USE_IMAKE</td>
1.242 gutterid 14091: <td>USE_JAVA</td>
1.205 wiz 14092: </tr>
14093: <tr>
1.251 gutterid 14094: <td>USE_JAVA2</td>
1.242 gutterid 14095: <td>USE_LANGUAGES</td>
1.156 leot 14096: </tr>
14097: <tr>
1.251 gutterid 14098: <td>USE_LIBTOOL</td>
1.242 gutterid 14099: <td>USE_NATIVE_GCC</td>
1.156 leot 14100: </tr>
14101: <tr>
1.251 gutterid 14102: <td>USE_NETBSD_REPO</td>
1.242 gutterid 14103: <td>USE_PKGSRC_GCC</td>
1.156 leot 14104: </tr>
14105: <tr>
1.251 gutterid 14106: <td>USE_PKGSRC_GCC_RUNTIME</td>
1.242 gutterid 14107: <td>USE_PKGTASKS</td>
1.156 leot 14108: </tr>
14109: <tr>
1.251 gutterid 14110: <td>USE_PKG_ADMIN_DIGEST</td>
1.242 gutterid 14111: <td>USE_RUBY_EXTCONF</td>
1.156 leot 14112: </tr>
14113: <tr>
1.251 gutterid 14114: <td>USE_RUBY_INSTALL</td>
1.242 gutterid 14115: <td>USE_RUBY_SETUP</td>
1.156 leot 14116: </tr>
14117: <tr>
1.251 gutterid 14118: <td>USE_RUBY_SETUP_PKG</td>
1.242 gutterid 14119: <td>USE_TOOLS</td>
1.156 leot 14120: </tr>
14121: <tr>
1.251 gutterid 14122: <td>UUCP_GROUP</td>
1.242 gutterid 14123: <td>UUCP_USER</td>
1.156 leot 14124: </tr>
14125: <tr>
1.251 gutterid 14126: <td>VARBASE</td>
1.242 gutterid 14127: <td>VARNAME</td>
1.156 leot 14128: </tr>
14129: <tr>
1.251 gutterid 14130: <td>VIM_EXTRA_OPTS</td>
1.242 gutterid 14131: <td>WARNING_MSG</td>
1.156 leot 14132: </tr>
14133: <tr>
1.251 gutterid 14134: <td>WCALC_CGIDIR</td>
1.242 gutterid 14135: <td>WCALC_CGIPATH</td>
1.156 leot 14136: </tr>
14137: <tr>
1.251 gutterid 14138: <td>WCALC_HTMLDIR</td>
1.242 gutterid 14139: <td>WCALC_HTMLPATH</td>
1.156 leot 14140: </tr>
14141: <tr>
1.251 gutterid 14142: <td>WDM_MANAGERS</td>
1.242 gutterid 14143: <td>WRAPPER_CC</td>
1.156 leot 14144: </tr>
14145: <tr>
1.251 gutterid 14146: <td>WRAPPER_REORDER_CMDS</td>
1.242 gutterid 14147: <td>WRKDIR</td>
1.156 leot 14148: </tr>
14149: <tr>
1.251 gutterid 14150: <td>WRKDIR_BASENAME</td>
1.242 gutterid 14151: <td>WRKDIR_LOCKTYPE</td>
1.156 leot 14152: </tr>
14153: <tr>
1.251 gutterid 14154: <td>WRKLOG</td>
1.242 gutterid 14155: <td>WRKOBJDIR</td>
1.156 leot 14156: </tr>
14157: <tr>
1.251 gutterid 14158: <td>WRKSRC</td>
1.242 gutterid 14159: <td>X10_PORT</td>
1.156 leot 14160: </tr>
14161: <tr>
1.251 gutterid 14162: <td>X11</td>
1.242 gutterid 14163: <td>X11BASE</td>
1.156 leot 14164: </tr>
14165: <tr>
1.251 gutterid 14166: <td>X11_PKGSRCDIR</td>
1.242 gutterid 14167: <td>X11_TYPE</td>
1.156 leot 14168: </tr>
14169: <tr>
1.251 gutterid 14170: <td>X509_CERTIFICATE</td>
1.242 gutterid 14171: <td>X509_KEY</td>
1.189 bacon 14172: </tr>
14173: <tr>
1.251 gutterid 14174: <td>XAW_TYPE</td>
1.242 gutterid 14175: <td>XLOCK_DEFAULT_MODE</td>
1.156 leot 14176: </tr>
14177: <tr>
1.251 gutterid 14178: <td>XMKMF</td>
1.242 gutterid 14179: <td>XMKMF_FLAGS</td>
1.156 leot 14180: </tr>
14181: <tr>
1.251 gutterid 14182: <td>XXX</td>
1.239 dholland 14183: <td>YES</td>
1.246 leot 14184: </tr>
14185: <tr>
1.251 gutterid 14186: <td>ZSH_STATIC</td>
1.246 leot 14187: <td>__stdc__</td>
1.233 wiz 14188: </tr>
14189: <tr>
1.251 gutterid 14190: <td>_vargroups</td>
1.246 leot 14191: <td>accept</td>
1.156 leot 14192: </tr>
14193: <tr>
1.251 gutterid 14194: <td>acquire-localbase-lock</td>
1.246 leot 14195: <td>acquire-lock</td>
1.227 wiz 14196: </tr>
14197: <tr>
1.251 gutterid 14198: <td>add</td>
1.246 leot 14199: <td>added</td>
1.156 leot 14200: </tr>
14201: <tr>
1.251 gutterid 14202: <td>administrator</td>
1.246 leot 14203: <td>alloca</td>
1.159 rillig 14204: </tr>
14205: <tr>
1.251 gutterid 14206: <td>alternatives</td>
1.246 leot 14207: <td>aslr</td>
1.217 rillig 14208: </tr>
14209: <tr>
1.251 gutterid 14210: <td>asprintf</td>
1.246 leot 14211: <td>atlas</td>
1.156 leot 14212: </tr>
14213: <tr>
1.251 gutterid 14214: <td>autoconf</td>
1.246 leot 14215: <td>automake</td>
1.201 cirnatda 14216: </tr>
14217: <tr>
1.251 gutterid 14218: <td>autoreconf</td>
1.246 leot 14219: <td>awk</td>
1.174 leot 14220: </tr>
14221: <tr>
1.251 gutterid 14222: <td>bash</td>
1.246 leot 14223: <td>big-endian</td>
1.156 leot 14224: </tr>
14225: <tr>
1.251 gutterid 14226: <td>bin-install</td>
1.246 leot 14227: <td>bind</td>
1.156 leot 14228: </tr>
14229: <tr>
1.251 gutterid 14230: <td>binpkg-list</td>
1.246 leot 14231: <td>blas</td>
1.174 leot 14232: </tr>
14233: <tr>
1.251 gutterid 14234: <td>bootstrap-depends</td>
1.246 leot 14235: <td>broken</td>
1.156 leot 14236: </tr>
14237: <tr>
1.251 gutterid 14238: <td>broken_on_platform</td>
1.246 leot 14239: <td>bsd</td>
1.161 leot 14240: </tr>
14241: <tr>
1.251 gutterid 14242: <td>bsd.prog.mk</td>
1.246 leot 14243: <td>build</td>
1.156 leot 14244: </tr>
14245: <tr>
1.251 gutterid 14246: <td>build-env</td>
1.246 leot 14247: <td>buildlink-directories</td>
1.156 leot 14248: </tr>
14249: <tr>
1.251 gutterid 14250: <td>buildlink-oss-soundcard-h</td>
1.246 leot 14251: <td>built-in</td>
1.156 leot 14252: </tr>
14253: <tr>
1.251 gutterid 14254: <td>builtin</td>
1.246 leot 14255: <td>c</td>
1.242 gutterid 14256: </tr>
14257: <tr>
1.251 gutterid 14258: <td>c++</td>
1.246 leot 14259: <td>ccache</td>
1.177 leot 14260: </tr>
14261: <tr>
1.251 gutterid 14262: <td>cce</td>
1.246 leot 14263: <td>cdefs</td>
1.159 rillig 14264: </tr>
14265: <tr>
1.251 gutterid 14266: <td>ceil</td>
1.246 leot 14267: <td>changes</td>
1.156 leot 14268: </tr>
14269: <tr>
1.251 gutterid 14270: <td>changes-entry</td>
1.246 leot 14271: <td>changes-entry-noupdate</td>
1.174 leot 14272: </tr>
14273: <tr>
1.251 gutterid 14274: <td>check</td>
1.246 leot 14275: <td>check-clean</td>
1.156 leot 14276: </tr>
14277: <tr>
1.251 gutterid 14278: <td>check-files</td>
1.246 leot 14279: <td>check-files-clean</td>
1.156 leot 14280: </tr>
14281: <tr>
1.251 gutterid 14282: <td>check-vulnerable</td>
1.246 leot 14283: <td>checksum</td>
1.156 leot 14284: </tr>
14285: <tr>
1.251 gutterid 14286: <td>checksum-phase</td>
1.246 leot 14287: <td>clean</td>
1.156 leot 14288: </tr>
14289: <tr>
1.251 gutterid 14290: <td>clean-depends</td>
1.246 leot 14291: <td>cleandir</td>
1.174 leot 14292: </tr>
14293: <tr>
1.251 gutterid 14294: <td>commit</td>
1.246 leot 14295: <td>commit-changes-entry</td>
1.156 leot 14296: </tr>
14297: <tr>
1.251 gutterid 14298: <td>compact</td>
1.246 leot 14299: <td>compiler</td>
1.156 leot 14300: </tr>
14301: <tr>
1.251 gutterid 14302: <td>conf</td>
1.246 leot 14303: <td>config.guess</td>
1.156 leot 14304: </tr>
14305: <tr>
1.251 gutterid 14306: <td>config.sub</td>
1.246 leot 14307: <td>configuration</td>
1.156 leot 14308: </tr>
14309: <tr>
1.251 gutterid 14310: <td>configure</td>
1.246 leot 14311: <td>configure-env</td>
1.156 leot 14312: </tr>
14313: <tr>
1.251 gutterid 14314: <td>configure-help</td>
1.246 leot 14315: <td>configure_args</td>
1.156 leot 14316: </tr>
14317: <tr>
1.251 gutterid 14318: <td>connect</td>
1.246 leot 14319: <td>cos</td>
1.156 leot 14320: </tr>
14321: <tr>
1.251 gutterid 14322: <td>cpe</td>
1.246 leot 14323: <td>cputime</td>
1.156 leot 14324: </tr>
14325: <tr>
1.251 gutterid 14326: <td>create-usergroup</td>
1.246 leot 14327: <td>csh</td>
1.156 leot 14328: </tr>
14329: <tr>
1.251 gutterid 14330: <td>ctf</td>
1.242 gutterid 14331: <td>debug</td>
1.241 rillig 14332: </tr>
14333: <tr>
1.251 gutterid 14334: <td>declaration</td>
1.242 gutterid 14335: <td>declare</td>
1.238 wiz 14336: </tr>
14337: <tr>
1.251 gutterid 14338: <td>defined</td>
1.242 gutterid 14339: <td>depend</td>
1.223 nia 14340: </tr>
14341: <tr>
1.251 gutterid 14342: <td>dependencies</td>
1.242 gutterid 14343: <td>depends</td>
1.174 leot 14344: </tr>
14345: <tr>
1.251 gutterid 14346: <td>depends-checksum</td>
1.242 gutterid 14347: <td>depends-fetch</td>
1.214 leot 14348: </tr>
14349: <tr>
1.251 gutterid 14350: <td>deps</td>
1.242 gutterid 14351: <td>describe</td>
1.205 wiz 14352: </tr>
14353: <tr>
1.251 gutterid 14354: <td>destdir</td>
1.242 gutterid 14355: <td>disable</td>
1.161 leot 14356: </tr>
14357: <tr>
1.251 gutterid 14358: <td>distclean</td>
1.242 gutterid 14359: <td>distinfo</td>
1.197 leot 14360: </tr>
14361: <tr>
1.251 gutterid 14362: <td>dl</td>
1.242 gutterid 14363: <td>dlopen</td>
1.156 leot 14364: </tr>
14365: <tr>
1.251 gutterid 14366: <td>do-buildlink</td>
1.242 gutterid 14367: <td>do-clean</td>
1.156 leot 14368: </tr>
14369: <tr>
1.251 gutterid 14370: <td>do-configure</td>
1.242 gutterid 14371: <td>do-configure-post-hook</td>
1.156 leot 14372: </tr>
14373: <tr>
1.251 gutterid 14374: <td>do-extract</td>
1.242 gutterid 14375: <td>do-fetch</td>
1.156 leot 14376: </tr>
14377: <tr>
1.251 gutterid 14378: <td>do-install</td>
1.242 gutterid 14379: <td>emul</td>
1.156 leot 14380: </tr>
14381: <tr>
1.251 gutterid 14382: <td>emul-distinfo</td>
1.242 gutterid 14383: <td>emul-fetch</td>
1.162 rillig 14384: </tr>
14385: <tr>
1.251 gutterid 14386: <td>emulation</td>
1.242 gutterid 14387: <td>emulator</td>
1.156 leot 14388: </tr>
14389: <tr>
1.251 gutterid 14390: <td>enable</td>
1.238 wiz 14391: <td>endian</td>
1.246 leot 14392: </tr>
14393: <tr>
1.251 gutterid 14394: <td>enomem</td>
1.246 leot 14395: <td>ensurepip</td>
1.233 wiz 14396: </tr>
14397: <tr>
1.251 gutterid 14398: <td>err</td>
1.246 leot 14399: <td>errx</td>
1.156 leot 14400: </tr>
14401: <tr>
1.251 gutterid 14402: <td>etc</td>
1.246 leot 14403: <td>exp</td>
1.227 wiz 14404: </tr>
14405: <tr>
1.251 gutterid 14406: <td>extract-rpm</td>
1.246 leot 14407: <td>fabs</td>
1.214 leot 14408: </tr>
14409: <tr>
1.251 gutterid 14410: <td>feature</td>
1.246 leot 14411: <td>features</td>
1.156 leot 14412: </tr>
14413: <tr>
1.251 gutterid 14414: <td>fetch</td>
1.246 leot 14415: <td>fetch-list</td>
1.205 wiz 14416: </tr>
14417: <tr>
1.251 gutterid 14418: <td>follows</td>
1.246 leot 14419: <td>forbids</td>
1.197 leot 14420: </tr>
14421: <tr>
1.251 gutterid 14422: <td>form</td>
1.246 leot 14423: <td>format</td>
1.156 leot 14424: </tr>
14425: <tr>
1.251 gutterid 14426: <td>fortify</td>
1.246 leot 14427: <td>fortify_source</td>
1.238 wiz 14428: </tr>
14429: <tr>
1.251 gutterid 14430: <td>friend</td>
1.242 gutterid 14431: <td>fts</td>
1.241 rillig 14432: </tr>
14433: <tr>
1.251 gutterid 14434: <td>fts_close</td>
1.242 gutterid 14435: <td>fts_open</td>
1.217 rillig 14436: </tr>
14437: <tr>
1.251 gutterid 14438: <td>fts_read</td>
1.242 gutterid 14439: <td>fts_set</td>
1.223 nia 14440: </tr>
14441: <tr>
1.251 gutterid 14442: <td>gcc</td>
1.242 gutterid 14443: <td>gethostbyaddr</td>
1.156 leot 14444: </tr>
14445: <tr>
1.251 gutterid 14446: <td>gethostbyname</td>
1.242 gutterid 14447: <td>gethostbyname2</td>
1.156 leot 14448: </tr>
14449: <tr>
1.251 gutterid 14450: <td>getopt_long</td>
1.242 gutterid 14451: <td>getprogname</td>
1.156 leot 14452: </tr>
14453: <tr>
1.251 gutterid 14454: <td>getservbyname</td>
1.242 gutterid 14455: <td>getservbyport</td>
1.156 leot 14456: </tr>
14457: <tr>
1.251 gutterid 14458: <td>getservent</td>
1.238 wiz 14459: <td>gettext</td>
1.246 leot 14460: </tr>
14461: <tr>
1.251 gutterid 14462: <td>github</td>
1.246 leot 14463: <td>gitlab</td>
1.233 wiz 14464: </tr>
14465: <tr>
1.251 gutterid 14466: <td>glob</td>
1.246 leot 14467: <td>gnu</td>
1.174 leot 14468: </tr>
14469: <tr>
1.251 gutterid 14470: <td>gnu_configure_strict</td>
1.246 leot 14471: <td>go</td>
1.227 wiz 14472: </tr>
14473: <tr>
1.251 gutterid 14474: <td>go-deps</td>
1.246 leot 14475: <td>golang</td>
1.223 nia 14476: </tr>
14477: <tr>
1.251 gutterid 14478: <td>guess-license</td>
1.246 leot 14479: <td>hashbang</td>
1.217 rillig 14480: </tr>
14481: <tr>
1.251 gutterid 14482: <td>heimdal</td>
1.246 leot 14483: <td>help</td>
1.238 wiz 14484: </tr>
14485: <tr>
1.251 gutterid 14486: <td>imake</td>
1.242 gutterid 14487: <td>in-tree</td>
1.241 rillig 14488: </tr>
14489: <tr>
1.251 gutterid 14490: <td>increment</td>
1.241 rillig 14491: <td>indirect</td>
1.156 leot 14492: </tr>
14493: <tr>
1.251 gutterid 14494: <td>inet_aton</td>
1.241 rillig 14495: <td>interp</td>
1.214 leot 14496: </tr>
14497: <tr>
1.251 gutterid 14498: <td>interpreter</td>
1.241 rillig 14499: <td>intl</td>
1.156 leot 14500: </tr>
14501: <tr>
1.251 gutterid 14502: <td>ip4</td>
1.241 rillig 14503: <td>ip6</td>
1.205 wiz 14504: </tr>
14505: <tr>
1.251 gutterid 14506: <td>ipv4</td>
1.241 rillig 14507: <td>ipv6</td>
1.197 leot 14508: </tr>
14509: <tr>
1.251 gutterid 14510: <td>iso</td>
1.241 rillig 14511: <td>kerberos</td>
1.161 leot 14512: </tr>
14513: <tr>
1.251 gutterid 14514: <td>krb</td>
1.241 rillig 14515: <td>krb5</td>
1.156 leot 14516: </tr>
14517: <tr>
1.251 gutterid 14518: <td>ksh</td>
1.241 rillig 14519: <td>lapack</td>
1.156 leot 14520: </tr>
14521: <tr>
1.251 gutterid 14522: <td>latex</td>
1.241 rillig 14523: <td>libintl_bindtextdomain</td>
1.156 leot 14524: </tr>
14525: <tr>
1.251 gutterid 14526: <td>libintl_gettext</td>
1.241 rillig 14527: <td>libintl_textdomain</td>
1.189 bacon 14528: </tr>
14529: <tr>
1.251 gutterid 14530: <td>libnbcompat</td>
1.241 rillig 14531: <td>libs</td>
1.189 bacon 14532: </tr>
14533: <tr>
1.251 gutterid 14534: <td>libtool</td>
1.241 rillig 14535: <td>licence</td>
1.156 leot 14536: </tr>
14537: <tr>
1.251 gutterid 14538: <td>license</td>
1.241 rillig 14539: <td>lintl</td>
1.177 leot 14540: </tr>
14541: <tr>
1.251 gutterid 14542: <td>little-endian</td>
1.241 rillig 14543: <td>lock</td>
1.156 leot 14544: </tr>
14545: <tr>
1.251 gutterid 14546: <td>locking</td>
1.241 rillig 14547: <td>lua</td>
1.174 leot 14548: </tr>
14549: <tr>
1.251 gutterid 14550: <td>lvalue</td>
1.241 rillig 14551: <td>make</td>
1.159 rillig 14552: </tr>
14553: <tr>
1.251 gutterid 14554: <td>makesum</td>
1.241 rillig 14555: <td>memory</td>
1.246 leot 14556: </tr>
14557: <tr>
1.251 gutterid 14558: <td>meta</td>
1.246 leot 14559: <td>meta-package</td>
1.156 leot 14560: </tr>
14561: <tr>
1.251 gutterid 14562: <td>meta_package</td>
1.246 leot 14563: <td>mit-krb5</td>
1.233 wiz 14564: </tr>
14565: <tr>
1.251 gutterid 14566: <td>mk.conf</td>
1.246 leot 14567: <td>mkl</td>
1.227 wiz 14568: </tr>
14569: <tr>
1.251 gutterid 14570: <td>mount</td>
1.246 leot 14571: <td>move</td>
1.156 leot 14572: </tr>
14573: <tr>
1.251 gutterid 14574: <td>moved</td>
1.246 leot 14575: <td>mprotect</td>
1.156 leot 14576: </tr>
14577: <tr>
1.251 gutterid 14578: <td>mremap</td>
1.246 leot 14579: <td>native</td>
1.177 leot 14580: </tr>
14581: <tr>
1.251 gutterid 14582: <td>nb</td>
1.246 leot 14583: <td>nbcompat</td>
1.159 rillig 14584: </tr>
14585: <tr>
1.251 gutterid 14586: <td>netlib</td>
1.246 leot 14587: <td>node</td>
1.226 gutterid 14588: </tr>
14589: <tr>
1.251 gutterid 14590: <td>node.js</td>
1.246 leot 14591: <td>nodejs</td>
1.156 leot 14592: </tr>
14593: <tr>
1.251 gutterid 14594: <td>obstack</td>
1.246 leot 14595: <td>obstack_ptr_grow</td>
1.156 leot 14596: </tr>
14597: <tr>
1.251 gutterid 14598: <td>occurs</td>
1.246 leot 14599: <td>only</td>
1.218 nia 14600: </tr>
14601: <tr>
1.251 gutterid 14602: <td>openblas</td>
1.246 leot 14603: <td>options</td>
1.218 nia 14604: </tr>
14605: <tr>
1.251 gutterid 14606: <td>options.mk</td>
1.246 leot 14607: <td>order</td>
1.205 wiz 14608: </tr>
14609: <tr>
1.251 gutterid 14610: <td>override</td>
1.246 leot 14611: <td>override-intltool</td>
1.156 leot 14612: </tr>
14613: <tr>
1.251 gutterid 14614: <td>override-message-intltool</td>
1.246 leot 14615: <td>package</td>
1.161 leot 14616: </tr>
14617: <tr>
1.251 gutterid 14618: <td>parallel</td>
1.246 leot 14619: <td>path</td>
1.156 leot 14620: </tr>
14621: <tr>
1.251 gutterid 14622: <td>pax</td>
1.246 leot 14623: <td>paxctl</td>
1.156 leot 14624: </tr>
14625: <tr>
1.251 gutterid 14626: <td>pbulk-index</td>
1.246 leot 14627: <td>pc</td>
1.156 leot 14628: </tr>
14629: <tr>
1.251 gutterid 14630: <td>perl</td>
1.246 leot 14631: <td>perl5</td>
1.156 leot 14632: </tr>
14633: <tr>
1.251 gutterid 14634: <td>perms</td>
1.246 leot 14635: <td>php</td>
1.156 leot 14636: </tr>
14637: <tr>
1.251 gutterid 14638: <td>pkg-build-options</td>
1.246 leot 14639: <td>pkg-config</td>
1.156 leot 14640: </tr>
14641: <tr>
1.251 gutterid 14642: <td>pkg_build_options</td>
1.246 leot 14643: <td>pkgsrc</td>
1.156 leot 14644: </tr>
14645: <tr>
1.251 gutterid 14646: <td>platform</td>
1.246 leot 14647: <td>plist</td>
1.156 leot 14648: </tr>
14649: <tr>
1.251 gutterid 14650: <td>post-extract</td>
1.246 leot 14651: <td>post-fetch</td>
1.156 leot 14652: </tr>
14653: <tr>
1.251 gutterid 14654: <td>post-wrapper</td>
1.246 leot 14655: <td>pre-build-checks-hook</td>
1.156 leot 14656: </tr>
14657: <tr>
1.251 gutterid 14658: <td>pre-configure-checks-hook</td>
1.246 leot 14659: <td>pre-extract</td>
1.156 leot 14660: </tr>
14661: <tr>
1.251 gutterid 14662: <td>pre-fetch</td>
1.246 leot 14663: <td>print-go-deps</td>
1.156 leot 14664: </tr>
14665: <tr>
1.251 gutterid 14666: <td>print-plist</td>
1.246 leot 14667: <td>print-summary-data</td>
1.156 leot 14668: </tr>
14669: <tr>
1.251 gutterid 14670: <td>privileged-install-hook</td>
1.246 leot 14671: <td>pypi</td>
1.174 leot 14672: </tr>
14673: <tr>
1.251 gutterid 14674: <td>python</td>
1.246 leot 14675: <td>r</td>
1.156 leot 14676: </tr>
14677: <tr>
1.251 gutterid 14678: <td>readme-all</td>
1.246 leot 14679: <td>recursive</td>
1.156 leot 14680: </tr>
14681: <tr>
1.251 gutterid 14682: <td>recv</td>
1.246 leot 14683: <td>recvfrom</td>
1.156 leot 14684: </tr>
14685: <tr>
1.251 gutterid 14686: <td>regcomp</td>
1.246 leot 14687: <td>release-localbase-lock</td>
1.156 leot 14688: </tr>
14689: <tr>
1.251 gutterid 14690: <td>release-lock</td>
1.246 leot 14691: <td>relro</td>
1.156 leot 14692: </tr>
14693: <tr>
1.251 gutterid 14694: <td>remove</td>
1.246 leot 14695: <td>removed</td>
1.174 leot 14696: </tr>
14697: <tr>
1.251 gutterid 14698: <td>rename</td>
1.246 leot 14699: <td>renamed</td>
1.174 leot 14700: </tr>
14701: <tr>
1.251 gutterid 14702: <td>reorder</td>
1.246 leot 14703: <td>replace</td>
1.156 leot 14704: </tr>
14705: <tr>
1.251 gutterid 14706: <td>replace_interpreter</td>
1.246 leot 14707: <td>reproducible</td>
1.226 gutterid 14708: </tr>
14709: <tr>
1.251 gutterid 14710: <td>resolv</td>
1.246 leot 14711: <td>root</td>
1.226 gutterid 14712: </tr>
14713: <tr>
1.251 gutterid 14714: <td>ruby</td>
1.246 leot 14715: <td>send</td>
1.156 leot 14716: </tr>
14717: <tr>
1.251 gutterid 14718: <td>sendfile</td>
1.246 leot 14719: <td>sendto</td>
1.156 leot 14720: </tr>
14721: <tr>
1.251 gutterid 14722: <td>setenv</td>
1.246 leot 14723: <td>setgid</td>
1.156 leot 14724: </tr>
14725: <tr>
1.251 gutterid 14726: <td>setprogname</td>
1.246 leot 14727: <td>setuid</td>
1.174 leot 14728: </tr>
14729: <tr>
1.251 gutterid 14730: <td>sh</td>
1.246 leot 14731: <td>shebang</td>
1.156 leot 14732: </tr>
14733: <tr>
1.251 gutterid 14734: <td>show</td>
1.246 leot 14735: <td>show-all</td>
1.156 leot 14736: </tr>
14737: <tr>
1.251 gutterid 14738: <td>show-build-defs</td>
1.246 leot 14739: <td>show-depends</td>
1.156 leot 14740: </tr>
14741: <tr>
1.251 gutterid 14742: <td>show-depends-dirs</td>
1.246 leot 14743: <td>show-depends-pkgpaths</td>
1.156 leot 14744: </tr>
14745: <tr>
1.251 gutterid 14746: <td>show-depends-recursive</td>
1.246 leot 14747: <td>show-deps</td>
1.181 rillig 14748: </tr>
14749: <tr>
1.251 gutterid 14750: <td>show-distfiles</td>
1.246 leot 14751: <td>show-downlevel</td>
1.156 leot 14752: </tr>
14753: <tr>
1.251 gutterid 14754: <td>show-subdir-var</td>
1.246 leot 14755: <td>show-tools</td>
1.222 gutterid 14756: </tr>
14757: <tr>
1.251 gutterid 14758: <td>show-var</td>
1.246 leot 14759: <td>show-vars</td>
1.223 nia 14760: </tr>
14761: <tr>
1.251 gutterid 14762: <td>snprintf</td>
1.246 leot 14763: <td>socket</td>
1.156 leot 14764: </tr>
14765: <tr>
1.251 gutterid 14766: <td>ssp</td>
1.246 leot 14767: <td>st_mode</td>
1.156 leot 14768: </tr>
14769: <tr>
1.251 gutterid 14770: <td>stage-install</td>
1.246 leot 14771: <td>strcasestr</td>
1.156 leot 14772: </tr>
14773: <tr>
1.251 gutterid 14774: <td>strict</td>
1.246 leot 14775: <td>strip</td>
1.156 leot 14776: </tr>
14777: <tr>
1.251 gutterid 14778: <td>strndup</td>
1.246 leot 14779: <td>strnlen</td>
1.174 leot 14780: </tr>
14781: <tr>
1.251 gutterid 14782: <td>strsep</td>
1.246 leot 14783: <td>subst</td>
1.238 wiz 14784: </tr>
14785: <tr>
1.251 gutterid 14786: <td>substitutions</td>
1.226 gutterid 14787: <td>sun</td>
1.241 rillig 14788: </tr>
14789: <tr>
1.251 gutterid 14790: <td>sunpro</td>
1.241 rillig 14791: <td>sunwspro</td>
1.214 leot 14792: </tr>
14793: <tr>
1.251 gutterid 14794: <td>symlink</td>
1.242 gutterid 14795: <td>test</td>
1.212 wiz 14796: </tr>
14797: <tr>
1.251 gutterid 14798: <td>test-env</td>
1.242 gutterid 14799: <td>tex</td>
1.227 wiz 14800: </tr>
14801: <tr>
1.251 gutterid 14802: <td>texlive</td>
1.242 gutterid 14803: <td>tmp</td>
1.223 nia 14804: </tr>
14805: <tr>
1.251 gutterid 14806: <td>todo</td>
1.242 gutterid 14807: <td>tool</td>
1.161 leot 14808: </tr>
14809: <tr>
1.251 gutterid 14810: <td>tools</td>
1.242 gutterid 14811: <td>tools-libtool-m4-override</td>
1.156 leot 14812: </tr>
14813: <tr>
1.251 gutterid 14814: <td>transitive</td>
1.242 gutterid 14815: <td>type</td>
1.156 leot 14816: </tr>
14817: <tr>
1.251 gutterid 14818: <td>ulimit</td>
1.242 gutterid 14819: <td>undefined</td>
1.156 leot 14820: </tr>
14821: <tr>
1.251 gutterid 14822: <td>undo-replace</td>
1.242 gutterid 14823: <td>unlimit</td>
1.156 leot 14824: </tr>
14825: <tr>
1.251 gutterid 14826: <td>unprivileged</td>
1.242 gutterid 14827: <td>unprivileged-install-hook</td>
1.156 leot 14828: </tr>
14829: <tr>
1.251 gutterid 14830: <td>unstripped</td>
1.242 gutterid 14831: <td>update</td>
1.156 leot 14832: </tr>
14833: <tr>
1.251 gutterid 14834: <td>updated</td>
1.242 gutterid 14835: <td>upload</td>
1.156 leot 14836: </tr>
14837: <tr>
1.251 gutterid 14838: <td>upload-distfiles</td>
1.242 gutterid 14839: <td>use_tools</td>
1.156 leot 14840: </tr>
14841: <tr>
1.251 gutterid 14842: <td>user</td>
1.242 gutterid 14843: <td>utimes</td>
1.156 leot 14844: </tr>
14845: <tr>
1.251 gutterid 14846: <td>vasprintf</td>
1.242 gutterid 14847: <td>verbose</td>
1.156 leot 14848: </tr>
14849: <tr>
1.251 gutterid 14850: <td>vsnprintf</td>
1.242 gutterid 14851: <td>warn</td>
1.156 leot 14852: </tr>
14853: <tr>
1.251 gutterid 14854: <td>warning</td>
1.242 gutterid 14855: <td>warnings</td>
1.156 leot 14856: </tr>
14857: <tr>
1.251 gutterid 14858: <td>warnx</td>
1.242 gutterid 14859: <td>wattr_off</td>
1.156 leot 14860: </tr>
14861: <tr>
1.251 gutterid 14862: <td>wattr_on</td>
1.242 gutterid 14863: <td>work</td>
1.156 leot 14864: </tr>
14865: <tr>
1.251 gutterid 14866: <td>wrapper</td>
1.174 leot 14867: <td>wrkdir</td>
1.156 leot 14868: </tr>
14869: </table>
1.154 rillig 14870: </div>
14871: <div class="appendix">
14872: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 14873: <a name="editing"></a>Appendix F. Editing guidelines for the pkgsrc guide</h1></div></div></div>
1.1 dsieger 14874: <div class="toc">
14875: <p><b>Table of Contents</b></p>
1.100 leot 14876: <dl class="toc">
1.207 leot 14877: <dt><span class="sect1"><a href="#targets">F.1. Make targets</a></span></dt>
14878: <dt><span class="sect1"><a href="#procedure">F.2. Procedure</a></span></dt>
1.1 dsieger 14879: </dl>
14880: </div>
14881: <p>This section contains information on editing the pkgsrc
14882: guide itself.</p>
1.41 asau 14883: <div class="sect1">
1.1 dsieger 14884: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 14885: <a name="targets"></a>F.1. Make targets</h2></div></div></div>
1.1 dsieger 14886: <p>The pkgsrc guide's source code is stored in
14887: <code class="filename">pkgsrc/doc/guide/files</code>, and several files
14888: are created from it:</p>
1.41 asau 14889: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 14890: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.txt</code></p></li>
14891: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.html</code></p></li>
1.174 leot 14892: <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>
14893: <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.1 dsieger 14894: The PDF version of the pkgsrc guide.</p></li>
1.174 leot 14895: <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.1 dsieger 14896: PostScript version of the pkgsrc guide.</p></li>
14897: </ul></div>
14898: </div>
1.41 asau 14899: <div class="sect1">
1.1 dsieger 14900: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 14901: <a name="procedure"></a>F.2. Procedure</h2></div></div></div>
1.1 dsieger 14902: <p>The procedure to edit the pkgsrc guide is:</p>
1.23 wiz 14903: <div class="procedure"><ol class="procedure" type="1">
1.190 bacon 14904: <li class="step"><p>Make sure you have checked out the htdocs repository
14905: into a sibling directory of your pkgsrc directory. You will need
14906: the ability to commit from both pkgsrc and htdocs.</p></li>
1.41 asau 14907: <li class="step"><p>Make sure you have the packages needed to
1.1 dsieger 14908: regenerate the pkgsrc guide (and other XML-based NetBSD
1.45 obache 14909: documentation) installed. These are automatically installed when
1.207 leot 14910: 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.41 asau 14911: <li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the
1.1 dsieger 14912: right directory. All further steps will take place
14913: here.</p></li>
1.41 asau 14914: <li class="step"><p>Edit the XML file(s) in
1.1 dsieger 14915: <code class="filename">files/</code>.</p></li>
1.41 asau 14916: <li class="step"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc
1.1 dsieger 14917: guide for valid XML and to build the final output files. If you
14918: get any errors at this stage, you can just edit the files, as
14919: there are only symbolic links in the working directory, pointing
14920: to the files in <code class="filename">files/</code>.</p></li>
1.41 asau 14921: <li class="step"><p><span class="command"><strong>(cd files && cvs
1.1 dsieger 14922: commit)</strong></span></p></li>
1.41 asau 14923: <li class="step"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to
1.1 dsieger 14924: regenerate the output files with the proper RCS
14925: Ids.</p></li>
1.41 asau 14926: <li class="step">
1.10 hubertf 14927: <p>Run <span class="command"><strong>bmake regen</strong></span> to install and
1.1 dsieger 14928: commit the files in both <code class="filename">pkgsrc/doc</code> and
14929: <code class="filename">htdocs</code>.</p>
1.41 asau 14930: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 14931: <h3 class="title">Note</h3>
14932: <p>If you have added, removed or renamed some chapters,
1.10 hubertf 14933: you need to synchronize them using <span class="command"><strong>cvs add</strong></span> or
14934: <span class="command"><strong>cvs delete</strong></span> in the htdocs
1.1 dsieger 14935: directory.</p>
14936: </div>
14937: </li>
14938: </ol></div>
14939: </div>
14940: </div>
14941: </div></body>
14942: </html>
CVSweb <webmaster@jp.NetBSD.org>