Annotation of htdocs/docs/pkgsrc/pkgsrc.html, revision 1.231
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.231 ! jnemeth 33: <div><p class="copyright">Copyright © 1994-2023 The NetBSD Foundation, Inc</p></div>
! 34: <div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.42 2023/01/02 05:45:23 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>
106: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
107: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1.1 dsieger 108: <dd><dl>
1.154 rillig 109: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
110: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
111: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 112: </dl></dd>
1.154 rillig 113: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
114: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.1 dsieger 115: </dl></dd>
1.154 rillig 116: <dt><span class="chapter"><a href="#binary">7. Creating binary packages</a></span></dt>
1.1 dsieger 117: <dd><dl>
1.154 rillig 118: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
119: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">7.2. Settings for creation of binary packages</a></span></dt>
1.6 rillig 120: </dl></dd>
1.154 rillig 121: <dt><span class="chapter"><a href="#bulk">8. Creating binary packages for everything in pkgsrc (bulk
1.6 rillig 122: builds)</a></span></dt>
1.1 dsieger 123: <dd><dl>
1.154 rillig 124: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.180 rillig 125: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.154 rillig 126: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
127: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.178 rillig 128: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
129: <dd><dl>
1.179 rillig 130: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
131: <dt><span class="sect2"><a href="#bulk.var.comperr">8.4.2. Detect classes of bugs by forcing compiler warnings</a></span></dt>
1.181 rillig 132: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
133: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
134: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
135: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
136: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
137: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
138: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
139: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.178 rillig 140: </dl></dd>
141: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
142: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.154 rillig 143: </dl></dd>
144: <dt><span class="chapter"><a href="#files">9. Directory layout of the installed files</a></span></dt>
145: <dd><dl>
146: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
147: <dt><span class="sect1"><a href="#files.varbase">9.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
148: </dl></dd>
149: <dt><span class="chapter"><a href="#faq">10. Frequently Asked Questions</a></span></dt>
150: <dd><dl>
151: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
152: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
153: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
154: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
155: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">10.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
156: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
157: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
158: <dt><span class="sect1"><a href="#passive-ftp">10.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
159: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
160: <dt><span class="sect1"><a href="#tmac.andoc-missing">10.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 161: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.154 rillig 162: <dt><span class="sect1"><a href="#bsd.own.mk-missing">10.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
1.221 nia 163: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.154 rillig 164: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
165: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
166: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
167: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
168: <dt><span class="sect1"><a href="#faq.rcs-conflicts">10.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</a></span></dt>
1.1 dsieger 169: </dl></dd>
170: </dl></dd>
171: <dt><span class="part"><a href="#developers-guide">II. The pkgsrc developer's guide</a></span></dt>
172: <dd><dl>
1.154 rillig 173: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.184 rillig 174: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.1 dsieger 175: <dd><dl>
1.184 rillig 176: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
177: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
178: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.1 dsieger 179: <dd><dl>
1.184 rillig 180: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
181: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
182: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
183: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
184: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.1 dsieger 185: </dl></dd>
1.184 rillig 186: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
187: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
188: <dd><dl>
189: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
190: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
191: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
192: </dl></dd>
193: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
194: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 195: </dl></dd>
1.184 rillig 196: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.6 rillig 197: <dd><dl>
1.184 rillig 198: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
199: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
200: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
201: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
202: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 203: <dd><dl>
1.184 rillig 204: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
205: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.6 rillig 206: </dl></dd>
1.184 rillig 207: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
208: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
209: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
210: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
211: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
212: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
213: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
214: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
215: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
216: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
217: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
218: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
219: </dl></dd>
220: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
221: <dd><dl>
222: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.6 rillig 223: <dd><dl>
1.219 nia 224: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
225: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
226: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.6 rillig 227: </dl></dd>
1.184 rillig 228: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
229: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">14.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
1.6 rillig 230: </dl></dd>
1.184 rillig 231: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 232: <dd><dl>
1.184 rillig 233: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
234: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
235: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
236: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.6 rillig 237: <dd><dl>
1.184 rillig 238: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
239: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
240: <dt><span class="sect2"><a href="#cflags-gnu-configure">15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</a></span></dt>
241: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 242: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.6 rillig 243: </dl></dd>
244: </dl></dd>
1.184 rillig 245: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.6 rillig 246: <dd><dl>
1.184 rillig 247: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
248: <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>
249: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
250: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 251: </dl></dd>
1.184 rillig 252: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.6 rillig 253: <dd><dl>
1.184 rillig 254: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
255: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
256: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
257: </dl></dd>
258: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
259: <dd><dl>
260: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
261: <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 262: <dd><dl>
1.184 rillig 263: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
264: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.26 wiz 265: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
266: and
267: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
268: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 269: </dl></dd>
1.184 rillig 270: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
271: <dd><dl>
272: <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>
273: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
274: </dl></dd>
275: </dl></dd>
276: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.6 rillig 277: <dd><dl>
1.184 rillig 278: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
279: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
280: <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>
281: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
282: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
283: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
284: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
285: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
286: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.6 rillig 287: </dl></dd>
1.184 rillig 288: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
289: <dd><dl>
290: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
291: <dd><dl>
292: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
293: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.6 rillig 294: </dl></dd>
1.184 rillig 295: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.6 rillig 296: <dd><dl>
1.184 rillig 297: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
298: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
299: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
300: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
301: </dl></dd>
302: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
303: <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>
304: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
305: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
306: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
307: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
308: <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 309: </dl></dd>
310: <dt><span class="chapter"><a href="#fixes">21. Making your package work</a></span></dt>
311: <dd><dl>
312: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
313: <dd><dl>
314: <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>
315: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
316: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
317: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
318: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
319: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
320: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
321: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
322: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
323: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
324: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
325: </dl></dd>
326: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
327: <dd><dl>
328: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
329: <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>
330: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
331: </dl></dd>
332: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
333: <dd><dl>
334: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
335: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
336: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.223 nia 337: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 rillig 338: </dl></dd>
339: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
340: <dd><dl>
341: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
342: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.205 wiz 343: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 nia 344: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
345: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
346: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
347: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.154 rillig 348: </dl></dd>
349: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
350: <dd><dl>
351: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
352: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.172 rillig 353: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
354: <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>
355: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.154 rillig 356: </dl></dd>
357: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
358: <dd><dl>
359: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
360: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
361: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
362: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
363: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.203 nia 364: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 rillig 365: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
366: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.203 nia 367: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
368: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
369: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
370: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
371: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
372: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
373: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.1 dsieger 374: emulation</a></span></dt>
1.203 nia 375: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
376: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.1 dsieger 377: </dl></dd>
1.154 rillig 378: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 379: </dl></dd>
1.184 rillig 380: <dt><span class="chapter"><a href="#gnome">22. GNOME packaging and porting</a></span></dt>
381: <dd><dl>
382: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
383: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
384: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
385: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
386: </dl></dd>
1.154 rillig 387: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.1 dsieger 388: <dd><dl>
1.154 rillig 389: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
390: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
391: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
392: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
393: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
394: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
395: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
396: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
397: </dl></dd>
398: <dt><span class="chapter"><a href="#devfaq">24. Frequently Asked Questions</a></span></dt>
1.1 dsieger 399: </dl></dd>
400: <dt><span class="part"><a href="#infrastructure">III. The pkgsrc infrastructure internals</a></span></dt>
401: <dd><dl>
1.184 rillig 402: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 403: <dd><dl>
1.184 rillig 404: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
405: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
406: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.1 dsieger 407: <dd><dl>
1.184 rillig 408: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
409: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.1 dsieger 410: </dl></dd>
1.184 rillig 411: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
412: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 413: <dd><dl>
1.184 rillig 414: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
415: <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 416: </dl></dd>
1.184 rillig 417: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 418: <dd><dl>
1.184 rillig 419: <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>
420: <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 421: </dl></dd>
422: </dl></dd>
1.184 rillig 423: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.1 dsieger 424: <dd><dl>
1.184 rillig 425: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
426: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.1 dsieger 427: <dd><dl>
1.184 rillig 428: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
429: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.1 dsieger 430: </dl></dd>
431: </dl></dd>
1.184 rillig 432: <dt><span class="chapter"><a href="#porting">27. Porting pkgsrc</a></span></dt>
433: <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 434: </dl></dd>
435: <dt><span class="appendix"><a href="#examples">A. A simple example package: bison</a></span></dt>
436: <dd><dl>
437: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
438: <dd><dl>
439: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
440: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
441: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.172 rillig 442: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.1 dsieger 443: </dl></dd>
444: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
445: </dl></dd>
1.207 leot 446: <dt><span class="appendix"><a href="#hardening">B. Security hardening</a></span></dt>
1.1 dsieger 447: <dd><dl>
1.207 leot 448: <dt><span class="sect1"><a href="#hardening.mechanisms">B.1. Mechanisms</a></span></dt>
449: <dd><dl>
450: <dt><span class="sect2"><a href="#hardening.mechanisms.enabled">B.1.1. Enabled by default</a></span></dt>
451: <dt><span class="sect2"><a href="#hardening.mechanisms.disabled">B.1.2. Not enabled by default</a></span></dt>
452: </dl></dd>
453: <dt><span class="sect1"><a href="#hardening.caveats">B.2. Caveats</a></span></dt>
454: <dd><dl>
455: <dt><span class="sect2"><a href="#hardening.caveats.pie">B.2.1. Problems with PKGSRC_MKPIE</a></span></dt>
456: <dt><span class="sect2"><a href="#hardening.caveats.fortify">B.2.2. Problems with PKGSRC_USE_FORTIFY</a></span></dt>
457: <dt><span class="sect2"><a href="#hardening.caveats.relro">B.2.3. Problems with PKGSRC_USE_RELRO</a></span></dt>
458: <dt><span class="sect2"><a href="#hardening.caveats.ssp">B.2.4. Problems with PKGSRC_USE_SSP</a></span></dt>
459: </dl></dd>
460: <dt><span class="sect1"><a href="#hardening.audit">B.3. Auditing the system</a></span></dt>
461: <dd><dl>
462: <dt><span class="sect2"><a href="#hardening.audit.pie">B.3.1. Checking for PIE</a></span></dt>
463: <dt><span class="sect2"><a href="#hardening.audit.relropartial">B.3.2. Checking for partial RELRO</a></span></dt>
464: <dt><span class="sect2"><a href="#hardening.audit.relrofull">B.3.3. Checking for full RELRO</a></span></dt>
465: <dt><span class="sect2"><a href="#hardening.audit.ssp">B.3.4. Checking for SSP</a></span></dt>
466: </dl></dd>
467: </dl></dd>
468: <dt><span class="appendix"><a href="#logs">C. Build logs</a></span></dt>
469: <dd><dl>
470: <dt><span class="sect1"><a href="#logs.building">C.1. Building figlet</a></span></dt>
471: <dt><span class="sect1"><a href="#logs.package">C.2. Packaging figlet</a></span></dt>
1.1 dsieger 472: </dl></dd>
1.207 leot 473: <dt><span class="appendix"><a href="#ftp-layout">D. Directory layout of the pkgsrc FTP server</a></span></dt>
1.1 dsieger 474: <dd><dl>
1.207 leot 475: <dt><span class="sect1"><a href="#ftp-distfiles">D.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
476: <dt><span class="sect1"><a href="#ftp-misc">D.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
477: <dt><span class="sect1"><a href="#ftp-packages">D.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
478: <dt><span class="sect1"><a href="#ftp-reports">D.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
479: <dt><span class="sect1"><a href="#ftp-source">D.5. <code class="filename">current</code>,
1.148 leot 480: <code class="filename">stable</code>,
1.23 wiz 481: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 482: source packages</a></span></dt>
483: </dl></dd>
1.207 leot 484: <dt><span class="appendix"><a href="#help-topics">E. Help topics</a></span></dt>
485: <dt><span class="appendix"><a href="#editing">F. Editing guidelines for the pkgsrc guide</a></span></dt>
1.1 dsieger 486: <dd><dl>
1.207 leot 487: <dt><span class="sect1"><a href="#targets">F.1. Make targets</a></span></dt>
488: <dt><span class="sect1"><a href="#procedure">F.2. Procedure</a></span></dt>
1.1 dsieger 489: </dl></dd>
490: </dl>
491: </div>
492: <div class="list-of-tables">
493: <p><b>List of Tables</b></p>
494: <dl>
495: <dt>1.1. <a href="#supported-platforms">Platforms supported by pkgsrc</a>
496: </dt>
1.184 rillig 497: <dt>12.1. <a href="#patch-examples">Patching examples</a>
1.1 dsieger 498: </dt>
1.184 rillig 499: <dt>22.1. <a href="#plist-handling">PLIST handling for GNOME packages</a>
1.1 dsieger 500: </dt>
501: </dl>
502: </div>
1.41 asau 503: <div class="chapter">
504: <div class="titlepage"><div><div><h1 class="title">
505: <a name="introduction"></a>Chapter 1. What is pkgsrc?</h1></div></div></div>
1.1 dsieger 506: <div class="toc">
507: <p><b>Table of Contents</b></p>
1.100 leot 508: <dl class="toc">
1.1 dsieger 509: <dt><span class="sect1"><a href="#introduction-section">1.1. Introduction</a></span></dt>
510: <dd><dl>
511: <dt><span class="sect2"><a href="#why-pkgsrc">1.1.1. Why pkgsrc?</a></span></dt>
512: <dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt>
513: </dl></dd>
514: <dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt>
515: <dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt>
516: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
517: <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
518: </dl>
519: </div>
1.41 asau 520: <div class="sect1">
1.1 dsieger 521: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
522: <a name="introduction-section"></a>1.1. Introduction</h2></div></div></div>
523: <p>There is a lot of software freely available for Unix-based
524: systems, which is usually available in form of the source code. Before
525: such software can be used, it needs to be configured to the local
526: system, compiled and installed, and this is exactly what The NetBSD
527: Packages Collection (pkgsrc) does. pkgsrc also has some basic commands
528: to handle binary packages, so that not every user has to build the
529: packages for himself, which is a time-costly task.</p>
530: <p>pkgsrc currently contains several thousand packages,
531: including:</p>
1.41 asau 532: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 533: <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 534: web server</p></li>
1.207 leot 535: <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 536: web browser</p></li>
1.207 leot 537: <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 538: Desktop Environment</p></li>
1.207 leot 539: <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 540: Desktop Environment</p></li>
541: </ul></div>
1.108 rillig 542: <p>… just to name a few.</p>
1.1 dsieger 543: <p>pkgsrc has built-in support for handling varying dependencies,
544: such as pthreads and X11, and extended features such as IPv6 support on
545: a range of platforms.</p>
1.41 asau 546: <div class="sect2">
1.1 dsieger 547: <div class="titlepage"><div><div><h3 class="title">
548: <a name="why-pkgsrc"></a>1.1.1. Why pkgsrc?</h3></div></div></div>
549: <p>
550: pkgsrc provides the following key features:
551: </p>
1.41 asau 552: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 553: <li class="listitem"><p>Easy building of software from source as well as the creation
1.1 dsieger 554: and installation of binary packages. The source and latest
555: patches are retrieved from a master or mirror download site, checksum
556: verified, then built on your system. Support for binary-only
557: distributions is available for both native platforms and NetBSD
558: emulated platforms.</p></li>
1.23 wiz 559: <li class="listitem"><p>All packages are installed in a consistent directory tree,
1.1 dsieger 560: including binaries, libraries, man pages and other
561: documentation.</p></li>
1.104 sevan 562: <li class="listitem"><p>Tracking of package dependencies automatically, including when
563: performing updates, to ensure required packages are installed. The
564: configuration files of various packages are handled automatically during
565: updates, so local changes are preserved.</p></li>
1.23 wiz 566: <li class="listitem"><p>Like NetBSD, pkgsrc is designed with portability in mind and
1.1 dsieger 567: consists of highly portable code. This allows the greatest speed of
1.25 spz 568: development when porting to a new platform. This portability also
1.1 dsieger 569: ensures that pkgsrc is <span class="emphasis"><em>consistent across all
570: platforms</em></span>.</p></li>
1.23 wiz 571: <li class="listitem"><p>The installation prefix, acceptable software licenses,
1.1 dsieger 572: international encryption requirements and build-time options for a
573: large number of packages are all set in a simple, central
574: configuration file.</p></li>
1.23 wiz 575: <li class="listitem"><p>The entire source (not including the distribution files) is
1.1 dsieger 576: freely available under a BSD license, so you may extend and adapt
577: pkgsrc to your needs. Support for local packages and patches is
578: available right out of the box, so you can configure it specifically
579: for your environment.</p></li>
580: </ul></div>
581: <p>The following principles are basic to pkgsrc:</p>
1.41 asau 582: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 583: <li class="listitem"><p><span class="quote">“<span class="quote">It should only work if it's right.</span>”</span>
1.14 jmcneill 584: — That means, if a package contains bugs, it's better to find
1.1 dsieger 585: them and to complain about them rather than to just install the package
586: and hope that it works. There are numerous checks in pkgsrc that try to
1.207 leot 587: 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 588: of shell scripts), and post-installation checks (installed files,
589: references to shared libraries, script interpreters).</p></li>
1.23 wiz 590: <li class="listitem"><p><span class="quote">“<span class="quote">If it works, it should work everywhere</span>”</span>
1.14 jmcneill 591: — Like NetBSD has been ported to many hardware architectures,
1.1 dsieger 592: pkgsrc has been ported to many operating systems. Care is taken that
593: packages behave the same on all platforms.</p></li>
594: </ul></div>
595: </div>
1.41 asau 596: <div class="sect2">
1.1 dsieger 597: <div class="titlepage"><div><div><h3 class="title">
598: <a name="intro.platforms"></a>1.1.2. Supported platforms</h3></div></div></div>
599: <p>pkgsrc consists of both a source distribution and a binary
600: distribution for these operating systems. After retrieving the required
601: source or binaries, you can be up and running with pkgsrc in just
602: minutes!</p>
603: <p>pkgsrc was derived from FreeBSD's ports system, and
604: initially developed for NetBSD only. Since then, pkgsrc has
605: grown a lot, and now supports the following platforms:</p>
606: <div class="table">
607: <a name="supported-platforms"></a><p class="title"><b>Table 1.1. Platforms supported by pkgsrc</b></p>
1.106 tnn 608: <div class="table-contents"><table class="table" summary="Platforms supported by pkgsrc" border="1">
1.1 dsieger 609: <colgroup>
610: <col>
611: <col>
1.92 sevan 612: <col>
1.1 dsieger 613: </colgroup>
614: <thead><tr>
615: <th>Platform</th>
616: <th>Date Support Added</th>
1.92 sevan 617: <th>Notes</th>
1.1 dsieger 618: </tr></thead>
619: <tbody>
620: <tr>
1.174 leot 621: <td><a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a></td>
1.1 dsieger 622: <td align="center">Aug 1997</td>
1.92 sevan 623: <td class="auto-generated"> </td>
1.1 dsieger 624: </tr>
625: <tr>
1.10 hubertf 626: <td><a class="ulink" href="http://wwws.sun.com/software/solaris/" target="_top">Solaris</a></td>
1.1 dsieger 627: <td align="center">Mar 1999</td>
1.151 sevan 628: <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 629: </tr>
630: <tr>
1.174 leot 631: <td><a class="ulink" href="https://www.kernel.org/" target="_top">Linux</a></td>
1.1 dsieger 632: <td align="center">Jun 1999</td>
1.151 sevan 633: <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 634: </tr>
635: <tr>
636: <td>
1.118 sevan 637: <a class="ulink" href="https://developer.apple.com/macos/" target="_top">Darwin / Mac OS X / OS X / macOS</a>
1.1 dsieger 638: </td>
639: <td align="center">Oct 2001</td>
1.191 bacon 640: <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 641: </tr>
642: <tr>
1.174 leot 643: <td><a class="ulink" href="https://www.freebsd.org/" target="_top">FreeBSD</a></td>
1.1 dsieger 644: <td align="center">Nov 2002</td>
1.151 sevan 645: <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 646: </tr>
647: <tr>
1.174 leot 648: <td><a class="ulink" href="https://www.openbsd.org/" target="_top">OpenBSD</a></td>
1.1 dsieger 649: <td align="center">Nov 2002</td>
1.151 sevan 650: <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 651: </tr>
652: <tr>
1.174 leot 653: <td><a class="ulink" href="https://www.sgi.com/software/irix/" target="_top">IRIX</a></td>
1.1 dsieger 654: <td align="center">Dec 2002</td>
1.92 sevan 655: <td>
1.151 sevan 656: <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX" target="_top">README.IRIX</a>
1.92 sevan 657: </td>
1.1 dsieger 658: </tr>
659: <tr>
660: <td>BSD/OS</td>
661: <td align="center">Dec 2003</td>
1.92 sevan 662: <td class="auto-generated"> </td>
1.1 dsieger 663: </tr>
664: <tr>
1.174 leot 665: <td><a class="ulink" href="https://www-1.ibm.com/servers/aix/" target="_top">AIX</a></td>
1.1 dsieger 666: <td align="center">Dec 2003</td>
1.151 sevan 667: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.AIX" target="_top">README.AIX</a></td>
1.1 dsieger 668: </tr>
669: <tr>
670: <td>
1.174 leot 671: <a class="ulink" href="https://www.microsoft.com/windows/sfu/" target="_top">Interix</a>
1.1 dsieger 672: (Microsoft Windows Services for Unix)
673: </td>
674: <td align="center">Mar 2004</td>
1.151 sevan 675: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Interix" target="_top">README.Interix</a></td>
1.1 dsieger 676: </tr>
677: <tr>
1.174 leot 678: <td><a class="ulink" href="https://www.dragonflybsd.org/" target="_top">DragonFlyBSD</a></td>
1.1 dsieger 679: <td align="center">Oct 2004</td>
1.92 sevan 680: <td class="auto-generated"> </td>
1.1 dsieger 681: </tr>
682: <tr>
1.10 hubertf 683: <td><a class="ulink" href="http://www.tru64.org/" target="_top">OSF/1</a></td>
1.1 dsieger 684: <td align="center">Nov 2004</td>
1.151 sevan 685: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OSF1" target="_top">README.OSF1</a></td>
1.1 dsieger 686: </tr>
687: <tr>
1.174 leot 688: <td><a class="ulink" href="https://www.hp.com/products1/unix/" target="_top">HP-UX</a></td>
1.1 dsieger 689: <td align="center">Apr 2007</td>
1.151 sevan 690: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.HPUX" target="_top">README.HPUX</a></td>
1.1 dsieger 691: </tr>
1.23 wiz 692: <tr>
1.174 leot 693: <td><a class="ulink" href="https://www.haiku-os.org/" target="_top">Haiku</a></td>
1.23 wiz 694: <td align="center">Sep 2010</td>
1.151 sevan 695: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Haiku" target="_top">README.Haiku</a></td>
1.23 wiz 696: </tr>
1.45 obache 697: <tr>
1.174 leot 698: <td><a class="ulink" href="https://www.mirbsd.org/" target="_top">MirBSD</a></td>
1.57 bsiegert 699: <td align="center">Jan 2011</td>
1.92 sevan 700: <td class="auto-generated"> </td>
1.45 obache 701: </tr>
702: <tr>
1.174 leot 703: <td><a class="ulink" href="https://www.minix3.org/" target="_top">Minix3</a></td>
1.45 obache 704: <td align="center">Nov 2011</td>
1.151 sevan 705: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Minix3" target="_top">README.Minix3</a></td>
1.45 obache 706: </tr>
707: <tr>
1.174 leot 708: <td><a class="ulink" href="https://cygwin.com/" target="_top">Cygwin</a></td>
1.45 obache 709: <td align="center">Mar 2013</td>
1.151 sevan 710: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Cygwin" target="_top">README.Cygwin</a></td>
1.45 obache 711: </tr>
1.58 ryoon 712: <tr>
1.174 leot 713: <td><a class="ulink" href="https://www.debian.org/ports/kfreebsd-gnu/" target="_top">GNU/kFreeBSD</a></td>
1.58 ryoon 714: <td align="center">Jul 2013</td>
1.151 sevan 715: <td><a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.GNUkFreeBSD" target="_top">README.GNUkFreeBSD</a></td>
1.58 ryoon 716: </tr>
1.104 sevan 717: <tr>
1.174 leot 718: <td><a class="ulink" href="https://www.bitrig.org/" target="_top">Bitrig</a></td>
1.104 sevan 719: <td align="center">Jun 2014</td>
1.229 gutterid 720: <td>Removed from pkgsrc Sep 2022</td>
1.104 sevan 721: </tr>
1.1 dsieger 722: </tbody>
723: </table></div>
724: </div>
725: <br class="table-break">
726: </div>
727: </div>
1.41 asau 728: <div class="sect1">
1.1 dsieger 729: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
730: <a name="overview"></a>1.2. Overview</h2></div></div></div>
731: <p>This document is divided into three parts. The first,
1.10 hubertf 732: <a class="link" href="#users-guide" title="Part I. The pkgsrc user's guide">The pkgsrc user's guide</a>,
1.1 dsieger 733: describes how one can use one of the packages in the Package
734: Collection, either by installing a precompiled binary package,
735: or by building one's own copy using the NetBSD package system.
1.10 hubertf 736: The second part, <a class="link" href="#developers-guide" title="Part II. The pkgsrc developer's guide">The pkgsrc developer's guide</a>, explains how to prepare a
1.1 dsieger 737: package so it can be easily built by other NetBSD users without
738: knowing about the package's building details. The third part,
1.10 hubertf 739: <a class="link" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">The pkgsrc infrastructure internals</a>
1.1 dsieger 740: is intended for those who want to understand how pkgsrc is
741: implemented.</p>
742: <p>This document is available in various formats:
1.10 hubertf 743: <span class="simplelist"><a class="ulink" href="index.html" target="_top">HTML</a>, <a class="ulink" href="pkgsrc.pdf" target="_top">PDF</a>, <a class="ulink" href="pkgsrc.ps" target="_top">PS</a>, <a class="ulink" href="pkgsrc.txt" target="_top">TXT</a></span>.</p>
1.1 dsieger 744: </div>
1.41 asau 745: <div class="sect1">
1.1 dsieger 746: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
747: <a name="terminology"></a>1.3. Terminology</h2></div></div></div>
1.23 wiz 748: <p>There has been a lot of talk about <span class="quote">“<span class="quote">ports</span>”</span>,
749: <span class="quote">“<span class="quote">packages</span>”</span>, etc. so far. Here is a description of all the
1.1 dsieger 750: terminology used within this document.</p>
1.41 asau 751: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 752: <dt><span class="term">Package</span></dt>
753: <dd><p>A set of files and building instructions
754: that describe what's necessary
755: to build a certain piece of software using
756: pkgsrc. Packages are traditionally stored under
1.123 wiz 757: <code class="filename">/usr/pkgsrc</code>,
758: but may be stored in any location,
759: referred to as <code class="varname">PKGSRCDIR</code>.</p></dd>
1.1 dsieger 760: <dt><span class="term">The NetBSD package system</span></dt>
1.23 wiz 761: <dd><p>This is the former name of <span class="quote">“<span class="quote">pkgsrc</span>”</span>. It
1.1 dsieger 762: is part of the NetBSD operating system and can be bootstrapped
763: to run on non-NetBSD operating systems as well. It handles
764: building (compiling), installing, and removing of
765: packages.</p></dd>
766: <dt><span class="term">Distfile</span></dt>
767: <dd><p>This term describes the file or files that are
768: provided by the author of the piece of software to
769: distribute his work. All the changes necessary to build on
770: NetBSD are reflected in the corresponding package. Usually
771: the distfile is in the form of a compressed tar-archive,
772: but other types are possible, too. Distfiles are usually
773: stored below
774: <code class="filename">/usr/pkgsrc/distfiles</code>.</p></dd>
775: <dt><span class="term">Port</span></dt>
776: <dd><p>This is the term used by FreeBSD and OpenBSD people
777: for what we call a package.
1.23 wiz 778: In NetBSD terminology, <span class="quote">“<span class="quote">port</span>”</span> refers to a different
1.1 dsieger 779: architecture.</p></dd>
780: <dt><span class="term">Precompiled/binary package</span></dt>
781: <dd>
782: <p>A set of binaries built with pkgsrc from a distfile
783: and stuffed together in a single <code class="filename">.tgz</code>
784: file so it can be installed on machines of the same
785: machine architecture without the need to
786: recompile. Packages are usually generated in
787: <code class="filename">/usr/pkgsrc/packages</code>; there is also
1.25 spz 788: an archive on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/" target="_top">ftp.NetBSD.org</a>.</p>
1.23 wiz 789: <p>Sometimes, this is referred to by the term <span class="quote">“<span class="quote">package</span>”</span> too,
1.1 dsieger 790: especially in the context of precompiled packages.</p>
791: </dd>
792: <dt><span class="term">Program</span></dt>
793: <dd><p>The piece of software to be installed which will be
794: constructed from all the files in the distfile by the
795: actions defined in the corresponding package.</p></dd>
796: </dl></div>
1.41 asau 797: <div class="sect2">
1.1 dsieger 798: <div class="titlepage"><div><div><h3 class="title">
799: <a name="term.roles"></a>1.3.1. Roles involved in pkgsrc</h3></div></div></div>
1.41 asau 800: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 801: <dt><span class="term">pkgsrc users</span></dt>
802: <dd>
803: <p>The
804: pkgsrc users are people who use the packages provided by pkgsrc.
805: Typically they are system administrators. The people using the
1.23 wiz 806: software that is inside the packages (maybe called <span class="quote">“<span class="quote">end
807: users</span>”</span>) are not covered by the pkgsrc guide.</p>
1.1 dsieger 808: <p>There are two kinds of pkgsrc users: Some only want to
809: install pre-built binary packages. Others build the pkgsrc
810: packages from source, either for installing them directly or for
1.10 hubertf 811: building binary packages themselves. For pkgsrc users <a class="xref" href="#users-guide" title="Part I. The pkgsrc user's guide">Part I, “The pkgsrc user's guide”</a> should provide all necessary
1.1 dsieger 812: documentation.</p>
813: </dd>
814: <dt><span class="term">package maintainers</span></dt>
815: <dd><p>A
1.10 hubertf 816: package maintainer creates packages as described in <a class="xref" href="#developers-guide" title="Part II. The pkgsrc developer's guide">Part II, “The pkgsrc developer's guide”</a>.</p></dd>
1.1 dsieger 817: <dt><span class="term">infrastructure developers</span></dt>
818: <dd><p>These people are involved in all those files
819: that live in the <code class="filename">mk/</code> directory and below.
1.10 hubertf 820: Only these people should need to read through <a class="xref" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">Part III, “The pkgsrc infrastructure internals”</a>, though others might be curious,
1.1 dsieger 821: too.</p></dd>
822: </dl></div>
823: </div>
824: </div>
1.41 asau 825: <div class="sect1">
1.1 dsieger 826: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
827: <a name="typography"></a>1.4. Typography</h2></div></div></div>
828: <p>When giving examples for commands, shell prompts are used to
829: show if the command should/can be issued as root, or if
1.23 wiz 830: <span class="quote">“<span class="quote">normal</span>”</span> user privileges are sufficient. We use a
1.115 sevan 831: <code class="prompt">#</code> for root's shell prompt, a <code class="prompt">%</code> for users'
832: shell prompt, assuming they use the C-shell or tcsh and a <code class="prompt">$</code> for
1.229 gutterid 833: Bourne shell and derivatives.</p>
1.1 dsieger 834: </div>
835: </div>
1.41 asau 836: <div class="part">
1.1 dsieger 837: <div class="titlepage"><div><div><h1 class="title">
838: <a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div>
839: <div class="toc">
840: <p><b>Table of Contents</b></p>
1.100 leot 841: <dl class="toc">
1.154 rillig 842: <dt><span class="chapter"><a href="#help-user">2. Getting help</a></span></dt>
843: <dt><span class="chapter"><a href="#getting">3. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
1.1 dsieger 844: <dd><dl>
1.154 rillig 845: <dt><span class="sect1"><a href="#getting-first">3.1. Getting pkgsrc for the first time</a></span></dt>
1.1 dsieger 846: <dd><dl>
1.154 rillig 847: <dt><span class="sect2"><a href="#getting-via-tar">3.1.1. As tar archive</a></span></dt>
848: <dt><span class="sect2"><a href="#getting-via-cvs">3.1.2. Via anonymous CVS</a></span></dt>
1.1 dsieger 849: </dl></dd>
1.154 rillig 850: <dt><span class="sect1"><a href="#uptodate">3.2. Keeping pkgsrc up-to-date</a></span></dt>
1.1 dsieger 851: <dd><dl>
1.154 rillig 852: <dt><span class="sect2"><a href="#uptodate-tar">3.2.1. Via tar files</a></span></dt>
853: <dt><span class="sect2"><a href="#uptodate-cvs">3.2.2. Via CVS</a></span></dt>
1.1 dsieger 854: </dl></dd>
855: </dl></dd>
1.154 rillig 856: <dt><span class="chapter"><a href="#platforms">4. Using pkgsrc on systems other than NetBSD</a></span></dt>
1.1 dsieger 857: <dd><dl>
1.154 rillig 858: <dt><span class="sect1"><a href="#binarydist">4.1. Binary distribution</a></span></dt>
859: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">4.2. Bootstrapping pkgsrc</a></span></dt>
1.1 dsieger 860: </dl></dd>
1.154 rillig 861: <dt><span class="chapter"><a href="#using">5. Using pkgsrc</a></span></dt>
1.1 dsieger 862: <dd><dl>
1.154 rillig 863: <dt><span class="sect1"><a href="#using-pkg">5.1. Using binary packages</a></span></dt>
1.1 dsieger 864: <dd><dl>
1.154 rillig 865: <dt><span class="sect2"><a href="#finding-binary-packages">5.1.1. Finding binary packages</a></span></dt>
866: <dt><span class="sect2"><a href="#installing-binary-packages">5.1.2. Installing binary packages</a></span></dt>
1.202 nia 867: <dt><span class="sect2"><a href="#using.pkgin_update">5.1.3. Updating packages</a></span></dt>
868: <dt><span class="sect2"><a href="#using.pkg_delete">5.1.4. Deinstalling packages</a></span></dt>
869: <dt><span class="sect2"><a href="#using.pkg_info">5.1.5. Getting information about installed packages</a></span></dt>
870: <dt><span class="sect2"><a href="#vulnerabilities">5.1.6. Checking for security vulnerabilities in installed packages</a></span></dt>
871: <dt><span class="sect2"><a href="#pkg_versions">5.1.7. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
872: <dt><span class="sect2"><a href="#using.pkg_admin">5.1.8. Other administrative functions</a></span></dt>
1.1 dsieger 873: </dl></dd>
1.154 rillig 874: <dt><span class="sect1"><a href="#building-packages-from-source">5.2. Building packages from source</a></span></dt>
1.1 dsieger 875: <dd><dl>
1.154 rillig 876: <dt><span class="sect2"><a href="#requirements">5.2.1. Requirements</a></span></dt>
877: <dt><span class="sect2"><a href="#fetching-distfiles">5.2.2. Fetching distfiles</a></span></dt>
878: <dt><span class="sect2"><a href="#how-to-build-and-install">5.2.3. How to build and install</a></span></dt>
1.1 dsieger 879: </dl></dd>
880: </dl></dd>
1.154 rillig 881: <dt><span class="chapter"><a href="#configuring">6. Configuring pkgsrc</a></span></dt>
1.1 dsieger 882: <dd><dl>
1.154 rillig 883: <dt><span class="sect1"><a href="#general-configuration">6.1. General configuration</a></span></dt>
884: <dt><span class="sect1"><a href="#variables-affecting-build">6.2. Variables affecting the build process</a></span></dt>
885: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
886: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1.1 dsieger 887: <dd><dl>
1.154 rillig 888: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
889: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
890: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 891: </dl></dd>
1.154 rillig 892: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
893: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.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.214 leot 1029: <code class="literal">2021Q4</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.214 leot 1055: <p>The tar file for the stable branch 2021Q4 is in the
1056: directory <code class="filename">pkgsrc-2021Q4</code> and is also called <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/pkgsrc-2021Q4/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p>
1.136 leot 1057: <p>To download the latest pkgsrc stable tarball, run:</p>
1.12 weinem 1058: <pre class="screen">
1.214 leot 1059: <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2021Q4/pkgsrc.tar.gz</code></strong></pre>
1.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.214 leot 1074: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-2021Q4 -P pkgsrc</code></strong>
1.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.214 leot 1159: <span class="quote">“<span class="quote">-rpkgsrc-2021Q4</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.207 leot 1412: to the root users <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/crontab.5"><span class="citerefentry"><span class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
1.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.207 leot 1441: see <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/daily.conf.5"><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a> and <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/security.conf.5"><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for more details.
1.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.207 leot 1629: <p>If you invoke the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> command with
1.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.207 leot 1637: <p>If you want to know the value of a certain <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 1638: definition, then the <code class="varname">VARNAME</code> definition
1639: should be used, in conjunction with the show-var
1.207 leot 1640: target. e.g. to show the expansion of the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.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.207 leot 1653: install a binary package - if available - via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>,
1.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.207 leot 1657: ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>
1.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>
1682: <dt><span class="sect1"><a href="#variables-affecting-installation">6.3. Variables affecting the installation process</a></span></dt>
1683: <dt><span class="sect1"><a href="#conf.compiler">6.4. Selecting and configuring the compiler</a></span></dt>
1684: <dd><dl>
1685: <dt><span class="sect2"><a href="#selecting-the-compiler">6.4.1. Selecting the compiler</a></span></dt>
1686: <dt><span class="sect2"><a href="#conf.cflags">6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
1687: <dt><span class="sect2"><a href="#conf.ldflags">6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 1688: </dl></dd>
1.154 rillig 1689: <dt><span class="sect1"><a href="#developer-advanced-settings">6.5. Developer/advanced settings</a></span></dt>
1690: <dt><span class="sect1"><a href="#selecting-build-options">6.6. Selecting Build Options</a></span></dt>
1.1 dsieger 1691: </dl>
1692: </div>
1.4 rillig 1693: <a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
1.1 dsieger 1694: called <code class="filename">mk.conf</code>. In which directory pkgsrc looks for
1695: that file depends on the installation. On NetBSD, when you use
1.207 leot 1696: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it is in the directory
1.1 dsieger 1697: <code class="filename">/etc/</code>. In all other cases the default location is
1698: <code class="literal">${PREFIX}/etc/</code>, depending on where you told the
1699: bootstrap program to install the binary packages.</p>
1700: <p>The format of the configuration file is that of the usual
1701: BSD-style <code class="filename">Makefile</code>s. The whole pkgsrc configuration
1702: is done by setting variables in this file. Note that you can define all
1703: kinds of variables, and no special error checking (for example for
1.112 rillig 1704: spelling mistakes) takes place.</p>
1.41 asau 1705: <div class="sect1">
1.1 dsieger 1706: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1707: <a name="general-configuration"></a>6.1. General configuration</h2></div></div></div>
1.112 rillig 1708: <p>The following variables apply to all
1.1 dsieger 1709: pkgsrc packages. A complete list of the variables that can be
1710: configured by the user is available in
1711: <code class="filename">mk/defaults/mk.conf</code>, together with some
1712: comments that describe each variable's intent.</p>
1.41 asau 1713: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1714: <li class="listitem"><p><code class="varname">LOCALBASE</code>: Where
1.1 dsieger 1715: packages will be installed. The default is
1716: <code class="filename">/usr/pkg</code>. Do not mix binary packages
1717: with different <code class="varname">LOCALBASE</code>s!</p></li>
1.23 wiz 1718: <li class="listitem"><p><code class="varname">CROSSBASE</code>: Where
1719: <span class="quote">“<span class="quote">cross</span>”</span> category packages will be
1.1 dsieger 1720: installed. The default is
1721: <code class="filename">${LOCALBASE}/cross</code>.</p></li>
1.23 wiz 1722: <li class="listitem"><p><code class="varname">X11BASE</code>: Where
1.1 dsieger 1723: X11 is installed on the system. The default is
1.84 wiz 1724: <code class="filename">/usr/X11R7</code>.</p></li>
1.23 wiz 1725: <li class="listitem"><p><code class="varname">DISTDIR</code>: Where to store the
1.1 dsieger 1726: downloaded copies of the original source distributions used
1727: for building pkgsrc packages. The default is
1728: <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li>
1.23 wiz 1729: <li class="listitem"><p><code class="varname">PKG_DBDIR</code>: Where the
1.1 dsieger 1730: database about installed packages is stored. The default is
1.118 sevan 1731: <code class="filename">/usr/pkg/pkgdb</code>.</p></li>
1.23 wiz 1732: <li class="listitem"><p><code class="varname">MASTER_SITE_OVERRIDE</code>:
1.1 dsieger 1733: If set, override the packages'
1734: <code class="varname">MASTER_SITES</code> with this value.</p></li>
1.23 wiz 1735: <li class="listitem"><p><code class="varname">MASTER_SITE_BACKUP</code>:
1.1 dsieger 1736: Backup location(s) for distribution files and patch files
1737: if not found locally or in
1738: <code class="filename">${MASTER_SITES}</code> or
1739: <code class="filename">${PATCH_SITES}</code> respectively.
1.118 sevan 1740: The defaults is
1741: <code class="filename">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}/</code>.</p></li>
1.23 wiz 1742: <li class="listitem"><p><code class="varname">BINPKG_SITES</code>:
1.1 dsieger 1743: List of sites carrying binary pkgs. <em class="replaceable"><code>rel</code></em> and
1744: <em class="replaceable"><code>arch</code></em> are replaced with OS
1.23 wiz 1745: release (<span class="quote">“<span class="quote">2.0</span>”</span>, etc.) and architecture
1746: (<span class="quote">“<span class="quote">mipsel</span>”</span>, etc.).</p></li>
1747: <li class="listitem"><p><code class="varname">ACCEPTABLE_LICENSES</code>:
1.22 jakllsch 1748: List of acceptable licenses. License names are case-sensitive.
1749: Whenever you try to build a package whose license is not in this
1750: list, you will get an error message. If the license condition is
1751: simple enough, the error message will include specific
1752: instructions on how to change this variable.</p></li>
1.1 dsieger 1753: </ul></div>
1754: </div>
1.41 asau 1755: <div class="sect1">
1.1 dsieger 1756: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1757: <a name="variables-affecting-build"></a>6.2. Variables affecting the build process</h2></div></div></div>
1.108 rillig 1758: <p>
1.1 dsieger 1759: </p>
1.41 asau 1760: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1761: <li class="listitem"><p><code class="varname">PACKAGES</code>: The top level
1.1 dsieger 1762: directory for the binary packages. The default is
1763: <code class="filename">${PKGSRCDIR}/packages</code>.</p></li>
1.23 wiz 1764: <li class="listitem"><p><code class="varname">WRKOBJDIR</code>:
1.1 dsieger 1765: The top level directory where, if defined, the separate
1766: working directories will get created, and symbolically
1767: linked to from <code class="filename">${WRKDIR}</code> (see below).
1768: This is useful for building packages on several
1769: architectures, then <code class="filename">${PKGSRCDIR}</code>
1770: can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code>
1771: is local to every architecture. (It should be noted that
1772: <code class="varname">PKGSRCDIR</code> should not be set by the user
1.14 jmcneill 1773: — it is an internal definition which refers to the
1.1 dsieger 1774: root of the pkgsrc tree. It is possible to have many
1775: pkgsrc tree instances.)</p></li>
1.23 wiz 1776: <li class="listitem"><p><code class="varname">LOCALPATCHES</code>:
1.1 dsieger 1777: Directory for local patches that aren't part of pkgsrc.
1.184 rillig 1778: 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 1779: information.</p></li>
1.23 wiz 1780: <li class="listitem"><p><code class="varname">PKGMAKECONF</code>: Location of
1.10 hubertf 1781: the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file used by a package's
1.1 dsieger 1782: BSD-style Makefile. If this is not set,
1783: <code class="varname">MAKECONF</code> is set to
1784: <code class="filename">/dev/null</code> to avoid picking up
1785: settings used by builds in <code class="filename">/usr/src</code>.</p></li>
1786: </ul></div>
1787: </div>
1.41 asau 1788: <div class="sect1">
1.1 dsieger 1789: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1790: <a name="variables-affecting-installation"></a>6.3. Variables affecting the installation process</h2></div></div></div>
1.198 leot 1791: <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 1792: By default, binary packages of built packages are
1.150 leot 1793: preserved in <code class="filename">${PACKAGES}/All</code>. Setting
1.143 maya 1794: this variable to "no" prevents this.</p></li></ul></div>
1.107 jnemeth 1795: <p>Packages have to support installation into a
1.4 rillig 1796: subdirectory of <code class="varname">WRKDIR</code>. This allows a package
1797: to be built, before the actual filesystem is touched. DESTDIR
1798: support exists in two variations:</p>
1.41 asau 1799: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1800: <li class="listitem"><p>Basic DESTDIR support means that the package
1.24 wiz 1801: installation and packaging is still run as root.</p></li>
1802: <li class="listitem"><p>Full DESTDIR support can run the complete
1803: build, installation and packaging as normal user. Root
1804: privileges are only needed to add packages.</p></li>
1805: </ul></div>
1.4 rillig 1806: <p>With basic DESTDIR support, <strong class="userinput"><code>make
1807: clean</code></strong> needs to be run as root.</p>
1.17 imil 1808: <p>Considering the <code class="filename">foo/bar</code> package,
1809: DESTDIR full support can be tested using the following commands
1810:
1811: </p>
1812: <pre class="programlisting">
1813: <code class="prompt">$</code> id
1814: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
1815: <code class="prompt">$</code> mkdir $HOME/packages
1816: <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
1817: </pre>
1818: <p>
1819:
1820: Verify <code class="varname">DESTDIR</code> full support, no root privileges
1821: should be needed
1822:
1823: </p>
1824: <pre class="programlisting">
1.66 asau 1825: <code class="prompt">$</code> make stage-install
1.17 imil 1826: </pre>
1827: <p>
1828:
1829: Create a package without root privileges
1830:
1831: </p>
1832: <pre class="programlisting">
1.66 asau 1833: <code class="prompt">$</code> make PACKAGES=$HOME/packages package
1.17 imil 1834: </pre>
1835: <p>
1836:
1837: For the following command, you must be able to gain root
1.207 leot 1838: privileges using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/su.1"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
1.17 imil 1839:
1840: </p>
1841: <pre class="programlisting">
1.66 asau 1842: <code class="prompt">$</code> make PACKAGES=$HOME/packages install
1.17 imil 1843: </pre>
1844: <p>
1845:
1846: Then, as a simple user
1847:
1848: </p>
1849: <pre class="programlisting">
1850: <code class="prompt">$</code> make clean
1851: </pre>
1852: <p>
1853:
1854: </p>
1.4 rillig 1855: </div>
1.41 asau 1856: <div class="sect1">
1.4 rillig 1857: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1858: <a name="conf.compiler"></a>6.4. Selecting and configuring the compiler</h2></div></div></div>
1.41 asau 1859: <div class="sect2">
1.1 dsieger 1860: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1861: <a name="selecting-the-compiler"></a>6.4.1. Selecting the compiler</h3></div></div></div>
1.1 dsieger 1862: <p>By default, pkgsrc will use GCC to build packages. This may be
1863: overridden by setting the following variables in /etc/mk.conf:</p>
1.41 asau 1864: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 1865: <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
1866: <dd>
1867: <p>This is a list of values specifying the chain of
1868: compilers to invoke when building packages. Valid values
1869: are:</p>
1.41 asau 1870: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.66 asau 1871: <li class="listitem"><p><code class="varname">ccc</code>:
1872: Compaq C Compilers (Tru64)</p></li>
1873: <li class="listitem"><p><code class="varname">ccache</code>:
1874: compiler cache (chainable)</p></li>
1875: <li class="listitem"><p><code class="varname">clang</code>:
1876: Clang C and Objective-C compiler</p></li>
1.23 wiz 1877: <li class="listitem"><p><code class="varname">distcc</code>:
1.1 dsieger 1878: distributed C/C++ (chainable)</p></li>
1.66 asau 1879: <li class="listitem"><p><code class="varname">f2c</code>:
1880: Fortran 77 to C compiler (chainable)</p></li>
1881: <li class="listitem"><p><code class="varname">icc</code>:
1882: Intel C++ Compiler (Linux)</p></li>
1883: <li class="listitem"><p><code class="varname">ido</code>:
1884: SGI IRIS Development Option cc (IRIX 5)</p></li>
1.23 wiz 1885: <li class="listitem"><p><code class="varname">gcc</code>:
1.1 dsieger 1886: GNU C/C++ Compiler</p></li>
1.66 asau 1887: <li class="listitem"><p><code class="varname">hp</code>:
1888: HP-UX C/aC++ compilers</p></li>
1.23 wiz 1889: <li class="listitem"><p><code class="varname">mipspro</code>:
1.1 dsieger 1890: Silicon Graphics, Inc. MIPSpro (n32/n64)</p></li>
1.66 asau 1891: <li class="listitem"><p><code class="varname">mipspro-ucode</code>:
1.1 dsieger 1892: Silicon Graphics, Inc. MIPSpro (o32)</p></li>
1.23 wiz 1893: <li class="listitem"><p><code class="varname">sunpro</code>:
1.1 dsieger 1894: Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio</p></li>
1.66 asau 1895: <li class="listitem"><p><code class="varname">xlc</code>:
1.118 sevan 1896: IBM's XL C/C++ compiler suite</p></li>
1.1 dsieger 1897: </ul></div>
1898: <p>The default is
1.23 wiz 1899: <span class="quote">“<span class="quote"><code class="varname">gcc</code></span>”</span>. You can use
1.1 dsieger 1900: <code class="varname">ccache</code> and/or
1901: <code class="varname">distcc</code> with an appropriate
1902: <code class="varname">PKGSRC_COMPILER</code> setting,
1.23 wiz 1903: e.g. <span class="quote">“<span class="quote"><code class="varname">ccache gcc</code></span>”</span>. This
1.1 dsieger 1904: variable should always be terminated with a value for
1905: a real compiler. Note that only one real compiler
1.23 wiz 1906: should be listed (e.g. <span class="quote">“<span class="quote"><code class="varname">sunpro gcc</code></span>”</span>
1.1 dsieger 1907: is not allowed).</p>
1908: </dd>
1909: <dt><span class="term"><code class="varname">GCC_REQD</code>:</span></dt>
1910: <dd><p>This specifies the minimum version of GCC to use
1911: when building packages. If the system GCC doesn't
1912: satisfy this requirement, then pkgsrc will build and
1913: install one of the GCC packages to use instead.</p></dd>
1.153 leot 1914: <dt><span class="term"><code class="varname">PYTHON_VERSION_DEFAULT</code>:</span></dt>
1.114 maya 1915: <dd><p>Specifies which version of python to use when several
1916: options are available.</p></dd>
1917: <dt><span class="term"><code class="varname">PKGSRC_FORTRAN</code>:</span></dt>
1.176 gutterid 1918: <dd><p>Specifies the Fortran compiler to use.
1919: The default is <code class="varname">gfortran</code>.</p></dd>
1.114 maya 1920: <dt><span class="term"><code class="varname">GFORTRAN_VERSION</code>:</span></dt>
1921: <dd><p>If <code class="varname">PKGSRC_FORTRAN</code><code class="literal">=</code>
1922: <code class="varname">gfortran</code> is used, this option specifies which
1923: version to use.</p></dd>
1.1 dsieger 1924: </dl></div>
1925: </div>
1.41 asau 1926: <div class="sect2">
1.1 dsieger 1927: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1928: <a name="conf.cflags"></a>6.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div>
1.1 dsieger 1929: <p>If you wish to set the <code class="varname">CFLAGS</code> variable,
1930: please make sure to use the <code class="literal">+=</code> operator
1931: instead of the <code class="literal">=</code> operator:</p>
1932: <pre class="programlisting">
1933: CFLAGS+= -your -flags
1934: </pre>
1935: <p>Using <code class="varname">CFLAGS=</code> (i.e. without the
1.23 wiz 1936: <span class="quote">“<span class="quote">+</span>”</span>) may lead to problems with packages that
1.16 jnemeth 1937: need to add their own flags. You may want to take a look
1.207 leot 1938: 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 1939: package if you're interested in optimization specifically
1940: for the current CPU. </p>
1.1 dsieger 1941: </div>
1.41 asau 1942: <div class="sect2">
1.1 dsieger 1943: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 1944: <a name="conf.ldflags"></a>6.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div>
1.1 dsieger 1945: <p>If you want to pass flags to the linker, both in the configure
1946: step and the build step, you can do this in two ways. Either set
1947: <code class="varname">LDFLAGS</code> or <code class="varname">LIBS</code>. The difference
1948: between the two is that <code class="varname">LIBS</code> will be appended to
1949: the command line, while <code class="varname">LDFLAGS</code> come earlier.
1950: <code class="varname">LDFLAGS</code> is pre-loaded with rpath settings for ELF
1951: machines depending on the setting of <code class="varname">USE_IMAKE</code> or
1952: the inclusion of <code class="filename">mk/x11.buildlink3.mk</code>. As with
1953: <code class="varname">CFLAGS</code>, if you do not wish to override these
1954: settings, use the <code class="literal">+=</code> operator:</p>
1955: <pre class="programlisting">
1956: LDFLAGS+= -your -linkerflags
1957: </pre>
1958: </div>
1959: </div>
1.41 asau 1960: <div class="sect1">
1.1 dsieger 1961: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1962: <a name="developer-advanced-settings"></a>6.5. Developer/advanced settings</h2></div></div></div>
1.84 wiz 1963: <p>
1.1 dsieger 1964: </p>
1.41 asau 1965: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1966: <li class="listitem">
1.1 dsieger 1967: <p><code class="varname">PKG_DEVELOPER</code>:
1968: Run some sanity checks that package developers want:
1969: </p>
1.41 asau 1970: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
1.23 wiz 1971: <li class="listitem"><p>make sure patches apply with zero
1.1 dsieger 1972: fuzz</p></li>
1.23 wiz 1973: <li class="listitem"><p>run check-shlibs to see that all
1.1 dsieger 1974: binaries will find their shared libs.</p></li>
1975: </ul></div>
1976: <p>
1977: </p>
1978: </li>
1.23 wiz 1979: <li class="listitem"><p><code class="varname">PKG_DEBUG_LEVEL</code>: The level
1.1 dsieger 1980: of debugging output which is displayed whilst making and
1981: installing the package. The default value for this is 0,
1982: which will not display the commands as they are executed
1983: (normal, default, quiet operation); the value 1 will display
1984: all shell commands before their invocation, and the value 2
1985: will display both the shell commands before their invocation,
1.112 rillig 1986: as well as their actual execution progress with <span class="command"><strong>set
1987: -x</strong></span>.</p></li>
1.1 dsieger 1988: </ul></div>
1989: <p>
1990: </p>
1991: </div>
1.41 asau 1992: <div class="sect1">
1.1 dsieger 1993: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 1994: <a name="selecting-build-options"></a>6.6. Selecting Build Options</h2></div></div></div>
1.1 dsieger 1995: <p>Some packages have build time options, usually to select
1996: between different dependencies, enable optional support for big
1997: dependencies or enable experimental features.</p>
1998: <p>To see which options, if any, a package supports, and which
1.10 hubertf 1999: options are mutually exclusive, run <span class="command"><strong>make
1.1 dsieger 2000: show-options</strong></span>, for example:</p>
2001: <pre class="programlisting">
2002: The following options are supported by this package:
2003: ssl Enable SSL support.
2004: Exactly one of the following gecko options is required:
2005: firefox Use firefox as gecko rendering engine.
2006: mozilla Use mozilla as gecko rendering engine.
2007: At most one of the following database options may be selected:
2008: mysql Enable support for MySQL database.
2009: pgsql Enable support for PostgreSQL database.
2010:
2011: These options are enabled by default: firefox
2012: These options are currently enabled: mozilla ssl
2013: </pre>
2014: <p>The following variables can be defined in
1.10 hubertf 2015: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to select which options to
1.1 dsieger 2016: enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>,
2017: which can be used to select or disable options for all packages
2018: that support them, and
2019: <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>,
2020: which can be used to select or disable options specifically for
2021: package <em class="replaceable"><code>pkgbase</code></em>. Options listed in
1.23 wiz 2022: these variables are selected, options preceded by <span class="quote">“<span class="quote">-</span>”</span>
1.1 dsieger 2023: are disabled. A few examples:</p>
2024: <pre class="screen">
1.10 hubertf 2025: <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 2026: PKG_DEFAULT_OPTIONS= -arts -dvdread -esound
2027: PKG_OPTIONS.kdebase= debug -sasl
2028: PKG_OPTIONS.apache= suexec </pre>
1.11 rillig 2029: <p>It is important to note that options that were specifically
1.18 snj 2030: suggested by the package maintainer must be explicitly removed if
1.11 rillig 2031: you do not wish to include the option. If you are unsure you can view
2032: the current state with <span class="command"><strong>make show-options</strong></span>.</p>
1.1 dsieger 2033: <p>The following settings are consulted in the order given, and
2034: the last setting that selects or disables an option is
2035: used:</p>
1.23 wiz 2036: <div class="orderedlist"><ol class="orderedlist" type="1">
2037: <li class="listitem"><p>the default options as suggested by the package
1.1 dsieger 2038: maintainer</p></li>
1.23 wiz 2039: <li class="listitem"><p>the options implied by the settings of legacy
1.1 dsieger 2040: variables (see below)</p></li>
1.23 wiz 2041: <li class="listitem"><p><code class="varname">PKG_DEFAULT_OPTIONS</code></p></li>
2042: <li class="listitem"><p><code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code></p></li>
1.1 dsieger 2043: </ol></div>
2044: <p>For groups of mutually exclusive options, the last option
2045: selected is used, all others are automatically disabled. If an
2046: option of the group is explicitly disabled, the previously
2047: selected option, if any, is used. It is an error if no option
2048: from a required group of options is selected, and building the
2049: package will fail.</p>
2050: <p>Before the options framework was introduced, build options
2051: were selected by setting a variable (often named
2052: <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in
1.10 hubertf 2053: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> for each option. To ease
1.1 dsieger 2054: transition to the options framework for the user, these legacy
2055: variables are converted to the appropriate options setting
2056: (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>)
2057: automatically. A warning is issued to prompt the user to update
1.10 hubertf 2058: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to use the options framework
1.1 dsieger 2059: directly. Support for the legacy variables will be removed
2060: eventually.</p>
2061: </div>
2062: </div>
1.41 asau 2063: <div class="chapter">
1.1 dsieger 2064: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2065: <a name="binary"></a>Chapter 7. Creating binary packages</h2></div></div></div>
1.1 dsieger 2066: <div class="toc">
2067: <p><b>Table of Contents</b></p>
1.100 leot 2068: <dl class="toc">
1.154 rillig 2069: <dt><span class="sect1"><a href="#building-a-single-binary-package">7.1. Building a single binary package</a></span></dt>
2070: <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 2071: </dl>
2072: </div>
1.41 asau 2073: <div class="sect1">
1.1 dsieger 2074: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2075: <a name="building-a-single-binary-package"></a>7.1. Building a single binary package</h2></div></div></div>
1.1 dsieger 2076: <p>Once you have built and installed a package, you can create
2077: a <span class="emphasis"><em>binary package</em></span> which can be installed on
1.207 leot 2078: another system with <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
1.1 dsieger 2079: the same package on a group of hosts and wasting CPU time. It also
2080: provides a simple means for others to install your package, should
2081: you distribute it.</p>
2082: <p>To create a binary package, change into the appropriate
1.10 hubertf 2083: directory in pkgsrc, and run <span class="command"><strong>make
1.1 dsieger 2084: package</strong></span>:</p>
2085: <pre class="screen">
1.112 rillig 2086: <code class="prompt">$</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
2087: <code class="prompt">$</code> <strong class="userinput"><code>make package</code></strong>
2088: </pre>
1.1 dsieger 2089: <p>This will build and install your package (if not already done),
2090: and then build a binary package from what was installed. You can
1.10 hubertf 2091: then use the <span class="command"><strong>pkg_*</strong></span> tools to manipulate
1.1 dsieger 2092: it. Binary packages are created by default in
2093: <code class="filename">/usr/pkgsrc/packages</code>, in the form of a
1.207 leot 2094: gzipped tar file. See <a class="xref" href="#logs.package" title="C.2. Packaging figlet">Section C.2, “Packaging figlet”</a> for a
2095: continuation of the above <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/misc/figlet/index.html" target="_top"><code class="filename">misc/figlet</code></a> example.</p>
1.154 rillig 2096: <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 2097: such a binary package.</p>
2098: </div>
1.41 asau 2099: <div class="sect1">
1.1 dsieger 2100: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2101: <a name="settings-for-creationg-of-binary-packages"></a>7.2. Settings for creation of binary packages</h2></div></div></div>
1.184 rillig 2102: <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 2103: </div>
2104: </div>
1.41 asau 2105: <div class="chapter">
1.6 rillig 2106: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2107: <a name="bulk"></a>Chapter 8. Creating binary packages for everything in pkgsrc (bulk
1.6 rillig 2108: builds)</h2></div></div></div>
2109: <div class="toc">
2110: <p><b>Table of Contents</b></p>
1.100 leot 2111: <dl class="toc">
1.154 rillig 2112: <dt><span class="sect1"><a href="#bulk.pre">8.1. Preparations</a></span></dt>
1.180 rillig 2113: <dt><span class="sect1"><a href="#bulk.pbulk">8.2. Running a bulk build</a></span></dt>
1.154 rillig 2114: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">8.2.1. Configuration</a></span></dt></dl></dd>
2115: <dt><span class="sect1"><a href="#bulk.req">8.3. Requirements of a full bulk build</a></span></dt>
1.178 rillig 2116: <dt><span class="sect1"><a href="#bulk.var">8.4. Bulk build variants</a></span></dt>
2117: <dd><dl>
1.179 rillig 2118: <dt><span class="sect2"><a href="#bulk.var.confopt">8.4.1. Detect unknown configure options</a></span></dt>
2119: <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 2120: <dt><span class="sect2"><a href="#bulk.var.builderr">8.4.3. Force compiler options only in the build phase</a></span></dt>
2121: <dt><span class="sect2"><a href="#bulk.var.dirs">8.4.4. Use custom directories</a></span></dt>
2122: <dt><span class="sect2"><a href="#bulk.var.warn">8.4.5. Turn warnings into errors</a></span></dt>
2123: <dt><span class="sect2"><a href="#bulk.var.pkglint">8.4.6. Reject packages for which pkglint reports errors</a></span></dt>
2124: <dt><span class="sect2"><a href="#bulk.var.strings">8.4.7. Reject packages that contain forbidden strings</a></span></dt>
2125: <dt><span class="sect2"><a href="#bulk.var.test">8.4.8. Reject packages whose self-test fails</a></span></dt>
2126: <dt><span class="sect2"><a href="#bulk.var.shvar">8.4.9. Reject packages that use undefined shell variables</a></span></dt>
2127: <dt><span class="sect2"><a href="#bulk.var.quiet">8.4.10. Turn off verbose logging</a></span></dt>
1.178 rillig 2128: </dl></dd>
2129: <dt><span class="sect1"><a href="#creating-cdroms">8.5. Creating a multiple CD-ROM packages collection</a></span></dt>
2130: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">8.5.1. Example of cdpack</a></span></dt></dl></dd>
1.6 rillig 2131: </dl>
2132: </div>
1.175 gutterid 2133: <p>For a number of reasons, you may want to build binary packages
2134: for a large selected set of packages in pkgsrc, or even for all pkgsrc packages.
1.71 wiz 2135: For instance, when you have multiple machines that should run the same software,
2136: it is wasted time if they all build their packages themselves from source.
2137: Or you may want to build a list of packages you want and check them before
1.175 gutterid 2138: deploying onto production systems.
1.71 wiz 2139: There is a way of getting a set of binary packages:
1.175 gutterid 2140: the bulk build system, or pbulk ("p" stands for "parallel").
1.112 rillig 2141: This chapter describes how to set it up.</p>
1.41 asau 2142: <div class="sect1">
1.6 rillig 2143: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2144: <a name="bulk.pre"></a>8.1. Preparations</h2></div></div></div>
1.71 wiz 2145: <p>First of all, you have to decide whether you build all packages
2146: or a limited set of them. Full bulk builds usually consume a lot more resources,
2147: both space and time, than builds for some practical sets of packages.
1.175 gutterid 2148: A number of particularly heavy packages exist that are not actually
2149: interesting to a wide audience. (The approximate resource consumption for a
2150: 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>.)
2151: For limited bulk builds you need to make a list of packages you want to build.
1.112 rillig 2152: Note that all their dependencies will be built, so you don't need to track them manually.
1.71 wiz 2153: </p>
2154: <p>During bulk builds various packages are installed and deinstalled
2155: in <code class="filename">/usr/pkg</code> (or whatever <code class="filename">LOCALBASE</code> is),
2156: so make sure that you don't need any package during the builds.
1.112 rillig 2157: Essentially, you should provide a fresh system, either a chroot environment
1.71 wiz 2158: or something even more restrictive, depending on what the operating system provides,
2159: or dedicate the whole physical machine.
2160: As a useful side effect this makes sure that bulk builds cannot
2161: break anything in your system. There have been numerous cases where
1.6 rillig 2162: certain packages tried to install files outside the
2163: <code class="filename">LOCALBASE</code> or wanted to edit some files in
1.71 wiz 2164: <code class="filename">/etc</code>.
2165: </p>
1.6 rillig 2166: </div>
1.41 asau 2167: <div class="sect1">
1.6 rillig 2168: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.180 rillig 2169: <a name="bulk.pbulk"></a>8.2. Running a bulk build</h2></div></div></div>
2170: <p>Running a bulk build works roughly as follows:</p>
1.41 asau 2171: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2172: <li class="listitem"><p>First, build the pbulk infrastructure in a fresh pkgsrc location.</p></li>
2173: <li class="listitem"><p>Then, build each of the packages from a clean installation directory using the infrastructure.</p></li>
1.15 rillig 2174: </ul></div>
1.41 asau 2175: <div class="sect2">
1.15 rillig 2176: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 2177: <a name="bulk.pbulk.conf"></a>8.2.1. Configuration</h3></div></div></div>
1.112 rillig 2178: <p>To simplify configuration, we provide the helper script <code class="filename">mk/pbulk/pbulk.sh</code>.</p>
1.68 asau 2179: <p>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
2180: Configure network access to fetch distribution files.
1.112 rillig 2181: Create a user with name "pbulk".</p>
1.68 asau 2182: <p>Fetch and extract pkgsrc. Use a command like one of these:</p>
2183: <pre class="screen">
1.151 sevan 2184: <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>
2185: <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 2186: <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 2187: </pre>
2188: <p>Or any other way that fits (e.g., curl, wget).</p>
2189: <p>Deploy and configure pbulk tools, e.g.:</p>
2190: <pre class="screen">
1.118 sevan 2191: <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 2192: <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>
2193: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build</code></strong>
2194: </pre>
2195: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2196: <h3 class="title">Note</h3>
2197: <p><code class="filename">mk.conf.frag</code> is a fragment of
2198: <code class="filename">mk.conf</code> that contains settings you want to
2199: apply to packages you build. For instance,</p>
2200: <pre class="programlisting">
1.112 rillig 2201: PKG_DEVELOPER= yes # perform more checks
2202: X11_TYPE= modular # use pkgsrc X11
2203: SKIP_LICENSE_CHECK= yes # accept all licences (useful
2204: # when building all packages)
1.68 asau 2205: </pre>
2206: </div>
2207: <p>If configured for limited list, replace the list in <code class="filename">/usr/pbulk/etc/pbulk.list</code>
1.112 rillig 2208: with your list of packages, one per line without empty lines or comments. E.g.:</p>
1.68 asau 2209: <pre class="programlisting">
2210: www/firefox
2211: mail/thunderbird
2212: misc/libreoffice4
2213: </pre>
1.69 asau 2214: <p>At this point you can also review configuration in <code class="filename">/usr/pbulk/etc</code>
2215: and make final amendments, if wanted.</p>
1.68 asau 2216: <p>Start it:</p>
2217: <pre class="screen">
2218: <code class="prompt">#</code> <strong class="userinput"><code>/usr/pbulk/bin/bulkbuild</code></strong>
2219: </pre>
2220: <p>After it finishes, you'll have <code class="filename">/mnt</code> filled with distribution files, binary packages, and reports,
2221: plain text summary in <code class="filename">/mnt/bulklog/meta/report.txt</code>
2222: </p>
2223: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2224: <h3 class="title">Note</h3>
2225: <p>The <code class="filename">pbulk.sh</code> script does not cover all possible use cases.
2226: While being ready to run, it serves as a good starting point to understand and build more complex setups.
2227: The script is kept small enough for better understanding.</p>
2228: </div>
2229: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2230: <h3 class="title">Note</h3>
2231: <p>The <code class="filename">pbulk.sh</code> script supports running
1.205 wiz 2232: unprivileged bulk build and helps configuring distributed bulk builds.
2233: Distributed bulk builds support either building in worker chroots
2234: (each node is a path to a different chroot)
2235: that replicate the target system, including the pbulk prefix,
2236: or remote machines (each node is
2237: an IP address that must be accessible over SSH without a password).</p>
1.68 asau 2238: </div>
1.6 rillig 2239: </div>
2240: </div>
1.41 asau 2241: <div class="sect1">
1.6 rillig 2242: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2243: <a name="bulk.req"></a>8.3. Requirements of a full bulk build</h2></div></div></div>
1.71 wiz 2244: <p>A complete bulk build requires lots of disk space. Some of the
2245: disk space can be read-only, some other must be writable. Some can be on
2246: remote filesystems (such as NFS) and some should be local. Some can be
2247: temporary filesystems, others must survive a sudden reboot.</p>
2248: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.205 wiz 2249: <li class="listitem"><p>70 GB for the distfiles (read-write, remote, temporary)</p></li>
2250: <li class="listitem"><p>60 GB for the binary packages (read-write, remote, permanent)</p></li>
1.71 wiz 2251: <li class="listitem"><p>1 GB for the pkgsrc tree (read-only, remote, permanent)</p></li>
2252: <li class="listitem"><p>5 GB for <code class="filename">LOCALBASE</code> (read-write, local, temporary)</p></li>
2253: <li class="listitem"><p>10 GB for the log files (read-write, remote, permanent)</p></li>
2254: <li class="listitem"><p>5 GB for temporary files (read-write, local, temporary)</p></li>
2255: </ul></div>
2256: </div>
2257: <div class="sect1">
2258: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.178 rillig 2259: <a name="bulk.var"></a>8.4. Bulk build variants</h2></div></div></div>
2260: <p>To ensure that pkgsrc packages work in different configurations, it
2261: makes sense to run non-default bulk builds from time to time. This
2262: section lists some ideas for bulk builds that intentionally let packages
2263: fail if they don't follow the pkgsrc style.</p>
2264: <div class="sect2">
2265: <div class="titlepage"><div><div><h3 class="title">
1.179 rillig 2266: <a name="bulk.var.confopt"></a>8.4.1. Detect unknown configure options</h3></div></div></div>
1.178 rillig 2267: <p>Add the following line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2268: <pre class="programlisting">
2269: GNU_CONFIGURE_STRICT= yes
2270: </pre>
2271: <p>When a package fails this additional check, the most common cause
2272: is that the configure option was valid for an older version of the
2273: package but does not apply anymore. In that case, just remove it.</p>
2274: </div>
2275: <div class="sect2">
2276: <div class="titlepage"><div><div><h3 class="title">
1.179 rillig 2277: <a name="bulk.var.comperr"></a>8.4.2. Detect classes of bugs by forcing compiler warnings</h3></div></div></div>
1.178 rillig 2278: <p>The job of a compiler is not restricted to producing executable
1.179 rillig 2279: code, most compilers also detect typical programming mistakes. The pkgsrc
2280: compiler wrappers make it easy to force compiler options when the package
2281: is built. This can be used to find typical bugs across all packages that
2282: are in pkgsrc. By reporting these bugs upstream, the packages will be
2283: more reliable with the next updates.</p>
2284: <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 2285: <pre class="programlisting">
2286: CFLAGS+= -Werror=char-subscripts
1.179 rillig 2287: CFLAGS+= -Werror=implicit-function-declaration
1.178 rillig 2288: </pre>
1.179 rillig 2289: <p>When a package fails to build using these stricter compiler
2290: options, document the circumstances in which the compiler produced the
2291: error message. This includes:</p>
1.178 rillig 2292: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
2293: <li class="listitem"><p>The platform
2294: (<code class="varname">MACHINE_PLATFORM</code>)</p></li>
2295: <li class="listitem"><p>The source file</p></li>
2296: <li class="listitem"><p>An excerpt of the code. GCC and Clang already do this as
2297: part of the diagnostic.</p></li>
1.179 rillig 2298: <li class="listitem"><p>The exact error message from the compiler.</p></li>
1.178 rillig 2299: </ul></div>
2300: <p>If a package produces these error messages, but the package is
1.179 rillig 2301: 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
2302: in the next builds:</p>
1.178 rillig 2303: <pre class="programlisting">
1.179 rillig 2304: .if ${PKGPATH} == category/package
1.178 rillig 2305: # Version ${VERSION} failed on ${MACHINE_PLATFORM}:
2306: # error message
2307: # code
1.179 rillig 2308: # Reason why the code does not need to be fixed.
1.178 rillig 2309: BUILDLINK_TRANSFORM+= rm:-Werror=char-subscripts
1.179 rillig 2310: .endif
1.178 rillig 2311: </pre>
2312: <p>If the error messages from the compiler are valid and the code
1.179 rillig 2313: needs to be fixed, prepare a local patch (see
2314: <code class="varname">LOCALPATCHES</code>) and report the bug to the upstream
2315: authors of the package, providing them with the information you collected
2316: above.</p>
2317: <p>Patches that are not essential for the package to work should only
2318: be reported upstream but not committed to pkgsrc, to make future updates
2319: easier.</p>
1.178 rillig 2320: </div>
2321: <div class="sect2">
2322: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2323: <a name="bulk.var.builderr"></a>8.4.3. Force compiler options only in the build phase</h3></div></div></div>
2324: <p>When adding custom compiler flags via <code class="varname">CFLAGS</code>,
2325: these apply to all phases of the package build process. Especially in the
2326: configure phase, adding <code class="literal">-Werror</code> leads to wrong
2327: decisions. The GNU configure scripts feed many small test programs to the
2328: C compiler to see whether certain headers are available, functions are
2329: defined in a library and programs can be run. In many cases these
2330: programs would not survive a strict compiler run with <code class="literal">-Wall
2331: -Wextra -Werror</code>.</p>
2332: <p>The pkgsrc infrastructure is flexible enough to support compiler
2333: options being added between the <code class="literal">configure</code> and
2334: <code class="literal">build</code> phases. It's a little more complicated than the
2335: other examples in this section but still easy enough.</p>
2336: <p>The basic idea is to use the pkgsrc compiler wrapper to inject the
2337: desired compiler options. The compiler wrapper's original task is to hide
2338: unwanted directories of include files and to normalize compiler options.
2339: It does this by wrapping the compiler command and rewriting the command
2340: line. To see this in action, run <span class="command"><strong>bmake patch</strong></span> in a
2341: package directory and examine the
2342: <code class="filename">work/.cwrappers/config</code> directory. It contains
2343: individual configurations for the C compiler and the related tools. The
2344: plan is to find a hook between the configure and build phases, and to
2345: modify these configuration files at that point.</p>
2346: <p>To find this hook, have a look at
2347: <code class="filename">mk/build/build.mk</code>, which contains among others the
2348: <code class="literal">pre-build-checks-hook</code>. The word
2349: <code class="literal">checks</code> doesn't quite fit, but the
2350: <code class="literal">pre-build-hook</code> sounds good enough.</p>
2351: <p>The code to be included in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> is:</p>
2352: <pre class="programlisting">
2353: # Just a few example options.
2354: BUILD_ONLY_CFLAGS= -Wall -Werror -O2 -DTEMPDIR='"/tmp"'
2355:
2356: .if ${BUILD_ONLY_CFLAGS:U:M*}
2357: pre-build-checks-hook: add-build-only-cflags
2358:
2359: add-build-only-cflags: .PHONY
2360: ${RUN} cd ${CWRAPPERS_CONFIG_DIR}; \
2361: ${TEST} ! -f ${.TARGET} || exit 0; \
2362: for flag in ${BUILD_ONLY_CFLAGS}; do \
2363: ${ECHO} "append=$$flag" >> cc; \
2364: done; \
2365: > ${.TARGET}
2366: .endif
2367: </pre>
2368: <p>(When editing the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, make sure that the commands of the
2369: <code class="literal">add-build-only-cflags</code> target are indented with a tab,
2370: not with spaces.)</p>
2371: <p>The condition in the <code class="literal">.if</code> statement contains the
2372: <code class="literal">:U</code> modifier to prevent parse errors if the variable
2373: should be undefined, possibly because it is only defined for a subset of
2374: the packages. The <code class="literal">:M*</code> modifier ensures that there is
2375: at least one compiler option, to prevent a syntax error in the shell
2376: parser.</p>
2377: <p>The code around the <code class="literal">${.TARGET}</code> variable ensures
2378: that the additional compiler options are only appended once, even if
2379: <span class="command"><strong>bmake build</strong></span> is run multiple times. To do this, it
2380: creates a marker file.</p>
2381: <p>To verify that this setup works, run <span class="command"><strong>bmake
2382: configure</strong></span> in a package directory. Up to now, everything works
2383: as usual. Examine the directory
2384: <code class="filename">work/.cwrappers/config</code> to see that the compiler
2385: options from <code class="varname">BUILD_ONLY_CFLAGS</code> are not yet added to
2386: the file <code class="filename">cc</code>. Examine the tail of the
2387: <code class="filename">work/.work.log</code> file to see that the normal compiler
2388: options are used.</p>
2389: <p>Now run <span class="command"><strong>bmake build</strong></span>. This will append the
2390: options to the file <code class="filename">cc</code> and will create the marker
2391: file in the same directory. After that, the build starts as usual, but
2392: with the added compiler options. Examine the tail of the file
2393: <code class="filename">work/.work.log</code> to see that the lines starting with
2394: <code class="literal">[*]</code> don't contain the compiler options, but the
2395: corresponding lines starting with <code class="literal"><.></code> do end
2396: with these options.</p>
2397: <p>Building packages using this setup variant and fixing the resulting
2398: 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>
2399: </div>
2400: <div class="sect2">
2401: <div class="titlepage"><div><div><h3 class="title">
2402: <a name="bulk.var.dirs"></a>8.4.4. Use custom directories</h3></div></div></div>
1.178 rillig 2403: <p>Some directories like <code class="varname">PREFIX</code>,
2404: <code class="varname">VARBASE</code>, <code class="varname">PKG_SYSCONFDIR</code>,
2405: <code class="varname">PKGMANDIR</code>, <code class="varname">PKG_INFODIR</code> can be
2406: configured in pkgsrc. Set these to arbitrary paths during bootstrap or
2407: afterwards in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2408: <pre class="programlisting">
2409: PREFIX= /a-random-uuid
2410: PKG_SYSCONFDIR= /a-random-uuid
2411: VARBASE= /a-random-uuid
2412: PKGMANDIR= a-random-uuid
2413: PKG_INFODIR= a-random-uuid
2414: </pre>
2415: </div>
2416: <div class="sect2">
2417: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2418: <a name="bulk.var.warn"></a>8.4.5. Turn warnings into errors</h3></div></div></div>
1.178 rillig 2419: <p>When building a package, warnings are typically ignored since they
2420: just flow by and do not cause the build to fail immediately. To find
2421: these warnings, redefine them to errors in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2422: <pre class="programlisting">
2423: DELAYED_WARNING_MSG= ${DELAYED_ERROR_MSG} "(was warning)"
2424: WARNING_MSG= ${FAIL_MSG} "(was warning)"
2425: </pre>
2426: <p>(There are many more classes of warnings in pkgsrc, and most of
2427: them can be redefined with a simple definition like above.</p>
1.179 rillig 2428: <p>If a package suggests to add <code class="varname">USE_TOOLS+=perl</code> to
1.178 rillig 2429: the package Makefile, research whether the package actually needs Perl.
2430: If it does, add <code class="varname">USE_TOOLS+=perl</code> to the package
2431: Makefile, and if it doesn't, add
2432: <code class="varname">TOOLS_BROKEN+=perl</code>.</p>
2433: </div>
2434: <div class="sect2">
2435: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2436: <a name="bulk.var.pkglint"></a>8.4.6. Reject packages for which pkglint reports errors</h3></div></div></div>
1.178 rillig 2437: <p>Using pkglint as part of the regular build process is mostly a
2438: waste of time. If you want to fix some of the warnings, just run pkglint
2439: recursively on the whole pkgsrc tree. This will take a few minutes (up to
2440: 10), which is much faster than a complete bulk build.</p>
2441: </div>
2442: <div class="sect2">
2443: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2444: <a name="bulk.var.strings"></a>8.4.7. Reject packages that contain forbidden strings</h3></div></div></div>
1.178 rillig 2445: <p>To ensure that the binary packages don't contain references to the
2446: build directory, there is already <code class="varname">CHECK_WRKREF</code>. If
2447: that variable includes the item <code class="literal">extra</code>, it is
2448: possible to define additional patterns that must not appear in any
2449: installed file. This is specified in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2450: <pre class="programlisting">
2451: CHECK_WRKREF= extra
2452: CHECK_WRKREF_EXTRA_DIRS+= /usr/local
2453: CHECK_WRKREF_EXTRA_DIRS+= /usr/pkg
2454: CHECK_WRKREF_EXTRA_DIRS+= @[A-Z][A-Z]*@
2455: </pre>
2456: <p>The above patterns will probably generate many false positives,
2457: therefore the results need to be taken with a grain of salt.</p>
2458: </div>
2459: <div class="sect2">
2460: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2461: <a name="bulk.var.test"></a>8.4.8. Reject packages whose self-test fails</h3></div></div></div>
1.178 rillig 2462: <p>To run the test suites that come with each package, add this line
2463: to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2464: <pre class="programlisting">
2465: PKGSRC_RUN_TEST= yes
2466: </pre>
2467: <p>Be prepared that even the most basic packages fail this test. When
2468: doing a bulk build with this, it will often abort in the early phase
2469: where the packages are scanned for their dependencies since there are
2470: cyclic dependencies. There is still a lot to do in this area.</p>
2471: </div>
2472: <div class="sect2">
2473: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2474: <a name="bulk.var.shvar"></a>8.4.9. Reject packages that use undefined shell variables</h3></div></div></div>
1.178 rillig 2475: <p>To catch typos in the shell snippets from the Makefile fragments,
2476: add the <code class="literal">-u</code> flag to most of the commands by adding this
2477: line to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2478: <pre class="programlisting">
2479: RUN= @set -eu;
2480: </pre>
1.181 rillig 2481: <p>After that, ensure that none of the bulk build log files (even
2482: those for successfully built packages) contains the string
2483: <code class="literal">parameter not set</code> or whatever error message the
2484: command <span class="command"><strong>sh -ceu '$undefined'</strong></span> outputs.</p>
1.178 rillig 2485: <p>See <code class="filename">mk/misc/common.mk</code> for the existing
2486: definition.</p>
2487: </div>
2488: <div class="sect2">
2489: <div class="titlepage"><div><div><h3 class="title">
1.181 rillig 2490: <a name="bulk.var.quiet"></a>8.4.10. Turn off verbose logging</h3></div></div></div>
1.178 rillig 2491: <p>The build logs of a package are often quite long. This allows error
2492: messages or other interesting details to hide between the noise. To make
2493: the actual error message stand out more, add these lines to
2494: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
2495: <pre class="programlisting">
2496: GNU_CONFIGURE_QUIET= yes
2497: MAKE_FLAGS+= -s
2498: </pre>
2499: <p>The <code class="literal">-s</code> option works for both GNU Make and BSD
2500: Make. On exotic platforms with their own make, it may be a little
2501: different.</p>
2502: </div>
2503: </div>
2504: <div class="sect1">
2505: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2506: <a name="creating-cdroms"></a>8.5. Creating a multiple CD-ROM packages collection</h2></div></div></div>
1.1 dsieger 2507: <p>After your pkgsrc bulk-build has completed, you may wish to
2508: create a CD-ROM set of the resulting binary packages to assist
2509: in installing packages on other machines. The
1.207 leot 2510: <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 2511: a simple tool for creating the ISO 9660 images.
1.10 hubertf 2512: <span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a
1.1 dsieger 2513: way that keeps all the dependencies for a given package on the same
2514: CD as that package.</p>
1.41 asau 2515: <div class="sect2">
1.1 dsieger 2516: <div class="titlepage"><div><div><h3 class="title">
1.178 rillig 2517: <a name="cdpack-example"></a>8.5.1. Example of cdpack</h3></div></div></div>
1.1 dsieger 2518: <p>Complete documentation for cdpack is found in the cdpack(1)
2519: man page. The following short example assumes that the binary
2520: packages are left in
2521: <code class="filename">/usr/pkgsrc/packages/All</code> and that
2522: sufficient disk space exists in <code class="filename">/u2</code> to
2523: hold the ISO 9660 images.</p>
2524: <pre class="screen">
2525: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /u2/images</code></strong>
2526: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong>
2527: <code class="prompt">#</code> <strong class="userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong>
2528: </pre>
2529: <p>If you wish to include a common set of files
2530: (<code class="filename">COPYRIGHT</code>, <code class="filename">README</code>,
2531: etc.) on each CD in the collection, then you need to create a
1.175 gutterid 2532: directory which contains these files, e.g.:</p>
1.1 dsieger 2533: <pre class="screen">
2534: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common</code></strong>
2535: <code class="prompt">#</code> <strong class="userinput"><code>echo "This is a README" > /tmp/common/README</code></strong>
2536: <code class="prompt">#</code> <strong class="userinput"><code>echo "Another file" > /tmp/common/COPYING</code></strong>
2537: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common/bin</code></strong>
2538: <code class="prompt">#</code> <strong class="userinput"><code>echo "#!/bin/sh" > /tmp/common/bin/myscript</code></strong>
2539: <code class="prompt">#</code> <strong class="userinput"><code>echo "echo Hello world" >> /tmp/common/bin/myscript</code></strong>
2540: <code class="prompt">#</code> <strong class="userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong>
2541: </pre>
2542: <p>Now create the images:</p>
2543: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong></pre>
2544: <p>Each image will contain <code class="filename">README</code>,
2545: <code class="filename">COPYING</code>, and <code class="filename">bin/myscript</code>
2546: in their root directories.</p>
2547: </div>
2548: </div>
2549: </div>
1.41 asau 2550: <div class="chapter">
1.1 dsieger 2551: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2552: <a name="files"></a>Chapter 9. Directory layout of the installed files</h2></div></div></div>
1.1 dsieger 2553: <div class="toc">
2554: <p><b>Table of Contents</b></p>
1.100 leot 2555: <dl class="toc">
1.154 rillig 2556: <dt><span class="sect1"><a href="#files.localbase">9.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
2557: <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 2558: </dl>
2559: </div>
2560: <p>The files that are installed by pkgsrc are organized in a way that
2561: is similar to what you find in the <code class="filename">/usr</code> directory
2562: of the base system. But some details are different. This is because
2563: pkgsrc initially came from FreeBSD and had adopted its file system
2564: hierarchy. Later it was largely influenced by NetBSD. But no matter
2565: which operating system you are using pkgsrc with, you can expect the
2566: same layout for pkgsrc.</p>
2567: <p>There are mainly four root directories for pkgsrc, which are all
2568: configurable in the <code class="filename">bootstrap/bootstrap</code> script.
2569: When pkgsrc has been installed as root, the default locations
2570: are:</p>
2571: <pre class="programlisting">
2572: LOCALBASE= /usr/pkg
2573: PKG_SYSCONFBASE= /usr/pkg/etc
2574: VARBASE= /var
1.119 sevan 2575: PKG_DBDIR= /usr/pkg/pkgdb
1.1 dsieger 2576: </pre>
2577: <p>In unprivileged mode (when pkgsrc has been installed as any other
2578: user), the default locations are:</p>
2579: <pre class="programlisting">
2580: LOCALBASE= ${HOME}/pkg
2581: PKG_SYSCONFBASE= ${HOME}/pkg/etc
2582: VARBASE= ${HOME}/pkg/var
1.119 sevan 2583: PKG_DBDIR= ${HOME}/pkg/pkgdb
1.1 dsieger 2584: </pre>
2585: <p>What these four directories are for, and what they look like is
2586: explained below.</p>
1.41 asau 2587: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2588: <li class="listitem"><p><code class="varname">LOCALBASE</code> corresponds to the
1.1 dsieger 2589: <code class="filename">/usr</code> directory in the base system. It is the
1.23 wiz 2590: <span class="quote">“<span class="quote">main</span>”</span> directory where the files are installed and contains
1.1 dsieger 2591: the well-known subdirectories like <code class="filename">bin</code>,
2592: <code class="filename">include</code>, <code class="filename">lib</code>,
2593: <code class="filename">share</code> and
2594: <code class="filename">sbin</code>.</p></li>
1.23 wiz 2595: <li class="listitem"><p><code class="varname">VARBASE</code> corresponds to
1.1 dsieger 2596: <code class="filename">/var</code> in the base system. Some programs (especially
2597: games, network daemons) need write access to it during normal
2598: operation.</p></li>
1.23 wiz 2599: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR</code> corresponds to
1.1 dsieger 2600: <code class="filename">/etc</code> in the base system. It contains configuration
1.10 hubertf 2601: 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 2602: itself.</p></li>
2603: </ul></div>
1.41 asau 2604: <div class="sect1">
1.1 dsieger 2605: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2606: <a name="files.localbase"></a>9.1. File system layout in <code class="literal">${LOCALBASE}</code>
1.1 dsieger 2607: </h2></div></div></div>
2608: <p>The following directories exist in a typical pkgsrc installation
2609: in <code class="filename">${LOCALBASE}</code>.</p>
1.41 asau 2610: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2611: <dt><span class="term"><code class="filename">bin</code></span></dt>
2612: <dd><p>Contains executable programs that are intended to be
2613: directly used by the end user.</p></dd>
2614: <dt><span class="term"><code class="filename">emul</code></span></dt>
2615: <dd><p>Contains files for the emulation layers of various other
2616: operating systems, especially for
2617: NetBSD.</p></dd>
2618: <dt><span class="term"><code class="filename">etc</code> (the usual location of
2619: <code class="filename">${PKG_SYSCONFDIR}</code>)</span></dt>
2620: <dd><p>Contains
2621: the configuration files.</p></dd>
2622: <dt><span class="term"><code class="filename">include</code></span></dt>
2623: <dd><p>Contains headers for the C and C++ programming
2624: languages.</p></dd>
2625: <dt><span class="term"><code class="filename">info</code></span></dt>
2626: <dd><p>Contains GNU info files of various
2627: packages.</p></dd>
2628: <dt><span class="term"><code class="filename">lib</code></span></dt>
2629: <dd><p>Contains shared and static
2630: libraries.</p></dd>
2631: <dt><span class="term"><code class="filename">libdata</code></span></dt>
2632: <dd><p>Contains data files that don't change after
2633: installation. Other data files belong into
2634: <code class="filename">${VARBASE}</code>.</p></dd>
2635: <dt><span class="term"><code class="filename">libexec</code></span></dt>
2636: <dd><p>Contains programs that are not intended to be used by
2637: end users, such as helper programs or network
2638: daemons.</p></dd>
2639: <dt><span class="term"><code class="filename">libexec/cgi-bin</code></span></dt>
2640: <dd><p>Contains programs that are intended to be executed as
2641: CGI scripts by a web server.</p></dd>
2642: <dt><span class="term"><code class="filename">man</code> (the usual value of
2643: <code class="filename">${PKGMANDIR}</code>)</span></dt>
2644: <dd><p>Contains brief
2645: documentation in form of manual pages.</p></dd>
2646: <dt><span class="term"><code class="filename">sbin</code></span></dt>
2647: <dd><p>Contains programs that are intended to be used only by
2648: the super-user.</p></dd>
2649: <dt><span class="term"><code class="filename">share</code></span></dt>
2650: <dd><p>Contains platform-independent data files that don't
2651: change after installation.</p></dd>
2652: <dt><span class="term"><code class="filename">share/doc</code></span></dt>
2653: <dd><p>Contains documentation files provided by the
2654: packages.</p></dd>
2655: <dt><span class="term"><code class="filename">share/examples</code></span></dt>
2656: <dd><p>Contains example files provided by the packages. Among
2657: others, the original configuration files are saved here and copied to
2658: <code class="filename">${PKG_SYSCONFDIR}</code> during
2659: installation.</p></dd>
2660: <dt><span class="term"><code class="filename">share/examples/rc.d</code></span></dt>
2661: <dd><p>Contains the original files for rc.d
2662: scripts.</p></dd>
2663: <dt><span class="term"><code class="filename">var</code> (the usual location of
2664: <code class="filename">${VARBASE}</code>)</span></dt>
2665: <dd><p>Contains files
2666: that may be modified after
2667: installation.</p></dd>
2668: </dl></div>
2669: </div>
1.41 asau 2670: <div class="sect1">
1.1 dsieger 2671: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2672: <a name="files.varbase"></a>9.2. File system layout in <code class="literal">${VARBASE}</code>
1.1 dsieger 2673: </h2></div></div></div>
1.41 asau 2674: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2675: <dt><span class="term"><code class="filename">db/pkg</code> (the usual location of
2676: <code class="filename">${PKG_DBDIR}</code>)</span></dt>
2677: <dd><p>Contains
2678: information about the currently installed
2679: packages.</p></dd>
2680: <dt><span class="term"><code class="filename">games</code></span></dt>
2681: <dd><p>Contains highscore
2682: files.</p></dd>
2683: <dt><span class="term"><code class="filename">log</code></span></dt>
2684: <dd><p>Contains log files.</p></dd>
2685: <dt><span class="term"><code class="filename">run</code></span></dt>
2686: <dd><p>Contains informational files about daemons that are
2687: currently running.</p></dd>
2688: </dl></div>
2689: </div>
2690: </div>
1.41 asau 2691: <div class="chapter">
1.1 dsieger 2692: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 2693: <a name="faq"></a>Chapter 10. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 2694: <div class="toc">
2695: <p><b>Table of Contents</b></p>
1.100 leot 2696: <dl class="toc">
1.154 rillig 2697: <dt><span class="sect1"><a href="#mailing-list-pointers">10.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
2698: <dt><span class="sect1"><a href="#faq-pkgtools">10.2. Utilities for package management (pkgtools)</a></span></dt>
2699: <dt><span class="sect1"><a href="#non-root-pkgsrc">10.3. How to use pkgsrc as non-root</a></span></dt>
2700: <dt><span class="sect1"><a href="#resume-transfers">10.4. How to resume transfers when fetching distfiles?</a></span></dt>
2701: <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>
2702: <dt><span class="sect1"><a href="#fetch-behind-firewall">10.6. How to fetch files from behind a firewall</a></span></dt>
2703: <dt><span class="sect1"><a href="#fetch-https">10.7. How to fetch files from HTTPS sites</a></span></dt>
2704: <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>
2705: <dt><span class="sect1"><a href="#fetching-all-distfiles">10.9. How to fetch all distfiles at once</a></span></dt>
2706: <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 2707: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.154 rillig 2708: <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 2709: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">10.12. Using 'sudo' or `priv` with pkgsrc</a></span></dt>
1.154 rillig 2710: <dt><span class="sect1"><a href="#faq.conf">10.13. How do I change the location of configuration files?</a></span></dt>
2711: <dt><span class="sect1"><a href="#audit-packages">10.14. Automated security checks</a></span></dt>
2712: <dt><span class="sect1"><a href="#ufaq-cflags">10.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
2713: <dt><span class="sect1"><a href="#ufaq-fail">10.16. A package does not build. What shall I do?</a></span></dt>
2714: <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 2715: </dl>
2716: </div>
2717: <p>This section contains hints, tips & tricks on special things in
2718: pkgsrc that we didn't find a better place for in the previous chapters, and
2719: it contains items for both pkgsrc users and developers.</p>
1.41 asau 2720: <div class="sect1">
1.1 dsieger 2721: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2722: <a name="mailing-list-pointers"></a>10.1. Are there any mailing lists for pkg-related discussion?</h2></div></div></div>
1.1 dsieger 2723: <p>The following mailing lists may be of interest to pkgsrc users:</p>
1.41 asau 2724: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2725: <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 2726: This is a general purpose list for most issues regarding
2727: pkgsrc, regardless of platform, e.g. soliciting user help
2728: for pkgsrc configuration, unexpected build failures, using
2729: particular packages, upgrading pkgsrc installations,
2730: questions regarding the pkgsrc release branches, etc. General announcements or
2731: proposals for changes that impact the pkgsrc user community,
2732: e.g. major infrastructure changes, new features, package
2733: removals, etc., may also be posted.</p></li>
1.174 leot 2734: <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 2735: A list where the results of pkgsrc bulk builds are sent and
2736: discussed.</p></li>
1.174 leot 2737: <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 2738: This list is for those who are interested in getting a
2739: commit message for every change committed to pkgsrc. It is
2740: also available in digest form, meaning one daily message
2741: containing all commit messages for changes to the package
2742: source tree in that 24 hour period.</p></li>
2743: </ul></div>
2744: <p>To subscribe, do:</p>
2745: <pre class="programlisting">
2746: <code class="prompt">%</code> echo subscribe <em class="replaceable"><code>listname</code></em> | mail majordomo@NetBSD.org
2747: </pre>
2748: <p>Archives for all these mailing lists are available from
1.174 leot 2749: <a class="ulink" href="https://mail-index.NetBSD.org/" target="_top">https://mail-index.NetBSD.org/</a>.</p>
1.1 dsieger 2750: </div>
1.41 asau 2751: <div class="sect1">
1.1 dsieger 2752: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2753: <a name="faq-pkgtools"></a>10.2. Utilities for package management (pkgtools)</h2></div></div></div>
1.1 dsieger 2754: <p>The directory <code class="filename">pkgsrc/pkgtools</code> contains
2755: a number of useful utilities for both users and developers of pkgsrc. This
1.121 sevan 2756: section attempts only to make the reader aware of some of the utilities and when
1.1 dsieger 2757: they might be useful, and not to duplicate the documentation that comes
2758: with each package.</p>
2759: <p>Utilities used by pkgsrc (automatically installed when needed):</p>
1.207 leot 2760: <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 2761: Symlinks for use by buildlink.</p></li></ul></div>
2762: <p>OS tool augmentation (automatically installed when needed):</p>
1.41 asau 2763: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2764: <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 2765: Calculates various kinds of checksums (including SHA3).</p></li>
1.207 leot 2766: <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 2767: Compatibility library for pkgsrc tools.</p></li>
1.207 leot 2768: <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 2769: non-BSD systems due to lack of native mtree.</p></li>
1.207 leot 2770: <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 2771: Up-to-date replacement for
2772: <code class="filename">/usr/sbin/pkg_install</code>, or for use on operating
2773: systems where pkg_install is not present.</p></li>
2774: </ul></div>
2775: <p>Utilities used by pkgsrc (not automatically installed):</p>
1.41 asau 2776: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2777: <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 2778: Create a binary package from an
1.10 hubertf 2779: already-installed package. Used by <span class="command"><strong>make replace</strong></span> to
1.1 dsieger 2780: save the old package.</p></li>
1.207 leot 2781: <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 2782: Adds extra functionality to pkgsrc, allowing it to fetch distfiles
2783: from multiple locations. It currently supports the following
2784: methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li>
1.207 leot 2785: <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 2786: the best compiler flags to optimise code for your current
1.23 wiz 2787: CPU and compiler. </p></li>
1.1 dsieger 2788: </ul></div>
2789: <p>Utilities for keeping track of installed packages, being up to date,
2790: etc:</p>
1.41 asau 2791: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2792: <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 2793: update tool similar to apt(1). Download, install, and upgrade
2794: binary packages easily.</p></li>
1.207 leot 2795: <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 2796: packages whose installed versions do not match the latest pkgsrc
2797: entries.</p></li>
1.207 leot 2798: <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 2799: dependency graphs of packages, to aid in choosing a strategy for
2800: updating.</p></li>
1.207 leot 2801: <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
2802: 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>
2803: <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 2804: pkglint(1) program checks a pkgsrc entry for errors.</p></li>
1.207 leot 2805: <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 2806: does various checks on the complete pkgsrc system.</p></li>
1.207 leot 2807: <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 2808: packages you have installed.</p></li>
2809: </ul></div>
2810: <p>Utilities for people maintaining or creating individual packages:</p>
1.41 asau 2811: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2812: <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 2813: making and maintaining patches for a package (includes pkgdiff,
2814: pkgvi, mkpatches, etc.).</p></li>
1.207 leot 2815: <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 2816: converting to pkgsrc.</p></li>
2817: </ul></div>
2818: <p>Utilities for people maintaining pkgsrc (or: more obscure pkg
2819: utilities)</p>
1.41 asau 2820: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 2821: <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 2822: packages in a chrooted area.</p></li>
1.207 leot 2823: <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 2824: kernel version for chrooted cross builds.</p></li>
2825: </ul></div>
2826: </div>
1.41 asau 2827: <div class="sect1">
1.1 dsieger 2828: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2829: <a name="non-root-pkgsrc"></a>10.3. How to use pkgsrc as non-root</h2></div></div></div>
1.108 rillig 2830: <p>To install packages from source as a non-root user, download
1.154 rillig 2831: 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 2832: directory and run the command <span class="command"><strong>./bootstrap/bootstrap
2833: --unprivileged</strong></span>.</p>
2834: <p>This will install the binary part of pkgsrc to
2835: <code class="filename">~/pkg</code> and put the pkgsrc configuration <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
2836: into <code class="filename">~/pkg/etc</code>.</p>
2837: <p>For more details, see <code class="filename">mk/unprivileged.mk</code>.</p>
1.1 dsieger 2838: </div>
1.41 asau 2839: <div class="sect1">
1.1 dsieger 2840: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2841: <a name="resume-transfers"></a>10.4. How to resume transfers when fetching distfiles?</h2></div></div></div>
1.1 dsieger 2842: <p>By default, resuming transfers in pkgsrc is disabled, but you can
2843: enable this feature by adding the option
2844: <code class="varname">PKG_RESUME_TRANSFERS=YES</code> into
1.10 hubertf 2845: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. If, during a fetch step, an incomplete
1.1 dsieger 2846: distfile is found, pkgsrc will try to resume it.</p>
2847: <p>You can also
1.61 wiz 2848: use a different program than the platform default program by changing the
1.16 jnemeth 2849: <code class="varname">FETCH_USING</code> variable. You can specify the program by
2850: using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
2851: by using the value manual. A value of custom disables the system defaults
2852: and dependency tracking for the fetch program. In that case you have to
2853: provide <code class="varname">FETCH_CMD</code>, <code class="varname">FETCH_BEFORE_ARGS</code>,
2854: <code class="varname">FETCH_RESUME_ARGS</code>, <code class="varname">FETCH_OUTPUT_ARGS</code>,
2855: <code class="varname">FETCH_AFTER_ARGS</code>.</p>
1.1 dsieger 2856: <p>For example, if you want to use
1.16 jnemeth 2857: <code class="filename">wget</code> to download, you'll have to use something
1.1 dsieger 2858: like:</p>
2859: <pre class="programlisting">
1.112 rillig 2860: FETCH_USING= wget
1.1 dsieger 2861: </pre>
2862: </div>
1.41 asau 2863: <div class="sect1">
1.1 dsieger 2864: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2865: <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 2866: <p>If you want to use modular X.org from pkgsrc instead of your system's own X11
1.1 dsieger 2867: (<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...)
2868: you will have to add the following line into
1.10 hubertf 2869: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 2870: <pre class="programlisting">
1.4 rillig 2871: X11_TYPE=modular
1.1 dsieger 2872: </pre>
2873: </div>
1.41 asau 2874: <div class="sect1">
1.1 dsieger 2875: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2876: <a name="fetch-behind-firewall"></a>10.6. How to fetch files from behind a firewall</h2></div></div></div>
1.1 dsieger 2877: <p>If you are sitting behind a firewall which does not allow direct
2878: connections to Internet hosts (i.e. non-NAT), you may specify the
2879: relevant proxy hosts. This is done using an environment variable in the
2880: form of a URL, e.g. in Amdahl, the machine
1.23 wiz 2881: <span class="quote">“<span class="quote">orpheus.amdahl.com</span>”</span> is one of the firewalls, and it uses
1.1 dsieger 2882: port 80 as the proxy port number. So the proxy environment variables
2883: are:</p>
2884: <pre class="programlisting">
2885: ftp_proxy=ftp://orpheus.amdahl.com:80/
2886: http_proxy=http://orpheus.amdahl.com:80/
2887: </pre>
2888: </div>
1.41 asau 2889: <div class="sect1">
1.1 dsieger 2890: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2891: <a name="fetch-https"></a>10.7. How to fetch files from HTTPS sites</h2></div></div></div>
1.65 wiz 2892: <p>Some fetch tools are not prepared to support HTTPS by default
2893: (for example, the one in NetBSD 6.0), or the one installed by the
2894: pkgsrc bootstrap (to avoid an openssl dependency that low in the
2895: dependency graph).</p>
2896: <p>Usually you won't notice, because distribution files are
2897: mirrored weekly to <span class="quote">“<span class="quote">ftp.NetBSD.org</span>”</span>, but that might not
2898: be often enough if you are following pkgsrc-current. In that case, set
2899: <code class="varname">FETCH_USING</code> in your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file to
2900: <span class="quote">“<span class="quote">curl</span>”</span> or <span class="quote">“<span class="quote">wget</span>”</span>, which are both compiled
2901: with HTTPS support by default. Of course, these tools need to be
2902: installed before you can use them this way.</p>
2903: </div>
2904: <div class="sect1">
2905: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2906: <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 2907: <p>This depends on which utility is used to retrieve distfiles. From
2908: <code class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned
2909: the first available command from the following list:</p>
1.41 asau 2910: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2911: <li class="listitem"><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li>
2912: <li class="listitem"><p><code class="filename">/usr/bin/ftp</code></p></li>
1.1 dsieger 2913: </ul></div>
2914: <p>On a default NetBSD installation, this will be
2915: <code class="filename">/usr/bin/ftp</code>, which automatically tries passive
2916: connections first, and falls back to active connections if the server
2917: refuses to do passive. For the other tools, add the following to your
1.10 hubertf 2918: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:
1.1 dsieger 2919: <code class="varname">PASSIVE_FETCH=1</code>.</p>
2920: <p>Having that option present will prevent
2921: <code class="filename">/usr/bin/ftp</code> from falling back to active
2922: transfers.</p>
2923: </div>
1.41 asau 2924: <div class="sect1">
1.1 dsieger 2925: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2926: <a name="fetching-all-distfiles"></a>10.9. How to fetch all distfiles at once</h2></div></div></div>
1.1 dsieger 2927: <p>You would like to download all the distfiles in a single batch
1.10 hubertf 2928: from work or university, where you can't run a <span class="command"><strong>make
1.25 spz 2929: 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 2930: but downloading the entire directory may not be appropriate.</p>
1.10 hubertf 2931: <p>The answer here is to do a <span class="command"><strong>make fetch-list</strong></span> in
1.1 dsieger 2932: <code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the
2933: resulting list to your machine at work/school and use it there. If you
1.207 leot 2934: don't have a NetBSD-compatible <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ftp.1"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
1.1 dsieger 2935: forget to set <code class="varname">FETCH_CMD</code> to something that fetches a
2936: URL:</p>
2937: <p>At home:</p>
2938: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
2939: <code class="prompt">%</code> <strong class="userinput"><code>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</code></strong>
2940: <code class="prompt">%</code> <strong class="userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong></pre>
2941: <p>At work:</p>
2942: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>sh /tmp/fetch.sh</code></strong></pre>
2943: <p>then tar up <code class="filename">/tmp/distfiles</code> and take it
2944: home.</p>
2945: <p>If you have a machine running NetBSD, and you want to get
2946: <span class="emphasis"><em>all</em></span> distfiles (even ones that aren't for your
2947: machine architecture), you can do so by using the above-mentioned
1.10 hubertf 2948: <span class="command"><strong>make fetch-list</strong></span> approach, or fetch the distfiles
1.1 dsieger 2949: directly by running:</p>
2950: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make mirror-distfiles</code></strong></pre>
2951: <p>If you even decide to ignore
2952: <code class="varname">NO_{SRC,BIN}_ON_{FTP,CDROM}</code>, then you can get everything
2953: by running:</p>
2954: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch NO_SKIP=yes</code></strong></pre>
2955: </div>
1.41 asau 2956: <div class="sect1">
1.1 dsieger 2957: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2958: <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 2959: /usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div>
1.207 leot 2960: <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 2961: package, you get the error from make that it doesn't know how to make
2962: <code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that
1.23 wiz 2963: you don't have installed the <span class="quote">“<span class="quote">text</span>”</span> set (nroff, ...) from
1.1 dsieger 2964: the NetBSD base distribution on your machine. It is recommended to do
2965: that to format man pages.</p>
1.207 leot 2966: <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 2967: can get away with setting <code class="varname">NOMAN=YES</code> either in the
1.10 hubertf 2968: environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 2969: </div>
1.41 asau 2970: <div class="sect1">
1.1 dsieger 2971: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 2972: <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 2973: <p>You didn't install the compiler set, <code class="filename">comp.tgz</code>,
2974: when you installed your NetBSD machine. Please get and install it, by
2975: extracting it in <code class="filename">/</code>:</p>
2976: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong>
2977: <code class="prompt">#</code> <strong class="userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong></pre>
2978: <p><code class="filename">comp.tgz</code> is part of every NetBSD release. Get
1.10 hubertf 2979: the one that corresponds to your release (determine via <span class="command"><strong>uname
1.1 dsieger 2980: -r</strong></span>).</p>
2981: </div>
1.41 asau 2982: <div class="sect1">
1.1 dsieger 2983: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.221 nia 2984: <a name="using-sudo-with-pkgsrc"></a>10.12. Using 'sudo' or `priv` with pkgsrc</h2></div></div></div>
1.1 dsieger 2985: <p>When installing packages as non-root user and using the just-in-time
1.207 leot 2986: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/su.1"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a> feature of pkgsrc, it can become annoying to type in the root
1.1 dsieger 2987: password for each required package installed. To avoid this, the sudo
2988: package can be used, which does password caching over a limited time. To
1.221 nia 2989: use it, install <span class="command"><strong>sudo</strong></span> or
2990: <span class="command"><strong>priv</strong></span> (either as binary package, from
2991: <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 2992: <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 2993: following into your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, somewhere
1.1 dsieger 2994: <span class="emphasis"><em>after</em></span> the definition of the
2995: <code class="varname">LOCALBASE</code> variable:</p>
2996: <pre class="programlisting">
2997: .if exists(${LOCALBASE}/bin/sudo)
2998: SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
2999: .endif
3000: </pre>
3001: </div>
1.41 asau 3002: <div class="sect1">
1.1 dsieger 3003: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3004: <a name="faq.conf"></a>10.13. How do I change the location of configuration files?</h2></div></div></div>
1.1 dsieger 3005: <p>As the system administrator, you can choose where configuration files
3006: are installed. The default settings make all these files go into
3007: <code class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may
3008: be suboptimal depending on your expectations (e.g., a read-only,
3009: NFS-exported <code class="varname">PREFIX</code> with a need of per-machine
3010: configuration of the provided packages).</p>
3011: <p>In order to change the defaults, you can modify the
3012: <code class="varname">PKG_SYSCONFBASE</code> variable (in
1.10 hubertf 3013: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>) to point to your preferred configuration
1.1 dsieger 3014: directory; some common examples include <code class="filename">/etc</code> or
3015: <code class="filename">/etc/pkg</code>.</p>
3016: <p>Furthermore, you can change this value on a per-package basis by
3017: setting the <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> variable.
3018: <code class="varname">PKG_SYSCONFVAR</code>'s value usually matches the name of the
3019: package you would like to modify, that is, the contents of
3020: <code class="varname">PKGBASE</code>.</p>
3021: <p>Note that after changing these settings, you must rebuild and
3022: reinstall any affected packages.</p>
3023: </div>
1.41 asau 3024: <div class="sect1">
1.1 dsieger 3025: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3026: <a name="audit-packages"></a>10.14. Automated security checks</h2></div></div></div>
1.1 dsieger 3027: <p>Please be aware that there can often be bugs in third-party software,
3028: and some of these bugs can leave a machine vulnerable to exploitation by
3029: attackers. In an effort to lessen the exposure, the NetBSD packages team
3030: maintains a database of known-exploits to packages which have at one time
3031: been included in pkgsrc. The database can be downloaded automatically, and
3032: a security audit of all packages installed on a system can take place. To
1.14 jmcneill 3033: do this, refer to the following two tools (installed as part of the
1.207 leot 3034: <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 3035: <div class="orderedlist"><ol class="orderedlist" type="1">
3036: <li class="listitem">
1.20 snj 3037: <p><span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>, an easy way to
1.1 dsieger 3038: download a list of the security vulnerabilities information. This list
1.25 spz 3039: is kept up to date by the pkgsrc security team, and is distributed
3040: from the NetBSD ftp server:</p>
1.177 leot 3041: <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 3042: </li>
1.23 wiz 3043: <li class="listitem"><p><span class="command"><strong>pkg_admin audit</strong></span>, an easy way to audit the
3044: current machine, checking each known vulnerability. If a
1.1 dsieger 3045: vulnerable package is installed, it will be shown by output to stdout,
3046: including a description of the type of vulnerability, and a URL
3047: containing more information.</p></li>
3048: </ol></div>
1.121 sevan 3049: <p>Use of these tools is strongly recommended!
1.202 nia 3050: 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 3051: reporting.</p>
3052: <p>If this database is installed, pkgsrc builds will use it to
3053: perform a security check before building any package.</p>
1.1 dsieger 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.154 rillig 3057: <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 3058: <p>When you add your own preferences to the
3059: <code class="varname">CFLAGS</code> variable in your
1.10 hubertf 3060: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, these flags are passed in
1.1 dsieger 3061: environment variables to the <code class="filename">./configure</code>
1.207 leot 3062: scripts and to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>. Some package authors ignore the
1.1 dsieger 3063: <code class="varname">CFLAGS</code> from the environment variable by
3064: overriding them in the <code class="filename">Makefile</code>s of their
3065: package.</p>
3066: <p>Currently there is no solution to this problem. If you
3067: really need the package to use your <code class="varname">CFLAGS</code>
1.10 hubertf 3068: you should run <span class="command"><strong>make patch</strong></span> in the package
1.1 dsieger 3069: directory and then inspect any <code class="filename">Makefile</code> and
3070: <code class="filename">Makefile.in</code> for whether they define
3071: <code class="varname">CFLAGS</code> explicitly. Usually you can remove
1.23 wiz 3072: these lines. But be aware that some <span class="quote">“<span class="quote">smart</span>”</span>
1.1 dsieger 3073: programmers write so bad code that it only works for the
3074: specific combination of <code class="varname">CFLAGS</code> they have
3075: chosen.</p>
1.172 rillig 3076: <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>
3077: <pre class="programlisting">
3078: CPPFLAGS+= -Dpkgsrc___CPPFLAGS
3079: CFLAGS+= -Dpkgsrc___CFLAGS
3080: CXXFLAGS+= -Dpkgsrc___CXXFLAGS
3081: </pre>
3082: <p>Then run <span class="command"><strong>bmake show-all-configure show-all-build</strong></span>
3083: to see whether the above flags are passed to the actual build
3084: commands in general.</p>
3085: <p>To find out whether the flags are passed to individual compiler
3086: commands, have a look at the file <code class="filename">work/.work.log</code>. In
3087: most cases, the flags from the original command lines (the lines starting
3088: with <code class="literal">[*]</code>) are passed unmodified to the actual compiler
3089: (the lines starting with <code class="literal"><.></code>). If the flag is
3090: missing from the actual compiler command, it must have been removed by
1.184 rillig 3091: the <a class="link" href="#build.wrapper" title="13.10. The wrapper phase">pkgsrc compiler wrappers</a>.</p>
1.1 dsieger 3092: </div>
1.41 asau 3093: <div class="sect1">
1.1 dsieger 3094: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3095: <a name="ufaq-fail"></a>10.16. A package does not build. What shall I do?</h2></div></div></div>
1.23 wiz 3096: <div class="procedure"><ol class="procedure" type="1">
1.41 asau 3097: <li class="step"><p>Make sure that your copy of pkgsrc is consistent. A
1.1 dsieger 3098: case that occurs often is that people only update pkgsrc in
3099: parts, because of performance reasons. Since pkgsrc is one large
3100: system, not a collection of many small systems, there are
3101: sometimes changes that only work when the whole pkgsrc tree is
3102: updated.</p></li>
1.41 asau 3103: <li class="step"><p>Make sure that you don't have any CVS conflicts.
1.23 wiz 3104: Search for <span class="quote">“<span class="quote"><<<<<<</span>”</span> or
3105: <span class="quote">“<span class="quote">>>>>>></span>”</span> in all your pkgsrc
1.1 dsieger 3106: files.</p></li>
1.41 asau 3107: <li class="step"><p>Make sure that you don't have old copies of the packages
1.10 hubertf 3108: extracted. Run <span class="command"><strong>make clean clean-depends</strong></span> to
1.1 dsieger 3109: verify this.</p></li>
1.108 rillig 3110: <li class="step"><p>If you are a package developer who wants to invest
1.154 rillig 3111: 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 3112: <li class="step"><p>If the problem still exists, write a mail to the
1.1 dsieger 3113: <code class="literal">pkgsrc-users</code> mailing list.</p></li>
3114: </ol></div>
3115: </div>
1.41 asau 3116: <div class="sect1">
1.1 dsieger 3117: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 3118: <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 3119: <p>You have modified a file from pkgsrc, and someone else has
3120: modified that same file afterwards in the CVS repository. Both changes
3121: are in the same region of the file, so when you updated pkgsrc, the
3122: <code class="literal">cvs</code> command marked the conflicting changes in the
3123: file. Because of these markers, the file is no longer a valid
3124: <code class="filename">Makefile</code>.</p>
3125: <p>Have a look at that file, and if you don't need your local changes
1.10 hubertf 3126: anymore, you can remove that file and run <span class="command"><strong>cvs -q update
1.1 dsieger 3127: -dP</strong></span> in that directory to download the current version.</p>
3128: </div>
3129: </div>
3130: </div>
1.41 asau 3131: <div class="part">
1.1 dsieger 3132: <div class="titlepage"><div><div><h1 class="title">
3133: <a name="developers-guide"></a>Part II. The pkgsrc developer's guide</h1></div></div></div>
1.41 asau 3134: <div class="partintro">
1.1 dsieger 3135: <div></div>
3136: <p>This part of the book deals with creating and
1.23 wiz 3137: modifying packages. It starts with a <span class="quote">“<span class="quote">HOWTO</span>”</span>-like
1.1 dsieger 3138: guide on creating a new package. The remaining chapters are more
3139: like a reference manual for pkgsrc.</p>
3140: <div class="toc">
3141: <p><b>Table of Contents</b></p>
1.100 leot 3142: <dl class="toc">
1.154 rillig 3143: <dt><span class="chapter"><a href="#help-devel">11. Getting help</a></span></dt>
1.184 rillig 3144: <dt><span class="chapter"><a href="#components">12. Package components - files, directories and contents</a></span></dt>
1.1 dsieger 3145: <dd><dl>
1.184 rillig 3146: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3147: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3148: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
1.1 dsieger 3149: <dd><dl>
1.184 rillig 3150: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3151: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3152: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3153: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3154: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
1.1 dsieger 3155: </dl></dd>
1.184 rillig 3156: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3157: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3158: <dd><dl>
3159: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3160: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3161: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
3162: </dl></dd>
3163: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3164: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 3165: </dl></dd>
1.184 rillig 3166: <dt><span class="chapter"><a href="#build">13. The build process</a></span></dt>
1.6 rillig 3167: <dd><dl>
1.184 rillig 3168: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
3169: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
3170: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
3171: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
3172: <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 3173: <dd><dl>
1.184 rillig 3174: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
3175: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
1.6 rillig 3176: </dl></dd>
1.184 rillig 3177: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
3178: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
3179: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
3180: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
3181: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
3182: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3183: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3184: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
3185: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3186: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
3187: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
3188: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
3189: </dl></dd>
3190: <dt><span class="chapter"><a href="#creating">14. Creating a new pkgsrc package from scratch</a></span></dt>
3191: <dd><dl>
3192: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
1.6 rillig 3193: <dd><dl>
1.219 nia 3194: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
3195: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
3196: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.6 rillig 3197: </dl></dd>
1.184 rillig 3198: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
3199: <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 3200: </dl></dd>
1.184 rillig 3201: <dt><span class="chapter"><a href="#makefile">15. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 3202: <dd><dl>
1.184 rillig 3203: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
3204: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
3205: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
3206: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
1.6 rillig 3207: <dd><dl>
1.184 rillig 3208: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
3209: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
3210: <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>
3211: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 3212: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.6 rillig 3213: </dl></dd>
3214: </dl></dd>
1.184 rillig 3215: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
1.6 rillig 3216: <dd><dl>
1.184 rillig 3217: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
3218: <dt><span class="sect1"><a href="#converting-to-options">16.2. Converting packages to use <code class="filename">bsd.options.mk</code></a></span></dt>
3219: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
3220: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 3221: </dl></dd>
1.184 rillig 3222: <dt><span class="chapter"><a href="#tools">17. Tools needed for building or running</a></span></dt>
1.6 rillig 3223: <dd><dl>
1.184 rillig 3224: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
3225: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
3226: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
3227: </dl></dd>
3228: <dt><span class="chapter"><a href="#buildlink">18. Buildlink methodology</a></span></dt>
3229: <dd><dl>
3230: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
3231: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3232: <dd><dl>
1.184 rillig 3233: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
3234: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
1.26 wiz 3235: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3236: and
3237: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3238: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3239: </dl></dd>
1.184 rillig 3240: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
3241: <dd><dl>
3242: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
3243: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
3244: </dl></dd>
3245: </dl></dd>
3246: <dt><span class="chapter"><a href="#plist">19. PLIST issues</a></span></dt>
1.6 rillig 3247: <dd><dl>
1.184 rillig 3248: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
3249: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
3250: <dt><span class="sect1"><a href="#print-PLIST">19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
3251: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
3252: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
3253: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
3254: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
3255: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
3256: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.6 rillig 3257: </dl></dd>
1.184 rillig 3258: <dt><span class="chapter"><a href="#pkginstall">20. The pkginstall framework</a></span></dt>
3259: <dd><dl>
3260: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
3261: <dd><dl>
3262: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
3263: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
1.6 rillig 3264: </dl></dd>
1.184 rillig 3265: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
1.6 rillig 3266: <dd><dl>
1.184 rillig 3267: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
3268: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
3269: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
3270: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
3271: </dl></dd>
3272: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
3273: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">20.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
3274: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
3275: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
3276: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
3277: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
3278: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">20.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
1.154 rillig 3279: </dl></dd>
3280: <dt><span class="chapter"><a href="#fixes">21. Making your package work</a></span></dt>
3281: <dd><dl>
3282: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
3283: <dd><dl>
3284: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">21.1.1. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
3285: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
3286: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
3287: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
3288: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
3289: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
3290: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
3291: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
3292: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
3293: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
3294: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
3295: </dl></dd>
3296: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
3297: <dd><dl>
3298: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
3299: <dt><span class="sect2"><a href="#modified-distfiles-same-name">21.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
3300: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
3301: </dl></dd>
3302: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3303: <dd><dl>
3304: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
3305: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
3306: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.223 nia 3307: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 rillig 3308: </dl></dd>
3309: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
3310: <dd><dl>
3311: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
3312: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.205 wiz 3313: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 nia 3314: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
3315: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
3316: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
3317: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.154 rillig 3318: </dl></dd>
3319: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3320: <dd><dl>
3321: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
3322: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.172 rillig 3323: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
3324: <dt><span class="sect2"><a href="#undefined-reference">21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
3325: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.154 rillig 3326: </dl></dd>
3327: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3328: <dd><dl>
3329: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
3330: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
3331: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
3332: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
3333: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.203 nia 3334: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 rillig 3335: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
3336: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.203 nia 3337: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
3338: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
3339: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
3340: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
3341: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
3342: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
3343: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.1 dsieger 3344: emulation</a></span></dt>
1.203 nia 3345: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
3346: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.1 dsieger 3347: </dl></dd>
1.154 rillig 3348: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 3349: </dl></dd>
1.184 rillig 3350: <dt><span class="chapter"><a href="#gnome">22. GNOME packaging and porting</a></span></dt>
3351: <dd><dl>
3352: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
3353: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
3354: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
3355: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
3356: </dl></dd>
1.154 rillig 3357: <dt><span class="chapter"><a href="#submit">23. Submitting and Committing</a></span></dt>
1.1 dsieger 3358: <dd><dl>
1.154 rillig 3359: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
3360: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
3361: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
3362: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
3363: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
3364: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
3365: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
3366: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
3367: </dl></dd>
3368: <dt><span class="chapter"><a href="#devfaq">24. Frequently Asked Questions</a></span></dt>
1.1 dsieger 3369: </dl>
3370: </div>
3371: </div>
1.41 asau 3372: <div class="chapter">
1.1 dsieger 3373: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 3374: <a name="help-devel"></a>Chapter 11. Getting help</h2></div></div></div>
3375: <p>
3376: To get help when developing pkgsrc, the definitive source is this
3377: document, the pkgsrc guide. If you don't find anything here,
3378: there are alternatives:
3379: </p>
3380: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3381: <li class="listitem">
3382: <p>
3383: The built-in pkgsrc help, which is available after bootstrapping
3384: pkgsrc. Run <span class="command"><strong>bmake help topic=…</strong></span> to get
3385: help for any topic, such as a variable name like
3386: <code class="varname">BUILD_DEFS</code>, a make target like
3387: <span class="command"><strong>do-build</strong></span>, a missing C or C++ function like
3388: <span class="command"><strong>strcasecmp</strong></span> or any other topic.</p>
1.207 leot 3389: <p>The available help topics are listed in <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.154 rillig 3390: </li>
3391: <li class="listitem"><p>
1.163 rillig 3392: To see the value of a single variable, run <span class="command"><strong>bmake
3393: show-var VARNAME=<em class="replaceable"><code>X</code></em></strong></span>.
3394: </p></li>
3395: <li class="listitem"><p>
3396: To see the values of the most common variables, run
3397: <span class="command"><strong>bmake show-all</strong></span>. These variables are grouped by
3398: topic. To see the variables for a single topic, run
3399: <span class="command"><strong>bmake
3400: show-all-<em class="replaceable"><code>topic</code></em></strong></span>, for example
3401: <span class="command"><strong>bmake show-all-fetch</strong></span>.
3402: </p></li>
3403: <li class="listitem"><p>
1.154 rillig 3404: The tech-pkg mailing list, to which
3405: <a class="ulink" href="https://www.NetBSD.org/mailinglists/#tech-pkg" target="_top">you
3406: can subscribe</a> and then <a class="ulink" href="mailto:tech-pkg@NetBSD.org" target="_top">ask your
3407: questions</a>.</p></li>
3408: <li class="listitem"><p>The #pkgsrc IRC channel, which is accessible
3409: <a class="ulink" href="https://webchat.freenode.net/" target="_top">via a web browser</a>
3410: or by using a specialized chat program such as
3411: <a class="ulink" href="http://xchat.org/" target="_top">XChat</a>.
3412: Pick any user name and join the channel #pkgsrc.</p></li>
3413: </ul></div>
3414: </div>
3415: <div class="chapter">
3416: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 3417: <a name="components"></a>Chapter 12. Package components - files, directories and contents</h2></div></div></div>
1.1 dsieger 3418: <div class="toc">
3419: <p><b>Table of Contents</b></p>
1.100 leot 3420: <dl class="toc">
1.184 rillig 3421: <dt><span class="sect1"><a href="#components.Makefile">12.1. <code class="filename">Makefile</code></a></span></dt>
3422: <dt><span class="sect1"><a href="#components.distinfo">12.2. <code class="filename">distinfo</code></a></span></dt>
3423: <dt><span class="sect1"><a href="#components.patches">12.3. <code class="filename">patches/*</code></a></span></dt>
3424: <dd><dl>
3425: <dt><span class="sect2"><a href="#components.patch.structure">12.3.1. Structure of a single patch file</a></span></dt>
3426: <dt><span class="sect2"><a href="#components.patches.caveats">12.3.2. Creating patch files</a></span></dt>
3427: <dt><span class="sect2"><a href="#components.patches.sources">12.3.3. Sources where the patch files come from</a></span></dt>
3428: <dt><span class="sect2"><a href="#components.patches.guidelines">12.3.4. Patching guidelines</a></span></dt>
3429: <dt><span class="sect2"><a href="#components.patches.feedback">12.3.5. Feedback to the author</a></span></dt>
3430: </dl></dd>
3431: <dt><span class="sect1"><a href="#other-mandatory-files">12.4. Other mandatory files</a></span></dt>
3432: <dt><span class="sect1"><a href="#components.optional">12.5. Optional files</a></span></dt>
3433: <dd><dl>
3434: <dt><span class="sect2"><a href="#components.optional.bin">12.5.1. Files affecting the binary package</a></span></dt>
3435: <dt><span class="sect2"><a href="#components.optional.build">12.5.2. Files affecting the build process</a></span></dt>
3436: <dt><span class="sect2"><a href="#components.optional.none">12.5.3. Files affecting nothing at all</a></span></dt>
1.1 dsieger 3437: </dl></dd>
1.184 rillig 3438: <dt><span class="sect1"><a href="#work-dir">12.6. <code class="filename">work*</code></a></span></dt>
3439: <dt><span class="sect1"><a href="#files-dir">12.7. <code class="filename">files/*</code></a></span></dt>
1.1 dsieger 3440: </dl>
3441: </div>
1.184 rillig 3442: <p>Whenever you're preparing a package, there are a number of
3443: files involved which are described in the following
3444: sections.</p>
3445: <div class="sect1">
3446: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3447: <a name="components.Makefile"></a>12.1. <code class="filename">Makefile</code>
3448: </h2></div></div></div>
3449: <p>Building, installation and creation of a binary package are all
3450: controlled by the package's <code class="filename">Makefile</code>.
3451: The <code class="filename">Makefile</code> describes various things about
3452: a package, for example from where to get it, how to configure,
3453: build, and install it.</p>
3454: <p>A package <code class="filename">Makefile</code> contains several
3455: sections that describe the package.</p>
3456: <p>In the first section there are the following variables, which
3457: should appear exactly in the order given here. The order and
3458: grouping of the variables is mostly historical and has no further
3459: meaning.</p>
3460: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3461: <li class="listitem"><p><code class="varname">DISTNAME</code> is the basename of the
3462: distribution file to be downloaded from the package's
3463: website.</p></li>
3464: <li class="listitem"><p><code class="varname">PKGNAME</code> is the name of the
3465: package, as used by pkgsrc. You need to provide it if
3466: <code class="varname">DISTNAME</code> (which is the default) is not a good
3467: name for the package in pkgsrc or <code class="varname">DISTNAME</code> is not
3468: provided (no distribution file is required). Usually it is the pkgsrc
3469: directory name together with the version number. It must match the
3470: regular expression
3471: <code class="varname">^[A-Za-z0-9][A-Za-z0-9-_.+]*$</code>, that is, it
3472: starts with a letter or digit, and contains only letters, digits,
1.204 nia 3473: dashes, underscores, dots and plus signs.
3474: New packages should have entirely lower-case names, with the exception
3475: of some that must follow pre-existing conventions
3476: (e.g. R packages begin with <code class="varname">R-</code>).
3477: You can use the <code class="code">:tl</code> variable modifier to lower-case
3478: the package name.</p></li>
1.184 rillig 3479: <li class="listitem">
3480: <p><code class="varname">CATEGORIES</code> is a list of categories
3481: which the package fits in. You can choose any of the top-level
3482: directories of pkgsrc for it.</p>
3483: <p>Currently the following values are available for
3484: <code class="varname">CATEGORIES</code>. If more than
3485: one is used, they need to be separated by spaces:</p>
1.1 dsieger 3486: <pre class="programlisting">
1.184 rillig 3487: archivers cross geography meta-pkgs security
3488: audio databases graphics misc shells
3489: benchmarks devel ham multimedia sysutils
3490: biology editors inputmethod net textproc
3491: cad emulators lang news time
3492: chat finance mail parallel wm
3493: comms fonts math pkgtools www
3494: converters games mbone print x11
1.1 dsieger 3495: </pre>
3496: </li>
1.184 rillig 3497: <li class="listitem"><p><code class="varname">MASTER_SITES</code>,
3498: <code class="varname">DYNAMIC_MASTER_SITES</code>,
3499: <code class="varname">DIST_SUBDIR</code>, <code class="varname">EXTRACT_SUFX</code>
3500: and <code class="varname">DISTFILES</code> are discussed in detail in
3501: <a class="xref" href="#build.fetch" title="13.5. The fetch phase">Section 13.5, “The <span class="emphasis"><em>fetch</em></span> phase”</a>.</p></li>
3502: </ul></div>
3503: <p>The second section contains information about separately
3504: downloaded patches, if any.
3505: </p>
3506: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3507: <li class="listitem"><p><code class="varname">PATCHFILES</code>:
3508: Name(s) of additional files that contain distribution patches.
3509: There is no default. pkgsrc will look for them at
3510: <code class="varname">PATCH_SITES</code>.
3511: They will automatically be uncompressed before patching if
3512: the names end with <code class="filename">.gz</code> or
3513: <code class="filename">.Z</code>.</p></li>
3514: <li class="listitem"><p><code class="varname">PATCH_SITES</code>:
3515: Primary location(s) for distribution patch files (see
3516: <code class="varname">PATCHFILES</code> above) if not found locally.</p></li>
3517: <li class="listitem"><p><code class="varname">PATCH_DIST_STRIP</code>:
1.207 leot 3518: an argument to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> that sets the pathname strip count to
1.184 rillig 3519: help find the correct files to patch. It defaults to
3520: <span class="command"><strong>-p0</strong></span>.</p></li>
3521: </ul></div>
3522: <p>The third section contains the following variables.
3523: </p>
3524: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3525: <li class="listitem"><p><code class="varname">MAINTAINER</code> is the email
3526: address of the person who feels responsible for this package,
3527: and who is most likely to look at problems or questions regarding
1.207 leot 3528: this package which have been reported with <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a>.
1.184 rillig 3529: Other developers may contact the <code class="varname">MAINTAINER</code>
3530: before making changes to the package, but are not required to
3531: do so. When packaging a new program, set <code class="varname">MAINTAINER</code>
3532: to yourself. If you really can't maintain the package for future
3533: updates, set it to
3534: <code class="email"><<a class="email" href="mailto:pkgsrc-users@NetBSD.org">pkgsrc-users@NetBSD.org</a>></code>.</p></li>
3535: <li class="listitem"><p><code class="varname">OWNER</code> should be used instead
3536: of <code class="varname">MAINTAINER</code> when you do not want other
3537: developers to update or change the package without contacting
3538: you first. A package Makefile should contain one of
3539: <code class="varname">MAINTAINER</code> or <code class="varname">OWNER</code>, but
3540: not both. </p></li>
3541: <li class="listitem"><p><code class="varname">HOMEPAGE</code> is a URL where users can
3542: find more information about the package.</p></li>
3543: <li class="listitem"><p><code class="varname">COMMENT</code> is a one-line
3544: description of the package (should not include the package
3545: name).</p></li>
3546: <li class="listitem"><p><code class="varname">LICENSE</code> indicates the license(s)
3547: applicable for the package. See <a class="xref" href="#handling-licenses" title="21.1.3. Handling licenses">Section 21.1.3, “Handling licenses”</a> for further details.</p></li>
3548: </ul></div>
3549: <p>Other variables that affect the build:
3550: </p>
3551: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3552: <p><code class="varname">WRKSRC</code>: The directory where the
3553: interesting distribution files of the package are found. The
3554: default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which
3555: works for most packages.</p>
3556: <p>If a package doesn't create a subdirectory for itself
3557: (most GNU software does, for instance), but extracts itself in
3558: the current directory, you should set
3559: <code class="varname">WRKSRC=${WRKDIR}</code>.</p>
3560: <p>If a package doesn't create a subdirectory with the
3561: name of <code class="varname">DISTNAME</code> but some different name,
3562: set <code class="varname">WRKSRC</code> to point to the proper name in
3563: <code class="filename">${WRKDIR}</code>, for example
3564: <code class="varname">WRKSRC=${WRKDIR}/${DISTNAME}/unix</code>. See
1.207 leot 3565: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/tcl/index.html" target="_top"><code class="filename">lang/tcl</code></a> and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/tk/index.html" target="_top"><code class="filename">x11/tk</code></a> for other examples.</p>
1.184 rillig 3566: <p>The name of the working directory created by pkgsrc is
3567: taken from the <code class="varname">WRKDIR_BASENAME</code>
3568: variable. By default, its value is
3569: <code class="filename">work</code>. If you want to use the same
3570: pkgsrc tree for building different kinds of binary packages,
3571: you can change the variable according to your needs. Two
3572: other variables handle common cases of setting
3573: <code class="varname">WRKDIR_BASENAME</code> individually. If
3574: <code class="varname">OBJHOSTNAME</code> is defined in
3575: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the first component of
3576: the host's name is attached to the directory name. If
3577: <code class="varname">OBJMACHINE</code> is defined, the platform name
3578: is attached, which might look like
3579: <code class="filename">work.i386</code> or
3580: <code class="filename">work.sparc</code>.</p>
3581: </li></ul></div>
3582: <p>Please pay attention to the following gotchas:</p>
3583: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3584: <li class="listitem"><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are
3585: installed in compressed form by the package. For packages using
3586: BSD-style makefiles which honor MANZ, there is
3587: <code class="varname">MANCOMPRESSED_IF_MANZ</code>.</p></li>
3588: <li class="listitem"><p>Replace <code class="filename">/usr/local</code> with
3589: <span class="quote">“<span class="quote">${PREFIX}</span>”</span> in all files (see patches,
3590: below).</p></li>
3591: <li class="listitem"><p>If the package installs any info files, see <a class="xref" href="#faq.info-files" title="21.6.7. Packages installing info files">Section 21.6.7, “Packages installing info files”</a>.</p></li>
3592: </ul></div>
3593: </div>
1.41 asau 3594: <div class="sect1">
1.1 dsieger 3595: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 3596: <a name="components.distinfo"></a>12.2. <code class="filename">distinfo</code>
3597: </h2></div></div></div>
3598: <p>The <code class="filename">distinfo</code> file contains the message
3599: digest, or checksum, of each distfile needed for the package. This
3600: ensures that the distfiles retrieved from the Internet have not been
3601: corrupted during transfer or altered by a malign force to introduce
3602: a security hole. To provide maximum security, all distfiles are
3603: protected using three different message digest algorithms (SHA1,
3604: RMD160, SHA512), as well as the file size.</p>
3605: <p>The <code class="filename">distinfo</code> file also contains the
3606: checksums for all the patches found in the
3607: <code class="filename">patches</code> directory (see <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a>). These checksums ensure that patches
3608: are only applied intentionally and that they don't accidentally change,
3609: e.g. when merging different changes together. They also make sure that
3610: new patches are actually added to CVS and old ones are removed.
3611: Too see whether the patches and the <code class="filename">distinfo</code> file
3612: match, run <span class="command"><strong>pkglint</strong></span> after changing the patches.</p>
3613: <p>To regenerate the <code class="filename">distinfo</code> file, use the
3614: <span class="command"><strong>make distinfo</strong></span> command.</p>
3615: <p>Some packages have different sets of distfiles depending on
1.207 leot 3616: the platform, for example <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/openjdk8/index.html" target="_top"><code class="filename">lang/openjdk8</code></a>. These are kept in the same
1.184 rillig 3617: <code class="filename">distinfo</code> file and care should be taken when
3618: upgrading such a package to ensure distfile information is not
3619: lost.</p>
3620: </div>
3621: <div class="sect1">
3622: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3623: <a name="components.patches"></a>12.3. <code class="filename">patches/*</code>
3624: </h2></div></div></div>
3625: <p>Some packages don't work out-of-the box on the various
3626: platforms that are supported by pkgsrc. These packages need
3627: to be patched to make them work. The patch files can be
3628: found in the <code class="filename">patches/</code> directory.</p>
3629: <p>In the <span class="emphasis"><em>patch</em></span> phase, these patches are
3630: applied to the files in <code class="varname">WRKSRC</code> directory after
3631: extracting them, in alphabetic order.</p>
1.41 asau 3632: <div class="sect2">
1.1 dsieger 3633: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3634: <a name="components.patch.structure"></a>12.3.1. Structure of a single patch file</h3></div></div></div>
3635: <p>The <code class="filename">patch-*</code> files should be in
3636: <span class="command"><strong>diff -bu</strong></span> format, and apply without a fuzz to avoid
3637: problems. (To force patches to apply with fuzz you can set
3638: <code class="varname">PATCH_FUZZ_FACTOR=-F2</code>). Furthermore, each patch
3639: should contain only changes for a single file, and no file should be
3640: patched by more than one patch file. This helps to keep future
3641: modifications simple.</p>
3642: <p>Each patch file is structured as follows: In the first line,
3643: there is the RCS Id of the patch itself. The second line should be
3644: empty for aesthetic reasons. After that, there should be a comment for
3645: each change that the patch does. There are a number of standard
3646: cases:</p>
3647: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3648: <li class="listitem"><p>Patches for commonly known vulnerabilities should
3649: mention the vulnerability ID (CAN, CVE).</p></li>
3650: <li class="listitem"><p>Patches that change source code should mention the
3651: platform and other environment (for example, the compiler) that the
3652: patch is needed for.</p></li>
3653: </ul></div>
3654: <p>The patch should be commented so that any
3655: developer who knows the code of the application can make some use of
3656: the patch. Special care should be taken for the upstream developers,
3657: since we generally want that they accept our patches, so we have less
3658: work in the future.</p>
1.1 dsieger 3659: </div>
1.41 asau 3660: <div class="sect2">
1.1 dsieger 3661: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3662: <a name="components.patches.caveats"></a>12.3.2. Creating patch files</h3></div></div></div>
3663: <p>One important thing to mention is to pay attention that no RCS
3664: IDs get stored in the patch files, as these will cause problems when
3665: later checked into the NetBSD CVS tree. Use the
1.207 leot 3666: <span class="command"><strong>pkgdiff</strong></span> command from the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package to avoid these
1.184 rillig 3667: problems.</p>
3668: <p>For even more automation, we recommend using
3669: <span class="command"><strong>mkpatches</strong></span> from the same package to make a
1.222 gutterid 3670: whole set of patches. You just have to back up files before you
3671: edit them to <code class="filename">filename.orig</code>, e.g., with
1.184 rillig 3672: <span class="command"><strong>cp -p filename filename.orig</strong></span> or, easier, by
3673: using <span class="command"><strong>pkgvi</strong></span> again from the same package. If
3674: you upgrade a package this way, you can easily compare the new
3675: set of patches with the previously existing one with
3676: <span class="command"><strong>patchdiff</strong></span>. The files in <code class="filename">patches</code>
3677: are replaced by new files, so carefully check if you want to take all
3678: the changes.</p>
3679: <p>When you have finished a package, remember to generate
3680: the checksums for the patch files by using the <span class="command"><strong>make
3681: makepatchsum</strong></span> command, see <a class="xref" href="#components.distinfo" title="12.2. distinfo">Section 12.2, “<code class="filename">distinfo</code>”</a>.</p>
3682: <p>When adding a patch that corrects a problem in the
3683: distfile (rather than e.g. enforcing pkgsrc's view of where
3684: man pages should go), send the patch as a bug report to the
3685: maintainer. This benefits non-pkgsrc users of the package,
3686: and usually makes it possible to remove the patch in future
3687: version.</p>
3688: <p>The file names of the patch files are usually of the form
3689: <code class="filename">patch-<em class="replaceable"><code>path_to_file__with__underscores.c</code></em></code>.
3690: Many packages still use the previous convention
3691: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>,
3692: but new patches should be of the form containing the filename.
1.207 leot 3693: <span class="command"><strong>mkpatches</strong></span> included in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> takes care of the name
1.184 rillig 3694: automatically.</p>
1.222 gutterid 3695: <p>When updating pre-existing patch files, if a file uses the old
3696: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>
3697: convention, it's best not to change it to the new form, as that will
3698: just cause churn that makes it harder to track changes to patching
3699: over time. Similarly, if a patch now applies at different line offsets,
3700: but still applies cleanly as-is, there's no need to update it, as that
3701: also unnecessarily complicates the patch history.</p>
1.17 imil 3702: </div>
1.160 brook 3703: <div class="sect2">
3704: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3705: <a name="components.patches.sources"></a>12.3.3. Sources where the patch files come from</h3></div></div></div>
3706: <p>If you want to share patches between multiple packages
3707: in pkgsrc, e.g. because they use the same distfiles, set
3708: <code class="varname">PATCHDIR</code> to the path where the patch files
3709: can be found, e.g.:</p>
3710: <pre class="programlisting">
3711: PATCHDIR= ../../editors/xemacs/patches
3712: </pre>
3713: <p>Patch files that are distributed by the author or other
3714: maintainers can be listed in
3715: <code class="varname">PATCHFILES</code>.</p>
3716: <p>If it is desired to store any patches that should not be
3717: committed into pkgsrc, they can be kept outside the pkgsrc
3718: tree in the <code class="filename">$LOCALPATCHES</code> directory. The
3719: directory tree there is expected to have the same
3720: <span class="quote">“<span class="quote">category/package</span>”</span> structure as pkgsrc, and
3721: patches are expected to be stored inside these dirs (also
3722: known as <code class="filename">$LOCALPATCHES/$PKGPATH</code>). For
3723: example, if you want to keep a private patch for
3724: <code class="filename">pkgsrc/graphics/png</code>, keep it in
3725: <code class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All
3726: files in the named directory are expected to be patch files,
3727: and <span class="emphasis"><em>they are applied after pkgsrc patches are
3728: applied</em></span>.</p>
1.160 brook 3729: </div>
3730: <div class="sect2">
3731: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 3732: <a name="components.patches.guidelines"></a>12.3.4. Patching guidelines</h3></div></div></div>
3733: <p>When fixing a portability issue in the code do not use
3734: preprocessor magic to check for the current operating system nor
3735: platform. Doing so hurts portability to other platforms because
3736: the OS-specific details are not abstracted appropriately.</p>
3737: <p>The general rule to follow is: instead of checking for the
3738: operating system the application is being built on, check for the
3739: specific <span class="emphasis"><em>features</em></span> you need. For example,
3740: instead of assuming that kqueue is available under NetBSD and
3741: using the <code class="varname">__NetBSD__</code> macro to conditionalize
3742: kqueue support, add a check that detects kqueue itself —
3743: yes, this generally involves patching the
3744: <span class="command"><strong>configure</strong></span> script. There is absolutely nothing
3745: that prevents some OSes from adopting interfaces from other OSes
3746: (e.g. Linux implementing kqueue), something that the above checks
3747: cannot take into account.</p>
3748: <p>Of course, checking for features generally involves more
3749: work on the developer's side, but the resulting changes are
3750: cleaner and there are chances they will work on many other
3751: platforms. Not to mention that there are higher chances of being
3752: later integrated into the mainstream sources. Remember:
3753: <span class="emphasis"><em>It doesn't work unless it is right!</em></span></p>
3754: <p>Some typical examples:</p>
3755: <div class="table">
3756: <a name="patch-examples"></a><p class="title"><b>Table 12.1. Patching examples</b></p>
3757: <div class="table-contents"><table class="table" summary="Patching examples" border="1">
3758: <colgroup>
3759: <col>
3760: <col>
3761: <col>
3762: </colgroup>
3763: <thead><tr>
3764: <th>Where</th>
3765: <th>Incorrect</th>
3766: <th>Correct</th>
3767: </tr></thead>
3768: <tbody>
3769: <tr>
3770: <td>configure script</td>
3771: <td>
1.160 brook 3772: <pre class="programlisting">
1.184 rillig 3773: case ${target_os} in
3774: netbsd*) have_kvm=yes ;;
3775: *) have_kvm=no ;;
3776: esac
1.160 brook 3777: </pre>
1.184 rillig 3778: </td>
3779: <td>
1.160 brook 3780: <pre class="programlisting">
1.184 rillig 3781: AC_CHECK_LIB(kvm, kvm_open, have_kvm=yes, have_kvm=no)
1.160 brook 3782: </pre>
1.184 rillig 3783: </td>
3784: </tr>
3785: <tr>
3786: <td>C source file</td>
3787: <td>
1.1 dsieger 3788: <pre class="programlisting">
1.184 rillig 3789: #if defined(__NetBSD__)
3790: # include <sys/event.h>
3791: #endif
1.1 dsieger 3792: </pre>
1.184 rillig 3793: </td>
3794: <td>
1.1 dsieger 3795: <pre class="programlisting">
1.184 rillig 3796: #if defined(HAVE_SYS_EVENT_H)
3797: # include <sys/event.h>
3798: #endif
1.1 dsieger 3799: </pre>
1.184 rillig 3800: </td>
3801: </tr>
3802: <tr>
3803: <td>C source file</td>
3804: <td>
1.1 dsieger 3805: <pre class="programlisting">
1.184 rillig 3806: int
3807: monitor_file(...)
3808: {
3809: #if defined(__NetBSD__)
3810: int fd = kqueue();
3811: ...
3812: #else
3813: ...
3814: #endif
3815: }
1.1 dsieger 3816: </pre>
1.184 rillig 3817: </td>
3818: <td>
1.1 dsieger 3819: <pre class="programlisting">
1.184 rillig 3820: int
3821: monitor_file(...)
3822: {
3823: #if defined(HAVE_KQUEUE)
3824: int fd = kqueue();
3825: ...
3826: #else
3827: ...
3828: #endif
3829: }
1.1 dsieger 3830: </pre>
1.184 rillig 3831: </td>
3832: </tr>
3833: </tbody>
3834: </table></div>
3835: </div>
3836: <br class="table-break">
3837: </div>
3838: <div class="sect2">
3839: <div class="titlepage"><div><div><h3 class="title">
3840: <a name="components.patches.feedback"></a>12.3.5. Feedback to the author</h3></div></div></div>
3841: <p>Always, always, <span class="strong"><strong>always</strong></span>
3842: feed back any <span class="emphasis"><em>portability fixes</em></span> or
3843: improvements you do to a package to the mainstream developers.
3844: This is the only way to get their attention on portability issues
3845: and to ensure that future versions can be built out-of-the box on
3846: NetBSD. Furthermore, any user that gets newer distfiles will get
3847: the fixes straight from the packaged code.</p>
3848: <p>This generally involves cleaning up the patches
3849: (because sometimes the patches that are
3850: added to pkgsrc are quick hacks), filing bug reports in the
3851: appropriate trackers for the projects and working with the
3852: mainstream authors to accept your changes. It is
3853: <span class="emphasis"><em>extremely important</em></span> that you do it so that
3854: the packages in pkgsrc are kept simple and thus further changes
3855: can be done without much hassle.</p>
3856: <p>When you have done this, please add a URL to the upstream
3857: bug report to the patch comment.</p>
3858: <p>Support the idea of free software!</p>
3859: </div>
1.1 dsieger 3860: </div>
1.184 rillig 3861: <div class="sect1">
3862: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3863: <a name="other-mandatory-files"></a>12.4. Other mandatory files</h2></div></div></div>
3864: <div class="variablelist"><dl class="variablelist">
3865: <dt><span class="term"><code class="filename">DESCR</code></span></dt>
3866: <dd><p>A multi-line description of the piece of software. This should include
3867: any credits where they are due. Please bear in mind that others do not
3868: share your sense of humour (or spelling idiosyncrasies), and that others
3869: will read everything that you write here.</p></dd>
3870: <dt><span class="term"><code class="filename">PLIST</code></span></dt>
3871: <dd><p>This file governs the files that are installed on your
3872: system: all the binaries, manual pages, etc. There are other
3873: directives which may be entered in this file, to control the
3874: creation and deletion of directories, and the location of
3875: inserted files. See <a class="xref" href="#plist" title="Chapter 19. PLIST issues">Chapter 19, <i>PLIST issues</i></a> for more
3876: information.</p></dd>
3877: </dl></div>
3878: </div>
3879: <div class="sect1">
3880: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
3881: <a name="components.optional"></a>12.5. Optional files</h2></div></div></div>
3882: <div class="sect2">
3883: <div class="titlepage"><div><div><h3 class="title">
3884: <a name="components.optional.bin"></a>12.5.1. Files affecting the binary package</h3></div></div></div>
3885: <div class="variablelist"><dl class="variablelist">
3886: <dt><span class="term"><code class="filename">INSTALL</code></span></dt>
3887: <dd>
1.207 leot 3888: <p>This shell script is invoked twice by <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>.
1.184 rillig 3889: First time after package extraction and before files are
3890: moved in place, the second time after the files to install
3891: are moved in place. This can be used to do any custom
3892: procedures not possible with @exec commands in
1.207 leot 3893: <code class="filename">PLIST</code>. See <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> and
3894: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information. See also <a class="xref" href="#files-and-dirs-outside-prefix" title="20.1. Files and directories outside the installation prefix">Section 20.1, “Files and directories outside the installation prefix”</a>.
1.184 rillig 3895: Please note that you can modify variables in it easily by using
3896: <code class="varname">FILES_SUBST</code> in the package's
3897: <code class="filename">Makefile</code>:</p>
1.1 dsieger 3898: <pre class="programlisting">
1.184 rillig 3899: FILES_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 3900: </pre>
1.184 rillig 3901: <p>replaces "@SOMEVAR@" with <span class="quote">“<span class="quote">somevalue</span>”</span> in the
3902: <code class="filename">INSTALL</code>. By default, substitution is
3903: performed for <code class="varname">PREFIX</code>,
3904: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
3905: <code class="varname">VARBASE</code>, and a few others, type
3906: <span class="command"><strong>make help topic=FILES_SUBST</strong></span> for a
3907: complete list.</p>
3908: </dd>
3909: <dt><span class="term"><code class="filename">DEINSTALL</code></span></dt>
3910: <dd><p>This script is executed before and after any files are removed. It is
3911: this script's responsibility to clean up any additional messy details
3912: around the package's installation, since all pkg_delete knows is how to
3913: delete the files created in the original distribution.
1.207 leot 3914: See <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
3915: and <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.
1.184 rillig 3916: The same methods to replace variables can be used as for
3917: the <code class="filename">INSTALL</code> file.</p></dd>
3918: <dt><span class="term"><code class="filename">MESSAGE</code></span></dt>
3919: <dd>
3920: <p>This file is displayed after installation of the package.
1.198 leot 3921: While this was used often in the past, it has two
3922: problems: the display will be missed if many packages are
3923: intalled at once, and the person installing the package
3924: and the one using or configuring it may be different. It
3925: should therefore be used only in exceptional circumstances
3926: where lasting negative consequences would result from
3927: someone not reading it.</p>
3928: <p>MESSAGE should not be used for:</p>
3929: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3930: <li class="listitem"><p>exhortations to read the documentation</p></li>
3931: <li class="listitem"><p>reminders to install rc.d files and set variables</p></li>
3932: <li class="listitem"><p>anything that should be explained in the
3933: installation/configuration documentation that should
3934: come with the package</p></li>
3935: </ul></div>
3936: <p>If the documentation provided by upstream needs
3937: enhancing, create e.g. files/README.pkgsrc and install it
3938: in the package's documentation directory.
3939: </p>
3940: <p>Note that MESSAGE is shown for all operating
3941: systems and all init systems. If a MESSAGE is necessary,
3942: it should be narrowed to only those operating systems and
3943: init systems to which it applies.</p>
3944: <p>Note that you can modify variables in it easily by using
1.184 rillig 3945: <code class="varname">MESSAGE_SUBST</code> in the package's
3946: <code class="filename">Makefile</code>:</p>
1.1 dsieger 3947: <pre class="programlisting">
1.184 rillig 3948: MESSAGE_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 3949: </pre>
1.184 rillig 3950: <p>replaces "${SOMEVAR}" with <span class="quote">“<span class="quote">somevalue</span>”</span> in
3951: <code class="filename">MESSAGE</code>. By default, substitution is
3952: performed for <code class="varname">PKGNAME</code>,
3953: <code class="varname">PKGBASE</code>, <code class="varname">PREFIX</code>,
3954: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
3955: <code class="varname">PKG_SYSCONFDIR</code>,
3956: <code class="varname">ROOT_GROUP</code>, and
3957: <code class="varname">ROOT_USER</code>.</p>
3958: <p>You can display a different or additional files by
3959: setting the <code class="varname">MESSAGE_SRC</code> variable. Its
3960: default is <code class="filename">MESSAGE</code>, if the file
3961: exists.</p>
3962: </dd>
3963: <dt><span class="term"><code class="filename">ALTERNATIVES</code></span></dt>
3964: <dd>
3965: <p>This file is used by the alternatives framework.
3966: It creates, configures, and destroys generic wrappers used to
3967: run programs with similar interfaces.
3968: See pkg_alternatives(8) from pkgtools/pkg_alternatives
3969: for more information.</p>
3970: <p>Each line of the file contains two filenames, first
3971: the wrapper and then the alternative provided by the package.
3972: Both paths are relative to <code class="varname">PREFIX</code>.</p>
3973: </dd>
3974: </dl></div>
3975: </div>
3976: <div class="sect2">
3977: <div class="titlepage"><div><div><h3 class="title">
3978: <a name="components.optional.build"></a>12.5.2. Files affecting the build process</h3></div></div></div>
3979: <div class="variablelist"><dl class="variablelist">
3980: <dt><span class="term"><code class="filename">Makefile.common</code></span></dt>
3981: <dd><p>This file contains arbitrary things that could
3982: also go into a <code class="filename">Makefile</code>, but its purpose is
3983: to be used by more than one package. This file should only be
3984: used when the packages that will use the file are known in
3985: advance. For other purposes it is often better to write a
3986: <code class="filename">*.mk</code> file and give it a good name that
3987: describes what it does.</p></dd>
3988: <dt><span class="term"><code class="filename">buildlink3.mk</code></span></dt>
3989: <dd><p>This file contains the dependency information
3990: for the buildlink3 framework (see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p></dd>
3991: <dt><span class="term"><code class="filename">hacks.mk</code></span></dt>
3992: <dd><p>This file contains workarounds for compiler bugs
3993: and similar things. It is included automatically by the pkgsrc
3994: infrastructure, so you don't need an extra
3995: <code class="literal">.include</code> line for
3996: it.</p></dd>
3997: <dt><span class="term"><code class="filename">options.mk</code></span></dt>
3998: <dd><p>This file contains the code for the
3999: package-specific options (see <a class="xref" href="#options" title="Chapter 16. Options handling">Chapter 16, <i>Options handling</i></a>) that can be
4000: selected by the user. If a package has only one or two options,
4001: it is equally acceptable to put the code directly into the
4002: <code class="filename">Makefile</code>.</p></dd>
4003: </dl></div>
4004: </div>
4005: <div class="sect2">
4006: <div class="titlepage"><div><div><h3 class="title">
4007: <a name="components.optional.none"></a>12.5.3. Files affecting nothing at all</h3></div></div></div>
4008: <div class="variablelist"><dl class="variablelist">
4009: <dt><span class="term"><code class="filename">README*</code></span></dt>
4010: <dd><p>These files do not take place in the creation of
4011: a package and thus are purely informative to the package
4012: developer.</p></dd>
4013: <dt><span class="term"><code class="filename">TODO</code></span></dt>
4014: <dd><p>This file contains things that need to be done
4015: to make the package even
4016: better.</p></dd>
4017: </dl></div>
4018: </div>
4019: </div>
4020: <div class="sect1">
4021: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4022: <a name="work-dir"></a>12.6. <code class="filename">work*</code>
4023: </h2></div></div></div>
4024: <p>When you type <span class="command"><strong>make</strong></span>, the distribution files are
4025: unpacked into the directory denoted by
4026: <code class="varname">WRKDIR</code>. It can be removed by running
4027: <span class="command"><strong>make clean</strong></span>. Besides the sources, this
4028: directory is also used to keep various timestamp files.
4029: The directory gets <span class="emphasis"><em>removed completely</em></span> on clean.
4030: The default is <code class="filename">${.CURDIR}/work</code>
4031: or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code>
4032: if <code class="varname">OBJMACHINE</code> is set.</p>
1.1 dsieger 4033: </div>
1.184 rillig 4034: <div class="sect1">
4035: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4036: <a name="files-dir"></a>12.7. <code class="filename">files/*</code>
4037: </h2></div></div></div>
4038: <p>If you have any files that you wish to be placed in the package
4039: prior to configuration or building, you can place these files here
4040: and use a <span class="command"><strong>${CP}</strong></span> command in the
4041: <span class="quote">“<span class="quote">post-extract</span>”</span> target to achieve this.</p>
4042: <p>If you want to share files in this way with other
4043: packages, set the <code class="varname">FILESDIR</code> variable to point
4044: to the other package's <code class="filename">files</code> directory,
4045: e.g.:</p>
1.1 dsieger 4046: <pre class="programlisting">
1.184 rillig 4047: FILESDIR= ../../editors/xemacs/files
1.1 dsieger 4048: </pre>
4049: </div>
4050: </div>
1.41 asau 4051: <div class="chapter">
1.1 dsieger 4052: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 4053: <a name="build"></a>Chapter 13. The build process</h2></div></div></div>
1.1 dsieger 4054: <div class="toc">
4055: <p><b>Table of Contents</b></p>
1.100 leot 4056: <dl class="toc">
1.184 rillig 4057: <dt><span class="sect1"><a href="#build.intro">13.1. Introduction</a></span></dt>
4058: <dt><span class="sect1"><a href="#build.prefix">13.2. Program location</a></span></dt>
4059: <dt><span class="sect1"><a href="#build.builddirs">13.3. Directories used during the build process</a></span></dt>
4060: <dt><span class="sect1"><a href="#build.running">13.4. Running a phase</a></span></dt>
4061: <dt><span class="sect1"><a href="#build.fetch">13.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
4062: <dd><dl>
4063: <dt><span class="sect2"><a href="#build.fetch.what">13.5.1. What to fetch and where to get it from</a></span></dt>
4064: <dt><span class="sect2"><a href="#build.fetch.how">13.5.2. How are the files fetched?</a></span></dt>
4065: </dl></dd>
4066: <dt><span class="sect1"><a href="#build.checksum">13.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
4067: <dt><span class="sect1"><a href="#build.extract">13.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
4068: <dt><span class="sect1"><a href="#build.patch">13.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
4069: <dt><span class="sect1"><a href="#build.tools">13.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
4070: <dt><span class="sect1"><a href="#build.wrapper">13.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
4071: <dt><span class="sect1"><a href="#build.configure">13.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
4072: <dt><span class="sect1"><a href="#build.build">13.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
4073: <dt><span class="sect1"><a href="#build.test">13.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
4074: <dt><span class="sect1"><a href="#build.install">13.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
4075: <dt><span class="sect1"><a href="#build.package">13.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
4076: <dt><span class="sect1"><a href="#build.clean">13.16. Cleaning up</a></span></dt>
4077: <dt><span class="sect1"><a href="#build.helpful-targets">13.17. Other helpful targets</a></span></dt>
1.1 dsieger 4078: </dl>
4079: </div>
1.41 asau 4080: <div class="sect1">
1.1 dsieger 4081: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4082: <a name="build.intro"></a>13.1. Introduction</h2></div></div></div>
4083: <p>This chapter gives a detailed description on how a package is
4084: built. Building a package is separated into different
4085: <span class="emphasis"><em>phases</em></span> (for example <code class="varname">fetch</code>,
4086: <code class="varname">build</code>, <code class="varname">install</code>), all of which are
4087: described in the following sections. Each phase is split into
4088: so-called <span class="emphasis"><em>stages</em></span>, which take the name of the
4089: containing phase, prefixed by one of <code class="varname">pre-</code>,
4090: <code class="varname">do-</code> or <code class="varname">post-</code>. (Examples are
4091: <code class="varname">pre-configure</code>, <code class="varname">post-build</code>.) Most
4092: of the actual work is done in the <code class="varname">do-*</code> stages.</p>
4093: <p>Never override the regular targets (like
4094: <code class="varname">fetch</code>), if you have to, override the
4095: <code class="varname">do-*</code> ones instead.</p>
4096: <p>The basic steps for building a program are always the same. First
4097: the program's source (<span class="emphasis"><em>distfile</em></span>) must be brought to
4098: the local system and then extracted. After any pkgsrc-specific patches
4099: to compile properly are applied, the software can be configured, then
4100: built (usually by compiling), and finally the generated binaries, etc.
4101: can be put into place on the system.</p>
4102: <p>To get more details about what is happening at each step,
4103: you can set the <code class="varname">PKG_VERBOSE</code> variable, or the
4104: <code class="varname">PATCH_DEBUG</code> variable if you are just interested
4105: in more details about the <span class="emphasis"><em>patch</em></span> step.</p>
4106: </div>
4107: <div class="sect1">
4108: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4109: <a name="build.prefix"></a>13.2. Program location</h2></div></div></div>
4110: <p>Before outlining the process performed by the NetBSD package system in
4111: the next section, here's a brief discussion on where programs are
4112: installed, and which variables influence this.</p>
4113: <p>The automatic variable <code class="varname">PREFIX</code> indicates
4114: where all files of the final program shall be installed. It is
4115: usually set to <code class="varname">LOCALBASE</code>
4116: (<code class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code>
4117: for pkgs in the <code class="filename">cross</code> category. The value of
4118: <code class="varname">PREFIX</code> needs to be put
4119: into the various places in the program's source where paths to
4120: these files are encoded. See <a class="xref" href="#components.patches" title="12.3. patches/*">Section 12.3, “<code class="filename">patches/*</code>”</a> and <a class="xref" href="#fixes.libtool" title="21.3.1. Shared libraries - libtool">Section 21.3.1, “Shared libraries - libtool”</a> for more details.</p>
4121: <p>When choosing which of these variables to use,
4122: follow the following rules:</p>
1.41 asau 4123: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.184 rillig 4124: <li class="listitem"><p><code class="varname">PREFIX</code> always points to the location
4125: where the current pkg will be installed. When referring to a
4126: pkg's own installation path, use
4127: <span class="quote">“<span class="quote">${PREFIX}</span>”</span>.</p></li>
1.223 nia 4128: <li class="listitem"><p><code class="varname">LOCALBASE</code> is where all pkgs
1.184 rillig 4129: are installed. If you need to construct a -I or -L argument
4130: to the compiler to find includes and libraries installed by
1.223 nia 4131: another pkg, use <span class="quote">“<span class="quote">${LOCALBASE}</span>”</span>. The name
1.184 rillig 4132: <code class="varname">LOCALBASE</code> stems from FreeBSD, which
4133: installed all packages in <code class="filename">/usr/local</code>. As
4134: pkgsrc leaves <code class="filename">/usr/local</code> for the system
4135: administrator, this variable is a misnomer.</p></li>
4136: <li class="listitem"><p><code class="varname">X11BASE</code> is where the actual X11
4137: distribution (from xsrc, etc.) is installed. When looking for
4138: <span class="emphasis"><em>standard</em></span> X11 includes (not those
4139: installed by a package), use <span class="quote">“<span class="quote">${X11BASE}</span>”</span>.</p></li>
4140: <li class="listitem"><p>X11-based packages using imake must set
4141: <code class="varname">USE_IMAKE</code> to be installed correctly under
4142: <code class="varname">LOCALBASE</code>.</p></li>
4143: <li class="listitem"><p>Within <code class="filename">${PREFIX}</code>, packages should
1.207 leot 4144: install files according to <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/hier.7"><span class="citerefentry"><span class="refentrytitle">hier</span>(7)</span></a>, with the exception that
1.184 rillig 4145: manual pages go into <code class="filename">${PREFIX}/man</code>, not
4146: <code class="filename">${PREFIX}/share/man</code>.</p></li>
4147: </ul></div>
4148: </div>
4149: <div class="sect1">
4150: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4151: <a name="build.builddirs"></a>13.3. Directories used during the build process</h2></div></div></div>
4152: <p>When building a package, various directories are used to store
4153: source files, temporary files, pkgsrc-internal files, and so on. These
4154: directories are explained here.</p>
4155: <p>Some of the directory variables contain relative pathnames. There
4156: are two common base directories for these relative directories:
4157: <code class="varname">PKGSRCDIR/PKGPATH</code> is used for directories that are
4158: pkgsrc-specific. <code class="varname">WRKSRC</code> is used for directories
4159: inside the package itself.</p>
4160: <div class="variablelist"><dl class="variablelist">
4161: <dt><span class="term"><code class="varname">PKGSRCDIR</code></span></dt>
4162: <dd><p>This is an absolute pathname that points to the pkgsrc
4163: root directory. Generally, you don't need
4164: it.</p></dd>
4165: <dt><span class="term"><code class="varname">PKGDIR</code></span></dt>
4166: <dd><p>This is an absolute pathname that points to the
4167: current package.</p></dd>
4168: <dt><span class="term"><code class="varname">PKGPATH</code></span></dt>
1.228 gutterid 4169: <dd>
4170: <p>This is a pathname relative to
4171: <code class="varname">PKGSRCDIR</code> that points to the current package.
4172: It is defined after including <code class="filename">bsd.prefs.mk</code>
4173: and can be used in makefile fragments that are used by several
4174: packages to distinguish between these packages. Other variables
4175: that would serve the same purpose are <code class="varname">PKGBASE</code>
4176: and <code class="varname">PKGNAME</code>, but these are only defined after
4177: including <code class="filename">bsd.pkg.mk</code>, which is too
4178: late.</p>
4179: <p>In <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the pkgsrc user can use
4180: <code class="varname">PKGPATH</code> to tweak variables like
4181: <code class="varname">MAKE_JOBS</code> and
4182: <code class="varname">CFLAGS</code>.</p>
4183: </dd>
1.184 rillig 4184: <dt><span class="term"><code class="varname">WRKDIR</code></span></dt>
4185: <dd><p>This is an absolute pathname pointing to the directory
4186: where all work takes place. The distfiles are extracted to this
4187: directory. It also contains temporary directories and log files used by
4188: the various pkgsrc frameworks, like <span class="emphasis"><em>buildlink</em></span> or
4189: the <span class="emphasis"><em>wrappers</em></span>.</p></dd>
4190: <dt><span class="term"><code class="varname">WRKSRC</code></span></dt>
4191: <dd><p>This is an absolute pathname pointing to the directory
4192: where the distfiles are extracted. It is usually a direct subdirectory
4193: of <code class="varname">WRKDIR</code>, and often it's the only directory entry
4194: that isn't hidden. This variable may be changed by a package
4195: <code class="filename">Makefile</code>.</p></dd>
4196: </dl></div>
4197: <p>The <code class="varname">CREATE_WRKDIR_SYMLINK</code> definition takes either
4198: the value <span class="emphasis"><em>yes</em></span> or <span class="emphasis"><em>no</em></span> and defaults
4199: to <span class="emphasis"><em>no</em></span>. It indicates whether a symbolic link to the
4200: <code class="varname">WRKDIR</code> is to be created in the pkgsrc entry's directory.
4201: If users would like to have their pkgsrc trees behave in a
4202: read-only manner, then the value of
4203: <code class="varname">CREATE_WRKDIR_SYMLINK</code> should be set to
4204: <span class="emphasis"><em>no</em></span>.</p>
1.1 dsieger 4205: </div>
1.41 asau 4206: <div class="sect1">
1.1 dsieger 4207: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4208: <a name="build.running"></a>13.4. Running a phase</h2></div></div></div>
4209: <p>You can run a particular phase by typing <span class="command"><strong>make
1.228 gutterid 4210: <em class="replaceable"><code>phase</code></em></strong></span>, where
4211: <em class="replaceable"><code>phase</code></em> is the name of the phase. This will
4212: automatically run all phases that are required for this phase. The
4213: default phase is <code class="varname">build</code>, that is, when you run
4214: <span class="command"><strong>make</strong></span> without parameters in a package directory,
1.184 rillig 4215: the package will be built, but not installed.</p>
1.1 dsieger 4216: </div>
1.41 asau 4217: <div class="sect1">
1.1 dsieger 4218: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4219: <a name="build.fetch"></a>13.5. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
4220: <p>The first step in building a package is to fetch the
4221: distribution files (distfiles) from the sites that are providing
4222: them. This is the task of the <span class="emphasis"><em>fetch</em></span>
4223: phase.</p>
1.41 asau 4224: <div class="sect2">
1.1 dsieger 4225: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 4226: <a name="build.fetch.what"></a>13.5.1. What to fetch and where to get it from</h3></div></div></div>
4227: <p>In simple cases, <code class="varname">MASTER_SITES</code>
4228: defines all URLs from where the distfile, whose name is
4229: derived from the <code class="varname">DISTNAME</code> variable, is
4230: fetched. The more complicated cases are described
4231: below.</p>
4232: <p>The variable <code class="varname">DISTFILES</code> specifies
4233: the list of distfiles that have to be fetched. Its value
4234: defaults to <code class="literal">${DEFAULT_DISTFILES}</code> and
4235: its value is <code class="literal">${DISTNAME}${EXTRACT_SUFX}</code>,
4236: so that most packages don't need to define it at all.
4237: <code class="varname">EXTRACT_SUFX</code> is
4238: <code class="literal">.tar.gz</code> by default, but can be changed
4239: freely. Note that if your package requires additional
4240: distfiles to the default one, you cannot just append the
4241: additional filenames using the <code class="literal">+=</code>
4242: operator, but you have write for example:</p>
4243: <pre class="programlisting">
4244: DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
4245: </pre>
4246: <p>Each distfile is fetched from a list of sites, usually
4247: <code class="varname">MASTER_SITES</code>. If the package has multiple
4248: <code class="varname">DISTFILES</code> or multiple
4249: <code class="varname">PATCHFILES</code> from different sites, you can
4250: set
4251: <code class="varname">SITES.<em class="replaceable"><code>distfile</code></em></code>
4252: to the list of URLs where the file
4253: <code class="filename"><em class="replaceable"><code>distfile</code></em></code>
4254: (including the suffix) can be found.</p>
4255: <pre class="programlisting">
4256: DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
4257: DISTFILES+= foo-file.tar.gz
4258: SITES.foo-file.tar.gz= \
4259: https://www.somewhere.com/somehow/ \
4260: https://www.somewhereelse.com/mirror/somehow/
4261: </pre>
4262: <p>When actually fetching the distfiles, each item from
4263: <code class="varname">MASTER_SITES</code> or
4264: <code class="varname">SITES.*</code> gets the name of each distfile
4265: appended to it, without an intermediate slash. Therefore,
4266: all site values have to end with a slash or other separator
4267: character. This allows for example to set
4268: <code class="varname">MASTER_SITES</code> to a URL of a CGI script
4269: that gets the name of the distfile as a parameter. In this
4270: case, the definition would look like:</p>
4271: <pre class="programlisting">
4272: MASTER_SITES= https://www.example.com/download.cgi?file=
4273: </pre>
4274: <p> The exception to this rule are URLs starting with a dash.
4275: In that case the URL is taken as is, fetched and the result
4276: stored under the name of the distfile. You can use this style
4277: for the case when the download URL style does not match the
4278: above common case. For example, if permanent download URL is a
4279: redirector to the real download URL, or the download file name
4280: is offered by an HTTP Content-Disposition header. In the
4281: following example, <code class="filename">foo-1.0.0.tar.gz</code> will be
4282: created instead of the default
4283: <code class="filename">v1.0.0.tar.gz</code>.</p>
4284: <pre class="programlisting">
4285: DISTNAME= foo-1.0.0
4286: MASTER_SITES= -https://www.example.com/archive/v1.0.0.tar.gz
4287: </pre>
4288: <p>There are some predefined values for
4289: <code class="varname">MASTER_SITES</code>, which can be used in
4290: packages. The names of the variables should speak for
4291: themselves.</p>
4292: <table border="0" summary="Simple list" class="simplelist">
4293: <tr>
4294: <td>MASTER_SITE_APACHE</td>
4295: <td>MASTER_SITE_BACKUP</td>
4296: </tr>
4297: <tr>
4298: <td>MASTER_SITE_CRATESIO</td>
4299: <td>MASTER_SITE_CYGWIN</td>
4300: </tr>
4301: <tr>
4302: <td>MASTER_SITE_DEBIAN</td>
4303: <td>MASTER_SITE_FREEBSD</td>
4304: </tr>
4305: <tr>
4306: <td>MASTER_SITE_FREEBSD_LOCAL</td>
4307: <td>MASTER_SITE_GENTOO</td>
4308: </tr>
4309: <tr>
4310: <td>MASTER_SITE_GITHUB</td>
1.225 gutterid 4311: <td>MASTER_SITE_GITLAB</td>
4312: </tr>
4313: <tr>
1.184 rillig 4314: <td>MASTER_SITE_GNOME</td>
1.225 gutterid 4315: <td>MASTER_SITE_GNU</td>
1.184 rillig 4316: </tr>
4317: <tr>
4318: <td>MASTER_SITE_GNUSTEP</td>
1.225 gutterid 4319: <td>MASTER_SITE_HASKELL_HACKAGE</td>
1.184 rillig 4320: </tr>
4321: <tr>
4322: <td>MASTER_SITE_IFARCHIVE</td>
1.225 gutterid 4323: <td>MASTER_SITE_KDE</td>
1.184 rillig 4324: </tr>
4325: <tr>
4326: <td>MASTER_SITE_MOZILLA</td>
1.225 gutterid 4327: <td>MASTER_SITE_MOZILLA_ALL</td>
1.184 rillig 4328: </tr>
4329: <tr>
4330: <td>MASTER_SITE_MYSQL</td>
1.225 gutterid 4331: <td>MASTER_SITE_NETLIB</td>
1.184 rillig 4332: </tr>
4333: <tr>
4334: <td>MASTER_SITE_OPENBSD</td>
1.225 gutterid 4335: <td>MASTER_SITE_OPENOFFICE</td>
1.184 rillig 4336: </tr>
4337: <tr>
4338: <td>MASTER_SITE_OSDN</td>
1.225 gutterid 4339: <td>MASTER_SITE_PERL_CPAN</td>
1.184 rillig 4340: </tr>
4341: <tr>
4342: <td>MASTER_SITE_PGSQL</td>
1.225 gutterid 4343: <td>MASTER_SITE_PYPI</td>
1.184 rillig 4344: </tr>
4345: <tr>
4346: <td>MASTER_SITE_RUBYGEMS</td>
1.225 gutterid 4347: <td>MASTER_SITE_R_CRAN</td>
1.184 rillig 4348: </tr>
4349: <tr>
4350: <td>MASTER_SITE_SOURCEFORGE</td>
1.225 gutterid 4351: <td>MASTER_SITE_SUNSITE</td>
1.184 rillig 4352: </tr>
1.1 dsieger 4353: <tr>
1.184 rillig 4354: <td>MASTER_SITE_SUSE</td>
1.225 gutterid 4355: <td>MASTER_SITE_TEX_CTAN</td>
1.1 dsieger 4356: </tr>
4357: <tr>
1.184 rillig 4358: <td>MASTER_SITE_XCONTRIB</td>
1.225 gutterid 4359: <td>MASTER_SITE_XEMACS</td>
1.1 dsieger 4360: </tr>
4361: <tr>
1.184 rillig 4362: <td>MASTER_SITE_XORG</td>
1.225 gutterid 4363: <td> </td>
1.184 rillig 4364: </tr>
4365: </table>
4366: <p>Some explanations for the less self-explaining ones:
4367: <code class="varname">MASTER_SITE_BACKUP</code> contains backup sites
4368: 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
4369: 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>
4370: <p>If you choose one of these predefined sites, you may
4371: want to specify a subdirectory of that site. Since these
4372: macros may expand to more than one actual site, you
4373: <span class="emphasis"><em>must</em></span> use the following construct to
4374: specify a subdirectory:</p>
1.1 dsieger 4375: <pre class="programlisting">
1.184 rillig 4376: MASTER_SITES= ${MASTER_SITE_GNU:=subdirectory/name/}
4377: MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/}
1.1 dsieger 4378: </pre>
1.184 rillig 4379: <p>Note the trailing slash after the subdirectory
4380: name.</p>
4381: </div>
4382: <div class="sect2">
4383: <div class="titlepage"><div><div><h3 class="title">
4384: <a name="build.fetch.how"></a>13.5.2. How are the files fetched?</h3></div></div></div>
4385: <p>The <span class="emphasis"><em>fetch</em></span> phase makes sure that
4386: all the distfiles exist in a local directory
4387: (<code class="varname">DISTDIR</code>, which can be set by the pkgsrc
4388: user). If the files do not exist, they are fetched using
4389: commands of the form</p>
1.1 dsieger 4390: <pre class="programlisting">
1.184 rillig 4391: ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
4392: </pre>
4393: <p>where <code class="literal">${site}</code> varies through
4394: several possibilities in turn: first,
4395: <code class="varname">MASTER_SITE_OVERRIDE</code> is tried, then the
4396: sites specified in either <code class="varname">SITES.file</code> if
4397: defined, else <code class="varname">MASTER_SITES</code> or
4398: <code class="varname">PATCH_SITES</code>, as applies, then finally the
4399: value of <code class="varname">MASTER_SITE_BACKUP</code>. The order of
4400: all except the first and the last can be optionally sorted
4401: by the user, via setting either
4402: <code class="varname">MASTER_SORT_RANDOM</code>, and
4403: <code class="varname">MASTER_SORT_AWK</code> or
4404: <code class="varname">MASTER_SORT_REGEX</code>.</p>
4405: <p> The specific command and arguments used depend on the
4406: <code class="varname">FETCH_USING</code> parameter. The example above is
4407: for <code class="literal">FETCH_USING=custom</code>.</p>
4408: <p>The distfiles mirror run by the NetBSD Foundation uses the
4409: <span class="emphasis"><em>mirror-distfiles</em></span> target to mirror the
4410: distfiles, if they are freely distributable. Packages setting
4411: <code class="varname">NO_SRC_ON_FTP</code> (usually to
4412: <span class="quote">“<span class="quote">${RESTRICTED}</span>”</span>) will not have their distfiles
4413: mirrored.</p>
1.1 dsieger 4414: </div>
4415: </div>
1.184 rillig 4416: <div class="sect1">
4417: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4418: <a name="build.checksum"></a>13.6. The <span class="emphasis"><em>checksum</em></span> phase</h2></div></div></div>
4419: <p>After the distfile(s) are fetched, their checksum is
4420: generated and compared with the checksums stored in the
4421: distinfo file. If the checksums don't match, the build is
4422: aborted. This is to ensure the same distfile is used for
4423: building, and that the distfile wasn't changed, e.g. by some
4424: malign force, deliberately changed distfiles on the master
4425: distribution site or network lossage.</p>
1.1 dsieger 4426: </div>
1.41 asau 4427: <div class="sect1">
1.1 dsieger 4428: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4429: <a name="build.extract"></a>13.7. The <span class="emphasis"><em>extract</em></span> phase</h2></div></div></div>
4430: <p>When the distfiles are present on the local system, they
4431: need to be extracted, as they usually come in the form of some
4432: compressed archive format.</p>
4433: <p>By default, all <code class="varname">DISTFILES</code> are
4434: extracted. If you only need some of them, you can set the
4435: <code class="varname">EXTRACT_ONLY</code> variable to the list of those
4436: files.</p>
4437: <p>Extracting the files is usually done by a little
4438: program, <code class="filename">mk/extract/extract</code>, which
4439: already knows how to extract various archive formats, so most
4440: likely you will not need to change anything here. But if you
4441: need, the following variables may help you:</p>
1.41 asau 4442: <div class="variablelist"><dl class="variablelist">
1.184 rillig 4443: <dt><span class="term"><code class="varname">EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}</code></span></dt>
4444: <dd><p>Use these variables to override the default
4445: options for an extract command, which are defined in
4446: <code class="filename">mk/extract/extract</code>.</p></dd>
4447: <dt><span class="term"><code class="varname">EXTRACT_USING</code></span></dt>
4448: <dd><p>This variable can be set to
4449: <code class="literal">bsdtar</code>, <code class="literal">gtar</code>, <code class="literal">nbtar</code>
4450: (which is the default value), <code class="literal">pax</code>, or an
4451: absolute pathname pointing to the command with which tar
4452: archives should be extracted. It is preferred to choose bsdtar over gtar
4453: if NetBSD's pax-as-tar is not good enough.</p></dd>
1.1 dsieger 4454: </dl></div>
1.184 rillig 4455: <p>If the <code class="filename">extract</code> program doesn't
4456: serve your needs, you can also override the
4457: <code class="varname">EXTRACT_CMD</code> variable, which holds the
4458: command used for extracting the files. This command is
4459: executed in the <code class="filename">${WRKSRC}</code>
4460: directory. During execution of this command, the shell
4461: variable <code class="varname">extract_file</code> holds the absolute
4462: pathname of the file that is going to be extracted.</p>
4463: <p>And if that still does not suffice, you can override the
4464: <code class="varname">do-extract</code> target in the package
4465: Makefile.</p>
1.1 dsieger 4466: </div>
1.41 asau 4467: <div class="sect1">
1.1 dsieger 4468: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4469: <a name="build.patch"></a>13.8. The <span class="emphasis"><em>patch</em></span> phase</h2></div></div></div>
4470: <p>After extraction, all the patches named by the
4471: <code class="varname">PATCHFILES</code>, those present in the patches
4472: subdirectory of the package as well as in
4473: $LOCALPATCHES/$PKGPATH (e.g.
4474: <code class="filename">/usr/local/patches/graphics/png</code>) are
4475: applied. Patchfiles ending in <code class="filename">.Z</code> or
4476: <code class="filename">.gz</code> are uncompressed before they are
4477: applied, files ending in <code class="filename">.orig</code> or
4478: <code class="filename">.rej</code> are ignored. Any special options to
1.207 leot 4479: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
1.184 rillig 4480: <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.207 leot 4481: <p>By default <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/patch.1"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given special arguments to make it
1.184 rillig 4482: fail if the expected text from the patch context is not found in the
4483: patched file. If that happens, fix the patch file by comparing it
4484: with the actual text in the file to be patched.</p>
1.1 dsieger 4485: </div>
1.41 asau 4486: <div class="sect1">
1.1 dsieger 4487: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4488: <a name="build.tools"></a>13.9. The <span class="emphasis"><em>tools</em></span> phase</h2></div></div></div>
4489: <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>.
4490: </p>
1.1 dsieger 4491: </div>
1.41 asau 4492: <div class="sect1">
1.1 dsieger 4493: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4494: <a name="build.wrapper"></a>13.10. The <span class="emphasis"><em>wrapper</em></span> phase</h2></div></div></div>
4495: <p>This phase creates wrapper programs for the compilers and
4496: linkers. The following variables can be used to tweak the
4497: wrappers.</p>
4498: <div class="variablelist"><dl class="variablelist">
4499: <dt><span class="term"><code class="varname">ECHO_WRAPPER_MSG</code></span></dt>
4500: <dd><p>The command used to print progress
4501: messages. Does nothing by default. Set to
4502: <code class="literal">${ECHO}</code> to see the progress
4503: messages.</p></dd>
4504: <dt><span class="term"><code class="varname">WRAPPER_DEBUG</code></span></dt>
4505: <dd><p>This variable can be set to
4506: <code class="literal">yes</code> (default) or <code class="literal">no</code>,
4507: depending on whether you want additional information in the
4508: wrapper log file.</p></dd>
4509: <dt><span class="term"><code class="varname">WRAPPER_UPDATE_CACHE</code></span></dt>
4510: <dd><p>This variable can be set to
4511: <code class="literal">yes</code> or <code class="literal">no</code>, depending
4512: on whether the wrapper should use its cache, which will
4513: improve the speed. The default value is
4514: <code class="literal">yes</code>, but is forced to
4515: <code class="literal">no</code> if the platform does not support
4516: it.</p></dd>
4517: <dt><span class="term"><code class="varname">WRAPPER_REORDER_CMDS</code></span></dt>
4518: <dd><p>A list of reordering commands. A reordering
4519: command has the form
4520: <code class="literal">reorder:l:<em class="replaceable"><code>lib1</code></em>:<em class="replaceable"><code>lib2</code></em></code>.
4521: It ensures that that
4522: <code class="literal">-l<em class="replaceable"><code>lib1</code></em></code> occurs
4523: before <code class="literal">-l<em class="replaceable"><code>lib2</code></em></code>.
4524: </p></dd>
4525: </dl></div>
4526: </div>
4527: <div class="sect1">
4528: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
4529: <a name="build.configure"></a>13.11. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
4530: <p>Most pieces of software need information on the header
4531: files, system calls, and library routines which are available
4532: on the platform they run on. The process of determining this
4533: information is known as configuration, and is usually
4534: automated. In most cases, a script is supplied with the
4535: distfiles, and its invocation results in generation of header
4536: files, Makefiles, etc.</p>
4537: <p>If the package contains a configure script, this can be
4538: invoked by setting <code class="varname">HAS_CONFIGURE</code> to
4539: <span class="quote">“<span class="quote">yes</span>”</span>. If the configure script is a GNU autoconf
4540: script, you should set <code class="varname">GNU_CONFIGURE</code> to
1.187 rillig 4541: <span class="quote">“<span class="quote">yes</span>”</span> instead.</p>
4542: <p>In the <code class="literal">do-configure</code> stage, a rough
4543: equivalent of the following command is run. See
4544: <code class="filename">mk/configure/configure.mk</code>, target
4545: <code class="literal">do-configure-script</code> for the exact
4546: definition.</p>
4547: <pre class="programlisting">
4548: .for dir in ${CONFIGURE_DIRS}
4549: cd ${WRKSRC} && cd ${dir} \
4550: && env ${CONFIGURE_ENV} \
4551: ${CONFIG_SHELL} ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
1.184 rillig 4552: .endfor
1.1 dsieger 4553: </pre>
1.184 rillig 4554: <p><code class="varname">CONFIGURE_DIRS</code> (default:
4555: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4556: <code class="varname">WRKSRC</code>. In each of these directories, the
4557: configure script is run with the environment
4558: <code class="varname">CONFIGURE_ENV</code> and arguments
4559: <code class="varname">CONFIGURE_ARGS</code>. The variables
4560: <code class="varname">CONFIGURE_ENV</code>,
4561: <code class="varname">CONFIGURE_SCRIPT</code> (default:
4562: <span class="quote">“<span class="quote">./configure</span>”</span>) and
4563: <code class="varname">CONFIGURE_ARGS</code> may all be changed by the
4564: package.</p>
4565: <p>If the program uses the Perl way of configuration (mainly Perl
4566: modules, but not only), i.e. a file called
4567: <code class="filename">Makefile.PL</code>, it should include
4568: <code class="filename">../../lang/perl5/module.mk</code>. To set any parameter for
4569: <code class="filename">Makefile.PL</code> use the <code class="varname">MAKE_PARAMS</code>
4570: variable (e.g., <code class="literal">MAKE_PARAMS+=foo=bar</code></p>
4571: <p>If the program uses an <code class="filename">Imakefile</code>
4572: for configuration, the appropriate steps can be invoked by
4573: setting <code class="varname">USE_IMAKE</code> to
4574: <span class="quote">“<span class="quote">yes</span>”</span>. If you only need xmkmf, add it to <code class="varname">USE_TOOLS</code>.
4575: You can add variables to xmkmf's environment by adding them to the
4576: <code class="varname">SCRIPTS_ENV</code> variable.</p>
4577: <p>If the program uses <code class="filename">cmake</code>
4578: for configuration, the appropriate steps can be invoked by
4579: setting <code class="varname">USE_CMAKE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.
4580: You can add variables to cmake's environment by adding them to the
4581: <code class="varname">CONFIGURE_ENV</code> variable and arguments to cmake
4582: by adding them to the <code class="varname">CMAKE_ARGS</code> variable.
4583: The top directory argument is given by the
4584: <code class="varname">CMAKE_ARG_PATH</code> variable, that defaults to
4585: <span class="quote">“<span class="quote">.</span>”</span> (relative to <code class="varname">CONFIGURE_DIRS</code>)</p>
4586: <p>If there is no configure step at all, set
4587: <code class="varname">NO_CONFIGURE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 4588: </div>
1.41 asau 4589: <div class="sect1">
1.1 dsieger 4590: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4591: <a name="build.build"></a>13.12. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.187 rillig 4592: <p>For building a package, a rough equivalent of the following
4593: code is executed; see <code class="filename">mk/build/build.mk</code>, target
4594: <code class="literal">do-build</code> for the exact definition.</p>
1.1 dsieger 4595: <pre class="programlisting">
1.187 rillig 4596: .for dir in ${BUILD_DIRS}
4597: cd ${WRKSRC} && cd ${dir} \
1.184 rillig 4598: && env ${MAKE_ENV} \
1.187 rillig 4599: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${BUILD_MAKE_FLAGS} \
1.184 rillig 4600: -f ${MAKE_FILE} \
4601: ${BUILD_TARGET}
4602: .endfor
1.1 dsieger 4603: </pre>
1.184 rillig 4604: <p><code class="varname">BUILD_DIRS</code> (default:
4605: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
4606: <code class="varname">WRKSRC</code>. In each of these directories,
4607: <code class="varname">MAKE_PROGRAM</code> is run with the environment
4608: <code class="varname">MAKE_ENV</code> and arguments
4609: <code class="varname">BUILD_MAKE_FLAGS</code>. The variables
4610: <code class="varname">MAKE_ENV</code>,
4611: <code class="varname">BUILD_MAKE_FLAGS</code>,
4612: <code class="varname">MAKE_FILE</code> and
4613: <code class="varname">BUILD_TARGET</code> may all be changed by the
4614: package.</p>
4615: <p>The default value of <code class="varname">MAKE_PROGRAM</code> is
4616: <span class="quote">“<span class="quote">gmake</span>”</span> if <code class="varname">USE_TOOLS</code> contains
4617: <span class="quote">“<span class="quote">gmake</span>”</span>, <span class="quote">“<span class="quote">make</span>”</span> otherwise. The
4618: default value of <code class="varname">MAKE_FILE</code> is
4619: <span class="quote">“<span class="quote">Makefile</span>”</span>, and <code class="varname">BUILD_TARGET</code>
4620: defaults to <span class="quote">“<span class="quote">all</span>”</span>.</p>
4621: <p>If there is no build step at all, set
4622: <code class="varname">NO_BUILD</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 4623: </div>
1.41 asau 4624: <div class="sect1">
1.1 dsieger 4625: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4626: <a name="build.test"></a>13.13. The <span class="emphasis"><em>test</em></span> phase</h2></div></div></div>
4627: <p>[TODO]</p>
1.1 dsieger 4628: </div>
1.41 asau 4629: <div class="sect1">
1.1 dsieger 4630: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4631: <a name="build.install"></a>13.14. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
4632: <p>Once the build stage has completed, the final step is to
4633: install the software in public directories, so users can
4634: access the programs and files.</p>
1.187 rillig 4635: <p>In the <span class="emphasis"><em>install</em></span> phase, a rough equivalent
4636: of the following code is executed; see
4637: <code class="filename">mk/install/install.mk</code>, target
4638: <code class="literal">do-install</code> for the exact definition. Additionally,
4639: before and after this code, several consistency checks are run
4640: against the files-to-be-installed, see
4641: <code class="filename">mk/check/*.mk</code> for details.</p>
4642: <pre class="programlisting">
4643: .for dir in ${INSTALL_DIRS}
4644: cd ${WRKSRC} && cd ${dir} \
4645: && env ${INSTALL_ENV} ${MAKE_ENV} \
4646: ${MAKE_PROGRAM} ${MAKE_FLAGS} ${INSTALL_MAKE_FLAGS} \
4647: -f ${MAKE_FILE} ${INSTALL_TARGET}
1.184 rillig 4648: .endfor
1.1 dsieger 4649: </pre>
1.184 rillig 4650: <p>The variable's meanings are analogous to the ones in the
4651: <span class="emphasis"><em>build</em></span> phase.
4652: <code class="varname">INSTALL_DIRS</code> defaults to
4653: <code class="varname">BUILD_DIRS</code>. <code class="varname">INSTALL_TARGET</code>
4654: is <span class="quote">“<span class="quote">install</span>”</span> by default, plus
4655: <span class="quote">“<span class="quote">install.man</span>”</span> if <code class="varname">USE_IMAKE</code> is
4656: defined and <code class="varname">NO_INSTALL_MANPAGES</code> is not
4657: defined.</p>
4658: <p>In the <span class="emphasis"><em>install</em></span> phase, the following
4659: variables are useful. They are all variations of the
1.207 leot 4660: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that have the owner, group and
1.184 rillig 4661: permissions preset. <code class="varname">INSTALL</code> is the plain
4662: install command. The specialized variants, together with their
4663: intended use, are:</p>
4664: <div class="variablelist"><dl class="variablelist">
4665: <dt><span class="term"><code class="varname">INSTALL_PROGRAM_DIR</code></span></dt>
4666: <dd><p>directories that contain
4667: binaries</p></dd>
4668: <dt><span class="term"><code class="varname">INSTALL_SCRIPT_DIR</code></span></dt>
4669: <dd><p>directories that contain
4670: scripts</p></dd>
4671: <dt><span class="term"><code class="varname">INSTALL_LIB_DIR</code></span></dt>
4672: <dd><p>directories that contain shared and static
4673: libraries</p></dd>
4674: <dt><span class="term"><code class="varname">INSTALL_DATA_DIR</code></span></dt>
4675: <dd><p>directories that contain data
4676: files</p></dd>
4677: <dt><span class="term"><code class="varname">INSTALL_MAN_DIR</code></span></dt>
4678: <dd><p>directories that contain man
4679: pages</p></dd>
4680: <dt><span class="term"><code class="varname">INSTALL_GAME_DIR</code></span></dt>
4681: <dd><p>directories that contain data files for games
4682: </p></dd>
4683: <dt><span class="term"><code class="varname">INSTALL_PROGRAM</code></span></dt>
4684: <dd><p>binaries that can be stripped from debugging
4685: symbols</p></dd>
4686: <dt><span class="term"><code class="varname">INSTALL_SCRIPT</code></span></dt>
4687: <dd><p>binaries that cannot be
4688: stripped</p></dd>
4689: <dt><span class="term"><code class="varname">INSTALL_GAME</code></span></dt>
4690: <dd><p>game
4691: binaries</p></dd>
4692: <dt><span class="term"><code class="varname">INSTALL_LIB</code></span></dt>
4693: <dd><p>shared and static
4694: libraries</p></dd>
4695: <dt><span class="term"><code class="varname">INSTALL_DATA</code></span></dt>
4696: <dd><p>data files</p></dd>
4697: <dt><span class="term"><code class="varname">INSTALL_GAME_DATA</code></span></dt>
4698: <dd><p>data files for
4699: games</p></dd>
4700: <dt><span class="term"><code class="varname">INSTALL_MAN</code></span></dt>
4701: <dd><p>man pages</p></dd>
4702: </dl></div>
4703: <p>Some other variables are:</p>
4704: <div class="variablelist"><dl class="variablelist">
4705: <dt><span class="term"><code class="varname">INSTALL_UNSTRIPPED</code></span></dt>
1.207 leot 4706: <dd><p>If set to <code class="literal">yes</code>, do not run <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/strip.1"><span class="citerefentry"><span class="refentrytitle">strip</span>(1)</span></a>
1.184 rillig 4707: when installing binaries. Any debugging sections and symbols present in
4708: binaries will be preserved.
4709: </p></dd>
4710: <dt><span class="term"><code class="varname">INSTALLATION_DIRS</code></span></dt>
4711: <dd><p>A list of directories relative to
4712: <code class="varname">PREFIX</code> that are created by pkgsrc at the
4713: beginning of the <span class="emphasis"><em>install</em></span> phase.
4714: The package is supposed to create all needed directories itself
4715: before installing files to it and list all other directories here.
4716: </p></dd>
4717: </dl></div>
4718: <p>In the rare cases that a package shouldn't install anything,
4719: set <code class="varname">NO_INSTALL</code> to <span class="quote">“<span class="quote">yes</span>”</span>. This is
4720: mostly relevant for packages in the <code class="filename">regress</code>
4721: category.</p>
1.1 dsieger 4722: </div>
1.41 asau 4723: <div class="sect1">
1.1 dsieger 4724: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4725: <a name="build.package"></a>13.15. The <span class="emphasis"><em>package</em></span> phase</h2></div></div></div>
4726: <p>Once the install stage has completed, a binary package of
4727: the installed files can be built. These binary packages can be
4728: used for quick installation without previous compilation, e.g. by
4729: the <span class="command"><strong>make bin-install</strong></span> or by using
4730: <span class="command"><strong>pkg_add</strong></span>.</p>
4731: <p>By default, the binary packages are created in
4732: <code class="filename">${PACKAGES}/All</code> and symlinks are created in
4733: <code class="filename">${PACKAGES}/<em class="replaceable"><code>category</code></em></code>,
4734: one for each category in the <code class="varname">CATEGORIES</code>
4735: variable. <code class="varname">PACKAGES</code> defaults to
4736: <code class="filename">pkgsrc/packages</code>.</p>
1.1 dsieger 4737: </div>
1.41 asau 4738: <div class="sect1">
1.1 dsieger 4739: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4740: <a name="build.clean"></a>13.16. Cleaning up</h2></div></div></div>
4741: <p>Once you're finished with a package, you can clean the work
4742: directory by running <span class="command"><strong>make clean</strong></span>. If you want
4743: to clean the work directories of all dependencies too, use
4744: <span class="command"><strong>make clean-depends</strong></span>.</p>
1.1 dsieger 4745: </div>
1.41 asau 4746: <div class="sect1">
1.1 dsieger 4747: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 4748: <a name="build.helpful-targets"></a>13.17. Other helpful targets</h2></div></div></div>
1.41 asau 4749: <div class="variablelist"><dl class="variablelist">
1.184 rillig 4750: <dt><span class="term">pre/post-*</span></dt>
4751: <dd>
4752: <p>For any of the main targets described in the previous
4753: section (configure, build, install, etc.), two auxiliary
4754: targets exist with
4755: <span class="quote">“<span class="quote">pre-</span>”</span> and <span class="quote">“<span class="quote">post-</span>”</span> used as a
4756: prefix for the main target's name. These targets are
4757: invoked before and after the main target is called,
4758: allowing extra configuration or installation steps be
4759: performed from a package's Makefile, for example, which
4760: a program's configure script or install target
4761: omitted.</p>
4762: <p>About 5% of the pkgsrc packages define their custom
4763: post-extract target, another 5% define pre-configure, and 10%
4764: define post-install. The other pre/post-* targets are defined
4765: even less often.</p>
4766: </dd>
4767: <dt><span class="term">do-*</span></dt>
1.1 dsieger 4768: <dd>
1.184 rillig 4769: <p>Should one of the main targets do the wrong thing,
4770: and should there be no variable to fix this, you can
4771: redefine it with the do-* target. (Note that redefining
4772: the target itself instead of the do-* target is a bad
4773: idea, as the pre-* and post-* targets won't be called
4774: anymore, etc.)</p>
4775: <p>About 15% of the pkgsrc packages override the default
4776: do-install, the other do-* targets are overridden even less
4777: often.</p>
1.1 dsieger 4778: </dd>
1.184 rillig 4779: <dt><span class="term">reinstall</span></dt>
1.1 dsieger 4780: <dd>
1.184 rillig 4781: <p>If you did a <span class="command"><strong>make install</strong></span> and
4782: you noticed some file was not installed properly, you
4783: can repeat the installation with this target, which will
4784: ignore the <span class="quote">“<span class="quote">already installed</span>”</span> flag.</p>
4785: <p>This is the default value of
4786: <code class="varname">DEPENDS_TARGET</code> except in the case of
4787: <span class="command"><strong>make update</strong></span> and <span class="command"><strong>make
4788: package</strong></span>, where the defaults are
4789: <span class="quote">“<span class="quote">package</span>”</span> and <span class="quote">“<span class="quote">update</span>”</span>,
4790: respectively.</p>
1.1 dsieger 4791: </dd>
1.184 rillig 4792: <dt><span class="term">deinstall</span></dt>
4793: <dd>
1.207 leot 4794: <p>This target does a <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> in the
1.184 rillig 4795: current directory, effectively de-installing the
4796: package. The following variables can be used to tune the
4797: behaviour:</p>
4798: <div class="variablelist"><dl class="variablelist">
4799: <dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt>
1.207 leot 4800: <dd><p>Add a "-v" to the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
1.184 rillig 4801: <dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt>
4802: <dd><p>Remove all packages that require (depend on)
4803: the given package. This can be used to remove any
4804: packages that may have been pulled in by a given
4805: package, e.g. if <span class="command"><strong>make deinstall
4806: DEINSTALLDEPENDS=1</strong></span> is done in
4807: <code class="filename">pkgsrc/x11/kde</code>, this is
4808: likely to remove whole KDE. Works by adding
1.207 leot 4809: <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
1.184 rillig 4810: command line.</p></dd>
4811: </dl></div>
4812: </dd>
4813: <dt><span class="term">bin-install</span></dt>
4814: <dd><p>Install a binary package from local disk and via FTP
4815: from a list of sites (see the
4816: <code class="varname">BINPKG_SITES</code> variable), and do a
4817: <span class="command"><strong>make package</strong></span> if no binary package is
4818: available anywhere. The arguments given to
4819: <span class="command"><strong>pkg_add</strong></span> can be set via
4820: <code class="varname">BIN_INSTALL_FLAGS</code> e.g., to do verbose
4821: operation, etc.</p></dd>
4822: <dt><span class="term">install-clean</span></dt>
4823: <dd><p>This target removes the state files for the "install" and later
4824: phases so that the "install" target may be re-invoked. This can be
4825: used after editing the PLIST to install the package without
4826: rebuilding it.</p></dd>
4827: <dt><span class="term">build-clean</span></dt>
4828: <dd><p>This target removes the state files for the "build" and later
4829: phases so that the "build" target may be re-invoked.</p></dd>
4830: <dt><span class="term">update</span></dt>
4831: <dd>
4832: <p>This target causes the current package to be
4833: updated to the latest version. The package and all
4834: depending packages first get de-installed, then current
4835: versions of the corresponding packages get compiled and
4836: installed. This is similar to manually noting which
4837: packages are currently installed, then performing a
4838: series of <span class="command"><strong>make deinstall</strong></span> and
4839: <span class="command"><strong>make install</strong></span> (or whatever
4840: <code class="varname">UPDATE_TARGET</code> is set to) for these
4841: packages.</p>
4842: <p>You can use the <span class="quote">“<span class="quote">update</span>”</span> target to
4843: resume package updating in case a previous <span class="command"><strong>make
4844: update</strong></span> was interrupted for some reason.
4845: However, in this case, make sure you don't call
4846: <span class="command"><strong>make clean</strong></span> or otherwise remove the
4847: list of dependent packages in <code class="varname">WRKDIR</code>.
4848: Otherwise, you lose the ability to automatically update
4849: the current package along with the dependent packages
4850: you have installed.</p>
4851: <p>Resuming an interrupted <span class="command"><strong>make
4852: update</strong></span> will only work as long as the package
4853: tree remains unchanged. If the source code for one of
4854: the packages to be updated has been changed, resuming
4855: <span class="command"><strong>make update</strong></span> will most certainly
4856: fail!</p>
4857: <p>The following variables can be used either on the
4858: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
4859: alter the behaviour of <span class="command"><strong>make
4860: update</strong></span>:</p>
4861: <div class="variablelist"><dl class="variablelist">
4862: <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt>
4863: <dd><p>Install target to recursively use for the
4864: updated package and the dependent packages.
4865: Defaults to <code class="varname">DEPENDS_TARGET</code> if
4866: set, <span class="quote">“<span class="quote">install</span>”</span> otherwise for
4867: <span class="command"><strong>make update</strong></span>. Other good
4868: targets are <span class="quote">“<span class="quote">package</span>”</span> or
4869: <span class="quote">“<span class="quote">bin-install</span>”</span>. Do not set this to
4870: <span class="quote">“<span class="quote">update</span>”</span> or you will get stuck in an
4871: endless loop!</p></dd>
4872: <dt><span class="term"><code class="varname">NOCLEAN</code></span></dt>
4873: <dd><p>Don't clean up after updating. Useful if
4874: you want to leave the work sources of the updated
4875: packages around for inspection or other purposes.
4876: Be sure you eventually clean up the source tree
4877: (see the <span class="quote">“<span class="quote">clean-update</span>”</span> target below)
4878: or you may run into troubles with old source code
4879: still lying around on your next
4880: <span class="command"><strong>make</strong></span> or <span class="command"><strong>make
4881: update</strong></span>.</p></dd>
4882: <dt><span class="term"><code class="varname">REINSTALL</code></span></dt>
4883: <dd><p>Deinstall each package before installing
4884: (making <code class="varname">DEPENDS_TARGET</code>). This
4885: may be necessary if the
4886: <span class="quote">“<span class="quote">clean-update</span>”</span> target (see below) was
4887: called after interrupting a running <span class="command"><strong>make
4888: update</strong></span>.</p></dd>
4889: <dt><span class="term"><code class="varname">DEPENDS_TARGET</code></span></dt>
4890: <dd><p>Allows you to disable recursion and hardcode
4891: the target for packages. The default is
4892: <span class="quote">“<span class="quote">update</span>”</span> for the update target,
4893: facilitating a recursive update of prerequisite
4894: packages. Only set
4895: <code class="varname">DEPENDS_TARGET</code> if you want to
4896: disable recursive updates. Use
4897: <code class="varname">UPDATE_TARGET</code> instead to just
4898: set a specific target for each package to be
4899: installed during <span class="command"><strong>make update</strong></span>
4900: (see above).</p></dd>
4901: </dl></div>
4902: </dd>
4903: <dt><span class="term">clean-update</span></dt>
4904: <dd>
4905: <p>Clean the source tree for all packages that would
4906: get updated if <span class="command"><strong>make update</strong></span> was called
4907: from the current directory. This target should not be
4908: used if the current package (or any of its depending
4909: packages) have already been de-installed (e.g., after
4910: calling <span class="command"><strong>make update</strong></span>) or you may lose
4911: some packages you intended to update. As a rule of
4912: thumb: only use this target <span class="emphasis"><em>before</em></span>
4913: the first time you run <span class="command"><strong>make update</strong></span>
4914: and only if you have a dirty package tree (e.g., if you
4915: used <code class="varname">NOCLEAN</code>).</p>
4916: <p>If you are unsure about whether your tree is
4917: clean, you can either perform a <span class="command"><strong>make
4918: clean</strong></span> at the top of the tree, or use the
4919: following sequence of commands from the directory of the
4920: package you want to update (<span class="emphasis"><em>before</em></span>
4921: running <span class="command"><strong>make update</strong></span> for the first
4922: time, otherwise you lose all the packages you wanted to
4923: update!):</p>
4924: <pre class="screen">
4925: <code class="prompt">#</code> <strong class="userinput"><code>make clean-update</code></strong>
4926: <code class="prompt">#</code> <strong class="userinput"><code>make clean CLEANDEPENDS=YES</code></strong>
4927: <code class="prompt">#</code> <strong class="userinput"><code>make update</code></strong>
4928: </pre>
4929: <p>The following variables can be used either on the
4930: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of
4931: <span class="command"><strong>make clean-update</strong></span>:</p>
4932: <div class="variablelist"><dl class="variablelist">
4933: <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt>
4934: <dd><p>After <span class="command"><strong>make clean</strong></span>, do not
4935: reconstruct the list of directories to update for
4936: this package. Only use this if <span class="command"><strong>make
4937: update</strong></span> successfully installed all
4938: packages you wanted to update. Normally, this is
4939: done automatically on <span class="command"><strong>make
4940: update</strong></span>, but may have been suppressed by
4941: the <code class="varname">NOCLEAN</code> variable (see
4942: above).</p></dd>
4943: </dl></div>
4944: </dd>
4945: <dt><span class="term">replace</span></dt>
4946: <dd>
4947: <p>Update the installation of the current package. This
4948: differs from update in that it does not replace dependent
1.207 leot 4949: 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 4950: target to work.</p>
4951: <p><span class="emphasis"><em>Be careful when using this
4952: target!</em></span> There are no guarantees that dependent
4953: packages will still work, in particular they will most
4954: certainly break if you <span class="command"><strong>make replace</strong></span> a
4955: library package whose shared library major version changed
4956: between your installed version and the new one. For this
4957: reason, this target is not officially supported and only
4958: recommended for advanced users.</p>
4959: </dd>
4960: <dt><span class="term">info</span></dt>
1.207 leot 4961: <dd><p>This target invokes <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a> for the current
1.184 rillig 4962: package. You can use this to check which version of a
4963: package is installed.</p></dd>
4964: <dt><span class="term">index</span></dt>
4965: <dd>
4966: <p>This is a top-level command, i.e. it should be used in
4967: the <code class="filename">pkgsrc</code> directory. It creates a
4968: database of all packages in the local pkgsrc tree, including
4969: dependencies, comment, maintainer, and some other useful
4970: information. Individual entries are created by running
4971: <span class="command"><strong>make describe</strong></span> in the packages'
4972: directories. This index file is saved as
4973: <code class="filename">pkgsrc/INDEX</code>. It can be displayed in
4974: verbose format by running <span class="command"><strong>make
4975: print-index</strong></span>. You can search in it with
4976: <span class="command"><strong>make search
4977: key=<em class="replaceable"><code>something</code></em></strong></span>. You can
4978: extract a list of all packages that depend on a particular
4979: one by running <span class="command"><strong>make show-deps
4980: PKG=<em class="replaceable"><code>somepackage</code></em></strong></span>.</p>
4981: <p>Running this command takes a very long time, some
4982: hours even on fast machines!</p>
4983: </dd>
4984: <dt><span class="term">readme</span></dt>
4985: <dd>
4986: <p>This target generates a
1.199 nia 4987: <code class="filename">index.html</code> file, which can be
1.207 leot 4988: 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 4989: contain references to any packages which are in the
4990: <code class="varname">PACKAGES</code> directory on the local
4991: host. The generated files can be made to refer to URLs
4992: based on <code class="varname">FTP_PKG_URL_HOST</code> and
4993: <code class="varname">FTP_PKG_URL_DIR</code>. For example, if I
1.199 nia 4994: wanted to generate <code class="filename">index.html</code>
1.184 rillig 4995: files which pointed to binary packages on the local
4996: machine, in the directory
4997: <code class="filename">/usr/packages</code>, set
4998: <code class="varname">FTP_PKG_URL_HOST=file://localhost</code> and
4999: <code class="varname">FTP_PKG_URL_DIR=/usr/packages</code>. The
5000: <code class="varname">${PACKAGES}</code> directory and its
5001: subdirectories will be searched for all the binary
5002: packages.</p>
5003: <p>The target can be run at the toplevel or in category
5004: directories, in which case it descends recursively.</p>
5005: </dd>
5006: <dt><span class="term">readme-all</span></dt>
5007: <dd><p>This is a top-level command, run it in
5008: <code class="filename">pkgsrc</code>. Use this target to create a
5009: file <code class="filename">README-all.html</code> which contains a
5010: list of all packages currently available in the NetBSD
5011: Packages Collection, together with the category they belong
5012: to and a short description. This file is compiled from the
1.199 nia 5013: <code class="filename">pkgsrc/*/index.html</code> files, so be sure
1.184 rillig 5014: to run this <span class="emphasis"><em>after</em></span> a <span class="command"><strong>make
5015: readme</strong></span>.</p></dd>
5016: <dt><span class="term">cdrom-readme</span></dt>
5017: <dd><p>This is very much the same as the
5018: <span class="quote">“<span class="quote">readme</span>”</span> target (see above), but is to be
5019: used when generating a pkgsrc tree to be written to a
5020: CD-ROM. This target also produces
1.199 nia 5021: <code class="filename">index.html</code> files, and can be made
1.184 rillig 5022: to refer to URLs based on
5023: <code class="varname">CDROM_PKG_URL_HOST</code> and
5024: <code class="varname">CDROM_PKG_URL_DIR</code>.</p></dd>
5025: <dt><span class="term">show-distfiles</span></dt>
5026: <dd><p>This target shows which distfiles and patchfiles
5027: are needed to build the package
5028: (<code class="varname">ALLFILES</code>, which contains all
5029: <code class="varname">DISTFILES</code> and
5030: <code class="varname">PATCHFILES</code>, but not
5031: <code class="filename">patches/*</code>).</p></dd>
5032: <dt><span class="term">show-downlevel</span></dt>
5033: <dd><p>This target shows nothing if the package is not
5034: installed. If a version of this package is installed,
5035: but is not the version provided in this version of
5036: pkgsrc, then a warning message is displayed. This target
5037: can be used to show which of your installed packages are
5038: downlevel, and so the old versions can be deleted, and
5039: the current ones added.</p></dd>
5040: <dt><span class="term">show-pkgsrc-dir</span></dt>
5041: <dd><p>This target shows the directory in the pkgsrc
5042: hierarchy from which the package can be built and
5043: installed. This may not be the same directory as the one
5044: from which the package was installed. This target is
5045: intended to be used by people who may wish to upgrade
5046: many packages on a single host, and can be invoked from
5047: the top-level pkgsrc Makefile by using the
5048: <span class="quote">“<span class="quote">show-host-specific-pkgs</span>”</span> target.</p></dd>
5049: <dt><span class="term">show-installed-depends</span></dt>
5050: <dd><p>This target shows which installed packages match
5051: the current package's <code class="varname">DEPENDS</code>. Useful
5052: if out of date dependencies are causing build
5053: problems.</p></dd>
5054: <dt><span class="term">print-build-depends-list</span></dt>
5055: <dd><p>This target shows the list of packages that the current package
5056: depends on for building.</p></dd>
5057: <dt><span class="term">print-run-depends-list</span></dt>
5058: <dd><p>This target shows the list of packages that the current package
5059: depends on for running.</p></dd>
5060: <dt><span class="term">check-shlibs</span></dt>
5061: <dd><p>After a package is installed, check all its
5062: binaries and (on ELF platforms) shared libraries to see
5063: if they find the shared libs they need. Run by default
5064: 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>
5065: <dt><span class="term">print-PLIST</span></dt>
5066: <dd>
5067: <p>After a <span class="quote">“<span class="quote">make install</span>”</span> from a new or
5068: upgraded pkg, this prints out an attempt to generate a
5069: new <code class="filename">PLIST</code> from a <span class="command"><strong>find
5070: -newer work/.extract_done</strong></span>. An attempt is made
5071: to care for shared libs etc., but it is
5072: <span class="emphasis"><em>strongly</em></span> recommended to review the
5073: result before putting it into
5074: <code class="filename">PLIST</code>. On upgrades, it's useful to
5075: diff the output of this command against an already
5076: existing <code class="filename">PLIST</code> file.</p>
1.207 leot 5077: <p>If the package installs files via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/tar.1"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a> or
1.184 rillig 5078: other methods that don't update file access times, be
5079: sure to add these files manually to your
5080: <code class="filename">PLIST</code>, as the <span class="quote">“<span class="quote">find
5081: -newer</span>”</span> command used by this target won't catch
5082: them!</p>
5083: <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
5084: information on this target.</p>
5085: </dd>
5086: </dl></div>
5087: </div>
5088: </div>
5089: <div class="chapter">
5090: <div class="titlepage"><div><div><h2 class="title">
5091: <a name="creating"></a>Chapter 14. Creating a new pkgsrc package from scratch</h2></div></div></div>
5092: <div class="toc">
5093: <p><b>Table of Contents</b></p>
5094: <dl class="toc">
5095: <dt><span class="sect1"><a href="#creating.common">14.1. Common types of packages</a></span></dt>
5096: <dd><dl>
1.219 nia 5097: <dt><span class="sect2"><a href="#creating.python-module">14.1.1. Python modules and programs</a></span></dt>
5098: <dt><span class="sect2"><a href="#creating.R-package">14.1.2. R packages</a></span></dt>
5099: <dt><span class="sect2"><a href="#creating.TeX-package">14.1.3. TeXlive packages</a></span></dt>
1.184 rillig 5100: </dl></dd>
5101: <dt><span class="sect1"><a href="#creating.examples">14.2. Examples</a></span></dt>
5102: <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>
5103: </dl>
5104: </div>
5105: <p>When you find a package that is not yet in pkgsrc, you
5106: most likely have a URL from where you can download the source
5107: code. Starting with this URL, creating a package involves only a
5108: few steps.</p>
5109: <div class="procedure"><ol class="procedure" type="1">
5110: <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
5111: enable the basic quality checks.</p></li>
5112: <li class="step">
1.207 leot 5113: <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 5114: install the utilities <span class="command"><strong>url2pkg</strong></span>,
5115: <span class="command"><strong>pkglint</strong></span>, <span class="command"><strong>pkgvi</strong></span> and
5116: <span class="command"><strong>mkpatches</strong></span>:</p>
5117: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
5118: <code class="prompt">$</code> <strong class="userinput"><code>(cd meta-pkgs/pkg_developer && bmake update)</code></strong></pre>
5119: </li>
5120: <li class="step">
5121: <p>Choose one of the top-level directories as the category in
5122: which you want to place your package. You can also create a directory of
1.219 nia 5123: your own (maybe called <code class="filename">local</code>). Change into that
5124: category directory:</p>
5125: <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 5126: </li>
5127: <li class="step">
1.219 nia 5128: <p>Run the program <span class="command"><strong>url2pkg</strong></span>, passing as
5129: argument the URL of the distribution file (in most cases a
5130: <code class="filename">.tar.gz</code> file). This will download the distribution
5131: file and create the necessary files of the package, based on what's in
5132: the distribution file:</p>
1.184 rillig 5133: <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>
5134: </li>
5135: <li class="step">
5136: <p>Examine the extracted files to determine the dependencies of
5137: your package. Ideally, this is mentioned in some
5138: <code class="filename">README</code> file, but things may differ. For each of
5139: these dependencies, look where it exists in pkgsrc, and if there is a
5140: file called <code class="filename">buildlink3.mk</code> in that directory, add a
5141: line to your package <code class="filename">Makefile</code> which includes that
5142: file just before the last line. If the
5143: <code class="filename">buildlink3.mk</code> file does not exist, it must be
5144: created first. The <code class="filename">buildlink3.mk</code> file makes sure
5145: that the package's include files and libraries are provided.</p>
1.219 nia 5146: <p>If you just need binaries from a dependent package, add a
1.184 rillig 5147: <code class="varname">DEPENDS</code> line to the Makefile, which specifies the
5148: version of the dependency and where it can be found in pkgsrc. This line
5149: should be placed in the third paragraph. If the dependency is only
5150: needed for building the package, but not when using it, use
5151: <code class="varname">TOOL_DEPENDS</code> or <code class="varname">BUILD_DEPENDS</code>
5152: instead of <code class="varname">DEPENDS</code>.
5153: The difference between <code class="varname">TOOL_DEPENDS</code> and
5154: <code class="varname">BUILD_DEPENDS</code> occurs when cross-compiling:
5155: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
1.219 nia 5156: packages, i.e. packages for the platform where the package is built;
1.184 rillig 5157: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.219 nia 5158: packages, i.e. packages for the platform for which the package
5159: is built. There is also <code class="varname">TEST_DEPENDS</code>, which
5160: specifies a dependency used only for testing the resulting package
5161: built, using the upstream project's included test suite, on the native
5162: platform.
1.184 rillig 5163: Your package may then look like this:</p>
5164: <pre class="programlisting">
5165: [...]
5166:
5167: TOOL_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
5168: DEPENDS+= screen-[0-9]*:../../misc/screen
5169: DEPENDS+= screen>=4.0:../../misc/screen
5170:
5171: [...]
5172:
5173: .include "../../<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>package</code></em>/buildlink3.mk"
5174: .include "../../devel/glib2/buildlink3.mk"
5175: .include "../../mk/bsd.pkg.mk"
5176: </pre>
5177: </li>
5178: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need
5179: to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't
5180: know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint
5181: --explain</strong></span> or <span class="command"><strong>pkglint -e</strong></span>, which outputs
5182: additional explanations.</p></li>
5183: <li class="step"><p>In many cases the package is not yet ready to build. You can
5184: 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
5185: over there, you can hopefully continue here.</p></li>
5186: <li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working
5187: directory from the extracted files. Besides these files, a lot of cache
1.219 nia 5188: files and other system information have been saved in the working
5189: directory, which may have become outdated after you edited the
1.184 rillig 5190: <code class="filename">Makefile</code>.</p></li>
5191: <li class="step">
5192: <p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For
5193: 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 5194: <p>If the extracted files from the package need to be fixed, run
5195: multiple rounds of these commands:</p>
5196: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>bmake</code></strong>
1.184 rillig 5197: <code class="prompt">$</code> <strong class="userinput"><code>pkgvi ${WRKSRC}/some/file/that/does/not/compile</code></strong>
5198: <code class="prompt">$</code> <strong class="userinput"><code>mkpatches</code></strong>
1.219 nia 5199: <code class="prompt">$</code> <strong class="userinput"><code>bmake mps</code></strong>
5200: <code class="prompt">$</code> <strong class="userinput"><code>bmake clean</code></strong></pre>
1.184 rillig 5201: </li>
5202: <li class="step"><p>When the package builds fine, the next step is to install
5203: the package. Run <span class="command"><strong>bmake install</strong></span> and hope that
5204: everything works.</p></li>
5205: <li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which
5206: contains a list of the files that are installed by the package, is
5207: nearly empty. Run <span class="command"><strong>bmake print-PLIST
5208: >PLIST</strong></span> to generate a probably correct list. Check
5209: the file using your preferred text editor to see if the list of
5210: files looks plausible.</p></li>
5211: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated
5212: <code class="filename">PLIST</code> contains garbage or not.</p></li>
5213: <li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package
5214: had been registered in the database of installed files, but with an
5215: empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span>
5216: and <span class="command"><strong>bmake install</strong></span> again. Now the package is
5217: registered with the list of files from
5218: <code class="filename">PLIST</code>.</p></li>
5219: <li class="step"><p>Run <span class="command"><strong>bmake clean update</strong></span> to run everything
5220: from above again in a single step, making sure that the PLIST is correct
5221: and the whole package is created as intended.</p></li>
1.219 nia 5222: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see if there's anything
5223: left to do.</p></li>
1.184 rillig 5224: <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>
5225: </ol></div>
5226: <div class="sect1">
5227: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5228: <a name="creating.common"></a>14.1. Common types of packages</h2></div></div></div>
5229: <div class="sect2">
5230: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5231: <a name="creating.python-module"></a>14.1.1. Python modules and programs</h3></div></div></div>
1.184 rillig 5232: <p>Python modules and programs packages are easily created using a
5233: set of predefined variables.</p>
5234: <p>
5235: If some Python versions are not supported by the software, set the
5236: <code class="varname">PYTHON_VERSIONS_INCOMPATIBLE</code> variable to the Python versions
5237: that are not supported, e.g.
5238: </p>
5239: <pre class="programlisting">
5240: PYTHON_VERSIONS_INCOMPATIBLE= 27
5241: </pre>
5242: <p>
5243: If the packaged software is a Python module, include one of
1.215 wiz 5244: <code class="filename">../../lang/python/egg.mk</code> or
1.184 rillig 5245: <code class="filename">../../lang/python/extension.mk</code>.</p>
1.215 wiz 5246: <p>Most Python packages use setuptools (<span class="quote">“<span class="quote">eggs</span>”</span>).
1.184 rillig 5247: If the packaged software is using setuptools, you only need
5248: to include <span class="quote">“<span class="quote"><code class="filename">../../lang/python/egg.mk</code></span>”</span>.
1.215 wiz 5249: </p>
1.184 rillig 5250: <p>Either way, the package directory should be called
5251: <span class="quote">“<span class="quote">py-software</span>”</span> and <code class="varname">PKGNAME</code> should be set to
5252: <span class="quote">“<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>”</span>, e.g.
5253: </p>
5254: <pre class="programlisting">
5255: DISTNAME= foopymodule-1.2.10
5256: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
5257: </pre>
1.226 gutterid 5258: <p>
5259: For software in PyPi, the name should match what PyPi specifies for
5260: "pip install software".
5261: </p>
1.184 rillig 5262: <p>If it is an application, include
5263: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>”</span>.
5264: In order to correctly set the path to the Python interpreter, use the
5265: <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
5266: (paths relative to <code class="varname">WRKSRC</code>) that must be corrected.
5267: For example:
5268: </p>
5269: <pre class="programlisting">
5270: REPLACE_PYTHON= *.py
5271: </pre>
5272: <p>Some Python modules have separate distributions for Python-2.x
5273: and Python-3.x support. In pkgsrc this is handled by the
5274: <code class="filename">versioned_dependencies.mk</code> file. Set
5275: <code class="varname">PYTHON_VERSIONED_DEPENDENCIES</code> to the list of
5276: packages that should be depended upon and include
5277: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/versioned_dependencies.mk</code></span>”</span>,
5278: then the pkgsrc infrastructure will depend on the appropriate package
5279: version. For example:
5280: </p>
5281: <pre class="programlisting">
5282: PYTHON_VERSIONED_DEPENDENCIES=dialog
5283: </pre>
5284: <p>
5285: Look inside <code class="filename">versioned_dependencies.mk</code> for a list
5286: of supported packages.</p>
5287: </div>
5288: <div class="sect2">
5289: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5290: <a name="creating.R-package"></a>14.1.2. R packages</h3></div></div></div>
1.184 rillig 5291: <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>
5292: are handled automatically by <span class="command"><strong>R2pkg</strong></span>, which is
1.207 leot 5293: 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 5294: Individual packages (and optionally their dependencies) may be created
5295: and updated. R packages generally follow the same form, and most of
5296: the relevant information needed is contained in a
5297: <code class="filename">DESCRIPTION</code> file as part of each R package on
5298: <a class="ulink" href="https://cran.r-project.org/web/packages/available_packages_by_name.html" target="_top">CRAN</a>.
5299: Consequently, <span class="command"><strong>R2pkg</strong></span> downloads that information and
5300: creates or updates a package in the canonical form. The resulting
5301: package should be reviewed for correctness.</p>
5302: </div>
5303: <div class="sect2">
5304: <div class="titlepage"><div><div><h3 class="title">
1.219 nia 5305: <a name="creating.TeX-package"></a>14.1.3. TeXlive packages</h3></div></div></div>
1.184 rillig 5306: <p>TeXlive packages from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> are handled automatically by
1.207 leot 5307: <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 5308: <p>If the TeXlive package name is not known, it may be useful to
5309: search <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>. A
5310: <span class="quote">“<span class="quote">Contained in</span>”</span> field on the package page typically
5311: 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
5312: archive</a>.</p>
5313: <p>If the TeXlive package name is known, download the files from
5314: the <a class="ulink" href="https://www.ctan.org/tex-archive/systems/texlive/tlnet/archive" target="_top">TeXlive
5315: archive</a>. For package <code class="filename">foo</code>, you will need
5316: to download <code class="filename">foo.tar.xz</code>. Most TeXlive packages
5317: also have associated documentation packages, so download
5318: <code class="filename">foo.doc.tar.xz</code> at the same time. These files
5319: should be placed in the appropriate category directory, which is often
5320: but not always <code class="filename">print</code>. Then run the following
5321: command in the category directory.</p>
5322: <pre class="programlisting">
5323: texlive2pkg foo.tar.xz foo.doc.tar.xz
5324: </pre>
5325: <p>This will create two packages, <code class="filename">tex-foo</code> and
5326: <code class="filename">tex-foo-doc</code>. Be sure to check that both packages
5327: are correct.</p>
5328: <p>Finally, <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a>
5329: currently does not include version information in package filenames
5330: and changes their contents periodically when updates occur.
5331: Consequently, pkgsrc avoids downloading distfiles directly from <a class="ulink" href="https://www.ctan.org/" target="_top">CTAN</a> and instead relies on the
5332: pkgsrc archives. For each new or updated TeXlive package, e.g., the
5333: main one and the corresponding documentation, upload the distfiles
5334: with the following command in each package directory.</p>
5335: <pre class="programlisting">
5336: make upload-distfiles
5337: </pre>
5338: </div>
5339: </div>
5340: <div class="sect1">
5341: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5342: <a name="creating.examples"></a>14.2. Examples</h2></div></div></div>
5343: <div class="sect2">
5344: <div class="titlepage"><div><div><h3 class="title">
5345: <a name="creating.nvu"></a>14.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div>
5346: <div class="sect3">
5347: <div class="titlepage"><div><div><h4 class="title">
5348: <a name="creating.nvu.init"></a>14.2.1.1. The initial package</h4></div></div></div>
5349: <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
5350: that the <span class="quote">“<span class="quote">nvu</span>”</span> package has not yet been imported into
5351: pkgsrc. As the description says it has to do with the web, the obvious
5352: choice for the category is <span class="quote">“<span class="quote">www</span>”</span>.</p>
5353: <pre class="programlisting">
5354: <code class="prompt">$</code> mkdir www/nvu
5355: <code class="prompt">$</code> cd www/nvu
5356: </pre>
5357: <p>The web site says that the sources are available as a tar file, so
5358: I fed that URL to the <span class="command"><strong>url2pkg</strong></span> program:</p>
5359: <pre class="programlisting">
5360: <code class="prompt">$</code> url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5361: </pre>
5362: <p>My editor popped up, and I added a <code class="varname">PKGNAME</code> line
5363: below the <code class="varname">DISTNAME</code> line, as the package name should
5364: not have the word <span class="quote">“<span class="quote">sources</span>”</span> in it. I also filled in the
5365: <code class="varname">MAINTAINER</code>, <code class="varname">HOMEPAGE</code> and
5366: <code class="varname">COMMENT</code> fields. Then the package
5367: <code class="filename">Makefile</code> looked like that:</p>
5368: <pre class="programlisting">
5369: # $NetBSD $
5370: #
5371:
5372: DISTNAME= nvu-1.0-sources
5373: PKGNAME= nvu-1.0
5374: CATEGORIES= www
5375: MASTER_SITES= http://cvs.nvu.com/download/
5376: EXTRACT_SUFX= .tar.bz2
5377:
5378: MAINTAINER= rillig@NetBSD.org
5379: HOMEPAGE= http://cvs.nvu.com/
5380: COMMENT= Web Authoring System
5381:
5382: # url2pkg-marker (please do not remove this line.)
5383: .include "../../mk/bsd.pkg.mk"
5384: </pre>
5385: <p>On the first line of output above, an artificial space has been added between NetBSD and $,
5386: this is a workaround to prevent CVS expanding to the filename of the
5387: guide.</p>
5388: <p>Then, I quit the editor and watched pkgsrc downloading a large
5389: source archive:</p>
5390: <pre class="programlisting">
5391: url2pkg> Running "make makesum" ...
5392: => Required installed package digest>=20010302: digest-20060826 found
5393: => Fetching nvu-1.0-sources.tar.bz2
5394: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
5395: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
5396: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
5397: url2pkg> Running "make extract" ...
5398: => Required installed package digest>=20010302: digest-20060826 found
5399: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5400: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5401: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
5402: ===> Installing dependencies for nvu-1.0
5403: ===> Overriding tools for nvu-1.0
5404: ===> Extracting for nvu-1.0
5405: url2pkg> Adjusting the Makefile.
5406:
5407: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
5408:
5409: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
5410: </pre>
5411: </div>
5412: <div class="sect3">
5413: <div class="titlepage"><div><div><h4 class="title">
5414: <a name="creating.nvu.problems"></a>14.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div>
5415: <p>Now that the package has been extracted, let's see what's inside
5416: it. The package has a <code class="filename">README.txt</code>, but that only
5417: says something about mozilla, so it's probably useless for seeing what
5418: dependencies this package has. But since there is a GNU configure script
5419: in the package, let's hope that it will complain about everything it
5420: needs.</p>
5421: <pre class="programlisting">
5422: <code class="prompt">$</code> bmake
5423: => Required installed package digest>=20010302: digest-20060826 found
5424: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
5425: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
5426: ===> Patching for nvu-1.0
5427: ===> Creating toolchain wrappers for nvu-1.0
5428: ===> Configuring for nvu-1.0
5429: [...]
5430: configure: error: Perl 5.004 or higher is required.
5431: [...]
5432: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
5433: [...]
5434: </pre>
5435: <p>That worked quite well. So I opened the package Makefile in my
5436: editor, and since it already has a <code class="varname">USE_TOOLS</code> line, I
5437: just appended <span class="quote">“<span class="quote">perl</span>”</span> to it. Since the dependencies of the
5438: package have changed now, and since a perl wrapper is automatically
5439: installed in the <span class="quote">“<span class="quote">tools</span>”</span> phase, I need to build the package
5440: from scratch.</p>
5441: <pre class="programlisting">
5442: <code class="prompt">$</code> bmake clean
5443: ===> Cleaning for nvu-1.0
5444: <code class="prompt">$</code> bmake
5445: [...]
5446: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
5447: GNU Make. You will not be able to build Mozilla without GNU Make.
5448: [...]
5449: </pre>
5450: <p>So I added <span class="quote">“<span class="quote">gmake</span>”</span> to the
5451: <code class="varname">USE_TOOLS</code> line and tried again (from scratch).</p>
5452: <pre class="programlisting">
5453: [...]
5454: checking for GTK - version >= 1.2.0... no
5455: *** Could not run GTK test program, checking why...
5456: [...]
5457: </pre>
5458: <p>Now to the other dependencies. The first question is: Where is the
5459: GTK package hidden in pkgsrc?</p>
5460: <pre class="programlisting">
5461: <code class="prompt">$</code> echo ../../*/gtk*
5462: [many packages ...]
5463: <code class="prompt">$</code> echo ../../*/gtk
5464: ../../x11/gtk
5465: <code class="prompt">$</code> echo ../../*/gtk2
5466: ../../x11/gtk2
5467: <code class="prompt">$</code> echo ../../*/gtk2/bui*
5468: ../../x11/gtk2/buildlink3.mk
5469: </pre>
5470: <p>The first try was definitely too broad. The second one had exactly
5471: one result, which is very good. But there is one pitfall with GNOME
5472: packages. Before GNOME 2 had been released, there were already many
5473: GNOME 1 packages in pkgsrc. To be able to continue to use these
5474: packages, the GNOME 2 packages were imported as separate packages, and
5475: their names usually have a <span class="quote">“<span class="quote">2</span>”</span> appended. So I checked
5476: whether this was the case here, and indeed it was.</p>
5477: <p>Since the GTK2 package has a <code class="filename">buildlink3.mk</code>
5478: file, adding the dependency is very easy. I just inserted an
5479: <code class="literal">.include</code> line before the last line of the package
5480: <code class="filename">Makefile</code>, so that it now looks like this:</p>
5481: <pre class="programlisting">
5482: [...]
5483: .include "../../x11/gtk2/buildlink3.mk"
5484: .include "../../mk/bsd.pkg.mk
5485: </pre>
5486: <p>After another <span class="command"><strong>bmake clean && bmake</strong></span>, the answer
5487: was:</p>
1.1 dsieger 5488: <pre class="programlisting">
1.184 rillig 5489: [...]
5490: checking for gtk-config... /home/roland/pkg/bin/gtk-config
5491: checking for GTK - version >= 1.2.0... no
5492: *** Could not run GTK test program, checking why...
5493: *** The test program failed to compile or link. See the file config.log for the
5494: *** exact error that occured. This usually means GTK was incorrectly installed
5495: *** or that you have moved GTK since it was installed. In the latter case, you
5496: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
5497: configure: error: Test for GTK failed.
5498: [...]
1.111 sevan 5499: </pre>
1.184 rillig 5500: <p>In this particular case, the assumption that <span class="quote">“<span class="quote">every package
5501: prefers GNOME 2</span>”</span> had been wrong. The first of the lines above
5502: told me that this package really wanted to have the GNOME 1 version of
5503: GTK. If the package had looked for GTK2, it would have looked for
5504: <span class="command"><strong>pkg-config</strong></span> instead of <span class="command"><strong>gtk-config</strong></span>.
5505: So I changed the <code class="literal">x11/gtk2</code> to
5506: <code class="literal">x11/gtk</code> in the package <code class="filename">Makefile</code>,
5507: and tried again.</p>
1.18 snj 5508: <pre class="programlisting">
1.184 rillig 5509: [...]
5510: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
5511: In file included from xpidl.c:42:
5512: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
5513: In file included from xpidl.c:42:
5514: xpidl.h:132: error: parse error before "IDL_ns"
5515: [...]
1.111 sevan 5516: </pre>
1.184 rillig 5517: <p>The package still does not find all of its dependencies. Now the
5518: question is: Which package provides the
5519: <code class="filename">libIDL/IDL.h</code> header file?</p>
1.18 snj 5520: <pre class="programlisting">
1.184 rillig 5521: <code class="prompt">$</code> echo ../../*/*idl*
5522: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
5523: <code class="prompt">$</code> echo ../../*/*IDL*
5524: ../../net/libIDL
1.111 sevan 5525: </pre>
1.184 rillig 5526: <p>Let's take the one from the second try. So I included the
5527: <code class="filename">../../net/libIDL/buildlink3.mk</code> file and tried
5528: again. But the error didn't change. After digging through some of the
5529: code, I concluded that the build process of the package was broken and
5530: couldn't have ever worked, but since the Mozilla source tree is quite
5531: large, I didn't want to fix it. So I added the following to the package
5532: <code class="filename">Makefile</code> and tried again:</p>
1.86 wiz 5533: <pre class="programlisting">
1.184 rillig 5534: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
5535: BUILDLINK_TRANSFORM+= l:IDL:IDL-2
1.111 sevan 5536: </pre>
1.184 rillig 5537: <p>The latter line is needed because the package expects the library
5538: <code class="filename">libIDL.so</code>, but only
5539: <code class="filename">libIDL-2.so</code> is available. So I told the compiler
5540: wrapper to rewrite that on the fly.</p>
5541: <p>The next problem was related to a recent change of the FreeType
1.207 leot 5542: 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 5543: which patch files were relevant for this issue and copied them to the
5544: <code class="filename">patches</code> directory. Then I retried, fixed the
5545: patches so that they applied cleanly and retried again. This time,
5546: everything worked.</p>
1.86 wiz 5547: </div>
1.184 rillig 5548: <div class="sect3">
5549: <div class="titlepage"><div><div><h4 class="title">
5550: <a name="creating.nvu.inst"></a>14.2.1.3. Installing the package</h4></div></div></div>
1.1 dsieger 5551: <pre class="programlisting">
1.184 rillig 5552: <code class="prompt">$</code> bmake CHECK_FILES=no install
5553: [...]
5554: <code class="prompt">$</code> bmake print-PLIST >PLIST
5555: <code class="prompt">$</code> bmake deinstall
5556: <code class="prompt">$</code> bmake install
1.111 sevan 5557: </pre>
1.184 rillig 5558: </div>
5559: </div>
1.1 dsieger 5560: </div>
5561: </div>
1.41 asau 5562: <div class="chapter">
1.1 dsieger 5563: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 5564: <a name="makefile"></a>Chapter 15. Programming in <code class="filename">Makefile</code>s</h2></div></div></div>
1.1 dsieger 5565: <div class="toc">
5566: <p><b>Table of Contents</b></p>
1.100 leot 5567: <dl class="toc">
1.184 rillig 5568: <dt><span class="sect1"><a href="#makefile.style">15.1. Caveats</a></span></dt>
5569: <dt><span class="sect1"><a href="#makefile.variables">15.2. <code class="filename">Makefile</code> variables</a></span></dt>
5570: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">15.2.1. Naming conventions</a></span></dt></dl></dd>
5571: <dt><span class="sect1"><a href="#makefile.code">15.3. Code snippets</a></span></dt>
5572: <dd><dl>
5573: <dt><span class="sect2"><a href="#adding-to-list">15.3.1. Adding things to a list</a></span></dt>
5574: <dt><span class="sect2"><a href="#echo-literal">15.3.2. Echoing a string exactly as-is</a></span></dt>
5575: <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>
5576: <dt><span class="sect2"><a href="#empty-variables">15.3.4. Handling possibly empty variables</a></span></dt>
1.229 gutterid 5577: <dt><span class="sect2"><a href="#makefile.yesno">15.3.5. Testing yes/no variables in conditions</a></span></dt>
1.1 dsieger 5578: </dl></dd>
5579: </dl>
5580: </div>
1.184 rillig 5581: <p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments,
5582: each of which forms a well-defined part of the pkgsrc system. Using
1.207 leot 5583: the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a programming language for a big system
1.184 rillig 5584: like pkgsrc requires some discipline to keep the code correct and
5585: understandable.</p>
5586: <p>The basic ingredients for <code class="filename">Makefile</code>
5587: programming are variables and shell
5588: commands. Among these shell commands may even be more complex ones
1.207 leot 5589: like <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/awk.1"><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make sure that every shell command runs
1.184 rillig 5590: as intended it is necessary to quote all variables correctly when they
5591: are used.</p>
5592: <p>This chapter describes some patterns that appear quite often in
5593: <code class="filename">Makefile</code>s, including the pitfalls that come along
5594: with them.</p>
1.41 asau 5595: <div class="sect1">
1.1 dsieger 5596: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 5597: <a name="makefile.style"></a>15.1. Caveats</h2></div></div></div>
5598: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
5599: <p>When you are creating a file as a
5600: target of a rule, always write the data to a temporary file first
5601: and finally rename that file. Otherwise there might occur an error
5602: in the middle of generating the file, and when the user runs
1.207 leot 5603: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> for the second time, the file exists and will not be
1.184 rillig 5604: regenerated properly. Example:</p>
1.1 dsieger 5605: <pre class="programlisting">
1.184 rillig 5606: wrong:
5607: @echo "line 1" > ${.TARGET}
5608: @echo "line 2" >> ${.TARGET}
5609: @false
5610:
5611: correct:
5612: @echo "line 1" > ${.TARGET}.tmp
5613: @echo "line 2" >> ${.TARGET}.tmp
5614: @false
5615: @mv ${.TARGET}.tmp ${.TARGET}
1.1 dsieger 5616: </pre>
1.184 rillig 5617: <p>When you run <span class="command"><strong>make wrong</strong></span> twice, the file
5618: <code class="filename">wrong</code> will exist, although there was an error
5619: message in the first run. On the other hand, running <span class="command"><strong>make
5620: correct</strong></span> gives an error message twice, as expected.</p>
1.207 leot 5621: <p>You might remember that <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> sometimes removes
1.184 rillig 5622: <code class="literal">${.TARGET}</code> in case of error, but this only
5623: happens when it is interrupted, for example by pressing
5624: <code class="literal">Ctrl+C</code>. This does <span class="emphasis"><em>not</em></span> happen
1.207 leot 5625: when one of the commands fails (like <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/false.1"><span class="citerefentry"><span class="refentrytitle">false</span>(1)</span></a> above).</p>
1.184 rillig 5626: </li></ul></div>
5627: </div>
5628: <div class="sect1">
5629: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5630: <a name="makefile.variables"></a>15.2. <code class="filename">Makefile</code> variables</h2></div></div></div>
5631: <p><code class="filename">Makefile</code> variables contain strings that
5632: can be processed using the five operators <code class="code">=</code>,
5633: <code class="code">+=</code>, <code class="code">?=</code>, <code class="code">:=</code> and
1.207 leot 5634: <code class="code">!=</code>, which are described in the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man
1.184 rillig 5635: page.</p>
5636: <p>When a variable's value is parsed from a
5637: <code class="filename">Makefile</code>, the hash character <code class="code">#</code> and
5638: the backslash character <code class="code">\</code> are handled specially. If a
5639: backslash is the last character in a line, that backslash is removed
5640: from the line and the line continues with the next line of the file.</p>
5641: <p>The <code class="code">#</code> character starts a comment that reaches
5642: until the end of the line. To get an actual <code class="code">#</code> character,
5643: such as in a URL, write <code class="code">\#</code> instead.</p>
5644: <p>The evaluation of variables either happens immediately or lazy.
5645: It happens immediately when the variable occurs on the right-hand
5646: side of the <code class="code">:=</code> or the <code class="code">!=</code> operator, in a
5647: <code class="varname">.if</code> condition or a <code class="varname">.for</code> loop.
5648: In the other cases, it is evaluated lazily.</p>
5649: <p>Some of the modifiers split the string into words and then
5650: operate on the words, others operate on the string as a whole. When a
5651: string is split into words, double quotes and single quotes are
1.207 leot 5652: interpreted as delimiters, just like in <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/sh.1"><span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span></a>.</p>
1.184 rillig 5653: <div class="sect2">
5654: <div class="titlepage"><div><div><h3 class="title">
5655: <a name="makefile.variables.names"></a>15.2.1. Naming conventions</h3></div></div></div>
5656: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
5657: <li class="listitem"><p>All variable names starting with an underscore
5658: are reserved for use by the pkgsrc infrastructure. They shall
5659: not be used by packages.</p></li>
5660: <li class="listitem"><p>In <span class="command"><strong>.for</strong></span> loops you should use
5661: lowercase variable names for the iteration
5662: variables.</p></li>
5663: <li class="listitem"><p>All list variables should have a plural name,
5664: such as <code class="varname">PKG_OPTIONS</code> or
5665: <code class="varname">DISTFILES</code>.</p></li>
5666: </ul></div>
5667: </div>
5668: </div>
5669: <div class="sect1">
5670: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5671: <a name="makefile.code"></a>15.3. Code snippets</h2></div></div></div>
5672: <div class="sect2">
5673: <div class="titlepage"><div><div><h3 class="title">
5674: <a name="adding-to-list"></a>15.3.1. Adding things to a list</h3></div></div></div>
5675: <p>When adding a string that possibly contains whitespace or quotes to
5676: a list (example 1), it must be quoted using the <code class="code">:Q</code>
5677: modifier.</p>
5678: <p>When adding another list to a list (example 2), it must not be
5679: quoted, since its elements are already quoted.</p>
1.1 dsieger 5680: <pre class="programlisting">
1.184 rillig 5681: STRING= foo * bar `date`
5682: LIST= # empty
5683: ANOTHER_LIST= a=b c=d
5684:
5685: LIST+= ${STRING:Q} # 1
5686: LIST+= ${ANOTHER_LIST} # 2
1.1 dsieger 5687: </pre>
1.184 rillig 5688: </div>
5689: <div class="sect2">
5690: <div class="titlepage"><div><div><h3 class="title">
5691: <a name="echo-literal"></a>15.3.2. Echoing a string exactly as-is</h3></div></div></div>
5692: <p>Echoing a string containing special characters needs special
5693: work.</p>
1.1 dsieger 5694: <pre class="programlisting">
1.184 rillig 5695: STRING= foo bar < > * `date` $$HOME ' "
5696: EXAMPLE_ENV= string=${STRING:Q} x=multiple\ quoted\ words
5697:
5698: all:
5699: echo ${STRING} # 1
5700: echo ${STRING:Q} # 2
5701: printf '%s\n' ${STRING:Q}'' # 3
5702: env ${EXAMPLE_ENV} sh -c 'echo "$$string"; echo "$$x"' # 4
1.1 dsieger 5703: </pre>
1.184 rillig 5704: <p>Example 1 leads to a syntax error in the shell, as the characters
5705: are just copied.</p>
5706: <p>Example 2 quotes the string so that the shell interprets it
5707: correctly. But the echo command may additionally interpret strings with a
5708: leading dash or those containing backslashes.</p>
1.207 leot 5709: <p>Example 3 can handle arbitrary strings, since <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> only
1.184 rillig 5710: interprets the format string, but not the next argument. The trailing
5711: single quotes handle the case when the string is empty. In that case, the
5712: :Q modifier would result in an empty string too, which would then be
1.207 leot 5713: skipped by the shell. For <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/printf.1"><span class="citerefentry"><span class="refentrytitle">printf</span>(1)</span></a> this doesn't make a difference,
1.184 rillig 5714: but other programs may care.</p>
5715: <p>In example 4, the <code class="varname">EXAMPLE_ENV</code> does not
5716: need to be quoted because the quoting has already been done
5717: when adding elements to the list.</p>
1.1 dsieger 5718: </div>
1.41 asau 5719: <div class="sect2">
1.1 dsieger 5720: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 5721: <a name="cflags-gnu-configure"></a>15.3.3. Passing <code class="varname">CFLAGS</code> to GNU configure scripts</h3></div></div></div>
5722: <p>When passing <code class="varname">CFLAGS</code> or similar variables to a
5723: GNU-style configure script (especially those that call other configure
5724: scripts), it must not have leading or trailing whitespace, since
5725: otherwise the configure script gets confused. To trim leading and
5726: trailing whitespace, use the <code class="code">:M</code> modifier, as in the
5727: following example:</p>
1.1 dsieger 5728: <pre class="programlisting">
1.184 rillig 5729: CPPFLAGS= # empty
5730: CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX}\"
5731: CPPFLAGS+= ${MY_CPPFLAGS}
1.1 dsieger 5732:
1.184 rillig 5733: CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
1.1 dsieger 5734:
1.184 rillig 5735: all:
5736: echo x${CPPFLAGS:Q}x # leading and trailing whitespace
5737: echo x${CONFIGURE_ARGS:Q}x # properly trimmed
5738: </pre>
5739: <p>In this example, <code class="varname">CPPFLAGS</code> has both leading and
5740: trailing whitespace because the <code class="code">+=</code> operator always adds a
5741: space.</p>
5742: </div>
5743: <div class="sect2">
5744: <div class="titlepage"><div><div><h3 class="title">
5745: <a name="empty-variables"></a>15.3.4. Handling possibly empty variables</h3></div></div></div>
5746: <p>When a possibly empty variable is used in a shell program, it may
5747: lead to a syntax error.</p>
5748: <pre class="programlisting">
5749: EGFILES= # empty
1.1 dsieger 5750:
1.184 rillig 5751: install-examples: # produces a syntax error in the shell
5752: for egfile in ${EGFILES}; do \
5753: echo "Installing $$egfile"; \
5754: done
5755: </pre>
5756: <p>The shell only sees the text <code class="code">for egfile in ; do</code>, since
1.207 leot 5757: <code class="code">${EGFILES}</code> is replaced with an empty string by <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.
1.184 rillig 5758: To fix this syntax error, use one of the snippets below.</p>
5759: <pre class="programlisting">
1.229 gutterid 5760: EGFILES= # empty
1.1 dsieger 5761:
1.184 rillig 5762: install-examples:
5763: for egfile in ${EGFILES} ""; do \
5764: [ -n "$$egfile" ] || continue; \
5765: echo "Installing $$egfile"; \
5766: done
5767: </pre>
5768: <p>In this case, an empty string is appended to the iteration list (to
5769: prevent the syntax error) and filtered out later.</p>
5770: <pre class="programlisting">
5771: EGFILES= # empty
1.1 dsieger 5772:
1.184 rillig 5773: install-examples:
5774: .for egfile in ${EGFILES}
5775: echo "Installing ${egfile}"
5776: .endfor
1.1 dsieger 5777: </pre>
1.184 rillig 5778: <p>If one of the filenames contains special characters, it should be
5779: enclosed in single or double quotes.</p>
5780: <p>To have a shell command test whether a make variable is empty, use
5781: the following code: <code class="code">${TEST} -z ${POSSIBLY_EMPTY:Q}""</code>.</p>
5782: </div>
1.229 gutterid 5783: <div class="sect2">
5784: <div class="titlepage"><div><div><h3 class="title">
5785: <a name="makefile.yesno"></a>15.3.5. Testing yes/no variables in conditions</h3></div></div></div>
5786: <p>When a variable can have the values <code class="literal">yes</code> or
5787: <code class="literal">no</code>, use the following pattern to test the variable:</p>
5788: <pre class="programlisting">
5789: .if ${VAR:U:tl} == "yes"
5790: # do something
5791: .endif
5792: </pre>
5793: <p>The <code class="literal">:U</code> modifier is only necessary if the variable
5794: can be undefined. If the variable is guaranteed to be defined, the
5795: <code class="literal">:U</code> can be omitted.</p>
5796: <p>The <code class="literal">:tl</code> modifier converts the variable value to
5797: lowercase, allowing for the values <code class="literal">yes</code>,
5798: <code class="literal">Yes</code>, <code class="literal">YES</code>.</p>
5799: </div>
1.184 rillig 5800: </div>
5801: </div>
5802: <div class="chapter">
5803: <div class="titlepage"><div><div><h2 class="title">
5804: <a name="options"></a>Chapter 16. Options handling</h2></div></div></div>
5805: <div class="toc">
5806: <p><b>Table of Contents</b></p>
5807: <dl class="toc">
5808: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
5809: <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>
5810: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
5811: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
5812: </dl>
1.1 dsieger 5813: </div>
1.184 rillig 5814: <p>Many packages have the ability to be built to support different
5815: sets of features. <code class="filename">bsd.options.mk</code> is a framework
5816: in pkgsrc that provides generic handling of those options that
5817: determine different ways in which the packages can be built. It's
5818: possible for the user to specify exactly which sets of options will be
5819: built into a package or to allow a set of global default options
5820: apply.</p>
5821: <p>There are two broad classes of behaviors that one might want to
5822: control via options. One is whether some particular feature is
5823: enabled in a program that will be built anyway, often by including or
5824: not including a dependency on some other package. The other is
5825: whether or not an additional program will be built as part of the
5826: package. Generally, it is better to make a split package for such
5827: additional programs instead of using options, because it enables
5828: binary packages to be built which can then be added separately. For
5829: example, the foo package might have minimal dependencies (those
5830: packages without which foo doesn't make sense), and then the foo-gfoo
5831: package might include the GTK frontend program gfoo. This is better
5832: than including a gtk option to foo that adds gfoo, because either that
5833: option is default, in which case binary users can't get foo without
5834: gfoo, or not default, in which case they can't get gfoo. With split
5835: packages, they can install foo without having GTK, and later decide to
5836: install gfoo (pulling in GTK at that time). This is an advantage to
5837: source users too, avoiding the need for rebuilds.</p>
5838: <p>Plugins with widely varying dependencies should usually be split
5839: instead of options.</p>
5840: <p>It is often more work to maintain split packages, especially if
5841: the upstream package does not support this. The decision of split
5842: vs. option should be made based on the likelihood that users will want
5843: or object to the various pieces, the size of the dependencies that are
5844: included, and the amount of work.</p>
5845: <p>A further consideration is licensing. Non-free parts, or parts
5846: that depend on non-free dependencies (especially plugins) should
5847: almost always be split if feasible.</p>
5848: <div class="sect1">
5849: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5850: <a name="global-default-options"></a>16.1. Global default options</h2></div></div></div>
5851: <p>Global default options are listed in
5852: <code class="varname">PKG_DEFAULT_OPTIONS</code>, which is a list of the options
5853: that should be built into every package if that option is supported.
5854: This variable should be set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 5855: </div>
1.41 asau 5856: <div class="sect1">
1.1 dsieger 5857: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 5858: <a name="converting-to-options"></a>16.2. Converting packages to use <code class="filename">bsd.options.mk</code>
5859: </h2></div></div></div>
5860: <p>The following example shows how
5861: <code class="filename">bsd.options.mk</code> should be used
5862: by the hypothetical ``wibble'' package, either in the package
5863: <code class="filename">Makefile</code>, or in a file,
5864: e.g. <code class="filename">options.mk</code>, that is included by the
5865: main package <code class="filename">Makefile</code>.</p>
1.1 dsieger 5866: <pre class="programlisting">
1.184 rillig 5867: PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
5868: PKG_SUPPORTED_OPTIONS= wibble-foo ldap
5869: PKG_OPTIONS_OPTIONAL_GROUPS= database
5870: PKG_OPTIONS_GROUP.database= mysql pgsql
5871: PKG_SUGGESTED_OPTIONS= wibble-foo
5872: PKG_OPTIONS_LEGACY_VARS+= WIBBLE_USE_OPENLDAP:ldap
5873: PKG_OPTIONS_LEGACY_OPTS+= foo:wibble-foo
5874:
5875: .include "../../mk/bsd.prefs.mk"
5876:
5877: # this package was previously named wibble2
5878: .if defined(PKG_OPTIONS.wibble2)
5879: PKG_LEGACY_OPTIONS+= ${PKG_OPTIONS.wibble2}
5880: PKG_OPTIONS_DEPRECATED_WARNINGS+= \
5881: "Deprecated variable PKG_OPTIONS.wibble2 used, use ${PKG_OPTIONS_VAR} instead."
5882: .endif
5883:
5884: .include "../../mk/bsd.options.mk"
5885:
5886: # Package-specific option-handling
1.1 dsieger 5887:
1.184 rillig 5888: ###
5889: ### FOO support
5890: ###
5891: .if !empty(PKG_OPTIONS:Mwibble-foo)
5892: CONFIGURE_ARGS+= --enable-foo
5893: .endif
1.1 dsieger 5894:
1.184 rillig 5895: ###
5896: ### LDAP support
5897: ###
5898: .if !empty(PKG_OPTIONS:Mldap)
5899: . include "../../databases/openldap-client/buildlink3.mk"
5900: CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap-client}
5901: .endif
1.1 dsieger 5902:
1.184 rillig 5903: ###
5904: ### database support
5905: ###
5906: .if !empty(PKG_OPTIONS:Mmysql)
5907: . include "../../mk/mysql.buildlink3.mk"
5908: .endif
5909: .if !empty(PKG_OPTIONS:Mpgsql)
5910: . include "../../mk/pgsql.buildlink3.mk"
5911: .endif
5912: </pre>
5913: <p>The first section contains the information about which build
5914: options are supported by the package, and any default options settings
5915: if needed.</p>
5916: <div class="orderedlist"><ol class="orderedlist" type="1">
5917: <li class="listitem"><p><code class="varname">PKG_OPTIONS_VAR</code> is the name of the
1.207 leot 5918: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> variable that the user can set to override the default
1.184 rillig 5919: options. It should be set to
5920: PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em>. Do not set it to
5921: PKG_OPTIONS.${PKGBASE}, since <code class="varname">PKGBASE</code> is not defined
5922: at the point where the options are processed.</p></li>
5923: <li class="listitem"><p><code class="varname">PKG_SUPPORTED_OPTIONS</code> is a list of
5924: build options supported by the package.</p></li>
5925: <li class="listitem"><p><code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code> is a
5926: list of names of groups of mutually exclusive options. The options in
5927: each group are listed in
5928: <code class="varname">PKG_OPTIONS_GROUP.<em class="replaceable"><code>groupname</code></em></code>.
5929: The most specific setting of any option from the group takes
5930: precedence over all other options in the group. Options from the
5931: groups will be automatically added to
5932: <code class="varname">PKG_SUPPORTED_OPTIONS</code>.</p></li>
5933: <li class="listitem"><p><code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> is like
5934: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, but building the
5935: packages will fail if no option from the group is
5936: selected.</p></li>
5937: <li class="listitem"><p><code class="varname">PKG_OPTIONS_NONEMPTY_SETS</code> is a list
5938: of names of sets of options. At least one option from each set must
5939: be selected. The options in each set are listed in
5940: <code class="varname">PKG_OPTIONS_SET.<em class="replaceable"><code>setname</code></em></code>.
5941: Options from the sets will be automatically added to
5942: <code class="varname">PKG_SUPPORTED_OPTIONS</code>. Building the package will
5943: fail if no option from the set is selected.</p></li>
5944: <li class="listitem"><p><code class="varname">PKG_SUGGESTED_OPTIONS</code> is a list of
5945: build options which are enabled by default.</p></li>
5946: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_VARS</code> is a list
5947: of
5948: <span class="quote">“<span class="quote"><em class="replaceable"><code>USE_VARIABLE</code></em>:<em class="replaceable"><code>option</code></em></span>”</span>
5949: pairs that map legacy <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> variables to
5950: their option counterparts. Pairs should be added with
5951: <span class="quote">“<span class="quote">+=</span>”</span> to keep the listing of global legacy variables. A
5952: warning will be issued if the user uses a legacy
5953: variable.</p></li>
5954: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> is a list
5955: of
5956: <span class="quote">“<span class="quote"><em class="replaceable"><code>old-option</code></em>:<em class="replaceable"><code>new-option</code></em></span>”</span>
5957: pairs that map options that have been renamed to their new
5958: counterparts. Pairs should be added with <span class="quote">“<span class="quote">+=</span>”</span> to keep
5959: the listing of global legacy options. A warning will be issued if
5960: the user uses a legacy option.</p></li>
5961: <li class="listitem"><p><code class="varname">PKG_LEGACY_OPTIONS</code> is a list of
5962: options implied by deprecated variables used. This can be used for
5963: cases that neither <code class="varname">PKG_OPTIONS_LEGACY_VARS</code> nor
5964: <code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> can handle, e. g. when
5965: <code class="varname">PKG_OPTIONS_VAR</code> is renamed.</p></li>
5966: <li class="listitem"><p><code class="varname">PKG_OPTIONS_DEPRECATED_WARNINGS</code> is
5967: a list of warnings about deprecated variables or options used, and
5968: what to use instead.</p></li>
5969: </ol></div>
5970: <p>A package should never modify
5971: <code class="varname">PKG_DEFAULT_OPTIONS</code> or the variable named in
5972: <code class="varname">PKG_OPTIONS_VAR</code>. These are strictly user-settable.
5973: To suggest a default set of options, use
5974: <code class="varname">PKG_SUGGESTED_OPTIONS</code>.</p>
5975: <p><code class="varname">PKG_OPTIONS_VAR</code> must be defined before
5976: including <code class="filename">bsd.options.mk</code>. If none of
5977: <code class="varname">PKG_SUPPORTED_OPTIONS</code>,
5978: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, and
5979: <code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> are defined (as can
5980: happen with platform-specific options if none of them is supported on
5981: the current platform), <code class="varname">PKG_OPTIONS</code> is set to the
5982: empty list and the package is otherwise treated as not using the
5983: options framework.</p>
5984: <p>After the inclusion of <code class="filename">bsd.options.mk</code>, the
5985: variable <code class="varname">PKG_OPTIONS</code> contains the list of selected
5986: build options, properly filtered to remove unsupported and duplicate
5987: options.</p>
5988: <p>The remaining sections contain the logic that is specific to
5989: each option. The correct way to check for an option is to check
5990: whether it is listed in <code class="varname">PKG_OPTIONS</code>:</p>
5991: <pre class="programlisting">
5992: .if !empty(PKG_OPTIONS:M<em class="replaceable"><code>option</code></em>)
1.1 dsieger 5993: </pre>
5994: </div>
1.184 rillig 5995: <div class="sect1">
5996: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5997: <a name="option-names"></a>16.3. Option Names</h2></div></div></div>
5998: <p>Options that enable similar features in different packages (like
5999: optional support for a library) should use a common name in all
6000: packages that support it (like the name of the library). If another
6001: package already has an option with the same meaning, use the same
6002: name.</p>
6003: <p>Options that enable features specific to one package, where it's
6004: unlikely that another (unrelated) package has the same (or a similar)
6005: optional feature, should use a name prefixed with
6006: <code class="varname"><em class="replaceable"><code>pkgname</code></em>-</code>.</p>
6007: <p>If a group of related packages share an optional feature
6008: specific to that group, prefix it with the name of the
6009: <span class="quote">“<span class="quote">main</span>”</span> package
6010: (e. g. <code class="varname">djbware-errno-hack</code>).</p>
6011: <p>For new options, add a line to
6012: <code class="filename">mk/defaults/options.description</code>. Lines have two
6013: fields, separated by tab. The first field is the option name, the
6014: second its description. The description should be a whole sentence
6015: (starting with an uppercase letter and ending with a period) that
6016: describes what enabling the option does. E. g. <span class="quote">“<span class="quote">Enable ispell
6017: support.</span>”</span> The file is sorted by option names.</p>
6018: </div>
6019: <div class="sect1">
6020: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6021: <a name="option-build"></a>16.4. Determining the options of dependencies</h2></div></div></div>
6022: <p>When writing <a class="link" href="#buildlink3.mk"><code class="filename">buildlink3.mk</code></a> files, it is often necessary to list
6023: different dependencies based on the options with which the package was
6024: built. For querying these options, the file
6025: <code class="filename">pkgsrc/mk/pkg-build-options.mk</code> should be used. A
6026: typical example looks like this:</p>
1.1 dsieger 6027: <pre class="programlisting">
1.184 rillig 6028: pkgbase := libpurple
6029: .include "../../mk/pkg-build-options.mk"
6030:
6031: .if !empty(PKG_BUILD_OPTIONS.libpurple:Mdbus)
6032: ...
6033: .endif
1.117 sevan 6034: </pre>
1.184 rillig 6035: <p>Including <code class="filename">pkg-build-options.mk</code> here will set
6036: the variable <code class="varname">PKG_BUILD_OPTIONS.libpurple</code> to the build
6037: options of the libpurple package, which can then be queried like
6038: <code class="varname">PKG_OPTIONS</code> in the <code class="filename">options.mk</code>
6039: file. See the file <code class="filename">pkg-build-options.mk</code> for more
6040: details.</p>
1.1 dsieger 6041: </div>
6042: </div>
1.41 asau 6043: <div class="chapter">
1.1 dsieger 6044: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 6045: <a name="tools"></a>Chapter 17. Tools needed for building or running</h2></div></div></div>
1.1 dsieger 6046: <div class="toc">
6047: <p><b>Table of Contents</b></p>
1.100 leot 6048: <dl class="toc">
1.184 rillig 6049: <dt><span class="sect1"><a href="#pkgsrc-tools">17.1. Tools for pkgsrc builds</a></span></dt>
6050: <dt><span class="sect1"><a href="#package-tools">17.2. Tools needed by packages</a></span></dt>
6051: <dt><span class="sect1"><a href="#platform-tools">17.3. Tools provided by platforms</a></span></dt>
1.1 dsieger 6052: </dl>
6053: </div>
1.184 rillig 6054: <p>The <code class="varname">USE_TOOLS</code> definition is used both internally
6055: by pkgsrc and also for individual packages to define what commands
6056: are needed for building a package (like <code class="varname">TOOL_DEPENDS</code>)
6057: or for later run-time of an installed packaged (such as
6058: <code class="varname">DEPENDS</code>).
6059: If the native system provides an adequate tool, then in many cases, a pkgsrc
6060: package will not be used.</p>
6061: <p>When building a package, the replacement tools are
6062: made available in a directory (as symlinks or wrapper scripts)
6063: that is early in the executable search path. Just like the buildlink
6064: system, this helps with consistent builds.</p>
6065: <p>A tool may be needed to help build a specific package. For example,
6066: perl, GNU make (gmake) or yacc may be needed.</p>
6067: <p>Also a tool may be needed, for example, because the native system's supplied
6068: tool may be inefficient for building a package with pkgsrc.
6069: For example, a package may need GNU awk, bison (instead of
6070: yacc) or a better sed.</p>
6071: <p>The tools used by a package can be listed by running
6072: <span class="command"><strong>make show-tools</strong></span>.</p>
1.41 asau 6073: <div class="sect1">
1.1 dsieger 6074: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6075: <a name="pkgsrc-tools"></a>17.1. Tools for pkgsrc builds</h2></div></div></div>
6076: <p>The default set of tools used by pkgsrc is defined in
6077: <code class="filename">bsd.pkg.mk</code>. This includes standard Unix tools,
6078: such as: <span class="command"><strong>cat</strong></span>, <span class="command"><strong>awk</strong></span>,
6079: <span class="command"><strong>chmod</strong></span>, <span class="command"><strong>test</strong></span>, and so on.
6080: These can be seen by running:
6081: <span class="command"><strong>make show-var VARNAME=USE_TOOLS</strong></span>.</p>
6082: <p>If a package needs a specific program to build
6083: then the <code class="varname">USE_TOOLS</code> variable can be used
6084: to define the tools needed.</p>
1.1 dsieger 6085: </div>
1.184 rillig 6086: <div class="sect1">
6087: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6088: <a name="package-tools"></a>17.2. Tools needed by packages</h2></div></div></div>
6089: <p>In the following examples, the :run means that it is needed at
6090: run-time (and becomes a DEPENDS).
6091: The default is a build dependency which can be set with
6092: :build. (So in this example, it is the same as gmake:build
6093: and pkg-config:build.)</p>
1.1 dsieger 6094: <pre class="programlisting">
1.184 rillig 6095: USE_TOOLS+= gmake perl:run pkg-config
1.1 dsieger 6096: </pre>
1.184 rillig 6097: <p>When using the tools framework, a
6098: <code class="varname">TOOLS_PATH.foo</code> variable is defined
6099: which contains the full path to the appropriate tool. For example,
6100: <code class="varname">TOOLS_PATH.bash</code> could be <span class="quote">“<span class="quote">/bin/bash</span>”</span>
6101: on Linux systems.</p>
6102: <p>If you always need a pkgsrc version of the
6103: tool at run-time, then just use <code class="varname">DEPENDS</code> instead.
6104: </p>
1.1 dsieger 6105: </div>
1.184 rillig 6106: <div class="sect1">
6107: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6108: <a name="platform-tools"></a>17.3. Tools provided by platforms</h2></div></div></div>
6109: <p>When improving or porting pkgsrc to a new platform, have a look
6110: at (or create) the corresponding platform specific make file fragment under
6111: <code class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines
6112: the name of the common tools. For example:</p>
1.1 dsieger 6113: <pre class="programlisting">
1.184 rillig 6114: .if exists(/usr/bin/bzcat)
6115: TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
6116: .elif exists(/usr/bin/bzip2)
6117: TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
6118: .endif
6119:
6120: TOOLS_PLATFORM.true?= true # shell builtin
1.1 dsieger 6121: </pre>
6122: </div>
6123: </div>
1.184 rillig 6124: <div class="chapter">
6125: <div class="titlepage"><div><div><h2 class="title">
6126: <a name="buildlink"></a>Chapter 18. Buildlink methodology</h2></div></div></div>
6127: <div class="toc">
6128: <p><b>Table of Contents</b></p>
6129: <dl class="toc">
6130: <dt><span class="sect1"><a href="#converting-to-buildlink3">18.1. Converting packages to use buildlink3</a></span></dt>
6131: <dt><span class="sect1"><a href="#creating-buildlink3.mk">18.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
6132: <dd><dl>
6133: <dt><span class="sect2"><a href="#anatomy-of-bl3">18.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
6134: <dt><span class="sect2"><a href="#updating-buildlink-depends">18.2.2. Updating
6135: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6136: and
6137: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6138: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
6139: </dl></dd>
6140: <dt><span class="sect1"><a href="#writing-builtin.mk">18.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
6141: <dd><dl>
6142: <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>
6143: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">18.3.2. Global preferences for native or pkgsrc software</a></span></dt>
6144: </dl></dd>
6145: </dl>
1.1 dsieger 6146: </div>
1.184 rillig 6147: <p>Buildlink is a framework in pkgsrc that controls what headers and libraries
6148: are seen by a package's configure and build processes. This is implemented
6149: in a two step process:</p>
6150: <div class="orderedlist"><ol class="orderedlist" type="1">
6151: <li class="listitem"><p>Symlink headers and libraries for dependencies into
6152: <code class="varname">BUILDLINK_DIR</code>, which by default is a subdirectory
6153: of <code class="varname">WRKDIR</code>.</p></li>
6154: <li class="listitem"><p>Create wrapper scripts that are used in place of the normal compiler
6155: tools that translate <code class="option">-I${LOCALBASE}/include</code> and
6156: <code class="option">-L${LOCALBASE}/lib</code> into references to
6157: <code class="varname">BUILDLINK_DIR</code>. The wrapper scripts also make
6158: native compiler on some operating systems look like GCC, so that
6159: packages that expect GCC won't require modifications to build with
6160: those native compilers.</p></li>
6161: </ol></div>
6162: <p>This normalizes the environment in which a package is built so that the
6163: package may be built consistently despite what other software may be
6164: installed. Please note that the normal system header and library paths,
6165: e.g. <code class="filename">/usr/include</code>,
6166: <code class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is
6167: designed to insulate the package build from non-system-supplied
6168: software.</p>
1.41 asau 6169: <div class="sect1">
1.1 dsieger 6170: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6171: <a name="converting-to-buildlink3"></a>18.1. Converting packages to use buildlink3</h2></div></div></div>
6172: <p>The process of converting packages to use the buildlink3
6173: framework (<span class="quote">“<span class="quote">bl3ifying</span>”</span>) is fairly straightforward.
6174: The things to keep in mind are:</p>
1.23 wiz 6175: <div class="orderedlist"><ol class="orderedlist" type="1">
1.184 rillig 6176: <li class="listitem"><p>Ensure that the build always calls the wrapper scripts
6177: instead of the actual toolchain. Some packages are tricky,
6178: and the only way to know for sure is the check
6179: <code class="filename">${WRKDIR}/.work.log</code> to see if the
6180: wrappers are being invoked.</p></li>
6181: <li class="listitem"><p>Don't override <code class="varname">PREFIX</code> from within
6182: the package Makefile, e.g. Java VMs, standalone shells,
6183: etc., because the code to symlink files into
6184: <code class="filename">${BUILDLINK_DIR}</code> looks for files
6185: relative to <span class="quote">“<span class="quote">pkg_info -qp <em class="replaceable"><code>pkgname</code></em></span>”</span>.
6186: </p></li>
6187: <li class="listitem"><p>Remember that <span class="emphasis"><em>only</em></span> the
6188: <code class="filename">buildlink3.mk</code> files that you list in a
6189: package's Makefile are added as dependencies for that package.
6190: </p></li>
6191: </ol></div>
6192: <p>If a dependency on a particular package is required for its libraries and
6193: headers, then we replace:</p>
6194: <pre class="programlisting">
6195: DEPENDS+= foo>=1.1.0:../../category/foo
6196: </pre>
6197: <p>with</p>
6198: <pre class="programlisting">
6199: .include "../../category/foo/buildlink3.mk"
6200: </pre>
6201: <p>The buildlink3.mk files usually define the required dependencies.
6202: If you need a newer version of the dependency when using buildlink3.mk
6203: files, then you can define it in your Makefile; for example:</p>
1.1 dsieger 6204: <pre class="programlisting">
1.184 rillig 6205: BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
6206: .include "../../category/foo/buildlink3.mk"
1.1 dsieger 6207: </pre>
1.184 rillig 6208: <p>There are several <code class="filename">buildlink3.mk</code>
6209: files in <code class="filename">pkgsrc/mk</code>
6210: that handle special package issues:</p>
6211: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6212: <li class="listitem"><p><code class="filename">bdb.buildlink3.mk</code> chooses either
6213: the native or a pkgsrc Berkeley DB implementation based on
6214: the values of <code class="varname">BDB_ACCEPTED</code> and
6215: <code class="varname">BDB_DEFAULT</code>.</p></li>
6216: <li class="listitem"><p><code class="filename">curses.buildlink3.mk</code>: If the system
6217: comes with neither Curses nor NCurses, this will take care
1.207 leot 6218: 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 6219: <li class="listitem"><p><code class="filename">krb5.buildlink3.mk</code> uses the value
6220: of <code class="varname">KRB5_ACCEPTED</code> to choose between
6221: adding a dependency on Heimdal or MIT-krb5 for packages that
6222: require a Kerberos 5 implementation.</p></li>
6223: <li class="listitem"><p><code class="filename">motif.buildlink3.mk</code> checks for a
6224: system-provided Motif installation or adds a dependency on
1.207 leot 6225: <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 6226: <code class="varname">MOTIF_TYPE</code> to <span class="quote">“<span class="quote">dt</span>”</span>,
6227: <span class="quote">“<span class="quote">lesstif</span>”</span> or <span class="quote">“<span class="quote">motif</span>”</span>
6228: to choose which Motif version will be used.</p></li>
6229: <li class="listitem"><p><code class="filename">readline.buildlink3.mk</code> checks for a
6230: system-provided GNU readline or editline (libedit) installation,
1.207 leot 6231: 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>,
6232: <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 6233: <code class="varname">READLINE_DEFAULT</code> to choose readline implementation.
6234: If your package really needs GNU readline library, its Makefile
6235: should include <code class="filename">devel/readline/buildlink3.mk</code>
6236: instead of <code class="filename">readline.buildlink3.mk</code>.</p></li>
6237: <li class="listitem"><p><code class="filename">oss.buildlink3.mk</code> defines several
6238: variables that may be used by packages that use the
6239: Open Sound System (OSS) API.</p></li>
6240: <li class="listitem"><p><code class="filename">pgsql.buildlink3.mk</code> will accept
6241: any of the Postgres versions in the variable
6242: <code class="varname">PGSQL_VERSIONS_ACCEPTED</code> and default to
6243: the version <code class="varname">PGSQL_VERSION_DEFAULT</code>. See
6244: the file for more information.</p></li>
6245: <li class="listitem"><p><code class="filename">pthread.buildlink3.mk</code> uses the value of
6246: <code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds
1.207 leot 6247: 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 6248: <li class="listitem"><p><code class="filename">xaw.buildlink3.mk</code> uses the value of
6249: <code class="varname">XAW_TYPE</code> to choose a particular Athena widgets
6250: library.</p></li>
6251: </ul></div>
6252: <p>The comments in those <code class="filename">buildlink3.mk</code>
6253: files provide a more complete
6254: description of how to use them properly.</p>
1.1 dsieger 6255: </div>
1.41 asau 6256: <div class="sect1">
1.1 dsieger 6257: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6258: <a name="creating-buildlink3.mk"></a>18.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div>
6259: <a name="buildlink3.mk"></a><p>A package's <code class="filename">buildlink3.mk</code> file is
6260: included by Makefiles to indicate the need to compile and link
6261: against header files and libraries provided by the package. A
6262: <code class="filename">buildlink3.mk</code> file should always provide
6263: enough information to add the correct type of dependency
6264: relationship and include any other
6265: <code class="filename">buildlink3.mk</code> files that it needs to find
6266: headers and libraries that it needs in turn.</p>
6267: <p>To generate an initial <code class="filename">buildlink3.mk</code>
1.207 leot 6268: 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 6269: package is highly recommended. For most packages, the following
6270: command will generate a good starting point for
6271: <code class="filename">buildlink3.mk</code> files:</p>
6272: <pre class="screen">
6273: <code class="prompt">%</code> <strong class="userinput"><code>cd pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>pkgdir</code></em>
6274: <code class="prompt">%</code> createbuildlink >buildlink3.mk</code></strong>
6275: </pre>
1.41 asau 6276: <div class="sect2">
1.1 dsieger 6277: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 6278: <a name="anatomy-of-bl3"></a>18.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div>
6279: <p>The following real-life example
6280: <code class="filename">buildlink3.mk</code> is taken
6281: from <code class="filename">pkgsrc/graphics/tiff</code>:</p>
1.1 dsieger 6282: <pre class="programlisting">
1.184 rillig 6283: BUILDLINK_TREE+= tiff
6284:
6285: .if !defined(TIFF_BUILDLINK3_MK)
6286: TIFF_BUILDLINK3_MK:=
6287:
6288: BUILDLINK_API_DEPENDS.tiff+= tiff>=3.6.1
6289: BUILDLINK_ABI_DEPENDS.tiff+= tiff>=3.7.2nb1
6290: BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
6291:
6292: .include "../../devel/zlib/buildlink3.mk"
6293: .include "../../graphics/jpeg/buildlink3.mk"
6294: .endif # TIFF_BUILDLINK3_MK
6295:
6296: BUILDLINK_TREE+= -tiff
1.1 dsieger 6297: </pre>
1.184 rillig 6298: <p>The header and footer manipulate
6299: <code class="varname">BUILDLINK_TREE</code>, which is common across all
6300: <code class="filename">buildlink3.mk</code> files and is used to track
6301: the dependency tree.</p>
6302: <p>The main section is protected from multiple inclusion
6303: and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is
6304: added. Several important variables are set in the section:</p>
6305: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6306: <li class="listitem"><p><code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6307: is the dependency version recorded in the installed
1.184 rillig 6308: package; this should always be set using
6309: <span class="command"><strong>+=</strong></span> to ensure that
6310: we're appending to any pre-existing list of values. This
1.185 wiz 6311: variable should be set to the last version of the
1.184 rillig 6312: package that had an backwards-incompatible API change.
6313: </p></li>
6314: <li class="listitem"><p><code class="varname">BUILDLINK_PKGSRCDIR.<em class="replaceable"><code>pkg</code></em></code>
6315: is the location of the <em class="replaceable"><code>pkg</code></em>
6316: pkgsrc directory.</p></li>
6317: <li class="listitem"><p><code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
6318: (not shown above) controls whether we use
6319: <code class="varname">BUILD_DEPENDS</code> or
6320: <code class="varname">DEPENDS</code> to add the dependency on
6321: <em class="replaceable"><code>pkg</code></em>. The build dependency is
6322: selected by setting
6323: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
6324: to <span class="quote">“<span class="quote">build</span>”</span>. By default, the full dependency is
6325: used.</p></li>
6326: <li class="listitem"><p><code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code>
6327: and
6328: <code class="varname">BUILDLINK_LIBDIRS.<em class="replaceable"><code>pkg</code></em></code>
6329: (not shown above) are lists of subdirectories of
6330: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6331: to add to the header and library search paths. These
6332: default to <span class="quote">“<span class="quote">include</span>”</span> and <span class="quote">“<span class="quote">lib</span>”</span>
6333: respectively.</p></li>
6334: <li class="listitem"><p><code class="varname">BUILDLINK_CPPFLAGS.<em class="replaceable"><code>pkg</code></em></code>
6335: (not shown above) is the list of preprocessor flags to add
6336: to <code class="varname">CPPFLAGS</code>, which are passed on to the
6337: configure and build phases. The <span class="quote">“<span class="quote">-I</span>”</span> option
6338: should be avoided and instead be handled using
6339: <code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code> as
6340: above.</p></li>
6341: </ul></div>
6342: <p>The following variables are all optionally defined within
6343: this second section (protected against multiple inclusion) and
6344: control which package files are symlinked into
6345: <code class="filename">${BUILDLINK_DIR}</code> and how their names are
6346: transformed during the symlinking:</p>
6347: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6348: <li class="listitem"><p><code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>
6349: (not shown above) is a shell glob pattern relative to
6350: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6351: to be symlinked into
6352: <code class="filename">${BUILDLINK_DIR}</code>,
6353: e.g. <code class="filename">include/*.h</code>.</p></li>
6354: <li class="listitem"><p><code class="varname">BUILDLINK_FILES_CMD.<em class="replaceable"><code>pkg</code></em></code>
6355: (not shown above) is a shell pipeline that
6356: outputs to stdout a list of files relative to
6357: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>.
6358: The resulting files are to be symlinked
6359: into <code class="filename">${BUILDLINK_DIR}</code>. By default,
6360: this takes the <code class="filename">+CONTENTS</code> of a
6361: <em class="replaceable"><code>pkg</code></em> and filters it through
6362: <code class="varname">${BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em>}</code>.</p></li>
6363: <li class="listitem"><p><code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6364: (not shown above) is a filter command that filters
6365: <code class="filename">+CONTENTS</code> input into a list of files
6366: relative to
6367: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
6368: on stdout. By default,
6369: <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
6370: outputs the contents of the <code class="filename">include</code>
6371: and <code class="filename">lib</code> directories in the package
6372: <code class="filename">+CONTENTS</code>.</p></li>
6373: <li class="listitem"><p><code class="varname">BUILDLINK_FNAME_TRANSFORM.<em class="replaceable"><code>pkg</code></em></code>
6374: (not shown above) is a list of sed arguments used to
6375: transform the name of the source filename into a
6376: destination filename, e.g. <span class="command"><strong>-e
6377: "s|/curses.h|/ncurses.h|g"</strong></span>.</p></li>
6378: </ul></div>
6379: <p>This section can additionally include any
6380: <code class="filename">buildlink3.mk</code> needed for
6381: <em class="replaceable"><code>pkg</code></em>'s library dependencies.
6382: Including these <code class="filename">buildlink3.mk</code> files
6383: means that the headers and libraries for these
6384: dependencies are also symlinked into
6385: <code class="filename">${BUILDLINK_DIR}</code>
6386: whenever the <em class="replaceable"><code>pkg</code></em>
6387: <code class="filename">buildlink3.mk</code>
6388: file is included. Dependencies are only added for directly
6389: include <code class="filename">buildlink3.mk</code> files.</p>
6390: <p>When providing a <code class="filename">buildlink3.mk</code> and
6391: including other <code class="filename">buildlink3.mk</code> files in it,
6392: please only add necessary ones, i.e., those whose libraries or
6393: header files are automatically exposed when the package is
6394: use.</p>
6395: <p>In particular, if only an executable
6396: (<code class="filename">bin/foo</code>) is linked against a library, that
6397: library does not need to be propagated in the
6398: <code class="filename">buildlink3.mk</code> file.</p>
6399: <p>The following steps should help you decide if a
6400: <code class="filename">buildlink3.mk</code> file needs to be included:
6401: </p>
6402: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6403: <li class="listitem"><p>Look at the installed header files: What
6404: headers do they include? The packages providing these files
6405: must be buildlinked.</p></li>
6406: <li class="listitem"><p>Run <code class="filename">ldd</code> on all installed
6407: libraries and look against what other libraries they link.
6408: Some of the packages providing these probably need to be
6409: buildlinked; however, it's not automatic, since e.g. GTK on
6410: some systems pulls in the X libraries, so they will show up in
6411: the <code class="filename">ldd</code> output, while on others (like OS
6412: X) it won't. <code class="filename">ldd</code> output can thus only be
6413: used as a hint.</p></li>
6414: </ul></div>
6415: <p>
6416: </p>
6417: </div>
1.41 asau 6418: <div class="sect2">
1.1 dsieger 6419: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 6420: <a name="updating-buildlink-depends"></a>18.2.2. Updating
6421: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6422: and
6423: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6424: in <code class="filename">buildlink3.mk</code> files</h3></div></div></div>
1.185 wiz 6425: <p>Both variables set lower bounds for a version of this package.
6426: The two variables differ in that one describes source
1.184 rillig 6427: compatibility (API) and the other binary compatibility (ABI).
6428: The difference is that a change in the API breaks compilation of
6429: programs while changes in the ABI stop compiled programs from
6430: running.</p>
1.185 wiz 6431: <p>The
6432: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6433: variable in a <code class="filename">buildlink3.mk</code> should be
6434: changed very rarely. (One possible scenario: If all packages
6435: using this package need a higher version than defined in the
6436: <code class="filename">buildlink3.mk</code>,
1.184 rillig 6437: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6438: could be updated to that higher version.)</p>
6439: <p>On the other hand, changes to
1.184 rillig 6440: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6441: are more common. The variable will need to be updated every
6442: time the major version of one of its shared libraries is changed,
6443: or any other change where a binary built against the previous
6444: version of the package will not run against the new version any
6445: longer.</p>
6446: <p>In such a case, the package's
1.184 rillig 6447: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6448: must be increased to require the new package version. Then the
6449: <code class="varname">PKGREVISION</code> of all packages
6450: <em class="replaceable"><code>foo</code></em> that depend on this package need
6451: to be increased, and if they have
6452: <code class="filename">buildlink3.mk</code> files,
6453: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>foo</code></em></code>
6454: in their <code class="filename">buildlink3.mk</code> files must be
6455: increased to the new version as well. This is required so that a
6456: package will pull in the versions of the packages that use the
6457: new ABI and that the packages' <code class="varname">PKGREVISION</code>s
6458: uniquely identify the packages built against the new ABI. The
1.207 leot 6459: <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 6460: help with these updates.</p>
6461: <p>See <a class="xref" href="#dependencies" title="21.1.5. Handling dependencies">Section 21.1.5, “Handling dependencies”</a> for more information
6462: about dependencies on other packages, including the
6463: <code class="varname">BUILDLINK_API_DEPENDS</code> definitions.</p>
1.184 rillig 6464: <p>Please take careful consideration before adjusting
6465: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6466: or
6467: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.185 wiz 6468: in a <code class="filename">buildlink3.mk</code> file as we don't want to
6469: cause unneeded package deletions and rebuilds. In many cases,
6470: new versions of packages work just fine with older
6471: dependencies.</p>
1.211 gutterid 6472: <p>Also, it is not needed to set
1.184 rillig 6473: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
6474: when it is identical to
1.211 gutterid 6475: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.</p>
6476: <p>Note there is also the distinction that users are able to disable
6477: enforcement of ABI dependencies using the <code class="varname">USE_ABI_DEPENDS</code>
6478: variable, but there is no equivalent option for API dependencies.</p>
1.1 dsieger 6479: </div>
6480: </div>
1.41 asau 6481: <div class="sect1">
1.1 dsieger 6482: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6483: <a name="writing-builtin.mk"></a>18.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div>
6484: <p>Some packages in pkgsrc install headers and libraries that
6485: coincide with headers and libraries present in the base system.
6486: Aside from a <code class="filename">buildlink3.mk</code> file, these
6487: packages should also include a <code class="filename">builtin.mk</code>
6488: file that includes the necessary checks to decide whether using
6489: the built-in software or the pkgsrc software is
6490: appropriate.</p>
6491: <p>The only requirements of a builtin.mk file for
6492: <em class="replaceable"><code>pkg</code></em> are:</p>
6493: <div class="orderedlist"><ol class="orderedlist" type="1">
6494: <li class="listitem"><p>It should set
6495: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6496: to either <span class="quote">“<span class="quote">yes</span>”</span> or <span class="quote">“<span class="quote">no</span>”</span>
6497: after it is included.</p></li>
6498: <li class="listitem"><p>It should <span class="emphasis"><em>not</em></span> override any
6499: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6500: which is already set before the
6501: <code class="filename">builtin.mk</code> file is included.</p></li>
6502: <li class="listitem"><p>It should be written to allow multiple inclusion. This
6503: is <span class="emphasis"><em>very</em></span> important and takes careful
6504: attention to <code class="filename">Makefile</code> coding.</p></li>
6505: </ol></div>
6506: <div class="sect2">
6507: <div class="titlepage"><div><div><h3 class="title">
6508: <a name="anatomy-of-builtin.mk"></a>18.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</h3></div></div></div>
6509: <p>The following is the recommended template for builtin.mk
6510: files:</p>
1.1 dsieger 6511: <pre class="programlisting">
1.184 rillig 6512: .if !defined(IS_BUILTIN.foo)
6513: #
6514: # IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
6515: # genuinely exists in the system or not.
6516: #
6517: IS_BUILTIN.foo?= no
1.1 dsieger 6518:
1.184 rillig 6519: # BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
6520: # version can be determined.
6521: #
6522: . if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
6523: BUILTIN_PKG.foo?= foo-1.0
6524: . endif
6525: .endif # IS_BUILTIN.foo
1.1 dsieger 6526:
1.184 rillig 6527: .if !defined(USE_BUILTIN.foo)
6528: USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
6529: . if defined(BUILTIN_PKG.foo)
6530: . for _depend_ in ${BUILDLINK_API_DEPENDS.foo}
6531: . if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
6532: USE_BUILTIN.foo!= \
6533: ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo} \
6534: && ${ECHO} "yes" || ${ECHO} "no"
6535: . endif
6536: . endfor
6537: . endif
6538: .endif # USE_BUILTIN.foo
1.1 dsieger 6539:
1.184 rillig 6540: CHECK_BUILTIN.foo?= no
6541: .if !empty(CHECK_BUILTIN.foo:M[nN][oO])
6542: #
6543: # Here we place code that depends on whether USE_BUILTIN.foo is set to
6544: # "yes" or "no".
6545: #
6546: .endif # CHECK_BUILTIN.foo
1.1 dsieger 6547: </pre>
1.184 rillig 6548: <p>The first section sets
6549: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6550: depending on if <em class="replaceable"><code>pkg</code></em> really exists
6551: in the base system. This should not be a base system software
6552: with similar functionality to <em class="replaceable"><code>pkg</code></em>;
6553: it should only be <span class="quote">“<span class="quote">yes</span>”</span> if the actual package is
6554: included as part of the base system. This variable is only
6555: used internally within the <code class="filename">builtin.mk</code>
6556: file.</p>
6557: <p>The second section sets
6558: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6559: to the version of <em class="replaceable"><code>pkg</code></em> in the base
6560: system if it exists (if
6561: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6562: is <span class="quote">“<span class="quote">yes</span>”</span>). This variable is only used internally
6563: within the <code class="filename">builtin.mk</code> file.</p>
6564: <p>The third section sets
6565: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6566: and is <span class="emphasis"><em>required</em></span> in all
6567: <code class="filename">builtin.mk</code> files. The code in this
6568: section must make the determination whether the built-in
6569: software is adequate to satisfy the dependencies listed in
6570: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6571: This is typically done by comparing
6572: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
6573: against each of the dependencies in
6574: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
6575: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6576: <span class="emphasis"><em>must</em></span> be set to the correct value by the
6577: end of the <code class="filename">builtin.mk</code> file. Note that
6578: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6579: may be <span class="quote">“<span class="quote">yes</span>”</span> even if
6580: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6581: is <span class="quote">“<span class="quote">no</span>”</span> because we may make the determination
6582: that the built-in version of the software is similar enough to
6583: be used as a replacement.</p>
6584: <p>The last section is guarded by
6585: <code class="varname">CHECK_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>,
6586: and includes code that uses the value of
6587: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
6588: set in the previous section. This typically includes, e.g.,
6589: adding additional dependency restrictions and listing additional
6590: files to symlink into <code class="filename">${BUILDLINK_DIR}</code> (via
6591: <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>).</p>
6592: </div>
6593: <div class="sect2">
6594: <div class="titlepage"><div><div><h3 class="title">
6595: <a name="native-or-pkgsrc-preference"></a>18.3.2. Global preferences for native or pkgsrc software</h3></div></div></div>
6596: <p>When building packages, it's possible to choose whether to set
6597: a global preference for using either the built-in (native)
6598: version or the pkgsrc version of software to satisfy a
6599: dependency. This is controlled by setting
6600: <code class="varname">PREFER_PKGSRC</code> and
6601: <code class="varname">PREFER_NATIVE</code>. These variables take values
6602: of either <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">no</span>”</span>, or a list of
6603: packages. <code class="varname">PREFER_PKGSRC</code> tells pkgsrc to
6604: use the pkgsrc versions of software, while
6605: <code class="varname">PREFER_NATIVE</code> tells pkgsrc to use the
6606: built-in versions. Preferences are determined by the most
6607: specific instance of the package in either
6608: <code class="varname">PREFER_PKGSRC</code> or
6609: <code class="varname">PREFER_NATIVE</code>. If a package is specified
6610: in neither or in both variables, then
6611: <code class="varname">PREFER_PKGSRC</code> has precedence over
6612: <code class="varname">PREFER_NATIVE</code>. For example, to require
6613: using pkgsrc versions of software for all but the most basic
6614: bits on a NetBSD system, you can set:</p>
1.1 dsieger 6615: <pre class="programlisting">
1.184 rillig 6616: PREFER_PKGSRC= yes
6617: PREFER_NATIVE= getopt skey tcp_wrappers
6618: </pre>
6619: <p>A package <span class="emphasis"><em>must</em></span> have a
6620: <code class="filename">builtin.mk</code>
6621: file to be listed in <code class="varname">PREFER_NATIVE</code>,
6622: otherwise it is simply ignored in that list.</p>
1.191 bacon 6623: <p><code class="varname">PREFER_PKGSRC</code> and
6624: <code class="varname">PREFER_NATIVE</code> should be set during bootstrap
6625: to ensure that the bootstrap process does not use inapropriate
6626: native tools as dependencies for core packages.
6627:
6628: </p>
6629: <pre class="screen">
6630: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap --prefer-pkgsrc yes --prefer-native openssl</code></strong>
6631: </pre>
6632: <p>
6633:
1.184 rillig 6634: Switching between settings globally at a later date can introduce
6635: complications with dependency resolution. This is caused by packages
1.191 bacon 6636: built with the opposite preference being installed alongside each
6637: other. Hence, any changes to these variables after bootstrap will
6638: necessitate rebuilding all packages depending on one whose preference
6639: has been changed. This is not trivial and should be avoided.</p>
6640: <p>When using pkgsrc on Linux systems, there is high risk of
6641: "leakage", where programs installed by pkgsrc may inadvertently use a
6642: command or library not installed by pkgsrc, e.g. those installed by
6643: yum or apt. Such foreign dependencies may be installed, removed, or
6644: upgraded to a version incompatible with the pkgsrc package at any
6645: time, causing pkgsrc packages to subsequently malfunction. Pkgsrc
6646: cannot prevent this, as it has no control over other package managers.
6647: Another potential problem is that under Redhat Enterprise and related
6648: Linux systems, yum packages are only patched and never upgraded, so
6649: eventually they may become too outdated for use by pkgsrc. Even
6650: intentionally using foreign dependencies, not considered leakage, can
6651: lead to these problems, so it is generally discouraged. In order to
6652: minimize such problems, PREFER_PKGSRC defaults to "yes" on Linux systems.
6653: This ensures that pkgsrc is aware of any changes to dependency packages
6654: and can rebuild or upgrade the entire dependency tree as needed. This
6655: default can be overridden by setting --prefer-pkgsrc to "no" or a list of
6656: packages, or by setting --prefer-native to "yes".</p>
1.1 dsieger 6657: </div>
1.7 rillig 6658: </div>
1.1 dsieger 6659: </div>
1.41 asau 6660: <div class="chapter">
1.1 dsieger 6661: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 6662: <a name="plist"></a>Chapter 19. PLIST issues</h2></div></div></div>
1.1 dsieger 6663: <div class="toc">
6664: <p><b>Table of Contents</b></p>
1.100 leot 6665: <dl class="toc">
1.184 rillig 6666: <dt><span class="sect1"><a href="#rcs-id">19.1. RCS ID</a></span></dt>
6667: <dt><span class="sect1"><a href="#automatic-plist-generation">19.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
6668: <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>
6669: <dt><span class="sect1"><a href="#plist.misc">19.4. Variable substitution in PLIST</a></span></dt>
6670: <dt><span class="sect1"><a href="#manpage-compression">19.5. Man page compression</a></span></dt>
6671: <dt><span class="sect1"><a href="#using-PLIST_SRC">19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
6672: <dt><span class="sect1"><a href="#platform-specific-plist">19.7. Platform-specific and differing PLISTs</a></span></dt>
6673: <dt><span class="sect1"><a href="#build-plist">19.8. Build-specific PLISTs</a></span></dt>
6674: <dt><span class="sect1"><a href="#faq.common-dirs">19.9. Sharing directories between packages</a></span></dt>
1.1 dsieger 6675: </dl>
6676: </div>
1.184 rillig 6677: <p>The <code class="filename">PLIST</code> file contains a package's
6678: <span class="quote">“<span class="quote">packing list</span>”</span>, i.e. a list of files that belong to
6679: the package (relative to the <code class="filename">${PREFIX}</code>
6680: directory it's been installed in) plus some additional statements
1.207 leot 6681: - see the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_create.1"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> man page for a full list.
1.184 rillig 6682: This chapter addresses some issues that need attention when
6683: dealing with the <code class="filename">PLIST</code> file (or files, see
6684: below!).</p>
1.41 asau 6685: <div class="sect1">
1.1 dsieger 6686: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6687: <a name="rcs-id"></a>19.1. RCS ID</h2></div></div></div>
6688: <p>Be sure to add a RCS ID line as the first thing in any
6689: <code class="filename">PLIST</code> file you write:</p>
6690: <pre class="programlisting">
6691: @comment $NetBSD $
6692: </pre>
6693: <p>An artificial space has been added between NetBSD and $, this is a
6694: workaround here to prevent CVS expanding to the filename of the guide. When
6695: adding the RCS ID the space should be omitted.</p>
1.1 dsieger 6696: </div>
1.41 asau 6697: <div class="sect1">
1.1 dsieger 6698: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6699: <a name="automatic-plist-generation"></a>19.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div>
6700: <p>You can use the <span class="command"><strong>make print-PLIST</strong></span> command
6701: to output a PLIST that matches any new files since the package
6702: was extracted. See <a class="xref" href="#build.helpful-targets" title="13.17. Other helpful targets">Section 13.17, “Other helpful targets”</a> for
6703: more information on this target.</p>
1.1 dsieger 6704: </div>
1.41 asau 6705: <div class="sect1">
1.1 dsieger 6706: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6707: <a name="print-PLIST"></a>19.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>
6708: </h2></div></div></div>
6709: <p>The <code class="varname">PRINT_PLIST_AWK</code> variable takes a set
6710: of AWK patterns and actions that are used to filter the output of
6711: print-PLIST. You can <span class="emphasis"><em>append</em></span> any chunk of AWK
6712: scripting you like to it, but be careful with quoting.</p>
6713: <p>For example, to get all files inside the
6714: <code class="filename">libdata/foo</code> directory removed from the
6715: resulting PLIST:</p>
1.1 dsieger 6716: <pre class="programlisting">
1.184 rillig 6717: PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
1.1 dsieger 6718: </pre>
1.185 wiz 6719: <p>The <code class="varname">PRINT_PLIST_AWK</code> transformations are
6720: evaluated after the file list and directory list are sorted.
6721: <code class="varname">EARLY_PRINT_PLIST_AWK</code> is like
6722: <code class="varname">PRINT_PLIST_AWK</code> except it operates before the file
6723: list and directory list are sorted.</p>
1.184 rillig 6724: </div>
6725: <div class="sect1">
6726: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6727: <a name="plist.misc"></a>19.4. Variable substitution in PLIST</h2></div></div></div>
6728: <p>A number of variables are substituted automatically in
6729: PLISTs when a package is installed on a system. This includes the
6730: following variables:</p>
6731: <div class="variablelist"><dl class="variablelist">
6732: <dt><span class="term"><code class="varname">${MACHINE_ARCH}</code>, <code class="varname">${MACHINE_GNU_ARCH}</code></span></dt>
6733: <dd>
6734: <p>Some packages like emacs and perl embed information
6735: about which architecture they were built on into the
6736: pathnames where they install their files. To handle this
6737: case, PLIST will be preprocessed before actually used, and
6738: the symbol
6739: <span class="quote">“<span class="quote"><code class="varname">${MACHINE_ARCH}</code></span>”</span> will be
6740: replaced by what <span class="command"><strong>uname -p</strong></span> gives. The
6741: same is done if the string
6742: <code class="varname">${MACHINE_GNU_ARCH}</code> is embedded in
6743: PLIST somewhere - use this on packages that have GNU
6744: autoconf-created configure scripts.</p>
6745: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
6746: <h3 class="title">Legacy note</h3>
6747: <p>There used to be a symbol
6748: <span class="quote">“<span class="quote"><code class="varname">$ARCH</code></span>”</span> that
6749: was replaced by the output of <span class="command"><strong>uname
6750: -m</strong></span>, but that's no longer supported and has
6751: been removed.</p>
6752: </div>
6753: </dd>
6754: <dt><span class="term"><code class="varname">${OPSYS}</code>, <code class="varname">${LOWER_OPSYS}</code>, <code class="varname">${OS_VERSION}</code></span></dt>
6755: <dd>
6756: <p>Some packages want to embed the OS name and version
6757: into some paths. To do this, use these variables in the
6758: <code class="filename">PLIST</code>:
6759: </p>
6760: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6761: <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>
6762: <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>
6763: <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>
6764: </ul></div>
6765: </dd>
6766: </dl></div>
6767: <p>For a list of values which are replaced by
6768: default, the output of <span class="command"><strong>make help topic=PLIST_SUBST</strong></span> as
6769: well as searching the <code class="filename">pkgsrc/mk</code> directory with <span class="command"><strong>grep</strong></span> for
6770: <code class="varname">PLIST_SUBST</code> should help.</p>
6771: <p>If you want to change other variables not listed above, you
6772: can add variables and their expansions to this variable in the
6773: 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 6774: <pre class="programlisting">
1.184 rillig 6775: PLIST_SUBST+= SOMEVAR="somevalue"
1.1 dsieger 6776: </pre>
1.184 rillig 6777: <p>This replaces all occurrences of <span class="quote">“<span class="quote">${SOMEVAR}</span>”</span>
6778: in the <code class="filename">PLIST</code> with
6779: <span class="quote">“<span class="quote">somevalue</span>”</span>.</p>
6780: <p>The <code class="varname">PLIST_VARS</code> variable can be used to simplify
6781: the common case of conditionally including some
6782: <code class="filename">PLIST</code> entries. It can be done by adding
6783: <code class="literal"><code class="varname">PLIST_VARS</code>+=foo</code> and
6784: setting the corresponding <code class="varname">PLIST.foo</code> variable
6785: to <code class="literal">yes</code> if the entry should be included.
6786: This will substitute <span class="quote">“<span class="quote"><code class="varname">${PLIST.foo}</code></span>”</span>
6787: in the <code class="filename">PLIST</code> with either
6788: <span class="quote">“<span class="quote"><code class="literal">""</code></span>”</span> or
6789: <span class="quote">“<span class="quote"><code class="literal">"@comment "</code></span>”</span>.
6790: For example, in <code class="filename">Makefile</code>:</p>
1.66 asau 6791: <pre class="programlisting">
1.184 rillig 6792: PLIST_VARS+= foo
6793: .if <em class="replaceable"><code>condition</code></em>
6794: PLIST.foo= yes
6795: .else
1.66 asau 6796: </pre>
1.184 rillig 6797: <p>And then in <code class="filename">PLIST</code>:</p>
1.1 dsieger 6798: <pre class="programlisting">
1.184 rillig 6799: @comment $NetBSD $
6800: bin/bar
6801: man/man1/bar.1
6802: ${PLIST.foo}bin/foo
6803: ${PLIST.foo}man/man1/foo.1
6804: ${PLIST.foo}share/bar/foo.data
1.1 dsieger 6805: </pre>
1.184 rillig 6806: <p>An artificial space has been added between NetBSD and $, this is a
6807: workaround here to prevent CVS expanding to the filename of the guide. When
1.195 gutterid 6808: adding the RCS ID the space should be omitted.</p>
1.1 dsieger 6809: </div>
1.184 rillig 6810: <div class="sect1">
6811: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6812: <a name="manpage-compression"></a>19.5. Man page compression</h2></div></div></div>
6813: <p>Man pages should be installed in compressed form if
6814: <code class="varname">MANZ</code> is set (in <code class="filename">bsd.own.mk</code>),
6815: and uncompressed otherwise. To handle this in the
6816: <code class="filename">PLIST</code> file, the suffix <span class="quote">“<span class="quote">.gz</span>”</span> is
6817: appended/removed automatically for man pages according to
6818: <code class="varname">MANZ</code> and <code class="varname">MANCOMPRESSED</code> being set
6819: or not, see above for details. This modification of the
6820: <code class="filename">PLIST</code> file is done on a copy of it, not
6821: <code class="filename">PLIST</code> itself.</p>
1.1 dsieger 6822: </div>
1.41 asau 6823: <div class="sect1">
1.1 dsieger 6824: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6825: <a name="using-PLIST_SRC"></a>19.6. Changing PLIST source with <code class="varname">PLIST_SRC</code>
6826: </h2></div></div></div>
6827: <p>To use one or more files as source for the <code class="filename">PLIST</code> used
6828: in generating the binary package, set the variable
6829: <code class="varname">PLIST_SRC</code> to the names of that file(s).
1.207 leot 6830: The files are later concatenated using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cat.1"><span class="citerefentry"><span class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
1.184 rillig 6831: important. The default for <code class="varname">PLIST_SRC</code> is
6832: <code class="filename">${PKGDIR}/PLIST</code>.</p>
1.1 dsieger 6833: </div>
1.41 asau 6834: <div class="sect1">
1.1 dsieger 6835: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6836: <a name="platform-specific-plist"></a>19.7. Platform-specific and differing PLISTs</h2></div></div></div>
6837: <p>Some packages decide to install a different set of files based on
6838: the operating system being used. These differences can be
6839: automatically handled by using the following files:</p>
6840: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6841: <li class="listitem"><p><code class="filename">PLIST.common</code></p></li>
6842: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}</code></p></li>
6843: <li class="listitem"><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li>
6844: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li>
6845: <li class="listitem"><p><code class="filename">PLIST.common_end</code></p></li>
6846: </ul></div>
1.1 dsieger 6847: </div>
1.41 asau 6848: <div class="sect1">
1.1 dsieger 6849: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6850: <a name="build-plist"></a>19.8. Build-specific PLISTs</h2></div></div></div>
6851: <p>Some packages decide to generate hard-to-guess file names
6852: during installation that are hard to wire down.</p>
6853: <p>In such cases, you can set the
6854: <code class="varname">GENERATE_PLIST</code> variable to shell code
6855: terminated (with a semicolon) that will output PLIST entries which
6856: will be appended to the PLIST</p>
6857: <p>You can find one example in editors/xemacs:</p>
6858: <pre class="programlisting">
6859: GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ;
6860: </pre>
6861: <p>which will append something like
6862: <code class="filename">bin/xemacs-21.4.23-54e8ea71.dmp</code> to the
6863: <code class="filename">PLIST</code>.
6864: </p>
1.1 dsieger 6865: </div>
1.41 asau 6866: <div class="sect1">
1.1 dsieger 6867: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6868: <a name="faq.common-dirs"></a>19.9. Sharing directories between packages</h2></div></div></div>
6869: <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where
6870: multiple (and unrelated) packages install files. These
6871: directories were problematic because you had to add special
6872: tricks in the PLIST to conditionally remove them, or have some
6873: centralized package handle them.</p>
6874: <p>In pkgsrc, it is now easy: Each package should create
6875: directories and install files as needed; <span class="command"><strong>pkg_delete</strong></span>
6876: will remove any directories left empty after uninstalling a
6877: package.</p>
6878: <p>If a package needs an empty directory to work, create
6879: the directory during installation as usual, and also add an
6880: entry to the PLIST:
6881:
6882: </p>
6883: <pre class="programlisting">
6884: @pkgdir path/to/empty/directory
6885: </pre>
6886: <p>
6887:
6888: or take a look at <code class="varname">MAKE_DIRS</code> and
6889: <code class="varname">OWN_DIRS</code>.
1.1 dsieger 6890: </p>
6891: </div>
1.184 rillig 6892: </div>
6893: <div class="chapter">
6894: <div class="titlepage"><div><div><h2 class="title">
6895: <a name="pkginstall"></a>Chapter 20. The pkginstall framework</h2></div></div></div>
6896: <div class="toc">
6897: <p><b>Table of Contents</b></p>
6898: <dl class="toc">
6899: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">20.1. Files and directories outside the installation prefix</a></span></dt>
6900: <dd><dl>
6901: <dt><span class="sect2"><a href="#dirs-outside-prefix">20.1.1. Directory manipulation</a></span></dt>
6902: <dt><span class="sect2"><a href="#files-outside-prefix">20.1.2. File manipulation</a></span></dt>
6903: </dl></dd>
6904: <dt><span class="sect1"><a href="#conf-files">20.2. Configuration files</a></span></dt>
6905: <dd><dl>
6906: <dt><span class="sect2"><a href="#conf-files-sysconfdir">20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
6907: <dt><span class="sect2"><a href="#conf-files-configure">20.2.2. Telling the software where configuration files are</a></span></dt>
6908: <dt><span class="sect2"><a href="#conf-files-patching">20.2.3. Patching installations</a></span></dt>
6909: <dt><span class="sect2"><a href="#conf-files-disable">20.2.4. Disabling handling of configuration files</a></span></dt>
6910: </dl></dd>
6911: <dt><span class="sect1"><a href="#rcd-scripts">20.3. System startup scripts</a></span></dt>
6912: <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>
6913: <dt><span class="sect1"><a href="#users-and-groups">20.4. System users and groups</a></span></dt>
6914: <dt><span class="sect1"><a href="#shells">20.5. System shells</a></span></dt>
6915: <dd><dl><dt><span class="sect2"><a href="#shells-disable">20.5.1. Disabling shell registration</a></span></dt></dl></dd>
6916: <dt><span class="sect1"><a href="#fonts">20.6. Fonts</a></span></dt>
6917: <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>
6918: </dl>
6919: </div>
6920: <p>This chapter describes the framework known as
6921: <code class="literal">pkginstall</code>, whose key features are:</p>
6922: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6923: <li class="listitem"><p>Generic installation and manipulation of directories and files
6924: outside the pkgsrc-handled tree, <code class="varname">LOCALBASE</code>.</p></li>
6925: <li class="listitem"><p>Automatic handling of configuration files during installation,
6926: provided that packages are correctly designed.</p></li>
6927: <li class="listitem"><p>Generation and installation of system startup scripts.</p></li>
6928: <li class="listitem"><p>Registration of system users and groups.</p></li>
6929: <li class="listitem"><p>Registration of system shells.</p></li>
6930: <li class="listitem"><p>Automatic updating of fonts databases.</p></li>
6931: </ul></div>
6932: <p>The following sections inspect each of the above points in detail.</p>
6933: <p>You may be thinking that many of the things described here could be
6934: easily done with simple code in the package's post-installation target
6935: (<code class="literal">post-install</code>). <span class="emphasis"><em>This is incorrect</em></span>,
6936: as the code in them is only executed when building from source. Machines
6937: using binary packages could not benefit from it at all (as the code itself
6938: could be unavailable). Therefore, the only way to achieve any of the items
6939: described above is by means of the installation scripts, which are
6940: automatically generated by pkginstall.</p>
1.41 asau 6941: <div class="sect1">
1.1 dsieger 6942: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 6943: <a name="files-and-dirs-outside-prefix"></a>20.1. Files and directories outside the installation prefix</h2></div></div></div>
6944: <p>As you already know, the <code class="filename">PLIST</code> file holds a list
6945: of files and directories that belong to a package. The names used in it
6946: are relative to the installation prefix (<code class="filename">${PREFIX}</code>),
6947: which means that it cannot register files outside this directory (absolute
6948: path names are not allowed). Despite this restriction, some packages need
6949: to install files outside this location; e.g., under
6950: <code class="filename">${VARBASE}</code> or
6951: <code class="filename">${PKG_SYSCONFDIR}</code>. The only way to achieve this
6952: is to create such files during installation time by using
6953: installation scripts.</p>
6954: <p>The generic installation scripts are shell scripts that can
6955: contain arbitrary code. The list of scripts to execute is taken from
6956: the <code class="varname">INSTALL_FILE</code> variable, which defaults to
6957: <code class="filename">INSTALL</code>. A similar variable exists for package
6958: removal (<code class="varname">DEINSTALL_FILE</code>, whose default is
6959: <code class="filename">DEINSTALL</code>). These scripts can run arbitrary
6960: commands, so they have the potential to create and manage files
6961: anywhere in the file system.</p>
6962: <p>Using these general installation files is not recommended, but
6963: may be needed in some special cases. One reason for avoiding them is
6964: that the user has to trust the packager that there is no unwanted or
6965: simply erroneous code included in the installation script. Also,
6966: previously there were many similar scripts for the same functionality,
6967: and fixing a common error involved finding and changing all of
6968: them.</p>
6969: <p>The pkginstall framework offers another, standardized way. It
6970: provides generic scripts to abstract the manipulation of such files
6971: and directories based on variables set in the package's
6972: <code class="filename">Makefile</code>. The rest of this section describes
6973: these variables.</p>
6974: <div class="sect2">
6975: <div class="titlepage"><div><div><h3 class="title">
6976: <a name="dirs-outside-prefix"></a>20.1.1. Directory manipulation</h3></div></div></div>
6977: <p>The following variables can be set to request the creation of
6978: directories anywhere in the file system:</p>
6979: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
6980: <li class="listitem">
6981: <p><code class="varname">MAKE_DIRS</code> and <code class="varname">OWN_DIRS</code>
6982: contain a list of directories that should be created and should attempt
6983: to be destroyed by the installation scripts. The difference between
6984: the two is that the latter prompts the administrator to remove any
6985: directories that may be left after deinstallation (because they were
6986: not empty), while the former does not. Example:</p>
6987: <pre class="programlisting">
6988: MAKE_DIRS+= ${VARBASE}/foo/private
6989: </pre>
6990: </li>
6991: <li class="listitem">
6992: <p><code class="varname">MAKE_DIRS_PERMS</code> and
6993: <code class="varname">OWN_DIRS_PERMS</code> contain a list of tuples describing
6994: which directories should be created and should attempt to be destroyed
6995: by the installation scripts. Each tuple holds the following values,
6996: separated by spaces: the directory name, its owner, its group and its
6997: numerical mode. For example:</p>
6998: <pre class="programlisting">
6999: MAKE_DIRS_PERMS+= ${VARBASE}/foo/private \
7000: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
7001: </pre>
7002: <p>The difference between the two is exactly the same as their
7003: non-<code class="varname">PERMS</code> counterparts.</p>
7004: </li>
7005: </ul></div>
1.1 dsieger 7006: </div>
1.184 rillig 7007: <div class="sect2">
7008: <div class="titlepage"><div><div><h3 class="title">
7009: <a name="files-outside-prefix"></a>20.1.2. File manipulation</h3></div></div></div>
7010: <p>Creating non-empty files outside the installation prefix is tricky
7011: because the <code class="filename">PLIST</code> forces all files to be inside it.
7012: To overcome this problem, the only solution is to extract the file in the
7013: known place (i.e., inside the installation prefix) and copy it to the
7014: appropriate location during installation (done by the installation scripts
7015: generated by pkginstall). We will call the former the <span class="emphasis"><em>master
7016: file</em></span> in the following paragraphs, which describe the variables
7017: that can be used to automatically and consistently handle files outside the
7018: installation prefix:</p>
7019: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7020: <li class="listitem">
7021: <p><code class="varname">CONF_FILES</code> and
7022: <code class="varname">REQD_FILES</code> are pairs of master and target files.
7023: During installation time, the master file is copied to the target one
7024: if and only if the latter does not exist. Upon deinstallation, the
7025: target file is removed provided that it was not modified by the
7026: installation.</p>
7027: <p>The difference between the two is that the latter prompts the
7028: administrator to remove any files that may be left after
7029: deinstallation (because they were not empty), while the former does
7030: not.</p>
7031: </li>
7032: <li class="listitem">
7033: <p><code class="varname">CONF_FILES_PERMS</code> and
7034: <code class="varname">REQD_FILES_PERMS</code> contain tuples describing master
7035: files as well as their target locations. For each of them, it also
7036: specifies their owner, their group and their numeric permissions, in
7037: this order. For example:</p>
1.1 dsieger 7038: <pre class="programlisting">
1.184 rillig 7039: REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile \
7040: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
1.1 dsieger 7041: </pre>
1.184 rillig 7042: <p>The difference between the two is exactly the same as their
7043: non-<code class="varname">PERMS</code> counterparts.</p>
7044: </li>
7045: </ul></div>
7046: </div>
1.1 dsieger 7047: </div>
1.41 asau 7048: <div class="sect1">
1.1 dsieger 7049: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7050: <a name="conf-files"></a>20.2. Configuration files</h2></div></div></div>
7051: <p>Configuration files are special in the sense that they are installed
7052: in their own specific directory, <code class="varname">PKG_SYSCONFDIR</code>, and
7053: need special treatment during installation (most of which is automated by
7054: pkginstall). The main concept you must bear in mind is that files marked
7055: as configuration files are automatically copied to the right place (somewhere
7056: inside <code class="varname">PKG_SYSCONFDIR</code>) during installation <span class="emphasis"><em>if
7057: and only if</em></span> they didn't exist before. Similarly, they will not
7058: be removed if they have local modifications. This ensures that
7059: administrators never lose any custom changes they may have made.</p>
7060: <div class="sect2">
7061: <div class="titlepage"><div><div><h3 class="title">
7062: <a name="conf-files-sysconfdir"></a>20.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</h3></div></div></div>
7063: <p>As said before, the <code class="varname">PKG_SYSCONFDIR</code> variable
7064: specifies where configuration files shall be installed. Its contents are
7065: set based upon the following variables:</p>
7066: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7067: <li class="listitem"><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root
7068: directory. Defaults to <code class="filename">${PREFIX}/etc</code> although it may
7069: be overridden by the user to point to his preferred location (e.g.,
7070: <code class="filename">/etc</code>, <code class="filename">/etc/pkg</code>, etc.).
7071: Packages must not use it directly.</p></li>
7072: <li class="listitem">
7073: <p><code class="varname">PKG_SYSCONFSUBDIR</code>: A subdirectory of
7074: <code class="varname">PKG_SYSCONFBASE</code> under which the configuration files
7075: for the package being built shall be installed. The definition of this
7076: variable only makes sense in the package's
7077: <code class="filename">Makefile</code> (i.e., it is not user-customizable).</p>
7078: <p>As an example, consider the Apache package,
1.207 leot 7079: <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 7080: configuration files under the
7081: <code class="filename">httpd/</code> subdirectory of
7082: <code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package
7083: Makefile.</p>
7084: </li>
7085: <li class="listitem"><p><code class="varname">PKG_SYSCONFVAR</code>: Specifies the name of the
7086: variable that holds this package's configuration directory (if
7087: different from <code class="varname">PKG_SYSCONFBASE</code>). It defaults to
7088: <code class="varname">PKGBASE</code>'s value, and is always prefixed with
7089: <code class="literal">PKG_SYSCONFDIR</code>.</p></li>
7090: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>: Holds the
7091: directory where the configuration files for the package identified by
7092: <code class="varname">PKG_SYSCONFVAR</code>'s shall be placed.</p></li>
7093: </ul></div>
7094: <p>Based on the above variables, pkginstall determines the value of
7095: <code class="varname">PKG_SYSCONFDIR</code>, which is the <span class="emphasis"><em>only</em></span>
7096: variable that can be used within a package to refer to its configuration
7097: directory. The algorithm used to set its value is basically the
7098: following:</p>
7099: <div class="orderedlist"><ol class="orderedlist" type="1">
7100: <li class="listitem"><p>If <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> is set,
7101: its value is used.</p></li>
7102: <li class="listitem"><p>If the previous variable is not defined but
7103: <code class="varname">PKG_SYSCONFSUBDIR</code> is set in the package's
7104: <code class="filename">Makefile</code>, the resulting value is
7105: <code class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li>
7106: <li class="listitem"><p>Otherwise, it is set to
7107: <code class="filename">${PKG_SYSCONFBASE}</code>.</p></li>
7108: </ol></div>
7109: <p>It is worth mentioning that <code class="filename">${PKG_SYSCONFDIR}</code> is
7110: automatically added to <code class="filename">OWN_DIRS</code>. See <a class="xref" href="#dirs-outside-prefix" title="20.1.1. Directory manipulation">Section 20.1.1, “Directory manipulation”</a> what this means. This does not apply to
7111: subdirectories of <code class="filename">${PKG_SYSCONFDIR}</code>, they still have to
7112: be created with OWN_DIRS or MAKE_DIRS.</p>
7113: </div>
7114: <div class="sect2">
7115: <div class="titlepage"><div><div><h3 class="title">
7116: <a name="conf-files-configure"></a>20.2.2. Telling the software where configuration files are</h3></div></div></div>
7117: <p>Given that pkgsrc (and users!) expect configuration files to be in a
7118: known place, you need to teach each package where it shall install its
7119: files. In some cases you will have to patch the package Makefiles to
7120: achieve it. If you are lucky, though, it may be as easy as passing an
7121: extra flag to the configuration script; this is the case of GNU Autoconf-
7122: generated files:</p>
1.1 dsieger 7123: <pre class="programlisting">
1.184 rillig 7124: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
1.1 dsieger 7125: </pre>
1.184 rillig 7126: <p>Note that this specifies where the package has to <span class="emphasis"><em>look
7127: for</em></span> its configuration files, not where they will be originally
7128: installed (although the difference is never explicit,
7129: unfortunately).</p>
1.1 dsieger 7130: </div>
1.184 rillig 7131: <div class="sect2">
7132: <div class="titlepage"><div><div><h3 class="title">
7133: <a name="conf-files-patching"></a>20.2.3. Patching installations</h3></div></div></div>
7134: <p>As said before, pkginstall automatically handles configuration files.
7135: This means that <span class="strong"><strong>the packages themselves must not
7136: touch the contents of <code class="filename">${PKG_SYSCONFDIR}</code>
7137: directly</strong></span>. Bad news is that many software installation scripts
7138: will, out of the box, mess with the contents of that directory. So what is
7139: the correct procedure to fix this issue?</p>
7140: <p>You must teach the package (usually by manually patching it) to
7141: install any configuration files under the examples hierarchy,
7142: <code class="filename">share/examples/${PKGBASE}/</code>. This way, the
7143: <code class="filename">PLIST</code> registers them and the administrator always
7144: has the original copies available.</p>
7145: <p>Once the required configuration files are in place (i.e., under the
7146: examples hierarchy), the pkginstall framework can use them as master copies
7147: during the package installation to update what is in
7148: <code class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables
7149: <code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are
7150: used. Check out <a class="xref" href="#files-outside-prefix" title="20.1.2. File manipulation">Section 20.1.2, “File manipulation”</a> for information
7151: about their syntax and their purpose. Here is an example, taken from the
1.207 leot 7152: <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/index.html" target="_top"><code class="filename">mail/mutt</code></a> package:</p>
1.1 dsieger 7153: <pre class="programlisting">
1.184 rillig 7154: EGDIR= ${PREFIX}/share/doc/mutt/samples
7155: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
1.1 dsieger 7156: </pre>
1.184 rillig 7157: <p>Note that the <code class="varname">EGDIR</code> variable is specific to that
7158: package and has no meaning outside it.</p>
1.1 dsieger 7159: </div>
1.184 rillig 7160: <div class="sect2">
7161: <div class="titlepage"><div><div><h3 class="title">
7162: <a name="conf-files-disable"></a>20.2.4. Disabling handling of configuration files</h3></div></div></div>
7163: <p>The automatic copying of config files can be toggled by setting the
7164: environment variable <code class="varname">PKG_CONFIG</code> prior to package
7165: installation.</p>
1.1 dsieger 7166: </div>
7167: </div>
1.41 asau 7168: <div class="sect1">
1.1 dsieger 7169: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7170: <a name="rcd-scripts"></a>20.3. System startup scripts</h2></div></div></div>
7171: <p>System startup scripts are special files because they must be
7172: installed in a place known by the underlying OS, usually outside the
7173: 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
7174: can be used. However, pkginstall provides a special mechanism to handle
7175: these files.</p>
7176: <p>In order to provide system startup scripts, the package has
7177: to:</p>
7178: <div class="orderedlist"><ol class="orderedlist" type="1">
7179: <li class="listitem"><p>Store the script inside <code class="filename">${FILESDIR}</code>, with
7180: the <code class="literal">.sh</code> suffix appended. Considering the
1.223 nia 7181: <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
7182: has a <code class="filename">cupsd.sh</code> in its files directory.</p></li>
1.184 rillig 7183: <li class="listitem">
7184: <p>Tell pkginstall to handle it, appending the name of the script,
7185: without its extension, to the <code class="varname">RCD_SCRIPTS</code> variable.
7186: Continuing the previous example:</p>
7187: <pre class="programlisting">
7188: RCD_SCRIPTS+= cupsd
7189: </pre>
7190: </li>
7191: </ol></div>
7192: <p>Once this is done, pkginstall will do the following steps for each
7193: script in an automated fashion:</p>
7194: <div class="orderedlist"><ol class="orderedlist" type="1">
7195: <li class="listitem"><p>Process the file found in the files directory applying all the
7196: substitutions described in the <code class="filename">FILES_SUBST</code>
7197: variable.</p></li>
7198: <li class="listitem"><p>Copy the script from the files directory to the examples
7199: hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>. Note
7200: that this master file must be explicitly registered in the
7201: <code class="filename">PLIST</code>.</p></li>
7202: <li class="listitem"><p>Add code to the installation scripts to copy the startup script
7203: from the examples hierarchy into the system-wide startup scripts
7204: directory.</p></li>
7205: </ol></div>
7206: <div class="sect2">
7207: <div class="titlepage"><div><div><h3 class="title">
7208: <a name="rcd-scripts-disable"></a>20.3.1. Disabling handling of system startup scripts</h3></div></div></div>
7209: <p>The automatic copying of config files can be toggled by setting the
7210: environment variable <code class="varname">PKG_RCD_SCRIPTS</code> prior to package
7211: installation. Note that the scripts will be always copied inside the
7212: examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>, no
7213: matter what the value of this variable is.</p>
1.1 dsieger 7214: </div>
7215: </div>
1.184 rillig 7216: <div class="sect1">
7217: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
7218: <a name="users-and-groups"></a>20.4. System users and groups</h2></div></div></div>
7219: <p>If a package needs to create special users and/or groups during
7220: installation, it can do so by using the pkginstall framework.</p>
7221: <p>Users can be created by adding entries to the
7222: <code class="varname">PKG_USERS</code> variable. Each entry has the following
7223: syntax:</p>
7224: <pre class="programlisting">
7225: user:group
7226: </pre>
7227: <p>Further specification of user details may be done by setting
7228: per-user variables.
7229: <code class="varname">PKG_UID.<em class="replaceable"><code>user</code></em></code> is the
7230: numeric UID for the user.
7231: <code class="varname">PKG_GECOS.<em class="replaceable"><code>user</code></em></code> is the
7232: user's description or comment.
7233: <code class="varname">PKG_HOME.<em class="replaceable"><code>user</code></em></code> is the
7234: user's home directory, and defaults to
7235: <code class="filename">/nonexistent</code> if not specified.
7236: <code class="varname">PKG_SHELL.<em class="replaceable"><code>user</code></em></code> is the
7237: user's shell, and defaults to <code class="filename">/sbin/nologin</code> if
7238: not specified.</p>
7239: <p>Similarly, groups can be created by adding entries to the
7240: <code class="varname">PKG_GROUPS</code> variable, whose syntax is:</p>
7241: <pre class="programlisting">
7242: group
7243: </pre>
7244: <p>The numeric GID of the group may be set by defining
7245: <code class="varname">PKG_GID.<em class="replaceable"><code>group</code></em></code>.</p>
7246: <p>If a package needs to create the users and groups at an earlier
7247: stage, then it can set <code class="varname">USERGROUP_PHASE</code> to either
7248: <code class="literal">configure</code>,<code class="literal">build</code>, or
7249: <code class="literal">pre-install</code> to indicate the phase before which the
7250: users and groups are created. In this case, the numeric UIDs and GIDs
7251: of the created users and groups are automatically hardcoded into the
7252: final installation scripts.</p>
1.1 dsieger 7253: </div>
1.41 asau 7254: <div class="sect1">
1.1 dsieger 7255: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7256: <a name="shells"></a>20.5. System shells</h2></div></div></div>
7257: <p>Packages that install system shells should register them in the shell
7258: database, <code class="filename">/etc/shells</code>, to make things easier to the
7259: administrator. This must be done from the installation scripts to keep
7260: binary packages working on any system. pkginstall provides an easy way to
7261: accomplish this task.</p>
7262: <p>When a package provides a shell interpreter, it has to set the
7263: <code class="varname">PKG_SHELL</code> variable to its absolute file name. This will
7264: add some hooks to the installation scripts to handle it. Consider the
1.207 leot 7265: 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 7266: <pre class="programlisting">
7267: PKG_SHELL= ${PREFIX}/bin/zsh
7268: </pre>
7269: <div class="sect2">
7270: <div class="titlepage"><div><div><h3 class="title">
7271: <a name="shells-disable"></a>20.5.1. Disabling shell registration</h3></div></div></div>
7272: <p>The automatic registration of shell interpreters can be disabled by
7273: the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</code>
7274: environment variable to <code class="literal">NO</code>.</p>
7275: </div>
1.1 dsieger 7276: </div>
1.41 asau 7277: <div class="sect1">
1.1 dsieger 7278: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 7279: <a name="fonts"></a>20.6. Fonts</h2></div></div></div>
7280: <p>Packages that install X11 fonts should update the database files
7281: that index the fonts within each fonts directory. This can easily be
7282: accomplished within the pkginstall framework.</p>
7283: <p>When a package installs X11 fonts, it must list the directories in
7284: which fonts are installed in the
7285: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code> variables,
7286: where <em class="replaceable"><code>type</code></em> can be one of <span class="quote">“<span class="quote">ttf</span>”</span>,
7287: <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
7288: installation scripts to run the appropriate commands to update the fonts
7289: database files within each of those directories. For convenience, if the
7290: directory path is relative, it is taken to be relative to the package's
1.207 leot 7291: 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 7292: <pre class="programlisting">
1.184 rillig 7293: FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
1.1 dsieger 7294: </pre>
1.184 rillig 7295: <div class="sect2">
7296: <div class="titlepage"><div><div><h3 class="title">
7297: <a name="fonts-disable"></a>20.6.1. Disabling automatic update of the fonts databases</h3></div></div></div>
7298: <p>The automatic update of fonts databases can be disabled by
7299: the administrator by setting the <code class="filename">PKG_UPDATE_FONTS_DB</code>
7300: environment variable to <code class="literal">NO</code>.</p>
1.1 dsieger 7301: </div>
7302: </div>
7303: </div>
1.41 asau 7304: <div class="chapter">
1.1 dsieger 7305: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 7306: <a name="fixes"></a>Chapter 21. Making your package work</h2></div></div></div>
1.1 dsieger 7307: <div class="toc">
7308: <p><b>Table of Contents</b></p>
1.100 leot 7309: <dl class="toc">
1.154 rillig 7310: <dt><span class="sect1"><a href="#general-operation">21.1. General operation</a></span></dt>
1.1 dsieger 7311: <dd><dl>
1.154 rillig 7312: <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>
7313: <dt><span class="sect2"><a href="#user-interaction">21.1.2. User interaction</a></span></dt>
7314: <dt><span class="sect2"><a href="#handling-licenses">21.1.3. Handling licenses</a></span></dt>
7315: <dt><span class="sect2"><a href="#restricted-packages">21.1.4. Restricted packages</a></span></dt>
7316: <dt><span class="sect2"><a href="#dependencies">21.1.5. Handling dependencies</a></span></dt>
7317: <dt><span class="sect2"><a href="#conflicts">21.1.6. Handling conflicts with other packages</a></span></dt>
7318: <dt><span class="sect2"><a href="#not-building-packages">21.1.7. Packages that cannot or should not be built</a></span></dt>
7319: <dt><span class="sect2"><a href="#undeletable-packages">21.1.8. Packages which should not be deleted, once installed</a></span></dt>
7320: <dt><span class="sect2"><a href="#security-handling">21.1.9. Handling packages with security problems</a></span></dt>
7321: <dt><span class="sect2"><a href="#bumping-pkgrevision">21.1.10. How to handle incrementing versions when fixing an existing package</a></span></dt>
7322: <dt><span class="sect2"><a href="#fixes.subst">21.1.11. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
7323: </dl></dd>
7324: <dt><span class="sect1"><a href="#fixes.fetch">21.2. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
7325: <dd><dl>
7326: <dt><span class="sect2"><a href="#no-plain-download">21.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
7327: <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>
7328: <dt><span class="sect2"><a href="#build.fetch.github">21.2.3. Packages hosted on github.com</a></span></dt>
7329: </dl></dd>
7330: <dt><span class="sect1"><a href="#fixes.configure">21.3. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
7331: <dd><dl>
7332: <dt><span class="sect2"><a href="#fixes.libtool">21.3.1. Shared libraries - libtool</a></span></dt>
7333: <dt><span class="sect2"><a href="#using-libtool">21.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
7334: <dt><span class="sect2"><a href="#autoconf-automake">21.3.3. GNU Autoconf/Automake</a></span></dt>
1.223 nia 7335: <dt><span class="sect2"><a href="#meson">21.3.4. Meson / ninja</a></span></dt>
1.154 rillig 7336: </dl></dd>
7337: <dt><span class="sect1"><a href="#programming-languages">21.4. Programming languages</a></span></dt>
7338: <dd><dl>
7339: <dt><span class="sect2"><a href="#basic-programming-languages">21.4.1. C, C++, and Fortran</a></span></dt>
7340: <dt><span class="sect2"><a href="#java-programming-language">21.4.2. Java</a></span></dt>
1.205 wiz 7341: <dt><span class="sect2"><a href="#go-programming-language">21.4.3. Go</a></span></dt>
1.223 nia 7342: <dt><span class="sect2"><a href="#rust-programming-language">21.4.4. Rust</a></span></dt>
7343: <dt><span class="sect2"><a href="#perl-scripts">21.4.5. Packages containing Perl scripts</a></span></dt>
7344: <dt><span class="sect2"><a href="#shell-scripts">21.4.6. Packages containing shell scripts</a></span></dt>
7345: <dt><span class="sect2"><a href="#other-programming-languages">21.4.7. Other programming languages</a></span></dt>
1.154 rillig 7346: </dl></dd>
7347: <dt><span class="sect1"><a href="#fixes.build">21.5. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
7348: <dd><dl>
7349: <dt><span class="sect2"><a href="#fixes.build.cpp">21.5.1. Compiling C and C++ code conditionally</a></span></dt>
7350: <dt><span class="sect2"><a href="#compiler-bugs">21.5.2. How to handle compiler bugs</a></span></dt>
1.172 rillig 7351: <dt><span class="sect2"><a href="#fixes.build.header">21.5.3. No such file or directory</a></span></dt>
7352: <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>
7353: <dt><span class="sect2"><a href="#out-of-memory">21.5.5. Running out of memory</a></span></dt>
1.154 rillig 7354: </dl></dd>
7355: <dt><span class="sect1"><a href="#fixes.install">21.6. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
7356: <dd><dl>
7357: <dt><span class="sect2"><a href="#install-scripts">21.6.1. Creating needed directories</a></span></dt>
7358: <dt><span class="sect2"><a href="#where-to-install-documentation">21.6.2. Where to install documentation</a></span></dt>
7359: <dt><span class="sect2"><a href="#installing-score-files">21.6.3. Installing highscore files</a></span></dt>
7360: <dt><span class="sect2"><a href="#destdir-support">21.6.4. Adding DESTDIR support to packages</a></span></dt>
7361: <dt><span class="sect2"><a href="#hardcoded-paths">21.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
1.203 nia 7362: <dt><span class="sect2"><a href="#perl-modules">21.6.6. Packages installing Perl modules</a></span></dt>
1.154 rillig 7363: <dt><span class="sect2"><a href="#faq.info-files">21.6.7. Packages installing info files</a></span></dt>
7364: <dt><span class="sect2"><a href="#manpages">21.6.8. Packages installing man pages</a></span></dt>
1.203 nia 7365: <dt><span class="sect2"><a href="#x11-fonts">21.6.9. Packages installing X11 fonts</a></span></dt>
7366: <dt><span class="sect2"><a href="#sgml-xml-data">21.6.10. Packages installing SGML or XML data</a></span></dt>
7367: <dt><span class="sect2"><a href="#mime-database">21.6.11. Packages installing extensions to the MIME database</a></span></dt>
7368: <dt><span class="sect2"><a href="#intltool">21.6.12. Packages using intltool</a></span></dt>
7369: <dt><span class="sect2"><a href="#startup-scripts">21.6.13. Packages installing startup scripts</a></span></dt>
7370: <dt><span class="sect2"><a href="#tex-packages">21.6.14. Packages installing TeX modules</a></span></dt>
7371: <dt><span class="sect2"><a href="#emulation-packages">21.6.15. Packages supporting running binaries in
1.1 dsieger 7372: emulation</a></span></dt>
1.203 nia 7373: <dt><span class="sect2"><a href="#hicolor-theme">21.6.16. Packages installing hicolor icons</a></span></dt>
7374: <dt><span class="sect2"><a href="#desktop-files">21.6.17. Packages installing desktop files</a></span></dt>
1.1 dsieger 7375: </dl></dd>
1.154 rillig 7376: <dt><span class="sect1"><a href="#punting">21.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 7377: </dl>
7378: </div>
1.41 asau 7379: <div class="sect1">
1.1 dsieger 7380: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 7381: <a name="general-operation"></a>21.1. General operation</h2></div></div></div>
1.1 dsieger 7382: <p>One appealing feature of pkgsrc is that it runs on many
1.108 rillig 7383: different platforms. As a result, it is important to ensure,
7384: where possible, that packages in pkgsrc are portable. This
7385: chapter mentions some particular details you should pay
7386: attention to while working on pkgsrc.</p>
1.41 asau 7387: <div class="sect2">
1.1 dsieger 7388: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7389: <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 7390: </h3></div></div></div>
7391: <p>The pkgsrc user can configure pkgsrc by overriding several
7392: variables in the file pointed to by <code class="varname">MAKECONF</code>,
1.10 hubertf 7393: which is <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> by default. When you
1.1 dsieger 7394: want to use those variables in the preprocessor directives of
1.207 leot 7395: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> (for example <code class="literal">.if</code> or
1.1 dsieger 7396: <code class="literal">.for</code>), you need to include the file
7397: <code class="filename">../../mk/bsd.prefs.mk</code> before, which in turn
7398: loads the user preferences.</p>
7399: <p>But note that some variables may not be completely defined
7400: after <code class="filename">../../mk/bsd.prefs.mk</code> has been
7401: included, as they may contain references to variables that are
1.108 rillig 7402: not yet defined. In shell commands (the lines in
7403: <code class="filename">Makefile</code> that are indented with a tab) this
7404: is no problem, since variables are only expanded when they are
7405: used. But in the preprocessor directives mentioned above and in
7406: dependency lines (of the form <code class="literal">target:
1.1 dsieger 7407: dependencies</code>) the variables are expanded at load
7408: time.</p>
1.41 asau 7409: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 7410: <h3 class="title">Note</h3>
1.108 rillig 7411: <p>To check whether a variable can be used at load time,
7412: run <span class="command"><strong>pkglint -Wall</strong></span> on your package.</p>
1.1 dsieger 7413: </div>
7414: </div>
1.41 asau 7415: <div class="sect2">
1.1 dsieger 7416: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7417: <a name="user-interaction"></a>21.1.2. User interaction</h3></div></div></div>
1.1 dsieger 7418: <p>Occasionally, packages require interaction from the user,
7419: and this can be in a number of ways:</p>
1.41 asau 7420: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7421: <li class="listitem"><p>When fetching the distfiles, some packages require user
1.1 dsieger 7422: interaction such as entering username/password or accepting a
7423: license on a web page.</p></li>
1.23 wiz 7424: <li class="listitem"><p>When extracting the distfiles, some packages may ask for
1.1 dsieger 7425: passwords.</p></li>
1.23 wiz 7426: <li class="listitem"><p>help to configure the package before it is built</p></li>
7427: <li class="listitem"><p>help during the build process</p></li>
7428: <li class="listitem"><p>help during the installation of a package</p></li>
1.1 dsieger 7429: </ul></div>
1.108 rillig 7430: <p>A package can set the <code class="varname">INTERACTIVE_STAGE</code>
7431: variable to define which stages need interaction. This should be
7432: done in the package's <code class="filename">Makefile</code>, e.g.:</p>
1.1 dsieger 7433: <pre class="programlisting">
7434: INTERACTIVE_STAGE= configure install
1.111 sevan 7435: </pre>
1.1 dsieger 7436: <p>The user can then decide to skip this package by setting the
1.108 rillig 7437: <code class="varname">BATCH</code> variable. Packages that require interaction
7438: are also excluded from bulk builds.</p>
1.1 dsieger 7439: </div>
1.41 asau 7440: <div class="sect2">
1.1 dsieger 7441: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7442: <a name="handling-licenses"></a>21.1.3. Handling licenses</h3></div></div></div>
1.111 sevan 7443: <p>Authors of software can choose the licence under which software
7444: can be copied. The Free Software Foundation has declared some
7445: licenses "Free", and the Open Source Initiative has a definition of
7446: "Open Source".</p>
7447: <p>By default, pkgsrc allows packages with Free or Open Source
7448: licenses to be built. To allow packages with other licenses to be
7449: built as well, the pkgsrc user needs to add these licenses to the
7450: <code class="varname">ACCEPTABLE_LICENSES</code> variable in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. Note
7451: that this variable only affects which packages may be
7452: <span class="emphasis"><em>built</em></span>, while the license terms often also
7453: restrict the actual use of the package and its redistribution.</p>
1.1 dsieger 7454: <p>One might want to only install packages with a BSD license,
1.108 rillig 7455: or the GPL, and not the other. The free licenses are added to the
1.111 sevan 7456: default <code class="varname">ACCEPTABLE_LICENSES</code> variable. The pkgsrc
1.19 jnemeth 7457: user can override the default by setting the
7458: <code class="varname">ACCEPTABLE_LICENSES</code> variable with "=" instead
1.111 sevan 7459: of "+=". The licenses accepted by default are defined in the
7460: <code class="varname">DEFAULT_ACCEPTABLE_LICENSES</code> variable in the file
7461: <code class="filename">pkgsrc/mk/license.mk</code>.</p>
1.1 dsieger 7462: <p>The license tag mechanism is intended to address
7463: copyright-related issues surrounding building, installing and
7464: using a package, and not to address redistribution issues (see
7465: <code class="varname">RESTRICTED</code> and
1.111 sevan 7466: <code class="varname">NO_SRC_ON_FTP</code>, etc.).
1.19 jnemeth 7467: Packages with redistribution restrictions should set these
7468: tags.</p>
1.1 dsieger 7469: <p>Denoting that a package may be copied according to a
7470: particular license is done by placing the license in
7471: <code class="filename">pkgsrc/licenses</code> and setting the
7472: <code class="varname">LICENSE</code> variable to a string identifying the
1.207 leot 7473: 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 7474: <pre class="programlisting">
7475: LICENSE= xv-license
1.111 sevan 7476: </pre>
1.1 dsieger 7477: <p>When trying to build, the user will get a notice that the
7478: package is covered by a license which has not been placed in the
7479: <code class="varname">ACCEPTABLE_LICENSES</code> variable:</p>
7480: <pre class="programlisting">
7481: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
7482: ===> xv-3.10anb9 has an unacceptable license: xv-license.
7483: ===> To view the license, enter "/usr/bin/make show-license".
7484: ===> To indicate acceptance, add this line to your /etc/mk.conf:
7485: ===> ACCEPTABLE_LICENSES+=xv-license
7486: *** Error code 1
1.111 sevan 7487: </pre>
1.10 hubertf 7488: <p>The license can be viewed with <span class="command"><strong>make
1.1 dsieger 7489: show-license</strong></span>, and if the user so chooses, the line
1.10 hubertf 7490: printed above can be added to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.1 dsieger 7491: convey to pkgsrc that it should not in the future fail because of
7492: that license:</p>
7493: <pre class="programlisting">
7494: ACCEPTABLE_LICENSES+=xv-license
1.111 sevan 7495: </pre>
7496: <p>The use of <code class="varname">LICENSE=shareware</code>,
7497: <code class="varname">LICENSE=no-commercial-use</code>, and similar language
7498: is deprecated because it does not crisply refer to a particular
7499: license text. Another problem with such usage is that it does not
7500: enable a user to tell pkgsrc to proceed for a single package
7501: without also telling pkgsrc to proceed for all packages with that
7502: tag.</p>
7503: <div class="sect3">
7504: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 7505: <a name="new-license"></a>21.1.3.1. Adding a package with a new license</h4></div></div></div>
1.48 rodent 7506: <p>When adding a package with a new license, the following steps
7507: are required:</p>
7508: <div class="orderedlist"><ol class="orderedlist" type="1">
7509: <li class="listitem">
1.169 rillig 7510: <p>Check whether the license qualifies as Free or Open Source by
7511: referencing <a class="ulink" href="https://www.gnu.org/licenses/license-list.en.html" target="_top">Various
7512: Licenses and Comments about Them</a> and <a class="ulink" href="https://opensource.org/licenses/alphabetical" target="_top">Licenses by Name |
1.111 sevan 7513: Open Source Initiative</a>. If this is the case, the filename in
7514: <code class="filename">pkgsrc/licenses/</code> does not need the
7515: <code class="filename">-license</code> suffix, and the license name should be
7516: added to:</p>
1.48 rodent 7517: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.169 rillig 7518: <li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in
7519: <code class="filename">pkgsrc/mk/license.mk</code></p></li>
7520: <li class="listitem"><p>default_acceptable_licenses in
7521: <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
1.48 rodent 7522: </ul></div>
7523: </li>
1.169 rillig 7524: <li class="listitem"><p>The license text should be added to
7525: <code class="filename">pkgsrc/licenses</code> for displaying. A list of known
7526: licenses can be seen in this directory.</p></li>
1.48 rodent 7527: </ol></div>
1.111 sevan 7528: </div>
7529: <div class="sect3">
7530: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 7531: <a name="change-license"></a>21.1.3.2. Change to the license</h4></div></div></div>
1.1 dsieger 7532: <p>When the license changes (in a way other than formatting),
1.111 sevan 7533: make sure that the new license has a different name (e.g.,
1.1 dsieger 7534: append the version number if it exists, or the date). Just
7535: because a user told pkgsrc to build programs under a previous
7536: version of a license does not mean that pkgsrc should build
7537: programs under the new licenses. The higher-level point is that
7538: pkgsrc does not evaluate licenses for reasonableness; the only
7539: test is a mechanistic test of whether a particular text has been
1.111 sevan 7540: approved by either of two bodies (FSF or OSI).</p>
7541: </div>
1.1 dsieger 7542: </div>
1.41 asau 7543: <div class="sect2">
1.1 dsieger 7544: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7545: <a name="restricted-packages"></a>21.1.4. Restricted packages</h3></div></div></div>
1.1 dsieger 7546: <p>Some licenses restrict how software may be re-distributed.
1.111 sevan 7547: By declaring the restrictions, package tools can
1.1 dsieger 7548: automatically refrain from e.g. placing binary packages on FTP
7549: sites.</p>
1.111 sevan 7550: <p>There are four possible restrictions, which are
1.1 dsieger 7551: the cross product of sources (distfiles) and binaries not being
7552: placed on FTP sites and CD-ROMs. Because this is rarely the exact
7553: language in any license, and because non-Free licenses tend to be
7554: different from each other, pkgsrc adopts a definition of FTP and
1.111 sevan 7555: CD-ROM.
7556:
7557: "FTP" means making the source or binary file available over the
7558: Internet at no charge.
7559:
7560: "CD-ROM" means making the source or binary available on some kind of
7561: media, together with other source and binary packages, which is sold
7562: for a distribution charge.
1.1 dsieger 7563: </p>
7564: <p>In order to encode these restrictions, the package system
7565: defines five make variables that can be set to note these
7566: restrictions:</p>
1.41 asau 7567: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7568: <li class="listitem">
1.1 dsieger 7569: <p><code class="varname">RESTRICTED</code></p>
7570: <p>This variable should be set whenever a restriction
7571: exists (regardless of its kind). Set this variable to a
7572: string containing the reason for the restriction. It should
7573: be understood that those wanting to understand the restriction
7574: will have to read the license, and perhaps seek advice of
7575: counsel.</p>
7576: </li>
1.23 wiz 7577: <li class="listitem">
1.1 dsieger 7578: <p><code class="varname">NO_BIN_ON_CDROM</code></p>
7579: <p>Binaries may not be placed on CD-ROM containing other
7580: binary packages, for which a distribution charge may be made.
7581: In this case, set this variable to
7582: <code class="varname">${RESTRICTED}</code>.</p>
7583: </li>
1.23 wiz 7584: <li class="listitem">
1.1 dsieger 7585: <p><code class="varname">NO_BIN_ON_FTP</code></p>
7586: <p>Binaries may not made available on the Internet without
7587: charge. In this case, set this variable to
7588: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7589: binary packages will not be included on ftp.NetBSD.org.</p>
7590: </li>
1.23 wiz 7591: <li class="listitem">
1.1 dsieger 7592: <p><code class="varname">NO_SRC_ON_CDROM</code></p>
7593: <p>Distfiles may not be placed on CD-ROM, together with
7594: other distfiles, for which a fee may be charged. In this
7595: case, set this variable to <code class="varname">${RESTRICTED}</code>.
7596: </p>
7597: </li>
1.23 wiz 7598: <li class="listitem">
1.1 dsieger 7599: <p><code class="varname">NO_SRC_ON_FTP</code></p>
7600: <p>Distfiles may not made available via FTP at no charge.
7601: In this case, set this variable to
7602: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7603: the distfile(s) will not be mirrored on ftp.NetBSD.org.</p>
7604: </li>
7605: </ul></div>
1.111 sevan 7606: <p>Please note that packages will be removed from pkgsrc when the
7607: distfiles are not distributable and cannot be obtained for a period
7608: of one full quarter branch. Packages with manual/interactive fetch
7609: must have a maintainer and it is his/her responsibility to ensure
7610: this.</p>
1.1 dsieger 7611: </div>
1.41 asau 7612: <div class="sect2">
1.1 dsieger 7613: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7614: <a name="dependencies"></a>21.1.5. Handling dependencies</h3></div></div></div>
1.175 gutterid 7615: <p>Your package may depend on some other package being present,
7616: and there are various ways of expressing this dependency.
7617: pkgsrc supports the <code class="varname">DEPENDS</code>,
7618: <code class="varname">BUILD_DEPENDS</code>,
7619: <code class="varname">TOOL_DEPENDS</code>, and
7620: <code class="varname">TEST_DEPENDS</code> definitions, the
1.1 dsieger 7621: <code class="varname">USE_TOOLS</code> definition, as well as dependencies
7622: via <code class="filename">buildlink3.mk</code>, which is the preferred way
7623: to handle dependencies, and which uses the variables named above.
1.184 rillig 7624: 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 7625: <p>The basic difference is that the <code class="varname">DEPENDS</code>
7626: definition registers that pre-requisite in the binary package so it
7627: will be pulled in when the binary package is later installed, whilst
7628: the <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7629: and <code class="varname">TEST_DEPENDS</code> definitions do not, marking a
7630: dependency that is only needed for building or testing the resulting
1.184 rillig 7631: 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 7632: <p>This means that if you only need a package present whilst
1.175 gutterid 7633: you are building or testing, it should be noted as a
7634: <code class="varname">TOOL_DEPENDS</code>,
7635: <code class="varname">BUILD_DEPENDS</code>, or
7636: <code class="varname">TEST_DEPENDS</code>. When cross-compiling,
1.156 leot 7637: <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
7638: packages, i.e. packages for the architecture where the package
7639: is built;
7640: <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
1.175 gutterid 7641: packages, i.e., packages for the architecture for which the package
1.156 leot 7642: is built.</p>
1.175 gutterid 7643: <p>The format for a <code class="varname">DEPENDS</code>,
7644: <code class="varname">BUILD_DEPENDS</code>, <code class="varname">TOOL_DEPENDS</code>,
7645: and <code class="varname">TEST_DEPENDS</code> definition is:</p>
1.1 dsieger 7646: <pre class="programlisting">
7647: <pre-req-package-name>:../../<category>/<pre-req-package>
1.111 sevan 7648: </pre>
1.23 wiz 7649: <p>Please note that the <span class="quote">“<span class="quote">pre-req-package-name</span>”</span>
1.1 dsieger 7650: may include any of the wildcard version numbers recognized by
1.207 leot 7651: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_info.1"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
1.23 wiz 7652: <div class="orderedlist"><ol class="orderedlist" type="1">
7653: <li class="listitem">
1.1 dsieger 7654: <p>If your package needs another package's binaries or
1.54 wiz 7655: libraries to build and run, and if that package has a
1.1 dsieger 7656: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7657: <pre class="programlisting">
7658: .include "../../graphics/jpeg/buildlink3.mk"
1.111 sevan 7659: </pre>
1.1 dsieger 7660: </li>
1.23 wiz 7661: <li class="listitem">
1.54 wiz 7662: <p>If your package needs another package's binaries or
7663: libraries only for building, and if that package has a
7664: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7665: <pre class="programlisting">
7666: .include "../../graphics/jpeg/buildlink3.mk"
1.111 sevan 7667: </pre>
1.54 wiz 7668: <p>but set
7669: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>jpeg</code></em>?=build</code>
7670: to make it a build dependency only. This case is rather
7671: rare.</p>
7672: </li>
7673: <li class="listitem">
1.25 spz 7674: <p>If your package needs binaries from another package to build,
1.156 leot 7675: use the <code class="varname">TOOL_DEPENDS</code> definition:</p>
1.1 dsieger 7676: <pre class="programlisting">
1.156 leot 7677: TOOL_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
1.111 sevan 7678: </pre>
1.1 dsieger 7679: </li>
1.156 leot 7680: <li class="listitem"><p>If your package needs static libraries to link against, header
7681: files to include, etc. from another package to build,
7682: use the <code class="varname">BUILD_DEPENDS</code> definition.</p></li>
1.25 spz 7683: <li class="listitem"><p>If your package needs a library with which to link and
7684: there is no <code class="filename">buildlink3.mk</code> file
7685: available, create one. Using
7686: <code class="varname">DEPENDS</code> won't be sufficient because the
7687: include files and libraries will be hidden from the compiler.</p></li>
1.23 wiz 7688: <li class="listitem">
1.25 spz 7689: <p>If your package needs some executable to be able to run
7690: correctly and if there's no
7691: <code class="filename">buildlink3.mk</code> file, this is specified
7692: using the <code class="varname">DEPENDS</code> variable. The
1.207 leot 7693: <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 7694: be able to execute the latex binary from the tex-latex-bin package
1.25 spz 7695: when it runs, and that is specified:</p>
1.1 dsieger 7696: <pre class="programlisting">
1.129 wiz 7697: DEPENDS+= tex-latex-bin-[0-9]*:../../print/tex-latex-bin
1.111 sevan 7698: </pre>
1.25 spz 7699: </li>
1.175 gutterid 7700: <li class="listitem"><p>If your package includes a test suite that has extra
7701: dependencies only required for this purpose (frequently this
7702: can be run as a <span class="quote">“<span class="quote">make test</span>”</span> target), use the
7703: <code class="varname">TEST_DEPENDS</code> variable.</p></li>
1.25 spz 7704: <li class="listitem">
7705: <p>You can use wildcards in package dependencies. Note that
7706: such wildcard dependencies are retained when creating binary
7707: packages. The dependency is checked when installing the binary
7708: package and any package which matches the pattern will be
7709: used. Wildcard dependencies should be used with care.</p>
1.23 wiz 7710: <p>The <span class="quote">“<span class="quote">-[0-9]*</span>”</span> should be used instead of
7711: <span class="quote">“<span class="quote">-*</span>”</span> to avoid potentially ambiguous matches
7712: such as <span class="quote">“<span class="quote">tk-postgresql</span>”</span> matching a
7713: <span class="quote">“<span class="quote">tk-*</span>”</span> <code class="varname">DEPENDS</code>.</p>
1.1 dsieger 7714: <p>Wildcards can also be used to specify that a package
7715: will only build against a certain minimum version of a
7716: pre-requisite:</p>
7717: <pre class="programlisting">
1.25 spz 7718: DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
1.111 sevan 7719: </pre>
1.25 spz 7720: <p>This means that the package will build using version 6.0
7721: of ImageMagick or newer. Such a dependency may be warranted
7722: if, for example, the command line options of an executable
7723: have changed.</p>
7724: <p>If you need to depend on minimum versions of libraries,
1.183 wiz 7725: set
7726: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
7727: to the appropriate pattern before including its
7728: <code class="filename">buildlink3.mk</code> file, e.g.</p>
7729: <pre class="programlisting">
7730: BUILDLINK_API_DEPENDS.jpeg+= jpeg>=9.0
7731: .include "../../graphics/jpeg/buildlink3.mk"
7732: </pre>
1.1 dsieger 7733: <p>For security fixes, please update the package
1.154 rillig 7734: 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 7735: information.</p>
7736: </li>
7737: </ol></div>
7738: <p>If your package needs files from another package to build,
7739: add the relevant distribution files to
7740: <code class="varname">DISTFILES</code>, so they will be extracted
1.207 leot 7741: 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 7742: (It relies on the jpeg sources being present in source form
7743: during the build.)</p>
7744: </div>
1.41 asau 7745: <div class="sect2">
1.1 dsieger 7746: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7747: <a name="conflicts"></a>21.1.6. Handling conflicts with other packages</h3></div></div></div>
1.226 gutterid 7748: <p>Your package may conflict with other packages users might
7749: already have installed on their system, e.g., if your package
1.1 dsieger 7750: installs the same set of files as another package in the pkgsrc
1.227 wiz 7751: tree.</p>
1.207 leot 7752: <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>
7753: 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 7754: install the same shared library, thus you set in
7755: <code class="filename">pkgsrc/x11/libXaw3d/Makefile</code>:</p>
7756: <pre class="programlisting">
7757: CONFLICTS= Xaw-Xpm-[0-9]*
7758: </pre>
7759: <p>and in <code class="filename">pkgsrc/x11/Xaw-Xpm/Makefile</code>:</p>
7760: <pre class="programlisting">
7761: CONFLICTS= libXaw3d-[0-9]*
7762: </pre>
1.207 leot 7763: <p><a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_add.1"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> is able to detect attempts to install packages
1.142 leot 7764: that conflict with existing packages and abort. However, in many
7765: situations this is too late in the process. Binary package managers
7766: will not know about the conflict until they attempt to install the
7767: package after already downloading it and all its dependencies.
7768: Users may also waste time building a package and its dependencies
7769: only to find out at the end that it conflicts with another package
7770: they have installed.</p>
7771: <p>To avoid these issues <code class="varname">CONFLICTS</code> entries
7772: should be added in all cases where it is known that packages conflict
7773: with each other. These <code class="varname">CONFLICTS</code> entries are
1.207 leot 7774: exported in <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> files and consumed by binary package
1.142 leot 7775: managers to inform users that packages cannot be installed onto
7776: the target system.</p>
1.1 dsieger 7777: </div>
1.41 asau 7778: <div class="sect2">
1.1 dsieger 7779: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7780: <a name="not-building-packages"></a>21.1.7. Packages that cannot or should not be built</h3></div></div></div>
1.1 dsieger 7781: <p>There are several reasons why a package might be
7782: instructed to not build under certain circumstances. If the
7783: package builds and runs on most platforms, the exceptions
1.83 dholland 7784: should be noted with <code class="varname">BROKEN_ON_PLATFORM</code>. If
7785: the package builds and runs on a small handful of platforms,
7786: set <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> instead.
7787: Both <code class="varname">BROKEN_ON_PLATFORM</code> and
7788: <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> are OS triples
7789: (OS-version-platform) that can use glob-style
7790: wildcards.</p>
7791: <p>If a package is not appropriate for some platforms (as
1.114 maya 7792: opposed to merely broken), a different set of variables should be
1.83 dholland 7793: used as this affects failure reporting and statistics.
7794: If the package is appropriate for most platforms, the exceptions
1.1 dsieger 7795: should be noted with <code class="varname">NOT_FOR_PLATFORM</code>. If
1.83 dholland 7796: the package is appropriate for only a small handful of platforms
7797: (often exactly one), set <code class="varname">ONLY_FOR_PLATFORM</code> instead.
1.1 dsieger 7798: Both <code class="varname">ONLY_FOR_PLATFORM</code> and
7799: <code class="varname">NOT_FOR_PLATFORM</code> are OS triples
7800: (OS-version-platform) that can use glob-style
7801: wildcards.</p>
7802: <p>Some packages are tightly bound to a specific version of an
1.207 leot 7803: 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 7804: backwards compatible with other versions of the OS, and should be
7805: uploaded to a version specific directory on the FTP server. Mark
7806: these packages by setting <code class="varname">OSVERSION_SPECIFIC</code> to
1.23 wiz 7807: <span class="quote">“<span class="quote">yes</span>”</span>. This variable is not currently used by any of
1.1 dsieger 7808: the package system internals, but may be used in the
7809: future.</p>
7810: <p>If the package should be skipped (for example, because it
7811: provides functionality already provided by the system), set
7812: <code class="varname">PKG_SKIP_REASON</code> to a descriptive message. If
7813: the package should fail because some preconditions are not met,
7814: set <code class="varname">PKG_FAIL_REASON</code> to a descriptive
7815: message.</p>
7816: </div>
1.41 asau 7817: <div class="sect2">
1.1 dsieger 7818: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7819: <a name="undeletable-packages"></a>21.1.8. Packages which should not be deleted, once installed</h3></div></div></div>
1.1 dsieger 7820: <p>To ensure that a package may not be deleted, once it has been
7821: installed, the <code class="varname">PKG_PRESERVE</code> definition should
7822: be set in the package Makefile. This will be carried into any
7823: binary package that is made from this pkgsrc entry. A
1.23 wiz 7824: <span class="quote">“<span class="quote">preserved</span>”</span> package will
1.207 leot 7825: not be deleted using <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_delete.1"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
1.23 wiz 7826: <span class="quote">“<span class="quote">-f</span>”</span> option is used.</p>
1.1 dsieger 7827: </div>
1.41 asau 7828: <div class="sect2">
1.1 dsieger 7829: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7830: <a name="security-handling"></a>21.1.9. Handling packages with security problems</h3></div></div></div>
1.1 dsieger 7831: <p>When a vulnerability is found, this should be noted in
1.205 wiz 7832: <code class="filename">localsrc/security/advisories/pkg-vulnerabilities</code>.
7833: Entries in that file consist of three parts:</p>
7834: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7835: <li class="listitem"><p>package version pattern</p></li>
7836: <li class="listitem"><p>type of vulnerability (please cut'n'paste an existing one where possible)</p></li>
7837: <li class="listitem"><p>URL providing additional information about the issue</p></li>
7838: </ul></div>
7839: <p>For the package version pattern please always use `<' to
7840: mark an upper bound (not `<='!). This will avoid possible
7841: problems due unrelated <code class="varname">PKGREVISION</code> bumps not
7842: related to security fixes. Lower bounds can be added too, using
7843: '>' or '>='. For example,
1.206 wiz 7844: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.2</code></span>”</span> would mark
1.205 wiz 7845: versions 1.0 (included) to 1.2 (excluded) of
7846: <span class="quote">“<span class="quote"><code class="literal">foo</code></span>”</span> as affected by the security
7847: issue.</p>
7848: <p>Entries should always be added at the bottom of the file.</p>
7849: <p>When fixing packages, please modify the upper bound of the
7850: corresponding entry. To continue the previous example, if a fix
7851: was backported to version 1.1nb2, change the previous pattern to
1.206 wiz 7852: <span class="quote">“<span class="quote"><code class="literal">foo>=1<1.1nb2</code></span>”</span>.</p>
1.205 wiz 7853: <p>To locally test a package version pattern against a
7854: <code class="varname">PKGNAME</code> you can use the <span class="command"><strong>pkg_admin
7855: pmatch</strong></span> command.</p>
7856: <p>The URL should be as permanent as possible and provide as
7857: much information about the issue as possible. CVE entries are
7858: preferred.</p>
7859: <p>After committing that file, ask pkgsrc-security@NetBSD.org to
1.31 wiz 7860: update the file on ftp.NetBSD.org.</p>
1.1 dsieger 7861: <p>After fixing the vulnerability by a patch, its
1.31 wiz 7862: <code class="varname">PKGREVISION</code> should be increased (this is of
7863: course not necessary if the problem is fixed by using a newer
7864: release of the software), and the pattern in the
7865: pkg-vulnerabilities file must be updated.</p>
1.1 dsieger 7866: <p>Also, if the fix should be applied to the stable pkgsrc
7867: branch, be sure to submit a pullup request!</p>
7868: <p>Binary packages already on ftp.NetBSD.org will be handled
7869: semi-automatically by a weekly cron job.</p>
1.205 wiz 7870: <p>In case a security issue is disputed, please contact
7871: pkgsrc-security@NetBSD.org.</p>
1.1 dsieger 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="bumping-pkgrevision"></a>21.1.10. How to handle incrementing versions when fixing an existing package</h3></div></div></div>
1.1 dsieger 7876: <p>When making fixes to an existing package it can be useful
7877: to change the version number in <code class="varname">PKGNAME</code>. To
7878: avoid conflicting with future versions by the original author, a
1.23 wiz 7879: <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 7880: on package versions by setting <code class="varname">PKGREVISION=1</code>
1.23 wiz 7881: (2, ...). The <span class="quote">“<span class="quote">nb</span>”</span> is treated like a
7882: <span class="quote">“<span class="quote">.</span>”</span> by the package tools. e.g.</p>
1.1 dsieger 7883: <pre class="programlisting">
7884: DISTNAME= foo-17.42
7885: PKGREVISION= 9
1.111 sevan 7886: </pre>
1.1 dsieger 7887: <p>will result in a <code class="varname">PKGNAME</code> of
1.23 wiz 7888: <span class="quote">“<span class="quote">foo-17.42nb9</span>”</span>. If you want to use the original
7889: value of <code class="varname">PKGNAME</code> without the <span class="quote">“<span class="quote">nbX</span>”</span>
1.1 dsieger 7890: suffix, e.g. for setting <code class="varname">DIST_SUBDIR</code>, use
7891: <code class="varname">PKGNAME_NOREV</code>.</p>
7892: <p>When a new release of the package is released, the
7893: <code class="varname">PKGREVISION</code> should be removed, e.g. on a new
7894: minor release of the above package, things should be like:</p>
7895: <pre class="programlisting">
7896: DISTNAME= foo-17.43
1.111 sevan 7897: </pre>
1.1 dsieger 7898: <p><code class="varname">PKGREVISION</code> should be incremented for any
7899: non-trivial change in the resulting binary package. Without a
7900: <code class="varname">PKGREVISION</code> bump, someone with the previous
7901: version installed has no way of knowing that their package is out
7902: of date. Thus, changes without increasing
7903: <code class="varname">PKGREVISION</code> are essentially labeled "this is so
7904: trivial that no reasonable person would want to upgrade", and this
7905: is the rough test for when increasing
7906: <code class="varname">PKGREVISION</code> is appropriate. Examples of
7907: changes that do not merit increasing
7908: <code class="varname">PKGREVISION</code> are:</p>
1.41 asau 7909: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7910: <li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>,
1.169 rillig 7911: <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>, or
7912: comments in Makefile.</p></li>
7913: <li class="listitem"><p>Changing build variables if the resulting binary
7914: package is the same.</p></li>
7915: <li class="listitem"><p>Changing
7916: <code class="filename">DESCR</code>.</p></li>
7917: <li class="listitem"><p>Adding <code class="varname">PKG_OPTIONS</code> if the
7918: default options don't change.</p></li>
1.1 dsieger 7919: </ul></div>
7920: <p>Examples of changes that do merit an increase to
7921: <code class="varname">PKGREVISION</code> include:</p>
1.41 asau 7922: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.169 rillig 7923: <li class="listitem"><p>Security fixes</p></li>
7924: <li class="listitem"><p>Changes or additions to a patch
7925: file</p></li>
7926: <li class="listitem"><p>Changes to the
7927: <code class="filename">PLIST</code></p></li>
7928: <li class="listitem"><p>A dependency is changed or
7929: renamed.</p></li>
1.1 dsieger 7930: </ul></div>
7931: <p>PKGREVISION must also be incremented when dependencies have ABI
7932: changes.</p>
7933: </div>
1.41 asau 7934: <div class="sect2">
1.1 dsieger 7935: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 7936: <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 7937: <p>When you want to replace the same text in multiple files, or
7938: multiple times in the same file, it is cumbersome to maintain a patch
7939: file for this. This is where the SUBST framework steps in. It provides an
7940: easy-to-use interface for replacing text in files. It just needs the
7941: following information:</p>
7942: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7943: <li class="listitem"><p>In which phase of the package build cycle should the
7944: replacement happen?</p></li>
7945: <li class="listitem"><p>In which files should the replacement
1.172 rillig 7946: happen?</p></li>
1.180 rillig 7947: <li class="listitem"><p>Which text should be replaced with
7948: what?</p></li>
1.172 rillig 7949: </ul></div>
7950: <p>This information is encoded in a block of <code class="varname">SUBST</code>
1.180 rillig 7951: variables. A minimal example is:</p>
7952: <pre class="programlisting">
7953: SUBST_CLASSES+= paths
7954: SUBST_STAGE.paths= pre-configure
7955: SUBST_FILES.paths= src/*.c
7956: SUBST_SED.paths= -e 's,/usr/local,${PREFIX},g'
7957: </pre>
7958: <p>Translated into English, it means: In the pre-configure stage (that
7959: is, after applying the patches from the patches/ directory and before
7960: running the configure script and the portability check), replace the text
7961: <code class="literal">/usr/local</code> with the content of the variable
7962: <code class="varname">PREFIX</code>.</p>
7963: <p>Each SUBST block starts by appending an identifier to
7964: <code class="varname">SUBST_CLASSES</code> (note the <code class="literal">+=</code>). This
7965: identifier can be chosen freely by the package. If there should ever be
7966: duplicate identifiers, the pkgsrc infrastructure will catch this and fail
7967: early, so don't worry about name collisions.</p>
7968: <p>Except for <code class="varname">SUBST_CLASSES</code>, all variables in a
7969: SUBST block are parameterized using this identifier. In the remainder of
7970: this section, these parameterized variables are written as
7971: <code class="varname">SUBST_STAGE.*</code>.</p>
7972: <pre class="programlisting">
7973: SUBST_CLASSES+= paths
7974: SUBST_STAGE.paths= pre-configure
7975: SUBST_MESSAGE.paths= Fixing absolute paths.
7976: SUBST_FILES.paths= src/*.c
7977: SUBST_FILES.paths+= scripts/*.sh
7978: SUBST_SED.paths= -e 's,"/usr/local,"${PREFIX},g'
7979: SUBST_SED.paths+= -e 's,"/var/log,"${VARBASE}/log,g'
7980: SUBST_VARS.paths= LOCALBASE PREFIX PKGVERSION
7981: </pre>
7982: <p>To get a complete picture about the SUBST substitutions, run
7983: <span class="command"><strong>bmake show-all-subst</strong></span>. If something doesn't work as
7984: expected, run pkglint on the package, which detects several typical
7985: mistakes surrounding the SUBST blocks. For any questions that might
7986: remain after this, have a look at
7987: <code class="filename">mk/subst.mk</code>.</p>
7988: <div class="sect3">
7989: <div class="titlepage"><div><div><h4 class="title">
7990: <a name="fixes.subst.when"></a>21.1.11.1. Choosing the time where the substitutions happen</h4></div></div></div>
7991: <p>The <code class="varname">SUBST_STAGE.*</code> is one of
7992: {pre,do,post}-{extract,patch,configure,build,test,install}. Of these,
7993: <code class="literal">pre-configure</code> is used most often, by far. The most
7994: popular stages are, in chronological order:</p>
7995: <div class="variablelist"><dl class="variablelist">
7996: <dt><span class="term"><code class="literal">post-extract</code></span></dt>
7997: <dd>
7998: <p>The substitutions are applied immediately after the
7999: distfiles are extracted. Running <span class="command"><strong>bmake extract</strong></span> on the
8000: package will leave no traces of the original files.</p>
8001: <p>When the substitution applies to files for which there is also a
8002: patch in the <code class="filename">patches/</code> directory, this means that the
8003: patches will be computed based on the result of the substitution. When
8004: these patches are sent to the upstream maintainer later, to be fixed in
8005: the upstream package, these patches may no longer match what the upstream
8006: author is used to. Because of this, <code class="literal">pre-configure</code> is
8007: often a better choice.</p>
8008: </dd>
8009: <dt><span class="term"><code class="literal">pre-configure</code></span></dt>
8010: <dd>
8011: <p>The substitutions are applied after the patches from the
8012: <code class="filename">patches/</code> directory. This makes it possible to run
8013: <span class="command"><strong>bmake patch</strong></span> on the package, after which the patches
1.207 leot 8014: 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 8015: <p>When updating the patches, it is helpful to explicitly separate the
8016: <span class="command"><strong>bmake patch</strong></span> from the <span class="command"><strong>bmake
8017: configure</strong></span>, and to only edit the patches between these commands.
8018: Otherwise the substitutions from the SUBST block will end up in the patch
8019: file. When this happens in really obvious ways, pkglint will complain
8020: about patches that contain a hard-coded <code class="literal">/usr/pkg</code>
8021: instead of the correct and intended <code class="literal">@PREFIX@</code>, but it
8022: can only detect these really obvious
8023: cases.</p>
8024: </dd>
8025: <dt><span class="term"><code class="literal">do-configure</code></span></dt>
8026: <dd><p>This stage should only be used if the package defines a
8027: <code class="literal">pre-configure</code> action itself, and the substitution must
8028: happen after that. Typical examples are packages that use the
8029: <code class="literal">pre-configure</code> stage to regenerate the GNU configure
8030: script from
8031: <code class="filename">configure.ac</code>.</p></dd>
8032: <dt><span class="term"><code class="literal">post-configure</code></span></dt>
8033: <dd><p>This stage is used to fix up any mistakes by the
8034: configure stage.</p></dd>
8035: <dt><span class="term"><code class="literal">pre-build</code></span></dt>
8036: <dd><p>This stage should only be used for substitutions that are
8037: clearly related to building the package, not for fixing the
8038: configuration. Substitutions for pathnames (such as replacing
8039: <code class="filename">/usr/local</code> with <code class="literal">${PREFIX}</code>) or
8040: user names (such as replacing <code class="literal">@MY_USER@</code> with the
8041: actual username) belong in pre-configure or post-configure
8042: instead.</p></dd>
8043: <dt><span class="term"><code class="literal">post-build</code></span></dt>
8044: <dd>
8045: <p>Just as with pre-build, this stage should only be used
8046: for substitutions that are clearly related to building the package, not
8047: for fixing the configuration. Substitutions for pathnames (such as
8048: replacing <code class="filename">/usr/local</code> with
8049: <code class="literal">${PREFIX}</code>) or user names (such as replacing
8050: <code class="literal">@MY_USER@</code> with the actual username) belong in
8051: pre-configure or post-configure instead.</p>
8052: <p>A typical use is to update pkg-config files to include the rpath
8053: compiler options.</p>
8054: </dd>
8055: <dt><span class="term"><code class="literal">pre-install</code></span></dt>
8056: <dd><p>In general, the install phase should be as simple as
8057: possible. As with the pre-build and post-build stages, it should not be
8058: used to fix pathnames or user names, these belong in pre-configure
8059: instead. There are only few legitimate use cases for applying
8060: substitutions in this stage.</p></dd>
8061: </dl></div>
8062: </div>
8063: <div class="sect3">
8064: <div class="titlepage"><div><div><h4 class="title">
1.181 rillig 8065: <a name="fixes.subst.where"></a>21.1.11.2. Choosing the files where the substitutions happen</h4></div></div></div>
1.180 rillig 8066: <p>The <code class="varname">SUBST_FILES.*</code> variable contains a list of
8067: filename patterns. These patterns are relative to
8068: <code class="varname">WRKSRC</code> since that is where most substitutions happen.
8069: A typical example is:</p>
8070: <pre class="programlisting">
8071: SUBST_FILES.path= Makefile */Makefile */*/Makefile *.[ch]
8072: </pre>
8073: <p>The above patterns, especially the last, are quite broad. The SUBST
8074: implementation checks that each filename pattern that is mentioned here
8075: has an effect. For example, if none of the
8076: <code class="filename">*/*/Makefile</code> files contains the patterns to be found
8077: and substituted, that filename pattern is redundant and should be left
1.181 rillig 8078: out. By default, the SUBST framework will complain with an error message.
8079: If the text to be substituted occurs in some of the files from a single
8080: pattern, but not in all of them, that is totally ok, and the SUBST
1.180 rillig 8081: framework will only print an INFO message for those files.</p>
8082: <p>If there is a good reason for having redundant filename patterns,
1.181 rillig 8083: set <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
1.180 rillig 8084: <p>Another popular way of choosing the files for the substitutions is
8085: via a shell command, like this:</p>
8086: <pre class="programlisting">
1.181 rillig 8087: C_FILES_CMD= cd ${WRKSRC} && ${FIND} . -name '*.c'
1.180 rillig 8088: SUBST_FILES.path= ${C_FILES_CMD:sh}
8089: </pre>
8090: <p>The variable name <code class="varname">C_FILES_CMD</code> in this example is
8091: freely chosen and independent of the SUBST framework.</p>
8092: <p>In this variant, the <code class="varname">SUBST_FILES.*</code> variable
8093: lists each file individually. Thereby chances are higher that there are
8094: filename patterns in which no substitution happens. Since the SUBST
8095: framework cannot know whether the filename patterns in
8096: <code class="varname">SUBST_FILES.*</code> have been explicitly listed in the
8097: Makefile (where any redundant filename pattern would be suspicious) or
8098: been generated by a shell command (in which redundant filename patterns
8099: are more likely and to be expected), it will complain about these
8100: redundant filename patterns. Therefore, SUBST blocks that use a shell
8101: command to generate the list of filename patterns often need to set
8102: <code class="varname">SUBST_NOOP_OK.*</code> to <code class="literal">yes</code>.</p>
8103: </div>
8104: <div class="sect3">
8105: <div class="titlepage"><div><div><h4 class="title">
8106: <a name="fixes.subst.what"></a>21.1.11.3. Choosing what to substitute</h4></div></div></div>
8107: <p>In most cases, the substitutions are given using one or more
1.207 leot 8108: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/sed.1"><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> commands, like this:</p>
1.180 rillig 8109: <pre class="programlisting">
8110: SUBST_SED.path= -e 's|/usr/local|${PREFIX}|g'
8111: </pre>
8112: <p>Each of the sed commands needs to be preceded by the
8113: <code class="literal">-e</code> option and should be specified on a line of its
8114: own, to avoid hiding short sed commands at the end of a line.</p>
8115: <p>Since the sed commands often contain shell metacharacters as the
8116: separator (the <code class="literal">|</code> in the above example), it is common
8117: to enclose them in single quotes.</p>
8118: <p>A common substitution is to replace placeholders of the form
8119: <code class="literal">@VARNAME@</code> with their pkgsrc counterpart variable
8120: <code class="literal">${VARNAME}</code>. A typical example is:</p>
8121: <pre class="programlisting">
8122: SUBST_VARS.path= PREFIX
8123: </pre>
8124: <p>This type of substitutions is typically done by the GNU configure
1.181 rillig 8125: scripts during the do-configure stage, but in some cases these need to be
8126: overridden. The same pattern is also used when a package defines patches
8127: that replace previously hard-coded paths like
8128: <code class="literal">/usr/local</code> with a <code class="literal">@PREFIX@</code>
8129: placeholder first, which then gets substituted by the actual
8130: <code class="literal">${PREFIX}</code> in the pre-configure stage. In many of these
8131: cases, it works equally well to just use the SUBST framework to directly
8132: replace <code class="literal">/usr/local</code> with <code class="literal">${PREFIX}</code>,
8133: thereby omitting the intermediate patch file.</p>
1.180 rillig 8134: <p>If the above is not flexible enough, it is possible to not use sed
8135: at all for the substitution but to specify an entirely different command,
8136: like this:</p>
1.1 dsieger 8137: <pre class="programlisting">
1.180 rillig 8138: SUBST_FILTER_CMD.path= LC_ALL=C ${TR} -d '\r'
8139: </pre>
8140: <p>This is used for the few remaining packages in which the
8141: distributed files use Windows-style line endings that need to be
8142: converted to UNIX-style line endings.</p>
8143: </div>
8144: <div class="sect3">
8145: <div class="titlepage"><div><div><h4 class="title">
8146: <a name="fixes.subst.other"></a>21.1.11.4. Other SUBST variables</h4></div></div></div>
8147: <p>When a SUBST block is applied during a package build, a message is
8148: logged. The default message is fine for most purposes but can be
8149: overridden by setting <code class="literal">SUBST_MESSAGE.*</code> to an individual
8150: message.</p>
8151: </div>
1.1 dsieger 8152: </div>
8153: </div>
1.41 asau 8154: <div class="sect1">
1.1 dsieger 8155: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8156: <a name="fixes.fetch"></a>21.2. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
1.41 asau 8157: <div class="sect2">
1.1 dsieger 8158: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8159: <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 8160: <p>If you need to download from a dynamic URL you can set
1.10 hubertf 8161: <code class="varname">DYNAMIC_MASTER_SITES</code> and a <span class="command"><strong>make
1.1 dsieger 8162: fetch</strong></span> will call <code class="filename">files/getsite.sh</code>
8163: with the name of each file to download as an argument, expecting
8164: it to output the URL of the directory from which to download
1.207 leot 8165: 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 8166: example of this usage.</p>
8167: <p>If the download can't be automated, because the user must
8168: submit personal information to apply for a password, or must pay
8169: for the source, or whatever, you can set
8170: <code class="varname">FETCH_MESSAGE</code> to a list of lines that are
8171: displayed to the user before aborting the build. Example:</p>
8172: <pre class="programlisting">
8173: FETCH_MESSAGE= "Please download the files"
8174: FETCH_MESSAGE+= " "${DISTFILES:Q}
8175: FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
1.111 sevan 8176: </pre>
1.1 dsieger 8177: </div>
1.41 asau 8178: <div class="sect2">
1.1 dsieger 8179: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8180: <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 8181: <p>Sometimes authors of a software package make some
8182: modifications after the software was released, and they put up a
8183: new distfile without changing the package's version number. If a
8184: package is already in pkgsrc at that time, the checksum will
8185: no longer match. The contents of the new distfile should be
8186: compared against the old one before changing anything, to make
8187: sure the distfile was really updated on purpose, and that
8188: no trojan horse or so crept in.
8189: Please mention that the distfiles were compared and what was found
1.53 rodent 8190: in your commit message.</p>
1.109 wiz 8191: <p>Then, the correct way to work around this is to set
8192: <code class="varname">DIST_SUBDIR</code> to a unique directory name, usually
8193: based on <code class="varname">PKGNAME_NOREV</code> (but take care with
8194: python or ruby packages, where <code class="varname">PKGNAME</code> includes
8195: a variable prefix). All <code class="varname">DISTFILES</code> and
1.1 dsieger 8196: <code class="varname">PATCHFILES</code> for this package will be put in that
1.154 rillig 8197: 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 8198: happens more often, <code class="varname">PKGNAME</code> can be used (thus
1.109 wiz 8199: including the <code class="filename">nbX</code> suffix) or a date stamp can
8200: be appended, like
8201: <code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>.</p>
1.169 rillig 8202: <p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's
8203: name does not contain a version and the distfile is apt to change. In
8204: cases where the likelihood of this is very small,
8205: <code class="varname">DIST_SUBDIR</code> might not be required. Additionally,
8206: <code class="varname">DIST_SUBDIR</code> must not be removed unless the
8207: distfile name changes, even if a package is being moved or
8208: renamed.</p>
1.53 rodent 8209: <p>Do not forget regenerating the <code class="filename">distinfo</code> file
1.1 dsieger 8210: after that, since it contains the <code class="varname">DIST_SUBDIR</code>
8211: path in the filenames.
1.53 rodent 8212: Also, increase the PKGREVISION if the installed package is different.
1.1 dsieger 8213: Furthermore, a mail to the package's authors seems appropriate
8214: telling them that changing distfiles after releases without
8215: changing the file names is not good practice.</p>
8216: </div>
1.88 tnn 8217: <div class="sect2">
8218: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8219: <a name="build.fetch.github"></a>21.2.3. Packages hosted on github.com</h3></div></div></div>
1.169 rillig 8220: <p>Helper methods exist for packages hosted on github.com which
8221: will often have distfile names that clash with other packages, for
8222: example <code class="filename">1.0.tar.gz</code>. Use one of the three recipes
8223: from below:</p>
1.88 tnn 8224: <div class="sect3">
8225: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8226: <a name="build.fetch.github.tag"></a>21.2.3.1. Fetch based on a tagged release</h4></div></div></div>
1.169 rillig 8227: <p>If your distfile URL looks similar to
1.189 bacon 8228: <code class="literal">https://github.com/username/example/archive/v1.0.zip</code>,
1.169 rillig 8229: then you are packaging a tagged release.</p>
1.88 tnn 8230: <pre class="programlisting">
1.189 bacon 8231: DISTNAME= example-1.0
1.90 tnn 8232: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.189 bacon 8233: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.90 tnn 8234: GITHUB_TAG= v${PKGVERSION_NOREV}
1.88 tnn 8235: EXTRACT_SUFX= .zip
8236: </pre>
1.230 gutterid 8237: <p>Here, DISTNAME combined with use of GITHUB_TAG leads the
8238: file fetching infrastructure to save the resulting file locally as
8239: <code class="literal">example-1.0.zip</code>.</p>
1.88 tnn 8240: </div>
8241: <div class="sect3">
8242: <div class="titlepage"><div><div><h4 class="title">
1.189 bacon 8243: <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>
8244: <p>If your distfile looks similar to
8245: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit before the first
8246: release, then set the package version to 0.0.0.N, where N is the number
8247: of commits to the repository, and set GITHUB_TAG to the commit hash.
8248: This will (almost) ensure that the first tagged release will have a
8249: version greater than this one so that package upgrades will function
8250: properly.</p>
8251: <pre class="programlisting">
8252: DISTNAME= example-0.0.0.347
8253: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8254: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
8255: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
8256: </pre>
8257: </div>
8258: <div class="sect3">
8259: <div class="titlepage"><div><div><h4 class="title">
8260: <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>
8261: <p>If your distfile looks similar to
8262: <code class="literal">https://github.com/username/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11</code> and is from a commit after a release,
8263: then include the last release version and the commit count since that
8264: release in the package version and set GITHUB_TAG to the commit hash.
8265: The latest release and commit count are shown in the output of
8266: "git describe --tags":
8267: </p>
8268: <pre class="screen">
8269: # git clone https://github.com/username/example
8270: # cd example
8271: # git describe --tags
8272: 1.2.3-5-g988881a
8273: </pre>
1.88 tnn 8274: <pre class="programlisting">
1.189 bacon 8275: DISTNAME= example-1.2.3.5
8276: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8277: #GITHUB_PROJECT= example # can be omitted if same as DISTNAME
1.90 tnn 8278: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
1.111 sevan 8279: </pre>
1.88 tnn 8280: </div>
8281: <div class="sect3">
8282: <div class="titlepage"><div><div><h4 class="title">
1.189 bacon 8283: <a name="build.fetch.github.release"></a>21.2.3.4. Fetch based on release</h4></div></div></div>
1.169 rillig 8284: <p>If your distfile URL looks similar to
1.189 bacon 8285: <code class="literal">https://github.com/username/example/releases/download/rel-1.6/offensive-1.6.zip</code>,
1.169 rillig 8286: then you are packaging a release.</p>
1.88 tnn 8287: <pre class="programlisting">
8288: DISTNAME= offensive-1.6
1.90 tnn 8289: PKGNAME= ${DISTNAME:S/offensive/proper/}
8290: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
1.189 bacon 8291: GITHUB_PROJECT= example
1.90 tnn 8292: GITHUB_RELEASE= rel-${PKGVERSION_NOREV} # usually just set this to ${DISTNAME}
8293: EXTRACT_SUFX= .zip
1.111 sevan 8294: </pre>
1.88 tnn 8295: </div>
8296: </div>
1.1 dsieger 8297: </div>
1.41 asau 8298: <div class="sect1">
1.1 dsieger 8299: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8300: <a name="fixes.configure"></a>21.3. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
1.41 asau 8301: <div class="sect2">
1.1 dsieger 8302: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8303: <a name="fixes.libtool"></a>21.3.1. Shared libraries - libtool</h3></div></div></div>
1.1 dsieger 8304: <p>pkgsrc supports many different machines, with different
8305: object formats like a.out and ELF, and varying abilities to do
8306: shared library and dynamic loading at all. To accompany this,
8307: varying commands and options have to be passed to the
8308: compiler, linker, etc. to get the Right Thing, which can be
8309: pretty annoying especially if you don't have all the machines
8310: at your hand to test things. The
1.207 leot 8311: <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 8312: can help here, as it just <span class="quote">“<span class="quote">knows</span>”</span> how to build
1.1 dsieger 8313: both static and dynamic libraries from a set of source files,
8314: thus being platform-independent.</p>
8315: <p>Here's how to use libtool in a package in seven simple
8316: steps:</p>
1.23 wiz 8317: <div class="orderedlist"><ol class="orderedlist" type="1">
8318: <li class="listitem"><p>Add <code class="varname">USE_LIBTOOL=yes</code> to the package
1.1 dsieger 8319: Makefile.</p></li>
1.23 wiz 8320: <li class="listitem"><p>For library objects, use <span class="quote">“<span class="quote">${LIBTOOL} --mode=compile
8321: ${CC}</span>”</span> in place of <span class="quote">“<span class="quote">${CC}</span>”</span>. You could even
1.1 dsieger 8322: add it to the definition of <code class="varname">CC</code>, if only
8323: libraries are being built in a given Makefile. This one command
8324: will build both PIC and non-PIC library objects, so you need not
8325: have separate shared and non-shared library rules.</p></li>
1.23 wiz 8326: <li class="listitem">
1.1 dsieger 8327: <p>For the linking of the library, remove any
1.23 wiz 8328: <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
8329: -Bshareable</span>”</span> commands, and instead use:</p>
1.1 dsieger 8330: <pre class="programlisting">
8331: ${LIBTOOL} --mode=link \
8332: ${CC} -o ${.TARGET:.a=.la} \
8333: ${OBJS:.o=.lo} \
8334: -rpath ${PREFIX}/lib \
8335: -version-info major:minor
1.111 sevan 8336: </pre>
1.1 dsieger 8337: <p>Note that the library is changed to have a
8338: <code class="filename">.la</code> extension, and the objects are
8339: changed to have a <code class="filename">.lo</code>
8340: extension. Change <code class="varname">OBJS</code> as
8341: necessary. This automatically creates all of the
8342: <code class="filename">.a</code>,
8343: <code class="filename">.so.major.minor</code>, and ELF symlinks (if
8344: necessary) in the build directory. Be sure to include
1.23 wiz 8345: <span class="quote">“<span class="quote">-version-info</span>”</span>, especially when major and
1.1 dsieger 8346: minor are zero, as libtool will otherwise strip off the
8347: shared library version.</p>
8348: <p>From the libtool manual:</p>
8349: <pre class="programlisting">
8350: So, libtool library versions are described by three integers:
8351:
8352: CURRENT
8353: The most recent interface number that this library implements.
8354:
8355: REVISION
8356: The implementation number of the CURRENT interface.
8357:
8358: AGE
8359: The difference between the newest and oldest interfaces that
8360: this library implements. In other words, the library implements
8361: all the interface numbers in the range from number `CURRENT -
8362: AGE' to `CURRENT'.
8363:
8364: If two libraries have identical CURRENT and AGE numbers, then the
8365: dynamic linker chooses the library with the greater REVISION number.
1.111 sevan 8366: </pre>
1.23 wiz 8367: <p>The <span class="quote">“<span class="quote">-release</span>”</span> option will produce
1.1 dsieger 8368: different results for a.out and ELF (excluding symlinks)
8369: in only one case. An ELF library of the form
1.23 wiz 8370: <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 8371: will have a symlink of
1.23 wiz 8372: <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 8373: on an a.out platform. This is handled
8374: automatically.</p>
1.23 wiz 8375: <p>The <span class="quote">“<span class="quote">-rpath argument</span>”</span> is the install
1.1 dsieger 8376: directory of the library being built.</p>
8377: <p>In the <code class="filename">PLIST</code>, include only the
8378: <code class="filename">.la</code> file, the other files will be
8379: added automatically.</p>
8380: </li>
1.23 wiz 8381: <li class="listitem">
1.1 dsieger 8382: <p>When linking shared object (<code class="filename">.so</code>)
1.207 leot 8383: files, i.e. files that are loaded via <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/dlopen.3"><span class="citerefentry"><span class="refentrytitle">dlopen</span>(3)</span></a>, NOT
1.23 wiz 8384: shared libraries, use <span class="quote">“<span class="quote">-module
8385: -avoid-version</span>”</span> to prevent them getting version
1.1 dsieger 8386: tacked on.</p>
8387: <p>The <code class="filename">PLIST</code> file gets the
8388: <code class="filename">foo.so</code> entry.</p>
8389: </li>
1.23 wiz 8390: <li class="listitem">
1.1 dsieger 8391: <p>When linking programs that depend on these libraries
8392: <span class="emphasis"><em>before</em></span> they are installed, preface
1.207 leot 8393: the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cc.1"><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ld.1"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8394: --mode=link</span>”</span>, and it will find the correct
1.1 dsieger 8395: libraries (static or shared), but please be aware that
8396: libtool will not allow you to specify a relative path in
1.23 wiz 8397: -L (such as <span class="quote">“<span class="quote">-L../somelib</span>”</span>), because it
1.1 dsieger 8398: expects you to change that argument to be the
8399: <code class="filename">.la</code> file. e.g.</p>
8400: <pre class="programlisting">
8401: ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
1.111 sevan 8402: </pre>
1.1 dsieger 8403: <p>should be changed to:</p>
8404: <pre class="programlisting">
8405: ${LIBTOOL} --mode=link ${CC} -o <em class="replaceable"><code>someprog</code></em> <em class="replaceable"><code>../somelib/somelib.la</code></em>
1.111 sevan 8406: </pre>
1.1 dsieger 8407: <p>and it will do the right thing with the libraries.</p>
8408: </li>
1.23 wiz 8409: <li class="listitem">
1.207 leot 8410: <p>When installing libraries, preface the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/install.1"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a>
8411: or <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/cp.1"><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8412: --mode=install</span>”</span>, and change the library name to
1.1 dsieger 8413: <code class="filename">.la</code>. e.g.</p>
8414: <pre class="programlisting">
1.22 jakllsch 8415: ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib
1.111 sevan 8416: </pre>
1.1 dsieger 8417: <p>This will install the static <code class="filename">.a</code>,
8418: shared library, any needed symlinks, and run
1.207 leot 8419: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/ldconfig.8"><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
1.1 dsieger 8420: </li>
1.23 wiz 8421: <li class="listitem"><p>In your <code class="filename">PLIST</code>, include only
1.1 dsieger 8422: the <code class="filename">.la</code>
8423: file (this is a change from previous behaviour).</p></li>
8424: </ol></div>
8425: </div>
1.41 asau 8426: <div class="sect2">
1.1 dsieger 8427: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8428: <a name="using-libtool"></a>21.3.2. Using libtool on GNU packages that already support libtool</h3></div></div></div>
1.1 dsieger 8429: <p>Add <code class="varname">USE_LIBTOOL=yes</code> to the
8430: package Makefile. This will override the package's own libtool
8431: in most cases. For older libtool using packages, libtool is
8432: made by ltconfig script during the do-configure step; you can
1.10 hubertf 8433: check the libtool script location by doing <span class="command"><strong>make
1.1 dsieger 8434: configure; find work*/ -name libtool</strong></span>.</p>
8435: <p><code class="varname">LIBTOOL_OVERRIDE</code> specifies which libtool
8436: scripts, relative to <code class="varname">WRKSRC</code>, to override. By
1.23 wiz 8437: default, it is set to <span class="quote">“<span class="quote">libtool */libtool
8438: */*/libtool</span>”</span>. If this does not match the location of the
1.1 dsieger 8439: package's libtool script(s), set it as appropriate.</p>
8440: <p>If you do not need <code class="filename">*.a</code> static
8441: libraries built and installed, then use
8442: <code class="varname">SHLIBTOOL_OVERRIDE</code> instead.</p>
8443: <p>If your package makes use of the platform-independent library
8444: for loading dynamic shared objects, that comes with libtool
8445: (libltdl), you should include devel/libltdl/buildlink3.mk.</p>
8446: <p>Some packages use libtool incorrectly so that the package
8447: may not work or build in some circumstances. Some of the more
8448: common errors are:</p>
1.41 asau 8449: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8450: <li class="listitem">
1.1 dsieger 8451: <p>The inclusion of a shared object (-module) as a dependent library in an
8452: executable or library. This in itself isn't a problem if one of two things
8453: has been done:</p>
1.23 wiz 8454: <div class="orderedlist"><ol class="orderedlist" type="1">
8455: <li class="listitem"><p>The shared object is named correctly, i.e.
1.1 dsieger 8456: <code class="filename">libfoo.la</code>, not
8457: <code class="filename">foo.la</code></p></li>
1.23 wiz 8458: <li class="listitem"><p>The -dlopen option is used when linking an executable.</p></li>
1.1 dsieger 8459: </ol></div>
8460: </li>
1.23 wiz 8461: <li class="listitem"><p>The use of libltdl without the correct calls to initialisation routines.
1.1 dsieger 8462: The function lt_dlinit() should be called and the macro
8463: <code class="varname">LTDL_SET_PRELOADED_SYMBOLS</code> included in
8464: executables.</p></li>
8465: </ul></div>
8466: </div>
1.41 asau 8467: <div class="sect2">
1.1 dsieger 8468: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8469: <a name="autoconf-automake"></a>21.3.3. GNU Autoconf/Automake</h3></div></div></div>
1.1 dsieger 8470: <p>If a package needs GNU autoconf or automake to be executed
1.223 nia 8471: to regenerate the
8472: <code class="filename">configure</code>
8473: script and <code class="filename">Makefile.in</code> makefile
8474: templates from <code class="filename">configure.ac</code> and
8475: <code class="filename">Makefile.am</code>,
8476: then they should be executed in a pre-configure target:</p>
1.1 dsieger 8477: <pre class="programlisting">
1.223 nia 8478: USE_TOOLS+= autoconf automake autoreconf
8479: GNU_CONFIGURE= yes
1.1 dsieger 8480: ...
8481:
8482: pre-configure:
1.223 nia 8483: set -e; cd ${WRKSRC} && autoreconf -fi
1.1 dsieger 8484: ...
1.111 sevan 8485: </pre>
1.223 nia 8486: <p>Packages which use GNU Automake will sometimes
8487: require GNU Make (<code class="literal">gmake</code> in
8488: <code class="varname">USE_TOOLS</code>),
8489: but not always. Note that autoreconf
8490: only needs to be executed if <code class="filename">configure.ac</code>
8491: or Makefiles are modified, or <code class="filename">configure</code>
8492: is not present.</p>
1.1 dsieger 8493: <p>There are times when the configure process makes
8494: additional changes to the generated files, which then causes
8495: the build process to try to re-execute the automake sequence.
8496: This is prevented by touching various files in the configure
8497: stage. If this causes problems with your package you can set
8498: <code class="varname">AUTOMAKE_OVERRIDE=NO</code> in the package
8499: Makefile.</p>
8500: </div>
1.223 nia 8501: <div class="sect2">
8502: <div class="titlepage"><div><div><h3 class="title">
8503: <a name="meson"></a>21.3.4. Meson / ninja</h3></div></div></div>
8504: <p>Packages using Meson to configure need to include:
8505:
8506: </p>
8507: <pre class="programlisting">
8508: .include "../../devel/meson/build.mk"
8509: </pre>
8510: <p>In nearly all cases (any program with dependencies),
8511: pkg-config needs to be added to
8512: <code class="varname">USE_TOOLS</code>. If the package installs
8513: translation files for non-English languages, also
8514: add msgfmt and xgettext:
8515:
8516: </p>
8517: <pre class="programlisting">
8518: USE_TOOLS+= pkg-config msgfmt xgettext
8519: </pre>
8520: <p>If any options need to be passed to Meson, use
8521: <code class="varname">MESON_ARGS</code> instead of
8522: <code class="varname">CONFIGURE_ARGS</code>:
8523:
8524: </p>
8525: <pre class="programlisting">
8526: MESON_ARGS+= -Dx11=false
8527: </pre>
8528: </div>
1.1 dsieger 8529: </div>
1.41 asau 8530: <div class="sect1">
1.1 dsieger 8531: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8532: <a name="programming-languages"></a>21.4. Programming languages</h2></div></div></div>
1.41 asau 8533: <div class="sect2">
1.1 dsieger 8534: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8535: <a name="basic-programming-languages"></a>21.4.1. C, C++, and Fortran</h3></div></div></div>
1.223 nia 8536: <p>Compilers for the C and C++ languages comes with
1.1 dsieger 8537: the NetBSD base system. By default, pkgsrc assumes that a package
8538: is written in C and will hide all other compilers (via the wrapper
1.184 rillig 8539: framework, see <a class="xref" href="#buildlink" title="Chapter 18. Buildlink methodology">Chapter 18, <i>Buildlink methodology</i></a>).</p>
1.1 dsieger 8540: <p>To declare which language's compiler a package needs, set
8541: the <code class="varname">USE_LANGUAGES</code> variable. Allowed values
1.212 wiz 8542: currently are:
8543: </p>
8544: <pre class="programlisting">
8545: c99, c++, c++03, gnu++03, c++0x, gnu++0x, c++11, gnu++11,
8546: c++14, gnu++14, c++17, gnu++17, c++20, gnu++20, fortran,
8547: fortran77, java, objc, obj-c++, and ada.
8548: </pre>
8549: <p>
8550: (and any combination). The default is
1.23 wiz 8551: <span class="quote">“<span class="quote">c</span>”</span>. Packages using GNU configure scripts, even if
1.1 dsieger 8552: written in C++, usually need a C compiler for the configure
8553: phase.</p>
1.223 nia 8554: <p>To express a general requirement on a specific C or C++
8555: version, normally only <code class="varname">GCC_REQD</code> needs to be set.
8556: For example, GCC 7 includes support for C++17, so if the package uses
8557: C++17 it should specify:
8558:
8559: </p>
8560: <pre class="programlisting">
8561: GCC_REQD+= 7
8562: </pre>
8563: <p>Language variants like <code class="literal">c++11</code> for
8564: <code class="varname">USE_LANGUAGES</code> should only be specified
8565: if the package does not explicitly set <code class="literal">-std=...</code>
8566: when compiling (i.e. the package assumes the compiler defaults to
8567: C++11 or some other standard). This is usually a bug in the
8568: upstream build system.</p>
8569: <p>GCC version 5 includes support for C++14, while GCC 4.7 includes
8570: more-or-less complete support for C++11. For more information, consult
8571: <a class="ulink" href="https://gcc.gnu.org/projects/cxx-status.html" target="_top">GCC's own documentation on programming language support.</a></p>
1.1 dsieger 8572: </div>
1.41 asau 8573: <div class="sect2">
1.1 dsieger 8574: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8575: <a name="java-programming-language"></a>21.4.2. Java</h3></div></div></div>
1.1 dsieger 8576: <p>If a program is written in Java, use the Java framework in
8577: pkgsrc. The package must include
8578: <code class="filename">../../mk/java-vm.mk</code>. This Makefile fragment
8579: provides the following variables:</p>
1.41 asau 8580: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8581: <li class="listitem"><p><code class="varname">USE_JAVA</code> defines if a build
1.1 dsieger 8582: dependency on the JDK is added. If
1.23 wiz 8583: <code class="varname">USE_JAVA</code> is set to <span class="quote">“<span class="quote">run</span>”</span>, then
1.1 dsieger 8584: there is only a runtime dependency on the JDK. The default is
1.23 wiz 8585: <span class="quote">“<span class="quote">yes</span>”</span>, which also adds a build dependency on the
1.1 dsieger 8586: JDK.</p></li>
1.23 wiz 8587: <li class="listitem"><p>Set <code class="varname">USE_JAVA2</code> to declare that
1.1 dsieger 8588: a package needs a Java2 implementation. The supported values
1.23 wiz 8589: are <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">1.4</span>”</span>, and
8590: <span class="quote">“<span class="quote">1.5</span>”</span>. <span class="quote">“<span class="quote">yes</span>”</span> accepts any Java2
8591: implementation, <span class="quote">“<span class="quote">1.4</span>”</span> insists on versions 1.4 or
8592: above, and <span class="quote">“<span class="quote">1.5</span>”</span> only accepts versions 1.5 or
1.1 dsieger 8593: above. This variable is not set by default.</p></li>
1.24 wiz 8594: <li class="listitem"><p><code class="varname">PKG_JAVA_HOME</code> is
8595: automatically set to the runtime location of the used Java
8596: implementation dependency. It may be used to set
8597: <code class="varname">JAVA_HOME</code> to a good value if the program
8598: needs this variable to be defined.
8599: </p></li>
1.1 dsieger 8600: </ul></div>
8601: </div>
1.41 asau 8602: <div class="sect2">
1.1 dsieger 8603: <div class="titlepage"><div><div><h3 class="title">
1.205 wiz 8604: <a name="go-programming-language"></a>21.4.3. Go</h3></div></div></div>
8605: <p>If a program is written in Go and has any dependencies on
8606: other Go modules, have the package include
8607: <code class="filename">../../lang/go/go-module.mk</code>.</p>
8608: <div class="orderedlist"><ol class="orderedlist" type="1">
8609: <li class="listitem"><p>Generate a list of those dependencies with
8610: <span class="command"><strong>make clean && make patch && make show-go-modules >
8611: go-modules.mk</strong></span>.</p></li>
1.223 nia 8612: <li class="listitem"><p>Prepend
8613: <code class="literal">.include "go-modules.mk"</code> to any other
8614: <code class="literal">.include</code>s.</p></li>
8615: <li class="listitem"><p>Incorporate these modules in
8616: <code class="filename">distinfo</code> with <span class="command"><strong>make
8617: makesum</strong></span>.</p></li>
8618: </ol></div>
8619: </div>
8620: <div class="sect2">
8621: <div class="titlepage"><div><div><h3 class="title">
8622: <a name="rust-programming-language"></a>21.4.4. Rust</h3></div></div></div>
8623: <p>If a program is written in Rust and uses Cargo to build,
8624: have the package include
8625: <code class="filename">../../lang/rust/cargo.mk</code>.</p>
8626: <div class="orderedlist"><ol class="orderedlist" type="1">
8627: <li class="listitem"><p>Generate a list of those dependencies with
8628: <span class="command"><strong>make CARGO_ARGS="build --release" build &&
8629: make print-cargo-depends > cargo-depends.mk</strong></span>.</p></li>
8630: <li class="listitem"><p>Prepend
8631: <code class="literal">.include "cargo-depends.mk"</code> to any other
8632: <code class="literal">.include</code>s.</p></li>
1.205 wiz 8633: <li class="listitem"><p>Incorporate these modules in
8634: <code class="filename">distinfo</code> with <span class="command"><strong>make
8635: makesum</strong></span>.</p></li>
8636: </ol></div>
8637: </div>
8638: <div class="sect2">
8639: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8640: <a name="perl-scripts"></a>21.4.5. Packages containing Perl scripts</h3></div></div></div>
1.203 nia 8641: <p>If your package contains interpreted Perl scripts, add
1.23 wiz 8642: <span class="quote">“<span class="quote">perl</span>”</span> to the <code class="varname">USE_TOOLS</code> variable
1.1 dsieger 8643: and set <code class="varname">REPLACE_PERL</code> to ensure that the proper
8644: interpreter path is set. <code class="varname">REPLACE_PERL</code> should
8645: contain a list of scripts, relative to <code class="varname">WRKSRC</code>,
1.74 wiz 8646: that you want adjusted. Every occurrence of
8647: <code class="filename">*/bin/perl</code> in a she-bang line will be
1.210 gutterid 8648: replaced with the full path to the Perl executable.</p>
8649: <p>If a particular version of Perl is needed, set the
1.1 dsieger 8650: <code class="varname">PERL5_REQD</code> variable to the version number. The
1.23 wiz 8651: default is <span class="quote">“<span class="quote">5.0</span>”</span>.</p>
1.203 nia 8652: <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 8653: about handling Perl modules.</p>
8654: <p>There is also the <code class="varname">REPLACE_PERL6</code> variable
8655: for the language now known as Raku.</p>
1.1 dsieger 8656: </div>
1.41 asau 8657: <div class="sect2">
1.1 dsieger 8658: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8659: <a name="shell-scripts"></a>21.4.6. Packages containing shell scripts</h3></div></div></div>
1.40 wiz 8660: <p><code class="varname">REPLACE_SH</code>,
8661: <code class="varname">REPLACE_BASH</code>, <code class="varname">REPLACE_CSH</code>,
8662: and <code class="varname">REPLACE_KSH</code> can be used to replace shell
1.225 gutterid 8663: she-bangs in files. Please use the appropriate one, preferring
8664: <code class="varname">REPLACE_SH</code> when this shell is sufficient.
1.74 wiz 8665: Each should contain a list of scripts, relative to
8666: <code class="varname">WRKSRC</code>, that you want adjusted. Every
8667: occurrence of the matching shell in a she-bang line will be
8668: replaced with the full path to the shell executable.
1.40 wiz 8669: When using <code class="varname">REPLACE_BASH</code>, don't forget to add
8670: <code class="filename">bash</code> to <code class="varname">USE_TOOLS</code>.</p>
8671: </div>
1.41 asau 8672: <div class="sect2">
1.40 wiz 8673: <div class="titlepage"><div><div><h3 class="title">
1.223 nia 8674: <a name="other-programming-languages"></a>21.4.7. Other programming languages</h3></div></div></div>
1.210 gutterid 8675: <p>There are further similar REPLACE variables available, e.g.,
8676: <code class="varname">REPLACE_AWK</code> for packages containing awk scripts,
8677: and <code class="varname">REPLACE_R</code> for R. These two, like the others
1.211 gutterid 8678: noted above, have their actions defined centrally in
1.210 gutterid 8679: <code class="filename">mk/configure/replace-interpreter.mk</code>. Other
1.211 gutterid 8680: languages define the actions of these variables within their own
8681: dedicated part of the tree, e.g., <code class="varname">REPLACE_PHP</code> is
8682: actioned in <code class="filename">lang/php/phpversion.mk</code>, and
8683: <code class="varname">REPLACE_PYTHON</code> is actioned in
1.210 gutterid 8684: <code class="filename">lang/python/application.mk</code>. For other languages,
8685: consult the mk files found within their specific directories (the
1.216 gutterid 8686: naming convention varies), or check the list found in
8687: <a class="xref" href="#help-topics" title="Appendix E. Help topics">Appendix E, <i>Help topics</i></a>.</p>
1.210 gutterid 8688: <p>Currently, special handling for other languages varies
1.1 dsieger 8689: in pkgsrc. If a compiler package provides a
8690: <code class="filename">buildlink3.mk</code> file, include that, otherwise
8691: just add a (build) dependency on the appropriate compiler
8692: package.</p>
8693: </div>
8694: </div>
1.41 asau 8695: <div class="sect1">
1.1 dsieger 8696: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 8697: <a name="fixes.build"></a>21.5. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.1 dsieger 8698: <p>The most common failures when building a package are that
8699: some platforms do not provide certain header files, functions or
8700: libraries, or they provide the functions in a library that the
8701: original package author didn't know. To work around this, you
8702: can rewrite the source code in most cases so that it does not
8703: use the missing functions or provides a replacement function.</p>
1.41 asau 8704: <div class="sect2">
1.1 dsieger 8705: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8706: <a name="fixes.build.cpp"></a>21.5.1. Compiling C and C++ code conditionally</h3></div></div></div>
1.1 dsieger 8707: <p>If a package already comes with a GNU configure script, the
8708: preferred way to fix the build failure is to change the
8709: configure script, not the code. In the other cases, you can
8710: utilize the C preprocessor, which defines certain macros
8711: depending on the operating system and hardware architecture it
8712: compiles for. These macros can be queried using for example
8713: <code class="varname">#if defined(__i386)</code>. Almost every operating
8714: system, hardware architecture and compiler has its own macro.
8715: For example, if the macros <code class="varname">__GNUC__</code>,
8716: <code class="varname">__i386__</code> and <code class="varname">__NetBSD__</code>
8717: are all defined, you know that you are using NetBSD on an i386
8718: compatible CPU, and your compiler is GCC.</p>
8719: <p>The list of the following macros for hardware and
8720: operating system depends on the compiler that is used. For
8721: example, if you want to conditionally compile code on Solaris,
8722: don't use <code class="varname">__sun__</code>, as the SunPro compiler
8723: does not define it. Use <code class="varname">__sun</code> instead.</p>
1.41 asau 8724: <div class="sect3">
1.1 dsieger 8725: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8726: <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 8727: <p>To distinguish between specific NetBSD versions,
8728: you should use the following code.</p>
8729: <pre class="programlisting">
8730: #ifdef __NetBSD__
8731: #include <sys/param.h>
8732: #if __NetBSD_Prereq__(9,99,17)
8733: /* use a newer feature */
8734: #else
8735: /* older code */
8736: #endif
8737: #endif
8738:
8739: #ifndef _WIN32
8740: /* Unix-like specific code */
8741: #endif
8742: </pre>
1.1 dsieger 8743: <p>To distinguish between 4.4 BSD-derived systems and the
8744: rest of the world, you should use the following code.</p>
8745: <pre class="programlisting">
8746: #include <sys/param.h>
8747: #if (defined(BSD) && BSD >= 199306)
8748: /* BSD-specific code goes here */
8749: #else
8750: /* non-BSD-specific code goes here */
8751: #endif
8752: </pre>
1.223 nia 8753: <p>You can also test for the following macros:</p>
1.1 dsieger 8754: <pre class="programlisting">
1.45 obache 8755: Cygwin __CYGWIN__
8756: DragonFly __DragonFly__
1.1 dsieger 8757: FreeBSD __FreeBSD__
1.45 obache 8758: Haiku __HAIKU__
1.1 dsieger 8759: Interix __INTERIX
8760: IRIX __sgi (TODO: get a definite source for this)
1.223 nia 8761: Linux __linux
1.83 dholland 8762: Mac OS X __APPLE__
1.45 obache 8763: MirBSD __MirBSD__ (__OpenBSD__ is also defined)
8764: Minix3 __minix
1.1 dsieger 8765: NetBSD __NetBSD__
8766: OpenBSD __OpenBSD__
8767: Solaris sun, __sun
8768: </pre>
8769: </div>
1.41 asau 8770: <div class="sect3">
1.1 dsieger 8771: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8772: <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 8773: <pre class="programlisting">
8774: i386 i386, __i386, __i386__
1.223 nia 8775: x86-64 __amd64__, __x86_64__
8776: ARM __arm__
1.1 dsieger 8777: MIPS __mips
8778: SPARC sparc, __sparc
1.223 nia 8779: PowerPC __powerpc
1.1 dsieger 8780: </pre>
8781: </div>
1.41 asau 8782: <div class="sect3">
1.1 dsieger 8783: <div class="titlepage"><div><div><h4 class="title">
1.154 rillig 8784: <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 8785: <pre class="programlisting">
8786: GCC __GNUC__ (major version), __GNUC_MINOR__
8787: MIPSpro _COMPILER_VERSION (0x741 for MIPSpro 7.41)
8788: SunPro __SUNPRO_C (0x570 for Sun C 5.7)
8789: SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8)
8790: </pre>
8791: </div>
8792: </div>
1.41 asau 8793: <div class="sect2">
1.1 dsieger 8794: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 8795: <a name="compiler-bugs"></a>21.5.2. How to handle compiler bugs</h3></div></div></div>
1.1 dsieger 8796: <p>Some source files trigger bugs in the compiler, based on
8797: combinations of compiler version and architecture and almost
8798: always relation to optimisation being enabled. Common symptoms
8799: are gcc internal errors or never finishing compiling a
8800: file.</p>
8801: <p>Typically, a workaround involves testing the
8802: <code class="varname">MACHINE_ARCH</code> and compiler version, disabling
8803: optimisation for that combination of file,
1.87 tnn 8804: <code class="varname">MACHINE_ARCH</code> and compiler.</p>
8805: <p>This used to be a big problem in the past, but is rarely
8806: needed now as compiler technology has matured. If you still need
8807: to add a compiler specific workaround, please do so in the file
8808: <code class="filename">hacks.mk</code> and describe the symptom and
8809: compiler version as detailed as possible.</p>
1.1 dsieger 8810: </div>
1.41 asau 8811: <div class="sect2">
1.1 dsieger 8812: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 8813: <a name="fixes.build.header"></a>21.5.3. No such file or directory</h3></div></div></div>
8814: <p>Compilation sometimes fails with an error message like this:</p>
8815: <pre class="programlisting">
8816: .../x11/gtk3/work/gtk+-3.24.12/gdk/gdktypes.h:35:10:
8817: fatal error: pango/pango.h: No such file or directory
8818: </pre>
8819: <p>The proper way to fix this problem depends on the type of the
8820: header, which is described in the following sections.</p>
8821: <div class="sect3">
8822: <div class="titlepage"><div><div><h4 class="title">
8823: <a name="fixes.build.header.bl3"></a>21.5.3.1. Headers from other packages</h4></div></div></div>
8824: <p>If the header name looks like it comes from a different package,
8825: that other package should be included via the buildlink3
8826: framework.</p>
8827: <p>First, look whether the header is somewhere in the buildlink3
8828: directory below <code class="varname">WRKDIR</code>. In the above case of
8829: the missing Pango header:</p>
8830: <pre class="programlisting">
8831: <code class="prompt">$</code> find work/.buildlink/ -print | grep -F pango/pango.h
8832: </pre>
8833: <p>In the case of Pango, the output is:</p>
8834: <pre class="programlisting">
8835: work/.buildlink/include/pango-1.0/pango/pango.h
8836: </pre>
8837: <p>If the <code class="filename">pango/pango.h</code> file were placed directly
8838: in the <code class="filename">.buildlink</code> directory, it would have been
8839: found automatically. There is an extra <code class="filename">pango-1.0</code>
8840: path component though, which means that the compiler command line must
8841: contain an option of the form
8842: <code class="literal">-I${BUILDLINK3_PREFIX.pango}/include/pango-1.0</code>. In
8843: most cases this option is generated by the configure script, which can be examined using:</p>
8844: <pre class="programlisting">
8845: <code class="prompt">$</code> $ grep -o '[-]I[^[:space:]]*/pango[^[:space:]]*' work/*/Makefile
8846: -I/usr/pkg/include/pango-1.0
8847: -I/usr/pkg/include/pango-1.0
8848: -I/usr/pkg/include/pango-1.0
8849: -I/usr/pkg/include/pango-1.0
8850: -I/usr/pkg/include/pango-1.0
8851: </pre>
8852: <p>This looks good. These options are transformed by the buildlink
8853: wrapper to refer to the correct path inside
8854: <code class="filename">work/.buildlink</code>.</p>
8855: <p>Since the compilation fails though, examine the compiler command
8856: lines in <code class="filename">work/.work.log</code> to see whether the
8857: <code class="literal">-I</code> option is included in the particular command
8858: line.</p>
8859: <p>To further analyze the situation, run <span class="command"><strong>bmake
8860: build-env</strong></span>, which sets up an interactive, realistic environment
8861: including all the pkgsrc wrapper commands and environment variables. From
8862: there, try to compile some simple example programs that use the
8863: header.</p>
8864: </div>
8865: <div class="sect3">
8866: <div class="titlepage"><div><div><h4 class="title">
8867: <a name="fixes.build.header.gen"></a>21.5.3.2. Headers generated during the build</h4></div></div></div>
8868: <p>If the name of the header seems to come from the package itself,
8869: and if the build is run with parallel jobs, the package may have some
8870: undeclared dependencies between the <code class="filename">.c</code> and the
8871: <code class="filename">.h</code> files, and a C file is compiled before its
8872: required header is generated.</p>
8873: <p>To see whether the build runs with parallel jobs, run
8874: <span class="command"><strong>bmake show-all-build | grep JOBS</strong></span>. Its output looks
8875: like this:</p>
8876: <pre class="programlisting">
8877: usr MAKE_JOBS= 7
8878: pkg MAKE_JOBS_SAFE # undefined
8879: def _MAKE_JOBS_N= 7
8880: </pre>
8881: <p>In this case the pkgsrc user has asked pkgsrc to build packages
8882: with 7 jobs in parallel (<code class="varname">MAKE_JOBS</code>). The
8883: package could have disabled parallel builds by setting
8884: <code class="varname">MAKE_JOBS_SAFE</code> to <code class="literal">no</code>, but
8885: in this case it hasn't.</p>
8886: <p>To see whether the build failure is caused by parallel builds,
8887: first save the exact error message and a bit of context, maybe you need
8888: it later for reporting a bug. Next, run:</p>
8889: <pre class="programlisting">
8890: MAKE_JOBS_SAFE=no bmake clean build
8891: </pre>
8892: <p>If that succeeds, <a class="ulink" href="https://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd" target="_top">file a bug
8893: report</a> against the pkgsrc package, including the exact error
8894: message and the contents of your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file.</p>
8895: </div>
1.173 rillig 8896: <div class="sect3">
8897: <div class="titlepage"><div><div><h4 class="title">
8898: <a name="fixes.build.header.symlink"></a>21.5.3.3. Symlinks</h4></div></div></div>
8899: <p>Pkgsrc does not work reliably if any of
8900: <code class="varname">LOCALBASE</code>, <code class="varname">VARBASE</code> or
8901: <code class="varname">WRKDIR</code> contains a symlink. Since 2019Q2, the pkgsrc
8902: bootstrap program prevents installing pkgsrc in symlink-based
8903: directories. Existing pkgsrc installations are not checked for symlinks
8904: though.</p>
8905: <p>The "No such file or directory" error messages are a typical
8906: symptom of symlinks, and it's quite difficult to find out that this is
8907: the actual cause.</p>
8908: </div>
8909: <div class="sect3">
8910: <div class="titlepage"><div><div><h4 class="title">
8911: <a name="fixes.build.header.stale"></a>21.5.3.4. Stale working directories</h4></div></div></div>
8912: <p>When building a hierarchy of packages, it may happen that one
8913: package is built and then pkgsrc is updated. This situation can provoke
8914: various hard to diagnose build errors. To clean up the situation:</p>
8915: <pre class="programlisting">
1.223 nia 8916: <code class="prompt">$</code> (cd ../../ && cat mk/bsd.pkg.mk >/dev/null && rm -rf */*/work)
1.173 rillig 8917: </pre>
1.223 nia 8918: <p>(The only purpose of the <code class="filename">bsd.pkg.mk</code> is to
8919: prevent running this command in the wrong directory.)</p>
1.173 rillig 8920: <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
8921: that directory as well.</p>
8922: </div>
8923: <div class="sect3">
8924: <div class="titlepage"><div><div><h4 class="title">
8925: <a name="fixes.build.header.misc"></a>21.5.3.5. Other possible reasons</h4></div></div></div>
8926: <p>On platforms other than BSD, third-party packages are installed in
8927: <code class="filename">/usr/include</code>, together with the base system. This
8928: means that pkgsrc cannot distinguish between headers provided by the base
8929: system (which it needs) and headers from third-party packages (which are
8930: often included in pkgsrc as well). This can lead to subtle version
8931: mismatches.</p>
8932: <p>In pkgsrc installations that have been active for several years, it
8933: may happen that some files are manually deleted. To exclude this unlikely
8934: reason, run <span class="command"><strong>pkg_admin check</strong></span>.</p>
8935: <p>It may help to run <span class="command"><strong>pkg_admin rebuild-tree</strong></span> to
8936: check/fix dependencies.</p>
8937: <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>
8938: for contact information. Be prepared to describe what you have tried so
8939: far and what any error messages were.</p>
8940: </div>
1.172 rillig 8941: </div>
8942: <div class="sect2">
8943: <div class="titlepage"><div><div><h3 class="title">
8944: <a name="undefined-reference"></a>21.5.4. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span>
1.23 wiz 8945: </h3></div></div></div>
1.1 dsieger 8946: <p>This error message often means that a package did not
8947: link to a shared library it needs. The following functions are
8948: known to cause this error message over and over.</p>
8949: <div class="informaltable">
1.106 tnn 8950: <a name="undefined-reference-functions"></a><table class="informaltable" border="1">
1.1 dsieger 8951: <colgroup>
8952: <col>
8953: <col>
8954: <col>
8955: </colgroup>
8956: <thead><tr>
8957: <th>Function</th>
8958: <th>Library</th>
8959: <th>Affected platforms</th>
8960: </tr></thead>
8961: <tbody>
8962: <tr>
8963: <td>accept, bind, connect</td>
8964: <td>-lsocket</td>
8965: <td>Solaris</td>
8966: </tr>
8967: <tr>
8968: <td>crypt</td>
8969: <td>-lcrypt</td>
8970: <td>DragonFly, NetBSD</td>
8971: </tr>
8972: <tr>
8973: <td>dlopen, dlsym</td>
8974: <td>-ldl</td>
8975: <td>Linux</td>
8976: </tr>
8977: <tr>
8978: <td>gethost*</td>
8979: <td>-lnsl</td>
8980: <td>Solaris</td>
8981: </tr>
8982: <tr>
8983: <td>inet_aton</td>
8984: <td>-lresolv</td>
8985: <td>Solaris</td>
8986: </tr>
8987: <tr>
8988: <td>nanosleep, sem_*, timer_*</td>
8989: <td>-lrt</td>
8990: <td>Solaris</td>
8991: </tr>
8992: <tr>
8993: <td>openpty</td>
8994: <td>-lutil</td>
8995: <td>Linux</td>
8996: </tr>
8997: </tbody>
8998: </table>
8999: </div>
1.223 nia 9000: <p>To fix these linker errors, it is often sufficient to add
1.1 dsieger 9001: <code class="literal">LIBS.<em class="replaceable"><code>OperatingSystem</code></em>+=
9002: -l<em class="replaceable"><code>foo</code></em></code> to the package
1.223 nia 9003: <code class="filename">Makefile</code> and then run <span class="command"><strong>bmake clean;
1.1 dsieger 9004: bmake</strong></span>.</p>
1.41 asau 9005: <div class="sect3">
1.1 dsieger 9006: <div class="titlepage"><div><div><h4 class="title">
1.223 nia 9007: <a name="undefined-reference-sunpro"></a>21.5.4.1. The SunPro compiler and inline functions</h4></div></div></div>
1.1 dsieger 9008: <p>When you are using the SunPro compiler, there is another
9009: possibility. That compiler cannot handle the following code:</p>
9010: <pre class="programlisting">
9011: extern int extern_func(int);
9012:
9013: static inline int
9014: inline_func(int x)
9015: {
9016: return extern_func(x);
9017: }
9018:
9019: int main(void)
9020: {
9021: return 0;
9022: }
9023: </pre>
9024: <p>It generates the code for <code class="function">inline_func</code> even if
9025: that function is never used. This code then refers to
9026: <code class="function">extern_func</code>, which can usually not be resolved. To
9027: solve this problem you can try to tell the package to disable inlining
9028: of functions.</p>
9029: </div>
1.228 gutterid 9030: <div class="sect3">
9031: <div class="titlepage"><div><div><h4 class="title">
9032: <a name="undefined-reference-atomic"></a>21.5.4.2. Missing atomic functions</h4></div></div></div>
9033: <p>When building for older machine architectures (e.g., i386, PowerPC),
9034: builds may fail because the package expects modern 64-bit atomic functions
9035: which the underlying hardware either doesn't support, or will only support
9036: with specific compiler flags. This is generally handled via inclusion of
9037: mk/atomic64.mk.</p>
9038: </div>
1.1 dsieger 9039: </div>
1.41 asau 9040: <div class="sect2">
1.1 dsieger 9041: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 9042: <a name="out-of-memory"></a>21.5.5. Running out of memory</h3></div></div></div>
1.1 dsieger 9043: <p>Sometimes packages fail to build because the compiler runs
9044: into an operating system specific soft limit. With the
9045: <code class="varname">UNLIMIT_RESOURCES</code> variable pkgsrc can be told
1.223 nia 9046: to unlimit the resources. The allowed values are any combination of
9047: <span class="quote">“<span class="quote">cputime</span>”</span>,
9048: <span class="quote">“<span class="quote">datasize</span>”</span>,
9049: <span class="quote">“<span class="quote">memorysize</span>”</span>,
9050: <span class="quote">“<span class="quote">stacksize</span>”</span> and
9051: <span class="quote">“<span class="quote">virtualsize</span>”</span>.
1.1 dsieger 9052: Setting this variable is similar to running the shell builtin
1.10 hubertf 9053: <span class="command"><strong>ulimit</strong></span> command to raise the maximum data
1.1 dsieger 9054: segment size or maximum stack size of a process, respectively, to
9055: their hard limits.</p>
9056: </div>
9057: </div>
1.41 asau 9058: <div class="sect1">
1.1 dsieger 9059: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9060: <a name="fixes.install"></a>21.6. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
1.41 asau 9061: <div class="sect2">
1.1 dsieger 9062: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9063: <a name="install-scripts"></a>21.6.1. Creating needed directories</h3></div></div></div>
1.10 hubertf 9064: <p>The BSD-compatible <span class="command"><strong>install</strong></span> supplied
1.1 dsieger 9065: with some operating systems cannot create more than one
9066: directory at a time. As such, you should call
9067: <code class="literal">${INSTALL_*_DIR}</code> like this:</p>
9068: <pre class="programlisting">
9069: ${INSTALL_DATA_DIR} ${PREFIX}/dir1
9070: ${INSTALL_DATA_DIR} ${PREFIX}/dir2
1.111 sevan 9071: </pre>
1.223 nia 9072: <p>Instead of running the <span class="command"><strong>install</strong></span> commands
9073: directly, you can also append <span class="quote">“<span class="quote"><code class="literal">dir1
9074: dir2</code></span>”</span> to the <code class="varname">INSTALLATION_DIRS</code>
9075: variable, which will automatically do the right thing.</p>
1.1 dsieger 9076: </div>
1.41 asau 9077: <div class="sect2">
1.1 dsieger 9078: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9079: <a name="where-to-install-documentation"></a>21.6.2. Where to install documentation</h3></div></div></div>
1.1 dsieger 9080: <p>In general, documentation should be installed into
9081: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
1.223 nia 9082: <code class="filename">${PREFIX}/share/doc/${PKGNAME_NOREV}</code> (the latter
1.1 dsieger 9083: includes the version number of the package).</p>
9084: <p>Many modern packages using GNU autoconf allow to set the
9085: directory where HTML documentation is installed with the
1.223 nia 9086: <span class="quote">“<span class="quote">--with-html-dir</span>”</span> option. Sometimes using this flag is
9087: needed because otherwise the documentation ends up in
9088: <code class="filename">${PREFIX}/share/doc/html</code> or other places. In
9089: pkgsrc, the HTML documentation should go into the package-specific
9090: directory, just like any other documentation.</p>
1.1 dsieger 9091: <p>An exception to the above is that library API documentation
1.207 leot 9092: 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 9093: browsers (devhelp) should be left at their default location, which
9094: is <code class="filename">${PREFIX}/share/gtk-doc</code>. Such
9095: documentation can be recognized from files ending in
9096: <code class="filename">.devhelp</code> or <code class="filename">.devhelp2</code>.
9097: (It is also acceptable to install such files in
9098: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
9099: <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code>; the
9100: <code class="filename">.devhelp*</code> file must be directly in that
9101: directory then, no additional subdirectory level is allowed in
9102: this case. This is usually achieved by using
1.23 wiz 9103: <span class="quote">“<span class="quote">--with-html-dir=${PREFIX}/share/doc</span>”</span>.
1.1 dsieger 9104: <code class="filename">${PREFIX}/share/gtk-doc</code> is preferred
9105: though.)</p>
9106: </div>
1.41 asau 9107: <div class="sect2">
1.1 dsieger 9108: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9109: <a name="installing-score-files"></a>21.6.3. Installing highscore files</h3></div></div></div>
1.1 dsieger 9110: <p>Certain packages, most of them in the games category, install
9111: a score file that allows all users on the system to record their
9112: highscores. In order for this to work, the binaries need to be
9113: installed setgid and the score files owned by the appropriate
1.35 wiz 9114: group and/or owner (traditionally the "games" user/group). Set
9115: <code class="varname">USE_GAMESGROUP</code> to yes to support this. The
1.1 dsieger 9116: following variables, documented in more detail in
9117: <code class="filename">mk/defaults/mk.conf</code>, control this
1.35 wiz 9118: behaviour: <code class="varname">GAMEDATAMODE</code>,
9119: <code class="varname">GAMEDIRMODE</code>, <code class="varname">GAMES_GROUP</code>,
1.100 leot 9120: <code class="varname">GAMEMODE</code>, <code class="varname">GAME_USER</code>.
9121: Other useful variables are: <code class="varname">GAMEDIR_PERMS</code>,
9122: <code class="varname">GAMEDATA_PERMS</code> and
9123: <code class="varname">SETGID_GAMES_PERMS</code>.</p>
9124: <p>An example that illustrates some of the variables described above is
9125: <code class="filename">games/moon-buggy</code>. <code class="varname">OWN_DIRS_PERMS</code> is
9126: used to properly set directory permissions of the directory where the
9127: scorefile is saved, <code class="varname">REQD_FILES_PERMS</code> is used to create a
9128: dummy scorefile (<code class="filename">mbscore</code>) with the proper permissions
9129: and <code class="varname">SPECIAL_PERMS</code> is used to install setgid the game
9130: binary:</p>
9131: <pre class="programlisting">
1.112 rillig 9132: USE_GAMESGROUP= yes
1.100 leot 9133:
1.112 rillig 9134: BUILD_DEFS+= VARBASE
1.100 leot 9135:
1.112 rillig 9136: OWN_DIRS_PERMS+= ${VARBASE}/games/moon-buggy ${GAMEDIR_PERMS}
9137: REQD_FILES_PERMS+= /dev/null ${VARBASE}/games/moon-buggy/mbscore ${GAMEDATA_PERMS}
9138: SPECIAL_PERMS+= ${PREFIX}/bin/moon-buggy ${SETGID_GAMES_PERMS}
1.111 sevan 9139: </pre>
1.100 leot 9140: <p>Various <code class="varname">INSTALL_*</code> variables are also available:
9141: <code class="varname">INSTALL_GAME</code> to install setgid game binaries,
9142: <code class="varname">INSTALL_GAME_DIR</code> to install game directories that are
9143: needed to be accessed by setgid games and
9144: <code class="varname">INSTALL_GAME_DATA</code> to install scorefiles.</p>
1.14 jmcneill 9145: <p>A package should therefore never hard code file ownership or
1.100 leot 9146: access permissions but rely on <code class="varname">*_PERMS</code> as described above
9147: or alternatively on <code class="varname">INSTALL_GAME</code>,
9148: <code class="varname">INSTALL_GAME_DATA</code> and
9149: <code class="varname">INSTALL_GAME_DIR</code> to set these correctly.</p>
1.1 dsieger 9150: </div>
1.41 asau 9151: <div class="sect2">
1.1 dsieger 9152: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9153: <a name="destdir-support"></a>21.6.4. Adding DESTDIR support to packages</h3></div></div></div>
1.14 jmcneill 9154: <p><code class="varname">DESTDIR</code> support means that a package
9155: installs into a staging directory, not the final location of the
9156: files. Then a binary package is created which can be used for
9157: installation as usual. There are two ways: Either the package must
1.23 wiz 9158: install as root (<span class="quote">“<span class="quote">destdir</span>”</span>) or the package can
9159: install as non-root user (<span class="quote">“<span class="quote">user-destdir</span>”</span>).</p>
1.41 asau 9160: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9161: <li class="listitem"><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be
1.113 leot 9162: set to <span class="quote">“<span class="quote">destdir</span>”</span> or <span class="quote">“<span class="quote">user-destdir</span>”</span>.
9163: By default <code class="varname">PKG_DESTDIR_SUPPORT</code>
1.38 wiz 9164: is set to <span class="quote">“<span class="quote">user-destdir</span>”</span> to help catching more
9165: potential packaging problems. If bsd.prefs.mk is included in the Makefile,
1.14 jmcneill 9166: <code class="varname">PKG_DESTDIR_SUPPORT</code> needs to be set before
9167: the inclusion.</p></li>
1.23 wiz 9168: <li class="listitem"><p>All installation operations have to be prefixed with
1.4 rillig 9169: <code class="filename">${DESTDIR}</code>.</p></li>
1.23 wiz 9170: <li class="listitem"><p>automake gets this DESTDIR mostly right
1.4 rillig 9171: automatically. Many manual rules and pre/post-install often are
9172: incorrect; fix them.</p></li>
1.23 wiz 9173: <li class="listitem"><p>If files are installed with special owner/group
1.17 imil 9174: use <code class="varname">SPECIAL_PERMS</code>.</p></li>
1.23 wiz 9175: <li class="listitem"><p>In general, packages should support
1.4 rillig 9176: <code class="varname">UNPRIVILEGED</code> to be able to use
9177: DESTDIR.</p></li>
9178: </ul></div>
9179: </div>
1.41 asau 9180: <div class="sect2">
1.4 rillig 9181: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9182: <a name="hardcoded-paths"></a>21.6.5. Packages with hardcoded paths to other interpreters</h3></div></div></div>
1.1 dsieger 9183: <p>Your package may also contain scripts with hardcoded paths to
1.203 nia 9184: other interpreters besides (or as well as) Perl. To correct the
1.1 dsieger 9185: full pathname to the script interpreter, you need to set the
9186: following definitions in your <code class="filename">Makefile</code> (we
1.10 hubertf 9187: shall use <span class="command"><strong>tclsh</strong></span> in this example):</p>
1.1 dsieger 9188: <pre class="programlisting">
9189: REPLACE_INTERPRETER+= tcl
9190: REPLACE.tcl.old= .*/bin/tclsh
9191: REPLACE.tcl.new= ${PREFIX}/bin/tclsh
9192: REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed,
9193: # relative to ${WRKSRC}, just as in REPLACE_PERL
1.111 sevan 9194: </pre>
1.1 dsieger 9195: </div>
1.41 asau 9196: <div class="sect2">
1.1 dsieger 9197: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9198: <a name="perl-modules"></a>21.6.6. Packages installing Perl modules</h3></div></div></div>
1.1 dsieger 9199: <p>Makefiles of packages providing perl5 modules should include
9200: the Makefile fragment
9201: <code class="filename">../../lang/perl5/module.mk</code>. It provides a
1.10 hubertf 9202: <span class="command"><strong>do-configure</strong></span> target for the standard perl
1.1 dsieger 9203: configuration for such modules as well as various hooks to tune
9204: this configuration. See comments in this file for
9205: details.</p>
9206: <p>Perl5 modules will install into different places depending
9207: on the version of perl used during the build process. To
9208: address this, pkgsrc will append lines to the
9209: <code class="filename">PLIST</code> corresponding to the files listed in
9210: the installed <code class="filename">.packlist</code> file generated by
9211: most perl5 modules. This is invoked by defining
9212: <code class="varname">PERL5_PACKLIST</code> to a space-separated list of
1.47 wiz 9213: packlist files relative to <code class="varname">PERL5_PACKLIST_DIR</code>
9214: (<code class="varname">PERL5_INSTALLVENDORARCH</code> by default),
9215: e.g.:</p>
1.1 dsieger 9216: <pre class="programlisting">
1.47 wiz 9217: PERL5_PACKLIST= auto/Pg/.packlist
1.111 sevan 9218: </pre>
1.47 wiz 9219: <p>The perl5 config variables
9220: <code class="varname">installarchlib</code>,
9221: <code class="varname">installscript</code>,
9222: <code class="varname">installvendorbin</code>,
9223: <code class="varname">installvendorscript</code>,
9224: <code class="varname">installvendorarch</code>,
9225: <code class="varname">installvendorlib</code>,
9226: <code class="varname">installvendorman1dir</code>, and
9227: <code class="varname">installvendorman3dir</code> represent those
9228: locations in which components of perl5 modules may be installed,
9229: provided as variable with uppercase and prefixed with
9230: <code class="varname">PERL5_</code>, e.g. <code class="varname">PERL5_INSTALLARCHLIB</code>
9231: and may be used by perl5 packages that don't have a packlist.
9232: These variables are also substituted for in the
9233: <code class="filename">PLIST</code> as uppercase prefixed with
9234: <code class="varname">PERL5_SUB_</code>.</p>
1.1 dsieger 9235: </div>
1.41 asau 9236: <div class="sect2">
1.1 dsieger 9237: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9238: <a name="faq.info-files"></a>21.6.7. Packages installing info files</h3></div></div></div>
1.1 dsieger 9239: <p>Some packages install info files or use the
1.23 wiz 9240: <span class="quote">“<span class="quote">makeinfo</span>”</span> or <span class="quote">“<span class="quote">install-info</span>”</span>
1.1 dsieger 9241: commands. <code class="varname">INFO_FILES</code> should be defined in
9242: the package Makefile so that <code class="filename">INSTALL</code> and
9243: <code class="filename">DEINSTALL</code> scripts will be generated to
9244: handle registration of the info files in the Info directory
1.23 wiz 9245: file. The <span class="quote">“<span class="quote">install-info</span>”</span> command used for the info
1.1 dsieger 9246: files registration is either provided by the system, or by a
9247: special purpose package automatically added as dependency if
9248: needed.</p>
9249: <p><code class="varname">PKGINFODIR</code> is the directory under
9250: <code class="filename">${PREFIX}</code> where info files are primarily
9251: located. <code class="varname">PKGINFODIR</code> defaults to
1.23 wiz 9252: <span class="quote">“<span class="quote">info</span>”</span> and can be overridden by the user.</p>
1.1 dsieger 9253: <p>The info files for the package should be listed in the
9254: package <code class="filename">PLIST</code>; however any split info files
9255: need not be listed.</p>
1.23 wiz 9256: <p>A package which needs the <span class="quote">“<span class="quote">makeinfo</span>”</span> command
9257: at build time must add <span class="quote">“<span class="quote">makeinfo</span>”</span> to
1.1 dsieger 9258: <code class="varname">USE_TOOLS</code> in its Makefile. If a minimum
1.23 wiz 9259: version of the <span class="quote">“<span class="quote">makeinfo</span>”</span> command is needed it
1.1 dsieger 9260: should be noted with the <code class="varname">TEXINFO_REQD</code>
9261: variable in the package <code class="filename">Makefile</code>. By
9262: default, a minimum version of 3.12 is required. If the system
1.10 hubertf 9263: does not provide a <span class="command"><strong>makeinfo</strong></span> command or if it
1.1 dsieger 9264: does not match the required minimum, a build dependency on the
1.207 leot 9265: <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 9266: be added automatically.</p>
9267: <p>The build and installation process of the software provided
9268: by the package should not use the
1.10 hubertf 9269: <span class="command"><strong>install-info</strong></span> command as the registration of
1.1 dsieger 9270: info files is the task of the package
9271: <code class="filename">INSTALL</code> script, and it must use the
1.10 hubertf 9272: appropriate <span class="command"><strong>makeinfo</strong></span> command.</p>
1.1 dsieger 9273: <p>To achieve this goal, the pkgsrc infrastructure creates
1.10 hubertf 9274: overriding scripts for the <span class="command"><strong>install-info</strong></span> and
9275: <span class="command"><strong>makeinfo</strong></span> commands in a directory listed early
1.1 dsieger 9276: in <code class="varname">PATH</code>.</p>
1.10 hubertf 9277: <p>The script overriding <span class="command"><strong>install-info</strong></span> has
1.1 dsieger 9278: no effect except the logging of a message. The script overriding
1.10 hubertf 9279: <span class="command"><strong>makeinfo</strong></span> logs a message and according to the
1.1 dsieger 9280: value of <code class="varname">TEXINFO_REQD</code> either runs the appropriate
1.10 hubertf 9281: <span class="command"><strong>makeinfo</strong></span> command or exit on error.</p>
1.1 dsieger 9282: </div>
1.41 asau 9283: <div class="sect2">
1.1 dsieger 9284: <div class="titlepage"><div><div><h3 class="title">
1.154 rillig 9285: <a name="manpages"></a>21.6.8. Packages installing man pages</h3></div></div></div>
1.1 dsieger 9286: <p>All packages that install manual pages should install them
9287: into the same directory, so that there is one common place to look
9288: for them. In pkgsrc, this place is
9289: <code class="literal">${PREFIX}/${PKGMANDIR}</code>, and this expression
9290: should be used in packages. The default for
9291: <code class="varname">PKGMANDIR</code> is
1.23 wiz 9292: <span class="quote">“<span class="quote"><code class="filename">man</code></span>”</span>. Another often-used value
9293: is <span class="quote">“<span class="quote"><code class="filename">share/man</code></span>”</span>.</p>
1.41 asau 9294: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9295: <h3 class="title">Note</h3>
9296: <p>The support for a custom <code class="varname">PKGMANDIR</code>
9297: is far from complete.</p>
9298: </div>
9299: <p>The <code class="filename">PLIST</code> files can just use
9300: <code class="filename">man/</code> as the top level directory for the man
9301: page file entries, and the pkgsrc framework will convert as
9302: needed. In all other places, the correct
9303: <code class="varname">PKGMANDIR</code> must be used.</p>
9304: <p>Packages that are
9305: configured with <code class="varname">GNU_CONFIGURE</code> set as
1.23 wiz 9306: <span class="quote">“<span class="quote">yes</span>”</span>, by default will use the
1.1 dsieger 9307: <code class="filename">./configure</code>
9308: --mandir switch to set where the man pages should be installed.
9309: The path is <code class="varname">GNU_CONFIGURE_MANDIR</code> which defaults
9310: to <code class="varname">${PREFIX}/${PKGMANDIR}</code>.</p>
9311: <p>Packages that use <code class="varname">GNU_CONFIGURE</code> but do not
9312: use --mandir, can set <code class="varname">CONFIGURE_HAS_MANDIR</code>
1.23 wiz 9313: to <span class="quote">“<span class="quote">no</span>”</span>.
1.1 dsieger 9314: Or if the <code class="filename">./configure</code> script uses
9315: a non-standard use of --mandir, you can set
9316: <code class="varname">GNU_CONFIGURE_MANDIR</code> as needed.</p>
1.184 rillig 9317: <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 9318: information on installation of compressed manual pages.</p>
9319: </div>
1.41 asau 9320: <div class="sect2">
1.1 dsieger 9321: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9322: <a name="x11-fonts"></a>21.6.9. Packages installing X11 fonts</h3></div></div></div>
1.1 dsieger 9323: <p>If a package installs font files, you will need to rebuild
9324: the fonts database in the directory where they get installed at
9325: installation and deinstallation time. This can be automatically
9326: done by using the pkginstall framework.</p>
9327: <p>You can list the directories where fonts are installed in the
9328: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code>
9329: variables, where <em class="replaceable"><code>type</code></em> can be one of
1.23 wiz 9330: <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 9331: Also make sure that the database file
9332: <code class="filename">fonts.dir</code> is not listed in the PLIST.</p>
9333: <p>Note that you should not create new directories for fonts;
9334: instead use the standard ones to avoid that the user needs to
9335: manually configure his X server to find them.</p>
9336: </div>
1.41 asau 9337: <div class="sect2">
1.1 dsieger 9338: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9339: <a name="sgml-xml-data"></a>21.6.10. Packages installing SGML or XML data</h3></div></div></div>
1.1 dsieger 9340: <p>If a package installs SGML or XML data files that need to be
9341: registered in system-wide catalogs (like DTDs, sub-catalogs,
9342: etc.), you need to take some extra steps:</p>
1.23 wiz 9343: <div class="orderedlist"><ol class="orderedlist" type="1">
9344: <li class="listitem"><p>Include
1.1 dsieger 9345: <code class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in
9346: your <code class="filename">Makefile</code>, which takes care of
9347: registering those files in system-wide catalogs at
9348: installation and deinstallation time.</p></li>
1.23 wiz 9349: <li class="listitem"><p>Set <code class="varname">SGML_CATALOGS</code> to the full path of
1.1 dsieger 9350: any SGML catalogs installed by the package.</p></li>
1.23 wiz 9351: <li class="listitem"><p>Set <code class="varname">XML_CATALOGS</code> to the full path of
1.1 dsieger 9352: any XML catalogs installed by the package.</p></li>
1.23 wiz 9353: <li class="listitem"><p>Set <code class="varname">SGML_ENTRIES</code> to individual entries
1.1 dsieger 9354: to be added to the SGML catalog. These come in groups of
9355: three strings; see xmlcatmgr(1) for more information
9356: (specifically, arguments recognized by the 'add' action).
9357: Note that you will normally not use this variable.</p></li>
1.23 wiz 9358: <li class="listitem"><p>Set <code class="varname">XML_ENTRIES</code> to individual entries
1.1 dsieger 9359: to be added to the XML catalog. These come in groups of three
9360: strings; see xmlcatmgr(1) for more information (specifically,
9361: arguments recognized by the 'add' action). Note that you will
9362: normally not use this variable.</p></li>
9363: </ol></div>
9364: </div>
1.41 asau 9365: <div class="sect2">
1.1 dsieger 9366: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9367: <a name="mime-database"></a>21.6.11. Packages installing extensions to the MIME database</h3></div></div></div>
1.1 dsieger 9368: <p>If a package provides extensions to the MIME database by
9369: installing <code class="filename">.xml</code> files inside
9370: <code class="filename">${PREFIX}/share/mime/packages</code>, you
9371: need to take some extra steps to ensure that the database is kept
9372: consistent with respect to these new files:</p>
1.23 wiz 9373: <div class="orderedlist"><ol class="orderedlist" type="1">
9374: <li class="listitem"><p>Include
1.1 dsieger 9375: <code class="filename">../../databases/shared-mime-info/mimedb.mk</code>
9376: (avoid using the <code class="filename">buildlink3.mk</code> file from
9377: this same directory, which is reserved for inclusion from
9378: other <code class="filename">buildlink3.mk</code> files). It takes
9379: care of rebuilding the MIME database at installation and
9380: deinstallation time, and disallows any access to it directly
9381: from the package.</p></li>
1.23 wiz 9382: <li class="listitem"><p>Check the PLIST and remove any entries under the
1.1 dsieger 9383: <code class="filename">share/mime</code> directory,
9384: <span class="emphasis"><em>except</em></span> for files saved under
9385: <code class="filename">share/mime/packages</code>. The former are
9386: handled automatically by
9387: the update-mime-database program, but the latter are
9388: package-dependent and must be removed by the package that
9389: installed them in the first place.</p></li>
1.23 wiz 9390: <li class="listitem"><p>Remove any <code class="filename">share/mime/*</code> directories
1.1 dsieger 9391: from the PLIST. They will be handled by the shared-mime-info
9392: package.</p></li>
9393: </ol></div>
9394: </div>
1.41 asau 9395: <div class="sect2">
1.1 dsieger 9396: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9397: <a name="intltool"></a>21.6.12. Packages using intltool</h3></div></div></div>
1.1 dsieger 9398: <p>If a package uses intltool during its build, add
9399: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>,
9400: which forces it to use the intltool package provided by pkgsrc,
9401: instead of the one bundled with the distribution file.</p>
9402: <p>This tracks intltool's build-time dependencies and uses the
9403: latest available version; this way, the package benefits of any
9404: bug fixes that may have appeared since it was released.</p>
9405: </div>
1.41 asau 9406: <div class="sect2">
1.1 dsieger 9407: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9408: <a name="startup-scripts"></a>21.6.13. Packages installing startup scripts</h3></div></div></div>
1.1 dsieger 9409: <p>If a package contains a rc.d script, it won't be copied into
9410: the startup directory by default, but you can enable it, by adding
9411: the option <code class="varname">PKG_RCD_SCRIPTS=YES</code> in
1.10 hubertf 9412: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. This option will copy the scripts
1.1 dsieger 9413: into <code class="filename">/etc/rc.d</code> when a package is installed, and
9414: it will automatically remove the scripts when the package is
9415: deinstalled.</p>
9416: </div>
1.41 asau 9417: <div class="sect2">
1.1 dsieger 9418: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9419: <a name="tex-packages"></a>21.6.14. Packages installing TeX modules</h3></div></div></div>
1.1 dsieger 9420: <p>If a package installs TeX packages into the texmf tree,
9421: the <code class="filename">ls-R</code> database of the tree needs to be
9422: updated.</p>
1.41 asau 9423: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9424: <h3 class="title">Note</h3>
1.22 jakllsch 9425: <p>Except the main TeX packages such as kpathsea,
1.1 dsieger 9426: packages should install files
1.22 jakllsch 9427: into <code class="filename">${PREFIX}/share/texmf-dist</code>,
9428: not <code class="filename">${PREFIX}/share/texmf</code>.</p>
1.1 dsieger 9429: </div>
1.23 wiz 9430: <div class="orderedlist"><ol class="orderedlist" type="1">
9431: <li class="listitem"><p>Include
1.22 jakllsch 9432: <code class="filename">../../print/kpathsea/texmf.mk</code>. This
1.1 dsieger 9433: takes care of rebuilding the <code class="filename">ls-R</code>
9434: database at installation and deinstallation time.</p></li>
1.23 wiz 9435: <li class="listitem">
1.1 dsieger 9436: <p>If your package installs files into a texmf
9437: tree other than the one
1.22 jakllsch 9438: at <code class="filename">${PREFIX}/share/texmf-dist</code>,
9439: set <code class="varname">TEX_TEXMF_DIRS</code> to the list of all texmf
1.1 dsieger 9440: trees that need database update.</p>
9441: <p>If your package also installs font map files that need
1.10 hubertf 9442: to be registered using <span class="command"><strong>updmap</strong></span>,
1.29 dholland 9443: include <code class="filename">../../print/tex-tetex/map.mk</code> and
1.22 jakllsch 9444: set <code class="varname">TEX_MAP_FILES</code> and/or
9445: <code class="varname">TEX_MIXEDMAP_FILES</code> to the list of all
1.10 hubertf 9446: such font map files. Then <span class="command"><strong>updmap</strong></span> will
1.1 dsieger 9447: be run automatically at installation/deinstallation to
9448: enable/disable font map files for TeX output
9449: drivers.</p>
9450: </li>
1.23 wiz 9451: <li class="listitem"><p>Make sure that none of <code class="filename">ls-R</code>
1.1 dsieger 9452: databases are included in <code class="filename">PLIST</code>, as
1.29 dholland 9453: they will be removed only by the kpathsea package.</p></li>
1.1 dsieger 9454: </ol></div>
9455: </div>
1.41 asau 9456: <div class="sect2">
1.1 dsieger 9457: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9458: <a name="emulation-packages"></a>21.6.15. Packages supporting running binaries in
1.1 dsieger 9459: emulation</h3></div></div></div>
9460: <p>There are some packages that provide libraries and
9461: executables for running binaries from a one operating system
9462: on a different one (if the latter supports it). One example
9463: is running Linux binaries on NetBSD.</p>
1.207 leot 9464: <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 9465: helps in extracting and packaging Linux rpm packages.</p>
9466: <p>The <code class="varname">CHECK_SHLIBS</code> can be set to no to
1.10 hubertf 9467: avoid the <span class="command"><strong>check-shlibs</strong></span> target, which tests
1.1 dsieger 9468: if all libraries for each installed executable can be found by
9469: the dynamic linker. Since the standard dynamic linker is run,
9470: this fails for emulation packages, because the libraries used
9471: by the emulation are not in the standard directories.</p>
9472: </div>
1.184 rillig 9473: <div class="sect2">
9474: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9475: <a name="hicolor-theme"></a>21.6.16. Packages installing hicolor icons</h3></div></div></div>
1.184 rillig 9476: <p>If a package installs images under the
9477: <code class="filename">share/icons/hicolor</code> and/or updates the
9478: <code class="filename">share/icons/hicolor/icon-theme.cache</code>
9479: database, you need to take some extra steps to make sure that the
9480: shared theme directory is handled appropriately and that the cache
9481: database is rebuilt:</p>
9482: <div class="orderedlist"><ol class="orderedlist" type="1">
9483: <li class="listitem"><p>Include
9484: <code class="filename">../../graphics/hicolor-icon-theme/buildlink3.mk</code>.</p></li>
9485: <li class="listitem"><p>Check the <code class="filename">PLIST</code> and remove the
9486: entry that refers to the theme cache.</p></li>
9487: <li class="listitem"><p>Ensure that the PLIST does not remove the shared icon
9488: directories from the <code class="filename">share/icons/hicolor</code>
9489: hierarchy because they will be handled automatically.</p></li>
9490: </ol></div>
9491: <p>The best way to verify that the PLIST is correct with
9492: respect to the last two points is to regenerate it using
9493: <span class="command"><strong>make print-PLIST</strong></span>.</p>
9494: </div>
9495: <div class="sect2">
9496: <div class="titlepage"><div><div><h3 class="title">
1.203 nia 9497: <a name="desktop-files"></a>21.6.17. Packages installing desktop files</h3></div></div></div>
1.184 rillig 9498: <p>If a package installs <code class="filename">.desktop</code> files
9499: under <code class="filename">share/applications</code> and these include
9500: MIME information (MimeType key), you need to take extra steps to
9501: ensure that they are registered into the MIME database:</p>
9502: <div class="orderedlist"><ol class="orderedlist" type="1">
9503: <li class="listitem"><p>Include
9504: <code class="filename">../../sysutils/desktop-file-utils/desktopdb.mk</code>.</p></li>
9505: <li class="listitem"><p>Check the PLIST and remove the entry that refers to the
9506: <code class="filename">share/applications/mimeinfo.cache</code> file.
9507: It will be handled automatically.</p></li>
9508: </ol></div>
9509: <p>The best way to verify that the PLIST is correct with
9510: respect to the last point is to regenerate it using <span class="command"><strong>make
9511: print-PLIST</strong></span>.</p>
9512: </div>
9513: </div>
9514: <div class="sect1">
9515: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9516: <a name="punting"></a>21.7. Marking packages as having problems</h2></div></div></div>
9517: <p>In some cases one does not have the time to solve a problem
9518: immediately. In this case, one can plainly mark a package as broken. For
9519: this, one just sets the variable <code class="varname">BROKEN</code> to the
9520: reason why the package is broken (similar to the
9521: <code class="varname">PKG_FAIL_REASON</code> variable). A user trying to build
9522: the package will immediately be shown this message, and the build
9523: will not be even tried.</p>
9524: <p><code class="varname">BROKEN</code> packages are removed from pkgsrc in irregular
9525: intervals.</p>
9526: </div>
9527: </div>
9528: <div class="chapter">
9529: <div class="titlepage"><div><div><h2 class="title">
9530: <a name="gnome"></a>Chapter 22. GNOME packaging and porting</h2></div></div></div>
9531: <div class="toc">
9532: <p><b>Table of Contents</b></p>
9533: <dl class="toc">
9534: <dt><span class="sect1"><a href="#meta-packages">22.1. Meta packages</a></span></dt>
9535: <dt><span class="sect1"><a href="#new-package">22.2. Packaging a GNOME application</a></span></dt>
9536: <dt><span class="sect1"><a href="#full-update">22.3. Updating GNOME to a newer version</a></span></dt>
9537: <dt><span class="sect1"><a href="#patching">22.4. Patching guidelines</a></span></dt>
9538: </dl>
9539: </div>
9540: <p>Quoting <a class="ulink" href="https://www.gnome.org/" target="_top">GNOME's web
9541: site</a>:</p>
9542: <div class="blockquote"><blockquote class="blockquote"><p>The GNOME project provides two things: The GNOME desktop
9543: environment, an intuitive and attractive desktop for users, and the
9544: GNOME development platform, an extensive framework for building
9545: applications that integrate into the rest of the desktop.</p></blockquote></div>
9546: <p>pkgsrc provides a seamless way to automatically build and install
9547: a complete GNOME environment <span class="emphasis"><em>under many different
9548: platforms</em></span>. We can say with confidence that pkgsrc is one of
9549: the most advanced build and packaging systems for GNOME due to its
9550: included technologies buildlink3, the wrappers and tools framework and
9551: automatic configuration file management. Lots of efforts are put into
9552: achieving a completely clean deinstallation of installed software
9553: components.</p>
9554: <p>Given that pkgsrc is <a class="ulink" href="https://www.NetBSD.org/" target="_top">NetBSD</a>'s official packaging system,
9555: the above also means that great efforts are put into making GNOME work
1.201 cirnatda 9556: under this operating system.</p>
1.184 rillig 9557: <p>This chapter is aimed at pkgsrc developers and other people
9558: interested in helping our GNOME porting and packaging efforts. It
9559: provides instructions on how to manage the existing packages and some
9560: important information regarding their internals.</p>
9561: <div class="sect1">
9562: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9563: <a name="meta-packages"></a>22.1. Meta packages</h2></div></div></div>
9564: <p>pkgsrc includes three GNOME-related meta packages:</p>
9565: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.207 leot 9566: <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 9567: the core GNOME desktop environment. It only includes the necessary
9568: bits to get it to boot correctly, although it may lack important
9569: functionality for daily operation. The idea behind this package is
9570: to let end users build their own configurations on top of this one,
9571: first installing this meta package to achieve a functional setup and
9572: then adding individual applications.</p></li>
1.207 leot 9573: <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 9574: complete installation of the GNOME platform and desktop as defined
9575: by the GNOME project; this is based on the components distributed in
9576: the <code class="filename">platform/x.y/x.y.z/sources</code> and
9577: <code class="filename">desktop/x.y/x.y.z/sources</code> directories of the
9578: official FTP server. Developer-only tools found in those
9579: directories are not installed unless required by some other
9580: component to work properly. Similarly, packages from the bindings
9581: set (<code class="filename">bindings/x.y/x.y.z/sources</code>) are not pulled
9582: in unless required as a dependency for an end-user component. This
1.207 leot 9583: 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>
9584: <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 9585: Installs all the tools required to build a GNOME component when
9586: fetched from the CVS repository. These are required to let the
9587: <span class="command"><strong>autogen.sh</strong></span> scripts work appropriately.</p></li>
9588: </ul></div>
9589: <p>In all these packages, the <code class="varname">DEPENDS</code> lines are
9590: sorted in a way that eases updates: a package may depend on other
9591: packages listed before it but not on any listed after it. It is very
9592: important to keep this order to ease updates so... <span class="emphasis"><em>do not
9593: change it to alphabetical sorting!</em></span></p>
9594: </div>
9595: <div class="sect1">
9596: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9597: <a name="new-package"></a>22.2. Packaging a GNOME application</h2></div></div></div>
9598: <p>Almost all GNOME applications are written in C and use a common
9599: set of tools as their build system. Things get different with the new
9600: bindings to other languages (such as Python), but the following will
9601: give you a general idea on the minimum required tools:</p>
9602: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9603: <li class="listitem">
9604: <p>Almost all GNOME applications use the GNU Autotools as their
9605: build system. As a general rule you will need to tell this to your
9606: package:</p>
9607: <pre class="programlisting">
1.223 nia 9608: GNU_CONFIGURE= yes
9609: USE_LIBTOOL= yes
9610: USE_TOOLS+= gmake
1.184 rillig 9611: </pre>
9612: </li>
9613: <li class="listitem">
9614: <p>If the package uses pkg-config to detect dependencies, add this
9615: tool to the list of required utilities:</p>
9616: <pre class="programlisting">
1.223 nia 9617: USE_TOOLS+= pkg-config
1.184 rillig 9618: </pre>
1.207 leot 9619: <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 9620: the end of the build process to ensure that you did not miss to
9621: specify any dependency in your package and that the version
9622: requirements are all correct.</p>
9623: </li>
9624: <li class="listitem"><p>If the package uses intltool, be sure to add
9625: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>
9626: to handle dependencies and to force the package to use the latest
9627: available version.</p></li>
9628: <li class="listitem">
9629: <p>If the package uses gtk-doc (a documentation generation
9630: utility), do <span class="emphasis"><em>not</em></span> add a dependency on it. The
9631: tool is rather big and the distfile should come with pregenerated
9632: documentation anyway; if it does not, it is a bug that you ought to
9633: report. For such packages you should disable gtk-doc (unless it is
9634: the default):</p>
9635: <pre class="programlisting">
1.223 nia 9636: CONFIGURE_ARGS+= --disable-gtk-doc
1.184 rillig 9637: </pre>
9638: <p>The default location of installed HTML files
9639: (<code class="filename">share/gtk-doc/<package-name></code>) is correct
9640: and should not be changed unless the package insists on installing
9641: them somewhere else. Otherwise programs as
9642: <span class="command"><strong>devhelp</strong></span> will not be able to open them. You can
9643: do that with an entry similar to:</p>
9644: <pre class="programlisting">
1.223 nia 9645: CONFIGURE_ARGS+= --with-html-dir=${PREFIX}/share/gtk-doc/...
1.184 rillig 9646: </pre>
9647: </li>
9648: </ul></div>
9649: <p>GNOME uses multiple <span class="emphasis"><em>shared</em></span> directories and
9650: files under the installation prefix to maintain databases. In this
9651: context, shared means that those exact same directories and files are
9652: used among several different packages, leading to conflicts in the
9653: <code class="filename">PLIST</code>. pkgsrc currently includes functionality to
9654: handle the most common cases, so you have to forget about using
9655: <code class="literal">@unexec ${RMDIR}</code> lines in your file lists and
9656: omitting shared files from them. If you find yourself doing those,
9657: <span class="emphasis"><em>your package is most likely incorrect</em></span>.</p>
9658: <p>The following table lists the common situations that result in
9659: using shared directories or files. For each of them, the appropriate
9660: solution is given. After applying the solution be sure to
9661: <span class="emphasis"><em>regenerate the package's file list</em></span> with
9662: <span class="command"><strong>make print-PLIST</strong></span> and ensure it is correct.</p>
9663: <div class="table">
9664: <a name="plist-handling"></a><p class="title"><b>Table 22.1. PLIST handling for GNOME packages</b></p>
9665: <div class="table-contents"><table class="table" summary="PLIST handling for GNOME packages" border="1">
9666: <colgroup>
9667: <col>
9668: <col>
9669: </colgroup>
9670: <thead><tr>
9671: <th>If the package...</th>
9672: <th>Then...</th>
9673: </tr></thead>
9674: <tbody>
9675: <tr>
9676: <td>Installs icons under the
9677: <code class="filename">share/icons/hicolor</code> hierarchy or updates
9678: <code class="filename">share/icons/hicolor/icon-theme.cache</code>.</td>
1.203 nia 9679: <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 9680: </tr>
9681: <tr>
9682: <td>Installs files under
9683: <code class="filename">share/mime/packages</code>.</td>
1.203 nia 9684: <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 9685: </tr>
9686: <tr>
9687: <td>Installs <code class="filename">.desktop</code> files under
9688: <code class="filename">share/applications</code> and these include MIME
9689: information.</td>
1.203 nia 9690: <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 9691: </tr>
9692: </tbody>
9693: </table></div>
1.1 dsieger 9694: </div>
1.184 rillig 9695: <br class="table-break">
1.1 dsieger 9696: </div>
1.41 asau 9697: <div class="sect1">
1.1 dsieger 9698: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 9699: <a name="full-update"></a>22.3. Updating GNOME to a newer version</h2></div></div></div>
9700: <p>When seeing GNOME as a whole, there are two kinds of
9701: updates:</p>
9702: <div class="variablelist"><dl class="variablelist">
9703: <dt><span class="term">Major update</span></dt>
9704: <dd>
9705: <p>Given that there is still a very long way for GNOME 3 (if it
9706: ever appears), we consider a major update one that goes from a
9707: <code class="literal">2.X</code> version to a <code class="literal">2.Y</code> one,
9708: where <code class="literal">Y</code> is even and greater than
9709: <code class="literal">X</code>. These are hard to achieve because they
9710: introduce lots of changes in the components' code and almost all
9711: GNOME distfiles are updated to newer versions. Some of them can
9712: even break API and ABI compatibility with the previous major
9713: version series. As a result, the update needs to be done all at
9714: once to minimize breakage.</p>
9715: <p>A major update typically consists of around 80 package
9716: updates and the addition of some new ones.</p>
9717: </dd>
9718: <dt><span class="term">Minor update</span></dt>
9719: <dd>
9720: <p>We consider a minor update one that goes from a
9721: <code class="literal">2.A.X</code> version to a <code class="literal">2.A.Y</code>
9722: one where <code class="literal">Y</code> is greater than
9723: <code class="literal">X</code>. These are easy to achieve because they do
9724: not update all GNOME components, can be done in an incremental way
9725: and do not break API nor ABI compatibility.</p>
9726: <p>A minor update typically consists of around 50 package
9727: updates, although the numbers here may vary a lot.</p>
9728: </dd>
9729: </dl></div>
9730: <p>In order to update the GNOME components in pkgsrc to a new stable
9731: release (either major or minor), the following steps should be
9732: followed:</p>
9733: <div class="orderedlist"><ol class="orderedlist" type="1">
1.23 wiz 9734: <li class="listitem">
1.184 rillig 9735: <p>Get a list of all the tarballs that form the new release by
9736: using the following commands. These will leave the full list of the
9737: components' distfiles into the <code class="filename">list.txt</code>
9738: file:</p>
9739: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9740: ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
9741: awk '{ print $9 }' >list.txt</code></strong>
9742: <code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
9743: ftp -V ftp://ftp.gnome.org/pub/gnome/desktop/x.y/x.y.z/sources/ | \
9744: awk '{ print $9 }' >>list.txt</code></strong></pre>
1.1 dsieger 9745: </li>
1.184 rillig 9746: <li class="listitem"><p>Open each meta package's <code class="filename">Makefile</code> and
9747: bump their version to the release you are updating them to. The
9748: three meta packages should be always consistent with versioning.
9749: Obviously remove any <code class="varname">PKGREVISION</code>s that might be
9750: in them.</p></li>
1.23 wiz 9751: <li class="listitem">
1.184 rillig 9752: <p>For each meta package, update all its
9753: <code class="varname">DEPENDS</code> lines to match the latest versions as
9754: shown by the above commands. Do <span class="emphasis"><em>not</em></span> list any
9755: newer version (even if found in the FTP) because the meta packages
9756: are supposed to list the exact versions that form a specific GNOME
9757: release. Exceptions are permitted here if a newer version solves a
9758: serious issue in the overall desktop experience; these typically
9759: come in the form of a revision bump in pkgsrc, not in newer versions
9760: from the developers.</p>
9761: <p>Packages not listed in the <code class="filename">list.txt</code> file
9762: should be updated to the latest version available (if found in
9763: pkgsrc). This is the case, for example, of the dependencies on the
1.207 leot 9764: 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 9765: </li>
1.23 wiz 9766: <li class="listitem">
1.184 rillig 9767: <p>Generate a patch from the modified meta packages and extract the
9768: list of "new" lines. This will provide you an outline on what
9769: packages need to be updated in pkgsrc and in what order:</p>
9770: <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 9771: </li>
1.184 rillig 9772: <li class="listitem"><p>For major desktop updates it is recommended to zap all your
9773: installed packages and start over from scratch at this point.</p></li>
9774: <li class="listitem"><p>Now comes the longest step by far: iterate over the contents
9775: of <code class="filename">todo.txt</code> and update the packages listed in
9776: it in order. For major desktop updates none of these should be
9777: committed until the entire set is completed because there are chances
9778: of breaking not-yet-updated packages.</p></li>
9779: <li class="listitem"><p>Once the packages are up to date and working, commit them to
9780: the tree one by one with appropriate log messages. At the end,
9781: commit the three meta package updates and all the corresponding
9782: changes to the <code class="filename">doc/CHANGES-<YEAR></code> and
9783: <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>
9784: </ol></div>
9785: </div>
9786: <div class="sect1">
9787: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9788: <a name="patching"></a>22.4. Patching guidelines</h2></div></div></div>
9789: <p>GNOME is a very big component in pkgsrc which approaches 100
9790: packages. Please, it is very important that you always, always,
9791: <span class="strong"><strong>always</strong></span> feed back any portability
9792: 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
9793: their attention on portability issues and to ensure that future versions
9794: can be built out-of-the box on NetBSD. The less custom patches in
9795: pkgsrc, the easier further updates are. Those developers in charge of
9796: issuing major GNOME updates will be grateful if you do that.</p>
1.200 cirnatda 9797: <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
9798: GitLab</a>. Not all components use these to track bugs, but most
1.184 rillig 9799: of them do. Do not be short on your reports: always provide detailed
9800: explanations of the current failure, how it can be improved to achieve
1.200 cirnatda 9801: maximum portability and, if at all possible, provide a patch against the
9802: main Git branch. The more verbose you are, the higher chances of your
9803: patch being accepted.</p>
1.184 rillig 9804: <p>Also, please avoid using preprocessor magic to fix portability
9805: issues. While the FreeBSD GNOME people are doing a great job in porting
9806: GNOME to their operating system, the official GNOME sources are now
9807: plagued by conditionals that check for <code class="varname">__FreeBSD__</code>
9808: and similar macros. This hurts portability. Please see our patching
9809: guidelines (<a class="xref" href="#components.patches.guidelines" title="12.3.4. Patching guidelines">Section 12.3.4, “Patching guidelines”</a>) for more
9810: details.</p>
9811: </div>
1.1 dsieger 9812: </div>
1.41 asau 9813: <div class="chapter">
1.1 dsieger 9814: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 9815: <a name="submit"></a>Chapter 23. Submitting and Committing</h2></div></div></div>
1.1 dsieger 9816: <div class="toc">
9817: <p><b>Table of Contents</b></p>
1.100 leot 9818: <dl class="toc">
1.154 rillig 9819: <dt><span class="sect1"><a href="#submitting-binary-packages">23.1. Submitting binary packages</a></span></dt>
9820: <dt><span class="sect1"><a href="#submitting-your-package">23.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
9821: <dt><span class="sect1"><a href="#general-notes-for-changes">23.3. General notes when adding, updating, or removing packages</a></span></dt>
9822: <dt><span class="sect1"><a href="#commit-messages">23.4. Commit Messages</a></span></dt>
9823: <dt><span class="sect1"><a href="#committing-importing">23.5. Committing: Adding a package to CVS</a></span></dt>
9824: <dt><span class="sect1"><a href="#updating-package">23.6. Updating a package to a newer version</a></span></dt>
9825: <dt><span class="sect1"><a href="#renaming-package">23.7. Renaming a package in pkgsrc</a></span></dt>
9826: <dt><span class="sect1"><a href="#moving-package">23.8. Moving a package in pkgsrc</a></span></dt>
1.1 dsieger 9827: </dl>
9828: </div>
1.41 asau 9829: <div class="sect1">
1.1 dsieger 9830: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9831: <a name="submitting-binary-packages"></a>23.1. Submitting binary packages</h2></div></div></div>
1.1 dsieger 9832: <p>Our policy is that we accept binaries only from pkgsrc
9833: developers to guarantee that the packages don't contain any
9834: trojan horses etc. This is not to annoy anyone but rather to
9835: protect our users! You're still free to put up your home-made
9836: binary packages and tell the world where to get them. NetBSD
9837: developers doing bulk builds and wanting to upload them please
1.154 rillig 9838: 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 9839: builds)</i></a>.</p>
1.1 dsieger 9840: </div>
1.41 asau 9841: <div class="sect1">
1.1 dsieger 9842: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9843: <a name="submitting-your-package"></a>23.2. Submitting source packages (for non-NetBSD-developers)</h2></div></div></div>
1.218 nia 9844: <p>Firstly, you can import new packages into
9845: pkgsrc-wip (<span class="quote">“<span class="quote">pkgsrc work-in-progress</span>”</span>); see the
9846: homepage at <a class="ulink" href="https://pkgsrc.org/wip/" target="_top">https://pkgsrc.org/wip/</a>
9847: for details.</p>
9848: <p>Next, check that your package is complete, compiles and
1.184 rillig 9849: 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 9850: 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>
9851: tool and fix any errors that appear.</p>
9852: <p>Finally, send a report to the pkgsrc bug tracking system,
1.207 leot 9853: either with the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> command, or if you don't have
1.1 dsieger 9854: that, go to the web page
1.174 leot 9855: <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 9856: which contains some instructions and a link to a form where you
9857: can submit packages. The
1.207 leot 9858: <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 9859: also available as a substitute for either of the above two tools.
9860: </p>
1.1 dsieger 9861: <p>In the form of the problem report, the category should be
1.23 wiz 9862: <span class="quote">“<span class="quote">pkg</span>”</span>, the synopsis should include the package name
1.1 dsieger 9863: and version number, and the description field should contain a
9864: short description of your package (contents of the COMMENT
1.218 nia 9865: variable or DESCR file are OK).</p>
1.1 dsieger 9866: </div>
1.41 asau 9867: <div class="sect1">
1.1 dsieger 9868: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9869: <a name="general-notes-for-changes"></a>23.3. General notes when adding, updating, or removing packages</h2></div></div></div>
1.1 dsieger 9870: <p>Please note all package additions, updates, moves, and
9871: removals in <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code>. It's very
9872: important to keep this file up to date and conforming to the
9873: existing format, because it will be used by scripts to
1.174 leot 9874: automatically update pages on <a class="ulink" href="https://www.NetBSD.org/" target="_top">www.NetBSD.org</a> and other
1.1 dsieger 9875: sites. Additionally, check the
9876: <code class="filename">pkgsrc/doc/TODO</code> file and remove the entry
9877: for the package you updated or removed, in case it was mentioned
9878: there.</p>
9879: <p>When the <code class="varname">PKGREVISION</code> of a package is
9880: bumped, the change should appear in
9881: <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code> if it is security
9882: related or otherwise relevant. Mass bumps that result from a
9883: dependency being updated should not be mentioned. In all other
9884: cases it's the developer's decision.</p>
9885: <p>There is a make target that helps in creating proper
1.10 hubertf 9886: <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code> entries: <span class="command"><strong>make
1.1 dsieger 9887: changes-entry</strong></span>. It uses the optional <code class="varname">CTYPE</code>
9888: and <code class="varname">NETBSD_LOGIN_NAME</code> variables. The general
9889: usage is to first make sure that your <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code>
9890: file is up-to-date (to avoid having to resolve conflicts later-on)
1.10 hubertf 9891: and then to <span class="command"><strong>cd</strong></span> to the package directory. For
9892: package updates, <span class="command"><strong>make changes-entry</strong></span> is enough.
1.1 dsieger 9893: For new packages, or package moves or removals, set the
9894: <code class="varname">CTYPE</code> variable on the command line to "Added",
9895: "Moved", or "Removed". You can set <code class="varname">NETBSD_LOGIN_NAME</code>
1.10 hubertf 9896: in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> if your local login name is
1.22 jakllsch 9897: not the same as your NetBSD login name. The target also automatically
9898: removes possibly existing entries for the package in the
9899: <code class="filename">TODO</code> file. Don't forget to commit
1.66 asau 9900: the changes, e.g. by using <span class="command"><strong>make commit-changes-entry</strong></span>!
1.22 jakllsch 9901: If you are not using a checkout directly from cvs.NetBSD.org, but e.g.
9902: a local copy of the repository, you can set USE_NETBSD_REPO=yes. This
9903: makes the cvs commands use the main repository.
9904: </p>
1.1 dsieger 9905: </div>
1.41 asau 9906: <div class="sect1">
1.1 dsieger 9907: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9908: <a name="commit-messages"></a>23.4. Commit Messages</h2></div></div></div>
1.130 wiz 9909: <p>For several years, there have been mirrors of pkgsrc in
9910: fossil, git, and hg. Standard practise when using these tools is to
9911: make the first line of a commit message function as a summary that
9912: can be read without the rest, such as is commonly done with "git log
9913: --oneline". For this reason, we have the following guidelines for
9914: pkgsrc commit messages:</p>
9915: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9916: <li class="listitem"><p>Start the commit message with a line that explains the
1.131 wiz 9917: big picture in 65 characters or less. When a commit is for one
1.130 wiz 9918: package, include the name of the package. For updates, include the
9919: version to which it is updated.</p></li>
9920: <li class="listitem"><p>Leave the next line empty.</p></li>
9921: <li class="listitem"><p>Then come the details for the commit (changes in that
9922: package, reason for a change) and any relevant PRs. Wrap this
9923: section.</p></li>
9924: </ul></div>
9925: <p>Here is an example:
9926: </p>
9927: <pre class="programlisting">
9928: libxslt: update to 1.0.30
9929:
9930: Changes since 1.0.29:
9931: ...
9932: </pre>
9933: <p>
9934: </p>
9935: <p>Here is another example:
9936: </p>
9937: <pre class="programlisting">
9938: mk/bsd.pkg.mk: enable SSP by default on NetBSD
9939:
9940: (rationale)
9941: </pre>
9942: <p>
9943: </p>
9944: <p>Commit messages are final: no <span class="quote">“<span class="quote">cvs admin</span>”</span> is
9945: allowed on the pkgsrc repository to change commit messages.</p>
9946: </div>
9947: <div class="sect1">
9948: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9949: <a name="committing-importing"></a>23.5. Committing: Adding a package to CVS</h2></div></div></div>
1.1 dsieger 9950: <p>This section is only of interest for pkgsrc developers with write
1.33 wiz 9951: access to the pkgsrc repository.</p>
9952: <p>When the package is finished, <span class="quote">“<span class="quote">cvs add</span>”</span> the files.
9953: Start by adding the directory and then files in the directory. Don't
9954: forget to add the new package to the category's
9955: <code class="filename">Makefile</code>. Make sure you don't forget any files;
9956: you can check by running <span class="quote">“<span class="quote">cvs status</span>”</span>. An example:</p>
9957: <pre class="programlisting">
9958: <code class="prompt">$</code> cd .../pkgsrc/category
9959: <code class="prompt">$</code> cvs add pkgname
9960: <code class="prompt">$</code> cd pkgname
9961: <code class="prompt">$</code> cvs add DESCR Makefile PLIST distinfo buildlink3.mk patches
9962: <code class="prompt">$</code> cvs add patches/p*
9963: <code class="prompt">$</code> cvs status | less
1.34 wiz 9964: <code class="prompt">$</code> cvs commit
1.33 wiz 9965: <code class="prompt">$</code> cd ..
9966: <code class="prompt">$</code> vi Makefile # add SUBDIRS+=pkgname line
1.34 wiz 9967: <code class="prompt">$</code> cvs commit Makefile
1.66 asau 9968: <code class="prompt">$</code> cd pkgname
1.73 jnemeth 9969: <code class="prompt">$</code> make CTYPE=Added commit-changes-entry
1.33 wiz 9970: </pre>
1.1 dsieger 9971: <p>The commit message of the initial import should include part of the
9972: <code class="filename">DESCR</code> file, so people reading the mailing lists know
9973: what the package is/does.</p>
1.33 wiz 9974: <p>Also mention the new package in
9975: <code class="filename">pkgsrc/doc/CHANGES-20xx</code>.</p>
9976: <p>Previously, <span class="quote">“<span class="quote">cvs import</span>”</span> was suggested, but it was
9977: much easier to get wrong than <span class="quote">“<span class="quote">cvs add</span>”</span>.</p>
1.1 dsieger 9978: </div>
1.41 asau 9979: <div class="sect1">
1.1 dsieger 9980: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 9981: <a name="updating-package"></a>23.6. Updating a package to a newer version</h2></div></div></div>
1.1 dsieger 9982: <p>Please always put a concise, appropriate and relevant summary of the
9983: changes between old and new versions into the commit log when updating
9984: a package. There are various reasons for this:</p>
1.41 asau 9985: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9986: <li class="listitem"><p>A URL is volatile, and can change over time. It may go away completely
1.1 dsieger 9987: or its information may be overwritten by newer information.</p></li>
1.23 wiz 9988: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 9989: repository is very useful for people who use either cvs or anoncvs.</p></li>
1.23 wiz 9990: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 9991: repository is very useful for people who read the pkgsrc-changes mailing
9992: list, so that they can make tactical decisions about when to upgrade
9993: the package.</p></li>
9994: </ul></div>
9995: <p>Please also recognize that, just because a new version of a package
9996: has been released, it should not automatically be upgraded in the CVS
9997: repository. We prefer to be conservative in the packages that are
9998: included in pkgsrc - development or beta packages are not really the
9999: best thing for most places in which pkgsrc is used. Please use your
10000: judgement about what should go into pkgsrc, and bear in mind that
10001: stability is to be preferred above new and possibly untested features.</p>
10002: </div>
1.41 asau 10003: <div class="sect1">
1.1 dsieger 10004: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10005: <a name="renaming-package"></a>23.7. Renaming a package in pkgsrc</h2></div></div></div>
1.20 snj 10006: <p>Renaming packages is not recommended.</p>
1.175 gutterid 10007: <p>When renaming packages, be sure to fix any references to the old name
1.20 snj 10008: in other Makefiles, options, buildlink files, etc.</p>
1.167 leot 10009: <p>
1.175 gutterid 10010: Also, when renaming a package, please add
1.167 leot 10011: the package name and version pattern(s) of the previous package
10012: to <code class="varname">SUPERSEDES</code>.
1.20 snj 10013: This may be repeated for multiple renames.
10014: The new package would be an exact replacement.
1.167 leot 10015: Example:
1.20 snj 10016: </p>
1.167 leot 10017: <pre class="programlisting">
10018: SUPERSEDES+= p5-IO-Compress-Zlib<2.017
10019: SUPERSEDES+= optcomp-[0-9]*
10020: </pre>
1.23 wiz 10021: <p>Note that <span class="quote">“<span class="quote">successor</span>”</span> in the
1.20 snj 10022: CHANGES-<em class="replaceable"><code>YYYY</code></em> file doesn't necessarily
10023: mean that it <span class="emphasis"><em>supersedes</em></span>, as that successor may
10024: not be an exact replacement but is a suggestion for the replaced
10025: functionality.</p>
10026: </div>
1.41 asau 10027: <div class="sect1">
1.20 snj 10028: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.154 rillig 10029: <a name="moving-package"></a>23.8. Moving a package in pkgsrc</h2></div></div></div>
1.20 snj 10030: <p>It is preferred that packages are not renamed or moved, but if needed
10031: please follow these steps.
10032: </p>
1.23 wiz 10033: <div class="orderedlist"><ol class="orderedlist" type="1">
10034: <li class="listitem"><p>Make a copy of the directory somewhere else.</p></li>
10035: <li class="listitem">
1.1 dsieger 10036: <p>Remove all CVS dirs.</p>
10037: <p>Alternatively to the first two steps you can also do:</p>
10038: <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>
10039: <p>and use that for further work.</p>
10040: </li>
1.23 wiz 10041: <li class="listitem"><p>Fix <code class="varname">CATEGORIES</code> and any
10042: <code class="varname">DEPENDS</code> paths that just did <span class="quote">“<span class="quote">../package</span>”</span>
10043: instead of <span class="quote">“<span class="quote">../../category/package</span>”</span>.</p></li>
10044: <li class="listitem"><p>In the modified package's Makefile, consider setting
1.20 snj 10045: <code class="varname">PREV_PKGPATH</code> to the previous category/package
10046: pathname. The <code class="varname">PREV_PKGPATH</code> can be used by tools
10047: for doing an update using pkgsrc building; for example, it can
1.207 leot 10048: search the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/pkg_summary.5"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> database for <code class="varname">PREV_PKGPATH</code>
1.20 snj 10049: (if no <code class="varname">SUPERSEDES</code>) and then use the corresponding
10050: new <code class="varname">PKGPATH</code> for that moved package. Note that
10051: it may have multiple matches, so the tool should also check on the
10052: <code class="varname">PKGBASE</code> too. The <code class="varname">PREV_PKGPATH</code>
10053: probably has no value unless <code class="varname">SUPERSEDES</code> is not
10054: set, i.e. <code class="varname">PKGBASE</code> stays the same. </p></li>
1.23 wiz 10055: <li class="listitem"><p><span class="command"><strong>cvs import</strong></span> the modified package in the new
1.1 dsieger 10056: place.</p></li>
1.23 wiz 10057: <li class="listitem">
1.1 dsieger 10058: <p>Check if any package depends on it:
10059: </p>
10060: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
10061: <code class="prompt">%</code> <strong class="userinput"><code>grep /package */*/Makefile* */*/buildlink*</code></strong></pre>
10062: </li>
1.23 wiz 10063: <li class="listitem"><p>Fix paths in packages from step 5 to point to new location.</p></li>
10064: <li class="listitem"><p><span class="command"><strong>cvs rm (-f)</strong></span> the package at the old location.</p></li>
10065: <li class="listitem"><p>Remove from <code class="filename">oldcategory/Makefile</code>.</p></li>
10066: <li class="listitem"><p>Add to <code class="filename">newcategory/Makefile</code>.</p></li>
10067: <li class="listitem">
1.1 dsieger 10068: <p>Commit the changed and removed files:</p>
10069: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong></pre>
10070: <p>(and any packages from step 5, of course).</p>
10071: </li>
10072: </ol></div>
10073: </div>
10074: </div>
1.41 asau 10075: <div class="chapter">
1.1 dsieger 10076: <div class="titlepage"><div><div><h2 class="title">
1.154 rillig 10077: <a name="devfaq"></a>Chapter 24. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 10078: <p>This section contains the answers to questions that may
10079: arise when you are writing a package. If you don't find your
10080: question answered here, first have a look in the other chapters,
10081: and if you still don't have the answer, ask on the
10082: <code class="literal">pkgsrc-users</code> mailing list.</p>
1.41 asau 10083: <div class="qandaset">
1.174 leot 10084: <a name="devfaq.qandaset"></a><dl>
1.154 rillig 10085: <dt>24.1. <a href="#devfaq.makeflags">What is the difference between
1.1 dsieger 10086: MAKEFLAGS, .MAKEFLAGS and
10087: MAKE_FLAGS?</a>
10088: </dt>
1.154 rillig 10089: <dt>24.2. <a href="#devfaq.make">What is the difference between
1.1 dsieger 10090: MAKE, GMAKE and
10091: MAKE_PROGRAM?</a>
10092: </dt>
1.154 rillig 10093: <dt>24.3. <a href="#devfaq.cc">What is the difference between
1.1 dsieger 10094: CC, PKG_CC and
10095: PKGSRC_COMPILER?</a>
10096: </dt>
1.223 nia 10097: <dt>24.4. <a href="#devfaq.bl3prefix">Why does make show-var
1.1 dsieger 10098: VARNAME=BUILDLINK_PREFIX.foo
10099: say it's empty?</a>
10100: </dt>
1.223 nia 10101: <dt>24.5. <a href="#devfaq.master_sites">What does
1.1 dsieger 10102: ${MASTER_SITE_SOURCEFORGE:=package/} mean? I
10103: don't understand the := inside
10104: it.</a>
10105: </dt>
1.223 nia 10106: <dt>24.6. <a href="#devfaq.mailinglists">Which mailing lists are there for package
1.1 dsieger 10107: developers?</a>
10108: </dt>
1.223 nia 10109: <dt>24.7. <a href="#devfaq.documentation">Where is the pkgsrc
1.1 dsieger 10110: documentation?</a>
10111: </dt>
1.223 nia 10112: <dt>24.8. <a href="#devfaq.too-much-time">I have a little time to kill.
1.174 leot 10113: What shall I do?</a>
1.1 dsieger 10114: </dt>
10115: </dl>
1.41 asau 10116: <table border="0" style="width: 100%;">
10117: <colgroup>
1.1 dsieger 10118: <col align="left" width="1%">
1.23 wiz 10119: <col>
1.41 asau 10120: </colgroup>
1.1 dsieger 10121: <tbody>
1.41 asau 10122: <tr class="question">
1.1 dsieger 10123: <td align="left" valign="top">
1.174 leot 10124: <a name="devfaq.makeflags"></a><a name="devfaq.makeflags.q"></a><p><b>24.1.</b></p>
1.1 dsieger 10125: </td>
10126: <td align="left" valign="top"><p>What is the difference between
10127: <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
10128: <code class="varname">MAKE_FLAGS</code>?</p></td>
10129: </tr>
10130: <tr class="answer">
10131: <td align="left" valign="top"></td>
1.223 nia 10132: <td align="left" valign="top">
10133: <p><code class="varname">MAKEFLAGS</code> are the flags passed
10134: to the pkgsrc-internal invocations of <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.</p>
10135: <p><code class="varname">MAKE_FLAGS</code> are the flags that are
10136: passed to the <code class="varname">MAKE_PROGRAM</code> when building the
10137: package.</p>
10138: <p><code class="varname">.MAKEFLAGS</code> is an internal variable of
10139: <span class="command"><strong>bmake</strong></span> and should not be used by
10140: packages.</p>
10141: </td>
1.1 dsieger 10142: </tr>
1.41 asau 10143: <tr class="question">
1.1 dsieger 10144: <td align="left" valign="top">
1.174 leot 10145: <a name="devfaq.make"></a><a name="devfaq.make.q"></a><p><b>24.2.</b></p>
1.1 dsieger 10146: </td>
10147: <td align="left" valign="top"><p>What is the difference between
10148: <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
10149: <code class="varname">MAKE_PROGRAM</code>?</p></td>
10150: </tr>
10151: <tr class="answer">
10152: <td align="left" valign="top"></td>
1.223 nia 10153: <td align="left" valign="top">
10154: <p><code class="varname">MAKE</code> is the path to the
1.207 leot 10155: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
1.223 nia 10156: infrastructure.</p>
10157: <p><code class="varname">GMAKE</code> is the path to GNU Make, but you
10158: need to say <code class="varname">USE_TOOLS+=gmake</code> to use
10159: that.</p>
10160: <p><code class="varname">MAKE_PROGRAM</code> is the path to the Make
10161: program that is used for building the package.</p>
10162: </td>
1.1 dsieger 10163: </tr>
1.41 asau 10164: <tr class="question">
1.1 dsieger 10165: <td align="left" valign="top">
1.174 leot 10166: <a name="devfaq.cc"></a><a name="devfaq.cc.q"></a><p><b>24.3.</b></p>
1.1 dsieger 10167: </td>
10168: <td align="left" valign="top"><p>What is the difference between
10169: <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
10170: <code class="varname">PKGSRC_COMPILER</code>?</p></td>
10171: </tr>
10172: <tr class="answer">
10173: <td align="left" valign="top"></td>
10174: <td align="left" valign="top">
1.223 nia 10175: <p><code class="varname">CC</code> is the path to the real C
10176: compiler, which can be configured by the pkgsrc user.</p>
10177: <p><code class="varname">PKG_CC</code> is the path to the compiler
10178: wrapper.</p>
10179: <p><code class="varname">PKGSRC_COMPILER</code> is
10180: <span class="emphasis"><em>not</em></span> a path to a compiler, but the type of
10181: compiler that should be used. See
10182: <code class="filename">mk/compiler.mk</code> for more information about
10183: the latter variable.</p>
1.1 dsieger 10184: </td>
10185: </tr>
1.41 asau 10186: <tr class="question">
1.1 dsieger 10187: <td align="left" valign="top">
1.223 nia 10188: <a name="devfaq.bl3prefix"></a><a name="devfaq.bl3prefix.q"></a><p><b>24.4.</b></p>
1.1 dsieger 10189: </td>
1.10 hubertf 10190: <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
1.1 dsieger 10191: VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
10192: say it's empty?</p></td>
10193: </tr>
10194: <tr class="answer">
10195: <td align="left" valign="top"></td>
10196: <td align="left" valign="top"><p>For optimization reasons, some variables are only
1.23 wiz 10197: available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To
10198: <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append
1.10 hubertf 10199: <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
1.1 dsieger 10200: command.</p></td>
10201: </tr>
1.41 asau 10202: <tr class="question">
1.1 dsieger 10203: <td align="left" valign="top">
1.223 nia 10204: <a name="devfaq.master_sites"></a><a name="devfaq.master_sites.q"></a><p><b>24.5.</b></p>
1.1 dsieger 10205: </td>
10206: <td align="left" valign="top"><p>What does
1.108 rillig 10207: <code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
10208: don't understand the <code class="code">:=</code> inside
1.1 dsieger 10209: it.</p></td>
10210: </tr>
10211: <tr class="answer">
10212: <td align="left" valign="top"></td>
1.223 nia 10213: <td align="left" valign="top"><p>The <code class="code">:=</code> is not an
10214: assignment operator, even though it may look like one.
1.1 dsieger 10215: Instead, it is a degenerate form of
1.108 rillig 10216: <code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
1.207 leot 10217: which is documented in the <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/make.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which is
1.108 rillig 10218: commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the
1.1 dsieger 10219: case of <code class="varname">MASTER_SITE_*</code>,
10220: <em class="replaceable"><code>old_string</code></em> is the empty string and
10221: <em class="replaceable"><code>new_string</code></em> is
1.108 rillig 10222: <code class="code">package/</code>. That's where the
10223: <code class="code">:</code> and the <code class="code">=</code> fall
1.1 dsieger 10224: together.</p></td>
10225: </tr>
1.41 asau 10226: <tr class="question">
1.1 dsieger 10227: <td align="left" valign="top">
1.223 nia 10228: <a name="devfaq.mailinglists"></a><a name="devfaq.mailinglists.q"></a><p><b>24.6.</b></p>
1.1 dsieger 10229: </td>
10230: <td align="left" valign="top"><p>Which mailing lists are there for package
10231: developers?</p></td>
10232: </tr>
10233: <tr class="answer">
10234: <td align="left" valign="top"></td>
1.41 asau 10235: <td align="left" valign="top"><div class="variablelist"><dl class="variablelist">
1.174 leot 10236: <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 10237: <dd><p>This is a list for technical discussions related
10238: to pkgsrc development, e.g. soliciting feedback for changes to
10239: pkgsrc infrastructure, proposed new features, questions related
10240: to porting pkgsrc to a new platform, advice for maintaining a
10241: package, patches that affect many packages, help requests moved
10242: from pkgsrc-users when an infrastructure bug is found,
10243: etc.</p></dd>
1.174 leot 10244: <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 10245: <dd><p>All bug reports in category "pkg" sent with
1.207 leot 10246: <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/send-pr.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here
1.1 dsieger 10247: directly; use one of the other mailing
10248: lists.</p></dd>
10249: </dl></div></td>
10250: </tr>
1.41 asau 10251: <tr class="question">
1.1 dsieger 10252: <td align="left" valign="top">
1.223 nia 10253: <a name="devfaq.documentation"></a><a name="devfaq.documentation.q"></a><p><b>24.7.</b></p>
1.1 dsieger 10254: </td>
10255: <td align="left" valign="top"><p>Where is the pkgsrc
10256: documentation?</p></td>
10257: </tr>
10258: <tr class="answer">
10259: <td align="left" valign="top"></td>
10260: <td align="left" valign="top">
10261: <p>There are many places where you can find
10262: documentation about pkgsrc:</p>
1.41 asau 10263: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10264: <li class="listitem"><p>The pkgsrc guide (this document) is a collection
1.1 dsieger 10265: of chapters that explain large parts of pkgsrc, but some
10266: chapters tend to be outdated. Which ones they are is hard to
10267: say.</p></li>
1.174 leot 10268: <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 10269: about certain features, announcements of new parts of the pkgsrc
10270: infrastructure and sometimes even announcements that a certain
10271: feature has been marked as obsolete. The benefit here is that
10272: each message has a date appended to it.</p></li>
1.23 wiz 10273: <li class="listitem"><p>Many of the files in the
1.1 dsieger 10274: <code class="filename">mk/</code> directory start with a comment that
10275: describes the purpose of the file and how it can be used by the
10276: pkgsrc user and package authors. An easy way to find this
1.10 hubertf 10277: documentation is to run <span class="command"><strong>bmake
1.1 dsieger 10278: help</strong></span>.</p></li>
1.23 wiz 10279: <li class="listitem"><p>The CVS log messages are a rich source of
1.1 dsieger 10280: information, but they tend to be highly abbreviated, especially
10281: for actions that occur often. Some contain a detailed
10282: description of what has changed, but they are geared towards the
10283: other pkgsrc developers, not towards an average pkgsrc user.
10284: They also only document <span class="emphasis"><em>changes</em></span>, so if you
10285: don't know what has been before, these messages may not be worth
10286: too much to you.</p></li>
1.23 wiz 10287: <li class="listitem"><p>Some parts of pkgsrc are only <span class="quote">“<span class="quote">implicitly
10288: documented</span>”</span>, that is the documentation exists only in the
1.1 dsieger 10289: mind of the developer who wrote the code. To get this
1.10 hubertf 10290: information, use the <span class="command"><strong>cvs annotate</strong></span> command
1.1 dsieger 10291: to see who has written it and ask on the
10292: <code class="literal">tech-pkg</code> mailing list, so that others can
10293: find your questions later (see above). To be sure that the
10294: developer in charge reads the mail, you may CC him or
10295: her.</p></li>
10296: </ul></div>
1.184 rillig 10297: </td>
10298: </tr>
10299: <tr class="question">
10300: <td align="left" valign="top">
1.223 nia 10301: <a name="devfaq.too-much-time"></a><a name="devfaq.too-much-time.q"></a><p><b>24.8.</b></p>
1.184 rillig 10302: </td>
1.223 nia 10303: <td align="left" valign="top"><p>I have a little time to kill.
1.184 rillig 10304: What shall I do?</p></td>
10305: </tr>
10306: <tr class="answer">
10307: <td align="left" valign="top"></td>
10308: <td align="left" valign="top">
10309: <p>This is not really an FAQ yet, but here's the answer
10310: anyway.</p>
1.41 asau 10311: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.184 rillig 10312: <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
1.207 leot 10313: <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 10314: will tell you about newer versions of installed packages that are
10315: available, but not yet updated in pkgsrc.</p></li>
10316: <li class="listitem"><p>Browse <code class="filename">pkgsrc/doc/TODO</code>
10317: — it contains a list of suggested new packages and a list of
10318: cleanups and enhancements for pkgsrc that would be nice to
10319: have.</p></li>
10320: <li class="listitem"><p>Review packages for which review was requested on
10321: the <a class="ulink" href="https://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a>
10322: mailing list.</p></li>
1.1 dsieger 10323: </ul></div>
1.184 rillig 10324: </td>
1.1 dsieger 10325: </tr>
10326: </tbody>
1.184 rillig 10327: </table>
1.1 dsieger 10328: </div>
10329: </div>
10330: </div>
1.41 asau 10331: <div class="part">
1.1 dsieger 10332: <div class="titlepage"><div><div><h1 class="title">
10333: <a name="infrastructure"></a>Part III. The pkgsrc infrastructure internals</h1></div></div></div>
1.41 asau 10334: <div class="partintro">
1.1 dsieger 10335: <div></div>
10336: <p>This part of the guide deals with everything
10337: from the infrastructure that is behind the interfaces described
10338: in the developer's guide. A casual package maintainer should not
10339: need anything from this part.</p>
10340: <div class="toc">
10341: <p><b>Table of Contents</b></p>
1.100 leot 10342: <dl class="toc">
1.184 rillig 10343: <dt><span class="chapter"><a href="#infr.design">25. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 10344: <dd><dl>
1.184 rillig 10345: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10346: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10347: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.1 dsieger 10348: <dd><dl>
1.184 rillig 10349: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10350: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.1 dsieger 10351: </dl></dd>
1.184 rillig 10352: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10353: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10354: <dd><dl>
1.184 rillig 10355: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10356: <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 10357: </dl></dd>
1.184 rillig 10358: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10359: <dd><dl>
1.184 rillig 10360: <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>
10361: <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 10362: </dl></dd>
10363: </dl></dd>
1.184 rillig 10364: <dt><span class="chapter"><a href="#regression">26. Regression tests</a></span></dt>
1.1 dsieger 10365: <dd><dl>
1.184 rillig 10366: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10367: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.1 dsieger 10368: <dd><dl>
1.184 rillig 10369: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10370: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.1 dsieger 10371: </dl></dd>
10372: </dl></dd>
1.184 rillig 10373: <dt><span class="chapter"><a href="#porting">27. Porting pkgsrc</a></span></dt>
10374: <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 10375: </dl>
10376: </div>
10377: </div>
1.41 asau 10378: <div class="chapter">
1.1 dsieger 10379: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10380: <a name="infr.design"></a>Chapter 25. Design of the pkgsrc infrastructure</h2></div></div></div>
1.1 dsieger 10381: <div class="toc">
10382: <p><b>Table of Contents</b></p>
1.100 leot 10383: <dl class="toc">
1.184 rillig 10384: <dt><span class="sect1"><a href="#infr.vardef">25.1. The meaning of variable definitions</a></span></dt>
10385: <dt><span class="sect1"><a href="#infr.vardef.problems">25.2. Avoiding problems before they arise</a></span></dt>
10386: <dt><span class="sect1"><a href="#infr.var">25.3. Variable evaluation</a></span></dt>
1.1 dsieger 10387: <dd><dl>
1.184 rillig 10388: <dt><span class="sect2"><a href="#infr.var.load">25.3.1. At load time</a></span></dt>
10389: <dt><span class="sect2"><a href="#infr.var.run">25.3.2. At runtime</a></span></dt>
1.1 dsieger 10390: </dl></dd>
1.184 rillig 10391: <dt><span class="sect1"><a href="#infr.varspec">25.4. How can variables be specified?</a></span></dt>
10392: <dt><span class="sect1"><a href="#infr.design.intf">25.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10393: <dd><dl>
1.184 rillig 10394: <dt><span class="sect2"><a href="#infr.design.intf.proc">25.5.1. Procedures with parameters</a></span></dt>
10395: <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 10396: </dl></dd>
1.184 rillig 10397: <dt><span class="sect1"><a href="#infr.order">25.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10398: <dd><dl>
1.184 rillig 10399: <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>
10400: <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 10401: </dl></dd>
10402: </dl>
10403: </div>
10404: <p>The pkgsrc infrastructure consists of many small Makefile
10405: fragments. Each such fragment needs a properly specified
10406: interface. This chapter explains how such an interface looks
10407: like.</p>
1.41 asau 10408: <div class="sect1">
1.1 dsieger 10409: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10410: <a name="infr.vardef"></a>25.1. The meaning of variable definitions</h2></div></div></div>
1.1 dsieger 10411: <p>Whenever a variable is defined in the pkgsrc
10412: infrastructure, the location and the way of definition provide
10413: much information about the intended use of that variable.
10414: Additionally, more documentation may be found in a header
10415: comment or in this pkgsrc guide.</p>
10416: <p>A special file is
10417: <code class="filename">mk/defaults/mk.conf</code>, which lists all
10418: variables that are intended to be user-defined. They are either
10419: defined using the <code class="literal">?=</code> operator or they are
10420: left undefined because defining them to anything would
1.23 wiz 10421: effectively mean <span class="quote">“<span class="quote">yes</span>”</span>. All these variables may be
1.1 dsieger 10422: overridden by the pkgsrc user in the <code class="varname">MAKECONF</code>
10423: file.</p>
10424: <p>Outside this file, the following conventions apply:
10425: Variables that are defined using the <code class="literal">?=</code>
10426: operator may be overridden by a package.</p>
10427: <p>Variables that are defined using the <code class="literal">=</code>
10428: operator may be used read-only at run-time.</p>
10429: <p>Variables whose name starts with an underscore must not be
10430: accessed outside the pkgsrc infrastructure at all. They may
10431: change without further notice.</p>
1.41 asau 10432: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 10433: <h3 class="title">Note</h3>
10434: <p>These conventions are currently not applied
10435: consistently to the complete pkgsrc
10436: infrastructure.</p>
10437: </div>
10438: </div>
1.41 asau 10439: <div class="sect1">
1.1 dsieger 10440: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10441: <a name="infr.vardef.problems"></a>25.2. Avoiding problems before they arise</h2></div></div></div>
1.1 dsieger 10442: <p>All variables that contain lists of things should default
10443: to being empty. Two examples that do not follow this rule are
10444: <code class="varname">USE_LANGUAGES</code> and
10445: <code class="varname">DISTFILES</code>. These variables cannot simply be
10446: modified using the <code class="literal">+=</code> operator in package
10447: <code class="filename">Makefile</code>s (or other files included by
10448: them), since there is no guarantee whether the variable is
10449: already set or not, and what its value is. In the case of
1.23 wiz 10450: <code class="varname">DISTFILES</code>, the packages <span class="quote">“<span class="quote">know</span>”</span>
1.1 dsieger 10451: the default value and just define it as in the following
10452: example.</p>
10453: <pre class="programlisting">
10454: DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz
10455: </pre>
10456: <p>Because of the selection of this default value, the same
10457: value appears in many package Makefiles. Similarly for
10458: <code class="varname">USE_LANGUAGES</code>, but in this case the default
1.23 wiz 10459: value (<span class="quote">“<span class="quote"><code class="literal">c</code></span>”</span>) is so short that it
1.1 dsieger 10460: doesn't stand out. Nevertheless it is mentioned in many
10461: files.</p>
10462: </div>
1.41 asau 10463: <div class="sect1">
1.1 dsieger 10464: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10465: <a name="infr.var"></a>25.3. Variable evaluation</h2></div></div></div>
1.41 asau 10466: <div class="sect2">
1.1 dsieger 10467: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10468: <a name="infr.var.load"></a>25.3.1. At load time</h3></div></div></div>
1.1 dsieger 10469: <p>Variable evaluation takes place either at load time or at
10470: runtime, depending on the context in which they occur. The
10471: contexts where variables are evaluated at load time are:</p>
1.41 asau 10472: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10473: <li class="listitem"><p>The right hand side of the <code class="literal">:=</code>
1.1 dsieger 10474: and <code class="literal">!=</code> operators,</p></li>
1.23 wiz 10475: <li class="listitem"><p>Make directives like <code class="literal">.if</code> or
1.1 dsieger 10476: <code class="literal">.for</code>,</p></li>
1.23 wiz 10477: <li class="listitem"><p>Dependency lines.</p></li>
1.1 dsieger 10478: </ul></div>
10479: <p>A special exception are references to the iteration
10480: variables of <code class="literal">.for</code> loops, which are expanded
10481: inline, no matter in which context they appear.</p>
10482: <p>As the values of variables may change during load time,
10483: care must be taken not to evaluate them by accident. Typical
10484: examples for variables that should not be evaluated at load time
10485: are <code class="varname">DEPENDS</code> and
10486: <code class="varname">CONFIGURE_ARGS</code>. To make the effect more
10487: clear, here is an example:</p>
10488: <pre class="programlisting">
10489: CONFIGURE_ARGS= # none
10490: CFLAGS= -O
10491: CONFIGURE_ARGS+= CFLAGS=${CFLAGS:Q}
10492:
10493: CONFIGURE_ARGS:= ${CONFIGURE_ARGS}
10494:
10495: CFLAGS+= -Wall
1.111 sevan 10496: </pre>
1.1 dsieger 10497: <p>This code shows how the use of the <code class="literal">:=</code>
10498: operator can quickly lead to unexpected results. The first
10499: paragraph is fairly common code. The second paragraph evaluates
10500: the <code class="varname">CONFIGURE_ARGS</code> variable, which results in
10501: <code class="literal">CFLAGS=-O</code>. In the third paragraph, the
10502: <code class="literal">-Wall</code> is appended to the
10503: <code class="varname">CFLAGS</code>, but this addition will not appear in
10504: <code class="varname">CONFIGURE_ARGS</code>. In actual code, the three
10505: paragraphs from above typically occur in completely unrelated
10506: files.</p>
10507: </div>
1.41 asau 10508: <div class="sect2">
1.1 dsieger 10509: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10510: <a name="infr.var.run"></a>25.3.2. At runtime</h3></div></div></div>
1.1 dsieger 10511: <p>After all the files have been loaded, the values of the
10512: variables cannot be changed anymore. Variables that are used in
10513: the shell commands are expanded at this point.</p>
10514: </div>
10515: </div>
1.41 asau 10516: <div class="sect1">
1.1 dsieger 10517: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10518: <a name="infr.varspec"></a>25.4. How can variables be specified?</h2></div></div></div>
1.1 dsieger 10519: <p>There are many ways in which the definition and use of a
1.108 rillig 10520: variable can be restricted in order to detect bugs and violations
10521: of the (mostly unwritten) policies. A package can be checked with
10522: <code class="literal">pkglint -Wall</code> to see whether it meets these
10523: rules.</p>
1.1 dsieger 10524: </div>
1.41 asau 10525: <div class="sect1">
1.1 dsieger 10526: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10527: <a name="infr.design.intf"></a>25.5. Designing interfaces for Makefile fragments</h2></div></div></div>
1.1 dsieger 10528: <p>Most of the <code class="filename">.mk</code> files fall into one
10529: of the following classes. Cases where a file falls into more
10530: than one class should be avoided as it often leads to subtle
10531: bugs.</p>
1.41 asau 10532: <div class="sect2">
1.1 dsieger 10533: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10534: <a name="infr.design.intf.proc"></a>25.5.1. Procedures with parameters</h3></div></div></div>
1.1 dsieger 10535: <p>In a traditional imperative programming language some of
10536: the <code class="filename">.mk</code> files could be described as
1.14 jmcneill 10537: procedures. They take some input parameters and—after
10538: inclusion—provide a result in output parameters. Since all
1.1 dsieger 10539: variables in <code class="filename">Makefile</code>s have global scope
10540: care must be taken not to use parameter names that have already
10541: another meaning. For example, <code class="varname">PKGNAME</code> is a
10542: bad choice for a parameter name.</p>
10543: <p>Procedures are completely evaluated at preprocessing time.
10544: That is, when calling a procedure all input parameters must be
10545: completely resolvable. For example,
10546: <code class="varname">CONFIGURE_ARGS</code> should never be an input
10547: parameter since it is very likely that further text will be
10548: added after calling the procedure, which would effectively apply
10549: the procedure to only a part of the variable. Also, references
1.108 rillig 10550: to other variables will be modified after calling the
1.1 dsieger 10551: procedure.</p>
10552: <p>A procedure can declare its output parameters either as
10553: suitable for use in preprocessing directives or as only
10554: available at runtime. The latter alternative is for variables
10555: that contain references to other runtime variables.</p>
10556: <p>Procedures shall be written such that it is possible to
10557: call the procedure more than once. That is, the file must not
10558: contain multiple-inclusion guards.</p>
10559: <p>Examples for procedures are
10560: <code class="filename">mk/bsd.options.mk</code> and
10561: <code class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express
10562: that the parameters are evaluated at load time, they should be
10563: assigned using the <code class="literal">:=</code> operator, which should
10564: be used only for this purpose.</p>
10565: </div>
1.41 asau 10566: <div class="sect2">
1.1 dsieger 10567: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10568: <a name="infr.design.intf.action"></a>25.5.2. Actions taken on behalf of parameters</h3></div></div></div>
1.1 dsieger 10569: <p>Action files take some input parameters and may define
10570: runtime variables. They shall not define loadtime variables.
10571: There are action files that are included implicitly by the
10572: pkgsrc infrastructure, while other must be included
10573: explicitly.</p>
10574: <p>An example for action files is
10575: <code class="filename">mk/subst.mk</code>.</p>
10576: </div>
10577: </div>
1.41 asau 10578: <div class="sect1">
1.1 dsieger 10579: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10580: <a name="infr.order"></a>25.6. The order in which files are loaded</h2></div></div></div>
1.1 dsieger 10581: <p>Package <code class="filename">Makefile</code>s usually consist of
10582: a set of variable definitions, and include the file
10583: <code class="filename">../../mk/bsd.pkg.mk</code> in the very last line.
10584: Before that, they may also include various other
10585: <code class="filename">*.mk</code> files if they need to query the
10586: availability of certain features like the type of compiler or
10587: the X11 implementation. Due to the heavy use of preprocessor
10588: directives like <code class="literal">.if</code> and
10589: <code class="literal">.for</code>, the order in which the files are loaded
10590: matters.</p>
10591: <p>This section describes at which point the various files
10592: are loaded and gives reasons for that order.</p>
1.41 asau 10593: <div class="sect2">
1.1 dsieger 10594: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10595: <a name="infr.order.prefs"></a>25.6.1. The order in <code class="filename">bsd.prefs.mk</code>
1.1 dsieger 10596: </h3></div></div></div>
10597: <p>The very first action in <code class="filename">bsd.prefs.mk</code>
10598: is to define some essential variables like
10599: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code> and
10600: <code class="varname">MACHINE_ARCH</code>.</p>
10601: <p>Then, the user settings are loaded from the file specified
1.10 hubertf 10602: 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 10603: After that, those variables
1.1 dsieger 10604: that have not been overridden by the user are loaded from
10605: <code class="filename">mk/defaults/mk.conf</code>.</p>
10606: <p>After the user settings, the system settings and platform
10607: settings are loaded, which may override the user
10608: settings.</p>
10609: <p>Then, the tool definitions are loaded. The tool wrappers
10610: are not yet in effect. This only happens when building a
10611: package, so the proper variables must be used instead of the
10612: direct tool names.</p>
10613: <p>As the last steps, some essential variables from the
10614: wrapper and the package system flavor are loaded, as well as the
10615: variables that have been cached in earlier phases of a package
10616: build.</p>
10617: </div>
1.41 asau 10618: <div class="sect2">
1.1 dsieger 10619: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10620: <a name="infr.order.pkg"></a>25.6.2. The order in <code class="filename">bsd.pkg.mk</code>
1.1 dsieger 10621: </h3></div></div></div>
10622: <p>First, <code class="filename">bsd.prefs.mk</code> is loaded.</p>
10623: <p>Then, the various <code class="filename">*-vars.mk</code> files are
10624: loaded, which fill default values for those variables that have
10625: not been defined by the package. These variables may later
10626: be used even in unrelated files.</p>
10627: <p>Then, the file <code class="filename">bsd.pkg.error.mk</code>
10628: provides the target <code class="literal">error-check</code> that is added
10629: as a special dependency to all other targets that use
10630: <code class="varname">DELAYED_ERROR_MSG</code> or
10631: <code class="varname">DELAYED_WARNING_MSG</code>.</p>
10632: <p>Then, the package-specific hacks from
10633: <code class="filename">hacks.mk</code> are included.</p>
10634: <p>Then, various other files follow. Most of them don't have
10635: any dependencies on what they need to have included before or
10636: after them, though some do.</p>
10637: <p>The code to check <code class="varname">PKG_FAIL_REASON</code> and
10638: <code class="varname">PKG_SKIP_REASON</code> is then executed, which
10639: restricts the use of these variables to all the files that have
10640: been included before. Appearances in later files will be
10641: silently ignored.</p>
10642: <p>Then, the files for the main targets are included, in the
10643: order of later execution, though the actual order should not
10644: matter.</p>
10645: <p>At last, some more files are included that don't set any
10646: interesting variables but rather just define make targets to be
10647: executed.</p>
10648: </div>
10649: </div>
10650: </div>
1.41 asau 10651: <div class="chapter">
1.1 dsieger 10652: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10653: <a name="regression"></a>Chapter 26. Regression tests</h2></div></div></div>
1.1 dsieger 10654: <div class="toc">
10655: <p><b>Table of Contents</b></p>
1.100 leot 10656: <dl class="toc">
1.184 rillig 10657: <dt><span class="sect1"><a href="#regression.run">26.1. Running the regression tests</a></span></dt>
10658: <dt><span class="sect1"><a href="#regression.new">26.2. Adding a new regression test</a></span></dt>
1.1 dsieger 10659: <dd><dl>
1.184 rillig 10660: <dt><span class="sect2"><a href="#regression.fun.override">26.2.1. Overridable functions</a></span></dt>
10661: <dt><span class="sect2"><a href="#regression.fun.helper">26.2.2. Helper functions</a></span></dt>
1.1 dsieger 10662: </dl></dd>
10663: </dl>
10664: </div>
10665: <p>The pkgsrc infrastructure consists of a large codebase,
10666: and there are many corners where every little bit of a file is
10667: well thought out, making pkgsrc likely to fail as soon as
10668: anything is changed near those parts. To prevent most changes
10669: from breaking anything, a suite of regression tests should go
10670: along with every important part of the pkgsrc infrastructure.
10671: This chapter describes how regression tests work in pkgsrc and
10672: how you can add new tests.</p>
1.41 asau 10673: <div class="sect1">
1.1 dsieger 10674: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10675: <a name="regression.run"></a>26.1. Running the regression tests</h2></div></div></div>
1.207 leot 10676: <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 10677: provides the <span class="command"><strong>pkg_regress</strong></span> command. Then you
1.1 dsieger 10678: can simply run that command, which will run all tests in the
1.168 rillig 10679: <code class="filename">regress/</code> directory.</p>
1.1 dsieger 10680: </div>
1.41 asau 10681: <div class="sect1">
1.1 dsieger 10682: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10683: <a name="regression.new"></a>26.2. Adding a new regression test</h2></div></div></div>
1.168 rillig 10684: <p>Every directory in the <code class="filename">regress/</code>
10685: directory that contains a file called <code class="filename">spec</code>
1.1 dsieger 10686: is considered a regression test. This file is a shell program
1.10 hubertf 10687: that is included by the <span class="command"><strong>pkg_regress</strong></span> command.
1.1 dsieger 10688: The following functions can be overridden to suit your
10689: needs.</p>
1.41 asau 10690: <div class="sect2">
1.1 dsieger 10691: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10692: <a name="regression.fun.override"></a>26.2.1. Overridable functions</h3></div></div></div>
1.108 rillig 10693: <p>These functions do not take any parameters. Although they
10694: are called in <span class="quote">“<span class="quote">set -e</span>”</span> mode, they don't stop at the
1.174 leot 10695: first failing command. See <a class="ulink" href="https://stackoverflow.com/q/4072984" target="_top">this Stack Overflow
1.108 rillig 10696: question</a> for details.</p>
1.41 asau 10697: <div class="variablelist"><dl class="variablelist">
1.108 rillig 10698: <dt><span class="term"><code class="varname">do_setup</code></span></dt>
1.1 dsieger 10699: <dd><p>This function prepares the environment for the
10700: test. By default it does nothing.</p></dd>
1.108 rillig 10701: <dt><span class="term"><code class="varname">do_test</code></span></dt>
10702: <dd>
10703: <p>This function runs the actual test. By default,
1.1 dsieger 10704: it calls <code class="varname">TEST_MAKE</code> with the arguments
10705: <code class="varname">MAKEARGS_TEST</code> and writes its output including
10706: error messages into the file
1.108 rillig 10707: <code class="varname">TEST_OUTFILE</code>.</p>
10708: <p>When defining this function, make sure that all output that
10709: needs to be checked is written to the correct output file.
10710: Example:</p>
10711: <pre class="programlisting">
10712: do_test() {
1.112 rillig 10713: echo "Example output"
1.108 rillig 10714: } 1>$TEST_OUTFILE 2>&1
10715: </pre>
10716: </dd>
10717: <dt><span class="term"><code class="varname">check_result</code></span></dt>
10718: <dd>
10719: <p>This function is run after the test and is
1.1 dsieger 10720: typically used to compare the actual output from the one that is
10721: expected. It can make use of the various helper functions from
1.108 rillig 10722: the next section. Example:</p>
10723: <pre class="programlisting">
10724: check_result() {
1.112 rillig 10725: exit_status 0
10726: output_require "Example"
10727: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
10728: output_prohibit "no such file or directory"
1.168 rillig 10729: regress_fail "expected $expected but got $actual for input $input"
1.108 rillig 10730: }
10731: </pre>
10732: </dd>
10733: <dt><span class="term"><code class="varname">do_cleanup</code></span></dt>
1.1 dsieger 10734: <dd><p>This function cleans everything up after the
10735: test has been run. By default it does nothing.</p></dd>
10736: </dl></div>
10737: </div>
1.41 asau 10738: <div class="sect2">
1.1 dsieger 10739: <div class="titlepage"><div><div><h3 class="title">
1.184 rillig 10740: <a name="regression.fun.helper"></a>26.2.2. Helper functions</h3></div></div></div>
1.41 asau 10741: <div class="variablelist"><dl class="variablelist">
1.168 rillig 10742: <dt><span class="term"><code class="varname">regress_fail <em class="replaceable"><code>message...</code></em></code></span></dt>
10743: <dd><p>This function makes the test fail with the given error message.</p></dd>
1.108 rillig 10744: <dt><span class="term"><code class="varname">exit_status expected</code></span></dt>
1.1 dsieger 10745: <dd><p>This function compares the exitcode of the
1.108 rillig 10746: <span class="command"><strong>do_test</strong></span> function with its first parameter.
1.1 dsieger 10747: If they differ, the test will fail.</p></dd>
1.108 rillig 10748: <dt><span class="term"><code class="varname">output_require regex...</code></span></dt>
10749: <dd>
10750: <p>This function checks for each of its parameters
10751: if the output from <span class="command"><strong>do_test</strong></span> matches the
1.1 dsieger 10752: extended regular expression. If it does not, the test will
1.108 rillig 10753: fail. Example:</p>
10754: <pre class="programlisting">
10755: output_require "looks fine"
10756: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
10757: </pre>
10758: </dd>
1.177 leot 10759: <dt><span class="term"><code class="varname">output_prohibit regex...</code></span></dt>
1.1 dsieger 10760: <dd><p>This function checks for each of its parameters
1.10 hubertf 10761: if the output from <span class="command"><strong>do_test()</strong></span> does
1.1 dsieger 10762: <span class="emphasis"><em>not</em></span> match the extended regular expression.
10763: If any of the regular expressions matches, the test will
10764: fail.</p></dd>
10765: </dl></div>
10766: </div>
10767: </div>
10768: </div>
1.41 asau 10769: <div class="chapter">
1.1 dsieger 10770: <div class="titlepage"><div><div><h2 class="title">
1.184 rillig 10771: <a name="porting"></a>Chapter 27. Porting pkgsrc</h2></div></div></div>
1.1 dsieger 10772: <div class="toc">
10773: <p><b>Table of Contents</b></p>
1.184 rillig 10774: <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 10775: </div>
10776: <p>The pkgsrc system has already been ported to many
10777: operating systems, hardware architectures and compilers. This
10778: chapter explains the necessary steps to make pkgsrc even more
10779: portable.</p>
1.41 asau 10780: <div class="sect1">
1.1 dsieger 10781: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.184 rillig 10782: <a name="porting.opsys"></a>27.1. Porting pkgsrc to a new operating system</h2></div></div></div>
1.1 dsieger 10783: <p>To port pkgsrc to a new operating system (called
10784: <code class="literal">MyOS</code> in this example), you need to touch the
10785: following files:</p>
1.41 asau 10786: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 10787: <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>
10788: <dd><p>This file contains some basic definitions, for
10789: example the name of the C
10790: compiler.</p></dd>
10791: <dt><span class="term"><code class="filename">mk/bsd.prefs.mk</code></span></dt>
10792: <dd><p>Insert code that defines the variables
10793: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code>,
1.212 wiz 10794: <code class="varname">OPSYS_VERSION</code>, <code class="varname">LOWER_VENDOR</code>,
1.1 dsieger 10795: <code class="varname">MACHINE_ARCH</code>, <code class="varname">OBJECT_FMT</code>,
10796: <code class="varname">APPEND_ELF</code>, and the other variables that
10797: appear in this file.</p></dd>
10798: <dt><span class="term"><code class="filename">mk/platform/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10799: <dd><p>This file contains the platform-specific
10800: definitions that are used by pkgsrc. Start by copying one of the
10801: other files and edit it to your
10802: needs.</p></dd>
10803: <dt><span class="term"><code class="filename">mk/tools/tools.<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10804: <dd><p>This file defines the paths to all the tools
10805: that are needed by one or the other package in pkgsrc, as well
10806: as by pkgsrc itself. Find out where these tools are on your
10807: platform and add them.</p></dd>
10808: </dl></div>
10809: <p>Now, you should be able to build some basic packages, like
1.207 leot 10810: <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 10811: </div>
10812: </div>
10813: </div>
1.41 asau 10814: <div class="appendix">
10815: <div class="titlepage"><div><div><h1 class="title">
10816: <a name="examples"></a>Appendix A. A simple example package: bison</h1></div></div></div>
1.1 dsieger 10817: <div class="toc">
10818: <p><b>Table of Contents</b></p>
1.100 leot 10819: <dl class="toc">
1.1 dsieger 10820: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
10821: <dd><dl>
10822: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
10823: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
10824: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.172 rillig 10825: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with pkglint</a></span></dt>
1.1 dsieger 10826: </dl></dd>
10827: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
10828: </dl>
10829: </div>
10830: <p>We checked to find a piece of software that wasn't in the packages
10831: collection, and picked GNU bison. Quite why someone would want to have
1.10 hubertf 10832: <span class="command"><strong>bison</strong></span> when Berkeley <span class="command"><strong>yacc</strong></span> is already
1.1 dsieger 10833: present in the tree is beyond us, but it's useful for the purposes of
10834: this exercise.</p>
1.41 asau 10835: <div class="sect1">
1.1 dsieger 10836: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10837: <a name="example-files"></a>A.1. files</h2></div></div></div>
1.41 asau 10838: <div class="sect2">
1.1 dsieger 10839: <div class="titlepage"><div><div><h3 class="title">
10840: <a name="example-Makefile"></a>A.1.1. Makefile</h3></div></div></div>
10841: <pre class="programlisting">
10842: # $NetBSD$
10843: #
10844:
10845: DISTNAME= bison-1.25
10846: CATEGORIES= devel
1.171 rillig 10847: MASTER_SITES= ${MASTER_SITE_GNU:=bison/}
1.1 dsieger 10848:
1.29 dholland 10849: MAINTAINER= pkgsrc-users@NetBSD.org
1.174 leot 10850: HOMEPAGE= https://www.gnu.org/software/bison/bison.html
1.1 dsieger 10851: COMMENT= GNU yacc clone
10852:
10853: GNU_CONFIGURE= yes
1.46 wiz 10854: INFO_FILES= yes
1.1 dsieger 10855:
10856: .include "../../mk/bsd.pkg.mk"
10857: </pre>
10858: </div>
1.41 asau 10859: <div class="sect2">
1.1 dsieger 10860: <div class="titlepage"><div><div><h3 class="title">
10861: <a name="example-descr"></a>A.1.2. DESCR</h3></div></div></div>
10862: <pre class="programlisting">
10863: GNU version of yacc. Can make re-entrant parsers, and numerous other
1.207 leot 10864: improvements. Why you would want this when Berkeley <a class="citerefentry" href="https://man.NetBSD.org/NetBSD-9.2/i386/yacc.1"><span class="citerefentry"><span class="refentrytitle">yacc</span>(1)</span></a> is part
1.1 dsieger 10865: of the NetBSD source tree is beyond me.
10866: </pre>
10867: </div>
1.41 asau 10868: <div class="sect2">
1.1 dsieger 10869: <div class="titlepage"><div><div><h3 class="title">
10870: <a name="example-plist"></a>A.1.3. PLIST</h3></div></div></div>
10871: <pre class="programlisting">
10872: @comment $NetBSD$
10873: bin/bison
10874: man/man1/bison.1.gz
10875: share/bison.simple
10876: share/bison.hairy
10877: </pre>
10878: </div>
1.41 asau 10879: <div class="sect2">
1.1 dsieger 10880: <div class="titlepage"><div><div><h3 class="title">
1.172 rillig 10881: <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with pkglint</h3></div></div></div>
1.1 dsieger 10882: <p>The NetBSD package system comes with
1.207 leot 10883: <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 10884: which helps to check the contents of these
10885: files. After installation it is quite easy to use, just change to the
1.171 rillig 10886: directory of the package you wish to examine and run
1.10 hubertf 10887: <span class="command"><strong>pkglint</strong></span>:</p>
1.1 dsieger 10888: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>pkglint</code></strong>
1.171 rillig 10889: ERROR: Makefile: Each package must define its LICENSE.
10890: WARN: Makefile:9: HOMEPAGE should migrate from http to https.
10891: NOTE: PLIST:3: The .gz extension is unnecessary for manual pages.
10892: WARN: PLIST:5: "share/bison.hairy" should be sorted before "share/bison.simple".
10893: 1 error, 2 warnings and 1 note found.
10894: (Run "pkglint -e" to show explanations.)
10895: (Run "pkglint -fs" to show what can be fixed automatically.)
1.172 rillig 10896: (Run "pkglint -F" to automatically fix some issues.)</pre>
1.1 dsieger 10897: <p>Depending on the supplied command line arguments (see pkglint(1)),
1.170 rillig 10898: more checks will be performed. Use e.g. <span class="command"><strong>pkglint
1.1 dsieger 10899: -Wall</strong></span> for a very thorough check.</p>
10900: </div>
10901: </div>
1.41 asau 10902: <div class="sect1">
1.1 dsieger 10903: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10904: <a name="steps-for-b-i-p"></a>A.2. Steps for building, installing, packaging</h2></div></div></div>
10905: <p>Create the directory where the package lives,
10906: plus any auxiliary directories:</p>
10907: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/pkgsrc/lang</code></strong>
10908: <code class="prompt">#</code> <strong class="userinput"><code>mkdir bison</code></strong>
10909: <code class="prompt">#</code> <strong class="userinput"><code>cd bison</code></strong>
10910: <code class="prompt">#</code> <strong class="userinput"><code>mkdir patches</code></strong></pre>
10911: <p>Create <code class="filename">Makefile</code>, <code class="filename">DESCR</code> and
1.184 rillig 10912: <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 10913: then continue with fetching the distfile:</p>
10914: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make fetch</code></strong>
10915: >> bison-1.25.tar.gz doesn't seem to exist on this system.
10916: >> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
10917: Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10918: ftp: Error retrieving file: 500 Internal error
10919:
10920: >> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
10921: Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10922: ftp: Error retrieving file: 500 Internal error
10923:
10924: >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
10925: Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10926: Successfully retrieved file.</pre>
10927: <p>Generate the checksum of the distfile into
10928: <code class="filename">distinfo</code>:</p>
10929: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make makedistinfo</code></strong></pre>
10930: <p>Now compile:</p>
10931: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
10932: >> Checksum OK for bison-1.25.tar.gz.
10933: ===> Extracting for bison-1.25
10934: ===> Patching for bison-1.25
10935: ===> Ignoring empty patch directory
10936: ===> Configuring for bison-1.25
10937: creating cache ./config.cache
10938: checking for gcc... cc
10939: checking whether we are using GNU C... yes
10940: checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
10941: checking how to run the C preprocessor... cc -E
10942: checking for minix/config.h... no
10943: checking for POSIXized ISC... no
10944: checking whether cross-compiling... no
10945: checking for ANSI C header files... yes
10946: checking for string.h... yes
10947: checking for stdlib.h... yes
10948: checking for memory.h... yes
10949: checking for working const... yes
10950: checking for working alloca.h... no
10951: checking for alloca... yes
10952: checking for strerror... yes
10953: updating cache ./config.cache
10954: creating ./config.status
10955: creating Makefile
10956: ===> Building for bison-1.25
10957: 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
10958: 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
10959: 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
10960: 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
10961: 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
10962: 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
10963: 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
10964: 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
10965: 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
10966: 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
10967: 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
10968: 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
10969: 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
10970: 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
10971: 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
10972: 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
10973: 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
10974: 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
10975: 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
10976: 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
10977: 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
10978: 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
10979: ./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
10980: rm -f bison.s1
10981: sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1</pre>
10982: <p>Everything seems OK, so install the files:</p>
10983: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
10984: >> Checksum OK for bison-1.25.tar.gz.
10985: ===> Installing for bison-1.25
10986: sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
10987: rm -f /usr/pkg/bin/bison
10988: cd /usr/pkg/share; rm -f bison.simple bison.hairy
10989: rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
10990: install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
10991: /usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
10992: /usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
10993: cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
10994: /usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
10995: ===> Registering installation for bison-1.25</pre>
10996: <p>You can now use bison, and also - if you decide so - remove it with
1.10 hubertf 10997: <span class="command"><strong>pkg_delete bison</strong></span>. Should you decide that you want a
1.1 dsieger 10998: binary package, do this now:</p>
10999: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
11000: >> Checksum OK for bison-1.25.tar.gz.
11001: ===> Building package for bison-1.25
11002: Creating package bison-1.25.tgz
11003: Registering depends:.
11004: Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre>
11005: <p>Now that you don't need the source and object files
11006: any more, clean up:</p>
11007: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make clean</code></strong>
11008: ===> Cleaning for bison-1.25</pre>
11009: </div>
11010: </div>
1.41 asau 11011: <div class="appendix">
11012: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 11013: <a name="hardening"></a>Appendix B. Security hardening</h1></div></div></div>
1.1 dsieger 11014: <div class="toc">
11015: <p><b>Table of Contents</b></p>
1.100 leot 11016: <dl class="toc">
1.207 leot 11017: <dt><span class="sect1"><a href="#hardening.mechanisms">B.1. Mechanisms</a></span></dt>
11018: <dd><dl>
11019: <dt><span class="sect2"><a href="#hardening.mechanisms.enabled">B.1.1. Enabled by default</a></span></dt>
11020: <dt><span class="sect2"><a href="#hardening.mechanisms.disabled">B.1.2. Not enabled by default</a></span></dt>
11021: </dl></dd>
11022: <dt><span class="sect1"><a href="#hardening.caveats">B.2. Caveats</a></span></dt>
11023: <dd><dl>
11024: <dt><span class="sect2"><a href="#hardening.caveats.pie">B.2.1. Problems with PKGSRC_MKPIE</a></span></dt>
11025: <dt><span class="sect2"><a href="#hardening.caveats.fortify">B.2.2. Problems with PKGSRC_USE_FORTIFY</a></span></dt>
11026: <dt><span class="sect2"><a href="#hardening.caveats.relro">B.2.3. Problems with PKGSRC_USE_RELRO</a></span></dt>
11027: <dt><span class="sect2"><a href="#hardening.caveats.ssp">B.2.4. Problems with PKGSRC_USE_SSP</a></span></dt>
11028: </dl></dd>
11029: <dt><span class="sect1"><a href="#hardening.audit">B.3. Auditing the system</a></span></dt>
11030: <dd><dl>
11031: <dt><span class="sect2"><a href="#hardening.audit.pie">B.3.1. Checking for PIE</a></span></dt>
11032: <dt><span class="sect2"><a href="#hardening.audit.relropartial">B.3.2. Checking for partial RELRO</a></span></dt>
11033: <dt><span class="sect2"><a href="#hardening.audit.relrofull">B.3.3. Checking for full RELRO</a></span></dt>
11034: <dt><span class="sect2"><a href="#hardening.audit.ssp">B.3.4. Checking for SSP</a></span></dt>
11035: </dl></dd>
1.1 dsieger 11036: </dl>
11037: </div>
1.207 leot 11038: <p>
11039: A number of mechanisms are available in pkgsrc to improve the security of the
11040: resulting system. This page describes the mechanisms, and gives hints
11041: about detecting and fixing problems.
11042: </p>
11043: <p>
11044: Mechanisms can be enabled individually in
11045: <code class="filename">mk.conf</code>, and are
11046: individually described below.
11047: </p>
11048: <p>
11049: Typically, a feature will cause some programs to fail to build or work
11050: when first enabled. This can be due to latent problems in the
11051: program, and can be due to other reasons. After enough testing to
11052: have confidence that user problems will be quite rare, individual
11053: mechanisms will be enabled by default.
11054: </p>
11055: <p>
11056: For each mechanism, see the Caveats section below for an explanation
11057: of what might go wrong at compile time and at run time, and how to
11058: notice and address these problems.
11059: </p>
1.41 asau 11060: <div class="sect1">
1.1 dsieger 11061: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11062: <a name="hardening.mechanisms"></a>B.1. Mechanisms</h2></div></div></div>
11063: <div class="sect2">
11064: <div class="titlepage"><div><div><h3 class="title">
11065: <a name="hardening.mechanisms.enabled"></a>B.1.1. Enabled by default</h3></div></div></div>
11066: <div class="sect3">
11067: <div class="titlepage"><div><div><h4 class="title">
11068: <a name="hardening.mechanisms.enabled.fortify"></a>B.1.1.1. PKGSRC_USE_FORTIFY</h4></div></div></div>
11069: <p>
11070: This allows substitute wrappers to be used for some commonly used
11071: library functions that do not have built-in bounds checking - but
11072: could in some cases.
11073: </p>
11074: <p>
11075: Two mitigation levels are available:
11076: </p>
11077: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11078: <li class="listitem"><p>"weak" only enables checks at compile-time.</p></li>
11079: <li class="listitem"><p>"strong" enables checks at compile-time and runtime.</p></li>
11080: </ul></div>
11081: <p>
11082: "strong" has been enabled by default since pkgsrc-2017Q3.
11083: </p>
11084: </div>
11085: <div class="sect3">
11086: <div class="titlepage"><div><div><h4 class="title">
11087: <a name="hardening.mechanisms.enabled.ssp"></a>B.1.1.2. PKGSRC_USE_SSP</h4></div></div></div>
11088: <p>
11089: This enables a stack-smashing protection mitigation. It is done by adding a
11090: guard variable to functions with vulnerable objects. The guards are initialized
11091: when a function is entered and then checked when the function exits. The guard
11092: check will fail and the program forcibly exited if the variable was modified in
11093: the meantime. This can happen in case of buffer overflows or memory corruption,
11094: and therefore exposing these bugs.
11095: </p>
11096: <p>
11097: Different mitigation levels are available:
11098: </p>
11099: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11100: <li class="listitem"><p>"yes", which will only protect functions considered vulnerable
11101: by the compiler;</p></li>
11102: <li class="listitem"><p>"all", which will protect every function;</p></li>
11103: <li class="listitem"><p>"strong", the default, which will apply a better balance between the
11104: two settings above.</p></li>
11105: </ul></div>
11106: <p>
11107: This mitigation is supported by both GCC and clang. It may be supported in
11108: additional compilers, possibly under a different name. It is particularly useful
11109: for unsafe programming languages, such as C/C++.
11110: </p>
11111: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11112: <li class="listitem"><p>"yes" is enabled by default where known supported since pkgsrc-2017Q3.</p></li>
11113: <li class="listitem"><p>"strong" is enabled by default where known supported since pkgsrc-2021Q4.</p></li>
11114: </ul></div>
11115: <p>More details can be found here:</p>
11116: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11117: <a class="ulink" href="https://en.wikipedia.org/wiki/Buffer_overflow_protection" target="_top">Buffer overflow protection on Wikipedia</a>
11118: </p></li></ul></div>
11119: </div>
11120: <div class="sect3">
11121: <div class="titlepage"><div><div><h4 class="title">
11122: <a name="hardening.mechanisms.enabled.pie"></a>B.1.1.3. PKGSRC_MKPIE</h4></div></div></div>
11123: <p>
11124: This requests the creation of PIE (Position Independent Executables) for all
11125: executables. The PIE mechanism is normally used for shared libraries, so that
11126: they can be loaded at differing addresses at runtime. PIE itself does not have
11127: useful security properties; however, it is necessary to fully leverage some,
11128: such as ASLR. Some operating systems support Address Space Layout Randomization
11129: (ASLR), which causes different addresses to be used each time a program is run.
11130: This makes it more difficult for an attacker to guess addresses and thus makes
11131: exploits harder to construct. With PIE, ASLR can really be applied to the entire
11132: program, instead of the stack and heap only.
11133: </p>
11134: <p>
11135: PIE executables will only be built for toolchains that are known to support PIE.
11136: Currently, this means NetBSD on x86, ARM, SPARC64, m68k, and MIPS.
11137: </p>
11138: <p>
11139: <code class="varname">PKGSRC_MKPIE</code> was enabled by default after the pkgsrc-2021Q3 branch.
11140: </p>
1.1 dsieger 11141: </div>
1.210 gutterid 11142: <div class="sect3">
11143: <div class="titlepage"><div><div><h4 class="title">
1.219 nia 11144: <a name="hardening.mechanisms.enabled.relro"></a>B.1.1.4. PKGSRC_USE_RELRO</h4></div></div></div>
1.207 leot 11145: <p>
11146: This also makes the exploitation of some security vulnerabilities more
11147: difficult in some cases.
11148: </p>
11149: <p>Two different mitigation levels are available:</p>
11150: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11151: <li class="listitem"><p>
1.219 nia 11152: partial (the default): the ELF sections are reordered so that internal data sections
1.207 leot 11153: precede the program's own data sections, and non-PLT GOT is read-only;
11154: </p></li>
11155: <li class="listitem"><p>
11156: full: in addition to partial RELRO, every relocation is performed immediately
1.218 nia 11157: when starting the program, allowing the entire GOT to be read-only. This
11158: can greatly slow down startup of large programs.
1.207 leot 11159: </p></li>
11160: </ul></div>
11161: <p>
11162: This is currently supported by GCC. Many software distributions now enable this
1.220 nia 11163: feature by default, at the "partial" level.
1.207 leot 11164: </p>
11165: <p>
11166: More details can be found here:
11167: </p>
11168: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11169: <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>
11170: </p></li></ul></div>
1.1 dsieger 11171: </div>
1.219 nia 11172: </div>
11173: <div class="sect2">
11174: <div class="titlepage"><div><div><h3 class="title">
11175: <a name="hardening.mechanisms.disabled"></a>B.1.2. Not enabled by default</h3></div></div></div>
11176: <div class="sect3">
11177: <div class="titlepage"><div><div><h4 class="title">
11178: <a name="hardening.mechanisms.disabled.repro"></a>B.1.2.1. PKGSRC_MKREPRO</h4></div></div></div>
11179: <p>
11180: With this option, pkgsrc will try to build packages reproducibly. This allows
11181: packages built from the same tree and with the same options, to produce
11182: identical results bit by bit. This option should be combined with ASLR and
11183: <code class="varname">PKGSRC_MKPIE</code> to avoid predictable address offsets for
11184: attackers attempting to exploit security vulnerabilities.
11185: </p>
11186: <p>
11187: More details can be found here:
11188: </p>
11189: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
11190: <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>
11191: </p></li></ul></div>
11192: <p>
11193: More work likely needs to be done before pkgsrc is fully reproducible.
11194: </p>
11195: </div>
1.207 leot 11196: <div class="sect3">
11197: <div class="titlepage"><div><div><h4 class="title">
1.219 nia 11198: <a name="hardening.mechanisms.disabled.stackcheck"></a>B.1.2.2. PKGSRC_USE_STACK_CHECK</h4></div></div></div>
1.207 leot 11199: <p>
11200: This uses <code class="literal">-fstack-check</code> with GCC for
11201: another stack protection mitigation.
11202: </p>
11203: <p>
11204: It asks the compiler to generate code verifying that it does not corrupt the
11205: stack. According to GCC's manual page, this is really only useful for
11206: multi-threaded programs.
11207: </p>
1.1 dsieger 11208: </div>
11209: </div>
11210: </div>
1.41 asau 11211: <div class="sect1">
1.1 dsieger 11212: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11213: <a name="hardening.caveats"></a>B.2. Caveats</h2></div></div></div>
11214: <div class="sect2">
11215: <div class="titlepage"><div><div><h3 class="title">
11216: <a name="hardening.caveats.pie"></a>B.2.1. Problems with PKGSRC_MKPIE</h3></div></div></div>
11217: <div class="sect3">
11218: <div class="titlepage"><div><div><h4 class="title">
11219: <a name="hardening.caveats.pie.build"></a>B.2.1.1. Packages failing to build</h4></div></div></div>
11220: <p>
11221: A number of packages may fail to build with this option enabled. The
11222: failures are often related to the absence of the <code class="literal">-fPIC</code>
11223: compilation flag when building libraries or executables (or ideally
11224: <code class="literal">-fPIE</code> in the latter case). This flag is added to the
11225: <code class="varname">CFLAGS</code> already, but requires the package to
11226: actually support it.
11227: </p>
11228: <div class="sect4">
11229: <div class="titlepage"><div><div><h5 class="title">
11230: <a name="hardening.caveats.pie.build.fix"></a>B.2.1.1.1. How to fix</h5></div></div></div>
11231: <p>
11232: These instructions are meant as a reference only; they likely need to be adapted
11233: for many packages individually.
11234: </p>
11235: <p>
11236: For packages using <code class="filename">Makefiles</code>:
11237: </p>
11238: <pre class="programlisting">
11239: MAKE_FLAGS+= CFLAGS=${CFLAGS:Q}
11240: MAKE_FLAGS+= LDFLAGS=${LDFLAGS:Q}
11241: </pre>
11242: <p>
11243: For packages using <code class="filename">Imakefiles</code>:
11244: </p>
11245: <pre class="programlisting">
11246: MAKE_FLAGS+= CCOPTIONS=${CFLAGS:Q}
11247: MAKE_FLAGS+= LOCAL_LDFLAGS=${LDFLAGS:Q}
11248: </pre>
11249: </div>
11250: </div>
11251: <div class="sect3">
11252: <div class="titlepage"><div><div><h4 class="title">
11253: <a name="hardening.caveats.pie.crash"></a>B.2.1.2. Run-time crashes</h4></div></div></div>
11254: <p>
11255: Some programs may fail to run, or crash at random times once built as PIE. Two
11256: scenarios are essentially possible. This is nearly always due to a bug in
11257: the program being exposed due to ASLR.
11258: </p>
11259: </div>
11260: <div class="sect3">
11261: <div class="titlepage"><div><div><h4 class="title">
11262: <a name="hardening.caveats.pie.disable"></a>B.2.1.3. Disabling PKGSRC_MKPIE on a per-package basis</h4></div></div></div>
11263: <p>
11264: Ideally, packages should be fixed for compatibility with MKPIE.
11265: However, in some cases this is very difficult, due to complex build systems,
11266: packages using non-standard toolchains, or programming languages with odd
11267: bootstrapping mechanisms.
11268: </p>
11269: <p>
11270: To disable <code class="varname">PKGSRC_MKPIE</code> on a per-package basis, set
11271: <code class="varname">MKPIE_SUPPORTED= no</code> in the package's Makefile before
11272: <code class="filename">bsd.prefs.mk</code> is included.
11273: </p>
11274: </div>
11275: </div>
11276: <div class="sect2">
11277: <div class="titlepage"><div><div><h3 class="title">
11278: <a name="hardening.caveats.fortify"></a>B.2.2. Problems with PKGSRC_USE_FORTIFY</h3></div></div></div>
11279: <div class="sect3">
11280: <div class="titlepage"><div><div><h4 class="title">
11281: <a name="hardening.caveats.fortify.build"></a>B.2.2.1. Packages failing to build</h4></div></div></div>
11282: <p>
11283: This feature makes use of pre-processing directives to look for hardened,
11284: alternative implementations of essential library calls. Some programs may fail
11285: to build as a result; this usually happens for those trying too hard to be
11286: portable, or otherwise abusing definitions in the standard library.
11287: </p>
11288: </div>
11289: <div class="sect3">
11290: <div class="titlepage"><div><div><h4 class="title">
11291: <a name="hardening.caveats.fortify.crash"></a>B.2.2.2. Run-time crashes</h4></div></div></div>
11292: <p>
11293: This feature may cause some programs to crash, usually indicating an
11294: actual bug in the program. The fix will typically involve patching the
11295: original program's source code.
11296: </p>
11297: </div>
11298: <div class="sect3">
11299: <div class="titlepage"><div><div><h4 class="title">
11300: <a name="hardening.caveats.fortify.opt"></a>B.2.2.3. Optimization is required</h4></div></div></div>
11301: <p>
11302: At least in the case of GCC, FORTIFY will only be applied if optimization is
11303: applied while compiling. This means that the <code class="varname">CFLAGS</code> should
11304: also contain <code class="literal">-O</code>, <code class="literal">-O2</code> or another
11305: optimization level. This cannot easily be applied globally, as some packages
11306: may require specific optimization levels.
11307: </p>
11308: </div>
11309: <div class="sect3">
11310: <div class="titlepage"><div><div><h4 class="title">
11311: <a name="hardening.caveats.fortify.disable"></a>B.2.2.4. Disabling FORTIFY on a per-package basis</h4></div></div></div>
11312: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11313: <h3 class="title">Note</h3>
11314: <p>FORTIFY should not be disabled to work around runtime crashes in
11315: the program! This is a very bad idea and will expose you to security
11316: vulnerabilities.
11317: </p>
11318: </div>
11319: <p>
11320: To disable FORTIFY on a per-package basis, set the following
11321: in the package's <code class="filename">Makefile</code>
11322: before <code class="filename">bsd.prefs.mk</code> is included:
11323: </p>
11324: <pre class="programlisting">
11325: FORTIFY_SUPPORTED= no
11326: </pre>
11327: </div>
11328: </div>
11329: <div class="sect2">
11330: <div class="titlepage"><div><div><h3 class="title">
11331: <a name="hardening.caveats.relro"></a>B.2.3. Problems with PKGSRC_USE_RELRO</h3></div></div></div>
11332: <div class="sect3">
11333: <div class="titlepage"><div><div><h4 class="title">
11334: <a name="hardening.caveats.relro.performance"></a>B.2.3.1. Performance impact</h4></div></div></div>
11335: <p>
11336: For better protection, full RELRO requires every symbol to be resolved when the
11337: program starts, rather than simply when required at run-time. This will have
11338: more impact on programs using a lot of symbols, or linked to libraries exposing
11339: a lot of symbols. Therefore, daemons or programs otherwise running in
11340: background are affected only when started. Programs loading plug-ins at
11341: run-time are affected when loading the plug-ins.
11342: </p>
11343: <p>
11344: The impact is not expected to be noticeable on modern hardware, except in some
11345: cases for big programs.
11346: </p>
11347: </div>
11348: <div class="sect3">
11349: <div class="titlepage"><div><div><h4 class="title">
11350: <a name="hardening.caveats.relro.crash"></a>B.2.3.2. Run-time crashes</h4></div></div></div>
11351: <p>
11352: Some programs handle plug-ins and dependencies in a way that conflicts with
11353: RELRO: for instance, with an initialization routine listing any other plug-in
11354: required. With full RELRO, the missing symbols are resolved before the
11355: initialization routine can run, and the dynamic loader will not be able to find
11356: them directly and abort as a result. Unfortunately, this is how Xorg loads its
11357: drivers. Partial RELRO can be applied instead in this case.
11358: </p>
11359: </div>
11360: <div class="sect3">
11361: <div class="titlepage"><div><div><h4 class="title">
11362: <a name="hardening.caveats.relro.disable"></a>B.2.3.3. Disabling RELRO on a per-package basis</h4></div></div></div>
11363: <p>
11364: To disable RELRO on a per-package basis, set the following
11365: in the package's <code class="filename">Makefile</code>
11366: before <code class="filename">bsd.prefs.mk</code> is included:
11367: </p>
11368: <pre class="programlisting">
11369: RELRO_SUPPORTED= no
11370: </pre>
1.209 nia 11371: <p>
11372: It is also possible to at most enable partial RELRO, by
11373: setting <code class="varname">RELRO_SUPPORTED</code> to <code class="literal">partial</code>.
11374: </p>
1.207 leot 11375: </div>
11376: </div>
11377: <div class="sect2">
11378: <div class="titlepage"><div><div><h3 class="title">
11379: <a name="hardening.caveats.ssp"></a>B.2.4. Problems with PKGSRC_USE_SSP</h3></div></div></div>
11380: <div class="sect3">
11381: <div class="titlepage"><div><div><h4 class="title">
11382: <a name="hardening.caveats.ssp.build"></a>B.2.4.1. Packages failing to build</h4></div></div></div>
11383: <p>
11384: The stack-smashing protection provided by this option does not work for some
11385: programs. The most common situation in which this happens is when the program
11386: allocates variables on the stack, with the size determined at run-time.
11387: </p>
11388: </div>
11389: <div class="sect3">
11390: <div class="titlepage"><div><div><h4 class="title">
11391: <a name="hardening.caveats.ssp.crash"></a>B.2.4.2. Run-time crashes</h4></div></div></div>
11392: <p>
11393: Again, this feature may cause some programs to crash via a
11394: <code class="varname">SIGABRT</code>, usually indicating an actual bug in the program.
11395: </p>
11396: <p>
11397: On NetBSD <code class="varname">LOG_CRIT</code> level syslog
11398: messages are sent and - by default -
11399: appended to <code class="filename">/var/log/messages</code>, e.g.:
11400: </p>
11401: <pre class="programlisting">
11402: Jan 6 15:42:51 hostname -: hostname program - - - buffer overflow detected; terminated
11403: </pre>
11404: <p>
11405: (where <code class="literal">hostname</code> is the hostname(1) and
11406: <code class="literal">program</code> is the basename(1) of the program crashed).
11407: </p>
11408: <p>
11409: Patching the original program is then required.
11410: </p>
11411: <p>
11412: Rebuilding the package via:
11413: </p>
11414: <pre class="programlisting">
11415: <strong class="userinput"><code>% env CFLAGS=-g INSTALL_UNSTRIPPED=yes make replace</code></strong>
11416: </pre>
11417: <p>
11418: and inspecting the backtrace of the coredump via the debugger
11419: should point out the problematic call by inspecting the frame
11420: calling the _chk() (SSP) function.
11421: </p>
11422: </div>
11423: <div class="sect3">
11424: <div class="titlepage"><div><div><h4 class="title">
11425: <a name="hardening.caveats.ssp.performance"></a>B.2.4.3. Performance impact</h4></div></div></div>
11426: <p>
11427: The compiler emits extra code when using this feature: a check for buffer
11428: overflows is performed when entering and exiting functions, requiring an extra
11429: variable on the stack. The level of protection can otherwise be adjusted to
11430: affect only those functions considered more sensitive by the compiler (with
11431: -fstack-protector instead of -fstack-protector-all).
11432: </p>
11433: <p>
11434: The impact is not expected to be noticeable on modern hardware. However,
11435: programs with a hard requirement to run at the fastest possible speed should
11436: avoid using this feature, or using libraries built with this feature.
11437: </p>
11438: </div>
11439: <div class="sect3">
11440: <div class="titlepage"><div><div><h4 class="title">
11441: <a name="hardening.caveats.ssp.disable"></a>B.2.4.4. Disabling SSP on a per-package basis</h4></div></div></div>
11442: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11443: <h3 class="title">Note</h3>
11444: <p>SSP should not be disabled to work around runtime crashes in
11445: the program! This is a very bad idea and will expose you to security
11446: vulnerabilities.</p>
11447: </div>
11448: <p>
11449: To disable SSP on a per-package basis, set the following
11450: in the package's <code class="filename">Makefile</code>
11451: before <code class="filename">bsd.prefs.mk</code> is included:
11452: </p>
11453: <pre class="programlisting">
11454: SSP_SUPPORTED= no
11455: </pre>
11456: </div>
11457: </div>
11458: </div>
11459: <div class="sect1">
11460: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11461: <a name="hardening.audit"></a>B.3. Auditing the system</h2></div></div></div>
11462: <p>
11463: The illusion of security is worse than having no security at all. This section
11464: lists a number of ways to ensure the security features requested are actually
11465: effective.
11466: </p>
11467: <p>
11468: These instructions were obtained and tested on a system derived from NetBSD 7
11469: (amd64). YMMV.
11470: </p>
11471: <div class="sect2">
11472: <div class="titlepage"><div><div><h3 class="title">
11473: <a name="hardening.audit.pie"></a>B.3.1. Checking for PIE</h3></div></div></div>
11474: <p>
11475: The ELF executable type in use changes for binaries built as PIE; without:
11476: </p>
11477: <pre class="programlisting">
11478: <strong class="userinput"><code>$ file /path/to/bin/ary</code></strong>
11479: /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
11480: </pre>
11481: <p>as opposed to the following binary, built as PIE:</p>
11482: <pre class="programlisting">
11483: <strong class="userinput"><code>$ file /path/to/pie/bin/ary</code></strong>
11484: /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
11485: </pre>
11486: <p>
11487: The latter result is then what is expected.
11488: </p>
11489: </div>
11490: <div class="sect2">
11491: <div class="titlepage"><div><div><h3 class="title">
11492: <a name="hardening.audit.relropartial"></a>B.3.2. Checking for partial RELRO</h3></div></div></div>
11493: <p>
11494: The following command should list a section called RELRO:
11495: </p>
11496: <pre class="programlisting">
11497: <strong class="userinput"><code>$ objdump -p /path/to/bin/ary</code></strong>
11498:
11499: /path/to/bin/ary: file format elf64-x86-64
11500:
11501: Program Header:
11502: [...]
11503: RELRO off 0x0000000000000d78 vaddr 0x0000000000600d78 paddr 0x0000000000600d78 align 2**0
11504: </pre>
11505: <p>
11506: This check is now performed automatically if
11507: <code class="varname">PKG_DEVELOPER</code> is set and RELRO is enabled.
11508: </p>
11509: </div>
11510: <div class="sect2">
11511: <div class="titlepage"><div><div><h3 class="title">
11512: <a name="hardening.audit.relrofull"></a>B.3.3. Checking for full RELRO</h3></div></div></div>
11513: <p>
11514: The dynamic loader will apply RELRO immediately when detecting the presence of
11515: the <code class="varname">BIND_NOW</code> flag:
11516: </p>
11517: <pre class="programlisting">
11518: <strong class="userinput"><code>$ objdump -x /path/to/bin/ary</code></strong>
11519:
11520: /path/to/bin/ary: file format elf64-x86-64
11521:
11522: Dynamic Section:
11523: [...]
11524: BIND_NOW 0x0000000000000000
11525: </pre>
11526: <p>
11527: This has to be combined with partial RELRO (see above) to be fully efficient.
11528: </p>
11529: <p>
11530: This check is now performed automatically (where supported) if
11531: <code class="varname">PKG_DEVELOPER</code> is set.
11532: </p>
11533: </div>
11534: <div class="sect2">
11535: <div class="titlepage"><div><div><h3 class="title">
11536: <a name="hardening.audit.ssp"></a>B.3.4. Checking for SSP</h3></div></div></div>
1.208 nia 11537: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
11538: <h3 class="title">Note</h3>
11539: <p>
11540: Checking for SSP using this method only works where the operating system
11541: uses <code class="literal">libssp</code>. <code class="literal">libssp</code> is not used
11542: on recent NetBSD/FreeBSD/Linux versions.
11543: </p>
11544: </div>
1.207 leot 11545: <p>
11546: Building objects, binaries and libraries with SSP will affect the presence of
11547: additional symbols in the resulting file:
11548: </p>
11549: <pre class="programlisting">
11550: <strong class="userinput"><code>$ nm /path/to/bin/ary</code></strong>
11551: [...]
11552: U __stack_chk_fail
11553: 0000000000600ea0 B __stack_chk_guard
11554: </pre>
11555: <p>
11556: This is an indicator that the program was indeed built with support for SSP.
11557: </p>
11558: <p>
11559: This check is now performed automatically (where supported) if
11560: <code class="varname">PKG_DEVELOPER</code> is set and SSP is enabled.
11561: </p>
11562: </div>
11563: </div>
11564: </div>
11565: <div class="appendix">
11566: <div class="titlepage"><div><div><h1 class="title">
11567: <a name="logs"></a>Appendix C. Build logs</h1></div></div></div>
11568: <div class="toc">
11569: <p><b>Table of Contents</b></p>
11570: <dl class="toc">
11571: <dt><span class="sect1"><a href="#logs.building">C.1. Building figlet</a></span></dt>
11572: <dt><span class="sect1"><a href="#logs.package">C.2. Packaging figlet</a></span></dt>
11573: </dl>
11574: </div>
11575: <div class="sect1">
11576: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11577: <a name="logs.building"></a>C.1. Building figlet</h2></div></div></div>
11578: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
11579: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11580: => figlet221.tar.gz doesn't seem to exist on this system.
11581: => Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
11582: => [172219 bytes]
11583: Connected to ftp.plig.net.
11584: 220 ftp.plig.org NcFTPd Server (licensed copy) ready.
11585: 331 Guest login ok, send your complete e-mail address as password.
11586: 230-You are user #5 of 500 simultaneous users allowed.
11587: 230-
11588: 230- ___ _ _ _
11589: 230- | _| |_ ___ ___| |_|___ ___ ___ ___
11590: 230- | _| _| . |_| . | | | . |_| . | _| . |
11591: 230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
11592: 230- |_| |_| |___| |___|
11593: 230-
11594: 230-** Welcome to ftp.plig.org **
11595: 230-
11596: 230-Please note that all transfers from this FTP site are logged. If you
11597: 230-do not like this, please disconnect now.
11598: 230-
11599: 230-This archive is available via
11600: 230-
11601: 230-HTTP: http://ftp.plig.org/
11602: 230-FTP: ftp://ftp.plig.org/ (max 500 connections)
11603: 230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
11604: 230-
11605: 230-Please email comments, bug reports and requests for packages to be
11606: 230-mirrored to ftp-admin@plig.org.
11607: 230-
11608: 230-
11609: 230 Logged in anonymously.
11610: Remote system type is UNIX.
11611: Using binary mode to transfer files.
11612: 200 Type okay.
11613: 250 "/pub" is new cwd.
11614: 250-"/pub/figlet" is new cwd.
11615: 250-
11616: 250-Welcome to the figlet archive at ftp.figlet.org
11617: 250-
11618: 250- ftp://ftp.figlet.org/pub/figlet/
11619: 250-
11620: 250-The official FIGlet web page is:
11621: 250- http://www.figlet.org/
11622: 250-
11623: 250-If you have questions, please mailto:info@figlet.org. If you want to
11624: 250-contribute a font or something else, you can email us.
11625: 250
11626: 250 "/pub/figlet/program" is new cwd.
11627: 250 "/pub/figlet/program/unix" is new cwd.
11628: local: figlet221.tar.gz remote: figlet221.tar.gz
11629: 502 Unimplemented command.
11630: 227 Entering Passive Mode (195,40,6,41,246,104)
11631: 150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
11632: 38% |************** | 65800 64.16 KB/s 00:01 ETA
11633: 226 Transfer completed.
11634: 172219 bytes received in 00:02 (75.99 KB/s)
11635: 221 Goodbye.
11636: => Checksum OK for figlet221.tar.gz.
11637: ===> Extracting for figlet-2.2.1nb2
11638: ===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
11639: ===> Patching for figlet-2.2.1nb2
11640: ===> Applying pkgsrc patches for figlet-2.2.1nb2
11641: ===> Overriding tools for figlet-2.2.1nb2
11642: ===> Creating toolchain wrappers for figlet-2.2.1nb2
11643: ===> Configuring for figlet-2.2.1nb2
11644: ===> Building for figlet-2.2.1nb2
11645: gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
11646: chmod a+x figlet
11647: gcc -O2 -o chkfont chkfont.c
11648: => Unwrapping files-to-be-installed.
11649: <code class="prompt">#</code>
11650: <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
11651: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11652: ===> Installing for figlet-2.2.1nb2
11653: install -d -o root -g wheel -m 755 /usr/pkg/bin
11654: install -d -o root -g wheel -m 755 /usr/pkg/man/man6
11655: mkdir -p /usr/pkg/share/figlet
11656: cp figlet /usr/pkg/bin
11657: cp chkfont /usr/pkg/bin
11658: chmod 555 figlist showfigfonts
11659: cp figlist /usr/pkg/bin
11660: cp showfigfonts /usr/pkg/bin
11661: cp fonts/*.flf /usr/pkg/share/figlet
11662: cp fonts/*.flc /usr/pkg/share/figlet
11663: cp figlet.6 /usr/pkg/man/man6
11664: ===> Registering installation for figlet-2.2.1nb2
11665: <code class="prompt">#</code></pre>
11666: </div>
11667: <div class="sect1">
11668: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11669: <a name="logs.package"></a>C.2. Packaging figlet</h2></div></div></div>
11670: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
11671: ===> Checking for vulnerabilities in figlet-2.2.1nb2
11672: ===> Packaging figlet-2.2.1nb2
11673: ===> Building binary package for figlet-2.2.1nb2
11674: Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
11675: Using SrcDir value of /usr/pkg
11676: Registering depends:.
11677: <code class="prompt">#</code></pre>
11678: </div>
11679: </div>
11680: <div class="appendix">
11681: <div class="titlepage"><div><div><h1 class="title">
11682: <a name="ftp-layout"></a>Appendix D. Directory layout of the pkgsrc FTP server</h1></div></div></div>
11683: <div class="toc">
11684: <p><b>Table of Contents</b></p>
11685: <dl class="toc">
11686: <dt><span class="sect1"><a href="#ftp-distfiles">D.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
11687: <dt><span class="sect1"><a href="#ftp-misc">D.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
11688: <dt><span class="sect1"><a href="#ftp-packages">D.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
11689: <dt><span class="sect1"><a href="#ftp-reports">D.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
11690: <dt><span class="sect1"><a href="#ftp-source">D.5. <code class="filename">current</code>,
11691: <code class="filename">stable</code>,
11692: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
11693: source packages</a></span></dt>
11694: </dl>
11695: </div>
11696: <p>As in other big projects, the directory layout of pkgsrc
11697: is quite complex for newbies. This chapter explains where you
11698: find things on the FTP server. The base directory on
11699: <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>.
11700: On other servers it may be different, but inside this directory,
11701: everything should look the same, no matter on which server you
11702: are. This directory contains some subdirectories, which are
11703: explained below.</p>
11704: <div class="sect1">
11705: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11706: <a name="ftp-distfiles"></a>D.1. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div>
11707: <p>The directory <code class="filename">distfiles</code> contains lots
11708: of archive files from all pkgsrc packages, which are mirrored
11709: here. The subdirectories are called after their package names
11710: and are used when the distributed files have names that don't
11711: explicitly contain a version number or are otherwise too generic
11712: (for example <code class="filename">release.tar.gz</code>).</p>
11713: </div>
11714: <div class="sect1">
11715: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11716: <a name="ftp-misc"></a>D.2. <code class="filename">misc</code>: Miscellaneous things</h2></div></div></div>
11717: <p>This directory contains things that individual pkgsrc
11718: developers find worth publishing.</p>
11719: </div>
11720: <div class="sect1">
11721: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11722: <a name="ftp-packages"></a>D.3. <code class="filename">packages</code>: Binary packages</h2></div></div></div>
11723: <p>This directory contains binary packages for the various
11724: platforms that are supported by pkgsrc.
11725: 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>
11726: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
11727: <li class="listitem"><p><code class="varname">OPSYS</code> is the name of the
11728: operating system for which the packages have been built. The
11729: name is taken from the output of the <span class="command"><strong>uname</strong></span>
11730: command, so it may differ from the one you are used to
11731: hear.</p></li>
11732: <li class="listitem"><p><code class="varname">ARCH</code> is the hardware
11733: architecture of the platform for which the packages have been
11734: built. It also includes the <code class="varname">ABI</code> (Application
11735: Binary Interface) for platforms that have several of
11736: them.</p></li>
11737: <li class="listitem"><p><code class="varname">OSVERSION</code> is the version of
11738: the operating system. For version numbers that change often (for
11739: example NetBSD-current), the often-changing part should be
11740: replaced with an <code class="literal">x</code>, for example
11741: <code class="literal">4.99.x</code>.</p></li>
11742: <li class="listitem"><p><code class="varname">TAG</code> is either
11743: <code class="literal">20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11744: for a stable branch, or <code class="literal">head</code> for packages
11745: built from the HEAD branch. The latter should only be used when
11746: the packages are updated on a regular basis. Otherwise the date
11747: from checking out pkgsrc should be appended, for example
11748: <code class="literal">head_20071015</code>.</p></li>
11749: </ul></div>
11750: <p>The rationale for exactly this scheme is that the pkgsrc users looking for binary packages
11751: can quickly click through the directories on the
11752: server and find the best binary packages for their machines. Since they
11753: usually know the operating system and the hardware architecture, OPSYS
11754: and ARCH are placed first. After these choices, they can select the
11755: best combination of OSVERSION and TAG together, since it is usually the
11756: case that packages stay compatible between different version of the
11757: operating system.</p>
11758: <p>In each of these directories, there is a
11759: whole binary packages collection for a specific platform. It has a directory called
11760: <code class="filename">All</code> which contains all binary packages.
11761: Besides that, there are various category directories that
11762: contain symbolic links to the real binary packages.</p>
11763: </div>
11764: <div class="sect1">
11765: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11766: <a name="ftp-reports"></a>D.4. <code class="filename">reports</code>: Bulk build reports</h2></div></div></div>
1.8 rillig 11767: <p>Here are the reports from bulk builds, for those who want
11768: to fix packages that didn't build on some of the platforms. The
1.207 leot 11769: 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 11770: </div>
1.41 asau 11771: <div class="sect1">
1.8 rillig 11772: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 11773: <a name="ftp-source"></a>D.5. <code class="filename">current</code>,
1.148 leot 11774: <code class="filename">stable</code>,
1.22 jakllsch 11775: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 11776: source packages</h2></div></div></div>
1.23 wiz 11777: <p>These directories contain the <span class="quote">“<span class="quote">real</span>”</span> pkgsrc,
1.1 dsieger 11778: that is the files that define how to create binary packages from
11779: source archives.</p>
1.149 leot 11780: <p>Each of the <code class="filename">current</code>,
11781: <code class="filename">stable</code> and
11782: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11783: directories share the same structure. They each contain a
11784: <code class="filename">pkgsrc</code> directory and
11785: <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> file.</p>
1.1 dsieger 11786: <p>The directory <code class="filename">pkgsrc</code> contains a
11787: snapshot of the CVS repository, which is updated regularly. The
1.149 leot 11788: file <code class="filename">pkgsrc.tar.{bz,gz,xz}</code> contains the same
11789: as the directory, ready to be downloaded as a whole.</p>
11790: <p>The <code class="filename">current</code> directory contains files
11791: related to the HEAD branch of the CVS repository.
11792: In this directory there is an additional file called
11793: <code class="filename">pkgsrc-readmes.tar.{bz,gz,xz}</code> that contains
11794: all pkgsrc <code class="filename">README</code>s with information about
11795: categories and packages.
11796: </p>
11797: <p>The <code class="filename">stable</code> directory is a symlink to
11798: the latest
11799: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11800: </p>
11801: <p>The
11802: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>.
11803: directories contain files related to the
11804: <code class="filename">-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
11805: stable branch of the CVS repository. In these directories there is
11806: an additional file called
11807: <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 11808: which contains the state of pkgsrc when it was branched.</p>
11809: </div>
11810: </div>
1.41 asau 11811: <div class="appendix">
11812: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 11813: <a name="help-topics"></a>Appendix E. Help topics</h1></div></div></div>
1.154 rillig 11814: <p>
11815: The following list contains all help topics that are available
11816: when running <span class="command"><strong>bmake help topic=:index</strong></span>.
11817: </p>
1.156 leot 11818: <table border="0" summary="Simple list" class="simplelist">
11819: <tr>
11820: <td>#!</td>
11821: <td>-lintl</td>
11822: </tr>
11823: <tr>
1.205 wiz 11824: <td>32bit</td>
1.156 leot 11825: <td>64bit</td>
1.205 wiz 11826: </tr>
11827: <tr>
1.156 leot 11828: <td>ABI</td>
1.205 wiz 11829: <td>ACCEPTABLE_LICENSES</td>
1.156 leot 11830: </tr>
11831: <tr>
11832: <td>ACROREAD_FONTPATH</td>
1.205 wiz 11833: <td>ADDITIONAL</td>
1.156 leot 11834: </tr>
11835: <tr>
11836: <td>AFAIK</td>
1.205 wiz 11837: <td>AIX</td>
1.156 leot 11838: </tr>
11839: <tr>
11840: <td>ALLOW_VULNERABLE_PACKAGES</td>
1.205 wiz 11841: <td>ALL_ENV</td>
1.156 leot 11842: </tr>
11843: <tr>
1.200 cirnatda 11844: <td>ALTERNATIVES_SRC</td>
1.228 gutterid 11845: <td>AMANDA_TMP</td>
1.227 wiz 11846: </tr>
11847: <tr>
11848: <td>AMANDA_USER</td>
1.228 gutterid 11849: <td>AMANDA_VAR</td>
1.223 nia 11850: </tr>
11851: <tr>
1.227 wiz 11852: <td>APACHE_GROUP</td>
1.228 gutterid 11853: <td>APACHE_MODULE_NAME</td>
1.217 rillig 11854: </tr>
11855: <tr>
1.227 wiz 11856: <td>APACHE_MODULE_SRC</td>
1.228 gutterid 11857: <td>APACHE_MODULE_SRCDIR</td>
1.214 leot 11858: </tr>
11859: <tr>
1.227 wiz 11860: <td>APACHE_PKG_PREFIX</td>
1.228 gutterid 11861: <td>APACHE_SUEXEC_CONFIGURE_ARGS</td>
1.212 wiz 11862: </tr>
11863: <tr>
1.227 wiz 11864: <td>APACHE_SUEXEC_DOCROOT</td>
1.228 gutterid 11865: <td>APACHE_USER</td>
1.197 leot 11866: </tr>
11867: <tr>
1.227 wiz 11868: <td>APPEND_ABI</td>
1.228 gutterid 11869: <td>APPEND_ELF</td>
1.177 leot 11870: </tr>
11871: <tr>
1.227 wiz 11872: <td>ARLA_CACHE</td>
1.228 gutterid 11873: <td>AUDIT_PACKAGES_FLAGS</td>
1.161 leot 11874: </tr>
11875: <tr>
1.227 wiz 11876: <td>AUTOCONF_REQD</td>
1.228 gutterid 11877: <td>AUTOMAKE_OVERRIDE</td>
1.159 rillig 11878: </tr>
11879: <tr>
1.227 wiz 11880: <td>AUTOMAKE_REQD</td>
1.228 gutterid 11881: <td>AUTO_MKDIRS</td>
1.156 leot 11882: </tr>
11883: <tr>
1.227 wiz 11884: <td>BDB185_DEFAULT</td>
1.228 gutterid 11885: <td>BDBBASE</td>
1.156 leot 11886: </tr>
11887: <tr>
1.227 wiz 11888: <td>BDB_ACCEPTED</td>
1.228 gutterid 11889: <td>BDB_DEFAULT</td>
1.156 leot 11890: </tr>
11891: <tr>
1.227 wiz 11892: <td>BDB_LIBS</td>
1.228 gutterid 11893: <td>BDB_TYPE</td>
1.156 leot 11894: </tr>
11895: <tr>
1.227 wiz 11896: <td>BINCIMAP_GROUP</td>
1.228 gutterid 11897: <td>BINCIMAP_USER</td>
1.156 leot 11898: </tr>
11899: <tr>
1.227 wiz 11900: <td>BIND_DIR</td>
1.228 gutterid 11901: <td>BIND_GROUP</td>
1.156 leot 11902: </tr>
11903: <tr>
1.227 wiz 11904: <td>BIND_USER</td>
1.228 gutterid 11905: <td>BINOWN</td>
1.156 leot 11906: </tr>
11907: <tr>
1.227 wiz 11908: <td>BINPKG_SITES</td>
1.228 gutterid 11909: <td>BIN_INSTALL_FLAGS</td>
1.156 leot 11910: </tr>
11911: <tr>
1.227 wiz 11912: <td>BISON_PKGDATADIR</td>
1.228 gutterid 11913: <td>BLAS</td>
1.156 leot 11914: </tr>
11915: <tr>
1.227 wiz 11916: <td>BLAS_ACCEPTED</td>
1.228 gutterid 11917: <td>BLAS_C_INTERFACE</td>
1.156 leot 11918: </tr>
11919: <tr>
1.227 wiz 11920: <td>BLAS_INCLUDES</td>
1.228 gutterid 11921: <td>BLAS_INDEX64</td>
1.198 leot 11922: </tr>
11923: <tr>
1.227 wiz 11924: <td>BLAS_LIBS</td>
1.229 gutterid 11925: <td>BLAS_PC</td>
11926: </tr>
11927: <tr>
1.228 gutterid 11928: <td>BLAS_TYPE</td>
1.229 gutterid 11929: <td>BOOTSTRAP_DEPENDS</td>
1.156 leot 11930: </tr>
11931: <tr>
1.228 gutterid 11932: <td>BROKEN</td>
1.229 gutterid 11933: <td>BROKEN_EXCEPT_ON_PLATFORM</td>
1.156 leot 11934: </tr>
11935: <tr>
1.228 gutterid 11936: <td>BROKEN_ON_PLATFORM</td>
1.229 gutterid 11937: <td>BSDSRCDIR</td>
1.189 bacon 11938: </tr>
11939: <tr>
1.228 gutterid 11940: <td>BSDXSRCDIR</td>
1.229 gutterid 11941: <td>BSD_MAKE_ENV</td>
1.205 wiz 11942: </tr>
11943: <tr>
1.228 gutterid 11944: <td>BUILDLINK_AUTO_DIRS</td>
1.229 gutterid 11945: <td>BUILDLINK_AUTO_VARS</td>
1.156 leot 11946: </tr>
11947: <tr>
1.228 gutterid 11948: <td>BUILDLINK_CFLAGS</td>
1.229 gutterid 11949: <td>BUILDLINK_CONTENTS_FILTER</td>
1.177 leot 11950: </tr>
11951: <tr>
1.214 leot 11952: <td>BUILDLINK_CPPFLAGS</td>
1.229 gutterid 11953: <td>BUILDLINK_FILES</td>
1.156 leot 11954: </tr>
11955: <tr>
1.216 gutterid 11956: <td>BUILDLINK_FILES_CMD</td>
1.229 gutterid 11957: <td>BUILDLINK_FNAME_TRANSFORM</td>
1.205 wiz 11958: </tr>
11959: <tr>
1.216 gutterid 11960: <td>BUILDLINK_LDFLAGS</td>
1.229 gutterid 11961: <td>BUILDLINK_LIBS</td>
1.156 leot 11962: </tr>
11963: <tr>
1.216 gutterid 11964: <td>BUILDLINK_OPSYS_SUPPORT_PTHREAD</td>
1.229 gutterid 11965: <td>BUILDLINK_PKGNAME</td>
1.156 leot 11966: </tr>
11967: <tr>
1.216 gutterid 11968: <td>BUILDLINK_PREFIX</td>
1.229 gutterid 11969: <td>BUILDLINK_RPATHDIRS</td>
1.156 leot 11970: </tr>
11971: <tr>
1.216 gutterid 11972: <td>BUILDLINK_TREE</td>
1.229 gutterid 11973: <td>BUILD_DEFS</td>
1.156 leot 11974: </tr>
11975: <tr>
1.216 gutterid 11976: <td>BUILD_DEFS_EFFECTS</td>
1.229 gutterid 11977: <td>BUILD_DEPENDS</td>
1.156 leot 11978: </tr>
11979: <tr>
1.216 gutterid 11980: <td>BUILD_DIRS</td>
1.229 gutterid 11981: <td>BUILD_ENV_SHELL</td>
1.156 leot 11982: </tr>
11983: <tr>
1.216 gutterid 11984: <td>BUILD_MAKE_CMD</td>
1.229 gutterid 11985: <td>BUILD_MAKE_FLAGS</td>
1.156 leot 11986: </tr>
11987: <tr>
1.216 gutterid 11988: <td>BUILD_TARGET</td>
1.229 gutterid 11989: <td>BUILTIN_FIND_FILES</td>
1.156 leot 11990: </tr>
11991: <tr>
1.216 gutterid 11992: <td>BUILTIN_FIND_FILES_VAR</td>
1.229 gutterid 11993: <td>BUILTIN_FIND_GREP</td>
1.156 leot 11994: </tr>
11995: <tr>
1.216 gutterid 11996: <td>BUILTIN_FIND_HEADERS</td>
1.229 gutterid 11997: <td>BUILTIN_FIND_HEADERS_VAR</td>
1.156 leot 11998: </tr>
11999: <tr>
1.216 gutterid 12000: <td>BUILTIN_FIND_PKGCONFIG</td>
1.229 gutterid 12001: <td>BUILTIN_FIND_PKGCONFIG_VAR</td>
1.156 leot 12002: </tr>
12003: <tr>
1.216 gutterid 12004: <td>BUILTIN_PKG</td>
1.229 gutterid 12005: <td>BUILTIN_TEST_CURSES_DEFINES</td>
1.195 gutterid 12006: </tr>
12007: <tr>
1.216 gutterid 12008: <td>BUILTIN_TEST_CURSES_FUNCS</td>
1.229 gutterid 12009: <td>BUILTIN_VERSION_SCRIPT</td>
1.156 leot 12010: </tr>
12011: <tr>
1.216 gutterid 12012: <td>BUILTIN_X11_TYPE</td>
1.229 gutterid 12013: <td>BUILTIN_X11_VERSION</td>
1.156 leot 12014: </tr>
12015: <tr>
1.216 gutterid 12016: <td>CACTI_GROUP</td>
1.229 gutterid 12017: <td>CACTI_USER</td>
1.156 leot 12018: </tr>
12019: <tr>
1.216 gutterid 12020: <td>CANNA_GROUP</td>
1.229 gutterid 12021: <td>CANNA_USER</td>
1.156 leot 12022: </tr>
12023: <tr>
1.216 gutterid 12024: <td>CAT</td>
1.229 gutterid 12025: <td>CBLAS_LIBS</td>
1.156 leot 12026: </tr>
12027: <tr>
1.229 gutterid 12028: <td>CBLAS_PC</td>
1.216 gutterid 12029: <td>CCACHE_BASE</td>
1.156 leot 12030: </tr>
12031: <tr>
1.189 bacon 12032: <td>CCACHE_DIR</td>
1.216 gutterid 12033: <td>CCACHE_LOGFILE</td>
1.156 leot 12034: </tr>
12035: <tr>
1.189 bacon 12036: <td>CC_VERSION</td>
1.216 gutterid 12037: <td>CC_VERSION_STRING</td>
1.156 leot 12038: </tr>
12039: <tr>
1.189 bacon 12040: <td>CDRECORD_CONF</td>
1.216 gutterid 12041: <td>CDROM_PKG_URL_DIR</td>
1.156 leot 12042: </tr>
12043: <tr>
1.189 bacon 12044: <td>CDROM_PKG_URL_HOST</td>
1.226 gutterid 12045: <td>CHANGES</td>
1.223 nia 12046: </tr>
12047: <tr>
1.226 gutterid 12048: <td>CHECK_COMPILER</td>
1.228 gutterid 12049: <td>CHECK_FAKEHOME</td>
1.227 wiz 12050: </tr>
12051: <tr>
12052: <td>CHECK_FILES</td>
1.228 gutterid 12053: <td>CHECK_FILES_SKIP</td>
1.217 rillig 12054: </tr>
12055: <tr>
1.227 wiz 12056: <td>CHECK_FILES_STRICT</td>
1.228 gutterid 12057: <td>CHECK_HEADERS</td>
1.214 leot 12058: </tr>
12059: <tr>
1.227 wiz 12060: <td>CHECK_HEADERS_SKIP</td>
1.228 gutterid 12061: <td>CHECK_INTERPRETER</td>
1.212 wiz 12062: </tr>
12063: <tr>
1.227 wiz 12064: <td>CHECK_INTERPRETER_SKIP</td>
1.228 gutterid 12065: <td>CHECK_PERMS</td>
1.205 wiz 12066: </tr>
12067: <tr>
1.227 wiz 12068: <td>CHECK_PERMS_AUTOFIX</td>
1.228 gutterid 12069: <td>CHECK_PERMS_SKIP</td>
1.197 leot 12070: </tr>
12071: <tr>
1.227 wiz 12072: <td>CHECK_PIE</td>
1.228 gutterid 12073: <td>CHECK_PIE_SKIP</td>
1.177 leot 12074: </tr>
12075: <tr>
1.227 wiz 12076: <td>CHECK_PIE_SUPPORTED</td>
1.228 gutterid 12077: <td>CHECK_PORTABILITY</td>
1.161 leot 12078: </tr>
12079: <tr>
1.227 wiz 12080: <td>CHECK_PORTABILITY_EXPERIMENTAL</td>
1.228 gutterid 12081: <td>CHECK_PORTABILITY_SKIP</td>
1.216 gutterid 12082: </tr>
12083: <tr>
1.227 wiz 12084: <td>CHECK_RELRO</td>
1.228 gutterid 12085: <td>CHECK_RELRO_SKIP</td>
1.159 rillig 12086: </tr>
12087: <tr>
1.227 wiz 12088: <td>CHECK_RELRO_SUPPORTED</td>
1.228 gutterid 12089: <td>CHECK_SHLIBS</td>
1.156 leot 12090: </tr>
12091: <tr>
1.227 wiz 12092: <td>CHECK_SHLIBS_SKIP</td>
1.228 gutterid 12093: <td>CHECK_SHLIBS_SUPPORTED</td>
1.156 leot 12094: </tr>
12095: <tr>
1.227 wiz 12096: <td>CHECK_SHLIBS_TOXIC</td>
1.228 gutterid 12097: <td>CHECK_SSP</td>
1.156 leot 12098: </tr>
12099: <tr>
1.227 wiz 12100: <td>CHECK_SSP_SKIP</td>
1.228 gutterid 12101: <td>CHECK_SSP_SUPPORTED</td>
1.156 leot 12102: </tr>
12103: <tr>
1.227 wiz 12104: <td>CHECK_STRIPPED</td>
1.228 gutterid 12105: <td>CHECK_STRIPPED_SKIP</td>
1.156 leot 12106: </tr>
12107: <tr>
1.227 wiz 12108: <td>CHECK_WRKREF</td>
1.228 gutterid 12109: <td>CHECK_WRKREF_EXTRA_DIRS</td>
1.156 leot 12110: </tr>
12111: <tr>
1.227 wiz 12112: <td>CHECK_WRKREF_SKIP</td>
1.228 gutterid 12113: <td>CLAMAV_DBDIR</td>
1.156 leot 12114: </tr>
12115: <tr>
1.227 wiz 12116: <td>CLAMAV_GROUP</td>
1.228 gutterid 12117: <td>CLAMAV_USER</td>
1.156 leot 12118: </tr>
12119: <tr>
1.227 wiz 12120: <td>CLANGBASE</td>
1.228 gutterid 12121: <td>CLEANDEPENDS</td>
1.156 leot 12122: </tr>
12123: <tr>
1.227 wiz 12124: <td>CMAKE_DEPENDENCIES_REWRITE</td>
1.228 gutterid 12125: <td>CMAKE_INSTALL_NAME_DIR</td>
1.156 leot 12126: </tr>
12127: <tr>
1.227 wiz 12128: <td>CMAKE_INSTALL_PREFIX</td>
1.228 gutterid 12129: <td>CMAKE_MODULE_PATH_OVERRIDE</td>
1.156 leot 12130: </tr>
12131: <tr>
1.227 wiz 12132: <td>CMAKE_PKGSRC_BUILD_FLAGS</td>
1.228 gutterid 12133: <td>CMAKE_PREFIX_PATH</td>
1.156 leot 12134: </tr>
12135: <tr>
1.227 wiz 12136: <td>CMAKE_USE_GNU_INSTALL_DIRS</td>
1.191 bacon 12137: <td>COMPILER_RPATH_FLAG</td>
1.156 leot 12138: </tr>
12139: <tr>
1.226 gutterid 12140: <td>COMPILER_USE_SYMLINKS</td>
1.191 bacon 12141: <td>CONFIGURE_ARGS</td>
1.156 leot 12142: </tr>
12143: <tr>
1.226 gutterid 12144: <td>CONFIGURE_DIRS</td>
1.191 bacon 12145: <td>CONFIGURE_ENV</td>
1.156 leot 12146: </tr>
12147: <tr>
1.226 gutterid 12148: <td>CONFIGURE_ENV_SHELL</td>
1.191 bacon 12149: <td>CONFIGURE_HAS_INFODIR</td>
1.156 leot 12150: </tr>
12151: <tr>
1.226 gutterid 12152: <td>CONFIGURE_HAS_MANDIR</td>
1.191 bacon 12153: <td>CONFIGURE_SCRIPT</td>
1.156 leot 12154: </tr>
12155: <tr>
1.226 gutterid 12156: <td>CONFIG_SHELL</td>
1.191 bacon 12157: <td>CONFIG_SHELL_FLAGS</td>
1.156 leot 12158: </tr>
12159: <tr>
1.226 gutterid 12160: <td>CONF_FILES</td>
1.191 bacon 12161: <td>CONF_FILES_MODE</td>
1.156 leot 12162: </tr>
12163: <tr>
1.226 gutterid 12164: <td>CONF_FILES_PERMS</td>
1.191 bacon 12165: <td>CONSERVER_DEFAULTHOST</td>
1.156 leot 12166: </tr>
12167: <tr>
1.226 gutterid 12168: <td>CONSERVER_DEFAULTPORT</td>
1.191 bacon 12169: <td>CP</td>
1.156 leot 12170: </tr>
12171: <tr>
1.226 gutterid 12172: <td>CPP</td>
1.191 bacon 12173: <td>CPP_PRECOMP_FLAGS</td>
1.156 leot 12174: </tr>
12175: <tr>
1.226 gutterid 12176: <td>CREATE_WRKDIR_SYMLINK</td>
1.191 bacon 12177: <td>CROSSBASE</td>
1.156 leot 12178: </tr>
12179: <tr>
1.226 gutterid 12180: <td>CTFCONVERT</td>
1.191 bacon 12181: <td>CTF_FILES_SKIP</td>
1.156 leot 12182: </tr>
12183: <tr>
1.226 gutterid 12184: <td>CTF_SUPPORTED</td>
1.191 bacon 12185: <td>CTYPE</td>
1.156 leot 12186: </tr>
12187: <tr>
1.226 gutterid 12188: <td>CUPS_GROUP</td>
1.191 bacon 12189: <td>CUPS_SYSTEM_GROUPS</td>
1.156 leot 12190: </tr>
12191: <tr>
1.226 gutterid 12192: <td>CUPS_USER</td>
1.191 bacon 12193: <td>CURSES_DEFAULT</td>
1.177 leot 12194: </tr>
12195: <tr>
1.226 gutterid 12196: <td>CURSES_TYPE</td>
1.228 gutterid 12197: <td>CXX</td>
1.227 wiz 12198: </tr>
12199: <tr>
12200: <td>CYRUS_GROUP</td>
1.228 gutterid 12201: <td>CYRUS_IDLE</td>
1.217 rillig 12202: </tr>
12203: <tr>
1.227 wiz 12204: <td>CYRUS_USER</td>
1.228 gutterid 12205: <td>DAEMONTOOLS_GROUP</td>
1.214 leot 12206: </tr>
12207: <tr>
1.227 wiz 12208: <td>DAEMONTOOLS_LOG_USER</td>
1.228 gutterid 12209: <td>DARWIN_NO_SYSTEM_LIBS</td>
1.212 wiz 12210: </tr>
12211: <tr>
1.227 wiz 12212: <td>DARWIN_REQUIRES_FILTER</td>
1.228 gutterid 12213: <td>DBUS_GROUP</td>
1.205 wiz 12214: </tr>
12215: <tr>
1.227 wiz 12216: <td>DBUS_USER</td>
1.228 gutterid 12217: <td>DEFANG_GROUP</td>
1.197 leot 12218: </tr>
12219: <tr>
1.227 wiz 12220: <td>DEFANG_USER</td>
1.228 gutterid 12221: <td>DEFAULT_ACCEPTABLE_LICENSES</td>
1.159 rillig 12222: </tr>
12223: <tr>
1.227 wiz 12224: <td>DEFAULT_DISTFILES</td>
1.228 gutterid 12225: <td>DEFAULT_IRC_SERVER</td>
1.156 leot 12226: </tr>
12227: <tr>
1.227 wiz 12228: <td>DEFAULT_SERIAL_DEVICE</td>
1.228 gutterid 12229: <td>DEF_UMASK</td>
1.156 leot 12230: </tr>
12231: <tr>
1.227 wiz 12232: <td>DEINSTALLDEPENDS</td>
1.228 gutterid 12233: <td>DEINSTALL_SRC</td>
1.195 gutterid 12234: </tr>
12235: <tr>
1.227 wiz 12236: <td>DEINSTALL_TEMPLATES</td>
1.228 gutterid 12237: <td>DELAYED_ERROR_MSG</td>
1.156 leot 12238: </tr>
12239: <tr>
1.227 wiz 12240: <td>DELAYED_WARNING_MSG</td>
1.228 gutterid 12241: <td>DEPENDS</td>
1.156 leot 12242: </tr>
12243: <tr>
1.227 wiz 12244: <td>DEPENDS_TARGET</td>
1.228 gutterid 12245: <td>DEPENDS_TYPE</td>
1.156 leot 12246: </tr>
12247: <tr>
1.227 wiz 12248: <td>DESTDIR</td>
1.228 gutterid 12249: <td>DESTDIR_VARNAME</td>
1.156 leot 12250: </tr>
12251: <tr>
1.227 wiz 12252: <td>DIALER_GROUP</td>
1.228 gutterid 12253: <td>DIGEST_REQD</td>
1.156 leot 12254: </tr>
12255: <tr>
1.227 wiz 12256: <td>DISTDIR</td>
1.228 gutterid 12257: <td>DISTFILES</td>
1.156 leot 12258: </tr>
12259: <tr>
1.227 wiz 12260: <td>DISTINFO_FILE</td>
1.228 gutterid 12261: <td>DISTNAME</td>
1.156 leot 12262: </tr>
12263: <tr>
1.227 wiz 12264: <td>DIST_PATH</td>
1.228 gutterid 12265: <td>DIST_SUBDIR</td>
1.156 leot 12266: </tr>
12267: <tr>
1.227 wiz 12268: <td>DJBDNS_AXFR_USER</td>
1.228 gutterid 12269: <td>DJBDNS_CACHE_USER</td>
1.156 leot 12270: </tr>
12271: <tr>
1.227 wiz 12272: <td>DJBDNS_DJBDNS_GROUP</td>
1.228 gutterid 12273: <td>DJBDNS_LOG_USER</td>
1.156 leot 12274: </tr>
12275: <tr>
1.227 wiz 12276: <td>DJBDNS_RBL_USER</td>
1.228 gutterid 12277: <td>DJBDNS_TINY_USER</td>
1.156 leot 12278: </tr>
12279: <tr>
1.227 wiz 12280: <td>DLOPEN_REQUIRE_PTHREADS</td>
1.228 gutterid 12281: <td>DL_AUTO_VARS</td>
1.156 leot 12282: </tr>
12283: <tr>
1.227 wiz 12284: <td>DL_CFLAGS</td>
1.228 gutterid 12285: <td>DL_LDFLAGS</td>
1.156 leot 12286: </tr>
12287: <tr>
1.227 wiz 12288: <td>DL_LIBS</td>
1.228 gutterid 12289: <td>DNS</td>
1.156 leot 12290: </tr>
12291: <tr>
1.227 wiz 12292: <td>DOCOWN</td>
1.228 gutterid 12293: <td>DOWNLOADED_DISTFILE</td>
1.156 leot 12294: </tr>
12295: <tr>
1.227 wiz 12296: <td>DQCACHE_GROUP</td>
1.228 gutterid 12297: <td>DQCACHE_USER</td>
1.156 leot 12298: </tr>
12299: <tr>
1.227 wiz 12300: <td>DT_LAYOUT</td>
1.228 gutterid 12301: <td>DYNAMIC_SITES_CMD</td>
1.218 nia 12302: </tr>
12303: <tr>
1.227 wiz 12304: <td>DYNAMIC_SITES_SCRIPT</td>
1.228 gutterid 12305: <td>ECHO</td>
1.156 leot 12306: </tr>
12307: <tr>
1.227 wiz 12308: <td>ECHO_N</td>
1.228 gutterid 12309: <td>ELK_GUI</td>
1.156 leot 12310: </tr>
12311: <tr>
1.227 wiz 12312: <td>EMACS_TYPE</td>
1.228 gutterid 12313: <td>EMULDIR</td>
1.156 leot 12314: </tr>
12315: <tr>
1.227 wiz 12316: <td>EMULSUBDIR</td>
1.228 gutterid 12317: <td>EMULSUBDIRSLASH</td>
1.156 leot 12318: </tr>
12319: <tr>
1.227 wiz 12320: <td>EMUL_ARCH</td>
1.228 gutterid 12321: <td>EMUL_DISTRO</td>
1.156 leot 12322: </tr>
12323: <tr>
1.227 wiz 12324: <td>EMUL_EXEC_FMT</td>
1.228 gutterid 12325: <td>EMUL_IS_NATIVE</td>
1.156 leot 12326: </tr>
12327: <tr>
1.227 wiz 12328: <td>EMUL_MODULES</td>
1.228 gutterid 12329: <td>EMUL_OPSYS</td>
1.156 leot 12330: </tr>
12331: <tr>
1.227 wiz 12332: <td>EMUL_PKG_FMT</td>
1.228 gutterid 12333: <td>EMUL_PLATFORM</td>
1.156 leot 12334: </tr>
12335: <tr>
1.227 wiz 12336: <td>EMUL_PLATFORMS</td>
1.228 gutterid 12337: <td>EMUL_PREFER</td>
1.156 leot 12338: </tr>
12339: <tr>
1.227 wiz 12340: <td>EMUL_REQD</td>
1.228 gutterid 12341: <td>EMUL_TYPE</td>
1.156 leot 12342: </tr>
12343: <tr>
1.227 wiz 12344: <td>ERROR_MSG</td>
1.228 gutterid 12345: <td>EXIM_GROUP</td>
1.156 leot 12346: </tr>
12347: <tr>
1.227 wiz 12348: <td>EXIM_USER</td>
1.228 gutterid 12349: <td>EXPORT_SYMBOLS_LDFLAGS</td>
1.156 leot 12350: </tr>
12351: <tr>
1.227 wiz 12352: <td>EXTRACTOR</td>
1.228 gutterid 12353: <td>EXTRACT_CMD</td>
1.156 leot 12354: </tr>
12355: <tr>
1.227 wiz 12356: <td>EXTRACT_CMD_DEFAULT</td>
1.228 gutterid 12357: <td>EXTRACT_DIR</td>
1.223 nia 12358: </tr>
12359: <tr>
1.227 wiz 12360: <td>EXTRACT_ELEMENTS</td>
1.228 gutterid 12361: <td>EXTRACT_ENV</td>
1.156 leot 12362: </tr>
12363: <tr>
1.227 wiz 12364: <td>EXTRACT_ONLY</td>
1.228 gutterid 12365: <td>EXTRACT_OPTS</td>
1.156 leot 12366: </tr>
12367: <tr>
1.227 wiz 12368: <td>EXTRACT_SUFX</td>
1.228 gutterid 12369: <td>EXTRACT_USING</td>
1.156 leot 12370: </tr>
12371: <tr>
1.227 wiz 12372: <td>FAIL</td>
1.228 gutterid 12373: <td>FAILOVER_FETCH</td>
1.156 leot 12374: </tr>
12375: <tr>
1.227 wiz 12376: <td>FAIL_MSG</td>
1.228 gutterid 12377: <td>FAKE_NCURSES</td>
1.156 leot 12378: </tr>
12379: <tr>
1.227 wiz 12380: <td>FAM</td>
1.228 gutterid 12381: <td>FAM_ACCEPTED</td>
1.156 leot 12382: </tr>
12383: <tr>
1.227 wiz 12384: <td>FAM_DEFAULT</td>
1.228 gutterid 12385: <td>FAM_SERVER</td>
1.156 leot 12386: </tr>
12387: <tr>
1.227 wiz 12388: <td>FCPATH</td>
1.228 gutterid 12389: <td>FEATURE_CPPFLAGS</td>
1.156 leot 12390: </tr>
12391: <tr>
1.227 wiz 12392: <td>FEATURE_LDFLAGS</td>
1.228 gutterid 12393: <td>FEATURE_LIBS</td>
1.156 leot 12394: </tr>
12395: <tr>
1.227 wiz 12396: <td>FETCH_AFTER_ARGS</td>
1.228 gutterid 12397: <td>FETCH_BEFORE_ARGS</td>
1.177 leot 12398: </tr>
12399: <tr>
1.227 wiz 12400: <td>FETCH_CMD</td>
1.228 gutterid 12401: <td>FETCH_OUTPUT_ARGS</td>
1.156 leot 12402: </tr>
12403: <tr>
1.227 wiz 12404: <td>FETCH_PROXY</td>
1.228 gutterid 12405: <td>FETCH_RESUME_ARGS</td>
1.156 leot 12406: </tr>
12407: <tr>
1.227 wiz 12408: <td>FETCH_TIMEOUT</td>
1.228 gutterid 12409: <td>FETCH_USE_IPV4_ONLY</td>
1.156 leot 12410: </tr>
12411: <tr>
1.227 wiz 12412: <td>FETCH_USING</td>
1.228 gutterid 12413: <td>FILES_SUBST</td>
1.156 leot 12414: </tr>
12415: <tr>
1.227 wiz 12416: <td>FILES_SUBST_SED</td>
1.223 nia 12417: <td>FIX_SYSTEM_HEADERS</td>
1.161 leot 12418: </tr>
12419: <tr>
1.226 gutterid 12420: <td>FONTS_DIRS</td>
1.191 bacon 12421: <td>FONTS_VERBOSE</td>
1.177 leot 12422: </tr>
12423: <tr>
1.226 gutterid 12424: <td>FOO_HACKS_MK</td>
1.191 bacon 12425: <td>FOX_USE_XUNICODE</td>
1.156 leot 12426: </tr>
12427: <tr>
1.226 gutterid 12428: <td>FREEWNN_GROUP</td>
1.191 bacon 12429: <td>FREEWNN_USER</td>
1.156 leot 12430: </tr>
12431: <tr>
1.226 gutterid 12432: <td>FTP_PKG_URL_DIR</td>
1.191 bacon 12433: <td>FTP_PKG_URL_HOST</td>
1.156 leot 12434: </tr>
12435: <tr>
1.226 gutterid 12436: <td>GAMEDATAMODE</td>
1.191 bacon 12437: <td>GAMEDATA_PERMS</td>
1.156 leot 12438: </tr>
12439: <tr>
1.226 gutterid 12440: <td>GAMEDIRMODE</td>
1.191 bacon 12441: <td>GAMEDIR_PERMS</td>
1.156 leot 12442: </tr>
12443: <tr>
1.226 gutterid 12444: <td>GAMEGRP</td>
1.191 bacon 12445: <td>GAMEMODE</td>
1.156 leot 12446: </tr>
12447: <tr>
1.226 gutterid 12448: <td>GAMEOWN</td>
1.191 bacon 12449: <td>GAMES_GROUP</td>
1.156 leot 12450: </tr>
12451: <tr>
1.226 gutterid 12452: <td>GAMES_USER</td>
1.191 bacon 12453: <td>GCC</td>
1.156 leot 12454: </tr>
12455: <tr>
1.226 gutterid 12456: <td>GCCBASE</td>
1.191 bacon 12457: <td>GCC_REQD</td>
1.156 leot 12458: </tr>
12459: <tr>
1.226 gutterid 12460: <td>GCC_VERSION_SUFFIX</td>
1.191 bacon 12461: <td>GEM_BUILD</td>
1.156 leot 12462: </tr>
12463: <tr>
1.226 gutterid 12464: <td>GEM_CLEANBUILD</td>
1.191 bacon 12465: <td>GEM_CLEANBUILD_EXTENSIONS</td>
1.156 leot 12466: </tr>
12467: <tr>
1.226 gutterid 12468: <td>GEM_DOCDIR</td>
1.191 bacon 12469: <td>GEM_EXTSDIR</td>
1.177 leot 12470: </tr>
12471: <tr>
1.226 gutterid 12472: <td>GEM_HOME</td>
1.191 bacon 12473: <td>GEM_KEEPBUILD</td>
1.156 leot 12474: </tr>
12475: <tr>
1.226 gutterid 12476: <td>GEM_LIBDIR</td>
1.191 bacon 12477: <td>GEM_NAME</td>
1.156 leot 12478: </tr>
12479: <tr>
1.226 gutterid 12480: <td>GEM_PATH</td>
1.198 leot 12481: <td>GEM_PLUGINSDIR</td>
12482: </tr>
12483: <tr>
1.226 gutterid 12484: <td>GEM_SPECFILE</td>
1.180 rillig 12485: <td>GENERATE_PLIST</td>
1.156 leot 12486: </tr>
12487: <tr>
1.226 gutterid 12488: <td>GHC</td>
1.201 cirnatda 12489: <td>GHOSTSCRIPT_REQD</td>
1.156 leot 12490: </tr>
12491: <tr>
1.226 gutterid 12492: <td>GITHUB_PROJECT</td>
1.201 cirnatda 12493: <td>GITHUB_RELEASE</td>
1.177 leot 12494: </tr>
12495: <tr>
1.226 gutterid 12496: <td>GITHUB_SUBMODULES</td>
1.201 cirnatda 12497: <td>GITHUB_TAG</td>
1.159 rillig 12498: </tr>
12499: <tr>
1.226 gutterid 12500: <td>GITHUB_TYPE</td>
1.223 nia 12501: <td>GITLAB_PROJECT</td>
12502: </tr>
12503: <tr>
1.226 gutterid 12504: <td>GITLAB_RELEASE</td>
1.225 gutterid 12505: <td>GITLAB_SUBMODULES</td>
1.223 nia 12506: </tr>
12507: <tr>
1.226 gutterid 12508: <td>GITLAB_TAG</td>
1.225 gutterid 12509: <td>GITLAB_TYPE</td>
1.223 nia 12510: </tr>
12511: <tr>
1.226 gutterid 12512: <td>GNU</td>
1.228 gutterid 12513: <td>GNU_CONFIGURE</td>
1.227 wiz 12514: </tr>
12515: <tr>
12516: <td>GNU_CONFIGURE_INFODIR</td>
1.228 gutterid 12517: <td>GNU_CONFIGURE_MANDIR</td>
1.156 leot 12518: </tr>
12519: <tr>
1.227 wiz 12520: <td>GNU_CONFIGURE_QUIET</td>
1.228 gutterid 12521: <td>GNU_CONFIGURE_STRICT</td>
1.156 leot 12522: </tr>
12523: <tr>
1.227 wiz 12524: <td>GODEP_REDIRECTS</td>
1.228 gutterid 12525: <td>GO_BUILD_PATTERN</td>
1.156 leot 12526: </tr>
12527: <tr>
1.227 wiz 12528: <td>GO_DEPS</td>
1.228 gutterid 12529: <td>GO_DIST_BASE</td>
1.156 leot 12530: </tr>
12531: <tr>
1.227 wiz 12532: <td>GO_EXTRA_MOD_DIRS</td>
1.228 gutterid 12533: <td>GO_MODULE_FILES</td>
1.156 leot 12534: </tr>
12535: <tr>
1.227 wiz 12536: <td>GO_SRCPATH</td>
1.229 gutterid 12537: <td>GROUP_SPECIFIC_PKGS</td>
1.156 leot 12538: </tr>
12539: <tr>
1.228 gutterid 12540: <td>GRUB_NETWORK_CARDS</td>
1.229 gutterid 12541: <td>GRUB_PRESET_COMMAND</td>
1.156 leot 12542: </tr>
12543: <tr>
1.228 gutterid 12544: <td>GRUB_SCAN_ARGS</td>
1.229 gutterid 12545: <td>GZIP</td>
1.156 leot 12546: </tr>
12547: <tr>
1.222 gutterid 12548: <td>HASKELL_ENABLE_DYNAMIC_EXECUTABLE</td>
1.229 gutterid 12549: <td>HASKELL_ENABLE_HADDOCK_DOCUMENTATION</td>
1.217 rillig 12550: </tr>
12551: <tr>
1.222 gutterid 12552: <td>HASKELL_ENABLE_LIBRARY_PROFILING</td>
1.229 gutterid 12553: <td>HASKELL_ENABLE_SHARED_LIBRARY</td>
1.226 gutterid 12554: </tr>
12555: <tr>
12556: <td>HASKELL_OPTIMIZATION_LEVEL</td>
1.229 gutterid 12557: <td>HASKELL_PKG_NAME</td>
1.220 nia 12558: </tr>
12559: <tr>
1.229 gutterid 12560: <td>HASKELL_UNRESTRICT_DEPENDENCIES</td>
1.223 nia 12561: <td>HAS_CONFIGURE</td>
1.229 gutterid 12562: </tr>
12563: <tr>
1.226 gutterid 12564: <td>HEADER_TEMPLATES</td>
1.229 gutterid 12565: <td>HOMEPAGE</td>
1.214 leot 12566: </tr>
12567: <tr>
1.228 gutterid 12568: <td>HOST_PKGTOOLS_ARGS</td>
1.229 gutterid 12569: <td>HOST_SPECIFIC_PKGS</td>
1.227 wiz 12570: </tr>
12571: <tr>
1.228 gutterid 12572: <td>HOWL_GROUP</td>
1.229 gutterid 12573: <td>HOWL_USER</td>
1.223 nia 12574: </tr>
12575: <tr>
1.228 gutterid 12576: <td>ICCBASE</td>
1.229 gutterid 12577: <td>ICECAST_CHROOTDIR</td>
1.156 leot 12578: </tr>
12579: <tr>
1.228 gutterid 12580: <td>ICON_THEMES</td>
1.229 gutterid 12581: <td>IDOBASE</td>
1.156 leot 12582: </tr>
12583: <tr>
1.228 gutterid 12584: <td>IGNORE_CCACHE</td>
1.229 gutterid 12585: <td>IGNORE_INFO_DIRS</td>
1.191 bacon 12586: </tr>
12587: <tr>
1.228 gutterid 12588: <td>IGNORE_INTERACTIVE_FETCH</td>
1.229 gutterid 12589: <td>IMAKE</td>
1.156 leot 12590: </tr>
12591: <tr>
1.228 gutterid 12592: <td>IMAKEOPTS</td>
1.229 gutterid 12593: <td>IMAKE_MAKE</td>
1.156 leot 12594: </tr>
12595: <tr>
1.228 gutterid 12596: <td>IMAKE_MANINSTALL</td>
1.229 gutterid 12597: <td>IMAP_UW_CCLIENT_MBOX_FMT</td>
1.156 leot 12598: </tr>
12599: <tr>
1.228 gutterid 12600: <td>IMDICTDIR</td>
1.229 gutterid 12601: <td>INCOMPAT_CURSES</td>
1.156 leot 12602: </tr>
12603: <tr>
1.228 gutterid 12604: <td>INFO_DIR</td>
1.229 gutterid 12605: <td>INFO_FILES</td>
1.156 leot 12606: </tr>
12607: <tr>
1.228 gutterid 12608: <td>INFO_FILES_VERBOSE</td>
1.229 gutterid 12609: <td>INFO_MSG</td>
1.156 leot 12610: </tr>
12611: <tr>
1.228 gutterid 12612: <td>INIT_SYSTEM</td>
1.229 gutterid 12613: <td>INN_DATA_DIR</td>
1.156 leot 12614: </tr>
12615: <tr>
1.228 gutterid 12616: <td>INN_GROUP</td>
1.229 gutterid 12617: <td>INN_USER</td>
1.156 leot 12618: </tr>
12619: <tr>
1.228 gutterid 12620: <td>INSTALLATION_DIRS</td>
1.229 gutterid 12621: <td>INSTALLATION_DIRS_FROM_PLIST</td>
1.156 leot 12622: </tr>
12623: <tr>
1.228 gutterid 12624: <td>INSTALL_ENV</td>
1.229 gutterid 12625: <td>INSTALL_SH_OVERRIDE</td>
1.172 rillig 12626: </tr>
12627: <tr>
1.228 gutterid 12628: <td>INSTALL_SRC</td>
1.229 gutterid 12629: <td>INSTALL_TEMPLATES</td>
1.156 leot 12630: </tr>
12631: <tr>
1.228 gutterid 12632: <td>INSTALL_UNSTRIPPED</td>
1.229 gutterid 12633: <td>IRCD_HYBRID_IRC_GROUP</td>
1.156 leot 12634: </tr>
12635: <tr>
1.228 gutterid 12636: <td>IRCD_HYBRID_IRC_USER</td>
1.229 gutterid 12637: <td>IRCD_HYBRID_MAXCONN</td>
1.156 leot 12638: </tr>
12639: <tr>
1.228 gutterid 12640: <td>IRCD_HYBRID_NICLEN</td>
1.229 gutterid 12641: <td>IRCD_HYBRID_SYSLOG_EVENTS</td>
1.156 leot 12642: </tr>
12643: <tr>
1.228 gutterid 12644: <td>IRCD_HYBRID_SYSLOG_FACILITY</td>
1.229 gutterid 12645: <td>IRCD_HYBRID_TOPICLEN</td>
1.156 leot 12646: </tr>
12647: <tr>
1.228 gutterid 12648: <td>IRIX</td>
1.229 gutterid 12649: <td>IRRD_USE_PGP</td>
1.156 leot 12650: </tr>
12651: <tr>
1.228 gutterid 12652: <td>JABBERD_GROUP</td>
1.229 gutterid 12653: <td>JABBERD_LOGDIR</td>
1.156 leot 12654: </tr>
12655: <tr>
1.228 gutterid 12656: <td>JABBERD_PIDDIR</td>
1.229 gutterid 12657: <td>JABBERD_SPOOLDIR</td>
1.156 leot 12658: </tr>
12659: <tr>
1.226 gutterid 12660: <td>JABBERD_USER</td>
1.229 gutterid 12661: <td>JAVA_BINPREFIX</td>
1.156 leot 12662: </tr>
12663: <tr>
1.228 gutterid 12664: <td>JAVA_CLASSPATH</td>
1.229 gutterid 12665: <td>JAVA_HOME</td>
1.227 wiz 12666: </tr>
12667: <tr>
1.228 gutterid 12668: <td>JAVA_LD_LIBRARY_PATH</td>
1.229 gutterid 12669: <td>JAVA_NAME</td>
1.177 leot 12670: </tr>
12671: <tr>
1.228 gutterid 12672: <td>JAVA_UNLIMIT</td>
1.229 gutterid 12673: <td>JAVA_WRAPPERS</td>
1.156 leot 12674: </tr>
12675: <tr>
1.228 gutterid 12676: <td>JPEG_ACCEPTED</td>
1.229 gutterid 12677: <td>JPEG_DEFAULT</td>
1.217 rillig 12678: </tr>
12679: <tr>
1.228 gutterid 12680: <td>KERBEROS</td>
1.229 gutterid 12681: <td>KERMIT_SUID_UUCP</td>
1.217 rillig 12682: </tr>
12683: <tr>
1.228 gutterid 12684: <td>KJS_USE_PCRE</td>
1.229 gutterid 12685: <td>KNEWS_DOMAIN_FILE</td>
1.156 leot 12686: </tr>
12687: <tr>
1.228 gutterid 12688: <td>KNEWS_DOMAIN_NAME</td>
1.229 gutterid 12689: <td>KRB5_ACCEPTED</td>
1.156 leot 12690: </tr>
12691: <tr>
1.228 gutterid 12692: <td>KRB5_DEFAULT</td>
1.229 gutterid 12693: <td>LANGUAGES</td>
1.156 leot 12694: </tr>
12695: <tr>
1.228 gutterid 12696: <td>LAPACKE_LIBS</td>
1.229 gutterid 12697: <td>LAPACKE_PC</td>
1.156 leot 12698: </tr>
12699: <tr>
1.227 wiz 12700: <td>LAPACK_LIBS</td>
1.229 gutterid 12701: <td>LAPACK_PC</td>
1.156 leot 12702: </tr>
12703: <tr>
1.229 gutterid 12704: <td>LATEX2HTML_ICONPATH</td>
1.227 wiz 12705: <td>LDCONFIG_ADD_CMD</td>
1.177 leot 12706: </tr>
12707: <tr>
1.229 gutterid 12708: <td>LDCONFIG_REMOVE_CMD</td>
1.227 wiz 12709: <td>LDD</td>
1.156 leot 12710: </tr>
12711: <tr>
1.229 gutterid 12712: <td>LEAFNODE_DATA_DIR</td>
1.227 wiz 12713: <td>LEAFNODE_GROUP</td>
1.156 leot 12714: </tr>
12715: <tr>
1.229 gutterid 12716: <td>LEAFNODE_USER</td>
1.227 wiz 12717: <td>LIBDVDCSS_HOMEPAGE</td>
1.156 leot 12718: </tr>
12719: <tr>
1.229 gutterid 12720: <td>LIBDVDCSS_MASTER_SITES</td>
1.227 wiz 12721: <td>LIBRSVG_TYPE</td>
1.156 leot 12722: </tr>
12723: <tr>
1.229 gutterid 12724: <td>LIBTOOL</td>
1.227 wiz 12725: <td>LIBTOOLIZE_PLIST</td>
1.205 wiz 12726: </tr>
12727: <tr>
1.229 gutterid 12728: <td>LIBTOOL_M4_OVERRIDE</td>
1.227 wiz 12729: <td>LIBUSB_TYPE</td>
1.157 leot 12730: </tr>
12731: <tr>
1.229 gutterid 12732: <td>LICENSE</td>
1.227 wiz 12733: <td>LINKER_RPATH_FLAG</td>
1.156 leot 12734: </tr>
12735: <tr>
1.229 gutterid 12736: <td>LINK_RPATH_FLAG</td>
1.220 nia 12737: <td>LINUX_LOCALES</td>
1.223 nia 12738: </tr>
12739: <tr>
1.229 gutterid 12740: <td>LOCALBASE</td>
1.223 nia 12741: <td>LOCALBASE_LOCKTYPE</td>
1.177 leot 12742: </tr>
12743: <tr>
1.229 gutterid 12744: <td>LOCALPATCHES</td>
1.223 nia 12745: <td>LOVE_DATA</td>
1.214 leot 12746: </tr>
12747: <tr>
1.229 gutterid 12748: <td>LOVE_GAME</td>
1.223 nia 12749: <td>LOVE_VERSION</td>
1.197 leot 12750: </tr>
12751: <tr>
1.229 gutterid 12752: <td>LP32PLATFORMS</td>
1.223 nia 12753: <td>LP64PLATFORMS</td>
1.156 leot 12754: </tr>
12755: <tr>
1.229 gutterid 12756: <td>LUA_BUSTED_ARGS</td>
1.223 nia 12757: <td>LUA_CDIR</td>
1.156 leot 12758: </tr>
12759: <tr>
1.229 gutterid 12760: <td>LUA_COMPILER</td>
1.223 nia 12761: <td>LUA_DOCDIR</td>
1.221 nia 12762: </tr>
12763: <tr>
1.229 gutterid 12764: <td>LUA_EXAMPLESDIR</td>
1.223 nia 12765: <td>LUA_INCDIR</td>
1.218 nia 12766: </tr>
12767: <tr>
1.229 gutterid 12768: <td>LUA_INTERPRETER</td>
1.223 nia 12769: <td>LUA_LDIR</td>
1.218 nia 12770: </tr>
12771: <tr>
1.229 gutterid 12772: <td>LUA_LINKER_MAGIC</td>
1.223 nia 12773: <td>LUA_PKGPREFIX</td>
1.218 nia 12774: </tr>
12775: <tr>
1.229 gutterid 12776: <td>LUA_SELF_CONFLICT</td>
1.223 nia 12777: <td>LUA_USE_BUSTED</td>
1.218 nia 12778: </tr>
12779: <tr>
1.229 gutterid 12780: <td>LUA_VERSIONS_ACCEPTED</td>
1.223 nia 12781: <td>LUA_VERSIONS_INCOMPATIBLE</td>
1.218 nia 12782: </tr>
12783: <tr>
1.229 gutterid 12784: <td>LUA_VERSION_DEFAULT</td>
1.223 nia 12785: <td>LUA_VERSION_REQD</td>
1.218 nia 12786: </tr>
12787: <tr>
1.229 gutterid 12788: <td>Lua</td>
1.223 nia 12789: <td>MACHINE_PLATFORM</td>
1.218 nia 12790: </tr>
12791: <tr>
1.229 gutterid 12792: <td>MAILAGENT_DOMAIN</td>
1.223 nia 12793: <td>MAILAGENT_EMAIL</td>
1.156 leot 12794: </tr>
12795: <tr>
1.229 gutterid 12796: <td>MAILAGENT_FQDN</td>
1.223 nia 12797: <td>MAILAGENT_ORGANIZATION</td>
1.205 wiz 12798: </tr>
12799: <tr>
1.229 gutterid 12800: <td>MAJORDOMO_HOMEDIR</td>
1.225 gutterid 12801: <td>MAKEINFO_ARGS</td>
1.227 wiz 12802: </tr>
12803: <tr>
1.229 gutterid 12804: <td>MAKE_DIRS</td>
1.227 wiz 12805: <td>MAKE_DIRS_PERMS</td>
1.156 leot 12806: </tr>
12807: <tr>
1.229 gutterid 12808: <td>MAKE_ENV</td>
1.227 wiz 12809: <td>MAKE_FILE</td>
1.212 wiz 12810: </tr>
12811: <tr>
1.229 gutterid 12812: <td>MAKE_FLAGS</td>
1.227 wiz 12813: <td>MAKE_JOBS</td>
1.156 leot 12814: </tr>
12815: <tr>
1.229 gutterid 12816: <td>MAKE_JOBS_SAFE</td>
1.227 wiz 12817: <td>MAKE_PROGRAM</td>
1.156 leot 12818: </tr>
12819: <tr>
1.229 gutterid 12820: <td>MANCOMPRESSED_IF_MANZ</td>
1.227 wiz 12821: <td>MANINSTALL</td>
1.156 leot 12822: </tr>
12823: <tr>
1.229 gutterid 12824: <td>MANZ</td>
1.227 wiz 12825: <td>MASTER_SITES</td>
1.156 leot 12826: </tr>
12827: <tr>
1.229 gutterid 12828: <td>MASTER_SITE_BACKUP</td>
1.227 wiz 12829: <td>MASTER_SITE_LOCAL</td>
1.189 bacon 12830: </tr>
12831: <tr>
1.229 gutterid 12832: <td>MASTER_SITE_MOZILLA</td>
1.227 wiz 12833: <td>MASTER_SITE_OVERRIDE</td>
1.156 leot 12834: </tr>
12835: <tr>
1.229 gutterid 12836: <td>MASTER_SITE_PERL_CPAN</td>
1.227 wiz 12837: <td>MASTER_SORT</td>
1.156 leot 12838: </tr>
12839: <tr>
1.229 gutterid 12840: <td>MASTER_SORT_RANDOM</td>
1.227 wiz 12841: <td>MASTER_SORT_REGEX</td>
1.156 leot 12842: </tr>
12843: <tr>
1.229 gutterid 12844: <td>MECAB_CHARSET</td>
1.227 wiz 12845: <td>MEDIATOMB_GROUP</td>
1.156 leot 12846: </tr>
12847: <tr>
1.229 gutterid 12848: <td>MEDIATOMB_USER</td>
1.227 wiz 12849: <td>MIPSPROBASE</td>
1.156 leot 12850: </tr>
12851: <tr>
1.229 gutterid 12852: <td>MIREDO_GROUP</td>
1.227 wiz 12853: <td>MIREDO_USER</td>
1.156 leot 12854: </tr>
12855: <tr>
1.229 gutterid 12856: <td>MISSING_FEATURES</td>
1.227 wiz 12857: <td>MKDIR</td>
1.156 leot 12858: </tr>
12859: <tr>
1.229 gutterid 12860: <td>MKPIE_SUPPORTED</td>
1.227 wiz 12861: <td>MLDONKEY_GROUP</td>
1.156 leot 12862: </tr>
12863: <tr>
1.229 gutterid 12864: <td>MLDONKEY_HOME</td>
1.227 wiz 12865: <td>MLDONKEY_USER</td>
1.156 leot 12866: </tr>
12867: <tr>
1.229 gutterid 12868: <td>MONOTONE_GROUP</td>
1.227 wiz 12869: <td>MONOTONE_USER</td>
1.207 leot 12870: </tr>
12871: <tr>
1.229 gutterid 12872: <td>MOTIFBASE</td>
1.227 wiz 12873: <td>MOTIF_TYPE</td>
1.156 leot 12874: </tr>
12875: <tr>
1.229 gutterid 12876: <td>MOTIF_TYPE_DEFAULT</td>
1.227 wiz 12877: <td>MPI_TYPE</td>
1.156 leot 12878: </tr>
12879: <tr>
1.229 gutterid 12880: <td>MSGFMT_STRIP_MSGCTXT</td>
1.227 wiz 12881: <td>MSGFMT_STRIP_MSGID_PLURAL</td>
1.156 leot 12882: </tr>
12883: <tr>
1.229 gutterid 12884: <td>MTOOLS_ENABLE_FLOPPYD</td>
1.221 nia 12885: <td>MV</td>
1.223 nia 12886: </tr>
12887: <tr>
1.229 gutterid 12888: <td>MYSQL_CHARSET</td>
1.223 nia 12889: <td>MYSQL_DATADIR</td>
1.214 leot 12890: </tr>
12891: <tr>
1.229 gutterid 12892: <td>MYSQL_EXTRA_CHARSET</td>
1.223 nia 12893: <td>MYSQL_GROUP</td>
1.197 leot 12894: </tr>
12895: <tr>
1.229 gutterid 12896: <td>MYSQL_USER</td>
1.223 nia 12897: <td>MYSQL_VERSION</td>
1.205 wiz 12898: </tr>
12899: <tr>
1.229 gutterid 12900: <td>MYSQL_VERSIONS_ACCEPTED</td>
1.223 nia 12901: <td>MYSQL_VERSIONS_ALL</td>
1.156 leot 12902: </tr>
12903: <tr>
1.229 gutterid 12904: <td>MYSQL_VERSION_DEFAULT</td>
1.223 nia 12905: <td>NAGIOSCMD_GROUP</td>
1.156 leot 12906: </tr>
12907: <tr>
1.229 gutterid 12908: <td>NAGIOSDIR</td>
1.223 nia 12909: <td>NAGIOS_GROUP</td>
1.156 leot 12910: </tr>
12911: <tr>
1.229 gutterid 12912: <td>NAGIOS_USER</td>
1.223 nia 12913: <td>NATIVE_APPEND_ABI</td>
1.156 leot 12914: </tr>
12915: <tr>
1.229 gutterid 12916: <td>NATIVE_APPEND_ELF</td>
1.223 nia 12917: <td>NATIVE_EXEC_FMT</td>
1.195 gutterid 12918: </tr>
12919: <tr>
1.229 gutterid 12920: <td>NATIVE_MACHINE_PLATFORM</td>
1.223 nia 12921: <td>NATIVE_OBJECT_FMT</td>
1.156 leot 12922: </tr>
12923: <tr>
1.229 gutterid 12924: <td>NBPAX_PROGRAM_PREFIX</td>
1.223 nia 12925: <td>NETBSD_LOGIN_NAME</td>
1.156 leot 12926: </tr>
12927: <tr>
1.229 gutterid 12928: <td>NMH_EDITOR</td>
1.223 nia 12929: <td>NMH_MTA</td>
1.156 leot 12930: </tr>
12931: <tr>
1.229 gutterid 12932: <td>NMH_PAGER</td>
1.223 nia 12933: <td>NODE_VERSIONS_ACCEPTED</td>
1.156 leot 12934: </tr>
12935: <tr>
1.229 gutterid 12936: <td>NODE_VERSIONS_INCOMPATIBLE</td>
1.223 nia 12937: <td>NODE_VERSION_DEFAULT</td>
1.156 leot 12938: </tr>
12939: <tr>
1.229 gutterid 12940: <td>NODE_VERSION_REQD</td>
1.223 nia 12941: <td>NOLOGIN</td>
1.229 gutterid 12942: </tr>
12943: <tr>
1.226 gutterid 12944: <td>NOTE</td>
1.229 gutterid 12945: <td>NOT_FOR_PLATFORM</td>
1.218 nia 12946: </tr>
12947: <tr>
1.226 gutterid 12948: <td>NOT_PAX_ASLR_SAFE</td>
1.229 gutterid 12949: <td>NOT_PAX_MPROTECT_SAFE</td>
1.218 nia 12950: </tr>
12951: <tr>
1.226 gutterid 12952: <td>NO_BUILD</td>
1.229 gutterid 12953: <td>NO_CHECKSUM</td>
1.156 leot 12954: </tr>
12955: <tr>
1.226 gutterid 12956: <td>NO_CONFIGURE</td>
1.229 gutterid 12957: <td>NO_SKIP</td>
1.178 rillig 12958: </tr>
12959: <tr>
1.226 gutterid 12960: <td>NS_PREFERRED</td>
1.229 gutterid 12961: <td>NULLMAILER_GROUP</td>
1.156 leot 12962: </tr>
12963: <tr>
1.226 gutterid 12964: <td>NULLMAILER_USER</td>
1.229 gutterid 12965: <td>OASIS</td>
1.156 leot 12966: </tr>
12967: <tr>
1.226 gutterid 12968: <td>OASIS_BUILD_ARGS</td>
1.229 gutterid 12969: <td>OBJHOSTNAME</td>
1.156 leot 12970: </tr>
12971: <tr>
1.226 gutterid 12972: <td>OBJMACHINE</td>
1.229 gutterid 12973: <td>OCAML_FINDLIB_DIRS</td>
1.156 leot 12974: </tr>
12975: <tr>
1.226 gutterid 12976: <td>OCAML_FINDLIB_REGISTER</td>
1.229 gutterid 12977: <td>OCAML_FINDLIB_REGISTER_VERBOSE</td>
1.156 leot 12978: </tr>
12979: <tr>
1.226 gutterid 12980: <td>OCAML_SITELIBDIR</td>
1.229 gutterid 12981: <td>OCAML_TOPKG_DOCDIR</td>
1.156 leot 12982: </tr>
12983: <tr>
1.226 gutterid 12984: <td>OCAML_USE_DUNE</td>
1.229 gutterid 12985: <td>OCAML_USE_FINDLIB</td>
1.156 leot 12986: </tr>
12987: <tr>
1.226 gutterid 12988: <td>OCAML_USE_OASIS</td>
1.229 gutterid 12989: <td>OCAML_USE_OASIS_DYNRUN</td>
1.156 leot 12990: </tr>
12991: <tr>
1.226 gutterid 12992: <td>OCAML_USE_OPAM</td>
1.229 gutterid 12993: <td>OCAML_USE_TOPKG</td>
1.156 leot 12994: </tr>
12995: <tr>
1.226 gutterid 12996: <td>OMF</td>
1.229 gutterid 12997: <td>ONLY_FOR_COMPILER</td>
1.156 leot 12998: </tr>
12999: <tr>
1.226 gutterid 13000: <td>ONLY_FOR_PLATFORM</td>
1.229 gutterid 13001: <td>OPENSSH_CHROOT</td>
1.156 leot 13002: </tr>
13003: <tr>
1.226 gutterid 13004: <td>OPENSSH_GROUP</td>
1.229 gutterid 13005: <td>OPENSSH_USER</td>
1.156 leot 13006: </tr>
13007: <tr>
1.226 gutterid 13008: <td>OPSYS</td>
1.229 gutterid 13009: <td>OPSYS_EMULDIR</td>
1.156 leot 13010: </tr>
13011: <tr>
1.226 gutterid 13012: <td>OPSYS_VERSION</td>
1.229 gutterid 13013: <td>OS</td>
1.156 leot 13014: </tr>
13015: <tr>
1.226 gutterid 13016: <td>OSS_TYPE</td>
1.229 gutterid 13017: <td>OSX</td>
1.156 leot 13018: </tr>
13019: <tr>
1.226 gutterid 13020: <td>OSX_TOLERATE_SDK_SKEW</td>
1.229 gutterid 13021: <td>OS_VARIANT</td>
1.156 leot 13022: </tr>
13023: <tr>
1.226 gutterid 13024: <td>OS_VERSION</td>
1.229 gutterid 13025: <td>OTF_FONTS_DIR</td>
1.223 nia 13026: </tr>
13027: <tr>
1.226 gutterid 13028: <td>OVERRIDE_DIRDEPTH</td>
1.229 gutterid 13029: <td>OVERRIDE_GEMSPEC</td>
1.212 wiz 13030: </tr>
13031: <tr>
1.226 gutterid 13032: <td>OVERRIDE_GNU_CONFIG_SCRIPTS</td>
1.229 gutterid 13033: <td>OWN_DIRS</td>
1.214 leot 13034: </tr>
13035: <tr>
1.228 gutterid 13036: <td>OWN_DIRS_PERMS</td>
1.229 gutterid 13037: <td>P4GROUP</td>
1.227 wiz 13038: </tr>
13039: <tr>
1.228 gutterid 13040: <td>P4PORT</td>
1.229 gutterid 13041: <td>P4ROOT</td>
1.205 wiz 13042: </tr>
13043: <tr>
1.228 gutterid 13044: <td>P4USER</td>
1.229 gutterid 13045: <td>PACKAGES</td>
1.161 leot 13046: </tr>
13047: <tr>
1.228 gutterid 13048: <td>PALMOS_DEFAULT_SDK</td>
1.229 gutterid 13049: <td>PAMBASE</td>
1.156 leot 13050: </tr>
13051: <tr>
1.228 gutterid 13052: <td>PAM_DEFAULT</td>
1.229 gutterid 13053: <td>PAPERSIZE</td>
1.156 leot 13054: </tr>
13055: <tr>
1.228 gutterid 13056: <td>PASSIVE_FETCH</td>
1.229 gutterid 13057: <td>PATCHDIR</td>
1.156 leot 13058: </tr>
13059: <tr>
1.228 gutterid 13060: <td>PATCHFILES</td>
1.229 gutterid 13061: <td>PATCH_ARGS</td>
1.156 leot 13062: </tr>
13063: <tr>
1.228 gutterid 13064: <td>PATCH_DEBUG</td>
1.229 gutterid 13065: <td>PATCH_DIST_ARGS</td>
1.156 leot 13066: </tr>
13067: <tr>
1.228 gutterid 13068: <td>PATCH_DIST_CAT</td>
1.229 gutterid 13069: <td>PATCH_DIST_STRIP</td>
1.209 nia 13070: </tr>
13071: <tr>
1.228 gutterid 13072: <td>PATCH_FUZZ_FACTOR</td>
1.229 gutterid 13073: <td>PATCH_STRIP</td>
1.156 leot 13074: </tr>
13075: <tr>
1.228 gutterid 13076: <td>PATH</td>
1.229 gutterid 13077: <td>PCCBASE</td>
1.156 leot 13078: </tr>
13079: <tr>
1.228 gutterid 13080: <td>PEAR_CMD</td>
1.229 gutterid 13081: <td>PEAR_LIB</td>
1.227 wiz 13082: </tr>
13083: <tr>
1.228 gutterid 13084: <td>PEAR_PACKAGE_XML</td>
1.229 gutterid 13085: <td>PERL5</td>
1.156 leot 13086: </tr>
13087: <tr>
1.228 gutterid 13088: <td>PERL5_CONFIGURE</td>
1.229 gutterid 13089: <td>PERL5_CONFIGURE_DIRS</td>
1.217 rillig 13090: </tr>
13091: <tr>
1.228 gutterid 13092: <td>PERL5_LDFLAGS</td>
1.229 gutterid 13093: <td>PERL5_LICENSE</td>
1.205 wiz 13094: </tr>
13095: <tr>
1.228 gutterid 13096: <td>PERL5_MODULE_TYPE</td>
1.229 gutterid 13097: <td>PERL5_PACKLIST</td>
1.177 leot 13098: </tr>
13099: <tr>
1.228 gutterid 13100: <td>PERL5_PACKLIST_DIR</td>
1.229 gutterid 13101: <td>PERL5_PERLBASE</td>
1.161 leot 13102: </tr>
13103: <tr>
1.228 gutterid 13104: <td>PERL5_SITEBASE</td>
1.229 gutterid 13105: <td>PERL5_USE_PACKLIST</td>
1.161 leot 13106: </tr>
13107: <tr>
1.228 gutterid 13108: <td>PERL5_VENDORBASE</td>
1.229 gutterid 13109: <td>PFCTL</td>
1.156 leot 13110: </tr>
13111: <tr>
1.228 gutterid 13112: <td>PFVAR_H</td>
1.229 gutterid 13113: <td>PF_VERSION</td>
1.156 leot 13114: </tr>
13115: <tr>
1.228 gutterid 13116: <td>PGGROUP</td>
1.229 gutterid 13117: <td>PGHOME</td>
1.156 leot 13118: </tr>
13119: <tr>
1.228 gutterid 13120: <td>PGPKGSRCDIR</td>
1.229 gutterid 13121: <td>PGSQL_TYPE</td>
1.156 leot 13122: </tr>
13123: <tr>
1.228 gutterid 13124: <td>PGSQL_VERSION</td>
1.229 gutterid 13125: <td>PGSQL_VERSIONS_ACCEPTED</td>
1.156 leot 13126: </tr>
13127: <tr>
1.228 gutterid 13128: <td>PGSQL_VERSION_DEFAULT</td>
1.229 gutterid 13129: <td>PGUSER</td>
1.156 leot 13130: </tr>
13131: <tr>
1.228 gutterid 13132: <td>PG_LIB_EXT</td>
1.229 gutterid 13133: <td>PHP</td>
1.156 leot 13134: </tr>
13135: <tr>
1.228 gutterid 13136: <td>PHPCOMMON_MK</td>
1.229 gutterid 13137: <td>PHPPKGSRCDIR</td>
1.156 leot 13138: </tr>
13139: <tr>
1.228 gutterid 13140: <td>PHP_BASE_VERS</td>
1.229 gutterid 13141: <td>PHP_CHECK_INSTALLED</td>
1.156 leot 13142: </tr>
13143: <tr>
1.228 gutterid 13144: <td>PHP_EXTENSION_DIR</td>
1.229 gutterid 13145: <td>PHP_INITIAL_TEENY</td>
1.156 leot 13146: </tr>
13147: <tr>
1.228 gutterid 13148: <td>PHP_PKG_PREFIX</td>
1.229 gutterid 13149: <td>PHP_VERSION</td>
1.156 leot 13150: </tr>
13151: <tr>
1.228 gutterid 13152: <td>PHP_VERSIONS_ACCEPTED</td>
1.229 gutterid 13153: <td>PHP_VERSIONS_INCOMPATIBLE</td>
1.156 leot 13154: </tr>
13155: <tr>
1.228 gutterid 13156: <td>PHP_VERSION_DEFAULT</td>
1.229 gutterid 13157: <td>PHP_VERSION_REQD</td>
1.156 leot 13158: </tr>
13159: <tr>
1.228 gutterid 13160: <td>PILRC_USE_GTK</td>
1.229 gutterid 13161: <td>PKGCONFIG_BASE</td>
1.156 leot 13162: </tr>
13163: <tr>
1.228 gutterid 13164: <td>PKGCONFIG_FILE</td>
1.229 gutterid 13165: <td>PKGCONFIG_OVERRIDE</td>
1.156 leot 13166: </tr>
13167: <tr>
1.228 gutterid 13168: <td>PKGCONFIG_OVERRIDE_STAGE</td>
1.229 gutterid 13169: <td>PKGDIR</td>
1.156 leot 13170: </tr>
13171: <tr>
1.228 gutterid 13172: <td>PKGGNUDIR</td>
1.229 gutterid 13173: <td>PKGINFODIR</td>
1.156 leot 13174: </tr>
13175: <tr>
1.228 gutterid 13176: <td>PKGLOCALEDIR</td>
1.229 gutterid 13177: <td>PKGMANDIR</td>
1.156 leot 13178: </tr>
13179: <tr>
1.228 gutterid 13180: <td>PKGNAME</td>
1.229 gutterid 13181: <td>PKGNAME_REQD</td>
1.156 leot 13182: </tr>
13183: <tr>
1.228 gutterid 13184: <td>PKGPATH</td>
1.229 gutterid 13185: <td>PKGREVISION</td>
1.156 leot 13186: </tr>
13187: <tr>
1.228 gutterid 13188: <td>PKGSRC_BLAS_TYPES</td>
1.229 gutterid 13189: <td>PKGSRC_CHANGES</td>
1.156 leot 13190: </tr>
13191: <tr>
1.228 gutterid 13192: <td>PKGSRC_COMPILER</td>
1.229 gutterid 13193: <td>PKGSRC_KEEP_BIN_PKGS</td>
1.156 leot 13194: </tr>
13195: <tr>
1.228 gutterid 13196: <td>PKGSRC_LOCKTYPE</td>
1.229 gutterid 13197: <td>PKGSRC_MAKE_ENV</td>
1.156 leot 13198: </tr>
13199: <tr>
1.228 gutterid 13200: <td>PKGSRC_MESSAGE_RECIPIENTS</td>
1.229 gutterid 13201: <td>PKGSRC_MKPIE</td>
1.156 leot 13202: </tr>
13203: <tr>
1.228 gutterid 13204: <td>PKGSRC_MKREPRO</td>
1.229 gutterid 13205: <td>PKGSRC_OVERRIDE_MKPIE</td>
1.177 leot 13206: </tr>
13207: <tr>
1.228 gutterid 13208: <td>PKGSRC_RUN_TEST</td>
1.229 gutterid 13209: <td>PKGSRC_SETENV</td>
1.156 leot 13210: </tr>
13211: <tr>
1.228 gutterid 13212: <td>PKGSRC_SLEEPSECS</td>
1.229 gutterid 13213: <td>PKGSRC_TODO</td>
1.159 rillig 13214: </tr>
13215: <tr>
1.228 gutterid 13216: <td>PKGSRC_USE_CTF</td>
1.229 gutterid 13217: <td>PKGSRC_USE_FORTIFY</td>
1.156 leot 13218: </tr>
13219: <tr>
1.228 gutterid 13220: <td>PKGSRC_USE_MKTOOLS</td>
1.229 gutterid 13221: <td>PKGSRC_USE_RELRO</td>
1.156 leot 13222: </tr>
13223: <tr>
1.228 gutterid 13224: <td>PKGSRC_USE_SSP</td>
1.229 gutterid 13225: <td>PKGSRC_USE_STACK_CHECK</td>
1.156 leot 13226: </tr>
13227: <tr>
1.228 gutterid 13228: <td>PKGTASKS_DATAFILE</td>
1.229 gutterid 13229: <td>PKGTOOLS_ARGS</td>
1.156 leot 13230: </tr>
13231: <tr>
1.228 gutterid 13232: <td>PKGTOOLS_ENV</td>
1.229 gutterid 13233: <td>PKG_ALTERNATIVES</td>
1.156 leot 13234: </tr>
13235: <tr>
1.228 gutterid 13236: <td>PKG_APACHE</td>
1.229 gutterid 13237: <td>PKG_APACHE_ACCEPTED</td>
1.156 leot 13238: </tr>
13239: <tr>
1.228 gutterid 13240: <td>PKG_APACHE_DEFAULT</td>
1.229 gutterid 13241: <td>PKG_BEST_EXISTS</td>
1.156 leot 13242: </tr>
13243: <tr>
1.228 gutterid 13244: <td>PKG_BUILD_OPTIONS</td>
1.229 gutterid 13245: <td>PKG_COMPRESSION</td>
1.156 leot 13246: </tr>
13247: <tr>
1.228 gutterid 13248: <td>PKG_CONFIG</td>
1.229 gutterid 13249: <td>PKG_CONFIG_PERMS</td>
1.156 leot 13250: </tr>
13251: <tr>
1.228 gutterid 13252: <td>PKG_CREATE_USERGROUP</td>
1.229 gutterid 13253: <td>PKG_DB_TMPDIR</td>
1.156 leot 13254: </tr>
13255: <tr>
1.228 gutterid 13256: <td>PKG_DEBUG_LEVEL</td>
1.229 gutterid 13257: <td>PKG_DEFAULT_OPTIONS</td>
1.156 leot 13258: </tr>
13259: <tr>
1.228 gutterid 13260: <td>PKG_DESTDIR_SUPPORT</td>
1.229 gutterid 13261: <td>PKG_DEVELOPER</td>
1.156 leot 13262: </tr>
13263: <tr>
1.228 gutterid 13264: <td>PKG_DISABLED_OPTIONS</td>
1.229 gutterid 13265: <td>PKG_FATAL_ERRORS</td>
1.156 leot 13266: </tr>
13267: <tr>
1.228 gutterid 13268: <td>PKG_FC</td>
1.229 gutterid 13269: <td>PKG_FILELIST_CMD</td>
1.156 leot 13270: </tr>
13271: <tr>
1.228 gutterid 13272: <td>PKG_GECOS</td>
1.229 gutterid 13273: <td>PKG_GID</td>
1.156 leot 13274: </tr>
13275: <tr>
1.228 gutterid 13276: <td>PKG_GROUPS</td>
1.229 gutterid 13277: <td>PKG_GROUPS_VARS</td>
1.156 leot 13278: </tr>
13279: <tr>
1.228 gutterid 13280: <td>PKG_HOME</td>
1.229 gutterid 13281: <td>PKG_INIT_SCRIPTS</td>
1.156 leot 13282: </tr>
13283: <tr>
1.228 gutterid 13284: <td>PKG_JAVA_HOME</td>
1.229 gutterid 13285: <td>PKG_JVM</td>
1.156 leot 13286: </tr>
13287: <tr>
1.228 gutterid 13288: <td>PKG_JVMS_ACCEPTED</td>
1.229 gutterid 13289: <td>PKG_JVM_DEFAULT</td>
1.156 leot 13290: </tr>
13291: <tr>
1.228 gutterid 13292: <td>PKG_LEGACY_OPTIONS</td>
1.229 gutterid 13293: <td>PKG_LIBTOOL</td>
1.156 leot 13294: </tr>
13295: <tr>
1.228 gutterid 13296: <td>PKG_MKSYMLINKS</td>
1.229 gutterid 13297: <td>PKG_OPTIONS</td>
1.156 leot 13298: </tr>
13299: <tr>
1.228 gutterid 13300: <td>PKG_OPTIONS_DEPRECATED_WARNINGS</td>
1.229 gutterid 13301: <td>PKG_OPTIONS_LEGACY_OPTS</td>
1.226 gutterid 13302: </tr>
13303: <tr>
1.228 gutterid 13304: <td>PKG_OPTIONS_LEGACY_VARS</td>
1.229 gutterid 13305: <td>PKG_OPTIONS_NONEMPTY_SETS</td>
1.156 leot 13306: </tr>
13307: <tr>
1.228 gutterid 13308: <td>PKG_OPTIONS_OPTIONAL_GROUPS</td>
1.229 gutterid 13309: <td>PKG_OPTIONS_REQUIRED_GROUPS</td>
1.156 leot 13310: </tr>
13311: <tr>
1.228 gutterid 13312: <td>PKG_OPTIONS_VAR</td>
1.229 gutterid 13313: <td>PKG_PHP</td>
1.156 leot 13314: </tr>
13315: <tr>
1.228 gutterid 13316: <td>PKG_PHP_MAJOR_VERS</td>
1.229 gutterid 13317: <td>PKG_PHP_VERSION</td>
1.156 leot 13318: </tr>
13319: <tr>
1.228 gutterid 13320: <td>PKG_RCD_SCRIPTS</td>
1.229 gutterid 13321: <td>PKG_REFCOUNT_DBDIR</td>
1.156 leot 13322: </tr>
13323: <tr>
1.228 gutterid 13324: <td>PKG_REGISTER_SHELLS</td>
1.229 gutterid 13325: <td>PKG_RESUME_TRANSFERS</td>
1.156 leot 13326: </tr>
13327: <tr>
1.228 gutterid 13328: <td>PKG_SHELL</td>
1.229 gutterid 13329: <td>PKG_SUGGESTED_OPTIONS</td>
1.156 leot 13330: </tr>
13331: <tr>
1.228 gutterid 13332: <td>PKG_SUPPORTED_OPTIONS</td>
1.229 gutterid 13333: <td>PKG_SYSCONFBASE</td>
1.156 leot 13334: </tr>
13335: <tr>
1.228 gutterid 13336: <td>PKG_SYSCONFBASEDIR</td>
1.229 gutterid 13337: <td>PKG_SYSCONFDIR</td>
1.156 leot 13338: </tr>
13339: <tr>
1.228 gutterid 13340: <td>PKG_SYSCONFDIR_PERMS</td>
1.229 gutterid 13341: <td>PKG_SYSCONFSUBDIR</td>
1.156 leot 13342: </tr>
13343: <tr>
1.228 gutterid 13344: <td>PKG_SYSCONFVAR</td>
1.229 gutterid 13345: <td>PKG_TOOLS_BIN</td>
1.156 leot 13346: </tr>
13347: <tr>
1.228 gutterid 13348: <td>PKG_UID</td>
1.229 gutterid 13349: <td>PKG_UPDATE_FONTS_DB</td>
1.156 leot 13350: </tr>
13351: <tr>
1.228 gutterid 13352: <td>PKG_USERS</td>
1.229 gutterid 13353: <td>PKG_USERS_VARS</td>
1.156 leot 13354: </tr>
13355: <tr>
1.228 gutterid 13356: <td>PKG_VERBOSE</td>
1.229 gutterid 13357: <td>PLEASE</td>
1.156 leot 13358: </tr>
13359: <tr>
1.228 gutterid 13360: <td>PLIST</td>
1.229 gutterid 13361: <td>PLIST_AWK</td>
1.156 leot 13362: </tr>
13363: <tr>
1.228 gutterid 13364: <td>PLIST_AWK_ENV</td>
1.229 gutterid 13365: <td>PLIST_SRC</td>
1.156 leot 13366: </tr>
13367: <tr>
1.228 gutterid 13368: <td>PLIST_SUBST</td>
1.229 gutterid 13369: <td>PLIST_TYPE</td>
1.156 leot 13370: </tr>
13371: <tr>
1.228 gutterid 13372: <td>PLIST_VARS</td>
1.229 gutterid 13373: <td>POPTOP_USE_MPPE</td>
1.156 leot 13374: </tr>
13375: <tr>
1.228 gutterid 13376: <td>POSSIBLE_GFORTRAN_VERSION</td>
1.229 gutterid 13377: <td>POST_FETCH_HOOK</td>
1.156 leot 13378: </tr>
13379: <tr>
1.228 gutterid 13380: <td>PREFER</td>
1.229 gutterid 13381: <td>PREFER_NATIVE</td>
1.156 leot 13382: </tr>
13383: <tr>
1.228 gutterid 13384: <td>PREFER_NATIVE_PTHREADS</td>
1.229 gutterid 13385: <td>PREFER_PKGSRC</td>
1.156 leot 13386: </tr>
13387: <tr>
1.228 gutterid 13388: <td>PREFIX</td>
1.229 gutterid 13389: <td>PREPEND_PATH</td>
1.156 leot 13390: </tr>
13391: <tr>
1.228 gutterid 13392: <td>PRE_ROOT_CMD</td>
1.229 gutterid 13393: <td>PRIVILEGED_STAGES</td>
1.156 leot 13394: </tr>
13395: <tr>
1.228 gutterid 13396: <td>PS</td>
1.229 gutterid 13397: <td>PTHREAD_AUTO_VARS</td>
1.156 leot 13398: </tr>
13399: <tr>
1.228 gutterid 13400: <td>PTHREAD_CFLAGS</td>
1.229 gutterid 13401: <td>PTHREAD_LDFLAGS</td>
1.156 leot 13402: </tr>
13403: <tr>
1.228 gutterid 13404: <td>PTHREAD_LIBS</td>
1.229 gutterid 13405: <td>PTHREAD_OPTS</td>
1.156 leot 13406: </tr>
13407: <tr>
1.228 gutterid 13408: <td>PTHREAD_TYPE</td>
1.229 gutterid 13409: <td>PVM_SSH</td>
1.156 leot 13410: </tr>
13411: <tr>
1.228 gutterid 13412: <td>PYPKGPREFIX</td>
1.229 gutterid 13413: <td>PYTHON_FOR_BUILD_ONLY</td>
1.156 leot 13414: </tr>
13415: <tr>
1.228 gutterid 13416: <td>PYTHON_SELF_CONFLICT</td>
1.229 gutterid 13417: <td>PYTHON_VERSIONED_DEPENDENCIES</td>
1.156 leot 13418: </tr>
13419: <tr>
1.228 gutterid 13420: <td>PYTHON_VERSIONS_ACCEPTED</td>
1.229 gutterid 13421: <td>PYTHON_VERSIONS_INCOMPATIBLE</td>
1.156 leot 13422: </tr>
13423: <tr>
1.228 gutterid 13424: <td>PYTHON_VERSION_DEFAULT</td>
1.229 gutterid 13425: <td>PYTHON_VERSION_REQD</td>
1.156 leot 13426: </tr>
13427: <tr>
1.228 gutterid 13428: <td>PYVERSSUFFIX</td>
1.229 gutterid 13429: <td>QMAILDIR</td>
1.156 leot 13430: </tr>
13431: <tr>
1.228 gutterid 13432: <td>QMAIL_ALIAS_USER</td>
1.229 gutterid 13433: <td>QMAIL_DAEMON_USER</td>
1.156 leot 13434: </tr>
13435: <tr>
1.228 gutterid 13436: <td>QMAIL_LOG_USER</td>
1.229 gutterid 13437: <td>QMAIL_NOFILES_GROUP</td>
1.156 leot 13438: </tr>
13439: <tr>
1.228 gutterid 13440: <td>QMAIL_PASSWD_USER</td>
1.229 gutterid 13441: <td>QMAIL_QMAIL_GROUP</td>
1.156 leot 13442: </tr>
13443: <tr>
1.228 gutterid 13444: <td>QMAIL_QUEUE_DIR</td>
1.229 gutterid 13445: <td>QMAIL_QUEUE_EXTRA</td>
1.156 leot 13446: </tr>
13447: <tr>
1.228 gutterid 13448: <td>QMAIL_QUEUE_USER</td>
1.229 gutterid 13449: <td>QMAIL_REMOTE_USER</td>
1.156 leot 13450: </tr>
13451: <tr>
1.228 gutterid 13452: <td>QMAIL_ROOT_USER</td>
1.229 gutterid 13453: <td>QMAIL_SEND_USER</td>
1.156 leot 13454: </tr>
13455: <tr>
1.228 gutterid 13456: <td>QORE_LATEST_MODULE_API</td>
1.229 gutterid 13457: <td>QORE_MODULE_API</td>
1.156 leot 13458: </tr>
13459: <tr>
1.228 gutterid 13460: <td>QORE_MODULE_DIR</td>
1.229 gutterid 13461: <td>QORE_USER_MODULE_DIR</td>
1.156 leot 13462: </tr>
13463: <tr>
1.228 gutterid 13464: <td>QORE_VERSION</td>
1.229 gutterid 13465: <td>QPOPPER_FAC</td>
1.156 leot 13466: </tr>
13467: <tr>
1.228 gutterid 13468: <td>QPOPPER_SPOOL_DIR</td>
1.229 gutterid 13469: <td>QPOPPER_USER</td>
1.218 nia 13470: </tr>
13471: <tr>
1.228 gutterid 13472: <td>RAKE_NAME</td>
1.229 gutterid 13473: <td>RASMOL_DEPTH</td>
1.218 nia 13474: </tr>
13475: <tr>
1.228 gutterid 13476: <td>RCD_SCRIPTS</td>
1.229 gutterid 13477: <td>RCD_SCRIPTS_DIR</td>
1.227 wiz 13478: </tr>
13479: <tr>
1.228 gutterid 13480: <td>RCD_SCRIPTS_EXAMPLEDIR</td>
1.229 gutterid 13481: <td>RCD_SCRIPTS_MODE</td>
1.156 leot 13482: </tr>
13483: <tr>
1.228 gutterid 13484: <td>RCD_SCRIPTS_SHELL</td>
1.229 gutterid 13485: <td>RCD_SCRIPT_SRC</td>
1.214 leot 13486: </tr>
13487: <tr>
1.226 gutterid 13488: <td>RDOC</td>
1.229 gutterid 13489: <td>READLINE_DEFAULT</td>
1.205 wiz 13490: </tr>
13491: <tr>
1.226 gutterid 13492: <td>READLINE_TYPE</td>
1.229 gutterid 13493: <td>REAL_ROOT_GROUP</td>
1.223 nia 13494: </tr>
13495: <tr>
1.226 gutterid 13496: <td>REAL_ROOT_USER</td>
1.229 gutterid 13497: <td>RECURSIVE_MAKE</td>
1.177 leot 13498: </tr>
13499: <tr>
1.226 gutterid 13500: <td>RELAY_CTRL_DIR</td>
1.229 gutterid 13501: <td>RELRO_SUPPORTED</td>
1.214 leot 13502: </tr>
13503: <tr>
1.226 gutterid 13504: <td>REPLACE_AWK</td>
1.229 gutterid 13505: <td>REPLACE_BASH</td>
1.212 wiz 13506: </tr>
13507: <tr>
1.226 gutterid 13508: <td>REPLACE_CSH</td>
1.229 gutterid 13509: <td>REPLACE_KSH</td>
1.156 leot 13510: </tr>
13511: <tr>
1.226 gutterid 13512: <td>REPLACE_LUA</td>
1.229 gutterid 13513: <td>REPLACE_NODEJS</td>
1.205 wiz 13514: </tr>
13515: <tr>
1.226 gutterid 13516: <td>REPLACE_OCTAVE</td>
1.229 gutterid 13517: <td>REPLACE_PERL</td>
1.197 leot 13518: </tr>
13519: <tr>
1.226 gutterid 13520: <td>REPLACE_PERL6</td>
1.229 gutterid 13521: <td>REPLACE_PHP</td>
1.156 leot 13522: </tr>
13523: <tr>
1.226 gutterid 13524: <td>REPLACE_PYTHON</td>
1.229 gutterid 13525: <td>REPLACE_QORE</td>
1.218 nia 13526: </tr>
13527: <tr>
1.226 gutterid 13528: <td>REPLACE_R</td>
1.229 gutterid 13529: <td>REPLACE_RUBY</td>
1.161 leot 13530: </tr>
13531: <tr>
1.226 gutterid 13532: <td>REPLACE_RUBY_DIRS</td>
1.229 gutterid 13533: <td>REPLACE_RUBY_PAT</td>
1.216 gutterid 13534: </tr>
13535: <tr>
1.226 gutterid 13536: <td>REPLACE_SH</td>
1.229 gutterid 13537: <td>REPLACE_TEXLUA</td>
1.156 leot 13538: </tr>
13539: <tr>
1.226 gutterid 13540: <td>REPLACE_WISH</td>
1.229 gutterid 13541: <td>REQD_DIRS</td>
1.218 nia 13542: </tr>
13543: <tr>
1.226 gutterid 13544: <td>REQD_DIRS_PERMS</td>
1.229 gutterid 13545: <td>REQD_FILES</td>
1.156 leot 13546: </tr>
13547: <tr>
1.226 gutterid 13548: <td>REQD_FILES_MODE</td>
1.229 gutterid 13549: <td>REQD_FILES_PERMS</td>
1.156 leot 13550: </tr>
13551: <tr>
1.226 gutterid 13552: <td>RESOLV_AUTO_VARS</td>
1.229 gutterid 13553: <td>RESOLV_LDFLAGS</td>
1.156 leot 13554: </tr>
13555: <tr>
1.226 gutterid 13556: <td>RESOLV_LIBS</td>
1.229 gutterid 13557: <td>RM</td>
1.156 leot 13558: </tr>
13559: <tr>
1.226 gutterid 13560: <td>ROOT_CMD</td>
1.229 gutterid 13561: <td>ROOT_GROUP</td>
1.156 leot 13562: </tr>
13563: <tr>
1.226 gutterid 13564: <td>ROOT_USER</td>
1.229 gutterid 13565: <td>RPCGEN</td>
1.205 wiz 13566: </tr>
13567: <tr>
1.226 gutterid 13568: <td>RPM</td>
1.229 gutterid 13569: <td>RPM2PKG_PLIST</td>
1.217 rillig 13570: </tr>
13571: <tr>
1.226 gutterid 13572: <td>RPM2PKG_PREFIX</td>
1.229 gutterid 13573: <td>RPM2PKG_STAGE</td>
1.214 leot 13574: </tr>
13575: <tr>
1.226 gutterid 13576: <td>RPM2PKG_STRIP</td>
1.229 gutterid 13577: <td>RPM2PKG_SUBPREFIX</td>
1.212 wiz 13578: </tr>
13579: <tr>
1.226 gutterid 13580: <td>RPMFILES</td>
1.229 gutterid 13581: <td>RPMIGNOREPATH</td>
1.156 leot 13582: </tr>
13583: <tr>
1.226 gutterid 13584: <td>RPM_DB_PREFIX</td>
1.229 gutterid 13585: <td>RSSH_CVS_PATH</td>
1.197 leot 13586: </tr>
13587: <tr>
1.226 gutterid 13588: <td>RSSH_RDIST_PATH</td>
1.229 gutterid 13589: <td>RSSH_RSYNC_PATH</td>
1.156 leot 13590: </tr>
13591: <tr>
1.226 gutterid 13592: <td>RSSH_SCP_PATH</td>
1.229 gutterid 13593: <td>RSSH_SFTP_SERVER_PATH</td>
1.156 leot 13594: </tr>
13595: <tr>
1.226 gutterid 13596: <td>RUBY</td>
1.229 gutterid 13597: <td>RUBYGEM</td>
1.156 leot 13598: </tr>
13599: <tr>
1.231 ! jnemeth 13600: <td>RUBYGEM_MANPAGES</td>
1.226 gutterid 13601: <td>RUBYGEM_NAME</td>
1.231 ! jnemeth 13602: </tr>
! 13603: <tr>
1.229 gutterid 13604: <td>RUBYGEM_OPTIONS</td>
1.231 ! jnemeth 13605: <td>RUBYGEM_USE_MANPAGES</td>
1.156 leot 13606: </tr>
13607: <tr>
1.226 gutterid 13608: <td>RUBYGEM_VERBOSE</td>
1.229 gutterid 13609: <td>RUBY_ABI_VERSION</td>
1.156 leot 13610: </tr>
13611: <tr>
1.226 gutterid 13612: <td>RUBY_ARCH</td>
1.229 gutterid 13613: <td>RUBY_ARCHINC</td>
1.156 leot 13614: </tr>
13615: <tr>
1.226 gutterid 13616: <td>RUBY_ARCHLIB</td>
1.229 gutterid 13617: <td>RUBY_BASE</td>
1.156 leot 13618: </tr>
13619: <tr>
1.226 gutterid 13620: <td>RUBY_BASERIDIR</td>
1.229 gutterid 13621: <td>RUBY_BUILD_DOCUMENT</td>
1.156 leot 13622: </tr>
13623: <tr>
1.226 gutterid 13624: <td>RUBY_DLEXT</td>
1.229 gutterid 13625: <td>RUBY_DOC</td>
1.156 leot 13626: </tr>
13627: <tr>
1.226 gutterid 13628: <td>RUBY_DYNAMIC_DIRS</td>
1.229 gutterid 13629: <td>RUBY_EG</td>
1.156 leot 13630: </tr>
13631: <tr>
1.226 gutterid 13632: <td>RUBY_ENCODING_ARG</td>
1.229 gutterid 13633: <td>RUBY_EXTCONF</td>
1.198 leot 13634: </tr>
13635: <tr>
1.226 gutterid 13636: <td>RUBY_EXTCONF_CHECK</td>
1.229 gutterid 13637: <td>RUBY_EXTCONF_DEBUG</td>
1.156 leot 13638: </tr>
13639: <tr>
1.226 gutterid 13640: <td>RUBY_EXTCONF_MAKEFILE</td>
1.229 gutterid 13641: <td>RUBY_GEM_ARCH</td>
1.156 leot 13642: </tr>
13643: <tr>
1.226 gutterid 13644: <td>RUBY_GEM_BASE</td>
1.229 gutterid 13645: <td>RUBY_INC</td>
1.156 leot 13646: </tr>
13647: <tr>
1.226 gutterid 13648: <td>RUBY_LIB</td>
1.229 gutterid 13649: <td>RUBY_LIB_BASE</td>
1.156 leot 13650: </tr>
13651: <tr>
1.226 gutterid 13652: <td>RUBY_NAME</td>
1.229 gutterid 13653: <td>RUBY_NOVERSION</td>
1.223 nia 13654: </tr>
13655: <tr>
1.226 gutterid 13656: <td>RUBY_PKGPREFIX</td>
1.229 gutterid 13657: <td>RUBY_RAILS</td>
1.156 leot 13658: </tr>
13659: <tr>
1.226 gutterid 13660: <td>RUBY_RAILS52_VERSION</td>
1.229 gutterid 13661: <td>RUBY_RAILS60_VERSION</td>
1.156 leot 13662: </tr>
13663: <tr>
1.226 gutterid 13664: <td>RUBY_RAILS61_VERSION</td>
1.229 gutterid 13665: <td>RUBY_RAILS70_VERSION</td>
1.156 leot 13666: </tr>
13667: <tr>
1.226 gutterid 13668: <td>RUBY_RAILS_ACCEPTED</td>
1.229 gutterid 13669: <td>RUBY_RAILS_DEFAULT</td>
1.156 leot 13670: </tr>
13671: <tr>
1.226 gutterid 13672: <td>RUBY_RAILS_REQD</td>
1.229 gutterid 13673: <td>RUBY_RAILS_STRICT_DEP</td>
1.156 leot 13674: </tr>
13675: <tr>
1.226 gutterid 13676: <td>RUBY_RIDIR</td>
1.229 gutterid 13677: <td>RUBY_SETUP</td>
1.156 leot 13678: </tr>
13679: <tr>
1.226 gutterid 13680: <td>RUBY_SHLIB</td>
1.229 gutterid 13681: <td>RUBY_SHLIBALIAS</td>
1.156 leot 13682: </tr>
13683: <tr>
1.226 gutterid 13684: <td>RUBY_SHLIBVER</td>
1.229 gutterid 13685: <td>RUBY_SIMPLE_INSTALL</td>
1.156 leot 13686: </tr>
13687: <tr>
1.226 gutterid 13688: <td>RUBY_SITEARCHLIB</td>
1.229 gutterid 13689: <td>RUBY_SITELIB</td>
1.156 leot 13690: </tr>
13691: <tr>
1.226 gutterid 13692: <td>RUBY_SITELIB_BASE</td>
1.229 gutterid 13693: <td>RUBY_SITERIDIR</td>
1.174 leot 13694: </tr>
13695: <tr>
1.226 gutterid 13696: <td>RUBY_SLEXT</td>
1.229 gutterid 13697: <td>RUBY_SRCDIR</td>
1.156 leot 13698: </tr>
13699: <tr>
1.226 gutterid 13700: <td>RUBY_STATICLIB</td>
1.229 gutterid 13701: <td>RUBY_SUFFIX</td>
1.156 leot 13702: </tr>
13703: <tr>
1.226 gutterid 13704: <td>RUBY_SYSRIDIR</td>
1.229 gutterid 13705: <td>RUBY_USE_PTHREAD</td>
1.156 leot 13706: </tr>
13707: <tr>
1.226 gutterid 13708: <td>RUBY_VENDORARCHLIB</td>
1.229 gutterid 13709: <td>RUBY_VENDORLIB</td>
1.156 leot 13710: </tr>
13711: <tr>
1.226 gutterid 13712: <td>RUBY_VENDORLIB_BASE</td>
1.229 gutterid 13713: <td>RUBY_VER</td>
1.156 leot 13714: </tr>
13715: <tr>
1.226 gutterid 13716: <td>RUBY_VERSION</td>
1.229 gutterid 13717: <td>RUBY_VERSIONS_ACCEPTED</td>
1.156 leot 13718: </tr>
13719: <tr>
1.226 gutterid 13720: <td>RUBY_VERSIONS_INCOMPATIBLE</td>
1.229 gutterid 13721: <td>RUBY_VERSION_DEFAULT</td>
1.156 leot 13722: </tr>
13723: <tr>
1.226 gutterid 13724: <td>RUBY_VERSION_REQD</td>
1.229 gutterid 13725: <td>RUBY_VER_DIR</td>
1.156 leot 13726: </tr>
13727: <tr>
1.226 gutterid 13728: <td>RUN</td>
1.229 gutterid 13729: <td>RUN_LDCONFIG</td>
1.156 leot 13730: </tr>
13731: <tr>
1.226 gutterid 13732: <td>RUST_TYPE</td>
1.229 gutterid 13733: <td>SCO</td>
1.156 leot 13734: </tr>
13735: <tr>
1.226 gutterid 13736: <td>SCREWS_GROUP</td>
1.229 gutterid 13737: <td>SCREWS_USER</td>
1.156 leot 13738: </tr>
13739: <tr>
1.226 gutterid 13740: <td>SCRIPTS_ENV</td>
1.229 gutterid 13741: <td>SCROLLKEEPER_DATADIR</td>
1.156 leot 13742: </tr>
13743: <tr>
1.226 gutterid 13744: <td>SCROLLKEEPER_REBUILDDB</td>
1.229 gutterid 13745: <td>SCROLLKEEPER_UPDATEDB</td>
1.156 leot 13746: </tr>
13747: <tr>
1.226 gutterid 13748: <td>SDIST_PAWD</td>
1.229 gutterid 13749: <td>SDL12_TYPE</td>
1.156 leot 13750: </tr>
13751: <tr>
1.226 gutterid 13752: <td>SERIAL_DEVICES</td>
1.229 gutterid 13753: <td>SETGIDGAME</td>
1.156 leot 13754: </tr>
13755: <tr>
1.226 gutterid 13756: <td>SETGID_GAMES_PERMS</td>
1.229 gutterid 13757: <td>SETUID_ROOT_PERMS</td>
1.221 nia 13758: </tr>
13759: <tr>
1.226 gutterid 13760: <td>SH</td>
1.229 gutterid 13761: <td>SHLIB</td>
1.156 leot 13762: </tr>
13763: <tr>
1.228 gutterid 13764: <td>SIGN_PACKAGES</td>
1.229 gutterid 13765: <td>SILC_CLIENT_WITH_PERL</td>
1.227 wiz 13766: </tr>
13767: <tr>
1.228 gutterid 13768: <td>SITE_SPECIFIC_PKGS</td>
1.229 gutterid 13769: <td>SKIP_DEPENDS</td>
1.156 leot 13770: </tr>
13771: <tr>
1.228 gutterid 13772: <td>SMF_INSTANCES</td>
1.229 gutterid 13773: <td>SMF_MANIFEST</td>
1.156 leot 13774: </tr>
13775: <tr>
1.228 gutterid 13776: <td>SMF_METHODS</td>
1.229 gutterid 13777: <td>SMF_METHOD_SHELL</td>
1.177 leot 13778: </tr>
13779: <tr>
1.228 gutterid 13780: <td>SMF_METHOD_SRC</td>
1.229 gutterid 13781: <td>SMF_NAME</td>
1.156 leot 13782: </tr>
13783: <tr>
1.228 gutterid 13784: <td>SMF_PREFIX</td>
1.229 gutterid 13785: <td>SMF_SRCDIR</td>
1.217 rillig 13786: </tr>
13787: <tr>
1.228 gutterid 13788: <td>SNIPROXY_GROUP</td>
1.229 gutterid 13789: <td>SNIPROXY_USER</td>
1.156 leot 13790: </tr>
13791: <tr>
1.228 gutterid 13792: <td>SOURCE_BUFFSIZE</td>
1.229 gutterid 13793: <td>SPECIAL_PERMS</td>
1.159 rillig 13794: </tr>
13795: <tr>
1.228 gutterid 13796: <td>SPECIFIC_PKGS</td>
1.229 gutterid 13797: <td>SSH_SUID</td>
1.156 leot 13798: </tr>
13799: <tr>
1.228 gutterid 13800: <td>SSP_SUPPORTED</td>
1.229 gutterid 13801: <td>SSYNC_PAWD</td>
1.156 leot 13802: </tr>
13803: <tr>
1.228 gutterid 13804: <td>STEP_MSG</td>
1.229 gutterid 13805: <td>STRIP</td>
1.156 leot 13806: </tr>
13807: <tr>
1.228 gutterid 13808: <td>STRIP_DBG</td>
1.229 gutterid 13809: <td>STRIP_DEBUG</td>
1.156 leot 13810: </tr>
13811: <tr>
1.228 gutterid 13812: <td>STRIP_DEBUG_SUPPORTED</td>
1.229 gutterid 13813: <td>STRIP_FILES_SKIP</td>
1.156 leot 13814: </tr>
13815: <tr>
1.228 gutterid 13816: <td>SU</td>
1.229 gutterid 13817: <td>SUBDIR</td>
1.156 leot 13818: </tr>
13819: <tr>
1.228 gutterid 13820: <td>SUBST</td>
1.229 gutterid 13821: <td>SUBST_CLASSES</td>
1.156 leot 13822: </tr>
13823: <tr>
1.228 gutterid 13824: <td>SUBST_FILES</td>
1.229 gutterid 13825: <td>SUBST_FILTER_CMD</td>
1.156 leot 13826: </tr>
13827: <tr>
1.228 gutterid 13828: <td>SUBST_MESSAGE</td>
1.229 gutterid 13829: <td>SUBST_NOOP_OK</td>
1.156 leot 13830: </tr>
13831: <tr>
1.228 gutterid 13832: <td>SUBST_SED</td>
1.229 gutterid 13833: <td>SUBST_SHOW_DIFF</td>
1.156 leot 13834: </tr>
13835: <tr>
1.228 gutterid 13836: <td>SUBST_SKIP_TEXT_CHECK</td>
1.229 gutterid 13837: <td>SUBST_STAGE</td>
1.156 leot 13838: </tr>
13839: <tr>
1.228 gutterid 13840: <td>SUBST_VARS</td>
1.229 gutterid 13841: <td>SUNWSPROBASE</td>
1.174 leot 13842: </tr>
13843: <tr>
1.228 gutterid 13844: <td>SUSE_PREFER</td>
1.229 gutterid 13845: <td>SU_CMD</td>
1.156 leot 13846: </tr>
13847: <tr>
1.228 gutterid 13848: <td>SYSCONFBASE</td>
1.229 gutterid 13849: <td>TARGET_ARCH</td>
1.227 wiz 13850: </tr>
13851: <tr>
1.228 gutterid 13852: <td>TBL</td>
1.229 gutterid 13853: <td>TERMCAP_TYPE</td>
1.156 leot 13854: </tr>
13855: <tr>
1.228 gutterid 13856: <td>TERMINFO_DEFAULT</td>
1.229 gutterid 13857: <td>TERMINFO_TYPE</td>
1.217 rillig 13858: </tr>
13859: <tr>
1.228 gutterid 13860: <td>TEST</td>
1.229 gutterid 13861: <td>TEST_DEPENDS</td>
1.212 wiz 13862: </tr>
13863: <tr>
1.228 gutterid 13864: <td>TEST_DIRS</td>
1.229 gutterid 13865: <td>TEST_ENV</td>
1.217 rillig 13866: </tr>
13867: <tr>
1.228 gutterid 13868: <td>TEST_ENV_SHELL</td>
1.229 gutterid 13869: <td>TEST_MAKE_CMD</td>
1.205 wiz 13870: </tr>
13871: <tr>
1.228 gutterid 13872: <td>TEST_MAKE_FLAGS</td>
1.229 gutterid 13873: <td>TEST_TARGET</td>
1.189 bacon 13874: </tr>
13875: <tr>
1.228 gutterid 13876: <td>TEXLIVE_IGNORE_PATTERNS</td>
1.229 gutterid 13877: <td>TEXLIVE_REV</td>
1.161 leot 13878: </tr>
13879: <tr>
1.228 gutterid 13880: <td>TEXLIVE_UNVERSIONED</td>
1.229 gutterid 13881: <td>TEXMFSITE</td>
1.159 rillig 13882: </tr>
13883: <tr>
1.228 gutterid 13884: <td>TEX_FORMATS</td>
1.229 gutterid 13885: <td>TEX_HYPHEN_DAT</td>
1.156 leot 13886: </tr>
13887: <tr>
1.228 gutterid 13888: <td>TEX_HYPHEN_DEF</td>
1.229 gutterid 13889: <td>TEX_TEXMF_DIRS</td>
1.156 leot 13890: </tr>
13891: <tr>
1.228 gutterid 13892: <td>THTTPD_LOG_FACILITY</td>
1.229 gutterid 13893: <td>TINYDYN_USER</td>
1.156 leot 13894: </tr>
13895: <tr>
1.228 gutterid 13896: <td>TLSWRAPPER_CHROOT</td>
1.229 gutterid 13897: <td>TO</td>
1.156 leot 13898: </tr>
13899: <tr>
1.228 gutterid 13900: <td>TOOLS_ALIASES</td>
1.229 gutterid 13901: <td>TOOLS_ALWAYS_WRAP</td>
1.156 leot 13902: </tr>
13903: <tr>
1.228 gutterid 13904: <td>TOOLS_ARGS</td>
1.229 gutterid 13905: <td>TOOLS_BROKEN</td>
1.156 leot 13906: </tr>
13907: <tr>
1.228 gutterid 13908: <td>TOOLS_CMD</td>
1.229 gutterid 13909: <td>TOOLS_CMDLINE_SED</td>
1.156 leot 13910: </tr>
13911: <tr>
1.228 gutterid 13912: <td>TOOLS_CREATE</td>
1.229 gutterid 13913: <td>TOOLS_CROSS_DESTDIR</td>
1.156 leot 13914: </tr>
13915: <tr>
1.228 gutterid 13916: <td>TOOLS_DIR</td>
1.229 gutterid 13917: <td>TOOLS_FAIL</td>
1.156 leot 13918: </tr>
13919: <tr>
1.228 gutterid 13920: <td>TOOLS_GNU_MISSING</td>
1.229 gutterid 13921: <td>TOOLS_LDCONFIG</td>
1.156 leot 13922: </tr>
13923: <tr>
1.228 gutterid 13924: <td>TOOLS_NOOP</td>
1.229 gutterid 13925: <td>TOOLS_PATH</td>
1.156 leot 13926: </tr>
13927: <tr>
1.228 gutterid 13928: <td>TOOLS_SCRIPT</td>
1.229 gutterid 13929: <td>TOOLS_USE_CROSS_COMPILE</td>
1.156 leot 13930: </tr>
13931: <tr>
1.226 gutterid 13932: <td>TOOL_DEPENDS</td>
1.229 gutterid 13933: <td>TTF_FONTS_DIR</td>
1.156 leot 13934: </tr>
13935: <tr>
1.226 gutterid 13936: <td>TYPE</td>
1.229 gutterid 13937: <td>UAC_REQD_EXECS</td>
1.223 nia 13938: </tr>
13939: <tr>
1.226 gutterid 13940: <td>UCSPI_SSL_GROUP</td>
1.229 gutterid 13941: <td>UCSPI_SSL_USER</td>
1.156 leot 13942: </tr>
13943: <tr>
1.226 gutterid 13944: <td>UNLIMIT_RESOURCES</td>
1.229 gutterid 13945: <td>UNPRIVILEGED</td>
1.214 leot 13946: </tr>
13947: <tr>
1.226 gutterid 13948: <td>UNPRIVILEGED_GROUP</td>
1.229 gutterid 13949: <td>UNPRIVILEGED_GROUPS</td>
1.212 wiz 13950: </tr>
13951: <tr>
1.226 gutterid 13952: <td>UNPRIVILEGED_USER</td>
1.229 gutterid 13953: <td>UNWRAP_FILES</td>
1.156 leot 13954: </tr>
13955: <tr>
1.226 gutterid 13956: <td>UNWRAP_PATTERNS</td>
1.229 gutterid 13957: <td>UPDATE_GEMSPEC</td>
1.156 leot 13958: </tr>
13959: <tr>
1.226 gutterid 13960: <td>UPDATE_TARGET</td>
1.229 gutterid 13961: <td>URI</td>
1.156 leot 13962: </tr>
13963: <tr>
1.226 gutterid 13964: <td>USERGROUP_PHASE</td>
1.229 gutterid 13965: <td>USERPPP_GROUP</td>
1.156 leot 13966: </tr>
13967: <tr>
1.226 gutterid 13968: <td>USER_SPECIFIC_PKGS</td>
1.229 gutterid 13969: <td>USE_ABI_DEPENDS</td>
1.156 leot 13970: </tr>
13971: <tr>
1.226 gutterid 13972: <td>USE_APR</td>
1.229 gutterid 13973: <td>USE_BSD_MAKEFILE</td>
1.156 leot 13974: </tr>
13975: <tr>
1.226 gutterid 13976: <td>USE_BUILTIN</td>
1.229 gutterid 13977: <td>USE_CROSS_COMPILE</td>
1.156 leot 13978: </tr>
13979: <tr>
1.226 gutterid 13980: <td>USE_CURSES</td>
1.229 gutterid 13981: <td>USE_CWRAPPERS</td>
1.156 leot 13982: </tr>
13983: <tr>
1.226 gutterid 13984: <td>USE_DB185</td>
1.229 gutterid 13985: <td>USE_FEATURES</td>
1.156 leot 13986: </tr>
13987: <tr>
1.226 gutterid 13988: <td>USE_GAMESGROUP</td>
1.229 gutterid 13989: <td>USE_GCC_RUNTIME</td>
1.205 wiz 13990: </tr>
13991: <tr>
1.226 gutterid 13992: <td>USE_IMAKE</td>
1.229 gutterid 13993: <td>USE_JAVA</td>
1.156 leot 13994: </tr>
13995: <tr>
1.226 gutterid 13996: <td>USE_JAVA2</td>
1.229 gutterid 13997: <td>USE_LANGUAGES</td>
1.156 leot 13998: </tr>
13999: <tr>
1.226 gutterid 14000: <td>USE_LIBTOOL</td>
1.229 gutterid 14001: <td>USE_NATIVE_GCC</td>
1.156 leot 14002: </tr>
14003: <tr>
1.226 gutterid 14004: <td>USE_NETBSD_REPO</td>
1.229 gutterid 14005: <td>USE_PKGSRC_GCC</td>
1.156 leot 14006: </tr>
14007: <tr>
1.226 gutterid 14008: <td>USE_PKGSRC_GCC_RUNTIME</td>
1.229 gutterid 14009: <td>USE_PKGTASKS</td>
1.156 leot 14010: </tr>
14011: <tr>
1.226 gutterid 14012: <td>USE_PKG_ADMIN_DIGEST</td>
1.229 gutterid 14013: <td>USE_RUBY_EXTCONF</td>
1.156 leot 14014: </tr>
14015: <tr>
1.226 gutterid 14016: <td>USE_RUBY_INSTALL</td>
1.229 gutterid 14017: <td>USE_RUBY_SETUP</td>
1.156 leot 14018: </tr>
14019: <tr>
1.226 gutterid 14020: <td>USE_RUBY_SETUP_PKG</td>
1.229 gutterid 14021: <td>USE_TOOLS</td>
1.156 leot 14022: </tr>
14023: <tr>
1.226 gutterid 14024: <td>UUCP_GROUP</td>
1.229 gutterid 14025: <td>UUCP_USER</td>
1.156 leot 14026: </tr>
14027: <tr>
1.226 gutterid 14028: <td>VARBASE</td>
1.229 gutterid 14029: <td>VARNAME</td>
1.156 leot 14030: </tr>
14031: <tr>
1.226 gutterid 14032: <td>VIM_EXTRA_OPTS</td>
1.229 gutterid 14033: <td>WARNING_MSG</td>
1.156 leot 14034: </tr>
14035: <tr>
1.226 gutterid 14036: <td>WCALC_CGIDIR</td>
1.229 gutterid 14037: <td>WCALC_CGIPATH</td>
1.156 leot 14038: </tr>
14039: <tr>
1.226 gutterid 14040: <td>WCALC_HTMLDIR</td>
1.229 gutterid 14041: <td>WCALC_HTMLPATH</td>
1.156 leot 14042: </tr>
14043: <tr>
1.226 gutterid 14044: <td>WDM_MANAGERS</td>
1.229 gutterid 14045: <td>WRAPPER_CC</td>
1.156 leot 14046: </tr>
14047: <tr>
1.226 gutterid 14048: <td>WRAPPER_REORDER_CMDS</td>
1.229 gutterid 14049: <td>WRKDIR</td>
1.156 leot 14050: </tr>
14051: <tr>
1.226 gutterid 14052: <td>WRKDIR_BASENAME</td>
1.229 gutterid 14053: <td>WRKDIR_LOCKTYPE</td>
1.156 leot 14054: </tr>
14055: <tr>
1.226 gutterid 14056: <td>WRKLOG</td>
1.229 gutterid 14057: <td>WRKOBJDIR</td>
1.156 leot 14058: </tr>
14059: <tr>
1.226 gutterid 14060: <td>WRKSRC</td>
1.229 gutterid 14061: <td>X10_PORT</td>
1.156 leot 14062: </tr>
14063: <tr>
1.226 gutterid 14064: <td>X11</td>
1.229 gutterid 14065: <td>X11BASE</td>
1.156 leot 14066: </tr>
14067: <tr>
1.226 gutterid 14068: <td>X11_PKGSRCDIR</td>
1.229 gutterid 14069: <td>X11_TYPE</td>
1.189 bacon 14070: </tr>
14071: <tr>
1.226 gutterid 14072: <td>X509_CERTIFICATE</td>
1.229 gutterid 14073: <td>X509_KEY</td>
1.156 leot 14074: </tr>
14075: <tr>
1.226 gutterid 14076: <td>XAW_TYPE</td>
1.229 gutterid 14077: <td>XLOCK_DEFAULT_MODE</td>
1.156 leot 14078: </tr>
14079: <tr>
1.226 gutterid 14080: <td>XMKMF</td>
1.229 gutterid 14081: <td>XMKMF_FLAGS</td>
1.156 leot 14082: </tr>
14083: <tr>
1.226 gutterid 14084: <td>XXX</td>
1.229 gutterid 14085: <td>YES</td>
1.156 leot 14086: </tr>
14087: <tr>
1.228 gutterid 14088: <td>ZSH_STATIC</td>
1.229 gutterid 14089: <td>__stdc__</td>
1.227 wiz 14090: </tr>
14091: <tr>
1.228 gutterid 14092: <td>_vargroups</td>
1.229 gutterid 14093: <td>accept</td>
1.156 leot 14094: </tr>
14095: <tr>
1.228 gutterid 14096: <td>acquire-localbase-lock</td>
1.229 gutterid 14097: <td>acquire-lock</td>
1.159 rillig 14098: </tr>
14099: <tr>
1.228 gutterid 14100: <td>add</td>
1.229 gutterid 14101: <td>added</td>
1.217 rillig 14102: </tr>
14103: <tr>
1.228 gutterid 14104: <td>administrator</td>
1.229 gutterid 14105: <td>alloca</td>
1.156 leot 14106: </tr>
14107: <tr>
1.228 gutterid 14108: <td>alternatives</td>
1.229 gutterid 14109: <td>aslr</td>
1.201 cirnatda 14110: </tr>
14111: <tr>
1.228 gutterid 14112: <td>asprintf</td>
1.229 gutterid 14113: <td>atlas</td>
1.174 leot 14114: </tr>
14115: <tr>
1.228 gutterid 14116: <td>autoconf</td>
1.229 gutterid 14117: <td>automake</td>
1.156 leot 14118: </tr>
14119: <tr>
1.228 gutterid 14120: <td>autoreconf</td>
1.229 gutterid 14121: <td>awk</td>
1.156 leot 14122: </tr>
14123: <tr>
1.228 gutterid 14124: <td>bash</td>
1.229 gutterid 14125: <td>big-endian</td>
1.174 leot 14126: </tr>
14127: <tr>
1.228 gutterid 14128: <td>bin-install</td>
1.229 gutterid 14129: <td>bind</td>
1.156 leot 14130: </tr>
14131: <tr>
1.228 gutterid 14132: <td>binpkg-list</td>
1.229 gutterid 14133: <td>blas</td>
1.161 leot 14134: </tr>
14135: <tr>
1.228 gutterid 14136: <td>bootstrap-depends</td>
1.229 gutterid 14137: <td>broken</td>
1.156 leot 14138: </tr>
14139: <tr>
1.228 gutterid 14140: <td>broken_on_platform</td>
1.229 gutterid 14141: <td>bsd</td>
1.156 leot 14142: </tr>
14143: <tr>
1.228 gutterid 14144: <td>bsd.prog.mk</td>
1.229 gutterid 14145: <td>build</td>
1.156 leot 14146: </tr>
14147: <tr>
1.228 gutterid 14148: <td>build-env</td>
1.229 gutterid 14149: <td>buildlink-directories</td>
1.177 leot 14150: </tr>
14151: <tr>
1.228 gutterid 14152: <td>buildlink-oss-soundcard-h</td>
1.229 gutterid 14153: <td>c</td>
1.159 rillig 14154: </tr>
14155: <tr>
1.228 gutterid 14156: <td>c++</td>
1.229 gutterid 14157: <td>ccache</td>
1.156 leot 14158: </tr>
14159: <tr>
1.228 gutterid 14160: <td>cce</td>
1.229 gutterid 14161: <td>cdefs</td>
1.174 leot 14162: </tr>
14163: <tr>
1.228 gutterid 14164: <td>ceil</td>
1.229 gutterid 14165: <td>changes</td>
1.156 leot 14166: </tr>
14167: <tr>
1.228 gutterid 14168: <td>changes-entry</td>
1.229 gutterid 14169: <td>changes-entry-noupdate</td>
1.156 leot 14170: </tr>
14171: <tr>
1.228 gutterid 14172: <td>check</td>
1.229 gutterid 14173: <td>check-clean</td>
1.156 leot 14174: </tr>
14175: <tr>
1.228 gutterid 14176: <td>check-files</td>
1.229 gutterid 14177: <td>check-files-clean</td>
1.156 leot 14178: </tr>
14179: <tr>
1.228 gutterid 14180: <td>check-vulnerable</td>
1.229 gutterid 14181: <td>checksum</td>
1.174 leot 14182: </tr>
14183: <tr>
1.228 gutterid 14184: <td>checksum-phase</td>
1.229 gutterid 14185: <td>clean</td>
1.156 leot 14186: </tr>
14187: <tr>
1.228 gutterid 14188: <td>clean-depends</td>
1.229 gutterid 14189: <td>cleandir</td>
1.156 leot 14190: </tr>
14191: <tr>
1.228 gutterid 14192: <td>commit</td>
1.229 gutterid 14193: <td>commit-changes-entry</td>
1.156 leot 14194: </tr>
14195: <tr>
1.228 gutterid 14196: <td>compact</td>
1.229 gutterid 14197: <td>compiler</td>
1.156 leot 14198: </tr>
14199: <tr>
1.228 gutterid 14200: <td>conf</td>
1.229 gutterid 14201: <td>config.guess</td>
1.156 leot 14202: </tr>
14203: <tr>
1.228 gutterid 14204: <td>config.sub</td>
1.229 gutterid 14205: <td>configuration</td>
1.156 leot 14206: </tr>
14207: <tr>
1.228 gutterid 14208: <td>configure</td>
1.229 gutterid 14209: <td>configure-env</td>
1.156 leot 14210: </tr>
14211: <tr>
1.228 gutterid 14212: <td>configure-help</td>
1.229 gutterid 14213: <td>configure_args</td>
1.156 leot 14214: </tr>
14215: <tr>
1.228 gutterid 14216: <td>connect</td>
1.229 gutterid 14217: <td>cos</td>
1.156 leot 14218: </tr>
14219: <tr>
1.228 gutterid 14220: <td>cputime</td>
1.229 gutterid 14221: <td>create-usergroup</td>
1.156 leot 14222: </tr>
14223: <tr>
1.228 gutterid 14224: <td>csh</td>
1.229 gutterid 14225: <td>ctf</td>
1.156 leot 14226: </tr>
14227: <tr>
1.225 gutterid 14228: <td>debug</td>
1.229 gutterid 14229: <td>declaration</td>
1.223 nia 14230: </tr>
14231: <tr>
1.225 gutterid 14232: <td>declare</td>
1.229 gutterid 14233: <td>defined</td>
1.174 leot 14234: </tr>
14235: <tr>
1.225 gutterid 14236: <td>depend</td>
1.229 gutterid 14237: <td>dependencies</td>
1.214 leot 14238: </tr>
14239: <tr>
1.225 gutterid 14240: <td>depends</td>
1.229 gutterid 14241: <td>depends-checksum</td>
1.205 wiz 14242: </tr>
14243: <tr>
1.225 gutterid 14244: <td>depends-fetch</td>
1.229 gutterid 14245: <td>deps</td>
1.161 leot 14246: </tr>
14247: <tr>
1.225 gutterid 14248: <td>describe</td>
1.229 gutterid 14249: <td>destdir</td>
1.197 leot 14250: </tr>
14251: <tr>
1.225 gutterid 14252: <td>disable</td>
1.229 gutterid 14253: <td>distclean</td>
1.156 leot 14254: </tr>
14255: <tr>
1.225 gutterid 14256: <td>distinfo</td>
1.229 gutterid 14257: <td>dl</td>
1.156 leot 14258: </tr>
14259: <tr>
1.225 gutterid 14260: <td>dlopen</td>
1.229 gutterid 14261: <td>do-buildlink</td>
1.156 leot 14262: </tr>
14263: <tr>
1.225 gutterid 14264: <td>do-clean</td>
1.229 gutterid 14265: <td>do-configure</td>
1.156 leot 14266: </tr>
14267: <tr>
1.225 gutterid 14268: <td>do-configure-post-hook</td>
1.229 gutterid 14269: <td>do-extract</td>
1.156 leot 14270: </tr>
14271: <tr>
1.225 gutterid 14272: <td>do-fetch</td>
1.229 gutterid 14273: <td>do-install</td>
1.162 rillig 14274: </tr>
14275: <tr>
1.225 gutterid 14276: <td>emul</td>
1.229 gutterid 14277: <td>emul-distinfo</td>
1.156 leot 14278: </tr>
14279: <tr>
1.225 gutterid 14280: <td>emul-fetch</td>
1.229 gutterid 14281: <td>emulation</td>
1.217 rillig 14282: </tr>
14283: <tr>
1.225 gutterid 14284: <td>emulator</td>
1.229 gutterid 14285: <td>enable</td>
1.156 leot 14286: </tr>
14287: <tr>
1.221 nia 14288: <td>endian</td>
1.229 gutterid 14289: <td>enomem</td>
1.156 leot 14290: </tr>
14291: <tr>
1.228 gutterid 14292: <td>ensurepip</td>
1.229 gutterid 14293: <td>err</td>
1.227 wiz 14294: </tr>
14295: <tr>
1.228 gutterid 14296: <td>errx</td>
1.229 gutterid 14297: <td>etc</td>
1.214 leot 14298: </tr>
14299: <tr>
1.228 gutterid 14300: <td>exp</td>
1.229 gutterid 14301: <td>extract-rpm</td>
1.156 leot 14302: </tr>
14303: <tr>
1.228 gutterid 14304: <td>fabs</td>
1.229 gutterid 14305: <td>feature</td>
1.205 wiz 14306: </tr>
14307: <tr>
1.228 gutterid 14308: <td>features</td>
1.229 gutterid 14309: <td>fetch</td>
1.197 leot 14310: </tr>
14311: <tr>
1.228 gutterid 14312: <td>fetch-list</td>
1.229 gutterid 14313: <td>follows</td>
1.156 leot 14314: </tr>
14315: <tr>
1.228 gutterid 14316: <td>forbids</td>
1.229 gutterid 14317: <td>form</td>
1.156 leot 14318: </tr>
14319: <tr>
1.228 gutterid 14320: <td>format</td>
1.229 gutterid 14321: <td>fortify</td>
1.174 leot 14322: </tr>
14323: <tr>
1.220 nia 14324: <td>fortify_source</td>
1.229 gutterid 14325: <td>friend</td>
1.217 rillig 14326: </tr>
14327: <tr>
1.225 gutterid 14328: <td>fts</td>
1.229 gutterid 14329: <td>fts_close</td>
1.223 nia 14330: </tr>
14331: <tr>
1.225 gutterid 14332: <td>fts_open</td>
1.229 gutterid 14333: <td>fts_read</td>
1.156 leot 14334: </tr>
14335: <tr>
1.225 gutterid 14336: <td>fts_set</td>
1.229 gutterid 14337: <td>gcc</td>
1.156 leot 14338: </tr>
14339: <tr>
1.225 gutterid 14340: <td>gethostbyaddr</td>
1.229 gutterid 14341: <td>gethostbyname</td>
1.156 leot 14342: </tr>
14343: <tr>
1.225 gutterid 14344: <td>gethostbyname2</td>
1.229 gutterid 14345: <td>getopt_long</td>
1.156 leot 14346: </tr>
14347: <tr>
1.225 gutterid 14348: <td>getprogname</td>
1.229 gutterid 14349: <td>getservbyname</td>
1.174 leot 14350: </tr>
14351: <tr>
1.225 gutterid 14352: <td>getservbyport</td>
1.229 gutterid 14353: <td>getservent</td>
1.156 leot 14354: </tr>
14355: <tr>
1.217 rillig 14356: <td>gettext</td>
1.229 gutterid 14357: <td>github</td>
1.174 leot 14358: </tr>
14359: <tr>
1.228 gutterid 14360: <td>gitlab</td>
1.229 gutterid 14361: <td>glob</td>
1.227 wiz 14362: </tr>
14363: <tr>
1.228 gutterid 14364: <td>gnu</td>
1.229 gutterid 14365: <td>gnu_configure_strict</td>
1.223 nia 14366: </tr>
14367: <tr>
1.228 gutterid 14368: <td>go</td>
1.229 gutterid 14369: <td>go-deps</td>
1.217 rillig 14370: </tr>
14371: <tr>
1.228 gutterid 14372: <td>golang</td>
1.229 gutterid 14373: <td>guess-license</td>
1.156 leot 14374: </tr>
14375: <tr>
1.228 gutterid 14376: <td>hashbang</td>
1.229 gutterid 14377: <td>heimdal</td>
1.159 rillig 14378: </tr>
14379: <tr>
1.223 nia 14380: <td>help</td>
1.229 gutterid 14381: <td>imake</td>
1.156 leot 14382: </tr>
14383: <tr>
1.225 gutterid 14384: <td>increment</td>
1.229 gutterid 14385: <td>indirect</td>
1.214 leot 14386: </tr>
14387: <tr>
1.225 gutterid 14388: <td>inet_aton</td>
1.229 gutterid 14389: <td>interp</td>
1.156 leot 14390: </tr>
14391: <tr>
1.225 gutterid 14392: <td>interpreter</td>
1.229 gutterid 14393: <td>intl</td>
1.205 wiz 14394: </tr>
14395: <tr>
1.225 gutterid 14396: <td>ip4</td>
1.229 gutterid 14397: <td>ip6</td>
1.197 leot 14398: </tr>
14399: <tr>
1.225 gutterid 14400: <td>ipv4</td>
1.229 gutterid 14401: <td>ipv6</td>
1.161 leot 14402: </tr>
14403: <tr>
1.225 gutterid 14404: <td>iso</td>
1.229 gutterid 14405: <td>kerberos</td>
1.156 leot 14406: </tr>
14407: <tr>
1.225 gutterid 14408: <td>krb</td>
1.229 gutterid 14409: <td>krb5</td>
1.156 leot 14410: </tr>
14411: <tr>
1.225 gutterid 14412: <td>ksh</td>
1.229 gutterid 14413: <td>lapack</td>
1.156 leot 14414: </tr>
14415: <tr>
1.225 gutterid 14416: <td>latex</td>
1.229 gutterid 14417: <td>libintl_bindtextdomain</td>
1.189 bacon 14418: </tr>
14419: <tr>
1.225 gutterid 14420: <td>libintl_gettext</td>
1.229 gutterid 14421: <td>libintl_textdomain</td>
1.189 bacon 14422: </tr>
14423: <tr>
1.225 gutterid 14424: <td>libnbcompat</td>
1.229 gutterid 14425: <td>libs</td>
1.156 leot 14426: </tr>
14427: <tr>
1.225 gutterid 14428: <td>libtool</td>
1.229 gutterid 14429: <td>licence</td>
1.177 leot 14430: </tr>
14431: <tr>
1.225 gutterid 14432: <td>license</td>
1.229 gutterid 14433: <td>lintl</td>
1.156 leot 14434: </tr>
14435: <tr>
1.225 gutterid 14436: <td>little-endian</td>
1.229 gutterid 14437: <td>lock</td>
1.174 leot 14438: </tr>
14439: <tr>
1.225 gutterid 14440: <td>locking</td>
1.229 gutterid 14441: <td>lua</td>
1.159 rillig 14442: </tr>
14443: <tr>
1.225 gutterid 14444: <td>lvalue</td>
1.229 gutterid 14445: <td>make</td>
1.156 leot 14446: </tr>
14447: <tr>
1.225 gutterid 14448: <td>makesum</td>
1.229 gutterid 14449: <td>memory</td>
1.156 leot 14450: </tr>
14451: <tr>
1.228 gutterid 14452: <td>meta</td>
1.229 gutterid 14453: <td>meta-package</td>
1.227 wiz 14454: </tr>
14455: <tr>
1.228 gutterid 14456: <td>meta_package</td>
1.229 gutterid 14457: <td>mit-krb5</td>
1.156 leot 14458: </tr>
14459: <tr>
1.228 gutterid 14460: <td>mk.conf</td>
1.229 gutterid 14461: <td>mkl</td>
1.156 leot 14462: </tr>
14463: <tr>
1.228 gutterid 14464: <td>mount</td>
1.229 gutterid 14465: <td>move</td>
1.177 leot 14466: </tr>
14467: <tr>
1.228 gutterid 14468: <td>moved</td>
1.229 gutterid 14469: <td>mprotect</td>
1.159 rillig 14470: </tr>
14471: <tr>
1.228 gutterid 14472: <td>mremap</td>
1.229 gutterid 14473: <td>nb</td>
1.226 gutterid 14474: </tr>
14475: <tr>
1.228 gutterid 14476: <td>nbcompat</td>
1.229 gutterid 14477: <td>netlib</td>
1.156 leot 14478: </tr>
14479: <tr>
1.228 gutterid 14480: <td>node</td>
1.229 gutterid 14481: <td>node.js</td>
1.156 leot 14482: </tr>
14483: <tr>
1.228 gutterid 14484: <td>nodejs</td>
1.229 gutterid 14485: <td>obstack</td>
1.218 nia 14486: </tr>
14487: <tr>
1.228 gutterid 14488: <td>obstack_ptr_grow</td>
1.229 gutterid 14489: <td>occurs</td>
1.218 nia 14490: </tr>
14491: <tr>
1.228 gutterid 14492: <td>only</td>
1.229 gutterid 14493: <td>openblas</td>
1.205 wiz 14494: </tr>
14495: <tr>
1.228 gutterid 14496: <td>options</td>
1.229 gutterid 14497: <td>options.mk</td>
1.156 leot 14498: </tr>
14499: <tr>
1.228 gutterid 14500: <td>order</td>
1.229 gutterid 14501: <td>override</td>
1.161 leot 14502: </tr>
14503: <tr>
1.228 gutterid 14504: <td>override-intltool</td>
1.229 gutterid 14505: <td>override-message-intltool</td>
1.156 leot 14506: </tr>
14507: <tr>
1.228 gutterid 14508: <td>package</td>
1.229 gutterid 14509: <td>parallel</td>
1.156 leot 14510: </tr>
14511: <tr>
1.228 gutterid 14512: <td>path</td>
1.229 gutterid 14513: <td>pax</td>
1.156 leot 14514: </tr>
14515: <tr>
1.228 gutterid 14516: <td>paxctl</td>
1.229 gutterid 14517: <td>pbulk-index</td>
1.156 leot 14518: </tr>
14519: <tr>
1.228 gutterid 14520: <td>pc</td>
1.229 gutterid 14521: <td>perl</td>
1.156 leot 14522: </tr>
14523: <tr>
1.228 gutterid 14524: <td>perl5</td>
1.229 gutterid 14525: <td>perms</td>
1.156 leot 14526: </tr>
14527: <tr>
1.228 gutterid 14528: <td>php</td>
1.229 gutterid 14529: <td>pkg-build-options</td>
1.156 leot 14530: </tr>
14531: <tr>
1.228 gutterid 14532: <td>pkg-config</td>
1.229 gutterid 14533: <td>pkg_build_options</td>
1.156 leot 14534: </tr>
14535: <tr>
1.228 gutterid 14536: <td>platform</td>
1.229 gutterid 14537: <td>plist</td>
1.156 leot 14538: </tr>
14539: <tr>
1.228 gutterid 14540: <td>post-extract</td>
1.229 gutterid 14541: <td>post-fetch</td>
1.156 leot 14542: </tr>
14543: <tr>
1.228 gutterid 14544: <td>post-wrapper</td>
1.229 gutterid 14545: <td>pre-build-checks-hook</td>
1.156 leot 14546: </tr>
14547: <tr>
1.228 gutterid 14548: <td>pre-configure</td>
1.229 gutterid 14549: <td>pre-configure-checks-hook</td>
1.156 leot 14550: </tr>
14551: <tr>
1.228 gutterid 14552: <td>pre-extract</td>
1.229 gutterid 14553: <td>pre-fetch</td>
1.156 leot 14554: </tr>
14555: <tr>
1.228 gutterid 14556: <td>print-go-deps</td>
1.229 gutterid 14557: <td>print-plist</td>
1.174 leot 14558: </tr>
14559: <tr>
1.228 gutterid 14560: <td>print-summary-data</td>
1.229 gutterid 14561: <td>privileged-install-hook</td>
1.156 leot 14562: </tr>
14563: <tr>
1.228 gutterid 14564: <td>pypi</td>
1.229 gutterid 14565: <td>python</td>
1.156 leot 14566: </tr>
14567: <tr>
1.228 gutterid 14568: <td>r</td>
1.229 gutterid 14569: <td>readme-all</td>
1.156 leot 14570: </tr>
14571: <tr>
1.228 gutterid 14572: <td>recursive</td>
1.229 gutterid 14573: <td>recv</td>
1.156 leot 14574: </tr>
14575: <tr>
1.228 gutterid 14576: <td>recvfrom</td>
1.229 gutterid 14577: <td>regcomp</td>
1.156 leot 14578: </tr>
14579: <tr>
1.228 gutterid 14580: <td>release-localbase-lock</td>
1.229 gutterid 14581: <td>release-lock</td>
1.174 leot 14582: </tr>
14583: <tr>
1.228 gutterid 14584: <td>relro</td>
1.229 gutterid 14585: <td>remove</td>
1.174 leot 14586: </tr>
14587: <tr>
1.228 gutterid 14588: <td>removed</td>
1.229 gutterid 14589: <td>rename</td>
1.156 leot 14590: </tr>
14591: <tr>
1.228 gutterid 14592: <td>renamed</td>
1.229 gutterid 14593: <td>reorder</td>
1.226 gutterid 14594: </tr>
14595: <tr>
1.228 gutterid 14596: <td>replace</td>
1.229 gutterid 14597: <td>replace_interpreter</td>
1.226 gutterid 14598: </tr>
14599: <tr>
1.228 gutterid 14600: <td>reproducible</td>
1.229 gutterid 14601: <td>resolv</td>
1.156 leot 14602: </tr>
14603: <tr>
1.228 gutterid 14604: <td>root</td>
1.229 gutterid 14605: <td>ruby</td>
1.156 leot 14606: </tr>
14607: <tr>
1.228 gutterid 14608: <td>send</td>
1.229 gutterid 14609: <td>sendfile</td>
1.156 leot 14610: </tr>
14611: <tr>
1.228 gutterid 14612: <td>sendto</td>
1.229 gutterid 14613: <td>setenv</td>
1.174 leot 14614: </tr>
14615: <tr>
1.228 gutterid 14616: <td>setgid</td>
1.229 gutterid 14617: <td>setprogname</td>
1.156 leot 14618: </tr>
14619: <tr>
1.228 gutterid 14620: <td>setuid</td>
1.229 gutterid 14621: <td>sh</td>
1.156 leot 14622: </tr>
14623: <tr>
1.228 gutterid 14624: <td>shebang</td>
1.229 gutterid 14625: <td>show</td>
1.156 leot 14626: </tr>
14627: <tr>
1.228 gutterid 14628: <td>show-all</td>
1.229 gutterid 14629: <td>show-build-defs</td>
1.156 leot 14630: </tr>
14631: <tr>
1.228 gutterid 14632: <td>show-depends</td>
1.229 gutterid 14633: <td>show-depends-dirs</td>
1.181 rillig 14634: </tr>
14635: <tr>
1.228 gutterid 14636: <td>show-depends-pkgpaths</td>
1.229 gutterid 14637: <td>show-depends-recursive</td>
1.156 leot 14638: </tr>
14639: <tr>
1.228 gutterid 14640: <td>show-deps</td>
1.229 gutterid 14641: <td>show-distfiles</td>
1.222 gutterid 14642: </tr>
14643: <tr>
1.228 gutterid 14644: <td>show-downlevel</td>
1.229 gutterid 14645: <td>show-subdir-var</td>
1.223 nia 14646: </tr>
14647: <tr>
1.228 gutterid 14648: <td>show-tools</td>
1.229 gutterid 14649: <td>show-var</td>
1.156 leot 14650: </tr>
14651: <tr>
1.228 gutterid 14652: <td>show-vars</td>
1.229 gutterid 14653: <td>snprintf</td>
1.156 leot 14654: </tr>
14655: <tr>
1.228 gutterid 14656: <td>socket</td>
1.229 gutterid 14657: <td>ssp</td>
1.156 leot 14658: </tr>
14659: <tr>
1.228 gutterid 14660: <td>st_mode</td>
1.229 gutterid 14661: <td>stage-install</td>
1.156 leot 14662: </tr>
14663: <tr>
1.228 gutterid 14664: <td>strcasestr</td>
1.229 gutterid 14665: <td>strict</td>
1.174 leot 14666: </tr>
14667: <tr>
1.228 gutterid 14668: <td>strip</td>
1.229 gutterid 14669: <td>strndup</td>
1.156 leot 14670: </tr>
14671: <tr>
1.228 gutterid 14672: <td>strnlen</td>
1.229 gutterid 14673: <td>strsep</td>
1.156 leot 14674: </tr>
14675: <tr>
1.228 gutterid 14676: <td>subst</td>
1.229 gutterid 14677: <td>substitutions</td>
1.162 rillig 14678: </tr>
14679: <tr>
1.226 gutterid 14680: <td>sun</td>
1.229 gutterid 14681: <td>sunpro</td>
1.214 leot 14682: </tr>
14683: <tr>
1.226 gutterid 14684: <td>sunwspro</td>
1.229 gutterid 14685: <td>symlink</td>
1.212 wiz 14686: </tr>
14687: <tr>
1.228 gutterid 14688: <td>test</td>
1.229 gutterid 14689: <td>test-env</td>
1.227 wiz 14690: </tr>
14691: <tr>
1.228 gutterid 14692: <td>tex</td>
1.229 gutterid 14693: <td>texlive</td>
1.223 nia 14694: </tr>
14695: <tr>
1.228 gutterid 14696: <td>tmp</td>
1.229 gutterid 14697: <td>todo</td>
1.161 leot 14698: </tr>
14699: <tr>
1.228 gutterid 14700: <td>tool</td>
1.229 gutterid 14701: <td>tools</td>
1.156 leot 14702: </tr>
14703: <tr>
1.228 gutterid 14704: <td>tools-libtool-m4-override</td>
1.229 gutterid 14705: <td>transitive</td>
1.156 leot 14706: </tr>
14707: <tr>
1.228 gutterid 14708: <td>type</td>
1.229 gutterid 14709: <td>ulimit</td>
1.156 leot 14710: </tr>
14711: <tr>
1.228 gutterid 14712: <td>undefined</td>
1.229 gutterid 14713: <td>undo-replace</td>
1.156 leot 14714: </tr>
14715: <tr>
1.228 gutterid 14716: <td>unlimit</td>
1.229 gutterid 14717: <td>unprivileged</td>
1.156 leot 14718: </tr>
14719: <tr>
1.228 gutterid 14720: <td>unprivileged-install-hook</td>
1.229 gutterid 14721: <td>unstripped</td>
1.156 leot 14722: </tr>
14723: <tr>
1.228 gutterid 14724: <td>update</td>
1.229 gutterid 14725: <td>updated</td>
1.156 leot 14726: </tr>
14727: <tr>
1.228 gutterid 14728: <td>upload</td>
1.229 gutterid 14729: <td>upload-distfiles</td>
1.156 leot 14730: </tr>
14731: <tr>
1.228 gutterid 14732: <td>use_tools</td>
1.229 gutterid 14733: <td>user</td>
1.156 leot 14734: </tr>
14735: <tr>
1.228 gutterid 14736: <td>utimes</td>
1.229 gutterid 14737: <td>vasprintf</td>
1.156 leot 14738: </tr>
14739: <tr>
1.228 gutterid 14740: <td>verbose</td>
1.229 gutterid 14741: <td>vsnprintf</td>
1.156 leot 14742: </tr>
14743: <tr>
1.228 gutterid 14744: <td>warn</td>
1.229 gutterid 14745: <td>warning</td>
1.156 leot 14746: </tr>
14747: <tr>
1.228 gutterid 14748: <td>warnings</td>
1.229 gutterid 14749: <td>warnx</td>
1.156 leot 14750: </tr>
14751: <tr>
1.228 gutterid 14752: <td>wattr_off</td>
1.229 gutterid 14753: <td>wattr_on</td>
1.156 leot 14754: </tr>
14755: <tr>
1.228 gutterid 14756: <td>work</td>
1.229 gutterid 14757: <td>wrapper</td>
1.156 leot 14758: </tr>
14759: <tr>
1.174 leot 14760: <td>wrkdir</td>
1.229 gutterid 14761: <td> </td>
1.156 leot 14762: </tr>
14763: </table>
1.154 rillig 14764: </div>
14765: <div class="appendix">
14766: <div class="titlepage"><div><div><h1 class="title">
1.207 leot 14767: <a name="editing"></a>Appendix F. Editing guidelines for the pkgsrc guide</h1></div></div></div>
1.1 dsieger 14768: <div class="toc">
14769: <p><b>Table of Contents</b></p>
1.100 leot 14770: <dl class="toc">
1.207 leot 14771: <dt><span class="sect1"><a href="#targets">F.1. Make targets</a></span></dt>
14772: <dt><span class="sect1"><a href="#procedure">F.2. Procedure</a></span></dt>
1.1 dsieger 14773: </dl>
14774: </div>
14775: <p>This section contains information on editing the pkgsrc
14776: guide itself.</p>
1.41 asau 14777: <div class="sect1">
1.1 dsieger 14778: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 14779: <a name="targets"></a>F.1. Make targets</h2></div></div></div>
1.1 dsieger 14780: <p>The pkgsrc guide's source code is stored in
14781: <code class="filename">pkgsrc/doc/guide/files</code>, and several files
14782: are created from it:</p>
1.41 asau 14783: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 14784: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.txt</code></p></li>
14785: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.html</code></p></li>
1.174 leot 14786: <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>
14787: <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 14788: The PDF version of the pkgsrc guide.</p></li>
1.174 leot 14789: <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 14790: PostScript version of the pkgsrc guide.</p></li>
14791: </ul></div>
14792: </div>
1.41 asau 14793: <div class="sect1">
1.1 dsieger 14794: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.207 leot 14795: <a name="procedure"></a>F.2. Procedure</h2></div></div></div>
1.1 dsieger 14796: <p>The procedure to edit the pkgsrc guide is:</p>
1.23 wiz 14797: <div class="procedure"><ol class="procedure" type="1">
1.190 bacon 14798: <li class="step"><p>Make sure you have checked out the htdocs repository
14799: into a sibling directory of your pkgsrc directory. You will need
14800: the ability to commit from both pkgsrc and htdocs.</p></li>
1.41 asau 14801: <li class="step"><p>Make sure you have the packages needed to
1.1 dsieger 14802: regenerate the pkgsrc guide (and other XML-based NetBSD
1.45 obache 14803: documentation) installed. These are automatically installed when
1.207 leot 14804: 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 14805: <li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the
1.1 dsieger 14806: right directory. All further steps will take place
14807: here.</p></li>
1.41 asau 14808: <li class="step"><p>Edit the XML file(s) in
1.1 dsieger 14809: <code class="filename">files/</code>.</p></li>
1.41 asau 14810: <li class="step"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc
1.1 dsieger 14811: guide for valid XML and to build the final output files. If you
14812: get any errors at this stage, you can just edit the files, as
14813: there are only symbolic links in the working directory, pointing
14814: to the files in <code class="filename">files/</code>.</p></li>
1.41 asau 14815: <li class="step"><p><span class="command"><strong>(cd files && cvs
1.1 dsieger 14816: commit)</strong></span></p></li>
1.41 asau 14817: <li class="step"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to
1.1 dsieger 14818: regenerate the output files with the proper RCS
14819: Ids.</p></li>
1.41 asau 14820: <li class="step">
1.10 hubertf 14821: <p>Run <span class="command"><strong>bmake regen</strong></span> to install and
1.1 dsieger 14822: commit the files in both <code class="filename">pkgsrc/doc</code> and
14823: <code class="filename">htdocs</code>.</p>
1.41 asau 14824: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 14825: <h3 class="title">Note</h3>
14826: <p>If you have added, removed or renamed some chapters,
1.10 hubertf 14827: you need to synchronize them using <span class="command"><strong>cvs add</strong></span> or
14828: <span class="command"><strong>cvs delete</strong></span> in the htdocs
1.1 dsieger 14829: directory.</p>
14830: </div>
14831: </li>
14832: </ol></div>
14833: </div>
14834: </div>
14835: </div></body>
14836: </html>
CVSweb <webmaster@jp.NetBSD.org>