Annotation of htdocs/docs/pkgsrc/pkgsrc.html, revision 1.101
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.84 wiz 33: <div><p class="copyright">Copyright © 1994-2015 The NetBSD Foundation, Inc</p></div>
34: <div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.28 2015/01/01 05:19:02 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>
63: <dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
64: <dd><dl>
65: <dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
66: <dd><dl>
1.51 asau 67: <dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
1.23 wiz 68: <dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
1.1 dsieger 69: </dl></dd>
70: <dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
71: <dd><dl>
72: <dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
73: <dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
74: </dl></dd>
75: </dl></dd>
76: <dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt>
77: <dd><dl>
78: <dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt>
79: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
80: <dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
81: <dd><dl>
1.45 obache 82: <dt><span class="sect2"><a href="#cygwin">3.3.1. Cygwin</a></span></dt>
83: <dt><span class="sect2"><a href="#darwin">3.3.2. Darwin (Mac OS X)</a></span></dt>
84: <dt><span class="sect2"><a href="#freebsd">3.3.3. FreeBSD</a></span></dt>
1.58 ryoon 85: <dt><span class="sect2"><a href="#gnukfreebsd">3.3.4. GNU/kFreeBSD</a></span></dt>
86: <dt><span class="sect2"><a href="#interix">3.3.5. Interix</a></span></dt>
87: <dt><span class="sect2"><a href="#irix">3.3.6. IRIX</a></span></dt>
88: <dt><span class="sect2"><a href="#linux">3.3.7. Linux</a></span></dt>
89: <dt><span class="sect2"><a href="#mirbsd">3.3.8. MirBSD</a></span></dt>
90: <dt><span class="sect2"><a href="#openbsd">3.3.9. OpenBSD</a></span></dt>
91: <dt><span class="sect2"><a href="#solaris">3.3.10. Solaris</a></span></dt>
1.1 dsieger 92: </dl></dd>
93: </dl></dd>
94: <dt><span class="chapter"><a href="#using">4. Using pkgsrc</a></span></dt>
95: <dd><dl>
96: <dt><span class="sect1"><a href="#using-pkg">4.1. Using binary packages</a></span></dt>
97: <dd><dl>
98: <dt><span class="sect2"><a href="#finding-binary-packages">4.1.1. Finding binary packages</a></span></dt>
99: <dt><span class="sect2"><a href="#installing-binary-packages">4.1.2. Installing binary packages</a></span></dt>
100: <dt><span class="sect2"><a href="#using.pkg_delete">4.1.3. Deinstalling packages</a></span></dt>
101: <dt><span class="sect2"><a href="#using.pkg_info">4.1.4. Getting information about installed packages</a></span></dt>
102: <dt><span class="sect2"><a href="#vulnerabilities">4.1.5. Checking for security vulnerabilities in installed packages</a></span></dt>
103: <dt><span class="sect2"><a href="#pkg_versions">4.1.6. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
104: <dt><span class="sect2"><a href="#using.pkg_admin">4.1.7. Other administrative functions</a></span></dt>
105: <dt><span class="sect2"><a href="#a-word-of-warning">4.1.8. A word of warning</a></span></dt>
106: </dl></dd>
107: <dt><span class="sect1"><a href="#building-packages-from-source">4.2. Building packages from source</a></span></dt>
108: <dd><dl>
109: <dt><span class="sect2"><a href="#requirements">4.2.1. Requirements</a></span></dt>
110: <dt><span class="sect2"><a href="#fetching-distfiles">4.2.2. Fetching distfiles</a></span></dt>
111: <dt><span class="sect2"><a href="#how-to-build-and-install">4.2.3. How to build and install</a></span></dt>
112: </dl></dd>
113: </dl></dd>
114: <dt><span class="chapter"><a href="#configuring">5. Configuring pkgsrc</a></span></dt>
115: <dd><dl>
116: <dt><span class="sect1"><a href="#general-configuration">5.1. General configuration</a></span></dt>
117: <dt><span class="sect1"><a href="#variables-affecting-build">5.2. Variables affecting the build process</a></span></dt>
1.9 rillig 118: <dt><span class="sect1"><a href="#variables-affecting-installation">5.3. Variables affecting the installation process</a></span></dt>
1.4 rillig 119: <dt><span class="sect1"><a href="#conf.compiler">5.4. Selecting and configuring the compiler</a></span></dt>
1.1 dsieger 120: <dd><dl>
1.4 rillig 121: <dt><span class="sect2"><a href="#selecting-the-compiler">5.4.1. Selecting the compiler</a></span></dt>
1.23 wiz 122: <dt><span class="sect2"><a href="#conf.cflags">5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
123: <dt><span class="sect2"><a href="#conf.ldflags">5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 124: </dl></dd>
1.4 rillig 125: <dt><span class="sect1"><a href="#developer-advanced-settings">5.5. Developer/advanced settings</a></span></dt>
126: <dt><span class="sect1"><a href="#selecting-build-options">5.6. Selecting Build Options</a></span></dt>
1.1 dsieger 127: </dl></dd>
128: <dt><span class="chapter"><a href="#binary">6. Creating binary packages</a></span></dt>
129: <dd><dl>
130: <dt><span class="sect1"><a href="#building-a-single-binary-package">6.1. Building a single binary package</a></span></dt>
131: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">6.2. Settings for creation of binary packages</a></span></dt>
1.6 rillig 132: </dl></dd>
133: <dt><span class="chapter"><a href="#bulk">7. Creating binary packages for everything in pkgsrc (bulk
134: builds)</a></span></dt>
1.1 dsieger 135: <dd><dl>
1.71 wiz 136: <dt><span class="sect1"><a href="#bulk.pre">7.1. Preparations</a></span></dt>
137: <dt><span class="sect1"><a href="#bulk.pbulk">7.2. Running a pbulk-style bulk build</a></span></dt>
138: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">7.2.1. Configuration</a></span></dt></dl></dd>
139: <dt><span class="sect1"><a href="#bulk.req">7.3. Requirements of a full bulk build</a></span></dt>
1.66 asau 140: <dt><span class="sect1"><a href="#creating-cdroms">7.4. Creating a multiple CD-ROM packages collection</a></span></dt>
141: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">7.4.1. Example of cdpack</a></span></dt></dl></dd>
1.6 rillig 142: </dl></dd>
143: <dt><span class="chapter"><a href="#files">8. Directory layout of the installed files</a></span></dt>
144: <dd><dl>
1.23 wiz 145: <dt><span class="sect1"><a href="#files.localbase">8.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
146: <dt><span class="sect1"><a href="#files.varbase">8.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
1.6 rillig 147: </dl></dd>
148: <dt><span class="chapter"><a href="#faq">9. Frequently Asked Questions</a></span></dt>
149: <dd><dl>
150: <dt><span class="sect1"><a href="#mailing-list-pointers">9.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
1.84 wiz 151: <dt><span class="sect1"><a href="#faq-pkgtools">9.2. Utilities for package management (pkgtools)</a></span></dt>
152: <dt><span class="sect1"><a href="#non-root-pkgsrc">9.3. How to use pkgsrc as non-root</a></span></dt>
153: <dt><span class="sect1"><a href="#resume-transfers">9.4. How to resume transfers when fetching distfiles?</a></span></dt>
154: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">9.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
155: <dt><span class="sect1"><a href="#fetch-behind-firewall">9.6. How to fetch files from behind a firewall</a></span></dt>
156: <dt><span class="sect1"><a href="#fetch-https">9.7. How to fetch files from HTTPS sites</a></span></dt>
157: <dt><span class="sect1"><a href="#passive-ftp">9.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
158: <dt><span class="sect1"><a href="#fetching-all-distfiles">9.9. How to fetch all distfiles at once</a></span></dt>
159: <dt><span class="sect1"><a href="#tmac.andoc-missing">9.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 160: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.84 wiz 161: <dt><span class="sect1"><a href="#bsd.own.mk-missing">9.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
162: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">9.12. Using 'sudo' with pkgsrc</a></span></dt>
163: <dt><span class="sect1"><a href="#faq.conf">9.13. How do I change the location of configuration files?</a></span></dt>
164: <dt><span class="sect1"><a href="#audit-packages">9.14. Automated security checks</a></span></dt>
165: <dt><span class="sect1"><a href="#ufaq-cflags">9.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
166: <dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build. What shall I do?</a></span></dt>
167: <dt><span class="sect1"><a href="#faq.rcs-conflicts">9.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 168: </dl></dd>
169: </dl></dd>
170: <dt><span class="part"><a href="#developers-guide">II. The pkgsrc developer's guide</a></span></dt>
171: <dd><dl>
1.6 rillig 172: <dt><span class="chapter"><a href="#creating">10. Creating a new pkgsrc package from scratch</a></span></dt>
1.1 dsieger 173: <dd><dl>
1.6 rillig 174: <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
1.1 dsieger 175: <dd><dl>
1.6 rillig 176: <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
1.66 asau 177: <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE3 applications</a></span></dt>
1.17 imil 178: <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
1.1 dsieger 179: </dl></dd>
1.6 rillig 180: <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
181: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
182: </dl></dd>
183: <dt><span class="chapter"><a href="#components">11. Package components - files, directories and contents</a></span></dt>
184: <dd><dl>
1.23 wiz 185: <dt><span class="sect1"><a href="#components.Makefile">11.1. <code class="filename">Makefile</code></a></span></dt>
186: <dt><span class="sect1"><a href="#components.distinfo">11.2. <code class="filename">distinfo</code></a></span></dt>
1.6 rillig 187: <dt><span class="sect1"><a href="#components.patches">11.3. patches/*</a></span></dt>
188: <dd><dl>
189: <dt><span class="sect2"><a href="#components.patch.structure">11.3.1. Structure of a single patch file</a></span></dt>
190: <dt><span class="sect2"><a href="#components.patches.caveats">11.3.2. Creating patch files</a></span></dt>
191: <dt><span class="sect2"><a href="#components.patches.sources">11.3.3. Sources where the patch files come from</a></span></dt>
192: <dt><span class="sect2"><a href="#components.patches.guidelines">11.3.4. Patching guidelines</a></span></dt>
193: <dt><span class="sect2"><a href="#components.patches.feedback">11.3.5. Feedback to the author</a></span></dt>
194: </dl></dd>
195: <dt><span class="sect1"><a href="#other-mandatory-files">11.4. Other mandatory files</a></span></dt>
196: <dt><span class="sect1"><a href="#components.optional">11.5. Optional files</a></span></dt>
197: <dd><dl>
198: <dt><span class="sect2"><a href="#components.optional.bin">11.5.1. Files affecting the binary package</a></span></dt>
199: <dt><span class="sect2"><a href="#components.optional.build">11.5.2. Files affecting the build process</a></span></dt>
200: <dt><span class="sect2"><a href="#components.optional.none">11.5.3. Files affecting nothing at all</a></span></dt>
201: </dl></dd>
1.23 wiz 202: <dt><span class="sect1"><a href="#work-dir">11.6. <code class="filename">work*</code></a></span></dt>
203: <dt><span class="sect1"><a href="#files-dir">11.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 204: </dl></dd>
1.23 wiz 205: <dt><span class="chapter"><a href="#makefile">12. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 206: <dd><dl>
207: <dt><span class="sect1"><a href="#makefile.style">12.1. Caveats</a></span></dt>
1.23 wiz 208: <dt><span class="sect1"><a href="#makefile.variables">12.2. <code class="filename">Makefile</code> variables</a></span></dt>
1.6 rillig 209: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">12.2.1. Naming conventions</a></span></dt></dl></dd>
210: <dt><span class="sect1"><a href="#makefile.code">12.3. Code snippets</a></span></dt>
211: <dd><dl>
212: <dt><span class="sect2"><a href="#adding-to-list">12.3.1. Adding things to a list</a></span></dt>
213: <dt><span class="sect2"><a href="#converting-internal-to-external">12.3.2. Converting an internal list into an external list</a></span></dt>
214: <dt><span class="sect2"><a href="#passing-variable-to-shell">12.3.3. Passing variables to a shell command</a></span></dt>
215: <dt><span class="sect2"><a href="#quoting-guideline">12.3.4. Quoting guideline</a></span></dt>
216: <dt><span class="sect2"><a href="#bsd-make-bug-workaround">12.3.5. Workaround for a bug in BSD Make</a></span></dt>
217: </dl></dd>
218: </dl></dd>
219: <dt><span class="chapter"><a href="#plist">13. PLIST issues</a></span></dt>
220: <dd><dl>
221: <dt><span class="sect1"><a href="#rcs-id">13.1. RCS ID</a></span></dt>
1.23 wiz 222: <dt><span class="sect1"><a href="#automatic-plist-generation">13.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
223: <dt><span class="sect1"><a href="#print-PLIST">13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
1.6 rillig 224: <dt><span class="sect1"><a href="#plist.misc">13.4. Variable substitution in PLIST</a></span></dt>
225: <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt>
1.23 wiz 226: <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
1.6 rillig 227: <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt>
1.86 wiz 228: <dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt>
229: <dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt>
1.6 rillig 230: </dl></dd>
231: <dt><span class="chapter"><a href="#buildlink">14. Buildlink methodology</a></span></dt>
232: <dd><dl>
233: <dt><span class="sect1"><a href="#converting-to-buildlink3">14.1. Converting packages to use buildlink3</a></span></dt>
1.23 wiz 234: <dt><span class="sect1"><a href="#creating-buildlink3.mk">14.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 235: <dd><dl>
236: <dt><span class="sect2"><a href="#anatomy-of-bl3">14.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
1.26 wiz 237: <dt><span class="sect2"><a href="#updating-buildlink-depends">14.2.2. Updating
238: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
239: and
240: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
241: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 242: </dl></dd>
1.23 wiz 243: <dt><span class="sect1"><a href="#writing-builtin.mk">14.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.6 rillig 244: <dd><dl>
1.23 wiz 245: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">14.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
1.6 rillig 246: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">14.3.2. Global preferences for native or pkgsrc software</a></span></dt>
247: </dl></dd>
248: </dl></dd>
249: <dt><span class="chapter"><a href="#pkginstall">15. The pkginstall framework</a></span></dt>
250: <dd><dl>
251: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">15.1. Files and directories outside the installation prefix</a></span></dt>
252: <dd><dl>
253: <dt><span class="sect2"><a href="#dirs-outside-prefix">15.1.1. Directory manipulation</a></span></dt>
254: <dt><span class="sect2"><a href="#files-outside-prefix">15.1.2. File manipulation</a></span></dt>
255: </dl></dd>
256: <dt><span class="sect1"><a href="#conf-files">15.2. Configuration files</a></span></dt>
257: <dd><dl>
1.23 wiz 258: <dt><span class="sect2"><a href="#conf-files-sysconfdir">15.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
1.6 rillig 259: <dt><span class="sect2"><a href="#conf-files-configure">15.2.2. Telling the software where configuration files are</a></span></dt>
260: <dt><span class="sect2"><a href="#conf-files-patching">15.2.3. Patching installations</a></span></dt>
261: <dt><span class="sect2"><a href="#conf-files-disable">15.2.4. Disabling handling of configuration files</a></span></dt>
262: </dl></dd>
263: <dt><span class="sect1"><a href="#rcd-scripts">15.3. System startup scripts</a></span></dt>
264: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">15.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
265: <dt><span class="sect1"><a href="#users-and-groups">15.4. System users and groups</a></span></dt>
266: <dt><span class="sect1"><a href="#shells">15.5. System shells</a></span></dt>
267: <dd><dl><dt><span class="sect2"><a href="#shells-disable">15.5.1. Disabling shell registration</a></span></dt></dl></dd>
268: <dt><span class="sect1"><a href="#fonts">15.6. Fonts</a></span></dt>
269: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">15.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
270: </dl></dd>
271: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
272: <dd><dl>
273: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
1.23 wiz 274: <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>
1.6 rillig 275: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
1.7 rillig 276: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 277: </dl></dd>
278: <dt><span class="chapter"><a href="#build">17. The build process</a></span></dt>
279: <dd><dl>
280: <dt><span class="sect1"><a href="#build.intro">17.1. Introduction</a></span></dt>
281: <dt><span class="sect1"><a href="#build.prefix">17.2. Program location</a></span></dt>
282: <dt><span class="sect1"><a href="#build.builddirs">17.3. Directories used during the build process</a></span></dt>
283: <dt><span class="sect1"><a href="#build.running">17.4. Running a phase</a></span></dt>
1.23 wiz 284: <dt><span class="sect1"><a href="#build.fetch">17.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 285: <dd><dl>
286: <dt><span class="sect2"><a href="#build.fetch.what">17.5.1. What to fetch and where to get it from</a></span></dt>
287: <dt><span class="sect2"><a href="#build.fetch.how">17.5.2. How are the files fetched?</a></span></dt>
288: </dl></dd>
1.23 wiz 289: <dt><span class="sect1"><a href="#build.checksum">17.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
290: <dt><span class="sect1"><a href="#build.extract">17.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
291: <dt><span class="sect1"><a href="#build.patch">17.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
292: <dt><span class="sect1"><a href="#build.tools">17.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
293: <dt><span class="sect1"><a href="#build.wrapper">17.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
294: <dt><span class="sect1"><a href="#build.configure">17.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
295: <dt><span class="sect1"><a href="#build.build">17.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
296: <dt><span class="sect1"><a href="#build.test">17.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
297: <dt><span class="sect1"><a href="#build.install">17.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
298: <dt><span class="sect1"><a href="#build.package">17.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
1.6 rillig 299: <dt><span class="sect1"><a href="#build.clean">17.16. Cleaning up</a></span></dt>
300: <dt><span class="sect1"><a href="#build.helpful-targets">17.17. Other helpful targets</a></span></dt>
301: </dl></dd>
302: <dt><span class="chapter"><a href="#tools">18. Tools needed for building or running</a></span></dt>
303: <dd><dl>
304: <dt><span class="sect1"><a href="#pkgsrc-tools">18.1. Tools for pkgsrc builds</a></span></dt>
305: <dt><span class="sect1"><a href="#package-tools">18.2. Tools needed by packages</a></span></dt>
306: <dt><span class="sect1"><a href="#platform-tools">18.3. Tools provided by platforms</a></span></dt>
307: <dt><span class="sect1"><a href="#tools.questions">18.4. Questions regarding the tools</a></span></dt>
308: </dl></dd>
309: <dt><span class="chapter"><a href="#fixes">19. Making your package work</a></span></dt>
310: <dd><dl>
311: <dt><span class="sect1"><a href="#general-operation">19.1. General operation</a></span></dt>
312: <dd><dl>
313: <dt><span class="sect2"><a href="#portability-of-packages">19.1.1. Portability of packages</a></span></dt>
1.23 wiz 314: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">19.1.2. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
1.6 rillig 315: <dt><span class="sect2"><a href="#user-interaction">19.1.3. User interaction</a></span></dt>
316: <dt><span class="sect2"><a href="#handling-licenses">19.1.4. Handling licenses</a></span></dt>
317: <dt><span class="sect2"><a href="#restricted-packages">19.1.5. Restricted packages</a></span></dt>
318: <dt><span class="sect2"><a href="#dependencies">19.1.6. Handling dependencies</a></span></dt>
319: <dt><span class="sect2"><a href="#conflicts">19.1.7. Handling conflicts with other packages</a></span></dt>
320: <dt><span class="sect2"><a href="#not-building-packages">19.1.8. Packages that cannot or should not be built</a></span></dt>
321: <dt><span class="sect2"><a href="#undeletable-packages">19.1.9. Packages which should not be deleted, once installed</a></span></dt>
322: <dt><span class="sect2"><a href="#security-handling">19.1.10. Handling packages with security problems</a></span></dt>
323: <dt><span class="sect2"><a href="#bumping-pkgrevision">19.1.11. How to handle incrementing versions when fixing an existing package</a></span></dt>
324: <dt><span class="sect2"><a href="#fixes.subst">19.1.12. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
325: </dl></dd>
1.23 wiz 326: <dt><span class="sect1"><a href="#fixes.fetch">19.2. Fixing problems in the <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 327: <dd><dl>
328: <dt><span class="sect2"><a href="#no-plain-download">19.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">19.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
1.88 tnn 330: <dt><span class="sect2"><a href="#build.fetch.github">19.2.3. Packages hosted on github.com</a></span></dt>
1.6 rillig 331: </dl></dd>
1.23 wiz 332: <dt><span class="sect1"><a href="#fixes.configure">19.3. Fixing problems in the <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
1.6 rillig 333: <dd><dl>
334: <dt><span class="sect2"><a href="#fixes.libtool">19.3.1. Shared libraries - libtool</a></span></dt>
335: <dt><span class="sect2"><a href="#using-libtool">19.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
336: <dt><span class="sect2"><a href="#autoconf-automake">19.3.3. GNU Autoconf/Automake</a></span></dt>
337: </dl></dd>
338: <dt><span class="sect1"><a href="#programming-languages">19.4. Programming languages</a></span></dt>
339: <dd><dl>
340: <dt><span class="sect2"><a href="#basic-programming-languages">19.4.1. C, C++, and Fortran</a></span></dt>
341: <dt><span class="sect2"><a href="#java-programming-language">19.4.2. Java</a></span></dt>
342: <dt><span class="sect2"><a href="#perl-scripts">19.4.3. Packages containing perl scripts</a></span></dt>
1.40 wiz 343: <dt><span class="sect2"><a href="#shell-scripts">19.4.4. Packages containing shell scripts</a></span></dt>
344: <dt><span class="sect2"><a href="#other-programming-languages">19.4.5. Other programming languages</a></span></dt>
1.6 rillig 345: </dl></dd>
1.23 wiz 346: <dt><span class="sect1"><a href="#fixes.build">19.5. Fixing problems in the <span class="emphasis"><em>build</em></span> phase</a></span></dt>
1.6 rillig 347: <dd><dl>
348: <dt><span class="sect2"><a href="#fixes.build.cpp">19.5.1. Compiling C and C++ code conditionally</a></span></dt>
349: <dt><span class="sect2"><a href="#compiler-bugs">19.5.2. How to handle compiler bugs</a></span></dt>
1.23 wiz 350: <dt><span class="sect2"><a href="#undefined-reference">19.5.3. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
1.6 rillig 351: <dt><span class="sect2"><a href="#out-of-memory">19.5.4. Running out of memory</a></span></dt>
352: </dl></dd>
1.23 wiz 353: <dt><span class="sect1"><a href="#fixes.install">19.6. Fixing problems in the <span class="emphasis"><em>install</em></span> phase</a></span></dt>
1.6 rillig 354: <dd><dl>
355: <dt><span class="sect2"><a href="#install-scripts">19.6.1. Creating needed directories</a></span></dt>
356: <dt><span class="sect2"><a href="#where-to-install-documentation">19.6.2. Where to install documentation</a></span></dt>
357: <dt><span class="sect2"><a href="#installing-score-files">19.6.3. Installing highscore files</a></span></dt>
358: <dt><span class="sect2"><a href="#destdir-support">19.6.4. Adding DESTDIR support to packages</a></span></dt>
359: <dt><span class="sect2"><a href="#hardcoded-paths">19.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
360: <dt><span class="sect2"><a href="#perl-modules">19.6.6. Packages installing perl modules</a></span></dt>
361: <dt><span class="sect2"><a href="#faq.info-files">19.6.7. Packages installing info files</a></span></dt>
362: <dt><span class="sect2"><a href="#manpages">19.6.8. Packages installing man pages</a></span></dt>
1.7 rillig 363: <dt><span class="sect2"><a href="#gconf-data-files">19.6.9. Packages installing GConf data files</a></span></dt>
1.18 snj 364: <dt><span class="sect2"><a href="#scrollkeeper-data-files">19.6.10. Packages installing scrollkeeper/rarian data files</a></span></dt>
1.6 rillig 365: <dt><span class="sect2"><a href="#x11-fonts">19.6.11. Packages installing X11 fonts</a></span></dt>
366: <dt><span class="sect2"><a href="#gtk2-modules">19.6.12. Packages installing GTK2 modules</a></span></dt>
367: <dt><span class="sect2"><a href="#sgml-xml-data">19.6.13. Packages installing SGML or XML data</a></span></dt>
368: <dt><span class="sect2"><a href="#mime-database">19.6.14. Packages installing extensions to the MIME database</a></span></dt>
369: <dt><span class="sect2"><a href="#intltool">19.6.15. Packages using intltool</a></span></dt>
370: <dt><span class="sect2"><a href="#startup-scripts">19.6.16. Packages installing startup scripts</a></span></dt>
371: <dt><span class="sect2"><a href="#tex-packages">19.6.17. Packages installing TeX modules</a></span></dt>
372: <dt><span class="sect2"><a href="#emulation-packages">19.6.18. Packages supporting running binaries in
1.1 dsieger 373: emulation</a></span></dt>
1.6 rillig 374: <dt><span class="sect2"><a href="#hicolor-theme">19.6.19. Packages installing hicolor theme icons</a></span></dt>
375: <dt><span class="sect2"><a href="#desktop-files">19.6.20. Packages installing desktop files</a></span></dt>
1.1 dsieger 376: </dl></dd>
1.6 rillig 377: <dt><span class="sect1"><a href="#punting">19.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 378: </dl></dd>
1.6 rillig 379: <dt><span class="chapter"><a href="#debug">20. Debugging</a></span></dt>
380: <dt><span class="chapter"><a href="#submit">21. Submitting and Committing</a></span></dt>
1.1 dsieger 381: <dd><dl>
1.6 rillig 382: <dt><span class="sect1"><a href="#submitting-binary-packages">21.1. Submitting binary packages</a></span></dt>
383: <dt><span class="sect1"><a href="#submitting-your-package">21.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
384: <dt><span class="sect1"><a href="#general-notes-for-changes">21.3. General notes when adding, updating, or removing packages</a></span></dt>
1.33 wiz 385: <dt><span class="sect1"><a href="#committing-importing">21.4. Committing: Adding a package to CVS</a></span></dt>
1.6 rillig 386: <dt><span class="sect1"><a href="#updating-package">21.5. Updating a package to a newer version</a></span></dt>
1.20 snj 387: <dt><span class="sect1"><a href="#renaming-package">21.6. Renaming a package in pkgsrc</a></span></dt>
388: <dt><span class="sect1"><a href="#moving-package">21.7. Moving a package in pkgsrc</a></span></dt>
1.6 rillig 389: </dl></dd>
390: <dt><span class="chapter"><a href="#devfaq">22. Frequently Asked Questions</a></span></dt>
391: <dt><span class="chapter"><a href="#gnome">23. GNOME packaging and porting</a></span></dt>
392: <dd><dl>
393: <dt><span class="sect1"><a href="#meta-packages">23.1. Meta packages</a></span></dt>
394: <dt><span class="sect1"><a href="#new-package">23.2. Packaging a GNOME application</a></span></dt>
395: <dt><span class="sect1"><a href="#full-update">23.3. Updating GNOME to a newer version</a></span></dt>
396: <dt><span class="sect1"><a href="#patching">23.4. Patching guidelines</a></span></dt>
1.1 dsieger 397: </dl></dd>
398: </dl></dd>
399: <dt><span class="part"><a href="#infrastructure">III. The pkgsrc infrastructure internals</a></span></dt>
400: <dd><dl>
1.6 rillig 401: <dt><span class="chapter"><a href="#infr.design">24. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 402: <dd><dl>
1.6 rillig 403: <dt><span class="sect1"><a href="#infr.vardef">24.1. The meaning of variable definitions</a></span></dt>
404: <dt><span class="sect1"><a href="#infr.vardef.problems">24.2. Avoiding problems before they arise</a></span></dt>
405: <dt><span class="sect1"><a href="#infr.var">24.3. Variable evaluation</a></span></dt>
1.1 dsieger 406: <dd><dl>
1.6 rillig 407: <dt><span class="sect2"><a href="#infr.var.load">24.3.1. At load time</a></span></dt>
408: <dt><span class="sect2"><a href="#infr.var.run">24.3.2. At runtime</a></span></dt>
1.1 dsieger 409: </dl></dd>
1.6 rillig 410: <dt><span class="sect1"><a href="#infr.varspec">24.4. How can variables be specified?</a></span></dt>
411: <dt><span class="sect1"><a href="#infr.design.intf">24.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 412: <dd><dl>
1.6 rillig 413: <dt><span class="sect2"><a href="#infr.design.intf.proc">24.5.1. Procedures with parameters</a></span></dt>
414: <dt><span class="sect2"><a href="#infr.design.intf.action">24.5.2. Actions taken on behalf of parameters</a></span></dt>
1.1 dsieger 415: </dl></dd>
1.6 rillig 416: <dt><span class="sect1"><a href="#infr.order">24.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 417: <dd><dl>
1.23 wiz 418: <dt><span class="sect2"><a href="#infr.order.prefs">24.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
419: <dt><span class="sect2"><a href="#infr.order.pkg">24.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.1 dsieger 420: </dl></dd>
421: </dl></dd>
1.6 rillig 422: <dt><span class="chapter"><a href="#regression">25. Regression tests</a></span></dt>
1.1 dsieger 423: <dd><dl>
1.6 rillig 424: <dt><span class="sect1"><a href="#regression.descr">25.1. The regression tests framework</a></span></dt>
425: <dt><span class="sect1"><a href="#regression.run">25.2. Running the regression tests</a></span></dt>
426: <dt><span class="sect1"><a href="#regression.new">25.3. Adding a new regression test</a></span></dt>
1.1 dsieger 427: <dd><dl>
1.6 rillig 428: <dt><span class="sect2"><a href="#regression.fun.override">25.3.1. Overridable functions</a></span></dt>
429: <dt><span class="sect2"><a href="#regression.fun.helper">25.3.2. Helper functions</a></span></dt>
1.1 dsieger 430: </dl></dd>
431: </dl></dd>
1.6 rillig 432: <dt><span class="chapter"><a href="#porting">26. Porting pkgsrc</a></span></dt>
1.1 dsieger 433: <dd><dl>
1.6 rillig 434: <dt><span class="sect1"><a href="#porting.opsys">26.1. Porting pkgsrc to a new operating system</a></span></dt>
435: <dt><span class="sect1"><a href="#porting.compiler">26.2. Adding support for a new compiler</a></span></dt>
1.1 dsieger 436: </dl></dd>
437: </dl></dd>
438: <dt><span class="appendix"><a href="#examples">A. A simple example package: bison</a></span></dt>
439: <dd><dl>
440: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
441: <dd><dl>
442: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
443: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
444: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.23 wiz 445: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with <span class="command"><strong>pkglint</strong></span></a></span></dt>
1.1 dsieger 446: </dl></dd>
447: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
448: </dl></dd>
449: <dt><span class="appendix"><a href="#logs">B. Build logs</a></span></dt>
450: <dd><dl>
451: <dt><span class="sect1"><a href="#logs.building">B.1. Building figlet</a></span></dt>
452: <dt><span class="sect1"><a href="#logs.package">B.2. Packaging figlet</a></span></dt>
453: </dl></dd>
454: <dt><span class="appendix"><a href="#ftp-layout">C. Directory layout of the pkgsrc FTP server</a></span></dt>
455: <dd><dl>
1.23 wiz 456: <dt><span class="sect1"><a href="#ftp-distfiles">C.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
457: <dt><span class="sect1"><a href="#ftp-misc">C.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
458: <dt><span class="sect1"><a href="#ftp-packages">C.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
459: <dt><span class="sect1"><a href="#ftp-reports">C.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
460: <dt><span class="sect1"><a href="#ftp-source">C.5. <code class="filename">current</code>,
461: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 462: source packages</a></span></dt>
463: </dl></dd>
464: <dt><span class="appendix"><a href="#editing">D. Editing guidelines for the pkgsrc guide</a></span></dt>
465: <dd><dl>
466: <dt><span class="sect1"><a href="#targets">D.1. Make targets</a></span></dt>
467: <dt><span class="sect1"><a href="#procedure">D.2. Procedure</a></span></dt>
468: </dl></dd>
469: </dl>
470: </div>
471: <div class="list-of-tables">
472: <p><b>List of Tables</b></p>
473: <dl>
474: <dt>1.1. <a href="#supported-platforms">Platforms supported by pkgsrc</a>
475: </dt>
1.6 rillig 476: <dt>11.1. <a href="#patch-examples">Patching examples</a>
1.1 dsieger 477: </dt>
1.6 rillig 478: <dt>23.1. <a href="#plist-handling">PLIST handling for GNOME packages</a>
1.1 dsieger 479: </dt>
480: </dl>
481: </div>
1.41 asau 482: <div class="chapter">
483: <div class="titlepage"><div><div><h1 class="title">
484: <a name="introduction"></a>Chapter 1. What is pkgsrc?</h1></div></div></div>
1.1 dsieger 485: <div class="toc">
486: <p><b>Table of Contents</b></p>
1.100 leot 487: <dl class="toc">
1.1 dsieger 488: <dt><span class="sect1"><a href="#introduction-section">1.1. Introduction</a></span></dt>
489: <dd><dl>
490: <dt><span class="sect2"><a href="#why-pkgsrc">1.1.1. Why pkgsrc?</a></span></dt>
491: <dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt>
492: </dl></dd>
493: <dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt>
494: <dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt>
495: <dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
496: <dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
497: </dl>
498: </div>
1.41 asau 499: <div class="sect1">
1.1 dsieger 500: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
501: <a name="introduction-section"></a>1.1. Introduction</h2></div></div></div>
502: <p>There is a lot of software freely available for Unix-based
503: systems, which is usually available in form of the source code. Before
504: such software can be used, it needs to be configured to the local
505: system, compiled and installed, and this is exactly what The NetBSD
506: Packages Collection (pkgsrc) does. pkgsrc also has some basic commands
507: to handle binary packages, so that not every user has to build the
508: packages for himself, which is a time-costly task.</p>
509: <p>pkgsrc currently contains several thousand packages,
510: including:</p>
1.41 asau 511: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 512: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache/README.html" target="_top"><code class="filename">www/apache</code></a> - The Apache
1.1 dsieger 513: web server</p></li>
1.79 snj 514: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html" target="_top"><code class="filename">www/firefox</code></a> - The Firefox
1.1 dsieger 515: web browser</p></li>
1.79 snj 516: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html" target="_top"><code class="filename">meta-pkgs/gnome</code></a> - The GNOME
1.1 dsieger 517: Desktop Environment</p></li>
1.79 snj 518: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html" target="_top"><code class="filename">meta-pkgs/kde3</code></a> - The K
1.1 dsieger 519: Desktop Environment</p></li>
520: </ul></div>
521: <p>...just to name a few.</p>
522: <p>pkgsrc has built-in support for handling varying dependencies,
523: such as pthreads and X11, and extended features such as IPv6 support on
524: a range of platforms.</p>
1.41 asau 525: <div class="sect2">
1.1 dsieger 526: <div class="titlepage"><div><div><h3 class="title">
527: <a name="why-pkgsrc"></a>1.1.1. Why pkgsrc?</h3></div></div></div>
528: <p>
529: pkgsrc provides the following key features:
530: </p>
1.41 asau 531: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 532: <li class="listitem"><p>Easy building of software from source as well as the creation
1.1 dsieger 533: and installation of binary packages. The source and latest
534: patches are retrieved from a master or mirror download site, checksum
535: verified, then built on your system. Support for binary-only
536: distributions is available for both native platforms and NetBSD
537: emulated platforms.</p></li>
1.23 wiz 538: <li class="listitem"><p>All packages are installed in a consistent directory tree,
1.1 dsieger 539: including binaries, libraries, man pages and other
540: documentation.</p></li>
1.23 wiz 541: <li class="listitem"><p>Package dependencies, including when performing package updates,
1.1 dsieger 542: are handled automatically. The configuration files of various
543: packages are handled automatically during updates, so local changes
544: are preserved.</p></li>
1.23 wiz 545: <li class="listitem"><p>Like NetBSD, pkgsrc is designed with portability in mind and
1.1 dsieger 546: consists of highly portable code. This allows the greatest speed of
1.25 spz 547: development when porting to a new platform. This portability also
1.1 dsieger 548: ensures that pkgsrc is <span class="emphasis"><em>consistent across all
549: platforms</em></span>.</p></li>
1.23 wiz 550: <li class="listitem"><p>The installation prefix, acceptable software licenses,
1.1 dsieger 551: international encryption requirements and build-time options for a
552: large number of packages are all set in a simple, central
553: configuration file.</p></li>
1.23 wiz 554: <li class="listitem"><p>The entire source (not including the distribution files) is
1.1 dsieger 555: freely available under a BSD license, so you may extend and adapt
556: pkgsrc to your needs. Support for local packages and patches is
557: available right out of the box, so you can configure it specifically
558: for your environment.</p></li>
559: </ul></div>
560: <p>The following principles are basic to pkgsrc:</p>
1.41 asau 561: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 562: <li class="listitem"><p><span class="quote">“<span class="quote">It should only work if it's right.</span>”</span>
1.14 jmcneill 563: — That means, if a package contains bugs, it's better to find
1.1 dsieger 564: them and to complain about them rather than to just install the package
565: and hope that it works. There are numerous checks in pkgsrc that try to
1.79 snj 566: find such bugs: Static analysis tools (<a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>), build-time checks (portability
1.1 dsieger 567: of shell scripts), and post-installation checks (installed files,
568: references to shared libraries, script interpreters).</p></li>
1.23 wiz 569: <li class="listitem"><p><span class="quote">“<span class="quote">If it works, it should work everywhere</span>”</span>
1.14 jmcneill 570: — Like NetBSD has been ported to many hardware architectures,
1.1 dsieger 571: pkgsrc has been ported to many operating systems. Care is taken that
572: packages behave the same on all platforms.</p></li>
573: </ul></div>
574: </div>
1.41 asau 575: <div class="sect2">
1.1 dsieger 576: <div class="titlepage"><div><div><h3 class="title">
577: <a name="intro.platforms"></a>1.1.2. Supported platforms</h3></div></div></div>
578: <p>pkgsrc consists of both a source distribution and a binary
579: distribution for these operating systems. After retrieving the required
580: source or binaries, you can be up and running with pkgsrc in just
581: minutes!</p>
582: <p>pkgsrc was derived from FreeBSD's ports system, and
583: initially developed for NetBSD only. Since then, pkgsrc has
584: grown a lot, and now supports the following platforms:</p>
585: <div class="table">
586: <a name="supported-platforms"></a><p class="title"><b>Table 1.1. Platforms supported by pkgsrc</b></p>
587: <div class="table-contents"><table summary="Platforms supported by pkgsrc" border="1">
588: <colgroup>
589: <col>
590: <col>
1.92 sevan 591: <col>
1.1 dsieger 592: </colgroup>
593: <thead><tr>
594: <th>Platform</th>
595: <th>Date Support Added</th>
1.92 sevan 596: <th>Notes</th>
1.1 dsieger 597: </tr></thead>
598: <tbody>
599: <tr>
1.10 hubertf 600: <td><a class="ulink" href="http://www.NetBSD.org/" target="_top">NetBSD</a></td>
1.1 dsieger 601: <td align="center">Aug 1997</td>
1.92 sevan 602: <td class="auto-generated"> </td>
1.1 dsieger 603: </tr>
604: <tr>
1.10 hubertf 605: <td><a class="ulink" href="http://wwws.sun.com/software/solaris/" target="_top">Solaris</a></td>
1.1 dsieger 606: <td align="center">Mar 1999</td>
1.93 sevan 607: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Solaris" target="_top">README.Solaris</a></td>
1.1 dsieger 608: </tr>
609: <tr>
1.10 hubertf 610: <td><a class="ulink" href="http://www.kernel.org/" target="_top">Linux</a></td>
1.1 dsieger 611: <td align="center">Jun 1999</td>
1.93 sevan 612: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Linux" target="_top">README.Linux</a></td>
1.1 dsieger 613: </tr>
614: <tr>
615: <td>
1.10 hubertf 616: <a class="ulink" href="http://developer.apple.com/darwin/" target="_top">Darwin</a>
617: (<a class="ulink" href="http://developer.apple.com/macosx/" target="_top">Mac OS X</a>)
1.1 dsieger 618: </td>
619: <td align="center">Oct 2001</td>
1.93 sevan 620: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.MacOSX" target="_top">README.MacOSX</a></td>
1.1 dsieger 621: </tr>
622: <tr>
1.10 hubertf 623: <td><a class="ulink" href="http://www.freebsd.org/" target="_top">FreeBSD</a></td>
1.1 dsieger 624: <td align="center">Nov 2002</td>
1.93 sevan 625: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.FreeBSD" target="_top">README.FreeBSD</a></td>
1.1 dsieger 626: </tr>
627: <tr>
1.10 hubertf 628: <td><a class="ulink" href="http://www.openbsd.org/" target="_top">OpenBSD</a></td>
1.1 dsieger 629: <td align="center">Nov 2002</td>
1.93 sevan 630: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OpenBSD" target="_top">README.OpenBSD</a></td>
1.1 dsieger 631: </tr>
632: <tr>
1.10 hubertf 633: <td><a class="ulink" href="http://www.sgi.com/software/irix/" target="_top">IRIX</a></td>
1.1 dsieger 634: <td align="center">Dec 2002</td>
1.92 sevan 635: <td>
1.93 sevan 636: <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX" target="_top">README.IRIX</a>
637: <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.IRIX5.3" target="_top">README.IRIX5.3</a>
1.92 sevan 638: </td>
1.1 dsieger 639: </tr>
640: <tr>
641: <td>BSD/OS</td>
642: <td align="center">Dec 2003</td>
1.92 sevan 643: <td class="auto-generated"> </td>
1.1 dsieger 644: </tr>
645: <tr>
1.10 hubertf 646: <td><a class="ulink" href="http://www-1.ibm.com/servers/aix/" target="_top">AIX</a></td>
1.1 dsieger 647: <td align="center">Dec 2003</td>
1.93 sevan 648: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.AIX" target="_top">README.AIX</a></td>
1.1 dsieger 649: </tr>
650: <tr>
651: <td>
1.10 hubertf 652: <a class="ulink" href="http://www.microsoft.com/windows/sfu/" target="_top">Interix</a>
1.1 dsieger 653: (Microsoft Windows Services for Unix)
654: </td>
655: <td align="center">Mar 2004</td>
1.93 sevan 656: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Interix" target="_top">README.Interix</a></td>
1.1 dsieger 657: </tr>
658: <tr>
1.10 hubertf 659: <td><a class="ulink" href="http://www.dragonflybsd.org/" target="_top">DragonFlyBSD</a></td>
1.1 dsieger 660: <td align="center">Oct 2004</td>
1.92 sevan 661: <td class="auto-generated"> </td>
1.1 dsieger 662: </tr>
663: <tr>
1.10 hubertf 664: <td><a class="ulink" href="http://www.tru64.org/" target="_top">OSF/1</a></td>
1.1 dsieger 665: <td align="center">Nov 2004</td>
1.93 sevan 666: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.OSF1" target="_top">README.OSF1</a></td>
1.1 dsieger 667: </tr>
668: <tr>
1.10 hubertf 669: <td><a class="ulink" href="http://www.hp.com/products1/unix/" target="_top">HP-UX</a></td>
1.1 dsieger 670: <td align="center">Apr 2007</td>
1.93 sevan 671: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.HPUX" target="_top">README.HPUX</a></td>
1.1 dsieger 672: </tr>
1.23 wiz 673: <tr>
674: <td><a class="ulink" href="http://www.haiku-os.org/" target="_top">Haiku</a></td>
675: <td align="center">Sep 2010</td>
1.93 sevan 676: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Haiku" target="_top">README.Haiku</a></td>
1.23 wiz 677: </tr>
1.45 obache 678: <tr>
679: <td><a class="ulink" href="http://www.mirbsd.org/" target="_top">MirBSD</a></td>
1.57 bsiegert 680: <td align="center">Jan 2011</td>
1.92 sevan 681: <td class="auto-generated"> </td>
1.45 obache 682: </tr>
683: <tr>
684: <td><a class="ulink" href="http://www.minix3.org/" target="_top">Minix3</a></td>
685: <td align="center">Nov 2011</td>
1.93 sevan 686: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Minix3" target="_top">README.Minix3</a></td>
1.45 obache 687: </tr>
688: <tr>
689: <td><a class="ulink" href="http://cygwin.com/" target="_top">Cygwin</a></td>
690: <td align="center">Mar 2013</td>
1.93 sevan 691: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Cygwin" target="_top">README.Cygwin</a></td>
1.45 obache 692: </tr>
1.58 ryoon 693: <tr>
694: <td><a class="ulink" href="http://www.debian.org/ports/kfreebsd-gnu/" target="_top">GNU/kFreeBSD</a></td>
695: <td align="center">Jul 2013</td>
1.93 sevan 696: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.GNUkFreeBSD" target="_top">README.GNUkFreeBSD</a></td>
1.58 ryoon 697: </tr>
1.101 ! sevan 698: <tr>
! 699: <td><a class="ulink" href="http://www.bitrig.org/" target="_top">Bitrig</a></td>
! 700: <td align="center">Jun 2014</td>
! 701: <td><a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Bitrig" target="_top">README.Bitrig</a></td>
! 702: </tr>
1.1 dsieger 703: </tbody>
704: </table></div>
705: </div>
706: <br class="table-break">
707: </div>
708: </div>
1.41 asau 709: <div class="sect1">
1.1 dsieger 710: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
711: <a name="overview"></a>1.2. Overview</h2></div></div></div>
712: <p>This document is divided into three parts. The first,
1.10 hubertf 713: <a class="link" href="#users-guide" title="Part I. The pkgsrc user's guide">The pkgsrc user's guide</a>,
1.1 dsieger 714: describes how one can use one of the packages in the Package
715: Collection, either by installing a precompiled binary package,
716: or by building one's own copy using the NetBSD package system.
1.10 hubertf 717: 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 718: package so it can be easily built by other NetBSD users without
719: knowing about the package's building details. The third part,
1.10 hubertf 720: <a class="link" href="#infrastructure" title="Part III. The pkgsrc infrastructure internals">The pkgsrc infrastructure internals</a>
1.1 dsieger 721: is intended for those who want to understand how pkgsrc is
722: implemented.</p>
723: <p>This document is available in various formats:
1.10 hubertf 724: <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 725: </div>
1.41 asau 726: <div class="sect1">
1.1 dsieger 727: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
728: <a name="terminology"></a>1.3. Terminology</h2></div></div></div>
1.23 wiz 729: <p>There has been a lot of talk about <span class="quote">“<span class="quote">ports</span>”</span>,
730: <span class="quote">“<span class="quote">packages</span>”</span>, etc. so far. Here is a description of all the
1.1 dsieger 731: terminology used within this document.</p>
1.41 asau 732: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 733: <dt><span class="term">Package</span></dt>
734: <dd><p>A set of files and building instructions
735: that describe what's necessary
736: to build a certain piece of software using
737: pkgsrc. Packages are traditionally stored under
738: <code class="filename">/usr/pkgsrc</code>.</p></dd>
739: <dt><span class="term">The NetBSD package system</span></dt>
1.23 wiz 740: <dd><p>This is the former name of <span class="quote">“<span class="quote">pkgsrc</span>”</span>. It
1.1 dsieger 741: is part of the NetBSD operating system and can be bootstrapped
742: to run on non-NetBSD operating systems as well. It handles
743: building (compiling), installing, and removing of
744: packages.</p></dd>
745: <dt><span class="term">Distfile</span></dt>
746: <dd><p>This term describes the file or files that are
747: provided by the author of the piece of software to
748: distribute his work. All the changes necessary to build on
749: NetBSD are reflected in the corresponding package. Usually
750: the distfile is in the form of a compressed tar-archive,
751: but other types are possible, too. Distfiles are usually
752: stored below
753: <code class="filename">/usr/pkgsrc/distfiles</code>.</p></dd>
754: <dt><span class="term">Port</span></dt>
755: <dd><p>This is the term used by FreeBSD and OpenBSD people
756: for what we call a package.
1.23 wiz 757: In NetBSD terminology, <span class="quote">“<span class="quote">port</span>”</span> refers to a different
1.1 dsieger 758: architecture.</p></dd>
759: <dt><span class="term">Precompiled/binary package</span></dt>
760: <dd>
761: <p>A set of binaries built with pkgsrc from a distfile
762: and stuffed together in a single <code class="filename">.tgz</code>
763: file so it can be installed on machines of the same
764: machine architecture without the need to
765: recompile. Packages are usually generated in
766: <code class="filename">/usr/pkgsrc/packages</code>; there is also
1.25 spz 767: an archive on <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/" target="_top">ftp.NetBSD.org</a>.</p>
1.23 wiz 768: <p>Sometimes, this is referred to by the term <span class="quote">“<span class="quote">package</span>”</span> too,
1.1 dsieger 769: especially in the context of precompiled packages.</p>
770: </dd>
771: <dt><span class="term">Program</span></dt>
772: <dd><p>The piece of software to be installed which will be
773: constructed from all the files in the distfile by the
774: actions defined in the corresponding package.</p></dd>
775: </dl></div>
1.41 asau 776: <div class="sect2">
1.1 dsieger 777: <div class="titlepage"><div><div><h3 class="title">
778: <a name="term.roles"></a>1.3.1. Roles involved in pkgsrc</h3></div></div></div>
1.41 asau 779: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 780: <dt><span class="term">pkgsrc users</span></dt>
781: <dd>
782: <p>The
783: pkgsrc users are people who use the packages provided by pkgsrc.
784: Typically they are system administrators. The people using the
1.23 wiz 785: software that is inside the packages (maybe called <span class="quote">“<span class="quote">end
786: users</span>”</span>) are not covered by the pkgsrc guide.</p>
1.1 dsieger 787: <p>There are two kinds of pkgsrc users: Some only want to
788: install pre-built binary packages. Others build the pkgsrc
789: packages from source, either for installing them directly or for
1.10 hubertf 790: 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 791: documentation.</p>
792: </dd>
793: <dt><span class="term">package maintainers</span></dt>
794: <dd><p>A
1.10 hubertf 795: 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 796: <dt><span class="term">infrastructure developers</span></dt>
797: <dd><p>These people are involved in all those files
798: that live in the <code class="filename">mk/</code> directory and below.
1.10 hubertf 799: 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 800: too.</p></dd>
801: </dl></div>
802: </div>
803: </div>
1.41 asau 804: <div class="sect1">
1.1 dsieger 805: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
806: <a name="typography"></a>1.4. Typography</h2></div></div></div>
807: <p>When giving examples for commands, shell prompts are used to
808: show if the command should/can be issued as root, or if
1.23 wiz 809: <span class="quote">“<span class="quote">normal</span>”</span> user privileges are sufficient. We use a
1.1 dsieger 810: <code class="prompt">#</code> for root's shell prompt, and a <code class="prompt">%</code> for users'
811: shell prompt, assuming they use the C-shell or tcsh.</p>
812: </div>
813: </div>
1.41 asau 814: <div class="part">
1.1 dsieger 815: <div class="titlepage"><div><div><h1 class="title">
816: <a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div>
817: <div class="toc">
818: <p><b>Table of Contents</b></p>
1.100 leot 819: <dl class="toc">
1.1 dsieger 820: <dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
821: <dd><dl>
822: <dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
823: <dd><dl>
1.51 asau 824: <dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
1.23 wiz 825: <dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
1.1 dsieger 826: </dl></dd>
827: <dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
828: <dd><dl>
829: <dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
830: <dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
831: </dl></dd>
832: </dl></dd>
833: <dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt>
834: <dd><dl>
835: <dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt>
836: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
837: <dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
838: <dd><dl>
1.45 obache 839: <dt><span class="sect2"><a href="#cygwin">3.3.1. Cygwin</a></span></dt>
840: <dt><span class="sect2"><a href="#darwin">3.3.2. Darwin (Mac OS X)</a></span></dt>
841: <dt><span class="sect2"><a href="#freebsd">3.3.3. FreeBSD</a></span></dt>
1.58 ryoon 842: <dt><span class="sect2"><a href="#gnukfreebsd">3.3.4. GNU/kFreeBSD</a></span></dt>
843: <dt><span class="sect2"><a href="#interix">3.3.5. Interix</a></span></dt>
844: <dt><span class="sect2"><a href="#irix">3.3.6. IRIX</a></span></dt>
845: <dt><span class="sect2"><a href="#linux">3.3.7. Linux</a></span></dt>
846: <dt><span class="sect2"><a href="#mirbsd">3.3.8. MirBSD</a></span></dt>
847: <dt><span class="sect2"><a href="#openbsd">3.3.9. OpenBSD</a></span></dt>
848: <dt><span class="sect2"><a href="#solaris">3.3.10. Solaris</a></span></dt>
1.1 dsieger 849: </dl></dd>
850: </dl></dd>
851: <dt><span class="chapter"><a href="#using">4. Using pkgsrc</a></span></dt>
852: <dd><dl>
853: <dt><span class="sect1"><a href="#using-pkg">4.1. Using binary packages</a></span></dt>
854: <dd><dl>
855: <dt><span class="sect2"><a href="#finding-binary-packages">4.1.1. Finding binary packages</a></span></dt>
856: <dt><span class="sect2"><a href="#installing-binary-packages">4.1.2. Installing binary packages</a></span></dt>
857: <dt><span class="sect2"><a href="#using.pkg_delete">4.1.3. Deinstalling packages</a></span></dt>
858: <dt><span class="sect2"><a href="#using.pkg_info">4.1.4. Getting information about installed packages</a></span></dt>
859: <dt><span class="sect2"><a href="#vulnerabilities">4.1.5. Checking for security vulnerabilities in installed packages</a></span></dt>
860: <dt><span class="sect2"><a href="#pkg_versions">4.1.6. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
861: <dt><span class="sect2"><a href="#using.pkg_admin">4.1.7. Other administrative functions</a></span></dt>
862: <dt><span class="sect2"><a href="#a-word-of-warning">4.1.8. A word of warning</a></span></dt>
863: </dl></dd>
864: <dt><span class="sect1"><a href="#building-packages-from-source">4.2. Building packages from source</a></span></dt>
865: <dd><dl>
866: <dt><span class="sect2"><a href="#requirements">4.2.1. Requirements</a></span></dt>
867: <dt><span class="sect2"><a href="#fetching-distfiles">4.2.2. Fetching distfiles</a></span></dt>
868: <dt><span class="sect2"><a href="#how-to-build-and-install">4.2.3. How to build and install</a></span></dt>
869: </dl></dd>
870: </dl></dd>
871: <dt><span class="chapter"><a href="#configuring">5. Configuring pkgsrc</a></span></dt>
872: <dd><dl>
873: <dt><span class="sect1"><a href="#general-configuration">5.1. General configuration</a></span></dt>
874: <dt><span class="sect1"><a href="#variables-affecting-build">5.2. Variables affecting the build process</a></span></dt>
1.9 rillig 875: <dt><span class="sect1"><a href="#variables-affecting-installation">5.3. Variables affecting the installation process</a></span></dt>
1.4 rillig 876: <dt><span class="sect1"><a href="#conf.compiler">5.4. Selecting and configuring the compiler</a></span></dt>
1.1 dsieger 877: <dd><dl>
1.4 rillig 878: <dt><span class="sect2"><a href="#selecting-the-compiler">5.4.1. Selecting the compiler</a></span></dt>
1.23 wiz 879: <dt><span class="sect2"><a href="#conf.cflags">5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
880: <dt><span class="sect2"><a href="#conf.ldflags">5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 881: </dl></dd>
1.4 rillig 882: <dt><span class="sect1"><a href="#developer-advanced-settings">5.5. Developer/advanced settings</a></span></dt>
883: <dt><span class="sect1"><a href="#selecting-build-options">5.6. Selecting Build Options</a></span></dt>
1.1 dsieger 884: </dl></dd>
885: <dt><span class="chapter"><a href="#binary">6. Creating binary packages</a></span></dt>
886: <dd><dl>
887: <dt><span class="sect1"><a href="#building-a-single-binary-package">6.1. Building a single binary package</a></span></dt>
888: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">6.2. Settings for creation of binary packages</a></span></dt>
1.6 rillig 889: </dl></dd>
890: <dt><span class="chapter"><a href="#bulk">7. Creating binary packages for everything in pkgsrc (bulk
891: builds)</a></span></dt>
1.1 dsieger 892: <dd><dl>
1.71 wiz 893: <dt><span class="sect1"><a href="#bulk.pre">7.1. Preparations</a></span></dt>
894: <dt><span class="sect1"><a href="#bulk.pbulk">7.2. Running a pbulk-style bulk build</a></span></dt>
895: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">7.2.1. Configuration</a></span></dt></dl></dd>
896: <dt><span class="sect1"><a href="#bulk.req">7.3. Requirements of a full bulk build</a></span></dt>
1.66 asau 897: <dt><span class="sect1"><a href="#creating-cdroms">7.4. Creating a multiple CD-ROM packages collection</a></span></dt>
898: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">7.4.1. Example of cdpack</a></span></dt></dl></dd>
1.6 rillig 899: </dl></dd>
900: <dt><span class="chapter"><a href="#files">8. Directory layout of the installed files</a></span></dt>
901: <dd><dl>
1.23 wiz 902: <dt><span class="sect1"><a href="#files.localbase">8.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
903: <dt><span class="sect1"><a href="#files.varbase">8.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
1.6 rillig 904: </dl></dd>
905: <dt><span class="chapter"><a href="#faq">9. Frequently Asked Questions</a></span></dt>
906: <dd><dl>
907: <dt><span class="sect1"><a href="#mailing-list-pointers">9.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
1.84 wiz 908: <dt><span class="sect1"><a href="#faq-pkgtools">9.2. Utilities for package management (pkgtools)</a></span></dt>
909: <dt><span class="sect1"><a href="#non-root-pkgsrc">9.3. How to use pkgsrc as non-root</a></span></dt>
910: <dt><span class="sect1"><a href="#resume-transfers">9.4. How to resume transfers when fetching distfiles?</a></span></dt>
911: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">9.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
912: <dt><span class="sect1"><a href="#fetch-behind-firewall">9.6. How to fetch files from behind a firewall</a></span></dt>
913: <dt><span class="sect1"><a href="#fetch-https">9.7. How to fetch files from HTTPS sites</a></span></dt>
914: <dt><span class="sect1"><a href="#passive-ftp">9.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
915: <dt><span class="sect1"><a href="#fetching-all-distfiles">9.9. How to fetch all distfiles at once</a></span></dt>
916: <dt><span class="sect1"><a href="#tmac.andoc-missing">9.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 917: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.84 wiz 918: <dt><span class="sect1"><a href="#bsd.own.mk-missing">9.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
919: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">9.12. Using 'sudo' with pkgsrc</a></span></dt>
920: <dt><span class="sect1"><a href="#faq.conf">9.13. How do I change the location of configuration files?</a></span></dt>
921: <dt><span class="sect1"><a href="#audit-packages">9.14. Automated security checks</a></span></dt>
922: <dt><span class="sect1"><a href="#ufaq-cflags">9.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
923: <dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build. What shall I do?</a></span></dt>
924: <dt><span class="sect1"><a href="#faq.rcs-conflicts">9.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 925: </dl></dd>
926: </dl>
927: </div>
1.41 asau 928: <div class="chapter">
1.1 dsieger 929: <div class="titlepage"><div><div><h2 class="title">
930: <a name="getting"></a>Chapter 2. Where to get pkgsrc and how to keep it up-to-date</h2></div></div></div>
931: <div class="toc">
932: <p><b>Table of Contents</b></p>
1.100 leot 933: <dl class="toc">
1.1 dsieger 934: <dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
935: <dd><dl>
1.51 asau 936: <dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
1.23 wiz 937: <dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
1.1 dsieger 938: </dl></dd>
939: <dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
940: <dd><dl>
941: <dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
942: <dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
943: </dl></dd>
944: </dl>
945: </div>
946: <p>Before you download and extract the files, you need to decide
947: where you want to extract them. When using pkgsrc as root user, pkgsrc
948: is usually installed in <code class="filename">/usr/pkgsrc</code>. You are though
949: free to install the sources and binary packages wherever you want in
950: your filesystem, provided that the pathname does not contain white-space
951: or other characters that are interpreted specially by the shell and some
952: other programs. A safe bet is to use only letters, digits, underscores
953: and dashes.</p>
1.41 asau 954: <div class="sect1">
1.1 dsieger 955: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
956: <a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div>
957: <p>Before you download any pkgsrc files, you should decide
958: whether you want the <span class="emphasis"><em>current</em></span> branch or the
959: <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a
960: quarterly basis from the current branch and only gets modified
961: for security updates. The names of the stable branches are built
962: from the year and the quarter, for example
1.78 snj 963: <code class="literal">2014Q3</code>.</p>
1.1 dsieger 964: <p>The second step is to decide <span class="emphasis"><em>how</em></span> you
1.23 wiz 965: want to download pkgsrc. You can get it as a tar file or via CVS.
966: Both ways are described here.</p>
1.51 asau 967: <p>Note that tar archive contains CVS working copy.
968: Thus you can switch to using CVS at any later time.</p>
1.41 asau 969: <div class="sect2">
1.1 dsieger 970: <div class="titlepage"><div><div><h3 class="title">
1.51 asau 971: <a name="getting-via-tar"></a>2.1.1. As tar archive</h3></div></div></div>
1.1 dsieger 972: <p>The primary download location for all pkgsrc files is
1.51 asau 973: <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/" target="_top">http://ftp.NetBSD.org/pub/pkgsrc/</a> or
974: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a>
975: (it points to the same location).
976: There are a number of subdirectories for different purposes,
977: which are described in detail in <a class="xref" href="#ftp-layout" title="Appendix C. Directory layout of the pkgsrc FTP server">Appendix C, <i>Directory layout of the pkgsrc FTP server</i></a>.</p>
978: <p>The tar archive for the current branch is in the directory
979: <code class="filename">current</code> and is called <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.
1.1 dsieger 980: It is autogenerated daily.</p>
1.51 asau 981: <p>To save download time we provide bzip2- and
982: xz-compressed archives which are published at
983: <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.bz2" target="_top"><code class="filename">pkgsrc.tar.bz2</code></a>
984: and
985: <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.xz" target="_top"><code class="filename">pkgsrc.tar.xz</code></a>
986: respectively.
987: </p>
988: <p>You can fetch the same files using FTP.</p>
1.78 snj 989: <p>The tar file for the stable branch 2014Q3 is in the
990: directory <code class="filename">pkgsrc-2014Q3</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2014Q3/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p>
1.12 weinem 991: <p>To download a pkgsrc stable tarball, run:</p>
992: <pre class="screen">
1.59 jnemeth 993: <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>/pkgsrc.tar.gz</code></strong></pre>
1.22 jakllsch 994: <p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the
1.12 weinem 995: stable branch to be downloaded, for example,
1.78 snj 996: <span class="quote">“<span class="quote">pkgsrc-2014Q3</span>”</span>.</p>
997: <p>If you prefer, you can also fetch it using "wget", "curl",
1.51 asau 998: or your web browser.</p>
1.12 weinem 999: <p>Then, extract it with:</p>
1.78 snj 1000: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre>
1.12 weinem 1001: <p>This will create the directory <code class="filename">pkgsrc/</code>
1002: in <code class="filename">/usr/</code> and all the package source will be
1003: stored under <code class="filename">/usr/pkgsrc/</code>.</p>
1004: <p>To download pkgsrc-current, run:</p>
1005: <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 1006: </div>
1.41 asau 1007: <div class="sect2">
1.1 dsieger 1008: <div class="titlepage"><div><div><h3 class="title">
1.23 wiz 1009: <a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div>
1010: <p>To fetch a specific pkgsrc stable branch, run:</p>
1.39 wiz 1011: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r <em class="replaceable"><code>pkgsrc-20xxQy</code></em> -P pkgsrc</code></strong>
1.23 wiz 1012: </pre>
1013: <p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the stable
1.78 snj 1014: branch to be checked out, for example, <span class="quote">“<span class="quote">pkgsrc-2014Q3</span>”</span></p>
1.23 wiz 1015: <p>This will create the directory <code class="filename">pkgsrc/</code>
1016: in your <code class="filename">/usr/</code> directory and all the package source
1017: will be stored under <code class="filename">/usr/pkgsrc/</code>.</p>
1018: <p>To fetch the pkgsrc current branch, run:</p>
1.39 wiz 1019: <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 1020: </pre>
1.78 snj 1021: <p>Refer to the <a class="ulink" href="http://www.NetBSD.org/mirrors/#anoncvs" target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p>
1.23 wiz 1022: <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 1023: <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 1024: </pre>
1025: <p>Refer to documentation on your command shell how to set CVS_RSH=ssh permanently.
1026: For Bourne shells, you can set it in your <code class="filename">.profile</code>
1027: or better globally in <code class="filename">/etc/profile</code>:</p>
1028: <pre class="programlisting">
1029: # set CVS remote shell command
1030: CVS_RSH=ssh
1031: export CVS_RSH
1032: </pre>
1033: <p>By default, CVS doesn't do things like most people would expect it to do.
1034: But there is a way to convince CVS, by creating a file called <code class="filename">.cvsrc</code>
1035: in your home directory and saving the following lines to it.
1036: This file will save you lots of headache and some bug reports, so we strongly recommend it.
1037: You can find an explanation of this file in the CVS documentation.</p>
1.2 rillig 1038: <pre class="programlisting">
1039: # recommended CVS configuration file from the pkgsrc guide
1.39 wiz 1040: cvs -q -z2
1.2 rillig 1041: checkout -P
1.4 rillig 1042: update -dP
1043: diff -upN
1.2 rillig 1044: rdiff -u
1.23 wiz 1045: release -d
1.2 rillig 1046: </pre>
1.1 dsieger 1047: </div>
1048: </div>
1.41 asau 1049: <div class="sect1">
1.1 dsieger 1050: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1051: <a name="uptodate"></a>2.2. Keeping pkgsrc up-to-date</h2></div></div></div>
1052: <p>The preferred way to keep pkgsrc up-to-date is via CVS
1053: (which also works if you have first installed it via a tar
1054: file). It saves bandwidth and hard disk activity, compared to
1055: downloading the tar file again.</p>
1.41 asau 1056: <div class="sect2">
1.1 dsieger 1057: <div class="titlepage"><div><div><h3 class="title">
1058: <a name="uptodate-tar"></a>2.2.1. Via tar files</h3></div></div></div>
1.41 asau 1059: <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1060: <h3 class="title">Warning</h3>
1061: <p>When updating from a tar file, you first need to
1062: completely remove the old pkgsrc directory. Otherwise those
1063: files that have been removed from pkgsrc in the mean time will
1064: not be removed on your local disk, resulting in inconsistencies.
1065: When removing the old files, any changes that you have done to
1066: the pkgsrc files will be lost after updating. Therefore updating
1067: via CVS is strongly recommended.</p>
1068: </div>
1069: <p>Note that by default the distfiles and the binary packages
1070: are saved in the pkgsrc tree, so don't forget to rescue them
1.78 snj 1071: before updating. You can also configure pkgsrc to store distfiles
1072: and packages in directories outside the pkgsrc tree by setting the
1.1 dsieger 1073: <code class="varname">DISTDIR</code> and <code class="varname">PACKAGES</code>
1.10 hubertf 1074: variables. See <a class="xref" href="#configuring" title="Chapter 5. Configuring pkgsrc">Chapter 5, <i>Configuring pkgsrc</i></a> for the details.</p>
1.1 dsieger 1075: <p>To update pkgsrc from a tar file, download the tar file as
1076: explained above. Then, make sure that you have not made any
1077: changes to the files in the pkgsrc directory. Remove the pkgsrc
1078: directory and extract the new tar file. Done.</p>
1079: </div>
1.41 asau 1080: <div class="sect2">
1.1 dsieger 1081: <div class="titlepage"><div><div><h3 class="title">
1082: <a name="uptodate-cvs"></a>2.2.2. Via CVS</h3></div></div></div>
1.25 spz 1083: <p>To update pkgsrc via CVS, change to the <code class="filename">pkgsrc</code> directory and run cvs:</p>
1084: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && cvs update -dP</code></strong>
1085: </pre>
1086: <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>
1087: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP</code></strong>
1088: </pre>
1.41 asau 1089: <div class="sect3">
1.1 dsieger 1090: <div class="titlepage"><div><div><h4 class="title">
1091: <a name="uptodate-cvs-switch"></a>2.2.2.1. Switching between different pkgsrc branches</h4></div></div></div>
1092: <p>When updating pkgsrc, the CVS program keeps track of the
1093: branch you selected. But if you, for whatever reason, want to
1094: switch from the stable branch to the current one, you can do it
1.23 wiz 1095: by adding the option <span class="quote">“<span class="quote">-A</span>”</span> after the
1096: <span class="quote">“<span class="quote">update</span>”</span> keyword. To switch from the current branch
1.1 dsieger 1097: back to the stable branch, add the
1.78 snj 1098: <span class="quote">“<span class="quote">-rpkgsrc-2014Q3</span>”</span> option.</p>
1.1 dsieger 1099: </div>
1.41 asau 1100: <div class="sect3">
1.1 dsieger 1101: <div class="titlepage"><div><div><h4 class="title">
1102: <a name="uptodate-cvs-changes"></a>2.2.2.2. What happens to my changes when updating?</h4></div></div></div>
1103: <p>When you update pkgsrc, the CVS program will only touch
1104: those files that are registered in the CVS repository. That
1105: means that any packages that you created on your own will stay
1106: unmodified. If you change files that are managed by CVS, later
1107: updates will try to merge your changes with those that have been
1108: done by others. See the CVS manual, chapter
1.23 wiz 1109: <span class="quote">“<span class="quote">update</span>”</span> for details.</p>
1.1 dsieger 1110: </div>
1111: </div>
1112: </div>
1113: </div>
1.41 asau 1114: <div class="chapter">
1.1 dsieger 1115: <div class="titlepage"><div><div><h2 class="title">
1116: <a name="platforms"></a>Chapter 3. Using pkgsrc on systems other than NetBSD</h2></div></div></div>
1117: <div class="toc">
1118: <p><b>Table of Contents</b></p>
1.100 leot 1119: <dl class="toc">
1.1 dsieger 1120: <dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt>
1121: <dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
1122: <dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
1123: <dd><dl>
1.45 obache 1124: <dt><span class="sect2"><a href="#cygwin">3.3.1. Cygwin</a></span></dt>
1125: <dt><span class="sect2"><a href="#darwin">3.3.2. Darwin (Mac OS X)</a></span></dt>
1126: <dt><span class="sect2"><a href="#freebsd">3.3.3. FreeBSD</a></span></dt>
1.58 ryoon 1127: <dt><span class="sect2"><a href="#gnukfreebsd">3.3.4. GNU/kFreeBSD</a></span></dt>
1128: <dt><span class="sect2"><a href="#interix">3.3.5. Interix</a></span></dt>
1129: <dt><span class="sect2"><a href="#irix">3.3.6. IRIX</a></span></dt>
1130: <dt><span class="sect2"><a href="#linux">3.3.7. Linux</a></span></dt>
1131: <dt><span class="sect2"><a href="#mirbsd">3.3.8. MirBSD</a></span></dt>
1132: <dt><span class="sect2"><a href="#openbsd">3.3.9. OpenBSD</a></span></dt>
1133: <dt><span class="sect2"><a href="#solaris">3.3.10. Solaris</a></span></dt>
1.1 dsieger 1134: </dl></dd>
1135: </dl>
1136: </div>
1.41 asau 1137: <div class="sect1">
1.1 dsieger 1138: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1139: <a name="binarydist"></a>3.1. Binary distribution</h2></div></div></div>
1.10 hubertf 1140: <p>See <a class="xref" href="#using-pkg" title="4.1. Using binary packages">Section 4.1, “Using binary packages”</a>.</p>
1.1 dsieger 1141: </div>
1.41 asau 1142: <div class="sect1">
1.1 dsieger 1143: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1144: <a name="bootstrapping-pkgsrc"></a>3.2. Bootstrapping pkgsrc</h2></div></div></div>
1.43 asau 1145: <p>pkgsrc can be bootstrapped for use in two different modes:
1146: privileged and unprivileged one. In unprivileged mode in contrast
1.44 asau 1147: to privileged one all programs are installed under one particular user
1.43 asau 1148: and cannot utilise privileged operations (packages don't create
1149: special users and all special file permissions like setuid are ignored).
1150: </p>
1.1 dsieger 1151: <p>Installing the bootstrap kit from source should be as simple as:</p>
1152: <pre class="screen">
1.60 asau 1153: <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 1154: <code class="prompt">#</code> <strong class="userinput"><code>cd pkgsrc/bootstrap</code></strong>
1155: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap</code></strong>
1156: </pre>
1.43 asau 1157: <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>
1158: <p>By default, in privileged mode pkgsrc uses
1159: <code class="filename">/usr/pkg</code> for <span class="emphasis"><em>prefix</em></span>
1160: where programs will be installed in,
1.1 dsieger 1161: and <code class="filename">/var/db/pkg</code> for the package database
1.43 asau 1162: directory where pkgsrc will do its internal bookkeeping,
1163: <code class="filename">/var</code> is used as <span class="emphasis"><em>varbase</em></span>,
1164: where packages install their persistent data.
1165: In unprivileged mode pkgsrc uses
1166: <code class="filename">~/pkg</code> for <span class="emphasis"><em>prefix</em></span>,
1167: <code class="filename">~/pkg/var/db/pkg</code> for the package database,
1168: and <code class="filename">~/pkg/var</code> for <span class="emphasis"><em>varbase</em></span>.
1169: </p>
1170: <p>You can change default layout using command-line arguments.
1171: Run <span class="quote">“<span class="quote">./bootstrap --help</span>”</span> to get details.
1172: </p>
1.41 asau 1173: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1174: <h3 class="title">Note</h3>
1.10 hubertf 1175: <p>The bootstrap installs a <span class="command"><strong>bmake</strong></span> tool.
1176: Use this <span class="command"><strong>bmake</strong></span> when building via pkgsrc.
1177: For examples in this guide, use <span class="command"><strong>bmake</strong></span>
1.23 wiz 1178: instead of <span class="quote">“<span class="quote">make</span>”</span>.</p>
1.1 dsieger 1179: </div>
1.43 asau 1180: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1181: <h3 class="title">Note</h3>
1182: <p>It is possible to bootstrap multiple instances of pkgsrc
1183: using non-intersecting directories. Use <span class="command"><strong>bmake</strong></span>
1184: corresponding to the installation you're working with to build
1185: and install packages.
1186: </p>
1187: </div>
1.1 dsieger 1188: </div>
1.41 asau 1189: <div class="sect1">
1.1 dsieger 1190: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1191: <a name="platform-specific-notes"></a>3.3. Platform-specific notes</h2></div></div></div>
1192: <p>Here are some platform-specific notes you should be aware of.</p>
1.41 asau 1193: <div class="sect2">
1.1 dsieger 1194: <div class="titlepage"><div><div><h3 class="title">
1.45 obache 1195: <a name="cygwin"></a>3.3.1. Cygwin</h3></div></div></div>
1196: <p>Cygwin 1.7.x and later are supported.</p>
1197: <p>You need to install minimal base packages in `Base' category
1198: plus any of compiler, gcc, gcc4, and/or clang.
1199: For gcc and gcc4, C and C++ compiler will be installed by default,
1200: but you can install Fortran compiler additionally
1201: because it will be required to use libtool.
1202: If it is not installed (or too old), Fortran compiler will be
1203: installed with pkgsrc automatically.</p>
1204: <p>As noted in
1205: <a class="ulink" href="http://cygwin.com/faq-nochunks.html#faq.using.su" target="_top">Cygwin FAQ: `Why doesn't su work?'</a>,
1206: su(1) command has been in Cygwin distribution, but it has never worked.
1207: Unless you bootstrap pkgsrc with the --unprivileged option, workaround is:
1208: </p>
1209: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Right click "Cygwin Terminal" in your Start Menu,
1210: then pick "Run as administrator".</p></li></ul></div>
1211: </div>
1212: <div class="sect2">
1213: <div class="titlepage"><div><div><h3 class="title">
1214: <a name="darwin"></a>3.3.2. Darwin (Mac OS X)</h3></div></div></div>
1.101 ! sevan 1215: <p>Darwin 8.x and up are supported.</p>
1.41 asau 1216: <p>Before you start, you need to download and install
1217: the Mac OS X Developer Tools from Apple's Developer Connection.
1218: This requires (free) membership. See
1.22 jakllsch 1219: <a class="ulink" href="http://developer.apple.com/macosx/" target="_top">http://developer.apple.com/macosx/</a>
1.41 asau 1220: for details. Also, make sure you install X11 (an optional
1221: package included with the Developer Tools) if you intend
1222: to build packages that use the X11 Window System.
1223: (If you don't want or need the full Xcode GUI,
1224: download and install Command Line Tools for Xcode.)</p>
1.1 dsieger 1225: </div>
1.41 asau 1226: <div class="sect2">
1.1 dsieger 1227: <div class="titlepage"><div><div><h3 class="title">
1.45 obache 1228: <a name="freebsd"></a>3.3.3. FreeBSD</h3></div></div></div>
1.29 dholland 1229: <p>FreeBSD 8.3 and 9.0 have been tested and are supported,
1.1 dsieger 1230: other versions may work.</p>
1231: <p>Care should be taken so that the tools that this kit installs do not conflict
1232: with the FreeBSD userland tools. There are several steps:</p>
1.23 wiz 1233: <div class="orderedlist"><ol class="orderedlist" type="1">
1234: <li class="listitem"><p>FreeBSD stores its ports pkg database in
1.1 dsieger 1235: <code class="filename">/var/db/pkg</code>. It is therefore
1236: recommended that you choose a different location (e.g.
1237: <code class="filename">/usr/pkgdb</code>) by
1238: using the --pkgdbdir option to the bootstrap script.</p></li>
1.23 wiz 1239: <li class="listitem">
1.1 dsieger 1240: <p>If you do not intend to use the FreeBSD ports tools, it's probably a
1241: good idea to move them out of the way to avoid confusion, e.g.</p>
1242: <pre class="screen">
1243: <code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sbin</code></strong>
1244: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_add pkg_add.orig</code></strong>
1245: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_create pkg_create.orig</code></strong>
1246: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
1247: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong>
1248: </pre>
1249: </li>
1.23 wiz 1250: <li class="listitem"><p>An example <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file will be placed in
1.1 dsieger 1251: <code class="filename">/etc/mk.conf.example</code> file
1252: when you use the bootstrap script.</p></li>
1253: </ol></div>
1254: </div>
1.41 asau 1255: <div class="sect2">
1.1 dsieger 1256: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1257: <a name="gnukfreebsd"></a>3.3.4. GNU/kFreeBSD</h3></div></div></div>
1258: <p>Debian GNU/kFreeBSD is the only GNU/kFreeBSD distribution now.
1259: Debian GNU/kFreeBSD 7.0 or later is tested and supported.</p>
1260: <p> You should install ncurses (libncurses and libncurses-dev)
1261: packages.</p>
1262: </div>
1263: <div class="sect2">
1264: <div class="titlepage"><div><div><h3 class="title">
1265: <a name="interix"></a>3.3.5. Interix</h3></div></div></div>
1.1 dsieger 1266: <p>Interix is a POSIX-compatible subsystem for the Windows NT kernel,
1267: providing a Unix-like environment with a tighter kernel integration than
1268: available with Cygwin. It is part of the Windows Services for Unix
1269: package, available for free for any licensed copy of Windows 2000, XP
1.10 hubertf 1270: (not including XP Home), or 2003. SFU can be downloaded from <a class="ulink" href="http://www.microsoft.com/windows/sfu/" target="_top">http://www.microsoft.com/windows/sfu/</a>.</p>
1.1 dsieger 1271: <p>Services for Unix 3.5 has been tested. 3.0 or 3.1 may work, but
1272: are not officially supported. (The main difference in 3.0/3.1 is lack
1273: of pthreads, but other parts of libc may also be lacking.)</p>
1.24 wiz 1274: <p>Services for Unix Applications (aka SUA) is an integrated
1275: component of Windows Server 2003 R2 (5.2), Windows Vista and
1276: Windows Server 2008 (6.0), Windows 7 and Windows Server 2008 R2
1277: (6.1). As of this writing, the SUA's Interix 6.0 (32bit) and
1278: 6.1 (64bit) subsystems have been tested. Other versions may
1279: work as well. The Interix 5.x subsystem has not yet been tested
1280: with pkgsrc.</p>
1.41 asau 1281: <div class="sect3">
1.1 dsieger 1282: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1283: <a name="platform.interix-sfu-install"></a>3.3.5.1. When installing Interix/SFU</h4></div></div></div>
1.1 dsieger 1284: <p>At an absolute minimum, the following packages must be installed from
1285: the Windows Services for Unix 3.5 distribution in order to use pkgsrc:</p>
1.41 asau 1286: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1287: <li class="listitem"><p>Utilities -> Base Utilities</p></li>
1288: <li class="listitem"><p>Interix GNU Components -> (all)</p></li>
1289: <li class="listitem"><p>Remote Connectivity</p></li>
1290: <li class="listitem"><p>Interix SDK</p></li>
1.1 dsieger 1291: </ul></div>
1292: <p>When using pkgsrc on Interix, DO NOT install the Utilities subcomponent
1293: "UNIX Perl". That is Perl 5.6 without shared module support, installed to
1294: /usr/local, and will only cause confusion. Instead, install Perl 5.8 from
1295: pkgsrc (or from a binary package).</p>
1296: <p>The Remote Connectivity subcomponent "Windows Remote Shell Service" does
1297: not need to be installed, but Remote Connectivity itself should be
1298: installed in order to have a working inetd.</p>
1299: <p>During installation you may be asked whether to enable setuid
1300: behavior for Interix programs, and whether to make pathnames default to
1301: case-sensitive. Setuid should be enabled, and case-sensitivity MUST be
1302: enabled. (Without case-sensitivity, a large number of packages including
1303: perl will not build.)</p>
1304: <p>NOTE: Newer Windows service packs change the way binary execution
1305: works (via the Data Execution Prevention feature). In order to use
1306: pkgsrc and other gcc-compiled binaries reliably, a hotfix containing
1307: POSIX.EXE, PSXDLL.DLL, PSXRUN.EXE, and PSXSS.EXE (899522 or newer)
1308: must be installed. Hotfixes are available from Microsoft through a
1.14 jmcneill 1309: support contract; however, Debian Interix Port has made most Interix
1310: hotfixes available for personal use from <a class="ulink" href="http://www.debian-interix.net/hotfixes/" target="_top">http://www.debian-interix.net/hotfixes/</a>.</p>
1.1 dsieger 1311: <p>In addition to the hotfix noted above, it may be necessary to
1312: disable Data Execution Prevention entirely to make Interix functional.
1313: This may happen only with certain types of CPUs; the cause is not fully
1314: understood at this time. If gcc or other applications still segfault
1315: repeatedly after installing one of the hotfixes note above, the
1316: following option can be added to the appropriate "boot.ini" line on the
1317: Windows boot drive: /NoExecute=AlwaysOff
1318: (WARNING, this will disable DEP completely, which may be a security
1319: risk if applications are often run as a user in the Administrators
1320: group!)</p>
1321: </div>
1.41 asau 1322: <div class="sect3">
1.1 dsieger 1323: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1324: <a name="platform.interix-sfu-postinstall"></a>3.3.5.2. What to do if Interix/SFU is already installed</h4></div></div></div>
1.1 dsieger 1325: <p>If SFU is already installed and you wish to alter these settings to work
1326: with pkgsrc, note the following things.</p>
1.41 asau 1327: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1328: <li class="listitem"><p>To uninstall UNIX Perl, use Add/Remove Programs, select Microsoft
1.1 dsieger 1329: Windows Services for UNIX, then click Change. In the installer, choose
1330: Add or Remove, then uncheck Utilities->UNIX Perl.</p></li>
1.23 wiz 1331: <li class="listitem">
1.1 dsieger 1332: <p>To enable case-sensitivity for the file system, run REGEDIT.EXE, and
1333: change the following registry key:</p>
1334: <p>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel</p>
1335: <p>Set the DWORD value "obcaseinsensitive" to 0; then reboot.</p>
1336: </li>
1.23 wiz 1337: <li class="listitem">
1.1 dsieger 1338: <p>To enable setuid binaries (optional), run REGEDIT.EXE, and change the
1339: following registry key:</p>
1340: <p>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Services for UNIX</p>
1341: <p>Set the DWORD value "EnableSetuidBinaries" to 1; then reboot.</p>
1342: </li>
1343: </ul></div>
1344: </div>
1.41 asau 1345: <div class="sect3">
1.1 dsieger 1346: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1347: <a name="platform.interix-notes"></a>3.3.5.3. Important notes for using pkgsrc</h4></div></div></div>
1.1 dsieger 1348: <p>The package manager (either the pkgsrc "su" user, or the user
1349: running "pkg_add") must be a member of the local Administrators
1350: group. Such a user must also be used to run the bootstrap. This is
1351: slightly relaxed from the normal pkgsrc requirement of "root".</p>
1352: <p>The package manager should use a umask of 002. "make install" will
1353: automatically complain if this is not the case. This ensures that
1354: directories written in /var/db/pkg are Administrators-group writeable.</p>
1355: <p>The popular Interix binary packages from http://www.interopsystems.com/
1356: use an older version of pkgsrc's pkg_* tools. Ideally, these should
1357: NOT be used in conjunction with pkgsrc. If you choose to use them at
1358: the same time as the pkgsrc packages, ensure that you use the proper
1359: pkg_* tools for each type of binary package.</p>
1360: <p>The TERM setting used for DOS-type console windows (including those
1361: invoked by the csh and ksh startup shortcuts) is "interix". Most systems
1362: don't have a termcap/terminfo entry for it, but the following .termcap
1363: entry provides adequate emulation in most cases:</p>
1364: <pre class="programlisting">
1365: interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi:
1366: </pre>
1367: </div>
1.41 asau 1368: <div class="sect3">
1.1 dsieger 1369: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1370: <a name="platform.interix-limits"></a>3.3.5.4. Limitations of the Interix platform</h4></div></div></div>
1.1 dsieger 1371: <p>Though Interix suffices as a familiar and flexible substitute
1372: for a full Unix-like platform, it has some drawbacks that should
1373: be noted for those desiring to make the most of Interix.</p>
1.41 asau 1374: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1375: <li class="listitem">
1.1 dsieger 1376: <p><span class="strong"><strong>X11:</strong></span></p>
1377: <p>Interix comes with the standard set of X11R6 client libraries,
1378: and can run X11 based applications, but it does
1379: <span class="emphasis"><em>not</em></span> come with an X server. Some options are
1.10 hubertf 1380: <a class="ulink" href="http://www.starnet.com/products/xwin32/" target="_top">StarNet X-Win32</a>,
1381: <a class="ulink" href="http://connectivity.hummingbird.com/products/nc/exceed/" target="_top">Hummingbird Exceed</a>
1.1 dsieger 1382: (available in a trimmed version for Interix from Interop Systems as the
1.10 hubertf 1383: <a class="ulink" href="http://www.interopsystems.com/InteropXserver.htm" target="_top">Interop X Server</a>),
1.1 dsieger 1384: and the free X11 server included with
1.10 hubertf 1385: <a class="ulink" href="http://x.cygwin.com/" target="_top">Cygwin</a>.</p>
1.1 dsieger 1386: </li>
1.23 wiz 1387: <li class="listitem">
1.1 dsieger 1388: <p><span class="strong"><strong>X11 acceleration:</strong></span></p>
1389: <p>Because Interix runs in a completely different NT subsystem from
1390: Win32 applications, it does not currently support various X11
1391: protocol extensions for acceleration (such as MIT-SHM or DGA).
1392: Most interactive applications to a local X server will run
1393: reasonably fast, but full motion video and other graphics
1394: intensive applications may require a faster-than-expected CPU.</p>
1395: </li>
1.23 wiz 1396: <li class="listitem">
1.1 dsieger 1397: <p><span class="strong"><strong>Audio:</strong></span></p>
1398: <p>Interix has no native support for audio output. For audio
1.10 hubertf 1399: support, pkgsrc uses the <span class="command"><strong>esound</strong></span> client/server
1.1 dsieger 1400: audio system on Interix. Unlike on most platforms, the
1.79 snj 1401: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/audio/esound/README.html" target="_top"><code class="filename">audio/esound</code></a> package does
1.10 hubertf 1402: <span class="emphasis"><em>not</em></span> contain the <span class="command"><strong>esd</strong></span>
1.1 dsieger 1403: server component. To output audio via an Interix host, the
1.79 snj 1404: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/cygwin_esound/README.html" target="_top"><code class="filename">emulators/cygwin_esound</code></a> package
1.1 dsieger 1405: must also be installed.</p>
1406: </li>
1.23 wiz 1407: <li class="listitem">
1.1 dsieger 1408: <p><span class="strong"><strong>CD/DVDs, USB, and SCSI:</strong></span></p>
1409: <p>Direct device access is not currently supported in Interix, so it
1410: is not currently possible to access CD/DVD drives, USB devices,
1411: or SCSI devices through non-filesystem means. Among other things,
1412: this makes it impossible to use Interix directly for CD/DVD
1413: burning.</p>
1414: </li>
1.23 wiz 1415: <li class="listitem">
1.1 dsieger 1416: <p><span class="strong"><strong>Tape drives:</strong></span></p>
1417: <p>Due to the same limitations as for CD-ROMs and SCSI devices, tape
1418: drives are also not directly accessible in Interix. However,
1419: support is in work to make tape drive access possible by using
1420: Cygwin as a bridge (similarly to audio bridged via Cygwin's
1421: esound server).</p>
1422: </li>
1423: </ul></div>
1424: </div>
1.41 asau 1425: <div class="sect3">
1.1 dsieger 1426: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1427: <a name="platform.interix-knownissues"></a>3.3.5.5. Known issues for pkgsrc on Interix</h4></div></div></div>
1.1 dsieger 1428: <p>It is not necessary, in general, to have a "root" user on the
1429: Windows system; any member of the local Administrators group will
1430: suffice. However, some packages currently assume that the user
1431: named "root" is the privileged user. To accommodate these, you
1432: may create such a user; make sure it is in the local group
1433: Administrators (or your language equivalent).</p>
1.10 hubertf 1434: <p><span class="command"><strong>pkg_add</strong></span> creates directories of mode
1.1 dsieger 1435: 0755, not 0775, in <code class="filename">$PKG_DBDIR</code>. For the
1436: time being, install packages as the local Administrator (or
1437: your language equivalent), or run the following command after
1438: installing a package to work around the issue:</p>
1439: <pre class="screen">
1440: <code class="prompt">#</code> <strong class="userinput"><code>chmod -R g+w $PKG_DBDIR</code></strong>
1441: </pre>
1442: </div>
1443: </div>
1.41 asau 1444: <div class="sect2">
1.1 dsieger 1445: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1446: <a name="irix"></a>3.3.6. IRIX</h3></div></div></div>
1.1 dsieger 1447: <p>You will need a working C compiler, either gcc or SGI's MIPS and MIPSpro
1448: compiler (cc/c89). Please set the <code class="varname">CC</code> environment variable
1449: according to your preference. If you do not have a license for the MIPSpro
1.10 hubertf 1450: compiler suite, you can download a gcc tardist file from <a class="ulink" href="http://freeware.sgi.com/" target="_top">http://freeware.sgi.com/</a>.</p>
1.1 dsieger 1451: <p>Please note that you will need IRIX 6.5.17 or higher, as this is the earliest
1.79 snj 1452: version of IRIX providing support for <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_indextoname+3+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">if_indextoname</span>(3)</span></a>, <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_nametoindex+3+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">if_nametoindex</span>(3)</span></a>,
1.1 dsieger 1453: etc.</p>
1454: <p>At this point in time, pkgsrc only supports one ABI at a time. That is, you cannot
1455: switch between the old 32-bit ABI, the new 32-bit ABI and the 64-bit ABI. If
1456: you start out using "abi=n32", that's what all your packages will be built
1457: with.</p>
1458: <p>Therefore, please make sure that you have no conflicting
1459: <code class="varname">CFLAGS</code> in your environment or the
1.10 hubertf 1460: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. Particularly, make sure that you do not
1.1 dsieger 1461: try to link n32 object files with lib64 or vice versa. Check your
1462: <code class="filename">/etc/compiler.defaults</code>!</p>
1463: <p>If you have the actual pkgsrc tree mounted via NFS from a different host,
1464: please make sure to set <code class="varname">WRKOBJDIR</code> to a local directory,
1465: as it appears that IRIX linker occasionally runs into issues when trying to
1466: link over a network-mounted file system.</p>
1467: <p>The bootstrapping process should set all the right options for programs such
1468: as imake(1), but you may want to set some options depending on your local
1469: setup. Please see <code class="filename">pkgsrc/mk/defaults/mk.conf</code> and, of
1470: course, your compiler's man pages for details.</p>
1471: <p>If you are using SGI's MIPSPro compiler, please set
1472:
1473: </p>
1474: <pre class="programlisting">
1475: PKGSRC_COMPILER= mipspro
1476: </pre>
1477: <p>
1478:
1.10 hubertf 1479: in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. Otherwise, pkgsrc will assume you
1.1 dsieger 1480: are using gcc and may end up passing invalid flags to the compiler. Note that
1481: bootstrap should create an appropriate <code class="filename">mk.conf.example</code> by
1482: default.</p>
1483: <p>If you have both the MIPSPro compiler chain installed as well as gcc,
1484: but want to make sure that MIPSPro is used, please set your <code class="varname">PATH</code>
1485: to <span class="emphasis"><em>not</em></span> include the location of gcc (often
1486: <code class="filename">/usr/freeware/bin</code>), and (important) pass the
1487: '--preserve-path' flag.</p>
1488: </div>
1.41 asau 1489: <div class="sect2">
1.1 dsieger 1490: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1491: <a name="linux"></a>3.3.7. Linux</h3></div></div></div>
1.1 dsieger 1492: <p>Some versions of Linux (for example Debian GNU/Linux) need
1493: either libtermcap or libcurses (libncurses). Installing the
1494: distributions libncurses-dev package (or equivalent) should fix
1495: the problem.</p>
1496: <p>pkgsrc supports both gcc (GNU Compiler Collection) and icc
1497: (Intel C++ Compiler). gcc is the default. icc 8.0 and 8.1 on
1498: i386 have been tested.</p>
1499: <p>To bootstrap using icc, assuming the default icc installation
1500: directory:</p>
1501: <pre class="programlisting">
1.31 wiz 1502: env ICCBASE=/opt/intel/cc/10.1.008 ./bootstrap --compiler=icc
1.1 dsieger 1503: </pre>
1.41 asau 1504: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1505: <h3 class="title">Note</h3>
1.31 wiz 1506: <p>For icc 8.0 you must add `LDFLAGS=-static-libcxa' to this.</p>
1507: <p>For icc 8.1 you must add `LDFLAGS=-i-static' instead.</p>
1508: <p>For icc 10.1 neither of these appears to be necessary.</p>
1509: </div>
1510: <p>Use a value for ICCBASE that corresponds to the directory
1511: where icc is installed. After bootstrapping, set
1512: <code class="varname">ICCBASE</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.30 wiz 1513: <pre class="programlisting">
1.31 wiz 1514: ICCBASE= /opt/intel/cc/10.1.008
1.1 dsieger 1515: </pre>
1.31 wiz 1516: <p>The pkgsrc default for <code class="varname">ICCBASE</code> is
1517: <code class="filename">/opt/intel_cc_80</code>. This is the default
1518: install directory for icc 8.0. If you are using a more recent
1519: version, be sure to set the correct path explicitly.
1520: </p>
1.1 dsieger 1521: <p>pkgsrc uses the static linking method of the runtime libraries
1522: provided by icc, so binaries can be run on other systems which do not
1523: have the shared libraries installed.</p>
1524: <p>Libtool, however, extracts a list of libraries from the
1.79 snj 1525: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> command run when linking a C++ shared library and
1.1 dsieger 1526: records it, throwing away the -Bstatic and -Bdynamic options
1527: interspersed between the libraries. This means that
1528: libtool-linked C++ shared libraries will have a runtime
1529: dependency on the icc libraries until this is fixed in
1530: libtool.</p>
1531: </div>
1.41 asau 1532: <div class="sect2">
1.1 dsieger 1533: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1534: <a name="mirbsd"></a>3.3.8. MirBSD</h3></div></div></div>
1.57 bsiegert 1535: <p>pkgsrc has been tested on MirBSD #10-current (2011 and newer).
1536: Older versions might also work. Releases before #10 are not
1537: supported.</p>
1538: <p>The package tools of the (older) native ports tree,
1539: <a class="ulink" href="//www.mirbsd.org/ports.htm" target="_top">MirPorts</a>,
1540: have the same names as the ones used by pkgsrc. Care should be taken
1541: that the right tools are used. When installing packages from source,
1542: use the <code class="filename">bmake</code> command for pkgsrc and
1543: <code class="filename">mmake</code> for MirPorts.</p>
1544: <p>pkgsrc and MirPorts use the same location for the package
1545: database, <code class="filename">/var/db/pkg</code>. It is strongly recommended
1546: to use <code class="filename">/usr/pkg/db</code> instead, so that the pkgsrc
1547: tree is self-contained. This is also the default setting used in the
1548: binary package builds.</p>
1549: <p>Binary packages for MirBSD/i386 can be found on the pkgsrc ftp
1550: server. The bootstrap kit there already contains the
1551: <span class="command"><strong>pkgin</strong></span> package manager. See the
1552: <a class="ulink" href="https://www.mirbsd.org/pkgsrc.htm" target="_top">pkgsrc on MirOS</a>
1553: page for more details.</p>
1554: </div>
1555: <div class="sect2">
1556: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1557: <a name="openbsd"></a>3.3.9. OpenBSD</h3></div></div></div>
1.29 dholland 1558: <p>OpenBSD 5.1 has been tested and supported,
1559: other versions may work.</p>
1.1 dsieger 1560: <p>Care should be taken so that the tools that this kit installs do not conflict
1561: with the OpenBSD userland tools. There are several steps:</p>
1.23 wiz 1562: <div class="orderedlist"><ol class="orderedlist" type="1">
1563: <li class="listitem"><p>OpenBSD stores its ports pkg database in
1.1 dsieger 1564: <code class="filename">/var/db/pkg</code>. It is therefore
1565: recommended that you choose a different location (e.g.
1566: <code class="filename">/usr/pkgdb</code>) by
1567: using the --pkgdbdir option to the bootstrap script.</p></li>
1.23 wiz 1568: <li class="listitem">
1.1 dsieger 1569: <p>If you do not intend to use the OpenBSD ports tools, it's probably a
1570: good idea to move them out of the way to avoid confusion, e.g.</p>
1571: <pre class="screen">
1572: <code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sbin</code></strong>
1573: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_add pkg_add.orig</code></strong>
1574: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_create pkg_create.orig</code></strong>
1575: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
1576: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong>
1577: </pre>
1578: </li>
1.23 wiz 1579: <li class="listitem">
1.10 hubertf 1580: <p>An example <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file will be placed in
1.1 dsieger 1581: <code class="filename">/etc/mk.conf.example</code> file
1582: when you use the bootstrap script. OpenBSD's make program uses
1.10 hubertf 1583: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
1.1 dsieger 1584: as well. You can work around this by enclosing all the pkgsrc-specific parts
1585: of the file with:</p>
1586: <pre class="programlisting">
1587: .ifdef BSD_PKG_MK
1588: # pkgsrc stuff, e.g. insert defaults/mk.conf or similar here
1589: .else
1590: # OpenBSD stuff
1591: .endif
1592: </pre>
1593: </li>
1594: </ol></div>
1595: </div>
1.41 asau 1596: <div class="sect2">
1.1 dsieger 1597: <div class="titlepage"><div><div><h3 class="title">
1.58 ryoon 1598: <a name="solaris"></a>3.3.10. Solaris</h3></div></div></div>
1.35 wiz 1599: <p>Solaris 2.6 through 10 are supported on both x86 and sparc.
1600: You will need a working C compiler. Both gcc 4.5.3 and
1.1 dsieger 1601: Sun WorkShop 5 have been tested.</p>
1602: <p>The following packages are required on Solaris 8 for the bootstrap
1603: process and to build packages.</p>
1.41 asau 1604: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1605: <li class="listitem"><p>SUNWsprot</p></li>
1606: <li class="listitem"><p>SUNWarc</p></li>
1607: <li class="listitem"><p>SUNWbtool</p></li>
1608: <li class="listitem"><p>SUNWtoo</p></li>
1609: <li class="listitem"><p>SUNWlibm</p></li>
1.1 dsieger 1610: </ul></div>
1611: <p>Please note that the use of GNU binutils on Solaris is
1612: <span class="emphasis"><em>not</em></span> supported, as of June 2006.</p>
1613: <p>Whichever compiler you use, please ensure the compiler tools and
1614: your $prefix are in your <code class="varname">PATH</code>. This includes
1615: <code class="filename">/usr/ccs/{bin,lib}</code>
1616: and e.g. <code class="filename">/usr/pkg/{bin,sbin}</code>.</p>
1.41 asau 1617: <div class="sect3">
1.1 dsieger 1618: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1619: <a name="solaris-gcc-note"></a>3.3.10.1. If you are using gcc</h4></div></div></div>
1.1 dsieger 1620: <p>It makes life much simpler if you only use the same gcc consistently
1621: for building all packages.</p>
1622: <p>It is recommended that an external gcc be used only for bootstrapping,
1623: then either build gcc from
1.79 snj 1624: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/gcc46/README.html" target="_top"><code class="filename">lang/gcc46</code></a> or install a binary gcc
1.1 dsieger 1625: package, then remove gcc used during bootstrapping.</p>
1.10 hubertf 1626: <p>Binary packages of gcc can be found through <a class="ulink" href="http://www.sunfreeware.com/" target="_top">http://www.sunfreeware.com/</a>.</p>
1.1 dsieger 1627: </div>
1.41 asau 1628: <div class="sect3">
1.1 dsieger 1629: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1630: <a name="solaris-sun-workshop-note"></a>3.3.10.2. If you are using Sun WorkShop</h4></div></div></div>
1.1 dsieger 1631: <p>You will need at least the following packages installed (from WorkShop
1632: 5.0)</p>
1.41 asau 1633: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1634: <li class="listitem"><p>SPROcc
1.1 dsieger 1635: - Sun WorkShop Compiler C 5.0</p></li>
1.23 wiz 1636: <li class="listitem"><p>SPROcpl
1.1 dsieger 1637: - Sun WorkShop Compiler C++ 5.0</p></li>
1.23 wiz 1638: <li class="listitem"><p>SPROild
1.1 dsieger 1639: - Sun WorkShop Incremental Linker</p></li>
1.23 wiz 1640: <li class="listitem"><p>SPROlang
1.1 dsieger 1641: - Sun WorkShop Compilers common components</p></li>
1642: </ul></div>
1643: <p>You should set the following variables in your
1.10 hubertf 1644: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:</p>
1.1 dsieger 1645: <pre class="programlisting">
1646: CC= cc
1647: CXX= CC
1648: CPP= cc -E
1649: CXXCPP= CC -E
1650: </pre>
1.41 asau 1651: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1652: <h3 class="title">Note</h3>
1653: <p>The <code class="varname">CPP</code> setting might break some
1654: packages that use the C preprocessor for processing things other
1655: than C source code.</p>
1656: </div>
1657: </div>
1.41 asau 1658: <div class="sect3">
1.1 dsieger 1659: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1660: <a name="solaris-sunpro-64"></a>3.3.10.3. Building 64-bit binaries with SunPro</h4></div></div></div>
1.1 dsieger 1661: <p>To build 64-bit packages, you just need to have the
1.10 hubertf 1662: following lines in your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:</p>
1.1 dsieger 1663: <pre class="programlisting">
1664: PKGSRC_COMPILER= sunpro
1665: ABI= 64
1666: </pre>
1.41 asau 1667: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 1668: <h3 class="title">Note</h3>
1669: <p>This setting has been tested for the SPARC
1670: architecture. Intel and AMD machines need some more
1671: work.</p>
1672: </div>
1673: </div>
1.41 asau 1674: <div class="sect3">
1.1 dsieger 1675: <div class="titlepage"><div><div><h4 class="title">
1.58 ryoon 1676: <a name="plat.sunos.problems"></a>3.3.10.4. Common problems</h4></div></div></div>
1.10 hubertf 1677: <p>Sometimes, when using <span class="command"><strong>libtool</strong></span>,
1.1 dsieger 1678: <code class="filename">/bin/ksh</code> crashes with a segmentation fault.
1679: The workaround is to use another shell for the configure
1.79 snj 1680: scripts, for example by installing <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a> and adding the following lines
1.10 hubertf 1681: to your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 1682: <pre class="programlisting">
1683: CONFIG_SHELL= ${LOCALBASE}/bin/bash
1684: WRAPPER_SHELL= ${LOCALBASE}/bin/bash
1685: </pre>
1.79 snj 1686: <p>Then, rebuild the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool-base/README.html" target="_top"><code class="filename">devel/libtool-base</code></a> package.</p>
1.1 dsieger 1687: </div>
1688: </div>
1689: </div>
1690: </div>
1.41 asau 1691: <div class="chapter">
1.1 dsieger 1692: <div class="titlepage"><div><div><h2 class="title">
1693: <a name="using"></a>Chapter 4. Using pkgsrc</h2></div></div></div>
1694: <div class="toc">
1695: <p><b>Table of Contents</b></p>
1.100 leot 1696: <dl class="toc">
1.1 dsieger 1697: <dt><span class="sect1"><a href="#using-pkg">4.1. Using binary packages</a></span></dt>
1698: <dd><dl>
1699: <dt><span class="sect2"><a href="#finding-binary-packages">4.1.1. Finding binary packages</a></span></dt>
1700: <dt><span class="sect2"><a href="#installing-binary-packages">4.1.2. Installing binary packages</a></span></dt>
1701: <dt><span class="sect2"><a href="#using.pkg_delete">4.1.3. Deinstalling packages</a></span></dt>
1702: <dt><span class="sect2"><a href="#using.pkg_info">4.1.4. Getting information about installed packages</a></span></dt>
1703: <dt><span class="sect2"><a href="#vulnerabilities">4.1.5. Checking for security vulnerabilities in installed packages</a></span></dt>
1704: <dt><span class="sect2"><a href="#pkg_versions">4.1.6. Finding if newer versions of your installed packages are in pkgsrc</a></span></dt>
1705: <dt><span class="sect2"><a href="#using.pkg_admin">4.1.7. Other administrative functions</a></span></dt>
1706: <dt><span class="sect2"><a href="#a-word-of-warning">4.1.8. A word of warning</a></span></dt>
1707: </dl></dd>
1708: <dt><span class="sect1"><a href="#building-packages-from-source">4.2. Building packages from source</a></span></dt>
1709: <dd><dl>
1710: <dt><span class="sect2"><a href="#requirements">4.2.1. Requirements</a></span></dt>
1711: <dt><span class="sect2"><a href="#fetching-distfiles">4.2.2. Fetching distfiles</a></span></dt>
1712: <dt><span class="sect2"><a href="#how-to-build-and-install">4.2.3. How to build and install</a></span></dt>
1713: </dl></dd>
1714: </dl>
1715: </div>
1716: <p>Basically, there are two ways of using pkgsrc. The first
1717: is to only install the package tools and to use binary packages
1.23 wiz 1718: that someone else has prepared. This is the <span class="quote">“<span class="quote">pkg</span>”</span>
1719: in pkgsrc. The second way is to install the <span class="quote">“<span class="quote">src</span>”</span>
1.1 dsieger 1720: of pkgsrc, too. Then you are able to build your own packages,
1721: and you can still use binary packages from someone else.</p>
1.41 asau 1722: <div class="sect1">
1.1 dsieger 1723: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1724: <a name="using-pkg"></a>4.1. Using binary packages</h2></div></div></div>
1.10 hubertf 1725: <p>On the <a class="ulink" href="ftp://ftp.NetBSD.org/" target="_top">ftp.NetBSD.org</a>
1.9 rillig 1726: server and its mirrors, there are collections of binary packages,
1727: ready to be installed. These binary packages have been built using the
1728: default settings for the directories, that is:</p>
1.41 asau 1729: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 1730: <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>
1731: <li class="listitem"><p><code class="filename">/usr/pkg/etc</code> for configuration files,</p></li>
1732: <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 1733: </ul></div>
1734: <p>If you cannot use these directories for whatever reasons (maybe
1735: because you're not root), you cannot use these binary packages, but
1.10 hubertf 1736: have to build the packages yourself, which is explained in <a class="xref" href="#bootstrapping-pkgsrc" title="3.2. Bootstrapping pkgsrc">Section 3.2, “Bootstrapping pkgsrc”</a>.</p>
1.41 asau 1737: <div class="sect2">
1.1 dsieger 1738: <div class="titlepage"><div><div><h3 class="title">
1739: <a name="finding-binary-packages"></a>4.1.1. Finding binary packages</h3></div></div></div>
1.5 weinem 1740: <p>To install binary packages, you first need to know from where
1741: to get them. The first place where you should look is on the main
1.10 hubertf 1742: pkgsrc FTP server in the directory <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/" target="_top"><code class="filename">/pub/pkgsrc/packages</code></a>.</p>
1.5 weinem 1743: <p>This directory contains binary packages for multiple
1744: platforms. First, select your operating system. (Ignore the
1745: directories with version numbers attached to it, they just exist for
1746: legacy reasons.) Then, select your hardware architecture, and in the
1.23 wiz 1747: third step, the OS version and the <span class="quote">“<span class="quote">version</span>”</span> of pkgsrc.</p>
1.9 rillig 1748: <p>In this directory, you often find a file called
1749: <code class="filename">bootstrap.tar.gz</code> which contains the package
1750: management tools. If the file is missing, it is likely that your
1751: operating system already provides those tools. Download the file and
1752: extract it in the <code class="filename">/</code> directory. It will create
1753: the directories <code class="filename">/usr/pkg</code> (containing the tools
1754: for managing binary packages) and <code class="filename">/var/db/pkg</code>
1755: (the database of installed packages).</p>
1.1 dsieger 1756: </div>
1.41 asau 1757: <div class="sect2">
1.1 dsieger 1758: <div class="titlepage"><div><div><h3 class="title">
1759: <a name="installing-binary-packages"></a>4.1.2. Installing binary packages</h3></div></div></div>
1.9 rillig 1760: <p>In the directory from the last section, there is a
1.85 wiz 1761: subdirectory called <code class="filename">All/</code>, which contains all the
1.9 rillig 1762: binary packages that are available for the platform, excluding those
1763: that may not be distributed via FTP or CDROM (depending on which
1.23 wiz 1764: medium you are using).</p>
1.9 rillig 1765: <p>To install packages directly from an FTP or HTTP server, run
1766: the following commands in a Bourne-compatible shell (be sure to
1.10 hubertf 1767: <span class="command"><strong>su</strong></span> to root first):</p>
1.9 rillig 1768: <pre class="screen">
1769: <code class="prompt">#</code> <strong class="userinput"><code>PATH="/usr/pkg/sbin:$PATH"</code></strong>
1.85 wiz 1770: <code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/<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 1771: <code class="prompt">#</code> <strong class="userinput"><code>export PATH PKG_PATH</code></strong>
1772: </pre>
1773: <p>Instead of URLs, you can also use local paths, for example if
1774: you are installing from a set of CDROMs, DVDs or an NFS-mounted
1775: repository. If you want to install packages from multiple sources,
1776: you can separate them by a semicolon in
1777: <code class="varname">PKG_PATH</code>.</p>
1778: <p>After these preparations, installing a package is very
1779: easy:</p>
1780: <pre class="screen">
1781: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add openoffice2</code></strong>
1782: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add kde-3.5.7</code></strong>
1783: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add ap2-php5-*</code></strong>
1784: </pre>
1.1 dsieger 1785: <p>Note that any prerequisite packages needed to run the
1786: package in question will be installed, too, assuming they are
1787: present where you install from.</p>
1.23 wiz 1788: <p>Adding packages might install vulnerable packages.
1789: Thus you should run <span class="command"><strong>pkg_admin audit</strong></span>
1.14 jmcneill 1790: regularly, especially after installing new packages, and verify
1791: that the vulnerabilities are acceptable for your configuration.</p>
1.1 dsieger 1792: <p>After you've installed packages, be sure to have
1793: <code class="filename">/usr/pkg/bin</code> and <code class="filename">/usr/pkg/sbin</code> in your
1794: <code class="varname">PATH</code> so you can actually start the just
1795: installed program.</p>
1796: </div>
1.41 asau 1797: <div class="sect2">
1.1 dsieger 1798: <div class="titlepage"><div><div><h3 class="title">
1799: <a name="using.pkg_delete"></a>4.1.3. Deinstalling packages</h3></div></div></div>
1800: <p>To deinstall a package, it does not matter whether it was
1801: installed from source code or from a binary package. The
1.10 hubertf 1802: <span class="command"><strong>pkg_delete</strong></span> command does not know it anyway.
1803: To delete a package, you can just run <span class="command"><strong>pkg_delete
1.1 dsieger 1804: <em class="replaceable"><code>package-name</code></em></strong></span>. The package
1805: name can be given with or without version number. Wildcards can
1806: also be used to deinstall a set of packages, for example
1807: <code class="literal">*emacs*</code>. Be sure to include them in quotes,
1808: so that the shell does not expand them before
1809: <code class="literal">pkg_delete</code> sees them.</p>
1810: <p>The <code class="option">-r</code> option is very powerful: it
1811: removes all the packages that require the package in question
1812: and then removes the package itself. For example:
1813:
1814: </p>
1815: <pre class="screen">
1816: <code class="prompt">#</code> <strong class="userinput"><code>pkg_delete -r jpeg</code></strong>
1817: </pre>
1818: <p>
1819:
1820: will remove jpeg and all the packages that used it; this allows
1821: upgrading the jpeg package.</p>
1822: </div>
1.41 asau 1823: <div class="sect2">
1.1 dsieger 1824: <div class="titlepage"><div><div><h3 class="title">
1825: <a name="using.pkg_info"></a>4.1.4. Getting information about installed packages</h3></div></div></div>
1.10 hubertf 1826: <p>The <span class="command"><strong>pkg_info</strong></span> shows information about
1.1 dsieger 1827: installed packages or binary package files.</p>
1828: </div>
1.41 asau 1829: <div class="sect2">
1.1 dsieger 1830: <div class="titlepage"><div><div><h3 class="title">
1831: <a name="vulnerabilities"></a>4.1.5. Checking for security vulnerabilities in installed packages</h3></div></div></div>
1832: <p>
1833: The NetBSD Security-Officer and Packages Groups maintain a list of
1834: known security vulnerabilities to packages which are (or have been)
1835: included in pkgsrc. The list is available from the NetBSD
1.10 hubertf 1836: FTP site at <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities</a>.
1.1 dsieger 1837: </p>
1838: <p>
1.22 jakllsch 1839: Through <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1.1 dsieger 1840: this list can be downloaded
1841: automatically, and a security audit of all packages installed on a system
1842: can take place.
1843: </p>
1844: <p>
1.22 jakllsch 1845: There are two components to auditing. The first
1846: step, <span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>,
1847: is for downloading
1.1 dsieger 1848: the list of vulnerabilities from the NetBSD FTP site. The second
1.22 jakllsch 1849: step, <span class="command"><strong>pkg_admin audit</strong></span>, checks to see if any of your
1.1 dsieger 1850: installed packages are vulnerable. If a package is vulnerable, you
1851: will see output similar to the following:
1852: </p>
1853: <pre class="screen">Package samba-2.0.9 has a local-root-shell vulnerability, see
1854: http://www.samba.org/samba/whatsnew/macroexploit.html</pre>
1855: <p>
1.22 jakllsch 1856: You may wish to have the
1.10 hubertf 1857: <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities" target="_top">vulnerabilities</a>
1.22 jakllsch 1858: file downloaded daily so that
1859: it remains current. This may be done by adding an appropriate entry
1.79 snj 1860: to the root users <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?crontab+5+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
1.22 jakllsch 1861: </p>
1862: <pre class="screen">
1863: # download vulnerabilities file
1864: 0 3 * * * /usr/sbin/pkg_admin fetch-pkg-vulnerabilities >/dev/null 2>&1
1865: </pre>
1866: <p>
1867: will update the vulnerability list every day at 3AM. You may wish to do
1868: this more often than once a day.
1869:
1870: In addition, you may wish to run the package audit from the daily
1871: security script. This may be accomplished by adding the following
1872: line to <code class="filename">/etc/security.local</code>:
1873: </p>
1874: <pre class="screen">
1875: /usr/sbin/pkg_admin audit
1876: </pre>
1877: <p>
1.1 dsieger 1878: </p>
1879: </div>
1.41 asau 1880: <div class="sect2">
1.1 dsieger 1881: <div class="titlepage"><div><div><h3 class="title">
1882: <a name="pkg_versions"></a>4.1.6. Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div>
1883: <p>
1.79 snj 1884: Install <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html" target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
1.23 wiz 1885: <span class="command"><strong>lintpkgsrc</strong></span> with the <span class="quote">“<span class="quote">-i</span>”</span>
1.1 dsieger 1886: argument to check if your packages are up-to-date, e.g.
1887: </p>
1888: <pre class="screen">
1889: <code class="prompt">%</code> <strong class="userinput"><code>lintpkgsrc -i</code></strong>
1890: ...
1891: Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
1892: </pre>
1.10 hubertf 1893: <p>You can then use <span class="command"><strong>make update</strong></span> to update the
1.1 dsieger 1894: package on your system and rebuild any dependencies.
1895: </p>
1896: </div>
1.41 asau 1897: <div class="sect2">
1.1 dsieger 1898: <div class="titlepage"><div><div><h3 class="title">
1899: <a name="using.pkg_admin"></a>4.1.7. Other administrative functions</h3></div></div></div>
1.10 hubertf 1900: <p>The <span class="command"><strong>pkg_admin</strong></span> executes various
1.1 dsieger 1901: administrative functions on the package system.</p>
1902: </div>
1.41 asau 1903: <div class="sect2">
1.1 dsieger 1904: <div class="titlepage"><div><div><h3 class="title">
1905: <a name="a-word-of-warning"></a>4.1.8. A word of warning</h3></div></div></div>
1906: <p>Please pay very careful attention to the warnings
1.79 snj 1907: expressed in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> manual page about the
1.1 dsieger 1908: inherent dangers of installing binary packages which you did
1909: not create yourself, and the security holes that can be
1910: introduced onto your system by indiscriminate adding of such
1911: files.</p>
1912: <p>The same warning of course applies to every package you
1913: install from source when you haven't completely read and
1914: understood the source code of the package, the compiler that
1915: is used to build the package and all the other tools that are
1916: involved.</p>
1917: </div>
1918: </div>
1.41 asau 1919: <div class="sect1">
1.1 dsieger 1920: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1921: <a name="building-packages-from-source"></a>4.2. Building packages from source</h2></div></div></div>
1922: <p>After obtaining pkgsrc, the <code class="filename">pkgsrc</code>
1923: directory now contains a set of packages, organized into
1924: categories. You can browse the online index of packages, or run
1.10 hubertf 1925: <span class="command"><strong>make readme</strong></span> from the <code class="filename">pkgsrc</code>
1.1 dsieger 1926: directory to build local <code class="filename">README.html</code> files for
1.79 snj 1927: all packages, viewable with any web browser such as <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html" target="_top"><code class="filename">www/lynx</code></a> or <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html" target="_top"><code class="filename">www/firefox</code></a>.</p>
1.1 dsieger 1928: <p>The default <span class="emphasis"><em>prefix</em></span> for installed packages
1929: is <code class="filename">/usr/pkg</code>. If you wish to change this, you
1930: should do so by setting <code class="varname">LOCALBASE</code> in
1.10 hubertf 1931: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. You should not try to use multiple
1.1 dsieger 1932: different <code class="varname">LOCALBASE</code> definitions on the same
1933: system (inside a chroot is an exception). </p>
1934: <p>The rest of this chapter assumes that the package is already
1.10 hubertf 1935: 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 1936: instructions how to create your own packages.</p>
1.41 asau 1937: <div class="sect2">
1.1 dsieger 1938: <div class="titlepage"><div><div><h3 class="title">
1939: <a name="requirements"></a>4.2.1. Requirements</h3></div></div></div>
1940: <p>To build packages from source, you need a working C
1941: compiler. On NetBSD, you need to install the
1.23 wiz 1942: <span class="quote">“<span class="quote">comp</span>”</span> and the <span class="quote">“<span class="quote">text</span>”</span> distribution
1.1 dsieger 1943: sets. If you want to build X11-related packages, the
1.23 wiz 1944: <span class="quote">“<span class="quote">xbase</span>”</span> and <span class="quote">“<span class="quote">xcomp</span>”</span> distribution
1.1 dsieger 1945: sets are required, too.</p>
1946: </div>
1.41 asau 1947: <div class="sect2">
1.1 dsieger 1948: <div class="titlepage"><div><div><h3 class="title">
1949: <a name="fetching-distfiles"></a>4.2.2. Fetching distfiles</h3></div></div></div>
1950: <p>The first step for building a package is downloading the
1951: distfiles (i.e. the unmodified source). If they have not yet been
1952: downloaded, pkgsrc will fetch them automatically.</p>
1953: <p>If you have all files that you need in the
1954: <code class="filename">distfiles</code> directory,
1955: you don't need to connect. If the distfiles are on CD-ROM, you can
1956: mount the CD-ROM on <code class="filename">/cdrom</code> and add:
1957: </p>
1958: <pre class="screen">DISTDIR=/cdrom/pkgsrc/distfiles</pre>
1959: <p>
1.10 hubertf 1960: to your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 1961: <p>By default a list of distribution sites will be randomly
1962: intermixed to prevent huge load on servers which holding popular
1963: packages (for example, SourceForge.net mirrors). Thus, every
1964: time when you need to fetch yet another distfile all the mirrors
1965: will be tried in new (random) order. You can turn this feature
1966: off by setting <code class="varname">MASTER_SORT_RANDOM=NO</code> (for
1967: <code class="varname">PKG_DEVELOPER</code>s it's already disabled).</p>
1968: <p>You can overwrite some of the major distribution sites to
1969: fit to sites that are close to your own. By setting one or two
1970: variables you can modify the order in which the master sites are
1971: accessed. <code class="varname">MASTER_SORT</code> contains a whitespace
1972: delimited list of domain suffixes.
1973: <code class="varname">MASTER_SORT_REGEX</code> is even more flexible, it
1974: contains a whitespace delimited list of regular expressions. It
1975: has higher priority than <code class="varname">MASTER_SORT</code>. Have a
1976: look at <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to find
1977: some examples. This may save some of your bandwidth and
1978: time.</p>
1979: <p>You can change these settings either in your shell's environment, or,
1980: if you want to keep the settings, by editing the
1.10 hubertf 1981: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file,
1.1 dsieger 1982: and adding the definitions there.</p>
1983: <p>
1984: If a package depends on many other packages (such as
1.79 snj 1985: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html" target="_top"><code class="filename">meta-pkgs/kde3</code></a>), the build process may
1.1 dsieger 1986: alternate between periods of
1987: downloading source, and compiling. To ensure you have all the source
1988: downloaded initially you can run the command:
1989: </p>
1990: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch-list | sh</code></strong></pre>
1991: <p>
1992: which will output and run a set of shell commands to fetch the
1993: necessary files into the <code class="filename">distfiles</code> directory. You can
1994: also choose to download the files manually.
1995: </p>
1996: </div>
1.41 asau 1997: <div class="sect2">
1.1 dsieger 1998: <div class="titlepage"><div><div><h3 class="title">
1999: <a name="how-to-build-and-install"></a>4.2.3. How to build and install</h3></div></div></div>
2000: <p>
2001: Once the software has downloaded, any patches will be applied, then it
2002: will be compiled for you. This may take some time depending on your
2003: computer, and how many other packages the software depends on and their
2004: compile time.
2005: </p>
1.41 asau 2006: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 2007: <h3 class="title">Note</h3>
2008: <p>If using bootstrap or pkgsrc on a non-NetBSD system,
1.10 hubertf 2009: use the pkgsrc <span class="command"><strong>bmake</strong></span> command instead of
1.23 wiz 2010: <span class="quote">“<span class="quote">make</span>”</span> in the examples in this guide.</p>
1.1 dsieger 2011: </div>
2012: <p>For example, type</p>
2013: <pre class="screen">
2014: <code class="prompt">%</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
2015: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
2016: </pre>
2017: <p>at the shell prompt to build the various components of the
2018: package.</p>
2019: <p>The next stage is to actually install the newly compiled
2020: program onto your system. Do this by entering:
2021:
2022: </p>
2023: <pre class="screen">
2024: <code class="prompt">%</code> <strong class="userinput"><code>make install</code></strong>
2025: </pre>
2026: <p>
2027:
2028: while you are still in the directory for whatever package you
2029: are installing.</p>
2030: <p>Installing the package on your system may require you to
2031: be root. However, pkgsrc has a
2032: <span class="emphasis"><em>just-in-time-su</em></span> feature, which allows you
2033: to only become root for the actual installation step.</p>
2034: <p>That's it, the software should now be installed and setup for use.
2035: You can now enter:
2036:
2037: </p>
2038: <pre class="screen">
2039: <code class="prompt">%</code> <strong class="userinput"><code>make clean</code></strong>
2040: </pre>
2041: <p>
2042:
2043: to remove the compiled files in the work directory, as you shouldn't need
2044: them any more. If other packages were also added to your system
2045: (dependencies) to allow your program to compile, you can tidy these up
2046: also with the command:</p>
2047: <pre class="screen">
2048: <code class="prompt">%</code> <strong class="userinput"><code>make clean-depends</code></strong>
2049: </pre>
2050: <p>Taking the figlet utility as an example, we can install it on our
1.10 hubertf 2051: system by building as shown in <a class="xref" href="#logs" title="Appendix B. Build logs">Appendix B, <i>Build logs</i></a>.</p>
1.1 dsieger 2052: <p>The program is installed under the default root of the
2053: packages tree - <code class="filename">/usr/pkg</code>. Should this not
2054: conform to your tastes, set the <code class="varname">LOCALBASE</code>
2055: variable in your environment, and it will use that value as the
2056: root of your packages tree. So, to use
2057: <code class="filename">/usr/local</code>, set
2058: <code class="varname">LOCALBASE=/usr/local</code> in your environment.
2059: Please note that you should use a directory which is dedicated to
2060: packages and not shared with other programs (i.e., do not try and
2061: use <code class="varname">LOCALBASE=/usr</code>). Also, you should not try
2062: to add any of your own files or directories (such as
2063: <code class="filename">src/</code>, <code class="filename">obj/</code>, or
2064: <code class="filename">pkgsrc/</code>) below the
2065: <code class="varname">LOCALBASE</code> tree. This is to prevent possible
2066: conflicts between programs and other files installed by the
2067: package system and whatever else may have been installed
2068: there.</p>
1.10 hubertf 2069: <p>Some packages look in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.1 dsieger 2070: alter some configuration options at build time. Have a look at
2071: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> to get an overview
2072: of what will be set there by default. Environment variables such
2073: as <code class="varname">LOCALBASE</code> can be set in
1.10 hubertf 2074: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to save having to remember to
1.1 dsieger 2075: set them each time you want to use pkgsrc.</p>
1.23 wiz 2076: <p>Occasionally, people want to <span class="quote">“<span class="quote">look under the
2077: covers</span>”</span> to see what is going on when a package is building
1.1 dsieger 2078: or being installed. This may be for debugging purposes, or out of
2079: simple curiosity. A number of utility values have been added to
2080: help with this.</p>
1.23 wiz 2081: <div class="orderedlist"><ol class="orderedlist" type="1">
2082: <li class="listitem">
1.79 snj 2083: <p>If you invoke the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> command with
1.1 dsieger 2084: <code class="varname">PKG_DEBUG_LEVEL=2</code>, then a huge amount of
2085: information will be displayed. For example,</p>
2086: <pre class="screen"><strong class="userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong></pre>
2087: <p>will show all the commands that are invoked, up to and
1.23 wiz 2088: including the <span class="quote">“<span class="quote">patch</span>”</span> stage.</p>
1.1 dsieger 2089: </li>
1.23 wiz 2090: <li class="listitem">
1.79 snj 2091: <p>If you want to know the value of a certain <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 2092: definition, then the <code class="varname">VARNAME</code> definition
2093: should be used, in conjunction with the show-var
1.79 snj 2094: target. e.g. to show the expansion of the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 2095: variable <code class="varname">LOCALBASE</code>:</p>
2096: <pre class="screen">
2097: <code class="prompt">%</code> <strong class="userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
2098: /usr/pkg
2099: <code class="prompt">%</code>
2100: </pre>
2101: </li>
2102: </ol></div>
2103: <p>If you want to install a binary package that you've either
2104: created yourself (see next section), that you put into
2105: pkgsrc/packages manually or that is located on a remote FTP
2106: server, you can use the "bin-install" target. This target will
1.79 snj 2107: install a binary package - if available - via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>,
1.10 hubertf 2108: else do a <span class="command"><strong>make package</strong></span>. The list of remote FTP
1.1 dsieger 2109: sites searched is kept in the variable
2110: <code class="varname">BINPKG_SITES</code>, which defaults to
1.79 snj 2111: ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>
1.1 dsieger 2112: can be put into <code class="varname">BIN_INSTALL_FLAGS</code>. See
2113: <code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more
2114: details.</p>
2115: <p>A final word of warning: If you set up a system that has a
2116: non-standard setting for <code class="varname">LOCALBASE</code>, be sure to
2117: set that before any packages are installed, as you cannot use
2118: several directories for the same purpose. Doing so will result in
2119: pkgsrc not being able to properly detect your installed packages,
2120: and fail miserably. Note also that precompiled binary packages are
2121: usually built with the default <code class="varname">LOCALBASE</code> of
2122: <code class="filename">/usr/pkg</code>, and that you should
2123: <span class="emphasis"><em>not</em></span> install any if you use a non-standard
2124: <code class="varname">LOCALBASE</code>.</p>
2125: </div>
2126: </div>
2127: </div>
1.41 asau 2128: <div class="chapter">
1.1 dsieger 2129: <div class="titlepage"><div><div><h2 class="title">
2130: <a name="configuring"></a>Chapter 5. Configuring pkgsrc</h2></div></div></div>
2131: <div class="toc">
2132: <p><b>Table of Contents</b></p>
1.100 leot 2133: <dl class="toc">
1.1 dsieger 2134: <dt><span class="sect1"><a href="#general-configuration">5.1. General configuration</a></span></dt>
2135: <dt><span class="sect1"><a href="#variables-affecting-build">5.2. Variables affecting the build process</a></span></dt>
1.9 rillig 2136: <dt><span class="sect1"><a href="#variables-affecting-installation">5.3. Variables affecting the installation process</a></span></dt>
1.4 rillig 2137: <dt><span class="sect1"><a href="#conf.compiler">5.4. Selecting and configuring the compiler</a></span></dt>
1.1 dsieger 2138: <dd><dl>
1.4 rillig 2139: <dt><span class="sect2"><a href="#selecting-the-compiler">5.4.1. Selecting the compiler</a></span></dt>
1.23 wiz 2140: <dt><span class="sect2"><a href="#conf.cflags">5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</a></span></dt>
2141: <dt><span class="sect2"><a href="#conf.ldflags">5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</a></span></dt>
1.1 dsieger 2142: </dl></dd>
1.4 rillig 2143: <dt><span class="sect1"><a href="#developer-advanced-settings">5.5. Developer/advanced settings</a></span></dt>
2144: <dt><span class="sect1"><a href="#selecting-build-options">5.6. Selecting Build Options</a></span></dt>
1.1 dsieger 2145: </dl>
2146: </div>
1.4 rillig 2147: <a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
1.1 dsieger 2148: called <code class="filename">mk.conf</code>. In which directory pkgsrc looks for
2149: that file depends on the installation. On NetBSD, when you use
1.79 snj 2150: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it is in the directory
1.1 dsieger 2151: <code class="filename">/etc/</code>. In all other cases the default location is
2152: <code class="literal">${PREFIX}/etc/</code>, depending on where you told the
2153: bootstrap program to install the binary packages.</p>
2154: <p>During the bootstrap, an example configuration file is created. To
2155: use that, you have to create the directory
2156: <code class="filename">${PREFIX}/etc</code> and copy the example file
2157: there.</p>
2158: <p>The format of the configuration file is that of the usual
2159: BSD-style <code class="filename">Makefile</code>s. The whole pkgsrc configuration
2160: is done by setting variables in this file. Note that you can define all
2161: kinds of variables, and no special error checking (for example for
2162: spelling mistakes) takes place, so you have to try it out to see if it
2163: works.</p>
1.41 asau 2164: <div class="sect1">
1.1 dsieger 2165: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2166: <a name="general-configuration"></a>5.1. General configuration</h2></div></div></div>
2167: <p>In this section, you can find some variables that apply to all
2168: pkgsrc packages. A complete list of the variables that can be
2169: configured by the user is available in
2170: <code class="filename">mk/defaults/mk.conf</code>, together with some
2171: comments that describe each variable's intent.</p>
1.41 asau 2172: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2173: <li class="listitem"><p><code class="varname">LOCALBASE</code>: Where
1.1 dsieger 2174: packages will be installed. The default is
2175: <code class="filename">/usr/pkg</code>. Do not mix binary packages
2176: with different <code class="varname">LOCALBASE</code>s!</p></li>
1.23 wiz 2177: <li class="listitem"><p><code class="varname">CROSSBASE</code>: Where
2178: <span class="quote">“<span class="quote">cross</span>”</span> category packages will be
1.1 dsieger 2179: installed. The default is
2180: <code class="filename">${LOCALBASE}/cross</code>.</p></li>
1.23 wiz 2181: <li class="listitem"><p><code class="varname">X11BASE</code>: Where
1.1 dsieger 2182: X11 is installed on the system. The default is
1.84 wiz 2183: <code class="filename">/usr/X11R7</code>.</p></li>
1.23 wiz 2184: <li class="listitem"><p><code class="varname">DISTDIR</code>: Where to store the
1.1 dsieger 2185: downloaded copies of the original source distributions used
2186: for building pkgsrc packages. The default is
2187: <code class="filename">${PKGSRCDIR}/distfiles</code>.</p></li>
1.23 wiz 2188: <li class="listitem"><p><code class="varname">PKG_DBDIR</code>: Where the
1.1 dsieger 2189: database about installed packages is stored. The default is
2190: <code class="filename">/var/db/pkg</code>.</p></li>
1.23 wiz 2191: <li class="listitem"><p><code class="varname">MASTER_SITE_OVERRIDE</code>:
1.1 dsieger 2192: If set, override the packages'
2193: <code class="varname">MASTER_SITES</code> with this value.</p></li>
1.23 wiz 2194: <li class="listitem"><p><code class="varname">MASTER_SITE_BACKUP</code>:
1.1 dsieger 2195: Backup location(s) for distribution files and patch files
2196: if not found locally or in
2197: <code class="filename">${MASTER_SITES}</code> or
2198: <code class="filename">${PATCH_SITES}</code> respectively.
2199: The defaults are
1.25 spz 2200: <code class="filename">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}/</code>
1.1 dsieger 2201: and
2202: <code class="filename">ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/${DIST_SUBDIR}/</code>.</p></li>
1.23 wiz 2203: <li class="listitem"><p><code class="varname">BINPKG_SITES</code>:
1.1 dsieger 2204: List of sites carrying binary pkgs. <em class="replaceable"><code>rel</code></em> and
2205: <em class="replaceable"><code>arch</code></em> are replaced with OS
1.23 wiz 2206: release (<span class="quote">“<span class="quote">2.0</span>”</span>, etc.) and architecture
2207: (<span class="quote">“<span class="quote">mipsel</span>”</span>, etc.).</p></li>
2208: <li class="listitem"><p><code class="varname">ACCEPTABLE_LICENSES</code>:
1.22 jakllsch 2209: List of acceptable licenses. License names are case-sensitive.
2210: Whenever you try to build a package whose license is not in this
2211: list, you will get an error message. If the license condition is
2212: simple enough, the error message will include specific
2213: instructions on how to change this variable.</p></li>
1.1 dsieger 2214: </ul></div>
2215: </div>
1.41 asau 2216: <div class="sect1">
1.1 dsieger 2217: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2218: <a name="variables-affecting-build"></a>5.2. Variables affecting the build process</h2></div></div></div>
2219: <p>XXX
2220: </p>
1.41 asau 2221: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2222: <li class="listitem"><p><code class="varname">PACKAGES</code>: The top level
1.1 dsieger 2223: directory for the binary packages. The default is
2224: <code class="filename">${PKGSRCDIR}/packages</code>.</p></li>
1.23 wiz 2225: <li class="listitem"><p><code class="varname">WRKOBJDIR</code>:
1.1 dsieger 2226: The top level directory where, if defined, the separate
2227: working directories will get created, and symbolically
2228: linked to from <code class="filename">${WRKDIR}</code> (see below).
2229: This is useful for building packages on several
2230: architectures, then <code class="filename">${PKGSRCDIR}</code>
2231: can be NFS-mounted while <code class="filename">${WRKOBJDIR}</code>
2232: is local to every architecture. (It should be noted that
2233: <code class="varname">PKGSRCDIR</code> should not be set by the user
1.14 jmcneill 2234: — it is an internal definition which refers to the
1.1 dsieger 2235: root of the pkgsrc tree. It is possible to have many
2236: pkgsrc tree instances.)</p></li>
1.23 wiz 2237: <li class="listitem"><p><code class="varname">LOCALPATCHES</code>:
1.1 dsieger 2238: Directory for local patches that aren't part of pkgsrc.
1.10 hubertf 2239: See <a class="xref" href="#components.patches" title="11.3. patches/*">Section 11.3, “patches/*”</a> for more
1.1 dsieger 2240: information.</p></li>
1.23 wiz 2241: <li class="listitem"><p><code class="varname">PKGMAKECONF</code>: Location of
1.10 hubertf 2242: the <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file used by a package's
1.1 dsieger 2243: BSD-style Makefile. If this is not set,
2244: <code class="varname">MAKECONF</code> is set to
2245: <code class="filename">/dev/null</code> to avoid picking up
2246: settings used by builds in <code class="filename">/usr/src</code>.</p></li>
1.23 wiz 2247: <li class="listitem"><p><code class="varname">DEPENDS_TARGET</code>:
1.1 dsieger 2248: By default, dependencies are only installed, and no binary
2249: package is created for them. You can set this variable to
1.66 asau 2250: <code class="literal">package-install</code> to automatically create binary
1.80 wiz 2251: packages after installing dependencies. Please note that the
1.84 wiz 2252: <code class="varname">PKGSRC_KEEP_BIN_PKGS</code> can be set to
1.80 wiz 2253: <code class="literal">yes</code> to preserve binary packages when
2254: using the <code class="literal">install</code> as well.</p></li>
1.1 dsieger 2255: </ul></div>
2256: </div>
1.41 asau 2257: <div class="sect1">
1.1 dsieger 2258: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.9 rillig 2259: <a name="variables-affecting-installation"></a>5.3. Variables affecting the installation process</h2></div></div></div>
1.24 wiz 2260: <p>Most packages support installation into a
1.4 rillig 2261: subdirectory of <code class="varname">WRKDIR</code>. This allows a package
2262: to be built, before the actual filesystem is touched. DESTDIR
2263: support exists in two variations:</p>
1.41 asau 2264: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2265: <li class="listitem"><p>Basic DESTDIR support means that the package
1.24 wiz 2266: installation and packaging is still run as root.</p></li>
2267: <li class="listitem"><p>Full DESTDIR support can run the complete
2268: build, installation and packaging as normal user. Root
2269: privileges are only needed to add packages.</p></li>
2270: </ul></div>
2271: <p>DESTDIR support is now the default. To switch back to non-DESTDIR,
2272: you can set
2273: <code class="varname">USE_DESTDIR=no</code>; this setting will be deprecated though,
2274: so it's preferable to convert a package to DESTDIR instead.</p>
1.4 rillig 2275: <p>With basic DESTDIR support, <strong class="userinput"><code>make
2276: clean</code></strong> needs to be run as root.</p>
1.17 imil 2277: <p>Considering the <code class="filename">foo/bar</code> package,
2278: DESTDIR full support can be tested using the following commands
2279:
2280: </p>
2281: <pre class="programlisting">
2282: <code class="prompt">$</code> id
2283: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
2284: <code class="prompt">$</code> mkdir $HOME/packages
2285: <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
2286: </pre>
2287: <p>
2288:
2289: Verify <code class="varname">DESTDIR</code> full support, no root privileges
2290: should be needed
2291:
2292: </p>
2293: <pre class="programlisting">
1.66 asau 2294: <code class="prompt">$</code> make stage-install
1.17 imil 2295: </pre>
2296: <p>
2297:
2298: Create a package without root privileges
2299:
2300: </p>
2301: <pre class="programlisting">
1.66 asau 2302: <code class="prompt">$</code> make PACKAGES=$HOME/packages package
1.17 imil 2303: </pre>
2304: <p>
2305:
2306: For the following command, you must be able to gain root
1.79 snj 2307: privileges using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
1.17 imil 2308:
2309: </p>
2310: <pre class="programlisting">
1.66 asau 2311: <code class="prompt">$</code> make PACKAGES=$HOME/packages install
1.17 imil 2312: </pre>
2313: <p>
2314:
2315: Then, as a simple user
2316:
2317: </p>
2318: <pre class="programlisting">
2319: <code class="prompt">$</code> make clean
2320: </pre>
2321: <p>
2322:
2323: </p>
1.4 rillig 2324: </div>
1.41 asau 2325: <div class="sect1">
1.4 rillig 2326: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2327: <a name="conf.compiler"></a>5.4. Selecting and configuring the compiler</h2></div></div></div>
1.41 asau 2328: <div class="sect2">
1.1 dsieger 2329: <div class="titlepage"><div><div><h3 class="title">
1.4 rillig 2330: <a name="selecting-the-compiler"></a>5.4.1. Selecting the compiler</h3></div></div></div>
1.1 dsieger 2331: <p>By default, pkgsrc will use GCC to build packages. This may be
2332: overridden by setting the following variables in /etc/mk.conf:</p>
1.41 asau 2333: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2334: <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
2335: <dd>
2336: <p>This is a list of values specifying the chain of
2337: compilers to invoke when building packages. Valid values
2338: are:</p>
1.41 asau 2339: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.66 asau 2340: <li class="listitem"><p><code class="varname">ccc</code>:
2341: Compaq C Compilers (Tru64)</p></li>
2342: <li class="listitem"><p><code class="varname">ccache</code>:
2343: compiler cache (chainable)</p></li>
2344: <li class="listitem"><p><code class="varname">clang</code>:
2345: Clang C and Objective-C compiler</p></li>
1.23 wiz 2346: <li class="listitem"><p><code class="varname">distcc</code>:
1.1 dsieger 2347: distributed C/C++ (chainable)</p></li>
1.66 asau 2348: <li class="listitem"><p><code class="varname">f2c</code>:
2349: Fortran 77 to C compiler (chainable)</p></li>
2350: <li class="listitem"><p><code class="varname">icc</code>:
2351: Intel C++ Compiler (Linux)</p></li>
2352: <li class="listitem"><p><code class="varname">ido</code>:
2353: SGI IRIS Development Option cc (IRIX 5)</p></li>
1.23 wiz 2354: <li class="listitem"><p><code class="varname">gcc</code>:
1.1 dsieger 2355: GNU C/C++ Compiler</p></li>
1.66 asau 2356: <li class="listitem"><p><code class="varname">hp</code>:
2357: HP-UX C/aC++ compilers</p></li>
1.23 wiz 2358: <li class="listitem"><p><code class="varname">mipspro</code>:
1.1 dsieger 2359: Silicon Graphics, Inc. MIPSpro (n32/n64)</p></li>
1.66 asau 2360: <li class="listitem"><p><code class="varname">mipspro-ucode</code>:
1.1 dsieger 2361: Silicon Graphics, Inc. MIPSpro (o32)</p></li>
1.23 wiz 2362: <li class="listitem"><p><code class="varname">sunpro</code>:
1.1 dsieger 2363: Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio</p></li>
1.66 asau 2364: <li class="listitem"><p><code class="varname">xlc</code>:
2365: IBM's XL C/C++ compiler suite (Darwin/MacOSX)</p></li>
1.1 dsieger 2366: </ul></div>
2367: <p>The default is
1.23 wiz 2368: <span class="quote">“<span class="quote"><code class="varname">gcc</code></span>”</span>. You can use
1.1 dsieger 2369: <code class="varname">ccache</code> and/or
2370: <code class="varname">distcc</code> with an appropriate
2371: <code class="varname">PKGSRC_COMPILER</code> setting,
1.23 wiz 2372: e.g. <span class="quote">“<span class="quote"><code class="varname">ccache gcc</code></span>”</span>. This
1.1 dsieger 2373: variable should always be terminated with a value for
2374: a real compiler. Note that only one real compiler
1.23 wiz 2375: should be listed (e.g. <span class="quote">“<span class="quote"><code class="varname">sunpro gcc</code></span>”</span>
1.1 dsieger 2376: is not allowed).</p>
2377: </dd>
2378: <dt><span class="term"><code class="varname">GCC_REQD</code>:</span></dt>
2379: <dd><p>This specifies the minimum version of GCC to use
2380: when building packages. If the system GCC doesn't
2381: satisfy this requirement, then pkgsrc will build and
2382: install one of the GCC packages to use instead.</p></dd>
2383: </dl></div>
2384: </div>
1.41 asau 2385: <div class="sect2">
1.1 dsieger 2386: <div class="titlepage"><div><div><h3 class="title">
1.4 rillig 2387: <a name="conf.cflags"></a>5.4.2. Additional flags to the compiler (<code class="varname">CFLAGS</code>)</h3></div></div></div>
1.1 dsieger 2388: <p>If you wish to set the <code class="varname">CFLAGS</code> variable,
2389: please make sure to use the <code class="literal">+=</code> operator
2390: instead of the <code class="literal">=</code> operator:</p>
2391: <pre class="programlisting">
2392: CFLAGS+= -your -flags
2393: </pre>
2394: <p>Using <code class="varname">CFLAGS=</code> (i.e. without the
1.23 wiz 2395: <span class="quote">“<span class="quote">+</span>”</span>) may lead to problems with packages that
1.16 jnemeth 2396: need to add their own flags. You may want to take a look
1.79 snj 2397: at the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html" target="_top"><code class="filename">devel/cpuflags</code></a>
1.23 wiz 2398: package if you're interested in optimization specifically
2399: for the current CPU. </p>
1.1 dsieger 2400: </div>
1.41 asau 2401: <div class="sect2">
1.1 dsieger 2402: <div class="titlepage"><div><div><h3 class="title">
1.4 rillig 2403: <a name="conf.ldflags"></a>5.4.3. Additional flags to the linker (<code class="varname">LDFLAGS</code>)</h3></div></div></div>
1.1 dsieger 2404: <p>If you want to pass flags to the linker, both in the configure
2405: step and the build step, you can do this in two ways. Either set
2406: <code class="varname">LDFLAGS</code> or <code class="varname">LIBS</code>. The difference
2407: between the two is that <code class="varname">LIBS</code> will be appended to
2408: the command line, while <code class="varname">LDFLAGS</code> come earlier.
2409: <code class="varname">LDFLAGS</code> is pre-loaded with rpath settings for ELF
2410: machines depending on the setting of <code class="varname">USE_IMAKE</code> or
2411: the inclusion of <code class="filename">mk/x11.buildlink3.mk</code>. As with
2412: <code class="varname">CFLAGS</code>, if you do not wish to override these
2413: settings, use the <code class="literal">+=</code> operator:</p>
2414: <pre class="programlisting">
2415: LDFLAGS+= -your -linkerflags
2416: </pre>
2417: </div>
2418: </div>
1.41 asau 2419: <div class="sect1">
1.1 dsieger 2420: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.4 rillig 2421: <a name="developer-advanced-settings"></a>5.5. Developer/advanced settings</h2></div></div></div>
1.84 wiz 2422: <p>
1.1 dsieger 2423: </p>
1.41 asau 2424: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2425: <li class="listitem">
1.1 dsieger 2426: <p><code class="varname">PKG_DEVELOPER</code>:
2427: Run some sanity checks that package developers want:
2428: </p>
1.41 asau 2429: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; ">
1.23 wiz 2430: <li class="listitem"><p>make sure patches apply with zero
1.1 dsieger 2431: fuzz</p></li>
1.23 wiz 2432: <li class="listitem"><p>run check-shlibs to see that all
1.1 dsieger 2433: binaries will find their shared libs.</p></li>
2434: </ul></div>
2435: <p>
2436: </p>
2437: </li>
1.23 wiz 2438: <li class="listitem"><p><code class="varname">PKG_DEBUG_LEVEL</code>: The level
1.1 dsieger 2439: of debugging output which is displayed whilst making and
2440: installing the package. The default value for this is 0,
2441: which will not display the commands as they are executed
2442: (normal, default, quiet operation); the value 1 will display
2443: all shell commands before their invocation, and the value 2
2444: will display both the shell commands before their invocation,
1.10 hubertf 2445: and their actual execution progress with <span class="command"><strong>set
1.1 dsieger 2446: -x</strong></span> will be displayed.</p></li>
2447: </ul></div>
2448: <p>
2449: </p>
2450: </div>
1.41 asau 2451: <div class="sect1">
1.1 dsieger 2452: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.4 rillig 2453: <a name="selecting-build-options"></a>5.6. Selecting Build Options</h2></div></div></div>
1.1 dsieger 2454: <p>Some packages have build time options, usually to select
2455: between different dependencies, enable optional support for big
2456: dependencies or enable experimental features.</p>
2457: <p>To see which options, if any, a package supports, and which
1.10 hubertf 2458: options are mutually exclusive, run <span class="command"><strong>make
1.1 dsieger 2459: show-options</strong></span>, for example:</p>
2460: <pre class="programlisting">
2461: The following options are supported by this package:
2462: ssl Enable SSL support.
2463: Exactly one of the following gecko options is required:
2464: firefox Use firefox as gecko rendering engine.
2465: mozilla Use mozilla as gecko rendering engine.
2466: At most one of the following database options may be selected:
2467: mysql Enable support for MySQL database.
2468: pgsql Enable support for PostgreSQL database.
2469:
2470: These options are enabled by default: firefox
2471: These options are currently enabled: mozilla ssl
2472: </pre>
2473: <p>The following variables can be defined in
1.10 hubertf 2474: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to select which options to
1.1 dsieger 2475: enable for a package: <code class="varname">PKG_DEFAULT_OPTIONS</code>,
2476: which can be used to select or disable options for all packages
2477: that support them, and
2478: <code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>,
2479: which can be used to select or disable options specifically for
2480: package <em class="replaceable"><code>pkgbase</code></em>. Options listed in
1.23 wiz 2481: these variables are selected, options preceded by <span class="quote">“<span class="quote">-</span>”</span>
1.1 dsieger 2482: are disabled. A few examples:</p>
2483: <pre class="screen">
1.10 hubertf 2484: <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 2485: PKG_DEFAULT_OPTIONS= -arts -dvdread -esound
2486: PKG_OPTIONS.kdebase= debug -sasl
2487: PKG_OPTIONS.apache= suexec </pre>
1.11 rillig 2488: <p>It is important to note that options that were specifically
1.18 snj 2489: suggested by the package maintainer must be explicitly removed if
1.11 rillig 2490: you do not wish to include the option. If you are unsure you can view
2491: the current state with <span class="command"><strong>make show-options</strong></span>.</p>
1.1 dsieger 2492: <p>The following settings are consulted in the order given, and
2493: the last setting that selects or disables an option is
2494: used:</p>
1.23 wiz 2495: <div class="orderedlist"><ol class="orderedlist" type="1">
2496: <li class="listitem"><p>the default options as suggested by the package
1.1 dsieger 2497: maintainer</p></li>
1.23 wiz 2498: <li class="listitem"><p>the options implied by the settings of legacy
1.1 dsieger 2499: variables (see below)</p></li>
1.23 wiz 2500: <li class="listitem"><p><code class="varname">PKG_DEFAULT_OPTIONS</code></p></li>
2501: <li class="listitem"><p><code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code></p></li>
1.1 dsieger 2502: </ol></div>
2503: <p>For groups of mutually exclusive options, the last option
2504: selected is used, all others are automatically disabled. If an
2505: option of the group is explicitly disabled, the previously
2506: selected option, if any, is used. It is an error if no option
2507: from a required group of options is selected, and building the
2508: package will fail.</p>
2509: <p>Before the options framework was introduced, build options
2510: were selected by setting a variable (often named
2511: <code class="varname">USE_<em class="replaceable"><code>FOO</code></em></code>) in
1.10 hubertf 2512: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> for each option. To ease
1.1 dsieger 2513: transition to the options framework for the user, these legacy
2514: variables are converted to the appropriate options setting
2515: (<code class="varname">PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em></code>)
2516: automatically. A warning is issued to prompt the user to update
1.10 hubertf 2517: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to use the options framework
1.1 dsieger 2518: directly. Support for the legacy variables will be removed
2519: eventually.</p>
2520: </div>
2521: </div>
1.41 asau 2522: <div class="chapter">
1.1 dsieger 2523: <div class="titlepage"><div><div><h2 class="title">
2524: <a name="binary"></a>Chapter 6. Creating binary packages</h2></div></div></div>
2525: <div class="toc">
2526: <p><b>Table of Contents</b></p>
1.100 leot 2527: <dl class="toc">
1.1 dsieger 2528: <dt><span class="sect1"><a href="#building-a-single-binary-package">6.1. Building a single binary package</a></span></dt>
2529: <dt><span class="sect1"><a href="#settings-for-creationg-of-binary-packages">6.2. Settings for creation of binary packages</a></span></dt>
2530: </dl>
2531: </div>
1.41 asau 2532: <div class="sect1">
1.1 dsieger 2533: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2534: <a name="building-a-single-binary-package"></a>6.1. Building a single binary package</h2></div></div></div>
2535: <p>Once you have built and installed a package, you can create
2536: a <span class="emphasis"><em>binary package</em></span> which can be installed on
1.79 snj 2537: another system with <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
1.1 dsieger 2538: the same package on a group of hosts and wasting CPU time. It also
2539: provides a simple means for others to install your package, should
2540: you distribute it.</p>
2541: <p>To create a binary package, change into the appropriate
1.10 hubertf 2542: directory in pkgsrc, and run <span class="command"><strong>make
1.1 dsieger 2543: package</strong></span>:</p>
2544: <pre class="screen">
2545: <code class="prompt">#</code> <strong class="userinput"><code>cd misc/figlet</code></strong>
2546: <code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
2547: </pre>
2548: <p>This will build and install your package (if not already done),
2549: and then build a binary package from what was installed. You can
1.10 hubertf 2550: then use the <span class="command"><strong>pkg_*</strong></span> tools to manipulate
1.1 dsieger 2551: it. Binary packages are created by default in
2552: <code class="filename">/usr/pkgsrc/packages</code>, in the form of a
1.10 hubertf 2553: gzipped tar file. See <a class="xref" href="#logs.package" title="B.2. Packaging figlet">Section B.2, “Packaging figlet”</a> for a
1.79 snj 2554: continuation of the above <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/misc/figlet/README.html" target="_top"><code class="filename">misc/figlet</code></a> example.</p>
1.10 hubertf 2555: <p>See <a class="xref" href="#submit" title="Chapter 21. Submitting and Committing">Chapter 21, <i>Submitting and Committing</i></a> for information on how to submit
1.1 dsieger 2556: such a binary package.</p>
2557: </div>
1.41 asau 2558: <div class="sect1">
1.1 dsieger 2559: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
2560: <a name="settings-for-creationg-of-binary-packages"></a>6.2. Settings for creation of binary packages</h2></div></div></div>
1.10 hubertf 2561: <p>See <a class="xref" href="#build.helpful-targets" title="17.17. Other helpful targets">Section 17.17, “Other helpful targets”</a>.</p>
1.6 rillig 2562: </div>
2563: </div>
1.41 asau 2564: <div class="chapter">
1.6 rillig 2565: <div class="titlepage"><div><div><h2 class="title">
2566: <a name="bulk"></a>Chapter 7. Creating binary packages for everything in pkgsrc (bulk
2567: builds)</h2></div></div></div>
2568: <div class="toc">
2569: <p><b>Table of Contents</b></p>
1.100 leot 2570: <dl class="toc">
1.71 wiz 2571: <dt><span class="sect1"><a href="#bulk.pre">7.1. Preparations</a></span></dt>
2572: <dt><span class="sect1"><a href="#bulk.pbulk">7.2. Running a pbulk-style bulk build</a></span></dt>
2573: <dd><dl><dt><span class="sect2"><a href="#bulk.pbulk.conf">7.2.1. Configuration</a></span></dt></dl></dd>
2574: <dt><span class="sect1"><a href="#bulk.req">7.3. Requirements of a full bulk build</a></span></dt>
1.66 asau 2575: <dt><span class="sect1"><a href="#creating-cdroms">7.4. Creating a multiple CD-ROM packages collection</a></span></dt>
2576: <dd><dl><dt><span class="sect2"><a href="#cdpack-example">7.4.1. Example of cdpack</a></span></dt></dl></dd>
1.6 rillig 2577: </dl>
2578: </div>
1.71 wiz 2579: <p>For a number of reasons you may want to build binary packages
2580: for a large selected set of packages in pkgsrc or even for all pkgsrc packages.
2581: For instance, when you have multiple machines that should run the same software,
2582: it is wasted time if they all build their packages themselves from source.
2583: Or you may want to build a list of packages you want and check them before
2584: deploying onto production system.
2585: There is a way of getting a set of binary packages:
1.66 asau 2586: The bulk build system, or pbulk ("p" stands for "parallel).
2587: This chapter describes how to set it up so that the packages
1.6 rillig 2588: are most likely to be usable later.</p>
1.41 asau 2589: <div class="sect1">
1.6 rillig 2590: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.71 wiz 2591: <a name="bulk.pre"></a>7.1. Preparations</h2></div></div></div>
2592: <p>First of all, you have to decide whether you build all packages
2593: or a limited set of them. Full bulk builds usually consume a lot more resources,
2594: both space and time, than builds for some practical sets of packages.
2595: There exists a number of particularly heavy packages that are not actually
2596: interesting to a wide audience.
2597:
2598: For a limited bulk builds you need to make a list of packages you want to build.
2599: Note, that all their dependencies will be built, so you don't need to track them manually.
2600: </p>
2601: <p>During bulk builds various packages are installed and deinstalled
2602: in <code class="filename">/usr/pkg</code> (or whatever <code class="filename">LOCALBASE</code> is),
2603: so make sure that you don't need any package during the builds.
2604: Essentially, you should provide fresh system, either a chroot environment
2605: or something even more restrictive, depending on what the operating system provides,
2606: or dedicate the whole physical machine.
2607: As a useful side effect this makes sure that bulk builds cannot
2608: break anything in your system. There have been numerous cases where
1.6 rillig 2609: certain packages tried to install files outside the
2610: <code class="filename">LOCALBASE</code> or wanted to edit some files in
1.71 wiz 2611: <code class="filename">/etc</code>.
2612: </p>
1.6 rillig 2613: </div>
1.41 asau 2614: <div class="sect1">
1.6 rillig 2615: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.71 wiz 2616: <a name="bulk.pbulk"></a>7.2. Running a pbulk-style bulk build</h2></div></div></div>
1.15 rillig 2617: <p>Running a pbulk-style bulk build works roughly as follows:</p>
1.41 asau 2618: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2619: <li class="listitem"><p>First, build the pbulk infrastructure in a fresh pkgsrc location.</p></li>
2620: <li class="listitem"><p>Then, build each of the packages from a clean installation directory using the infrastructure.</p></li>
1.15 rillig 2621: </ul></div>
1.41 asau 2622: <div class="sect2">
1.15 rillig 2623: <div class="titlepage"><div><div><h3 class="title">
1.71 wiz 2624: <a name="bulk.pbulk.conf"></a>7.2.1. Configuration</h3></div></div></div>
1.68 asau 2625: <p>To simplify configuration we provide helper script <code class="filename">mk/pbulk/pbulk.sh</code>.</p>
2626: <p>In order to use it, prepare a clear system (real one, chroot environment, jail, zone, virtual machine).
2627: Configure network access to fetch distribution files.
2628: Create user with name "pbulk".</p>
2629: <p>Fetch and extract pkgsrc. Use a command like one of these:</p>
2630: <pre class="screen">
1.72 wiz 2631: <code class="prompt">#</code> <strong class="userinput"><code>(cd /usr && ftp -o - http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)</code></strong>
2632: <code class="prompt">#</code> <strong class="userinput"><code>(cd /usr && fetch -o - http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)</code></strong>
2633: <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 2634: </pre>
2635: <p>Or any other way that fits (e.g., curl, wget).</p>
2636: <p>Deploy and configure pbulk tools, e.g.:</p>
2637: <pre class="screen">
2638: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -n # native (NetBSD)</code></strong>
2639: <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>
2640: <code class="prompt">#</code> <strong class="userinput"><code>sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build</code></strong>
2641: </pre>
2642: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2643: <h3 class="title">Note</h3>
2644: <p><code class="filename">mk.conf.frag</code> is a fragment of
2645: <code class="filename">mk.conf</code> that contains settings you want to
2646: apply to packages you build. For instance,</p>
2647: <pre class="programlisting">
2648: PKG_DEVELOPER= yes # perform more checks
2649: X11_TYPE= modular # use pkgsrc X11
2650: SKIP_LICENSE_CHECK= yes # accept all licences (useful when building all packages)
2651: </pre>
2652: </div>
2653: <p>If configured for limited list, replace the list in <code class="filename">/usr/pbulk/etc/pbulk.list</code>
2654: with your list of packages one per line without empty lines or comments. E.g.:</p>
2655: <pre class="programlisting">
2656: www/firefox
2657: mail/thunderbird
2658: misc/libreoffice4
2659: </pre>
1.69 asau 2660: <p>At this point you can also review configuration in <code class="filename">/usr/pbulk/etc</code>
2661: and make final amendments, if wanted.</p>
1.68 asau 2662: <p>Start it:</p>
2663: <pre class="screen">
2664: <code class="prompt">#</code> <strong class="userinput"><code>/usr/pbulk/bin/bulkbuild</code></strong>
2665: </pre>
2666: <p>After it finishes, you'll have <code class="filename">/mnt</code> filled with distribution files, binary packages, and reports,
2667: plain text summary in <code class="filename">/mnt/bulklog/meta/report.txt</code>
2668: </p>
2669: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2670: <h3 class="title">Note</h3>
2671: <p>The <code class="filename">pbulk.sh</code> script does not cover all possible use cases.
2672: While being ready to run, it serves as a good starting point to understand and build more complex setups.
2673: The script is kept small enough for better understanding.</p>
2674: </div>
2675: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2676: <h3 class="title">Note</h3>
2677: <p>The <code class="filename">pbulk.sh</code> script supports running
2678: unprivileged bulk build and helps configuring distributed bulk builds.</p>
2679: </div>
1.6 rillig 2680: </div>
2681: </div>
1.41 asau 2682: <div class="sect1">
1.6 rillig 2683: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.71 wiz 2684: <a name="bulk.req"></a>7.3. Requirements of a full bulk build</h2></div></div></div>
2685: <p>A complete bulk build requires lots of disk space. Some of the
2686: disk space can be read-only, some other must be writable. Some can be on
2687: remote filesystems (such as NFS) and some should be local. Some can be
2688: temporary filesystems, others must survive a sudden reboot.</p>
2689: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
2690: <li class="listitem"><p>40 GB for the distfiles (read-write, remote, temporary)</p></li>
2691: <li class="listitem"><p>30 GB for the binary packages (read-write, remote, permanent)</p></li>
2692: <li class="listitem"><p>1 GB for the pkgsrc tree (read-only, remote, permanent)</p></li>
2693: <li class="listitem"><p>5 GB for <code class="filename">LOCALBASE</code> (read-write, local, temporary)</p></li>
2694: <li class="listitem"><p>10 GB for the log files (read-write, remote, permanent)</p></li>
2695: <li class="listitem"><p>5 GB for temporary files (read-write, local, temporary)</p></li>
2696: </ul></div>
2697: </div>
2698: <div class="sect1">
2699: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.66 asau 2700: <a name="creating-cdroms"></a>7.4. Creating a multiple CD-ROM packages collection</h2></div></div></div>
1.1 dsieger 2701: <p>After your pkgsrc bulk-build has completed, you may wish to
2702: create a CD-ROM set of the resulting binary packages to assist
2703: in installing packages on other machines. The
1.79 snj 2704: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/cdpack/README.html" target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides
1.1 dsieger 2705: a simple tool for creating the ISO 9660 images.
1.10 hubertf 2706: <span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a
1.1 dsieger 2707: way that keeps all the dependencies for a given package on the same
2708: CD as that package.</p>
1.41 asau 2709: <div class="sect2">
1.1 dsieger 2710: <div class="titlepage"><div><div><h3 class="title">
1.66 asau 2711: <a name="cdpack-example"></a>7.4.1. Example of cdpack</h3></div></div></div>
1.1 dsieger 2712: <p>Complete documentation for cdpack is found in the cdpack(1)
2713: man page. The following short example assumes that the binary
2714: packages are left in
2715: <code class="filename">/usr/pkgsrc/packages/All</code> and that
2716: sufficient disk space exists in <code class="filename">/u2</code> to
2717: hold the ISO 9660 images.</p>
2718: <pre class="screen">
2719: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /u2/images</code></strong>
2720: <code class="prompt">#</code> <strong class="userinput"><code>pkg_add /usr/pkgsrc/packages/All/cdpack</code></strong>
2721: <code class="prompt">#</code> <strong class="userinput"><code>cdpack /usr/pkgsrc/packages/All /u2/images</code></strong>
2722: </pre>
2723: <p>If you wish to include a common set of files
2724: (<code class="filename">COPYRIGHT</code>, <code class="filename">README</code>,
2725: etc.) on each CD in the collection, then you need to create a
2726: directory which contains these files. e.g.</p>
2727: <pre class="screen">
2728: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common</code></strong>
2729: <code class="prompt">#</code> <strong class="userinput"><code>echo "This is a README" > /tmp/common/README</code></strong>
2730: <code class="prompt">#</code> <strong class="userinput"><code>echo "Another file" > /tmp/common/COPYING</code></strong>
2731: <code class="prompt">#</code> <strong class="userinput"><code>mkdir /tmp/common/bin</code></strong>
2732: <code class="prompt">#</code> <strong class="userinput"><code>echo "#!/bin/sh" > /tmp/common/bin/myscript</code></strong>
2733: <code class="prompt">#</code> <strong class="userinput"><code>echo "echo Hello world" >> /tmp/common/bin/myscript</code></strong>
2734: <code class="prompt">#</code> <strong class="userinput"><code>chmod 755 /tmp/common/bin/myscript</code></strong>
2735: </pre>
2736: <p>Now create the images:</p>
2737: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images</code></strong></pre>
2738: <p>Each image will contain <code class="filename">README</code>,
2739: <code class="filename">COPYING</code>, and <code class="filename">bin/myscript</code>
2740: in their root directories.</p>
2741: </div>
2742: </div>
2743: </div>
1.41 asau 2744: <div class="chapter">
1.1 dsieger 2745: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 2746: <a name="files"></a>Chapter 8. Directory layout of the installed files</h2></div></div></div>
1.1 dsieger 2747: <div class="toc">
2748: <p><b>Table of Contents</b></p>
1.100 leot 2749: <dl class="toc">
1.23 wiz 2750: <dt><span class="sect1"><a href="#files.localbase">8.1. File system layout in <code class="literal">${LOCALBASE}</code></a></span></dt>
2751: <dt><span class="sect1"><a href="#files.varbase">8.2. File system layout in <code class="literal">${VARBASE}</code></a></span></dt>
1.1 dsieger 2752: </dl>
2753: </div>
2754: <p>The files that are installed by pkgsrc are organized in a way that
2755: is similar to what you find in the <code class="filename">/usr</code> directory
2756: of the base system. But some details are different. This is because
2757: pkgsrc initially came from FreeBSD and had adopted its file system
2758: hierarchy. Later it was largely influenced by NetBSD. But no matter
2759: which operating system you are using pkgsrc with, you can expect the
2760: same layout for pkgsrc.</p>
2761: <p>There are mainly four root directories for pkgsrc, which are all
2762: configurable in the <code class="filename">bootstrap/bootstrap</code> script.
2763: When pkgsrc has been installed as root, the default locations
2764: are:</p>
2765: <pre class="programlisting">
2766: LOCALBASE= /usr/pkg
2767: PKG_SYSCONFBASE= /usr/pkg/etc
2768: VARBASE= /var
2769: PKG_DBDIR= /var/db/pkg
2770: </pre>
2771: <p>In unprivileged mode (when pkgsrc has been installed as any other
2772: user), the default locations are:</p>
2773: <pre class="programlisting">
2774: LOCALBASE= ${HOME}/pkg
2775: PKG_SYSCONFBASE= ${HOME}/pkg/etc
2776: VARBASE= ${HOME}/pkg/var
2777: PKG_DBDIR= ${HOME}/pkg/var/db/pkg
2778: </pre>
2779: <p>What these four directories are for, and what they look like is
2780: explained below.</p>
1.41 asau 2781: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2782: <li class="listitem"><p><code class="varname">LOCALBASE</code> corresponds to the
1.1 dsieger 2783: <code class="filename">/usr</code> directory in the base system. It is the
1.23 wiz 2784: <span class="quote">“<span class="quote">main</span>”</span> directory where the files are installed and contains
1.1 dsieger 2785: the well-known subdirectories like <code class="filename">bin</code>,
2786: <code class="filename">include</code>, <code class="filename">lib</code>,
2787: <code class="filename">share</code> and
2788: <code class="filename">sbin</code>.</p></li>
1.23 wiz 2789: <li class="listitem"><p><code class="varname">VARBASE</code> corresponds to
1.1 dsieger 2790: <code class="filename">/var</code> in the base system. Some programs (especially
2791: games, network daemons) need write access to it during normal
2792: operation.</p></li>
1.23 wiz 2793: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR</code> corresponds to
1.1 dsieger 2794: <code class="filename">/etc</code> in the base system. It contains configuration
1.10 hubertf 2795: 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 2796: itself.</p></li>
2797: </ul></div>
1.41 asau 2798: <div class="sect1">
1.1 dsieger 2799: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 2800: <a name="files.localbase"></a>8.1. File system layout in <code class="literal">${LOCALBASE}</code>
1.1 dsieger 2801: </h2></div></div></div>
2802: <p>The following directories exist in a typical pkgsrc installation
2803: in <code class="filename">${LOCALBASE}</code>.</p>
1.41 asau 2804: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2805: <dt><span class="term"><code class="filename">bin</code></span></dt>
2806: <dd><p>Contains executable programs that are intended to be
2807: directly used by the end user.</p></dd>
2808: <dt><span class="term"><code class="filename">emul</code></span></dt>
2809: <dd><p>Contains files for the emulation layers of various other
2810: operating systems, especially for
2811: NetBSD.</p></dd>
2812: <dt><span class="term"><code class="filename">etc</code> (the usual location of
2813: <code class="filename">${PKG_SYSCONFDIR}</code>)</span></dt>
2814: <dd><p>Contains
2815: the configuration files.</p></dd>
2816: <dt><span class="term"><code class="filename">include</code></span></dt>
2817: <dd><p>Contains headers for the C and C++ programming
2818: languages.</p></dd>
2819: <dt><span class="term"><code class="filename">info</code></span></dt>
2820: <dd><p>Contains GNU info files of various
2821: packages.</p></dd>
2822: <dt><span class="term"><code class="filename">lib</code></span></dt>
2823: <dd><p>Contains shared and static
2824: libraries.</p></dd>
2825: <dt><span class="term"><code class="filename">libdata</code></span></dt>
2826: <dd><p>Contains data files that don't change after
2827: installation. Other data files belong into
2828: <code class="filename">${VARBASE}</code>.</p></dd>
2829: <dt><span class="term"><code class="filename">libexec</code></span></dt>
2830: <dd><p>Contains programs that are not intended to be used by
2831: end users, such as helper programs or network
2832: daemons.</p></dd>
2833: <dt><span class="term"><code class="filename">libexec/cgi-bin</code></span></dt>
2834: <dd><p>Contains programs that are intended to be executed as
2835: CGI scripts by a web server.</p></dd>
2836: <dt><span class="term"><code class="filename">man</code> (the usual value of
2837: <code class="filename">${PKGMANDIR}</code>)</span></dt>
2838: <dd><p>Contains brief
2839: documentation in form of manual pages.</p></dd>
2840: <dt><span class="term"><code class="filename">sbin</code></span></dt>
2841: <dd><p>Contains programs that are intended to be used only by
2842: the super-user.</p></dd>
2843: <dt><span class="term"><code class="filename">share</code></span></dt>
2844: <dd><p>Contains platform-independent data files that don't
2845: change after installation.</p></dd>
2846: <dt><span class="term"><code class="filename">share/doc</code></span></dt>
2847: <dd><p>Contains documentation files provided by the
2848: packages.</p></dd>
2849: <dt><span class="term"><code class="filename">share/examples</code></span></dt>
2850: <dd><p>Contains example files provided by the packages. Among
2851: others, the original configuration files are saved here and copied to
2852: <code class="filename">${PKG_SYSCONFDIR}</code> during
2853: installation.</p></dd>
2854: <dt><span class="term"><code class="filename">share/examples/rc.d</code></span></dt>
2855: <dd><p>Contains the original files for rc.d
2856: scripts.</p></dd>
2857: <dt><span class="term"><code class="filename">var</code> (the usual location of
2858: <code class="filename">${VARBASE}</code>)</span></dt>
2859: <dd><p>Contains files
2860: that may be modified after
2861: installation.</p></dd>
2862: </dl></div>
2863: </div>
1.41 asau 2864: <div class="sect1">
1.1 dsieger 2865: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 2866: <a name="files.varbase"></a>8.2. File system layout in <code class="literal">${VARBASE}</code>
1.1 dsieger 2867: </h2></div></div></div>
1.41 asau 2868: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 2869: <dt><span class="term"><code class="filename">db/pkg</code> (the usual location of
2870: <code class="filename">${PKG_DBDIR}</code>)</span></dt>
2871: <dd><p>Contains
2872: information about the currently installed
2873: packages.</p></dd>
2874: <dt><span class="term"><code class="filename">games</code></span></dt>
2875: <dd><p>Contains highscore
2876: files.</p></dd>
2877: <dt><span class="term"><code class="filename">log</code></span></dt>
2878: <dd><p>Contains log files.</p></dd>
2879: <dt><span class="term"><code class="filename">run</code></span></dt>
2880: <dd><p>Contains informational files about daemons that are
2881: currently running.</p></dd>
2882: </dl></div>
2883: </div>
2884: </div>
1.41 asau 2885: <div class="chapter">
1.1 dsieger 2886: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 2887: <a name="faq"></a>Chapter 9. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 2888: <div class="toc">
2889: <p><b>Table of Contents</b></p>
1.100 leot 2890: <dl class="toc">
1.6 rillig 2891: <dt><span class="sect1"><a href="#mailing-list-pointers">9.1. Are there any mailing lists for pkg-related discussion?</a></span></dt>
1.84 wiz 2892: <dt><span class="sect1"><a href="#faq-pkgtools">9.2. Utilities for package management (pkgtools)</a></span></dt>
2893: <dt><span class="sect1"><a href="#non-root-pkgsrc">9.3. How to use pkgsrc as non-root</a></span></dt>
2894: <dt><span class="sect1"><a href="#resume-transfers">9.4. How to resume transfers when fetching distfiles?</a></span></dt>
2895: <dt><span class="sect1"><a href="#x.org-from-pkgsrc">9.5. How can I install/use modular X.org from pkgsrc?</a></span></dt>
2896: <dt><span class="sect1"><a href="#fetch-behind-firewall">9.6. How to fetch files from behind a firewall</a></span></dt>
2897: <dt><span class="sect1"><a href="#fetch-https">9.7. How to fetch files from HTTPS sites</a></span></dt>
2898: <dt><span class="sect1"><a href="#passive-ftp">9.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</a></span></dt>
2899: <dt><span class="sect1"><a href="#fetching-all-distfiles">9.9. How to fetch all distfiles at once</a></span></dt>
2900: <dt><span class="sect1"><a href="#tmac.andoc-missing">9.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 2901: /usr/share/tmac/tmac.andoc</span>”</span> mean?</a></span></dt>
1.84 wiz 2902: <dt><span class="sect1"><a href="#bsd.own.mk-missing">9.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</a></span></dt>
2903: <dt><span class="sect1"><a href="#using-sudo-with-pkgsrc">9.12. Using 'sudo' with pkgsrc</a></span></dt>
2904: <dt><span class="sect1"><a href="#faq.conf">9.13. How do I change the location of configuration files?</a></span></dt>
2905: <dt><span class="sect1"><a href="#audit-packages">9.14. Automated security checks</a></span></dt>
2906: <dt><span class="sect1"><a href="#ufaq-cflags">9.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</a></span></dt>
2907: <dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build. What shall I do?</a></span></dt>
2908: <dt><span class="sect1"><a href="#faq.rcs-conflicts">9.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 2909: </dl>
2910: </div>
2911: <p>This section contains hints, tips & tricks on special things in
2912: pkgsrc that we didn't find a better place for in the previous chapters, and
2913: it contains items for both pkgsrc users and developers.</p>
1.41 asau 2914: <div class="sect1">
1.1 dsieger 2915: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 2916: <a name="mailing-list-pointers"></a>9.1. Are there any mailing lists for pkg-related discussion?</h2></div></div></div>
1.1 dsieger 2917: <p>The following mailing lists may be of interest to pkgsrc users:</p>
1.41 asau 2918: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 2919: <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 2920: This is a general purpose list for most issues regarding
2921: pkgsrc, regardless of platform, e.g. soliciting user help
2922: for pkgsrc configuration, unexpected build failures, using
2923: particular packages, upgrading pkgsrc installations,
2924: questions regarding the pkgsrc release branches, etc. General announcements or
2925: proposals for changes that impact the pkgsrc user community,
2926: e.g. major infrastructure changes, new features, package
2927: removals, etc., may also be posted.</p></li>
1.23 wiz 2928: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bulk" target="_top">pkgsrc-bulk</a>:
1.1 dsieger 2929: A list where the results of pkgsrc bulk builds are sent and
2930: discussed.</p></li>
1.23 wiz 2931: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-changes" target="_top">pkgsrc-changes</a>:
1.1 dsieger 2932: This list is for those who are interested in getting a
2933: commit message for every change committed to pkgsrc. It is
2934: also available in digest form, meaning one daily message
2935: containing all commit messages for changes to the package
2936: source tree in that 24 hour period.</p></li>
2937: </ul></div>
2938: <p>To subscribe, do:</p>
2939: <pre class="programlisting">
2940: <code class="prompt">%</code> echo subscribe <em class="replaceable"><code>listname</code></em> | mail majordomo@NetBSD.org
2941: </pre>
2942: <p>Archives for all these mailing lists are available from
1.10 hubertf 2943: <a class="ulink" href="http://mail-index.NetBSD.org/" target="_top">http://mail-index.NetBSD.org/</a>.</p>
1.1 dsieger 2944: </div>
1.41 asau 2945: <div class="sect1">
1.1 dsieger 2946: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 2947: <a name="faq-pkgtools"></a>9.2. Utilities for package management (pkgtools)</h2></div></div></div>
1.1 dsieger 2948: <p>The directory <code class="filename">pkgsrc/pkgtools</code> contains
2949: a number of useful utilities for both users and developers of pkgsrc. This
2950: section attempts only to make the reader aware of the utilities and when
2951: they might be useful, and not to duplicate the documentation that comes
2952: with each package.</p>
2953: <p>Utilities used by pkgsrc (automatically installed when needed):</p>
1.79 snj 2954: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/README.html" target="_top"><code class="filename">pkgtools/x11-links</code></a>:
1.1 dsieger 2955: Symlinks for use by buildlink.</p></li></ul></div>
2956: <p>OS tool augmentation (automatically installed when needed):</p>
1.41 asau 2957: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 2958: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/digest/README.html" target="_top"><code class="filename">pkgtools/digest</code></a>:
1.1 dsieger 2959: Calculates various kinds of checksums (including SHA1).</p></li>
1.79 snj 2960: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libnbcompat/README.html" target="_top"><code class="filename">pkgtools/libnbcompat</code></a>:
1.1 dsieger 2961: Compatibility library for pkgsrc tools.</p></li>
1.79 snj 2962: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/README.html" target="_top"><code class="filename">pkgtools/mtree</code></a>: Installed on
1.1 dsieger 2963: non-BSD systems due to lack of native mtree.</p></li>
1.79 snj 2964: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a>:
1.1 dsieger 2965: Up-to-date replacement for
2966: <code class="filename">/usr/sbin/pkg_install</code>, or for use on operating
2967: systems where pkg_install is not present.</p></li>
2968: </ul></div>
2969: <p>Utilities used by pkgsrc (not automatically installed):</p>
1.41 asau 2970: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 2971: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html" target="_top"><code class="filename">pkgtools/pkg_tarup</code></a>:
1.1 dsieger 2972: Create a binary package from an
1.10 hubertf 2973: already-installed package. Used by <span class="command"><strong>make replace</strong></span> to
1.1 dsieger 2974: save the old package.</p></li>
1.79 snj 2975: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/dfdisk/README.html" target="_top"><code class="filename">pkgtools/dfdisk</code></a>:
1.1 dsieger 2976: Adds extra functionality to pkgsrc, allowing it to fetch distfiles
2977: from multiple locations. It currently supports the following
2978: methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li>
1.79 snj 2979: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html" target="_top"><code class="filename">devel/cpuflags</code></a>: Determine
1.16 jnemeth 2980: the best compiler flags to optimise code for your current
1.23 wiz 2981: CPU and compiler. </p></li>
1.1 dsieger 2982: </ul></div>
2983: <p>Utilities for keeping track of installed packages, being up to date,
2984: etc:</p>
1.41 asau 2985: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 2986: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgin/README.html" target="_top"><code class="filename">pkgtools/pkgin</code></a>: A package
1.65 wiz 2987: update tool similar to apt(1). Download, install, and upgrade
2988: binary packages easily.</p></li>
1.79 snj 2989: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a>: Reports on
1.1 dsieger 2990: packages whose installed versions do not match the latest pkgsrc
2991: entries.</p></li>
1.79 snj 2992: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a>: Makes
1.1 dsieger 2993: dependency graphs of packages, to aid in choosing a strategy for
2994: updating.</p></li>
1.79 snj 2995: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdepgraph/README.html" target="_top"><code class="filename">pkgtools/pkgdepgraph</code></a>: Makes
2996: graphs from the output of <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html" target="_top"><code class="filename">pkgtools/pkgdep</code></a> (uses graphviz).</p></li>
2997: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>: The
1.12 weinem 2998: pkglint(1) program checks a pkgsrc entry for errors.</p></li>
1.79 snj 2999: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html" target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a>: The lintpkgsrc(1) program
1.1 dsieger 3000: does various checks on the complete pkgsrc system.</p></li>
1.79 snj 3001: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgsurvey/README.html" target="_top"><code class="filename">pkgtools/pkgsurvey</code></a>: Report what
1.1 dsieger 3002: packages you have installed.</p></li>
3003: </ul></div>
3004: <p>Utilities for people maintaining or creating individual packages:</p>
1.41 asau 3005: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 3006: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a>: Automate
1.1 dsieger 3007: making and maintaining patches for a package (includes pkgdiff,
3008: pkgvi, mkpatches, etc.).</p></li>
1.79 snj 3009: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>: Aids in
1.1 dsieger 3010: converting to pkgsrc.</p></li>
3011: </ul></div>
3012: <p>Utilities for people maintaining pkgsrc (or: more obscure pkg
3013: utilities)</p>
1.41 asau 3014: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 3015: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_comp/README.html" target="_top"><code class="filename">pkgtools/pkg_comp</code></a>: Build
1.1 dsieger 3016: packages in a chrooted area.</p></li>
1.79 snj 3017: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libkver/README.html" target="_top"><code class="filename">pkgtools/libkver</code></a>: Spoof
1.1 dsieger 3018: kernel version for chrooted cross builds.</p></li>
3019: </ul></div>
3020: </div>
1.41 asau 3021: <div class="sect1">
1.1 dsieger 3022: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3023: <a name="non-root-pkgsrc"></a>9.3. How to use pkgsrc as non-root</h2></div></div></div>
1.1 dsieger 3024: <p>If you want to use pkgsrc as non-root user, you can set some
3025: variables to make pkgsrc work under these conditions. At the very least,
1.23 wiz 3026: you need to set <code class="varname">UNPRIVILEGED</code> to <span class="quote">“<span class="quote">yes</span>”</span>; this
1.1 dsieger 3027: will turn on unprivileged mode and set multiple related variables to allow
3028: installation of packages as non-root.</p>
3029: <p>In case the defaults are not enough, you may want to tune some other
3030: variables used. For example, if the automatic user/group detection leads
3031: to incorrect values (or not the ones you would like to use), you can change
3032: them by setting <code class="varname">UNPRIVILEGED_USER</code> and
3033: <code class="varname">UNPRIVILEGED_GROUP</code> respectively.</p>
3034: <p>As regards bootstrapping, please note that the
1.10 hubertf 3035: <span class="command"><strong>bootstrap</strong></span> script will ease non-root configuration when
1.23 wiz 3036: given the <span class="quote">“<span class="quote">--ignore-user-check</span>”</span> flag, as it will choose and
1.1 dsieger 3037: use multiple default directories under <code class="filename">~/pkg</code> as the
3038: installation targets. These directories can be overridden by the
1.23 wiz 3039: <span class="quote">“<span class="quote">--prefix</span>”</span> flag provided by the script, as well as some others
1.1 dsieger 3040: that allow finer tuning of the tree layout.</p>
3041: </div>
1.41 asau 3042: <div class="sect1">
1.1 dsieger 3043: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3044: <a name="resume-transfers"></a>9.4. How to resume transfers when fetching distfiles?</h2></div></div></div>
1.1 dsieger 3045: <p>By default, resuming transfers in pkgsrc is disabled, but you can
3046: enable this feature by adding the option
3047: <code class="varname">PKG_RESUME_TRANSFERS=YES</code> into
1.10 hubertf 3048: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. If, during a fetch step, an incomplete
1.1 dsieger 3049: distfile is found, pkgsrc will try to resume it.</p>
3050: <p>You can also
1.61 wiz 3051: use a different program than the platform default program by changing the
1.16 jnemeth 3052: <code class="varname">FETCH_USING</code> variable. You can specify the program by
3053: using of ftp, fetch, wget or curl. Alternatively, fetching can be disabled
3054: by using the value manual. A value of custom disables the system defaults
3055: and dependency tracking for the fetch program. In that case you have to
3056: provide <code class="varname">FETCH_CMD</code>, <code class="varname">FETCH_BEFORE_ARGS</code>,
3057: <code class="varname">FETCH_RESUME_ARGS</code>, <code class="varname">FETCH_OUTPUT_ARGS</code>,
3058: <code class="varname">FETCH_AFTER_ARGS</code>.</p>
1.1 dsieger 3059: <p>For example, if you want to use
1.16 jnemeth 3060: <code class="filename">wget</code> to download, you'll have to use something
1.1 dsieger 3061: like:</p>
3062: <pre class="programlisting">
1.16 jnemeth 3063: FETCH_USING= wget
1.1 dsieger 3064: </pre>
3065: </div>
1.41 asau 3066: <div class="sect1">
1.1 dsieger 3067: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3068: <a name="x.org-from-pkgsrc"></a>9.5. How can I install/use modular X.org from pkgsrc?</h2></div></div></div>
1.4 rillig 3069: <p>If you want to use modular X.org from pkgsrc instead of your system's own X11
1.1 dsieger 3070: (<code class="filename">/usr/X11R6</code>, <code class="filename">/usr/openwin</code>, ...)
3071: you will have to add the following line into
1.10 hubertf 3072: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 3073: <pre class="programlisting">
1.4 rillig 3074: X11_TYPE=modular
1.1 dsieger 3075: </pre>
1.41 asau 3076: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 3077: <h3 class="title">Note</h3>
1.4 rillig 3078: <p>The DragonFly operating system defaults to using modular X.org from pkgsrc.
3079: </p>
1.1 dsieger 3080: </div>
3081: </div>
1.41 asau 3082: <div class="sect1">
1.1 dsieger 3083: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3084: <a name="fetch-behind-firewall"></a>9.6. How to fetch files from behind a firewall</h2></div></div></div>
1.1 dsieger 3085: <p>If you are sitting behind a firewall which does not allow direct
3086: connections to Internet hosts (i.e. non-NAT), you may specify the
3087: relevant proxy hosts. This is done using an environment variable in the
3088: form of a URL, e.g. in Amdahl, the machine
1.23 wiz 3089: <span class="quote">“<span class="quote">orpheus.amdahl.com</span>”</span> is one of the firewalls, and it uses
1.1 dsieger 3090: port 80 as the proxy port number. So the proxy environment variables
3091: are:</p>
3092: <pre class="programlisting">
3093: ftp_proxy=ftp://orpheus.amdahl.com:80/
3094: http_proxy=http://orpheus.amdahl.com:80/
3095: </pre>
3096: </div>
1.41 asau 3097: <div class="sect1">
1.1 dsieger 3098: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3099: <a name="fetch-https"></a>9.7. How to fetch files from HTTPS sites</h2></div></div></div>
1.65 wiz 3100: <p>Some fetch tools are not prepared to support HTTPS by default
3101: (for example, the one in NetBSD 6.0), or the one installed by the
3102: pkgsrc bootstrap (to avoid an openssl dependency that low in the
3103: dependency graph).</p>
3104: <p>Usually you won't notice, because distribution files are
3105: mirrored weekly to <span class="quote">“<span class="quote">ftp.NetBSD.org</span>”</span>, but that might not
3106: be often enough if you are following pkgsrc-current. In that case, set
3107: <code class="varname">FETCH_USING</code> in your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file to
3108: <span class="quote">“<span class="quote">curl</span>”</span> or <span class="quote">“<span class="quote">wget</span>”</span>, which are both compiled
3109: with HTTPS support by default. Of course, these tools need to be
3110: installed before you can use them this way.</p>
3111: </div>
3112: <div class="sect1">
3113: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3114: <a name="passive-ftp"></a>9.8. How do I tell <span class="command"><strong>make fetch</strong></span> to do passive FTP?</h2></div></div></div>
1.1 dsieger 3115: <p>This depends on which utility is used to retrieve distfiles. From
3116: <code class="filename">bsd.pkg.mk</code>, <code class="varname">FETCH_CMD</code> is assigned
3117: the first available command from the following list:</p>
1.41 asau 3118: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 3119: <li class="listitem"><p><code class="filename">${LOCALBASE}/bin/ftp</code></p></li>
3120: <li class="listitem"><p><code class="filename">/usr/bin/ftp</code></p></li>
1.1 dsieger 3121: </ul></div>
3122: <p>On a default NetBSD installation, this will be
3123: <code class="filename">/usr/bin/ftp</code>, which automatically tries passive
3124: connections first, and falls back to active connections if the server
3125: refuses to do passive. For the other tools, add the following to your
1.10 hubertf 3126: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> file:
1.1 dsieger 3127: <code class="varname">PASSIVE_FETCH=1</code>.</p>
3128: <p>Having that option present will prevent
3129: <code class="filename">/usr/bin/ftp</code> from falling back to active
3130: transfers.</p>
3131: </div>
1.41 asau 3132: <div class="sect1">
1.1 dsieger 3133: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3134: <a name="fetching-all-distfiles"></a>9.9. How to fetch all distfiles at once</h2></div></div></div>
1.1 dsieger 3135: <p>You would like to download all the distfiles in a single batch
1.10 hubertf 3136: from work or university, where you can't run a <span class="command"><strong>make
1.25 spz 3137: 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 3138: but downloading the entire directory may not be appropriate.</p>
1.10 hubertf 3139: <p>The answer here is to do a <span class="command"><strong>make fetch-list</strong></span> in
1.1 dsieger 3140: <code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the
3141: resulting list to your machine at work/school and use it there. If you
1.79 snj 3142: don't have a NetBSD-compatible <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
1.1 dsieger 3143: forget to set <code class="varname">FETCH_CMD</code> to something that fetches a
3144: URL:</p>
3145: <p>At home:</p>
3146: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
3147: <code class="prompt">%</code> <strong class="userinput"><code>make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh</code></strong>
3148: <code class="prompt">%</code> <strong class="userinput"><code>scp /tmp/fetch.sh work:/tmp</code></strong></pre>
3149: <p>At work:</p>
3150: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>sh /tmp/fetch.sh</code></strong></pre>
3151: <p>then tar up <code class="filename">/tmp/distfiles</code> and take it
3152: home.</p>
3153: <p>If you have a machine running NetBSD, and you want to get
3154: <span class="emphasis"><em>all</em></span> distfiles (even ones that aren't for your
3155: machine architecture), you can do so by using the above-mentioned
1.10 hubertf 3156: <span class="command"><strong>make fetch-list</strong></span> approach, or fetch the distfiles
1.1 dsieger 3157: directly by running:</p>
3158: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make mirror-distfiles</code></strong></pre>
3159: <p>If you even decide to ignore
3160: <code class="varname">NO_{SRC,BIN}_ON_{FTP,CDROM}</code>, then you can get everything
3161: by running:</p>
3162: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make fetch NO_SKIP=yes</code></strong></pre>
3163: </div>
1.41 asau 3164: <div class="sect1">
1.1 dsieger 3165: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3166: <a name="tmac.andoc-missing"></a>9.10. What does <span class="quote">“<span class="quote">Don't know how to make
1.23 wiz 3167: /usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div>
1.79 snj 3168: <p>When compiling the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a>
1.1 dsieger 3169: package, you get the error from make that it doesn't know how to make
3170: <code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that
1.23 wiz 3171: you don't have installed the <span class="quote">“<span class="quote">text</span>”</span> set (nroff, ...) from
1.1 dsieger 3172: the NetBSD base distribution on your machine. It is recommended to do
3173: that to format man pages.</p>
1.79 snj 3174: <p>In the case of the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you
1.1 dsieger 3175: can get away with setting <code class="varname">NOMAN=YES</code> either in the
1.10 hubertf 3176: environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 3177: </div>
1.41 asau 3178: <div class="sect1">
1.1 dsieger 3179: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3180: <a name="bsd.own.mk-missing"></a>9.11. What does <span class="quote">“<span class="quote">Could not find bsd.own.mk</span>”</span> mean?</h2></div></div></div>
1.1 dsieger 3181: <p>You didn't install the compiler set, <code class="filename">comp.tgz</code>,
3182: when you installed your NetBSD machine. Please get and install it, by
3183: extracting it in <code class="filename">/</code>:</p>
3184: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong>
3185: <code class="prompt">#</code> <strong class="userinput"><code>tar --unlink -zxvpf .../comp.tgz</code></strong></pre>
3186: <p><code class="filename">comp.tgz</code> is part of every NetBSD release. Get
1.10 hubertf 3187: the one that corresponds to your release (determine via <span class="command"><strong>uname
1.1 dsieger 3188: -r</strong></span>).</p>
3189: </div>
1.41 asau 3190: <div class="sect1">
1.1 dsieger 3191: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3192: <a name="using-sudo-with-pkgsrc"></a>9.12. Using 'sudo' with pkgsrc</h2></div></div></div>
1.1 dsieger 3193: <p>When installing packages as non-root user and using the just-in-time
1.79 snj 3194: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1+NetBSD-5.0.1+i386"><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 3195: password for each required package installed. To avoid this, the sudo
3196: package can be used, which does password caching over a limited time. To
3197: use it, install sudo (either as binary package or from
1.79 snj 3198: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/sudo/README.html" target="_top"><code class="filename">security/sudo</code></a>) and then put the
1.10 hubertf 3199: following into your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, somewhere
1.1 dsieger 3200: <span class="emphasis"><em>after</em></span> the definition of the
3201: <code class="varname">LOCALBASE</code> variable:</p>
3202: <pre class="programlisting">
3203: .if exists(${LOCALBASE}/bin/sudo)
3204: SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
3205: .endif
3206: </pre>
3207: </div>
1.41 asau 3208: <div class="sect1">
1.1 dsieger 3209: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3210: <a name="faq.conf"></a>9.13. How do I change the location of configuration files?</h2></div></div></div>
1.1 dsieger 3211: <p>As the system administrator, you can choose where configuration files
3212: are installed. The default settings make all these files go into
3213: <code class="filename">${PREFIX}/etc</code> or some of its subdirectories; this may
3214: be suboptimal depending on your expectations (e.g., a read-only,
3215: NFS-exported <code class="varname">PREFIX</code> with a need of per-machine
3216: configuration of the provided packages).</p>
3217: <p>In order to change the defaults, you can modify the
3218: <code class="varname">PKG_SYSCONFBASE</code> variable (in
1.10 hubertf 3219: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>) to point to your preferred configuration
1.1 dsieger 3220: directory; some common examples include <code class="filename">/etc</code> or
3221: <code class="filename">/etc/pkg</code>.</p>
3222: <p>Furthermore, you can change this value on a per-package basis by
3223: setting the <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> variable.
3224: <code class="varname">PKG_SYSCONFVAR</code>'s value usually matches the name of the
3225: package you would like to modify, that is, the contents of
3226: <code class="varname">PKGBASE</code>.</p>
3227: <p>Note that after changing these settings, you must rebuild and
3228: reinstall any affected packages.</p>
3229: </div>
1.41 asau 3230: <div class="sect1">
1.1 dsieger 3231: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3232: <a name="audit-packages"></a>9.14. Automated security checks</h2></div></div></div>
1.1 dsieger 3233: <p>Please be aware that there can often be bugs in third-party software,
3234: and some of these bugs can leave a machine vulnerable to exploitation by
3235: attackers. In an effort to lessen the exposure, the NetBSD packages team
3236: maintains a database of known-exploits to packages which have at one time
3237: been included in pkgsrc. The database can be downloaded automatically, and
3238: a security audit of all packages installed on a system can take place. To
1.14 jmcneill 3239: do this, refer to the following two tools (installed as part of the
1.79 snj 3240: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> package):</p>
1.23 wiz 3241: <div class="orderedlist"><ol class="orderedlist" type="1">
3242: <li class="listitem">
1.20 snj 3243: <p><span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>, an easy way to
1.1 dsieger 3244: download a list of the security vulnerabilities information. This list
1.25 spz 3245: is kept up to date by the pkgsrc security team, and is distributed
3246: from the NetBSD ftp server:</p>
3247: <p><a class="ulink" href="ftp://ftp.NetBSD.org/pkgsrc/distfiles/pkg-vulnerabilities" target="_top">ftp://ftp.NetBSD.org/pkgsrc/distfiles/pkg-vulnerabilities</a></p>
1.1 dsieger 3248: </li>
1.23 wiz 3249: <li class="listitem"><p><span class="command"><strong>pkg_admin audit</strong></span>, an easy way to audit the
3250: current machine, checking each known vulnerability. If a
1.1 dsieger 3251: vulnerable package is installed, it will be shown by output to stdout,
3252: including a description of the type of vulnerability, and a URL
3253: containing more information.</p></li>
3254: </ol></div>
1.14 jmcneill 3255: <p>Use of these tools is strongly recommended! After
1.23 wiz 3256: <span class="quote">“<span class="quote">pkg_install</span>”</span> is installed, please read
1.1 dsieger 3257: the package's message, which you can get by running <strong class="userinput"><code>pkg_info -D
1.14 jmcneill 3258: pkg_install</code></strong>.</p>
1.1 dsieger 3259: <p>If this package is installed, pkgsrc builds will use it to
1.10 hubertf 3260: perform a security check before building any package. See <a class="xref" href="#variables-affecting-build" title="5.2. Variables affecting the build process">Section 5.2, “Variables affecting the build process”</a> for ways to control this
1.1 dsieger 3261: check.</p>
3262: </div>
1.41 asau 3263: <div class="sect1">
1.1 dsieger 3264: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3265: <a name="ufaq-cflags"></a>9.15. Why do some packages ignore my <code class="varname">CFLAGS</code>?</h2></div></div></div>
1.1 dsieger 3266: <p>When you add your own preferences to the
3267: <code class="varname">CFLAGS</code> variable in your
1.10 hubertf 3268: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, these flags are passed in
1.1 dsieger 3269: environment variables to the <code class="filename">./configure</code>
1.79 snj 3270: scripts and to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>. Some package authors ignore the
1.1 dsieger 3271: <code class="varname">CFLAGS</code> from the environment variable by
3272: overriding them in the <code class="filename">Makefile</code>s of their
3273: package.</p>
3274: <p>Currently there is no solution to this problem. If you
3275: really need the package to use your <code class="varname">CFLAGS</code>
1.10 hubertf 3276: you should run <span class="command"><strong>make patch</strong></span> in the package
1.1 dsieger 3277: directory and then inspect any <code class="filename">Makefile</code> and
3278: <code class="filename">Makefile.in</code> for whether they define
3279: <code class="varname">CFLAGS</code> explicitly. Usually you can remove
1.23 wiz 3280: these lines. But be aware that some <span class="quote">“<span class="quote">smart</span>”</span>
1.1 dsieger 3281: programmers write so bad code that it only works for the
3282: specific combination of <code class="varname">CFLAGS</code> they have
3283: chosen.</p>
3284: </div>
1.41 asau 3285: <div class="sect1">
1.1 dsieger 3286: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3287: <a name="ufaq-fail"></a>9.16. A package does not build. What shall I do?</h2></div></div></div>
1.23 wiz 3288: <div class="procedure"><ol class="procedure" type="1">
1.41 asau 3289: <li class="step"><p>Make sure that your copy of pkgsrc is consistent. A
1.1 dsieger 3290: case that occurs often is that people only update pkgsrc in
3291: parts, because of performance reasons. Since pkgsrc is one large
3292: system, not a collection of many small systems, there are
3293: sometimes changes that only work when the whole pkgsrc tree is
3294: updated.</p></li>
1.41 asau 3295: <li class="step"><p>Make sure that you don't have any CVS conflicts.
1.23 wiz 3296: Search for <span class="quote">“<span class="quote"><<<<<<</span>”</span> or
3297: <span class="quote">“<span class="quote">>>>>>></span>”</span> in all your pkgsrc
1.1 dsieger 3298: files.</p></li>
1.41 asau 3299: <li class="step"><p>Make sure that you don't have old copies of the packages
1.10 hubertf 3300: extracted. Run <span class="command"><strong>make clean clean-depends</strong></span> to
1.1 dsieger 3301: verify this.</p></li>
1.41 asau 3302: <li class="step"><p>If the problem still exists, write a mail to the
1.1 dsieger 3303: <code class="literal">pkgsrc-users</code> mailing list.</p></li>
3304: </ol></div>
3305: </div>
1.41 asau 3306: <div class="sect1">
1.1 dsieger 3307: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.84 wiz 3308: <a name="faq.rcs-conflicts"></a>9.17. What does <span class="quote">“<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>”</span> mean?</h2></div></div></div>
1.1 dsieger 3309: <p>You have modified a file from pkgsrc, and someone else has
3310: modified that same file afterwards in the CVS repository. Both changes
3311: are in the same region of the file, so when you updated pkgsrc, the
3312: <code class="literal">cvs</code> command marked the conflicting changes in the
3313: file. Because of these markers, the file is no longer a valid
3314: <code class="filename">Makefile</code>.</p>
3315: <p>Have a look at that file, and if you don't need your local changes
1.10 hubertf 3316: anymore, you can remove that file and run <span class="command"><strong>cvs -q update
1.1 dsieger 3317: -dP</strong></span> in that directory to download the current version.</p>
3318: </div>
3319: </div>
3320: </div>
1.41 asau 3321: <div class="part">
1.1 dsieger 3322: <div class="titlepage"><div><div><h1 class="title">
3323: <a name="developers-guide"></a>Part II. The pkgsrc developer's guide</h1></div></div></div>
1.41 asau 3324: <div class="partintro">
1.1 dsieger 3325: <div></div>
3326: <p>This part of the book deals with creating and
1.23 wiz 3327: modifying packages. It starts with a <span class="quote">“<span class="quote">HOWTO</span>”</span>-like
1.1 dsieger 3328: guide on creating a new package. The remaining chapters are more
3329: like a reference manual for pkgsrc.</p>
3330: <div class="toc">
3331: <p><b>Table of Contents</b></p>
1.100 leot 3332: <dl class="toc">
1.6 rillig 3333: <dt><span class="chapter"><a href="#creating">10. Creating a new pkgsrc package from scratch</a></span></dt>
1.1 dsieger 3334: <dd><dl>
1.6 rillig 3335: <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
1.1 dsieger 3336: <dd><dl>
1.6 rillig 3337: <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
1.66 asau 3338: <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE3 applications</a></span></dt>
1.17 imil 3339: <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
1.1 dsieger 3340: </dl></dd>
1.6 rillig 3341: <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
3342: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
3343: </dl></dd>
3344: <dt><span class="chapter"><a href="#components">11. Package components - files, directories and contents</a></span></dt>
3345: <dd><dl>
1.23 wiz 3346: <dt><span class="sect1"><a href="#components.Makefile">11.1. <code class="filename">Makefile</code></a></span></dt>
3347: <dt><span class="sect1"><a href="#components.distinfo">11.2. <code class="filename">distinfo</code></a></span></dt>
1.6 rillig 3348: <dt><span class="sect1"><a href="#components.patches">11.3. patches/*</a></span></dt>
3349: <dd><dl>
3350: <dt><span class="sect2"><a href="#components.patch.structure">11.3.1. Structure of a single patch file</a></span></dt>
3351: <dt><span class="sect2"><a href="#components.patches.caveats">11.3.2. Creating patch files</a></span></dt>
3352: <dt><span class="sect2"><a href="#components.patches.sources">11.3.3. Sources where the patch files come from</a></span></dt>
3353: <dt><span class="sect2"><a href="#components.patches.guidelines">11.3.4. Patching guidelines</a></span></dt>
3354: <dt><span class="sect2"><a href="#components.patches.feedback">11.3.5. Feedback to the author</a></span></dt>
3355: </dl></dd>
3356: <dt><span class="sect1"><a href="#other-mandatory-files">11.4. Other mandatory files</a></span></dt>
3357: <dt><span class="sect1"><a href="#components.optional">11.5. Optional files</a></span></dt>
3358: <dd><dl>
3359: <dt><span class="sect2"><a href="#components.optional.bin">11.5.1. Files affecting the binary package</a></span></dt>
3360: <dt><span class="sect2"><a href="#components.optional.build">11.5.2. Files affecting the build process</a></span></dt>
3361: <dt><span class="sect2"><a href="#components.optional.none">11.5.3. Files affecting nothing at all</a></span></dt>
3362: </dl></dd>
1.23 wiz 3363: <dt><span class="sect1"><a href="#work-dir">11.6. <code class="filename">work*</code></a></span></dt>
3364: <dt><span class="sect1"><a href="#files-dir">11.7. <code class="filename">files/*</code></a></span></dt>
1.6 rillig 3365: </dl></dd>
1.23 wiz 3366: <dt><span class="chapter"><a href="#makefile">12. Programming in <code class="filename">Makefile</code>s</a></span></dt>
1.6 rillig 3367: <dd><dl>
3368: <dt><span class="sect1"><a href="#makefile.style">12.1. Caveats</a></span></dt>
1.23 wiz 3369: <dt><span class="sect1"><a href="#makefile.variables">12.2. <code class="filename">Makefile</code> variables</a></span></dt>
1.6 rillig 3370: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">12.2.1. Naming conventions</a></span></dt></dl></dd>
3371: <dt><span class="sect1"><a href="#makefile.code">12.3. Code snippets</a></span></dt>
3372: <dd><dl>
3373: <dt><span class="sect2"><a href="#adding-to-list">12.3.1. Adding things to a list</a></span></dt>
3374: <dt><span class="sect2"><a href="#converting-internal-to-external">12.3.2. Converting an internal list into an external list</a></span></dt>
3375: <dt><span class="sect2"><a href="#passing-variable-to-shell">12.3.3. Passing variables to a shell command</a></span></dt>
3376: <dt><span class="sect2"><a href="#quoting-guideline">12.3.4. Quoting guideline</a></span></dt>
3377: <dt><span class="sect2"><a href="#bsd-make-bug-workaround">12.3.5. Workaround for a bug in BSD Make</a></span></dt>
3378: </dl></dd>
3379: </dl></dd>
3380: <dt><span class="chapter"><a href="#plist">13. PLIST issues</a></span></dt>
3381: <dd><dl>
3382: <dt><span class="sect1"><a href="#rcs-id">13.1. RCS ID</a></span></dt>
1.23 wiz 3383: <dt><span class="sect1"><a href="#automatic-plist-generation">13.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
3384: <dt><span class="sect1"><a href="#print-PLIST">13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
1.6 rillig 3385: <dt><span class="sect1"><a href="#plist.misc">13.4. Variable substitution in PLIST</a></span></dt>
3386: <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt>
1.23 wiz 3387: <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
1.6 rillig 3388: <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt>
1.86 wiz 3389: <dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt>
3390: <dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt>
1.6 rillig 3391: </dl></dd>
3392: <dt><span class="chapter"><a href="#buildlink">14. Buildlink methodology</a></span></dt>
3393: <dd><dl>
3394: <dt><span class="sect1"><a href="#converting-to-buildlink3">14.1. Converting packages to use buildlink3</a></span></dt>
1.23 wiz 3395: <dt><span class="sect1"><a href="#creating-buildlink3.mk">14.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3396: <dd><dl>
3397: <dt><span class="sect2"><a href="#anatomy-of-bl3">14.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
1.26 wiz 3398: <dt><span class="sect2"><a href="#updating-buildlink-depends">14.2.2. Updating
3399: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3400: and
3401: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
3402: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.6 rillig 3403: </dl></dd>
1.23 wiz 3404: <dt><span class="sect1"><a href="#writing-builtin.mk">14.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.6 rillig 3405: <dd><dl>
1.23 wiz 3406: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">14.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
1.6 rillig 3407: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">14.3.2. Global preferences for native or pkgsrc software</a></span></dt>
3408: </dl></dd>
3409: </dl></dd>
3410: <dt><span class="chapter"><a href="#pkginstall">15. The pkginstall framework</a></span></dt>
3411: <dd><dl>
3412: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">15.1. Files and directories outside the installation prefix</a></span></dt>
3413: <dd><dl>
3414: <dt><span class="sect2"><a href="#dirs-outside-prefix">15.1.1. Directory manipulation</a></span></dt>
3415: <dt><span class="sect2"><a href="#files-outside-prefix">15.1.2. File manipulation</a></span></dt>
3416: </dl></dd>
3417: <dt><span class="sect1"><a href="#conf-files">15.2. Configuration files</a></span></dt>
3418: <dd><dl>
1.23 wiz 3419: <dt><span class="sect2"><a href="#conf-files-sysconfdir">15.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
1.6 rillig 3420: <dt><span class="sect2"><a href="#conf-files-configure">15.2.2. Telling the software where configuration files are</a></span></dt>
3421: <dt><span class="sect2"><a href="#conf-files-patching">15.2.3. Patching installations</a></span></dt>
3422: <dt><span class="sect2"><a href="#conf-files-disable">15.2.4. Disabling handling of configuration files</a></span></dt>
3423: </dl></dd>
3424: <dt><span class="sect1"><a href="#rcd-scripts">15.3. System startup scripts</a></span></dt>
3425: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">15.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
3426: <dt><span class="sect1"><a href="#users-and-groups">15.4. System users and groups</a></span></dt>
3427: <dt><span class="sect1"><a href="#shells">15.5. System shells</a></span></dt>
3428: <dd><dl><dt><span class="sect2"><a href="#shells-disable">15.5.1. Disabling shell registration</a></span></dt></dl></dd>
3429: <dt><span class="sect1"><a href="#fonts">15.6. Fonts</a></span></dt>
3430: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">15.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
3431: </dl></dd>
3432: <dt><span class="chapter"><a href="#options">16. Options handling</a></span></dt>
3433: <dd><dl>
3434: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
1.23 wiz 3435: <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>
1.6 rillig 3436: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
1.7 rillig 3437: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.6 rillig 3438: </dl></dd>
3439: <dt><span class="chapter"><a href="#build">17. The build process</a></span></dt>
3440: <dd><dl>
3441: <dt><span class="sect1"><a href="#build.intro">17.1. Introduction</a></span></dt>
3442: <dt><span class="sect1"><a href="#build.prefix">17.2. Program location</a></span></dt>
3443: <dt><span class="sect1"><a href="#build.builddirs">17.3. Directories used during the build process</a></span></dt>
3444: <dt><span class="sect1"><a href="#build.running">17.4. Running a phase</a></span></dt>
1.23 wiz 3445: <dt><span class="sect1"><a href="#build.fetch">17.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 3446: <dd><dl>
3447: <dt><span class="sect2"><a href="#build.fetch.what">17.5.1. What to fetch and where to get it from</a></span></dt>
3448: <dt><span class="sect2"><a href="#build.fetch.how">17.5.2. How are the files fetched?</a></span></dt>
3449: </dl></dd>
1.23 wiz 3450: <dt><span class="sect1"><a href="#build.checksum">17.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
3451: <dt><span class="sect1"><a href="#build.extract">17.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
3452: <dt><span class="sect1"><a href="#build.patch">17.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
3453: <dt><span class="sect1"><a href="#build.tools">17.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
3454: <dt><span class="sect1"><a href="#build.wrapper">17.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
3455: <dt><span class="sect1"><a href="#build.configure">17.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
3456: <dt><span class="sect1"><a href="#build.build">17.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
3457: <dt><span class="sect1"><a href="#build.test">17.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
3458: <dt><span class="sect1"><a href="#build.install">17.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
3459: <dt><span class="sect1"><a href="#build.package">17.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
1.6 rillig 3460: <dt><span class="sect1"><a href="#build.clean">17.16. Cleaning up</a></span></dt>
3461: <dt><span class="sect1"><a href="#build.helpful-targets">17.17. Other helpful targets</a></span></dt>
3462: </dl></dd>
3463: <dt><span class="chapter"><a href="#tools">18. Tools needed for building or running</a></span></dt>
3464: <dd><dl>
3465: <dt><span class="sect1"><a href="#pkgsrc-tools">18.1. Tools for pkgsrc builds</a></span></dt>
3466: <dt><span class="sect1"><a href="#package-tools">18.2. Tools needed by packages</a></span></dt>
3467: <dt><span class="sect1"><a href="#platform-tools">18.3. Tools provided by platforms</a></span></dt>
3468: <dt><span class="sect1"><a href="#tools.questions">18.4. Questions regarding the tools</a></span></dt>
3469: </dl></dd>
3470: <dt><span class="chapter"><a href="#fixes">19. Making your package work</a></span></dt>
3471: <dd><dl>
3472: <dt><span class="sect1"><a href="#general-operation">19.1. General operation</a></span></dt>
3473: <dd><dl>
3474: <dt><span class="sect2"><a href="#portability-of-packages">19.1.1. Portability of packages</a></span></dt>
1.23 wiz 3475: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">19.1.2. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
1.6 rillig 3476: <dt><span class="sect2"><a href="#user-interaction">19.1.3. User interaction</a></span></dt>
3477: <dt><span class="sect2"><a href="#handling-licenses">19.1.4. Handling licenses</a></span></dt>
3478: <dt><span class="sect2"><a href="#restricted-packages">19.1.5. Restricted packages</a></span></dt>
3479: <dt><span class="sect2"><a href="#dependencies">19.1.6. Handling dependencies</a></span></dt>
3480: <dt><span class="sect2"><a href="#conflicts">19.1.7. Handling conflicts with other packages</a></span></dt>
3481: <dt><span class="sect2"><a href="#not-building-packages">19.1.8. Packages that cannot or should not be built</a></span></dt>
3482: <dt><span class="sect2"><a href="#undeletable-packages">19.1.9. Packages which should not be deleted, once installed</a></span></dt>
3483: <dt><span class="sect2"><a href="#security-handling">19.1.10. Handling packages with security problems</a></span></dt>
3484: <dt><span class="sect2"><a href="#bumping-pkgrevision">19.1.11. How to handle incrementing versions when fixing an existing package</a></span></dt>
3485: <dt><span class="sect2"><a href="#fixes.subst">19.1.12. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
3486: </dl></dd>
1.23 wiz 3487: <dt><span class="sect1"><a href="#fixes.fetch">19.2. Fixing problems in the <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 3488: <dd><dl>
3489: <dt><span class="sect2"><a href="#no-plain-download">19.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
3490: <dt><span class="sect2"><a href="#modified-distfiles-same-name">19.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
1.88 tnn 3491: <dt><span class="sect2"><a href="#build.fetch.github">19.2.3. Packages hosted on github.com</a></span></dt>
1.6 rillig 3492: </dl></dd>
1.23 wiz 3493: <dt><span class="sect1"><a href="#fixes.configure">19.3. Fixing problems in the <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
1.6 rillig 3494: <dd><dl>
3495: <dt><span class="sect2"><a href="#fixes.libtool">19.3.1. Shared libraries - libtool</a></span></dt>
3496: <dt><span class="sect2"><a href="#using-libtool">19.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
3497: <dt><span class="sect2"><a href="#autoconf-automake">19.3.3. GNU Autoconf/Automake</a></span></dt>
3498: </dl></dd>
3499: <dt><span class="sect1"><a href="#programming-languages">19.4. Programming languages</a></span></dt>
3500: <dd><dl>
3501: <dt><span class="sect2"><a href="#basic-programming-languages">19.4.1. C, C++, and Fortran</a></span></dt>
3502: <dt><span class="sect2"><a href="#java-programming-language">19.4.2. Java</a></span></dt>
3503: <dt><span class="sect2"><a href="#perl-scripts">19.4.3. Packages containing perl scripts</a></span></dt>
1.40 wiz 3504: <dt><span class="sect2"><a href="#shell-scripts">19.4.4. Packages containing shell scripts</a></span></dt>
3505: <dt><span class="sect2"><a href="#other-programming-languages">19.4.5. Other programming languages</a></span></dt>
1.6 rillig 3506: </dl></dd>
1.23 wiz 3507: <dt><span class="sect1"><a href="#fixes.build">19.5. Fixing problems in the <span class="emphasis"><em>build</em></span> phase</a></span></dt>
1.6 rillig 3508: <dd><dl>
3509: <dt><span class="sect2"><a href="#fixes.build.cpp">19.5.1. Compiling C and C++ code conditionally</a></span></dt>
3510: <dt><span class="sect2"><a href="#compiler-bugs">19.5.2. How to handle compiler bugs</a></span></dt>
1.23 wiz 3511: <dt><span class="sect2"><a href="#undefined-reference">19.5.3. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
1.6 rillig 3512: <dt><span class="sect2"><a href="#out-of-memory">19.5.4. Running out of memory</a></span></dt>
3513: </dl></dd>
1.23 wiz 3514: <dt><span class="sect1"><a href="#fixes.install">19.6. Fixing problems in the <span class="emphasis"><em>install</em></span> phase</a></span></dt>
1.6 rillig 3515: <dd><dl>
3516: <dt><span class="sect2"><a href="#install-scripts">19.6.1. Creating needed directories</a></span></dt>
3517: <dt><span class="sect2"><a href="#where-to-install-documentation">19.6.2. Where to install documentation</a></span></dt>
3518: <dt><span class="sect2"><a href="#installing-score-files">19.6.3. Installing highscore files</a></span></dt>
3519: <dt><span class="sect2"><a href="#destdir-support">19.6.4. Adding DESTDIR support to packages</a></span></dt>
3520: <dt><span class="sect2"><a href="#hardcoded-paths">19.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
3521: <dt><span class="sect2"><a href="#perl-modules">19.6.6. Packages installing perl modules</a></span></dt>
3522: <dt><span class="sect2"><a href="#faq.info-files">19.6.7. Packages installing info files</a></span></dt>
3523: <dt><span class="sect2"><a href="#manpages">19.6.8. Packages installing man pages</a></span></dt>
1.7 rillig 3524: <dt><span class="sect2"><a href="#gconf-data-files">19.6.9. Packages installing GConf data files</a></span></dt>
1.18 snj 3525: <dt><span class="sect2"><a href="#scrollkeeper-data-files">19.6.10. Packages installing scrollkeeper/rarian data files</a></span></dt>
1.6 rillig 3526: <dt><span class="sect2"><a href="#x11-fonts">19.6.11. Packages installing X11 fonts</a></span></dt>
3527: <dt><span class="sect2"><a href="#gtk2-modules">19.6.12. Packages installing GTK2 modules</a></span></dt>
3528: <dt><span class="sect2"><a href="#sgml-xml-data">19.6.13. Packages installing SGML or XML data</a></span></dt>
3529: <dt><span class="sect2"><a href="#mime-database">19.6.14. Packages installing extensions to the MIME database</a></span></dt>
3530: <dt><span class="sect2"><a href="#intltool">19.6.15. Packages using intltool</a></span></dt>
3531: <dt><span class="sect2"><a href="#startup-scripts">19.6.16. Packages installing startup scripts</a></span></dt>
3532: <dt><span class="sect2"><a href="#tex-packages">19.6.17. Packages installing TeX modules</a></span></dt>
3533: <dt><span class="sect2"><a href="#emulation-packages">19.6.18. Packages supporting running binaries in
1.1 dsieger 3534: emulation</a></span></dt>
1.6 rillig 3535: <dt><span class="sect2"><a href="#hicolor-theme">19.6.19. Packages installing hicolor theme icons</a></span></dt>
3536: <dt><span class="sect2"><a href="#desktop-files">19.6.20. Packages installing desktop files</a></span></dt>
1.1 dsieger 3537: </dl></dd>
1.6 rillig 3538: <dt><span class="sect1"><a href="#punting">19.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 3539: </dl></dd>
1.6 rillig 3540: <dt><span class="chapter"><a href="#debug">20. Debugging</a></span></dt>
3541: <dt><span class="chapter"><a href="#submit">21. Submitting and Committing</a></span></dt>
1.1 dsieger 3542: <dd><dl>
1.6 rillig 3543: <dt><span class="sect1"><a href="#submitting-binary-packages">21.1. Submitting binary packages</a></span></dt>
3544: <dt><span class="sect1"><a href="#submitting-your-package">21.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
3545: <dt><span class="sect1"><a href="#general-notes-for-changes">21.3. General notes when adding, updating, or removing packages</a></span></dt>
1.33 wiz 3546: <dt><span class="sect1"><a href="#committing-importing">21.4. Committing: Adding a package to CVS</a></span></dt>
1.6 rillig 3547: <dt><span class="sect1"><a href="#updating-package">21.5. Updating a package to a newer version</a></span></dt>
1.20 snj 3548: <dt><span class="sect1"><a href="#renaming-package">21.6. Renaming a package in pkgsrc</a></span></dt>
3549: <dt><span class="sect1"><a href="#moving-package">21.7. Moving a package in pkgsrc</a></span></dt>
1.6 rillig 3550: </dl></dd>
3551: <dt><span class="chapter"><a href="#devfaq">22. Frequently Asked Questions</a></span></dt>
3552: <dt><span class="chapter"><a href="#gnome">23. GNOME packaging and porting</a></span></dt>
3553: <dd><dl>
3554: <dt><span class="sect1"><a href="#meta-packages">23.1. Meta packages</a></span></dt>
3555: <dt><span class="sect1"><a href="#new-package">23.2. Packaging a GNOME application</a></span></dt>
3556: <dt><span class="sect1"><a href="#full-update">23.3. Updating GNOME to a newer version</a></span></dt>
3557: <dt><span class="sect1"><a href="#patching">23.4. Patching guidelines</a></span></dt>
1.1 dsieger 3558: </dl></dd>
3559: </dl>
3560: </div>
3561: </div>
1.41 asau 3562: <div class="chapter">
1.1 dsieger 3563: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 3564: <a name="creating"></a>Chapter 10. Creating a new pkgsrc package from scratch</h2></div></div></div>
1.1 dsieger 3565: <div class="toc">
3566: <p><b>Table of Contents</b></p>
1.100 leot 3567: <dl class="toc">
1.6 rillig 3568: <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
1.1 dsieger 3569: <dd><dl>
1.6 rillig 3570: <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
1.66 asau 3571: <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE3 applications</a></span></dt>
1.17 imil 3572: <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
1.1 dsieger 3573: </dl></dd>
1.6 rillig 3574: <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
3575: <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
1.1 dsieger 3576: </dl>
3577: </div>
3578: <p>When you find a package that is not yet in pkgsrc, you
3579: most likely have a URL from where you can download the source
3580: code. Starting with this URL, creating a package involves only a
3581: few steps.</p>
1.23 wiz 3582: <div class="procedure"><ol class="procedure" type="1">
1.79 snj 3583: <li class="step"><p>First, install the packages <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a> and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>.</p></li>
1.41 asau 3584: <li class="step"><p>Then, choose one of the top-level directories as the
1.1 dsieger 3585: category in which you want to place your package. You can also create a
3586: directory of your own (maybe called <code class="filename">local</code>). In that
3587: category directory, create another directory for your package and change
3588: into it.</p></li>
1.41 asau 3589: <li class="step"><p>Run the program <span class="command"><strong>url2pkg</strong></span>, which will ask
1.1 dsieger 3590: you for a URL. Enter the URL of the distribution file (in most cases a
3591: <code class="filename">.tar.gz</code> file) and watch how the basic ingredients
3592: of your package are created automatically. The distribution file is
3593: extracted automatically to fill in some details in the
3594: <code class="filename">Makefile</code> that would otherwise have to be done
3595: manually.</p></li>
1.41 asau 3596: <li class="step">
1.1 dsieger 3597: <p>Examine the extracted files to determine the dependencies of
3598: your package. Ideally, this is mentioned in some
3599: <code class="filename">README</code> file, but things may differ. For each of
3600: these dependencies, look where it exists in pkgsrc, and if there is a
3601: file called <code class="filename">buildlink3.mk</code> in that directory, add a
3602: line to your package <code class="filename">Makefile</code> which includes that
3603: file just before the last line. If the
1.25 spz 3604: <code class="filename">buildlink3.mk</code> file does not exist, it must be
3605: created first. The <code class="filename">buildlink3.mk</code> file makes sure that the package's include files and libraries are provided.</p>
3606: <p>If you just need binaries from a package, add a
1.1 dsieger 3607: <code class="varname">DEPENDS</code> line to the Makefile, which specifies the
3608: version of the dependency and where it can be found in pkgsrc. This line
3609: should be placed in the third paragraph. If the dependency is only
3610: needed for building the package, but not when using it, use
3611: <code class="varname">BUILD_DEPENDS</code> instead of <code class="varname">DEPENDS</code>.
3612: Your package may then look like this:</p>
3613: <pre class="programlisting">
3614: [...]
3615:
1.66 asau 3616: BUILD_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
1.1 dsieger 3617: DEPENDS+= screen-[0-9]*:../../misc/screen
3618: DEPENDS+= screen>=4.0:../../misc/screen
3619:
3620: [...]
3621:
3622: .include "../../<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>package</code></em>/buildlink3.mk"
3623: .include "../../devel/glib2/buildlink3.mk"
3624: .include "../../mk/bsd.pkg.mk"
3625: </pre>
3626: </li>
1.41 asau 3627: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> to see what things still need
1.23 wiz 3628: to be done to make your package a <span class="quote">“<span class="quote">good</span>”</span> one. If you don't
1.10 hubertf 3629: know what pkglint's warnings want to tell you, try <span class="command"><strong>pkglint
3630: --explain</strong></span> or <span class="command"><strong>pkglint
1.1 dsieger 3631: -e</strong></span>, which outputs additional
3632: explanations.</p></li>
1.41 asau 3633: <li class="step"><p>In many cases the package is not yet ready to build. You can
1.10 hubertf 3634: find instructions for the most common cases in the next section, <a class="xref" href="#creating.common" title="10.1. Common types of packages">Section 10.1, “Common types of packages”</a>. After you have followed the instructions
1.1 dsieger 3635: over there, you can hopefully continue here.</p></li>
1.41 asau 3636: <li class="step"><p>Run <span class="command"><strong>bmake clean</strong></span> to clean the working
1.1 dsieger 3637: directory from the extracted files. Besides these files, a lot of cache
3638: files and other system information has been saved in the working
3639: directory, which may become wrong after you edited the
3640: <code class="filename">Makefile</code>.</p></li>
1.41 asau 3641: <li class="step"><p>Now, run <span class="command"><strong>bmake</strong></span> to build the package. For
1.10 hubertf 3642: the various things that can go wrong in this phase, consult <a class="xref" href="#fixes" title="Chapter 19. Making your package work">Chapter 19, <i>Making your package work</i></a>.</p></li>
1.41 asau 3643: <li class="step"><p>When the package builds fine, the next step is to install
1.10 hubertf 3644: the package. Run <span class="command"><strong>bmake install</strong></span> and hope that
1.1 dsieger 3645: everything works.</p></li>
1.41 asau 3646: <li class="step"><p>Up to now, the file <code class="filename">PLIST</code>, which
1.1 dsieger 3647: contains a list of the files that are installed by the package, is
1.10 hubertf 3648: nearly empty. Run <span class="command"><strong>bmake print-PLIST
1.1 dsieger 3649: >PLIST</strong></span> to generate a probably correct list. Check
3650: the file using your preferred text editor to see if the list of
3651: files looks plausible.</p></li>
1.41 asau 3652: <li class="step"><p>Run <span class="command"><strong>pkglint</strong></span> again to see if the generated
1.1 dsieger 3653: <code class="filename">PLIST</code> contains garbage or not.</p></li>
1.41 asau 3654: <li class="step"><p>When you ran <span class="command"><strong>bmake install</strong></span>, the package
1.1 dsieger 3655: has been registered in the database of installed files, but with an
1.10 hubertf 3656: empty list of files. To fix this, run <span class="command"><strong>bmake deinstall</strong></span>
3657: and <span class="command"><strong>bmake install</strong></span> again. Now the package is
1.1 dsieger 3658: registered with the list of files from
3659: <code class="filename">PLIST</code>.</p></li>
1.41 asau 3660: <li class="step"><p>Run <span class="command"><strong>bmake package</strong></span> to create a binary
1.1 dsieger 3661: package from the set of installed files.</p></li>
3662: </ol></div>
1.41 asau 3663: <div class="sect1">
1.1 dsieger 3664: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 3665: <a name="creating.common"></a>10.1. Common types of packages</h2></div></div></div>
1.41 asau 3666: <div class="sect2">
1.1 dsieger 3667: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 3668: <a name="creating.perl-module"></a>10.1.1. Perl modules</h3></div></div></div>
1.1 dsieger 3669: <p>Simple Perl modules are handled automatically by
1.10 hubertf 3670: <span class="command"><strong>url2pkg</strong></span>, including dependencies.</p>
1.1 dsieger 3671: </div>
1.41 asau 3672: <div class="sect2">
1.1 dsieger 3673: <div class="titlepage"><div><div><h3 class="title">
1.66 asau 3674: <a name="creating.kde-app"></a>10.1.2. KDE3 applications</h3></div></div></div>
3675: <p>KDE3 applications should always include
1.1 dsieger 3676: <code class="filename">meta-pkgs/kde3/kde3.mk</code>, which contains numerous
1.66 asau 3677: settings that are typical of KDE3 packages.</p>
1.1 dsieger 3678: </div>
1.41 asau 3679: <div class="sect2">
1.17 imil 3680: <div class="titlepage"><div><div><h3 class="title">
3681: <a name="creating.python-module"></a>10.1.3. Python modules and programs</h3></div></div></div>
3682: <p>Python modules and programs packages are easily created using a
3683: set of predefined variables.</p>
3684: <p>
1.63 wiz 3685: If some Python versions are not supported by the software, set the
3686: <code class="varname">PYTHON_VERSIONS_INCOMPATIBLE</code> variable to the Python versions
3687: that are not supported, e.g.
1.17 imil 3688: </p>
3689: <pre class="programlisting">
1.93 sevan 3690: PYTHON_VERSIONS_INCOMPATIBLE= 27
1.17 imil 3691: </pre>
3692: <p>
3693: If the packaged software is a Python module, include
1.23 wiz 3694: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/extension.mk</code></span>”</span>.
1.17 imil 3695: In this case, the package directory should be called
1.23 wiz 3696: <span class="quote">“<span class="quote">py-software</span>”</span> and <code class="varname">PKGNAME</code> should be set to
3697: <span class="quote">“<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>”</span>, e.g.
1.17 imil 3698: </p>
3699: <pre class="programlisting">
3700: DISTNAME= foopymodule-1.2.10
3701: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
3702: </pre>
1.63 wiz 3703: <p>If it is an application, include
3704: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>”</span>.
3705: In order to correctly set the path to the Python interpreter, use the
1.17 imil 3706: <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
1.35 wiz 3707: (paths relative to <code class="varname">WRKSRC</code>) that must be corrected.
1.63 wiz 3708: For example:
1.17 imil 3709: </p>
3710: <pre class="programlisting">
1.35 wiz 3711: REPLACE_PYTHON= *.py
1.17 imil 3712: </pre>
1.63 wiz 3713: <p>Most Python packages use either <span class="quote">“<span class="quote">distutils</span>”</span> or
3714: easy-setup (<span class="quote">“<span class="quote">eggs</span>”</span>).
3715: If the software uses <span class="quote">“<span class="quote">distutils</span>”</span>, include
3716: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/distutils.mk</code></span>”</span>.
3717: so pkgsrc will use this framework.
3718: <span class="quote">“<span class="quote">distutils</span>”</span> uses a script called <code class="filename">setup.py</code>,
3719: if the <span class="quote">“<span class="quote">distutils</span>”</span> driver is not called
3720: <code class="filename">setup.py</code>, set the <code class="varname">PYSETUP</code> variable
3721: to the name of the script.</p>
3722: <p>Otherwise, if the packaged software is egg-aware, you only need
3723: to include
3724: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/egg.mk</code></span>”</span>.</p>
3725: <p>Some Python modules have separate distributions for Python-2.x
3726: and Python-3.x support. In pkgsrc this is handled by the
3727: <code class="filename">versioned_dependencies.mk</code> file. Set
3728: <code class="varname">PYTHON_VERSIONED_DEPENDENCIES</code> to the list of
3729: packages that should be depended upon and include
3730: <span class="quote">“<span class="quote"><code class="filename">../../lang/python/versioned_dependencies.mk</code></span>”</span>,
3731: then the pkgsrc infrastructure will depend on the appropriate package
3732: version. For example:
3733: </p>
3734: <pre class="programlisting">
3735: PYTHON_VERSIONED_DEPENDENCIES=dateutil dns
3736: </pre>
3737: <p>
3738: Look inside <code class="filename">versioned_dependencies.mk</code> for a list
3739: of supported packages.</p>
1.17 imil 3740: </div>
1.1 dsieger 3741: </div>
1.41 asau 3742: <div class="sect1">
1.1 dsieger 3743: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 3744: <a name="creating.examples"></a>10.2. Examples</h2></div></div></div>
1.41 asau 3745: <div class="sect2">
1.1 dsieger 3746: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 3747: <a name="creating.nvu"></a>10.2.1. How the www/nvu package came into pkgsrc</h3></div></div></div>
1.41 asau 3748: <div class="sect3">
1.1 dsieger 3749: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 3750: <a name="creating.nvu.init"></a>10.2.1.1. The initial package</h4></div></div></div>
1.1 dsieger 3751: <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
1.23 wiz 3752: that the <span class="quote">“<span class="quote">nvu</span>”</span> package has not yet been imported into
1.1 dsieger 3753: pkgsrc. As the description says it has to do with the web, the obvious
1.23 wiz 3754: choice for the category is <span class="quote">“<span class="quote">www</span>”</span>.</p>
1.1 dsieger 3755: <pre class="programlisting">
3756: <code class="prompt">$</code> mkdir www/nvu
3757: <code class="prompt">$</code> cd www/nvu
3758: </pre>
3759: <p>The web site says that the sources are available as a tar file, so
1.10 hubertf 3760: I fed that URL to the <span class="command"><strong>url2pkg</strong></span> program:</p>
1.1 dsieger 3761: <pre class="programlisting">
3762: <code class="prompt">$</code> url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
3763: </pre>
3764: <p>My editor popped up, and I added a <code class="varname">PKGNAME</code> line
3765: below the <code class="varname">DISTNAME</code> line, as the package name should
1.23 wiz 3766: not have the word <span class="quote">“<span class="quote">sources</span>”</span> in it. I also filled in the
1.1 dsieger 3767: <code class="varname">MAINTAINER</code>, <code class="varname">HOMEPAGE</code> and
3768: <code class="varname">COMMENT</code> fields. Then the package
3769: <code class="filename">Makefile</code> looked like that:</p>
3770: <pre class="programlisting">
3771: # $NetBSD$
3772: #
3773:
3774: DISTNAME= nvu-1.0-sources
3775: PKGNAME= nvu-1.0
3776: CATEGORIES= www
3777: MASTER_SITES= http://cvs.nvu.com/download/
3778: EXTRACT_SUFX= .tar.bz2
3779:
3780: MAINTAINER= rillig@NetBSD.org
3781: HOMEPAGE= http://cvs.nvu.com/
3782: COMMENT= Web Authoring System
3783:
3784: # url2pkg-marker (please do not remove this line.)
3785: .include "../../mk/bsd.pkg.mk"
3786: </pre>
3787: <p>Then, I quit the editor and watched pkgsrc downloading a large
3788: source archive:</p>
3789: <pre class="programlisting">
3790: url2pkg> Running "make makesum" ...
3791: => Required installed package digest>=20010302: digest-20060826 found
3792: => Fetching nvu-1.0-sources.tar.bz2
3793: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
3794: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
3795: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
3796: url2pkg> Running "make extract" ...
3797: => Required installed package digest>=20010302: digest-20060826 found
3798: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
3799: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
3800: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
3801: ===> Installing dependencies for nvu-1.0
3802: ===> Overriding tools for nvu-1.0
3803: ===> Extracting for nvu-1.0
3804: url2pkg> Adjusting the Makefile.
3805:
3806: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
3807:
3808: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
3809: </pre>
3810: </div>
1.41 asau 3811: <div class="sect3">
1.1 dsieger 3812: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 3813: <a name="creating.nvu.problems"></a>10.2.1.2. Fixing all kinds of problems to make the package work</h4></div></div></div>
1.1 dsieger 3814: <p>Now that the package has been extracted, let's see what's inside
3815: it. The package has a <code class="filename">README.txt</code>, but that only
3816: says something about mozilla, so it's probably useless for seeing what
3817: dependencies this package has. But since there is a GNU configure script
3818: in the package, let's hope that it will complain about everything it
3819: needs.</p>
3820: <pre class="programlisting">
3821: <code class="prompt">$</code> bmake
3822: => Required installed package digest>=20010302: digest-20060826 found
3823: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
3824: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
3825: ===> Patching for nvu-1.0
3826: ===> Creating toolchain wrappers for nvu-1.0
3827: ===> Configuring for nvu-1.0
3828: [...]
3829: configure: error: Perl 5.004 or higher is required.
3830: [...]
3831: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
3832: [...]
3833: </pre>
3834: <p>That worked quite well. So I opened the package Makefile in my
3835: editor, and since it already has a <code class="varname">USE_TOOLS</code> line, I
1.23 wiz 3836: just appended <span class="quote">“<span class="quote">perl</span>”</span> to it. Since the dependencies of the
1.1 dsieger 3837: package have changed now, and since a perl wrapper is automatically
1.23 wiz 3838: installed in the <span class="quote">“<span class="quote">tools</span>”</span> phase, I need to build the package
1.1 dsieger 3839: from scratch.</p>
3840: <pre class="programlisting">
3841: <code class="prompt">$</code> bmake clean
3842: ===> Cleaning for nvu-1.0
3843: <code class="prompt">$</code> bmake
3844: [...]
3845: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
3846: GNU Make. You will not be able to build Mozilla without GNU Make.
3847: [...]
3848: </pre>
1.23 wiz 3849: <p>So I added <span class="quote">“<span class="quote">gmake</span>”</span> to the
1.1 dsieger 3850: <code class="varname">USE_TOOLS</code> line and tried again (from scratch).</p>
3851: <pre class="programlisting">
3852: [...]
3853: checking for GTK - version >= 1.2.0... no
3854: *** Could not run GTK test program, checking why...
3855: [...]
3856: </pre>
3857: <p>Now to the other dependencies. The first question is: Where is the
3858: GTK package hidden in pkgsrc?</p>
3859: <pre class="programlisting">
3860: <code class="prompt">$</code> echo ../../*/gtk*
3861: [many packages ...]
3862: <code class="prompt">$</code> echo ../../*/gtk
3863: ../../x11/gtk
3864: <code class="prompt">$</code> echo ../../*/gtk2
3865: ../../x11/gtk2
3866: <code class="prompt">$</code> echo ../../*/gtk2/bui*
3867: ../../x11/gtk2/buildlink3.mk
3868: </pre>
3869: <p>The first try was definitely too broad. The second one had exactly
3870: one result, which is very good. But there is one pitfall with GNOME
3871: packages. Before GNOME 2 had been released, there were already many
3872: GNOME 1 packages in pkgsrc. To be able to continue to use these
3873: packages, the GNOME 2 packages were imported as separate packages, and
1.23 wiz 3874: their names usually have a <span class="quote">“<span class="quote">2</span>”</span> appended. So I checked
1.1 dsieger 3875: whether this was the case here, and indeed it was.</p>
3876: <p>Since the GTK2 package has a <code class="filename">buildlink3.mk</code>
3877: file, adding the dependency is very easy. I just inserted an
3878: <code class="literal">.include</code> line before the last line of the package
3879: <code class="filename">Makefile</code>, so that it now looks like this:</p>
3880: <pre class="programlisting">
3881: [...]
3882: .include "../../x11/gtk2/buildlink3.mk"
3883: .include "../../mk/bsd.pkg.mk
3884: </pre>
1.10 hubertf 3885: <p>After another <span class="command"><strong>bmake clean && bmake</strong></span>, the answer
1.1 dsieger 3886: was:</p>
3887: <pre class="programlisting">
3888: [...]
3889: checking for gtk-config... /home/roland/pkg/bin/gtk-config
3890: checking for GTK - version >= 1.2.0... no
3891: *** Could not run GTK test program, checking why...
3892: *** The test program failed to compile or link. See the file config.log for the
3893: *** exact error that occured. This usually means GTK was incorrectly installed
3894: *** or that you have moved GTK since it was installed. In the latter case, you
3895: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
3896: configure: error: Test for GTK failed.
3897: [...]
3898: </pre>
1.23 wiz 3899: <p>In this particular case, the assumption that <span class="quote">“<span class="quote">every package
3900: prefers GNOME 2</span>”</span> had been wrong. The first of the lines above
1.1 dsieger 3901: told me that this package really wanted to have the GNOME 1 version of
3902: GTK. If the package had looked for GTK2, it would have looked for
1.10 hubertf 3903: <span class="command"><strong>pkg-config</strong></span> instead of <span class="command"><strong>gtk-config</strong></span>.
1.1 dsieger 3904: So I changed the <code class="literal">x11/gtk2</code> to
3905: <code class="literal">x11/gtk</code> in the package <code class="filename">Makefile</code>,
3906: and tried again.</p>
3907: <pre class="programlisting">
3908: [...]
1.59 jnemeth 3909: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
1.1 dsieger 3910: In file included from xpidl.c:42:
3911: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
3912: In file included from xpidl.c:42:
3913: xpidl.h:132: error: parse error before "IDL_ns"
3914: [...]
3915: </pre>
3916: <p>The package still does not find all of its dependencies. Now the
3917: question is: Which package provides the
3918: <code class="filename">libIDL/IDL.h</code> header file?</p>
3919: <pre class="programlisting">
3920: <code class="prompt">$</code> echo ../../*/*idl*
3921: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
3922: <code class="prompt">$</code> echo ../../*/*IDL*
3923: ../../net/libIDL
3924: </pre>
3925: <p>Let's take the one from the second try. So I included the
3926: <code class="filename">../../net/libIDL/buildlink3.mk</code> file and tried
3927: again. But the error didn't change. After digging through some of the
3928: code, I concluded that the build process of the package was broken and
3929: couldn't have ever worked, but since the Mozilla source tree is quite
3930: large, I didn't want to fix it. So I added the following to the package
3931: <code class="filename">Makefile</code> and tried again:</p>
3932: <pre class="programlisting">
3933: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
3934: BUILDLINK_TRANSFORM+= -l:IDL:IDL-2
3935: </pre>
3936: <p>The latter line is needed because the package expects the library
3937: <code class="filename">libIDL.so</code>, but only
3938: <code class="filename">libIDL-2.so</code> is available. So I told the compiler
3939: wrapper to rewrite that on the fly.</p>
3940: <p>The next problem was related to a recent change of the FreeType
1.79 snj 3941: interface. I looked up in <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/seamonkey/README.html" target="_top"><code class="filename">www/seamonkey</code></a>
1.1 dsieger 3942: which patch files were relevant for this issue and copied them to the
3943: <code class="filename">patches</code> directory. Then I retried, fixed the
3944: patches so that they applied cleanly and retried again. This time,
3945: everything worked.</p>
3946: </div>
1.41 asau 3947: <div class="sect3">
1.1 dsieger 3948: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 3949: <a name="creating.nvu.inst"></a>10.2.1.3. Installing the package</h4></div></div></div>
1.1 dsieger 3950: <pre class="programlisting">
3951: <code class="prompt">$</code> bmake CHECK_FILES=no install
3952: [...]
3953: <code class="prompt">$</code> bmake print-PLIST >PLIST
3954: <code class="prompt">$</code> bmake deinstall
3955: <code class="prompt">$</code> bmake install
3956: </pre>
3957: </div>
3958: </div>
3959: </div>
3960: </div>
1.41 asau 3961: <div class="chapter">
1.1 dsieger 3962: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 3963: <a name="components"></a>Chapter 11. Package components - files, directories and contents</h2></div></div></div>
1.1 dsieger 3964: <div class="toc">
3965: <p><b>Table of Contents</b></p>
1.100 leot 3966: <dl class="toc">
1.23 wiz 3967: <dt><span class="sect1"><a href="#components.Makefile">11.1. <code class="filename">Makefile</code></a></span></dt>
3968: <dt><span class="sect1"><a href="#components.distinfo">11.2. <code class="filename">distinfo</code></a></span></dt>
1.6 rillig 3969: <dt><span class="sect1"><a href="#components.patches">11.3. patches/*</a></span></dt>
3970: <dd><dl>
3971: <dt><span class="sect2"><a href="#components.patch.structure">11.3.1. Structure of a single patch file</a></span></dt>
3972: <dt><span class="sect2"><a href="#components.patches.caveats">11.3.2. Creating patch files</a></span></dt>
3973: <dt><span class="sect2"><a href="#components.patches.sources">11.3.3. Sources where the patch files come from</a></span></dt>
3974: <dt><span class="sect2"><a href="#components.patches.guidelines">11.3.4. Patching guidelines</a></span></dt>
3975: <dt><span class="sect2"><a href="#components.patches.feedback">11.3.5. Feedback to the author</a></span></dt>
3976: </dl></dd>
3977: <dt><span class="sect1"><a href="#other-mandatory-files">11.4. Other mandatory files</a></span></dt>
3978: <dt><span class="sect1"><a href="#components.optional">11.5. Optional files</a></span></dt>
3979: <dd><dl>
3980: <dt><span class="sect2"><a href="#components.optional.bin">11.5.1. Files affecting the binary package</a></span></dt>
3981: <dt><span class="sect2"><a href="#components.optional.build">11.5.2. Files affecting the build process</a></span></dt>
3982: <dt><span class="sect2"><a href="#components.optional.none">11.5.3. Files affecting nothing at all</a></span></dt>
1.1 dsieger 3983: </dl></dd>
1.23 wiz 3984: <dt><span class="sect1"><a href="#work-dir">11.6. <code class="filename">work*</code></a></span></dt>
3985: <dt><span class="sect1"><a href="#files-dir">11.7. <code class="filename">files/*</code></a></span></dt>
1.1 dsieger 3986: </dl>
3987: </div>
3988: <p>Whenever you're preparing a package, there are a number of
3989: files involved which are described in the following
3990: sections.</p>
1.41 asau 3991: <div class="sect1">
1.1 dsieger 3992: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 3993: <a name="components.Makefile"></a>11.1. <code class="filename">Makefile</code>
1.1 dsieger 3994: </h2></div></div></div>
3995: <p>Building, installation and creation of a binary package are all
3996: controlled by the package's <code class="filename">Makefile</code>.
3997: The <code class="filename">Makefile</code> describes various things about
3998: a package, for example from where to get it, how to configure,
3999: build, and install it.</p>
4000: <p>A package <code class="filename">Makefile</code> contains several
4001: sections that describe the package.</p>
4002: <p>In the first section there are the following variables, which
4003: should appear exactly in the order given here. The order and
4004: grouping of the variables is mostly historical and has no further
4005: meaning.</p>
1.41 asau 4006: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4007: <li class="listitem"><p><code class="varname">DISTNAME</code> is the basename of the
1.1 dsieger 4008: distribution file to be downloaded from the package's
4009: website.</p></li>
1.23 wiz 4010: <li class="listitem"><p><code class="varname">PKGNAME</code> is the name of the
1.66 asau 4011: package, as used by pkgsrc. You need to provide it if
1.1 dsieger 4012: <code class="varname">DISTNAME</code> (which is the default) is not a good
1.66 asau 4013: name for the package in pkgsrc or <code class="varname">DISTNAME</code> is not
4014: provided (no distribution file is required). Usually it is the pkgsrc
1.1 dsieger 4015: directory name together with the version number. It must match the
4016: regular expression
4017: <code class="varname">^[A-Za-z0-9][A-Za-z0-9-_.+]*$</code>, that is, it
4018: starts with a letter or digit, and contains only letters, digits,
4019: dashes, underscores, dots and plus signs.</p></li>
1.23 wiz 4020: <li class="listitem">
1.1 dsieger 4021: <p><code class="varname">CATEGORIES</code> is a list of categories
4022: which the package fits in. You can choose any of the top-level
4023: directories of pkgsrc for it.</p>
4024: <p>Currently the following values are available for
4025: <code class="varname">CATEGORIES</code>. If more than
4026: one is used, they need to be separated by spaces:</p>
4027: <pre class="programlisting">
4028: archivers cross geography meta-pkgs security
4029: audio databases graphics misc shells
4030: benchmarks devel ham multimedia sysutils
4031: biology editors inputmethod net textproc
4032: cad emulators lang news time
4033: chat finance mail parallel wm
4034: comms fonts math pkgtools www
4035: converters games mbone print x11
4036: </pre>
4037: </li>
1.23 wiz 4038: <li class="listitem"><p><code class="varname">MASTER_SITES</code>,
1.1 dsieger 4039: <code class="varname">DYNAMIC_MASTER_SITES</code>,
4040: <code class="varname">DIST_SUBDIR</code>, <code class="varname">EXTRACT_SUFX</code>
4041: and <code class="varname">DISTFILES</code> are discussed in detail in
1.23 wiz 4042: <a class="xref" href="#build.fetch" title="17.5. The fetch phase">Section 17.5, “The <span class="emphasis"><em>fetch</em></span> phase”</a>.</p></li>
1.1 dsieger 4043: </ul></div>
4044: <p>The second section contains information about separately
4045: downloaded patches, if any.
4046: </p>
1.41 asau 4047: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.80 wiz 4048: <li class="listitem"><p><code class="varname">PATCHFILES</code>:
1.1 dsieger 4049: Name(s) of additional files that contain distribution patches.
4050: There is no default. pkgsrc will look for them at
4051: <code class="varname">PATCH_SITES</code>.
4052: They will automatically be uncompressed before patching if
4053: the names end with <code class="filename">.gz</code> or
4054: <code class="filename">.Z</code>.</p></li>
1.23 wiz 4055: <li class="listitem"><p><code class="varname">PATCH_SITES</code>:
1.1 dsieger 4056: Primary location(s) for distribution patch files (see
1.80 wiz 4057: <code class="varname">PATCHFILES</code> above) if not found locally.</p></li>
4058: <li class="listitem"><p><code class="varname">PATCH_DIST_STRIP</code>:
4059: an argument to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> that sets the pathname strip count to
4060: help find the correct files to patch. It defaults to
4061: <span class="command"><strong>-p0</strong></span>.</p></li>
1.1 dsieger 4062: </ul></div>
4063: <p>The third section contains the following variables.
4064: </p>
1.41 asau 4065: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4066: <li class="listitem"><p><code class="varname">MAINTAINER</code> is the email
1.14 jmcneill 4067: address of the person who feels responsible for this package,
4068: and who is most likely to look at problems or questions regarding
1.79 snj 4069: this package which have been reported with <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a>.
1.14 jmcneill 4070: Other developers may contact the <code class="varname">MAINTAINER</code>
4071: before making changes to the package, but are not required to
4072: do so. When packaging a new program, set <code class="varname">MAINTAINER</code>
4073: to yourself. If you really can't maintain the package for future
4074: updates, set it to
1.10 hubertf 4075: <code class="email"><<a class="email" href="mailto:pkgsrc-users@NetBSD.org">pkgsrc-users@NetBSD.org</a>></code>.</p></li>
1.23 wiz 4076: <li class="listitem"><p><code class="varname">OWNER</code> should be used instead
1.14 jmcneill 4077: of <code class="varname">MAINTAINER</code> when you do not want other
4078: developers to update or change the package without contacting
4079: you first. A package Makefile should contain one of
4080: <code class="varname">MAINTAINER</code> or <code class="varname">OWNER</code>, but
4081: not both. </p></li>
1.23 wiz 4082: <li class="listitem"><p><code class="varname">HOMEPAGE</code> is a URL where users can
1.1 dsieger 4083: find more information about the package.</p></li>
1.23 wiz 4084: <li class="listitem"><p><code class="varname">COMMENT</code> is a one-line
1.1 dsieger 4085: description of the package (should not include the package
4086: name).</p></li>
4087: </ul></div>
4088: <p>Other variables that affect the build:
4089: </p>
1.41 asau 4090: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1.1 dsieger 4091: <p><code class="varname">WRKSRC</code>: The directory where the
4092: interesting distribution files of the package are found. The
4093: default is <code class="filename">${WRKDIR}/${DISTNAME}</code>, which
4094: works for most packages.</p>
4095: <p>If a package doesn't create a subdirectory for itself
4096: (most GNU software does, for instance), but extracts itself in
4097: the current directory, you should set
4098: <code class="varname">WRKSRC=${WRKDIR}</code>.</p>
4099: <p>If a package doesn't create a subdirectory with the
4100: name of <code class="varname">DISTNAME</code> but some different name,
4101: set <code class="varname">WRKSRC</code> to point to the proper name in
4102: <code class="filename">${WRKDIR}</code>, for example
4103: <code class="varname">WRKSRC=${WRKDIR}/${DISTNAME}/unix</code>. See
1.79 snj 4104: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/tcl/README.html" target="_top"><code class="filename">lang/tcl</code></a> and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/tk/README.html" target="_top"><code class="filename">x11/tk</code></a> for other examples.</p>
1.1 dsieger 4105: <p>The name of the working directory created by pkgsrc is
4106: taken from the <code class="varname">WRKDIR_BASENAME</code>
4107: variable. By default, its value is
4108: <code class="filename">work</code>. If you want to use the same
4109: pkgsrc tree for building different kinds of binary packages,
4110: you can change the variable according to your needs. Two
4111: other variables handle common cases of setting
4112: <code class="varname">WRKDIR_BASENAME</code> individually. If
4113: <code class="varname">OBJHOSTNAME</code> is defined in
1.10 hubertf 4114: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, the first component of
1.1 dsieger 4115: the host's name is attached to the directory name. If
4116: <code class="varname">OBJMACHINE</code> is defined, the platform name
4117: is attached, which might look like
4118: <code class="filename">work.i386</code> or
4119: <code class="filename">work.sparc</code>.</p>
4120: </li></ul></div>
4121: <p>Please pay attention to the following gotchas:</p>
1.41 asau 4122: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4123: <li class="listitem"><p>Add <code class="varname">MANCOMPRESSED</code> if man pages are
1.1 dsieger 4124: installed in compressed form by the package. For packages using
4125: BSD-style makefiles which honor MANZ, there is
4126: <code class="varname">MANCOMPRESSED_IF_MANZ</code>.</p></li>
1.23 wiz 4127: <li class="listitem"><p>Replace <code class="filename">/usr/local</code> with
4128: <span class="quote">“<span class="quote">${PREFIX}</span>”</span> in all files (see patches,
1.1 dsieger 4129: below).</p></li>
1.23 wiz 4130: <li class="listitem"><p>If the package installs any info files, see <a class="xref" href="#faq.info-files" title="19.6.7. Packages installing info files">Section 19.6.7, “Packages installing info files”</a>.</p></li>
1.1 dsieger 4131: </ul></div>
4132: </div>
1.41 asau 4133: <div class="sect1">
1.1 dsieger 4134: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4135: <a name="components.distinfo"></a>11.2. <code class="filename">distinfo</code>
1.1 dsieger 4136: </h2></div></div></div>
4137: <p>The <code class="filename">distinfo</code> file contains the message
4138: digest, or checksum, of each distfile needed for the package. This
4139: ensures that the distfiles retrieved from the Internet have not been
4140: corrupted during transfer or altered by a malign force to introduce
4141: a security hole. Due to recent rumor about weaknesses of digest
4142: algorithms, all distfiles are protected using both SHA1 and RMD160
4143: message digests, as well as the file size.</p>
4144: <p>The <code class="filename">distinfo</code> file also contains the
4145: checksums for all the patches found in the
1.10 hubertf 4146: <code class="filename">patches</code> directory (see <a class="xref" href="#components.patches" title="11.3. patches/*">Section 11.3, “patches/*”</a>).</p>
1.1 dsieger 4147: <p>To regenerate the <code class="filename">distinfo</code> file, use the
1.10 hubertf 4148: <span class="command"><strong>make makedistinfo</strong></span> or <span class="command"><strong>make mdi</strong></span>
1.1 dsieger 4149: command.</p>
4150: <p>Some packages have different sets of distfiles depending on
1.79 snj 4151: the platform, for example <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/openjdk7/README.html" target="_top"><code class="filename">lang/openjdk7</code></a>. These are kept in the same
1.1 dsieger 4152: <code class="filename">distinfo</code> file and care should be taken when
4153: upgrading such a package to ensure distfile information is not
4154: lost.</p>
4155: </div>
1.41 asau 4156: <div class="sect1">
1.1 dsieger 4157: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4158: <a name="components.patches"></a>11.3. patches/*</h2></div></div></div>
1.1 dsieger 4159: <p>Many packages still don't work out-of-the box on the various
4160: platforms that are supported by pkgsrc. Therefore, a number of custom
4161: patch files are needed to make the package work. These patch files are
4162: found in the <code class="filename">patches/</code> directory.</p>
4163: <p>In the <span class="emphasis"><em>patch</em></span> phase, these patches are
4164: applied to the files in <code class="varname">WRKSRC</code> directory after
1.10 hubertf 4165: extracting them, in <a class="ulink" href="http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_13_03" target="_top">alphabetic
1.24 wiz 4166: order</a>.</p>
1.41 asau 4167: <div class="sect2">
1.1 dsieger 4168: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4169: <a name="components.patch.structure"></a>11.3.1. Structure of a single patch file</h3></div></div></div>
1.1 dsieger 4170: <p>The <code class="filename">patch-*</code> files should be in
1.10 hubertf 4171: <span class="command"><strong>diff -bu</strong></span> format, and apply without a fuzz to avoid
1.1 dsieger 4172: problems. (To force patches to apply with fuzz you can set
4173: <code class="varname">PATCH_FUZZ_FACTOR=-F2</code>). Furthermore, each patch
4174: should contain only changes for a single file, and no file should be
4175: patched by more than one patch file. This helps to keep future
4176: modifications simple.</p>
4177: <p>Each patch file is structured as follows: In the first line,
4178: there is the RCS Id of the patch itself. The second line should be
4179: empty for aesthetic reasons. After that, there should be a comment for
4180: each change that the patch does. There are a number of standard
4181: cases:</p>
1.41 asau 4182: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4183: <li class="listitem"><p>Patches for commonly known vulnerabilities should
1.1 dsieger 4184: mention the vulnerability ID (CAN, CVE).</p></li>
1.23 wiz 4185: <li class="listitem"><p>Patches that change source code should mention the
1.1 dsieger 4186: platform and other environment (for example, the compiler) that the
4187: patch is needed for.</p></li>
4188: </ul></div>
1.24 wiz 4189: <p>In all, the patch should be commented so that any
1.1 dsieger 4190: developer who knows the code of the application can make some use of
4191: the patch. Special care should be taken for the upstream developers,
4192: since we generally want that they accept our patches, so we have less
4193: work in the future.</p>
4194: </div>
1.41 asau 4195: <div class="sect2">
1.1 dsieger 4196: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4197: <a name="components.patches.caveats"></a>11.3.2. Creating patch files</h3></div></div></div>
1.1 dsieger 4198: <p>One important thing to mention is to pay attention that no RCS
4199: IDs get stored in the patch files, as these will cause problems when
4200: later checked into the NetBSD CVS tree. Use the
1.79 snj 4201: <span class="command"><strong>pkgdiff</strong></span> command from the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> package to avoid these
1.1 dsieger 4202: problems.</p>
4203: <p>For even more automation, we recommend using
1.10 hubertf 4204: <span class="command"><strong>mkpatches</strong></span> from the same package to make a
1.1 dsieger 4205: whole set of patches. You just have to backup files before you
4206: edit them to <code class="filename">filename.orig</code>, e.g. with
1.10 hubertf 4207: <span class="command"><strong>cp -p filename filename.orig</strong></span> or, easier, by
4208: using <span class="command"><strong>pkgvi</strong></span> again from the same package. If
1.1 dsieger 4209: you upgrade a package this way, you can easily compare the new
4210: set of patches with the previously existing one with
1.24 wiz 4211: <span class="command"><strong>patchdiff</strong></span>. The files in <code class="filename">patches</code>
4212: are replaced by new files, so carefully check if you want to take all
4213: the changes.</p>
1.1 dsieger 4214: <p>When you have finished a package, remember to generate
1.10 hubertf 4215: the checksums for the patch files by using the <span class="command"><strong>make
1.23 wiz 4216: makepatchsum</strong></span> command, see <a class="xref" href="#components.distinfo" title="11.2. distinfo">Section 11.2, “<code class="filename">distinfo</code>”</a>.</p>
1.1 dsieger 4217: <p>When adding a patch that corrects a problem in the
4218: distfile (rather than e.g. enforcing pkgsrc's view of where
4219: man pages should go), send the patch as a bug report to the
4220: maintainer. This benefits non-pkgsrc users of the package,
4221: and usually makes it possible to remove the patch in future
4222: version.</p>
1.2 rillig 4223: <p>The file names of the patch files are usually of the form
1.24 wiz 4224: <code class="filename">patch-<em class="replaceable"><code>path_to_file__with__underscores.c</code></em></code>.
4225: Many packages still use the previous convention
4226: <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>,
4227: but new patches should be of the form containing the filename.
1.79 snj 4228: <span class="command"><strong>mkpatches</strong></span> included in <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a> takes care of the name
1.24 wiz 4229: automatically.</p>
1.1 dsieger 4230: </div>
1.41 asau 4231: <div class="sect2">
1.1 dsieger 4232: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4233: <a name="components.patches.sources"></a>11.3.3. Sources where the patch files come from</h3></div></div></div>
1.1 dsieger 4234: <p>If you want to share patches between multiple packages
4235: in pkgsrc, e.g. because they use the same distfiles, set
4236: <code class="varname">PATCHDIR</code> to the path where the patch files
4237: can be found, e.g.:</p>
4238: <pre class="programlisting">
4239: PATCHDIR= ${.CURDIR}/../xemacs/patches
4240: </pre>
4241: <p>Patch files that are distributed by the author or other
4242: maintainers can be listed in
4243: <code class="varname">PATCHFILES</code>.</p>
4244: <p>If it is desired to store any patches that should not be
4245: committed into pkgsrc, they can be kept outside the pkgsrc
4246: tree in the <code class="filename">$LOCALPATCHES</code> directory. The
4247: directory tree there is expected to have the same
1.23 wiz 4248: <span class="quote">“<span class="quote">category/package</span>”</span> structure as pkgsrc, and
1.1 dsieger 4249: patches are expected to be stored inside these dirs (also
4250: known as <code class="filename">$LOCALPATCHES/$PKGPATH</code>). For
4251: example, if you want to keep a private patch for
4252: <code class="filename">pkgsrc/graphics/png</code>, keep it in
4253: <code class="filename">$LOCALPATCHES/graphics/png/mypatch</code>. All
4254: files in the named directory are expected to be patch files,
4255: and <span class="emphasis"><em>they are applied after pkgsrc patches are
4256: applied</em></span>.</p>
4257: </div>
1.41 asau 4258: <div class="sect2">
1.1 dsieger 4259: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4260: <a name="components.patches.guidelines"></a>11.3.4. Patching guidelines</h3></div></div></div>
1.1 dsieger 4261: <p>When fixing a portability issue in the code do not use
4262: preprocessor magic to check for the current operating system nor
4263: platform. Doing so hurts portability to other platforms because
4264: the OS-specific details are not abstracted appropriately.</p>
4265: <p>The general rule to follow is: instead of checking for the
4266: operating system the application is being built on, check for the
4267: specific <span class="emphasis"><em>features</em></span> you need. For example,
4268: instead of assuming that kqueue is available under NetBSD and
4269: using the <code class="varname">__NetBSD__</code> macro to conditionalize
1.14 jmcneill 4270: kqueue support, add a check that detects kqueue itself —
1.1 dsieger 4271: yes, this generally involves patching the
1.10 hubertf 4272: <span class="command"><strong>configure</strong></span> script. There is absolutely nothing
1.1 dsieger 4273: that prevents some OSes from adopting interfaces from other OSes
4274: (e.g. Linux implementing kqueue), something that the above checks
4275: cannot take into account.</p>
4276: <p>Of course, checking for features generally involves more
4277: work on the developer's side, but the resulting changes are
4278: cleaner and there are chances they will work on many other
4279: platforms. Not to mention that there are higher chances of being
4280: later integrated into the mainstream sources. Remember:
4281: <span class="emphasis"><em>It doesn't work unless it is right!</em></span></p>
4282: <p>Some typical examples:</p>
4283: <div class="table">
1.6 rillig 4284: <a name="patch-examples"></a><p class="title"><b>Table 11.1. Patching examples</b></p>
1.1 dsieger 4285: <div class="table-contents"><table summary="Patching examples" border="1">
4286: <colgroup>
4287: <col>
4288: <col>
4289: <col>
4290: </colgroup>
4291: <thead><tr>
4292: <th>Where</th>
4293: <th>Incorrect</th>
4294: <th>Correct</th>
4295: </tr></thead>
4296: <tbody>
4297: <tr>
4298: <td>configure script</td>
4299: <td>
4300: <pre class="programlisting">
4301: case ${target_os} in
4302: netbsd*) have_kvm=yes ;;
4303: *) have_kvm=no ;;
4304: esac
4305: </pre>
4306: </td>
4307: <td>
4308: <pre class="programlisting">
4309: AC_CHECK_LIB(kvm, kvm_open, have_kvm=yes, have_kvm=no)
4310: </pre>
4311: </td>
4312: </tr>
4313: <tr>
4314: <td>C source file</td>
4315: <td>
4316: <pre class="programlisting">
4317: #if defined(__NetBSD__)
4318: # include <sys/event.h>
4319: #endif
4320: </pre>
4321: </td>
4322: <td>
4323: <pre class="programlisting">
4324: #if defined(HAVE_SYS_EVENT_H)
4325: # include <sys/event.h>
4326: #endif
4327: </pre>
4328: </td>
4329: </tr>
4330: <tr>
4331: <td>C source file</td>
4332: <td>
4333: <pre class="programlisting">
4334: int
4335: monitor_file(...)
4336: {
4337: #if defined(__NetBSD__)
4338: int fd = kqueue();
4339: ...
4340: #else
4341: ...
4342: #endif
4343: }
4344: </pre>
4345: </td>
4346: <td>
4347: <pre class="programlisting">
4348: int
4349: monitor_file(...)
4350: {
4351: #if defined(HAVE_KQUEUE)
4352: int fd = kqueue();
4353: ...
4354: #else
4355: ...
4356: #endif
4357: }
4358: </pre>
4359: </td>
4360: </tr>
4361: </tbody>
4362: </table></div>
4363: </div>
4364: <br class="table-break"><p>For more information, please read the <span class="emphasis"><em>Making
1.10 hubertf 4365: packager-friendly software</em></span> article (<a class="ulink" href="http://www.onlamp.com/pub/a/onlamp/2005/03/31/packaging.html" target="_top">part
4366: 1</a>, <a class="ulink" href="http://www.oreillynet.com/pub/a/onlamp/2005/04/28/packaging2.html" target="_top">part
1.1 dsieger 4367: 2</a>). It summarizes multiple details on how to make
4368: software easier to package; all the suggestions in it were
4369: collected from our experience in pkgsrc work, so they are possibly
4370: helpful when creating patches too.</p>
4371: </div>
1.41 asau 4372: <div class="sect2">
1.1 dsieger 4373: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4374: <a name="components.patches.feedback"></a>11.3.5. Feedback to the author</h3></div></div></div>
1.1 dsieger 4375: <p>Always, always, <span class="strong"><strong>always</strong></span>
4376: feed back any <span class="emphasis"><em>portability fixes</em></span> or
4377: improvements you do to a package to the mainstream developers.
4378: This is the only way to get their attention on portability issues
4379: and to ensure that future versions can be built out-of-the box on
4380: NetBSD. Furthermore, any user that gets newer distfiles will get
4381: the fixes straight from the packaged code.</p>
4382: <p>This generally involves cleaning up the patches
4383: (because sometimes the patches that are
1.40 wiz 4384: added to pkgsrc are quick hacks), filing bug reports in the
1.1 dsieger 4385: appropriate trackers for the projects and working with the
4386: mainstream authors to accept your changes. It is
4387: <span class="emphasis"><em>extremely important</em></span> that you do it so that
4388: the packages in pkgsrc are kept simple and thus further changes
4389: can be done without much hassle.</p>
1.24 wiz 4390: <p>When you have done this, please add a URL to the upstream
4391: bug report to the patch comment.</p>
1.1 dsieger 4392: <p>Support the idea of free software!</p>
4393: </div>
4394: </div>
1.41 asau 4395: <div class="sect1">
1.1 dsieger 4396: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4397: <a name="other-mandatory-files"></a>11.4. Other mandatory files</h2></div></div></div>
1.41 asau 4398: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 4399: <dt><span class="term"><code class="filename">DESCR</code></span></dt>
4400: <dd><p>A multi-line description of the piece of software. This should include
4401: any credits where they are due. Please bear in mind that others do not
4402: share your sense of humour (or spelling idiosyncrasies), and that others
4403: will read everything that you write here.</p></dd>
4404: <dt><span class="term"><code class="filename">PLIST</code></span></dt>
4405: <dd><p>This file governs the files that are installed on your
4406: system: all the binaries, manual pages, etc. There are other
4407: directives which may be entered in this file, to control the
4408: creation and deletion of directories, and the location of
1.10 hubertf 4409: inserted files. See <a class="xref" href="#plist" title="Chapter 13. PLIST issues">Chapter 13, <i>PLIST issues</i></a> for more
1.1 dsieger 4410: information.</p></dd>
4411: </dl></div>
4412: </div>
1.41 asau 4413: <div class="sect1">
1.1 dsieger 4414: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4415: <a name="components.optional"></a>11.5. Optional files</h2></div></div></div>
1.41 asau 4416: <div class="sect2">
1.1 dsieger 4417: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4418: <a name="components.optional.bin"></a>11.5.1. Files affecting the binary package</h3></div></div></div>
1.41 asau 4419: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 4420: <dt><span class="term"><code class="filename">INSTALL</code></span></dt>
1.28 wiz 4421: <dd>
1.79 snj 4422: <p>This shell script is invoked twice by <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>.
1.1 dsieger 4423: First time after package extraction and before files are
4424: moved in place, the second time after the files to install
4425: are moved in place. This can be used to do any custom
4426: procedures not possible with @exec commands in
1.79 snj 4427: <code class="filename">PLIST</code>. See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> and
4428: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-5.0.1+i386"><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="15.1. Files and directories outside the installation prefix">Section 15.1, “Files and directories outside the installation prefix”</a>.
1.28 wiz 4429: Please note that you can modify variables in it easily by using
4430: <code class="varname">FILES_SUBST</code> in the package's
4431: <code class="filename">Makefile</code>:</p>
4432: <pre class="programlisting">
4433: FILES_SUBST+= SOMEVAR="somevalue"
4434: </pre>
4435: <p>replaces "@SOMEVAR@" with <span class="quote">“<span class="quote">somevalue</span>”</span> in the
4436: <code class="filename">INSTALL</code>. By default, substitution is
4437: performed for <code class="varname">PREFIX</code>,
4438: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
4439: <code class="varname">VARBASE</code>, and a few others, type
4440: <span class="command"><strong>make help topic=FILES_SUBST</strong></span> for a
4441: complete list.</p>
4442: </dd>
1.1 dsieger 4443: <dt><span class="term"><code class="filename">DEINSTALL</code></span></dt>
4444: <dd><p>This script is executed before and after any files are removed. It is
4445: this script's responsibility to clean up any additional messy details
4446: around the package's installation, since all pkg_delete knows is how to
4447: delete the files created in the original distribution.
1.79 snj 4448: See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
4449: and <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for more information.
1.28 wiz 4450: The same methods to replace variables can be used as for
4451: the <code class="filename">INSTALL</code> file.</p></dd>
1.1 dsieger 4452: <dt><span class="term"><code class="filename">MESSAGE</code></span></dt>
4453: <dd>
4454: <p>This file is displayed after installation of the package.
4455: Useful for things like legal notices on almost-free
4456: software and hints for updating config files after
4457: installing modules for apache, PHP etc.
4458: Please note that you can modify variables in it easily by using
4459: <code class="varname">MESSAGE_SUBST</code> in the package's
4460: <code class="filename">Makefile</code>:</p>
4461: <pre class="programlisting">
4462: MESSAGE_SUBST+= SOMEVAR="somevalue"
4463: </pre>
1.23 wiz 4464: <p>replaces "${SOMEVAR}" with <span class="quote">“<span class="quote">somevalue</span>”</span> in
1.1 dsieger 4465: <code class="filename">MESSAGE</code>. By default, substitution is
4466: performed for <code class="varname">PKGNAME</code>,
4467: <code class="varname">PKGBASE</code>, <code class="varname">PREFIX</code>,
1.99 sevan 4468: <code class="varname">LOCALBASE</code>, <code class="varname">X11BASE</code>,
1.1 dsieger 4469: <code class="varname">PKG_SYSCONFDIR</code>,
4470: <code class="varname">ROOT_GROUP</code>, and
1.16 jnemeth 4471: <code class="varname">ROOT_USER</code>.</p>
1.1 dsieger 4472: <p>You can display a different or additional files by
4473: setting the <code class="varname">MESSAGE_SRC</code> variable. Its
4474: default is <code class="filename">MESSAGE</code>, if the file
4475: exists.</p>
4476: </dd>
4477: <dt><span class="term"><code class="filename">ALTERNATIVES</code></span></dt>
1.66 asau 4478: <dd>
4479: <p>This file is used by the alternatives framework.
4480: It creates, configures, and destroys generic wrappers used to
4481: run programs with similar interfaces.
4482: See pkg_alternatives(8) from pkgtools/pkg_alternatives
4483: for more information.</p>
4484: <p>Each line of the file contains two filenames, first
4485: the wrapper and then the alternative provided by the package.
4486: Both paths are relative to <code class="varname">PREFIX</code>.</p>
4487: </dd>
1.1 dsieger 4488: </dl></div>
4489: </div>
1.41 asau 4490: <div class="sect2">
1.1 dsieger 4491: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4492: <a name="components.optional.build"></a>11.5.2. Files affecting the build process</h3></div></div></div>
1.41 asau 4493: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 4494: <dt><span class="term"><code class="filename">Makefile.common</code></span></dt>
4495: <dd><p>This file contains arbitrary things that could
4496: also go into a <code class="filename">Makefile</code>, but its purpose is
4497: to be used by more than one package. This file should only be
4498: used when the packages that will use the file are known in
4499: advance. For other purposes it is often better to write a
4500: <code class="filename">*.mk</code> file and give it a good name that
4501: describes what it does.</p></dd>
4502: <dt><span class="term"><code class="filename">buildlink3.mk</code></span></dt>
4503: <dd><p>This file contains the dependency information
1.10 hubertf 4504: for the buildlink3 framework (see <a class="xref" href="#buildlink" title="Chapter 14. Buildlink methodology">Chapter 14, <i>Buildlink methodology</i></a>).</p></dd>
1.1 dsieger 4505: <dt><span class="term"><code class="filename">hacks.mk</code></span></dt>
4506: <dd><p>This file contains workarounds for compiler bugs
4507: and similar things. It is included automatically by the pkgsrc
4508: infrastructure, so you don't need an extra
4509: <code class="literal">.include</code> line for
4510: it.</p></dd>
4511: <dt><span class="term"><code class="filename">options.mk</code></span></dt>
4512: <dd><p>This file contains the code for the
1.10 hubertf 4513: package-specific options (see <a class="xref" href="#options" title="Chapter 16. Options handling">Chapter 16, <i>Options handling</i></a>) that can be
1.1 dsieger 4514: selected by the user. If a package has only one or two options,
4515: it is equally acceptable to put the code directly into the
4516: <code class="filename">Makefile</code>.</p></dd>
4517: </dl></div>
4518: </div>
1.41 asau 4519: <div class="sect2">
1.1 dsieger 4520: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4521: <a name="components.optional.none"></a>11.5.3. Files affecting nothing at all</h3></div></div></div>
1.41 asau 4522: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 4523: <dt><span class="term"><code class="filename">README*</code></span></dt>
4524: <dd><p>These files do not take place in the creation of
4525: a package and thus are purely informative to the package
4526: developer.</p></dd>
4527: <dt><span class="term"><code class="filename">TODO</code></span></dt>
4528: <dd><p>This file contains things that need to be done
4529: to make the package even
4530: better.</p></dd>
4531: </dl></div>
4532: </div>
4533: </div>
1.41 asau 4534: <div class="sect1">
1.1 dsieger 4535: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4536: <a name="work-dir"></a>11.6. <code class="filename">work*</code>
1.1 dsieger 4537: </h2></div></div></div>
1.10 hubertf 4538: <p>When you type <span class="command"><strong>make</strong></span>, the distribution files are
1.1 dsieger 4539: unpacked into the directory denoted by
4540: <code class="varname">WRKDIR</code>. It can be removed by running
1.10 hubertf 4541: <span class="command"><strong>make clean</strong></span>. Besides the sources, this
1.1 dsieger 4542: directory is also used to keep various timestamp files.
4543: The directory gets <span class="emphasis"><em>removed completely</em></span> on clean.
4544: The default is <code class="filename">${.CURDIR}/work</code>
4545: or <code class="filename">${.CURDIR}/work.${MACHINE_ARCH}</code>
4546: if <code class="varname">OBJMACHINE</code> is set.</p>
4547: </div>
1.41 asau 4548: <div class="sect1">
1.1 dsieger 4549: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4550: <a name="files-dir"></a>11.7. <code class="filename">files/*</code>
1.1 dsieger 4551: </h2></div></div></div>
4552: <p>If you have any files that you wish to be placed in the package prior
4553: to configuration or building, you could place these files here and use
1.10 hubertf 4554: a <span class="command"><strong>${CP}</strong></span> command in the
1.23 wiz 4555: <span class="quote">“<span class="quote">pre-configure</span>”</span> target to achieve
1.1 dsieger 4556: this. Alternatively, you could simply diff the file against
4557: <code class="filename">/dev/null</code> and use the patch mechanism to manage
4558: the creation of this file.</p>
4559: <p>If you want to share files in this way with other
4560: packages, set the <code class="varname">FILESDIR</code> variable to point
4561: to the other package's <code class="filename">files</code> directory,
4562: e.g.:</p>
4563: <pre class="programlisting">
4564: FILESDIR=${.CURDIR}/../xemacs/files
4565: </pre>
4566: </div>
4567: </div>
1.41 asau 4568: <div class="chapter">
1.1 dsieger 4569: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 4570: <a name="makefile"></a>Chapter 12. Programming in <code class="filename">Makefile</code>s</h2></div></div></div>
1.1 dsieger 4571: <div class="toc">
4572: <p><b>Table of Contents</b></p>
1.100 leot 4573: <dl class="toc">
1.6 rillig 4574: <dt><span class="sect1"><a href="#makefile.style">12.1. Caveats</a></span></dt>
1.23 wiz 4575: <dt><span class="sect1"><a href="#makefile.variables">12.2. <code class="filename">Makefile</code> variables</a></span></dt>
1.6 rillig 4576: <dd><dl><dt><span class="sect2"><a href="#makefile.variables.names">12.2.1. Naming conventions</a></span></dt></dl></dd>
4577: <dt><span class="sect1"><a href="#makefile.code">12.3. Code snippets</a></span></dt>
4578: <dd><dl>
4579: <dt><span class="sect2"><a href="#adding-to-list">12.3.1. Adding things to a list</a></span></dt>
4580: <dt><span class="sect2"><a href="#converting-internal-to-external">12.3.2. Converting an internal list into an external list</a></span></dt>
4581: <dt><span class="sect2"><a href="#passing-variable-to-shell">12.3.3. Passing variables to a shell command</a></span></dt>
4582: <dt><span class="sect2"><a href="#quoting-guideline">12.3.4. Quoting guideline</a></span></dt>
4583: <dt><span class="sect2"><a href="#bsd-make-bug-workaround">12.3.5. Workaround for a bug in BSD Make</a></span></dt>
1.1 dsieger 4584: </dl></dd>
4585: </dl>
4586: </div>
4587: <p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments,
4588: each of which forms a well-defined part of the pkgsrc system. Using
1.79 snj 4589: the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a programming language for a big system
1.1 dsieger 4590: like pkgsrc requires some discipline to keep the code correct and
4591: understandable.</p>
4592: <p>The basic ingredients for <code class="filename">Makefile</code>
4593: programming are variables (which are actually macros) and shell
4594: commands. Among these shell commands may even be more complex ones
1.79 snj 4595: like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?awk+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make sure that every shell command runs
1.1 dsieger 4596: as intended it is necessary to quote all variables correctly when they
4597: are used.</p>
4598: <p>This chapter describes some patterns, that appear quite often in
4599: <code class="filename">Makefile</code>s, including the pitfalls that come along
4600: with them.</p>
1.41 asau 4601: <div class="sect1">
1.1 dsieger 4602: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4603: <a name="makefile.style"></a>12.1. Caveats</h2></div></div></div>
1.41 asau 4604: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1.1 dsieger 4605: <p>When you are creating a file as a
4606: target of a rule, always write the data to a temporary file first
4607: and finally rename that file. Otherwise there might occur an error
4608: in the middle of generating the file, and when the user runs
1.79 snj 4609: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> for the second time, the file exists and will not be
1.1 dsieger 4610: regenerated properly. Example:</p>
4611: <pre class="programlisting">
4612: wrong:
4613: @echo "line 1" > ${.TARGET}
4614: @echo "line 2" >> ${.TARGET}
4615: @false
4616:
4617: correct:
4618: @echo "line 1" > ${.TARGET}.tmp
4619: @echo "line 2" >> ${.TARGET}.tmp
4620: @false
4621: @mv ${.TARGET}.tmp ${.TARGET}
4622: </pre>
1.10 hubertf 4623: <p>When you run <span class="command"><strong>make wrong</strong></span> twice, the file
1.1 dsieger 4624: <code class="filename">wrong</code> will exist, although there was an error
1.10 hubertf 4625: message in the first run. On the other hand, running <span class="command"><strong>make
1.1 dsieger 4626: correct</strong></span> gives an error message twice, as expected.</p>
1.79 snj 4627: <p>You might remember that <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> sometimes removes
1.1 dsieger 4628: <code class="literal">${.TARGET}</code> in case of error, but this only
4629: happens when it is interrupted, for example by pressing
4630: <code class="literal">^C</code>. This does <span class="emphasis"><em>not</em></span> happen
1.79 snj 4631: when one of the commands fails (like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?false+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">false</span>(1)</span></a> above).</p>
1.1 dsieger 4632: </li></ul></div>
4633: </div>
1.41 asau 4634: <div class="sect1">
1.1 dsieger 4635: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4636: <a name="makefile.variables"></a>12.2. <code class="filename">Makefile</code> variables</h2></div></div></div>
1.1 dsieger 4637: <p><code class="filename">Makefile</code> variables contain strings that
4638: can be processed using the five operators ``='', ``+='', ``?='',
1.79 snj 4639: ``:='', and ``!='', which are described in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man
1.1 dsieger 4640: page.</p>
4641: <p>When a variable's value is parsed from a
4642: <code class="filename">Makefile</code>, the hash character ``#'' and the
4643: backslash character ``\'' are handled specially. If a backslash is
4644: followed by a newline, any whitespace immediately in front of the
4645: backslash, the backslash, the newline, and any whitespace
4646: immediately behind the newline are replaced with a single space. A
4647: backslash character and an immediately following hash character are
4648: replaced with a single hash character. Otherwise, the backslash is
4649: passed as is. In a variable assignment, any hash character that is
4650: not preceded by a backslash starts a comment that continues upto the
4651: end of the logical line.</p>
4652: <p><span class="emphasis"><em>Note:</em></span> Because of this parsing algorithm
4653: the only way to create a variable consisting of a single backslash
4654: is using the ``!='' operator, for example: <code class="varname">BACKSLASH!=echo "\\"</code>.</p>
4655: <p>So far for defining variables. The other thing you can do with
4656: variables is evaluating them. A variable is evaluated when it is
4657: part of the right side of the ``:='' or the ``!='' operator, or
4658: directly before executing a shell command which the variable is part
1.79 snj 4659: of. In all other cases, <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> performs lazy evaluation, that
1.1 dsieger 4660: is, variables are not evaluated until there's no other way. The
4661: ``modifiers'' mentioned in the man page also evaluate the
4662: variable.</p>
4663: <p>Some of the modifiers split the string into words and then
4664: operate on the words, others operate on the string as a whole. When
4665: a string is split into words, it is split as you would expect
1.79 snj 4666: it from <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sh+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span></a>.</p>
1.14 jmcneill 4667: <p>No rule without exception—the <span class="command"><strong>.for</strong></span>
1.1 dsieger 4668: loop does not follow the shell quoting rules but splits at sequences
4669: of whitespace.</p>
4670: <p>There are several types of variables that should be handled
4671: differently. Strings and two types of lists.</p>
1.41 asau 4672: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4673: <li class="listitem"><p><span class="emphasis"><em>Strings</em></span> can contain arbitrary
1.1 dsieger 4674: characters. Nevertheless, you should restrict yourself to only
4675: using printable characters. Examples are
4676: <code class="varname">PREFIX</code> and
4677: <code class="varname">COMMENT</code>.</p></li>
1.23 wiz 4678: <li class="listitem"><p><span class="emphasis"><em>Internal lists</em></span> are lists that
1.1 dsieger 4679: are never exported to any shell command. Their elements are
4680: separated by whitespace. Therefore, the elements themselves cannot
4681: have embedded whitespace. Any other characters are allowed.
1.10 hubertf 4682: Internal lists can be used in <span class="command"><strong>.for</strong></span> loops.
1.1 dsieger 4683: Examples are <code class="varname">DEPENDS</code> and
4684: <code class="varname">BUILD_DEPENDS</code>.</p></li>
1.23 wiz 4685: <li class="listitem"><p><span class="emphasis"><em>External lists</em></span> are lists that
1.1 dsieger 4686: may be exported to a shell command. Their elements can contain any
4687: characters, including whitespace. That's why they cannot be used
1.10 hubertf 4688: in <span class="command"><strong>.for</strong></span> loops. Examples are
1.1 dsieger 4689: <code class="varname">DISTFILES</code> and
4690: <code class="varname">MASTER_SITES</code>.</p></li>
4691: </ul></div>
1.41 asau 4692: <div class="sect2">
1.1 dsieger 4693: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4694: <a name="makefile.variables.names"></a>12.2.1. Naming conventions</h3></div></div></div>
1.41 asau 4695: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4696: <li class="listitem"><p>All variable names starting with an underscore
1.1 dsieger 4697: are reserved for use by the pkgsrc infrastructure. They shall
4698: not be used by package
4699: <code class="filename">Makefile</code>s.</p></li>
1.23 wiz 4700: <li class="listitem"><p>In <span class="command"><strong>.for</strong></span> loops you should use
1.1 dsieger 4701: lowercase variable names for the iteration
4702: variables.</p></li>
1.23 wiz 4703: <li class="listitem"><p>All list variables should have a ``plural''
1.1 dsieger 4704: name, e.g. <code class="varname">PKG_OPTIONS</code> or
4705: <code class="varname">DISTFILES</code>.</p></li>
4706: </ul></div>
4707: </div>
4708: </div>
1.41 asau 4709: <div class="sect1">
1.1 dsieger 4710: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4711: <a name="makefile.code"></a>12.3. Code snippets</h2></div></div></div>
1.1 dsieger 4712: <p>This section presents you with some code snippets you should
4713: use in your own code. If you don't find anything appropriate here,
4714: you should test your code and add it here.</p>
1.41 asau 4715: <div class="sect2">
1.1 dsieger 4716: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4717: <a name="adding-to-list"></a>12.3.1. Adding things to a list</h3></div></div></div>
1.1 dsieger 4718: <pre class="programlisting">
4719: STRING= foo * bar `date`
4720: INT_LIST= # empty
4721: ANOTHER_INT_LIST= apache-[0-9]*:../../www/apache
4722: EXT_LIST= # empty
4723: ANOTHER_EXT_LIST= a=b c=d
4724:
4725: INT_LIST+= ${STRING} # 1
4726: INT_LIST+= ${ANOTHER_INT_LIST} # 2
4727: EXT_LIST+= ${STRING:Q} # 3
4728: EXT_LIST+= ${ANOTHER_EXT_LIST} # 4
4729: </pre>
4730: <p>When you add a string to an external list (example 3), it
4731: must be quoted. In all other cases, you must not add a quoting
4732: level. You must not merge internal and external lists, unless you
4733: are sure that all entries are correctly interpreted in both
4734: lists.</p>
4735: </div>
1.41 asau 4736: <div class="sect2">
1.1 dsieger 4737: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4738: <a name="converting-internal-to-external"></a>12.3.2. Converting an internal list into an external list</h3></div></div></div>
1.1 dsieger 4739: <pre class="programlisting">
4740: EXT_LIST= # empty
4741: .for i in ${INT_LIST}
4742: EXT_LIST+= ${i:Q}""
4743: .endfor
4744: </pre>
4745: <p>This code converts the internal list
4746: <code class="varname">INT_LIST</code> into the external list
4747: <code class="varname">EXT_LIST</code>. As the elements of an internal list
4748: are unquoted they must be quoted here. The reason for appending
4749: <code class="varname">""</code> is explained below.</p>
4750: </div>
1.41 asau 4751: <div class="sect2">
1.1 dsieger 4752: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4753: <a name="passing-variable-to-shell"></a>12.3.3. Passing variables to a shell command</h3></div></div></div>
1.1 dsieger 4754: <p>Sometimes you may want to print an arbitrary string. There
4755: are many ways to get it wrong and only few that can handle every
4756: nastiness.</p>
4757: <pre class="programlisting">
4758: STRING= foo bar < > * `date` $$HOME ' "
4759: EXT_LIST= string=${STRING:Q} x=second\ item
4760:
4761: all:
4762: echo ${STRING} # 1
4763: echo "${STRING}" # 2
4764: echo "${STRING:Q}" # 3
4765: echo ${STRING:Q} # 4
4766: echo x${STRING:Q} | sed 1s,.,, # 5
4767: printf "%s\\n" ${STRING:Q}"" # 6
4768: env ${EXT_LIST} /bin/sh -c 'echo "$$string"; echo "$$x"'
4769: </pre>
4770: <p>Example 1 leads to a syntax error in the shell, as the
4771: characters are just copied.</p>
4772: <p>Example 2 leads to a syntax error too, and if you leave out
4773: the last " character from <code class="varname">${STRING}</code>,
1.79 snj 4774: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?date+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">date</span>(1)</span></a> will be executed. The <code class="varname">$HOME</code> shell
1.1 dsieger 4775: variable would be evaluated, too.</p>
4776: <p>Example 3 outputs each space character preceded by a
4777: backslash (or not), depending on the implementation of the
1.79 snj 4778: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">echo</span>(1)</span></a> command.</p>
1.1 dsieger 4779: <p>Example 4 handles correctly every string that does not start
4780: with a dash. In that case, the result depends on the
1.79 snj 4781: implementation of the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">echo</span>(1)</span></a> command. As long as you can
1.1 dsieger 4782: guarantee that your input does not start with a dash, this form is
4783: appropriate.</p>
4784: <p>Example 5 handles even the case of a leading dash
4785: correctly.</p>
4786: <p>Example 6 also works with every string and is the
4787: light-weight solution, since it does not involve a pipe, which has
4788: its own problems.</p>
4789: <p>The <code class="varname">EXT_LIST</code> does not need to be quoted
4790: because the quoting has already been done when adding elements to
4791: the list.</p>
4792: <p>As internal lists shall not be passed to the shell, there is
4793: no example for it.</p>
4794: </div>
1.41 asau 4795: <div class="sect2">
1.1 dsieger 4796: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4797: <a name="quoting-guideline"></a>12.3.4. Quoting guideline</h3></div></div></div>
1.1 dsieger 4798: <p>There are many possible sources of wrongly quoted variables.
4799: This section lists some of the commonly known ones.</p>
1.41 asau 4800: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4801: <li class="listitem">
1.1 dsieger 4802: <p>Whenever you use the value of a list, think
4803: about what happens to leading or trailing whitespace. If the
4804: list is a well-formed shell expression, you can apply the
4805: <code class="varname">:M*</code> modifier to strip leading and trailing
4806: whitespace from each word. The <code class="varname">:M</code> operator
4807: first splits its argument according to the rules of the shell,
4808: and then creates a new list consisting of all words that match
4809: the shell glob expression <code class="varname">*</code>, that is: all.
4810: One class of situations where this is needed is when adding a
4811: variable like <code class="varname">CPPFLAGS</code> to
4812: <code class="varname">CONFIGURE_ARGS</code>. If the configure script
4813: invokes other configure scripts, it strips the leading and
4814: trailing whitespace from the variable and then passes it to the
4815: other configure scripts. But these configure scripts expect the
4816: (child) <code class="varname">CPPFLAGS</code> variable to be the same as
4817: the parent <code class="varname">CPPFLAGS</code>. That's why we better
4818: pass the <code class="varname">CPPFLAGS</code> value properly trimmed. And
4819: here is how we do it:</p>
4820: <pre class="programlisting">
4821: CPPFLAGS= # empty
4822: CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX:Q}\"
4823: CPPFLAGS+= ${MY_CPPFLAGS}
4824:
4825: CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
4826:
4827: all:
4828: echo x${CPPFLAGS:Q}x # leading and trailing whitespace
4829: echo x${CONFIGURE_ARGS}x # properly trimmed
4830: </pre>
4831: </li>
1.23 wiz 4832: <li class="listitem"><p>The example above contains one bug: The
1.1 dsieger 4833: <code class="varname">${PREFIX}</code> is a properly quoted shell
4834: expression, but there is the C compiler after it, which also
4835: expects a properly quoted string (this time in C syntax). The
4836: version above is therefore only correct if
4837: <code class="varname">${PREFIX}</code> does not have embedded backslashes
4838: or double quotes. If you want to allow these, you have to add
4839: another layer of quoting to each variable that is used as a C
4840: string literal. You cannot use the <code class="varname">:Q</code>
4841: operator for it, as this operator only works for the
4842: shell.</p></li>
1.23 wiz 4843: <li class="listitem">
1.1 dsieger 4844: <p>Whenever a variable can be empty, the
4845: <code class="varname">:Q</code> operator can have surprising results. Here
4846: are two completely different cases which can be solved with the
4847: same trick.</p>
4848: <pre class="programlisting">
4849: EMPTY= # empty
4850: empty_test:
4851: for i in a ${EMPTY:Q} c; do \
4852: echo "$$i"; \
4853: done
4854:
4855: for_test:
4856: .for i in a:\ a:\test.txt
4857: echo ${i:Q}
4858: echo "foo"
4859: .endfor
4860: </pre>
4861: <p>The first example will only print two of the three lines
4862: we might have expected. This is because
4863: <code class="varname">${EMPTY:Q}</code> expands to the empty string, which
4864: the shell cannot see. The workaround is to write
4865: <code class="varname">${EMPTY:Q}""</code>. This pattern can be often found
4866: as <code class="varname">${TEST} -z ${VAR:Q}</code> or as <code class="varname">${TEST}
4867: -f ${FNAME:Q}</code> (both of these are wrong).</p>
4868: <p>The second example will only print three lines instead of
4869: four. The first line looks like <code class="varname">a:\ echo foo</code>.
4870: This is because the backslash of the value
4871: <code class="varname">a:\</code> is interpreted as a line-continuation by
1.79 snj 4872: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, which makes the second line the arguments of the
4873: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?echo+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">echo</span>(1)</span></a> command from the first line. To avoid this, write
1.1 dsieger 4874: <code class="varname">${i:Q}""</code>.</p>
4875: </li>
4876: </ul></div>
4877: </div>
1.41 asau 4878: <div class="sect2">
1.1 dsieger 4879: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 4880: <a name="bsd-make-bug-workaround"></a>12.3.5. Workaround for a bug in BSD Make</h3></div></div></div>
1.1 dsieger 4881: <p>The pkgsrc bmake program does not handle the following
4882: assignment correctly. In case <code class="varname">_othervar_</code>
4883: contains a ``-'' character, one of the closing braces is included
4884: in <code class="varname">${VAR}</code> after this code executes.</p>
4885: <pre class="programlisting">
4886: VAR:= ${VAR:N${_othervar_:C/-//}}
4887: </pre>
4888: <p>For a more complex code snippet and a workaround, see the
1.79 snj 4889: package <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/regress/make-quoting/README.html" target="_top"><code class="filename">regress/make-quoting</code></a>, testcase
1.1 dsieger 4890: <code class="varname">bug1</code>.</p>
4891: </div>
4892: </div>
4893: </div>
1.41 asau 4894: <div class="chapter">
1.1 dsieger 4895: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 4896: <a name="plist"></a>Chapter 13. PLIST issues</h2></div></div></div>
1.1 dsieger 4897: <div class="toc">
4898: <p><b>Table of Contents</b></p>
1.100 leot 4899: <dl class="toc">
1.6 rillig 4900: <dt><span class="sect1"><a href="#rcs-id">13.1. RCS ID</a></span></dt>
1.23 wiz 4901: <dt><span class="sect1"><a href="#automatic-plist-generation">13.2. Semi-automatic <code class="filename">PLIST</code> generation</a></span></dt>
4902: <dt><span class="sect1"><a href="#print-PLIST">13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span></a></span></dt>
1.6 rillig 4903: <dt><span class="sect1"><a href="#plist.misc">13.4. Variable substitution in PLIST</a></span></dt>
4904: <dt><span class="sect1"><a href="#manpage-compression">13.5. Man page compression</a></span></dt>
1.23 wiz 4905: <dt><span class="sect1"><a href="#using-PLIST_SRC">13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code></a></span></dt>
1.6 rillig 4906: <dt><span class="sect1"><a href="#platform-specific-plist">13.7. Platform-specific and differing PLISTs</a></span></dt>
1.86 wiz 4907: <dt><span class="sect1"><a href="#build-plist">13.8. Build-specific PLISTs</a></span></dt>
4908: <dt><span class="sect1"><a href="#faq.common-dirs">13.9. Sharing directories between packages</a></span></dt>
1.1 dsieger 4909: </dl>
4910: </div>
4911: <p>The <code class="filename">PLIST</code> file contains a package's
1.23 wiz 4912: <span class="quote">“<span class="quote">packing list</span>”</span>, i.e. a list of files that belong to
1.1 dsieger 4913: the package (relative to the <code class="filename">${PREFIX}</code>
4914: directory it's been installed in) plus some additional statements
1.79 snj 4915: - see the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> man page for a full list.
1.1 dsieger 4916: This chapter addresses some issues that need attention when
4917: dealing with the <code class="filename">PLIST</code> file (or files, see
4918: below!).</p>
1.41 asau 4919: <div class="sect1">
1.1 dsieger 4920: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4921: <a name="rcs-id"></a>13.1. RCS ID</h2></div></div></div>
1.1 dsieger 4922: <p>Be sure to add a RCS ID line as the first thing in any
4923: <code class="filename">PLIST</code> file you write:</p>
4924: <pre class="programlisting">
4925: @comment $NetBSD$
4926: </pre>
4927: </div>
1.41 asau 4928: <div class="sect1">
1.1 dsieger 4929: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4930: <a name="automatic-plist-generation"></a>13.2. Semi-automatic <code class="filename">PLIST</code> generation</h2></div></div></div>
1.10 hubertf 4931: <p>You can use the <span class="command"><strong>make print-PLIST</strong></span> command
1.1 dsieger 4932: to output a PLIST that matches any new files since the package
1.10 hubertf 4933: was extracted. See <a class="xref" href="#build.helpful-targets" title="17.17. Other helpful targets">Section 17.17, “Other helpful targets”</a> for
1.1 dsieger 4934: more information on this target.</p>
4935: </div>
1.41 asau 4936: <div class="sect1">
1.1 dsieger 4937: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.10 hubertf 4938: <a name="print-PLIST"></a>13.3. Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>
1.1 dsieger 4939: </h2></div></div></div>
4940: <p>The <code class="varname">PRINT_PLIST_AWK</code> variable takes a set
4941: of AWK patterns and actions that are used to filter the output of
4942: print-PLIST. You can <span class="emphasis"><em>append</em></span> any chunk of AWK
4943: scripting you like to it, but be careful with quoting.</p>
4944: <p>For example, to get all files inside the
4945: <code class="filename">libdata/foo</code> directory removed from the
4946: resulting PLIST:</p>
4947: <pre class="programlisting">
4948: PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
4949: </pre>
4950: </div>
1.41 asau 4951: <div class="sect1">
1.1 dsieger 4952: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 4953: <a name="plist.misc"></a>13.4. Variable substitution in PLIST</h2></div></div></div>
1.1 dsieger 4954: <p>A number of variables are substituted automatically in
4955: PLISTs when a package is installed on a system. This includes the
4956: following variables:</p>
1.41 asau 4957: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 4958: <dt><span class="term"><code class="varname">${MACHINE_ARCH}</code>, <code class="varname">${MACHINE_GNU_ARCH}</code></span></dt>
4959: <dd>
4960: <p>Some packages like emacs and perl embed information
4961: about which architecture they were built on into the
4962: pathnames where they install their files. To handle this
4963: case, PLIST will be preprocessed before actually used, and
4964: the symbol
1.23 wiz 4965: <span class="quote">“<span class="quote"><code class="varname">${MACHINE_ARCH}</code></span>”</span> will be
1.10 hubertf 4966: replaced by what <span class="command"><strong>uname -p</strong></span> gives. The
1.1 dsieger 4967: same is done if the string
4968: <code class="varname">${MACHINE_GNU_ARCH}</code> is embedded in
4969: PLIST somewhere - use this on packages that have GNU
4970: autoconf-created configure scripts.</p>
1.41 asau 4971: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 4972: <h3 class="title">Legacy note</h3>
4973: <p>There used to be a symbol
1.23 wiz 4974: <span class="quote">“<span class="quote"><code class="varname">$ARCH</code></span>”</span> that
1.10 hubertf 4975: was replaced by the output of <span class="command"><strong>uname
1.1 dsieger 4976: -m</strong></span>, but that's no longer supported and has
4977: been removed.</p>
4978: </div>
4979: </dd>
4980: <dt><span class="term"><code class="varname">${OPSYS}</code>, <code class="varname">${LOWER_OPSYS}</code>, <code class="varname">${OS_VERSION}</code></span></dt>
4981: <dd>
4982: <p>Some packages want to embed the OS name and version
4983: into some paths. To do this, use these variables in the
4984: <code class="filename">PLIST</code>:
4985: </p>
1.41 asau 4986: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 4987: <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>
4988: <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>
4989: <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>
1.1 dsieger 4990: </ul></div>
4991: </dd>
4992: </dl></div>
1.88 tnn 4993: <p>For a list of values which are replaced by
4994: default, the output of <span class="command"><strong>make help topic=PLIST_SUBST</strong></span> as
4995: well as searching the <code class="filename">pkgsrc/mk</code> directory with <span class="command"><strong>grep</strong></span> for
4996: <code class="varname">PLIST_SUBST</code> should help.</p>
1.1 dsieger 4997: <p>If you want to change other variables not listed above, you
4998: can add variables and their expansions to this variable in the
1.10 hubertf 4999: following way, similar to <code class="varname">MESSAGE_SUBST</code> (see <a class="xref" href="#components.optional" title="11.5. Optional files">Section 11.5, “Optional files”</a>):</p>
1.1 dsieger 5000: <pre class="programlisting">
5001: PLIST_SUBST+= SOMEVAR="somevalue"
5002: </pre>
1.23 wiz 5003: <p>This replaces all occurrences of <span class="quote">“<span class="quote">${SOMEVAR}</span>”</span>
1.1 dsieger 5004: in the <code class="filename">PLIST</code> with
1.23 wiz 5005: <span class="quote">“<span class="quote">somevalue</span>”</span>.</p>
1.18 snj 5006: <p>The <code class="varname">PLIST_VARS</code> variable can be used to simplify
5007: the common case of conditionally including some
5008: <code class="filename">PLIST</code> entries. It can be done by adding
5009: <code class="literal"><code class="varname">PLIST_VARS</code>+=foo</code> and
5010: setting the corresponding <code class="varname">PLIST.foo</code> variable
5011: to <code class="literal">yes</code> if the entry should be included.
1.23 wiz 5012: This will substitute <span class="quote">“<span class="quote"><code class="varname">${PLIST.foo}</code></span>”</span>
1.18 snj 5013: in the <code class="filename">PLIST</code> with either
1.23 wiz 5014: <span class="quote">“<span class="quote"><code class="literal">""</code></span>”</span> or
5015: <span class="quote">“<span class="quote"><code class="literal">"@comment "</code></span>”</span>.
1.18 snj 5016: For example, in <code class="filename">Makefile</code>:</p>
5017: <pre class="programlisting">
5018: PLIST_VARS+= foo
5019: .if <em class="replaceable"><code>condition</code></em>
5020: PLIST.foo= yes
5021: .else
5022: </pre>
5023: <p>And then in <code class="filename">PLIST</code>:</p>
5024: <pre class="programlisting">
5025: @comment $NetBSD$
5026: bin/bar
5027: man/man1/bar.1
5028: ${PLIST.foo}bin/foo
5029: ${PLIST.foo}man/man1/foo.1
5030: ${PLIST.foo}share/bar/foo.data
5031: </pre>
1.1 dsieger 5032: </div>
1.41 asau 5033: <div class="sect1">
1.1 dsieger 5034: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5035: <a name="manpage-compression"></a>13.5. Man page compression</h2></div></div></div>
1.1 dsieger 5036: <p>Man pages should be installed in compressed form if
5037: <code class="varname">MANZ</code> is set (in <code class="filename">bsd.own.mk</code>),
5038: and uncompressed otherwise. To handle this in the
1.23 wiz 5039: <code class="filename">PLIST</code> file, the suffix <span class="quote">“<span class="quote">.gz</span>”</span> is
1.1 dsieger 5040: appended/removed automatically for man pages according to
5041: <code class="varname">MANZ</code> and <code class="varname">MANCOMPRESSED</code> being set
5042: or not, see above for details. This modification of the
5043: <code class="filename">PLIST</code> file is done on a copy of it, not
5044: <code class="filename">PLIST</code> itself.</p>
5045: </div>
1.41 asau 5046: <div class="sect1">
1.1 dsieger 5047: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5048: <a name="using-PLIST_SRC"></a>13.6. Changing PLIST source with <code class="varname">PLIST_SRC</code>
1.1 dsieger 5049: </h2></div></div></div>
5050: <p>To use one or more files as source for the <code class="filename">PLIST</code> used
5051: in generating the binary package, set the variable
5052: <code class="varname">PLIST_SRC</code> to the names of that file(s).
1.79 snj 5053: The files are later concatenated using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cat+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
1.1 dsieger 5054: important. The default for <code class="varname">PLIST_SRC</code> is
5055: <code class="filename">${PKGDIR}/PLIST</code>.</p>
5056: </div>
1.41 asau 5057: <div class="sect1">
1.1 dsieger 5058: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5059: <a name="platform-specific-plist"></a>13.7. Platform-specific and differing PLISTs</h2></div></div></div>
1.1 dsieger 5060: <p>Some packages decide to install a different set of files based on
5061: the operating system being used. These differences can be
5062: automatically handled by using the following files:</p>
1.41 asau 5063: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5064: <li class="listitem"><p><code class="filename">PLIST.common</code></p></li>
5065: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}</code></p></li>
5066: <li class="listitem"><p><code class="filename">PLIST.${MACHINE_ARCH}</code></p></li>
5067: <li class="listitem"><p><code class="filename">PLIST.${OPSYS}-${MACHINE_ARCH}</code></p></li>
5068: <li class="listitem"><p><code class="filename">PLIST.common_end</code></p></li>
1.1 dsieger 5069: </ul></div>
5070: </div>
1.41 asau 5071: <div class="sect1">
1.1 dsieger 5072: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.86 wiz 5073: <a name="build-plist"></a>13.8. Build-specific PLISTs</h2></div></div></div>
5074: <p>Some packages decide to generate hard-to-guess file names
5075: during installation that are hard to wire down.</p>
5076: <p>In such cases, you can set the
5077: <code class="varname">GENERATE_PLIST</code> variable to shell code
5078: terminated (with a semicolon) that will output PLIST entries which
5079: will be appended to the PLIST</p>
5080: <p>You can find one example in editors/xemacs:</p>
5081: <pre class="programlisting">
5082: GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ;
5083: </pre>
5084: <p>which will append something like
5085: <code class="filename">bin/xemacs-21.4.23-54e8ea71.dmp</code> to the
5086: <code class="filename">PLIST</code>.
5087: </p>
5088: </div>
5089: <div class="sect1">
5090: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
5091: <a name="faq.common-dirs"></a>13.9. Sharing directories between packages</h2></div></div></div>
1.23 wiz 5092: <p>A <span class="quote">“<span class="quote">shared directory</span>”</span> is a directory where
1.1 dsieger 5093: multiple (and unrelated) packages install files. These
1.22 jakllsch 5094: directories were problematic because you had to add special
5095: tricks in the PLIST to conditionally remove them, or have some
1.1 dsieger 5096: centralized package handle them.</p>
1.22 jakllsch 5097: <p>In pkgsrc, it is now easy: Each package should create
5098: directories and install files as needed; <span class="command"><strong>pkg_delete</strong></span>
5099: will remove any directories left empty after uninstalling a
5100: package.</p>
5101: <p>If a package needs an empty directory to work, create
5102: the directory during installation as usual, and also add an
5103: entry to the PLIST:
5104: </p>
1.1 dsieger 5105: <pre class="programlisting">
1.22 jakllsch 5106: @pkgdir path/to/empty/directory
1.1 dsieger 5107: </pre>
1.22 jakllsch 5108: <p>
1.86 wiz 5109: or take a look at <code class="varname">MAKE_DIRS</code> and
5110: <code class="varname">OWN_DIRS</code>.
1.22 jakllsch 5111: </p>
1.1 dsieger 5112: </div>
5113: </div>
1.41 asau 5114: <div class="chapter">
1.1 dsieger 5115: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 5116: <a name="buildlink"></a>Chapter 14. Buildlink methodology</h2></div></div></div>
1.1 dsieger 5117: <div class="toc">
5118: <p><b>Table of Contents</b></p>
1.100 leot 5119: <dl class="toc">
1.6 rillig 5120: <dt><span class="sect1"><a href="#converting-to-buildlink3">14.1. Converting packages to use buildlink3</a></span></dt>
1.23 wiz 5121: <dt><span class="sect1"><a href="#creating-buildlink3.mk">14.2. Writing <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.1 dsieger 5122: <dd><dl>
1.6 rillig 5123: <dt><span class="sect2"><a href="#anatomy-of-bl3">14.2.1. Anatomy of a buildlink3.mk file</a></span></dt>
1.26 wiz 5124: <dt><span class="sect2"><a href="#updating-buildlink-depends">14.2.2. Updating
5125: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5126: and
5127: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5128: in <code class="filename">buildlink3.mk</code> files</a></span></dt>
1.1 dsieger 5129: </dl></dd>
1.23 wiz 5130: <dt><span class="sect1"><a href="#writing-builtin.mk">14.3. Writing <code class="filename">builtin.mk</code> files</a></span></dt>
1.1 dsieger 5131: <dd><dl>
1.23 wiz 5132: <dt><span class="sect2"><a href="#anatomy-of-builtin.mk">14.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</a></span></dt>
1.6 rillig 5133: <dt><span class="sect2"><a href="#native-or-pkgsrc-preference">14.3.2. Global preferences for native or pkgsrc software</a></span></dt>
1.1 dsieger 5134: </dl></dd>
5135: </dl>
5136: </div>
5137: <p>Buildlink is a framework in pkgsrc that controls what headers and libraries
5138: are seen by a package's configure and build processes. This is implemented
5139: in a two step process:</p>
1.23 wiz 5140: <div class="orderedlist"><ol class="orderedlist" type="1">
5141: <li class="listitem"><p>Symlink headers and libraries for dependencies into
1.1 dsieger 5142: <code class="varname">BUILDLINK_DIR</code>, which by default is a subdirectory
5143: of <code class="varname">WRKDIR</code>.</p></li>
1.23 wiz 5144: <li class="listitem"><p>Create wrapper scripts that are used in place of the normal compiler
1.1 dsieger 5145: tools that translate <code class="option">-I${LOCALBASE}/include</code> and
5146: <code class="option">-L${LOCALBASE}/lib</code> into references to
5147: <code class="varname">BUILDLINK_DIR</code>. The wrapper scripts also make
5148: native compiler on some operating systems look like GCC, so that
5149: packages that expect GCC won't require modifications to build with
5150: those native compilers.</p></li>
5151: </ol></div>
5152: <p>This normalizes the environment in which a package is built so that the
5153: package may be built consistently despite what other software may be
5154: installed. Please note that the normal system header and library paths,
5155: e.g. <code class="filename">/usr/include</code>,
5156: <code class="filename">/usr/lib</code>, etc., are always searched -- buildlink3 is
5157: designed to insulate the package build from non-system-supplied
5158: software.</p>
1.41 asau 5159: <div class="sect1">
1.1 dsieger 5160: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5161: <a name="converting-to-buildlink3"></a>14.1. Converting packages to use buildlink3</h2></div></div></div>
1.1 dsieger 5162: <p>The process of converting packages to use the buildlink3
1.23 wiz 5163: framework (<span class="quote">“<span class="quote">bl3ifying</span>”</span>) is fairly straightforward.
1.1 dsieger 5164: The things to keep in mind are:</p>
1.23 wiz 5165: <div class="orderedlist"><ol class="orderedlist" type="1">
5166: <li class="listitem"><p>Ensure that the build always calls the wrapper scripts
1.1 dsieger 5167: instead of the actual toolchain. Some packages are tricky,
5168: and the only way to know for sure is the check
5169: <code class="filename">${WRKDIR}/.work.log</code> to see if the
5170: wrappers are being invoked.</p></li>
1.23 wiz 5171: <li class="listitem"><p>Don't override <code class="varname">PREFIX</code> from within
1.1 dsieger 5172: the package Makefile, e.g. Java VMs, standalone shells,
5173: etc., because the code to symlink files into
5174: <code class="filename">${BUILDLINK_DIR}</code> looks for files
1.23 wiz 5175: relative to <span class="quote">“<span class="quote">pkg_info -qp <em class="replaceable"><code>pkgname</code></em></span>”</span>.
1.1 dsieger 5176: </p></li>
1.23 wiz 5177: <li class="listitem"><p>Remember that <span class="emphasis"><em>only</em></span> the
1.1 dsieger 5178: <code class="filename">buildlink3.mk</code> files that you list in a
5179: package's Makefile are added as dependencies for that package.
5180: </p></li>
5181: </ol></div>
5182: <p>If a dependency on a particular package is required for its libraries and
5183: headers, then we replace:</p>
5184: <pre class="programlisting">
5185: DEPENDS+= foo>=1.1.0:../../category/foo
5186: </pre>
5187: <p>with</p>
5188: <pre class="programlisting">
5189: .include "../../category/foo/buildlink3.mk"
5190: </pre>
5191: <p>The buildlink3.mk files usually define the required dependencies.
5192: If you need a newer version of the dependency when using buildlink3.mk
5193: files, then you can define it in your Makefile; for example:</p>
5194: <pre class="programlisting">
5195: BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
5196: .include "../../category/foo/buildlink3.mk"
5197: </pre>
5198: <p>There are several <code class="filename">buildlink3.mk</code>
5199: files in <code class="filename">pkgsrc/mk</code>
5200: that handle special package issues:</p>
1.41 asau 5201: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5202: <li class="listitem"><p><code class="filename">bdb.buildlink3.mk</code> chooses either
1.1 dsieger 5203: the native or a pkgsrc Berkeley DB implementation based on
5204: the values of <code class="varname">BDB_ACCEPTED</code> and
5205: <code class="varname">BDB_DEFAULT</code>.</p></li>
1.23 wiz 5206: <li class="listitem"><p><code class="filename">curses.buildlink3.mk</code>: If the system
1.1 dsieger 5207: comes with neither Curses nor NCurses, this will take care
1.79 snj 5208: to install the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/ncurses/README.html" target="_top"><code class="filename">devel/ncurses</code></a> package.</p></li>
1.23 wiz 5209: <li class="listitem"><p><code class="filename">krb5.buildlink3.mk</code> uses the value
1.1 dsieger 5210: of <code class="varname">KRB5_ACCEPTED</code> to choose between
5211: adding a dependency on Heimdal or MIT-krb5 for packages that
5212: require a Kerberos 5 implementation.</p></li>
1.23 wiz 5213: <li class="listitem"><p><code class="filename">motif.buildlink3.mk</code> checks for a
1.1 dsieger 5214: system-provided Motif installation or adds a dependency on
1.79 snj 5215: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/lesstif/README.html" target="_top"><code class="filename">x11/lesstif</code></a>, <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/motif/README.html" target="_top"><code class="filename">x11/motif</code></a> or <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/openmotif/README.html" target="_top"><code class="filename">x11/openmotif</code></a>. The user can set
1.23 wiz 5216: <code class="varname">MOTIF_TYPE</code> to <span class="quote">“<span class="quote">dt</span>”</span>,
1.45 obache 5217: <span class="quote">“<span class="quote">lesstif</span>”</span>, <span class="quote">“<span class="quote">motif</span>”</span> or
5218: <span class="quote">“<span class="quote">openmotif</span>”</span> to choose
1.1 dsieger 5219: which Motif version will be used.</p></li>
1.55 ryoon 5220: <li class="listitem"><p><code class="filename">readline.buildlink3.mk</code> checks for a
1.56 wiz 5221: system-provided GNU readline or editline (libedit) installation,
1.79 snj 5222: or adds a dependency on <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/readline/README.html" target="_top"><code class="filename">devel/readline</code></a>,
5223: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/editline/README.html" target="_top"><code class="filename">devel/editline</code></a>. The user can set
1.55 ryoon 5224: <code class="varname">READLINE_DEFAULT</code> to choose readline implementation.
5225: If your package really needs GNU readline library, its Makefile
5226: should include <code class="filename">devel/readline/buildlink3.mk</code>
5227: instead of <code class="filename">readline.buildlink3.mk</code>.</p></li>
1.23 wiz 5228: <li class="listitem"><p><code class="filename">oss.buildlink3.mk</code> defines several
1.1 dsieger 5229: variables that may be used by packages that use the
5230: Open Sound System (OSS) API.</p></li>
1.23 wiz 5231: <li class="listitem"><p><code class="filename">pgsql.buildlink3.mk</code> will accept
1.35 wiz 5232: any of the Postgres versions in the variable
5233: <code class="varname">PGSQL_VERSIONS_ACCEPTED</code> and default to
5234: the version <code class="varname">PGSQL_VERSION_DEFAULT</code>. See
1.1 dsieger 5235: the file for more information.</p></li>
1.23 wiz 5236: <li class="listitem"><p><code class="filename">pthread.buildlink3.mk</code> uses the value of
1.1 dsieger 5237: <code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds
1.79 snj 5238: a dependency on <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/pth/README.html" target="_top"><code class="filename">devel/pth</code></a> as needed.</p></li>
1.23 wiz 5239: <li class="listitem"><p><code class="filename">xaw.buildlink3.mk</code> uses the value of
1.1 dsieger 5240: <code class="varname">XAW_TYPE</code> to choose a particular Athena widgets
5241: library.</p></li>
5242: </ul></div>
5243: <p>The comments in those <code class="filename">buildlink3.mk</code>
5244: files provide a more complete
5245: description of how to use them properly.</p>
5246: </div>
1.41 asau 5247: <div class="sect1">
1.1 dsieger 5248: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5249: <a name="creating-buildlink3.mk"></a>14.2. Writing <code class="filename">buildlink3.mk</code> files</h2></div></div></div>
1.7 rillig 5250: <a name="buildlink3.mk"></a><p>A package's <code class="filename">buildlink3.mk</code> file is
1.1 dsieger 5251: included by Makefiles to indicate the need to compile and link
5252: against header files and libraries provided by the package. A
5253: <code class="filename">buildlink3.mk</code> file should always provide
5254: enough information to add the correct type of dependency
5255: relationship and include any other
5256: <code class="filename">buildlink3.mk</code> files that it needs to find
5257: headers and libraries that it needs in turn.</p>
5258: <p>To generate an initial <code class="filename">buildlink3.mk</code>
1.79 snj 5259: file for further editing, Rene Hexel's <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/createbuildlink/README.html" target="_top"><code class="filename">pkgtools/createbuildlink</code></a>
1.1 dsieger 5260: package is highly recommended. For most packages, the following
5261: command will generate a good starting point for
5262: <code class="filename">buildlink3.mk</code> files:</p>
5263: <pre class="screen">
5264: <code class="prompt">%</code> <strong class="userinput"><code>cd pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>pkgdir</code></em>
5265: <code class="prompt">%</code> createbuildlink >buildlink3.mk</code></strong>
5266: </pre>
1.41 asau 5267: <div class="sect2">
1.1 dsieger 5268: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5269: <a name="anatomy-of-bl3"></a>14.2.1. Anatomy of a buildlink3.mk file</h3></div></div></div>
1.1 dsieger 5270: <p>The following real-life example
5271: <code class="filename">buildlink3.mk</code> is taken
5272: from <code class="filename">pkgsrc/graphics/tiff</code>:</p>
5273: <pre class="programlisting">
1.18 snj 5274: # $NetBSD: buildlink3.mk,v 1.16 2009/03/20 19:24:45 joerg Exp $
1.1 dsieger 5275:
1.18 snj 5276: BUILDLINK_TREE+= tiff
1.1 dsieger 5277:
1.18 snj 5278: .if !defined(TIFF_BUILDLINK3_MK)
5279: TIFF_BUILDLINK3_MK:=
1.1 dsieger 5280:
1.18 snj 5281: BUILDLINK_API_DEPENDS.tiff+= tiff>=3.6.1
5282: BUILDLINK_ABI_DEPENDS.tiff+= tiff>=3.7.2nb1
5283: BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
1.1 dsieger 5284:
5285: .include "../../devel/zlib/buildlink3.mk"
5286: .include "../../graphics/jpeg/buildlink3.mk"
1.18 snj 5287: .endif # TIFF_BUILDLINK3_MK
1.1 dsieger 5288:
1.18 snj 5289: BUILDLINK_TREE+= -tiff
1.1 dsieger 5290: </pre>
5291: <p>The header and footer manipulate
1.18 snj 5292: <code class="varname">BUILDLINK_TREE</code>, which is common across all
1.1 dsieger 5293: <code class="filename">buildlink3.mk</code> files and is used to track
1.18 snj 5294: the dependency tree.</p>
5295: <p>The main section is protected from multiple inclusion
1.1 dsieger 5296: and controls how the dependency on <em class="replaceable"><code>pkg</code></em> is
5297: added. Several important variables are set in the section:</p>
1.41 asau 5298: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5299: <li class="listitem"><p><code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5300: is the actual dependency recorded in the installed
5301: package; this should always be set using
1.10 hubertf 5302: <span class="command"><strong>+=</strong></span> to ensure that
1.1 dsieger 5303: we're appending to any pre-existing list of values. This
5304: variable should be set to the first version of the
1.26 wiz 5305: package that had an backwards-incompatible API change.
1.1 dsieger 5306: </p></li>
1.23 wiz 5307: <li class="listitem"><p><code class="varname">BUILDLINK_PKGSRCDIR.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5308: is the location of the <em class="replaceable"><code>pkg</code></em>
5309: pkgsrc directory.</p></li>
1.23 wiz 5310: <li class="listitem"><p><code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5311: (not shown above) controls whether we use
5312: <code class="varname">BUILD_DEPENDS</code> or
5313: <code class="varname">DEPENDS</code> to add the dependency on
5314: <em class="replaceable"><code>pkg</code></em>. The build dependency is
5315: selected by setting
5316: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>pkg</code></em></code>
1.23 wiz 5317: to <span class="quote">“<span class="quote">build</span>”</span>. By default, the full dependency is
1.1 dsieger 5318: used.</p></li>
1.23 wiz 5319: <li class="listitem"><p><code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5320: and
5321: <code class="varname">BUILDLINK_LIBDIRS.<em class="replaceable"><code>pkg</code></em></code>
5322: (not shown above) are lists of subdirectories of
5323: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
5324: to add to the header and library search paths. These
1.23 wiz 5325: default to <span class="quote">“<span class="quote">include</span>”</span> and <span class="quote">“<span class="quote">lib</span>”</span>
1.1 dsieger 5326: respectively.</p></li>
1.23 wiz 5327: <li class="listitem"><p><code class="varname">BUILDLINK_CPPFLAGS.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5328: (not shown above) is the list of preprocessor flags to add
5329: to <code class="varname">CPPFLAGS</code>, which are passed on to the
1.23 wiz 5330: configure and build phases. The <span class="quote">“<span class="quote">-I</span>”</span> option
1.1 dsieger 5331: should be avoided and instead be handled using
5332: <code class="varname">BUILDLINK_INCDIRS.<em class="replaceable"><code>pkg</code></em></code> as
5333: above.</p></li>
5334: </ul></div>
5335: <p>The following variables are all optionally defined within
5336: this second section (protected against multiple inclusion) and
5337: control which package files are symlinked into
5338: <code class="filename">${BUILDLINK_DIR}</code> and how their names are
5339: transformed during the symlinking:</p>
1.41 asau 5340: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5341: <li class="listitem"><p><code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5342: (not shown above) is a shell glob pattern relative to
5343: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
5344: to be symlinked into
5345: <code class="filename">${BUILDLINK_DIR}</code>,
5346: e.g. <code class="filename">include/*.h</code>.</p></li>
1.23 wiz 5347: <li class="listitem"><p><code class="varname">BUILDLINK_FILES_CMD.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5348: (not shown above) is a shell pipeline that
5349: outputs to stdout a list of files relative to
5350: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>.
5351: The resulting files are to be symlinked
5352: into <code class="filename">${BUILDLINK_DIR}</code>. By default,
5353: this takes the <code class="filename">+CONTENTS</code> of a
5354: <em class="replaceable"><code>pkg</code></em> and filters it through
5355: <code class="varname">${BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em>}</code>.</p></li>
1.23 wiz 5356: <li class="listitem"><p><code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5357: (not shown above) is a filter command that filters
5358: <code class="filename">+CONTENTS</code> input into a list of files
5359: relative to
5360: <code class="filename">${BUILDLINK_PREFIX.<em class="replaceable"><code>pkg</code></em>}</code>
1.84 wiz 5361: on stdout. By default,
1.1 dsieger 5362: <code class="varname">BUILDLINK_CONTENTS_FILTER.<em class="replaceable"><code>pkg</code></em></code>
5363: outputs the contents of the <code class="filename">include</code>
5364: and <code class="filename">lib</code> directories in the package
1.84 wiz 5365: <code class="filename">+CONTENTS</code>.</p></li>
1.23 wiz 5366: <li class="listitem"><p><code class="varname">BUILDLINK_FNAME_TRANSFORM.<em class="replaceable"><code>pkg</code></em></code>
1.1 dsieger 5367: (not shown above) is a list of sed arguments used to
5368: transform the name of the source filename into a
1.10 hubertf 5369: destination filename, e.g. <span class="command"><strong>-e
1.1 dsieger 5370: "s|/curses.h|/ncurses.h|g"</strong></span>.</p></li>
5371: </ul></div>
1.18 snj 5372: <p>This section can additionally include any
1.1 dsieger 5373: <code class="filename">buildlink3.mk</code> needed for
5374: <em class="replaceable"><code>pkg</code></em>'s library dependencies.
5375: Including these <code class="filename">buildlink3.mk</code> files
5376: means that the headers and libraries for these
5377: dependencies are also symlinked into
5378: <code class="filename">${BUILDLINK_DIR}</code>
5379: whenever the <em class="replaceable"><code>pkg</code></em>
5380: <code class="filename">buildlink3.mk</code>
1.18 snj 5381: file is included. Dependencies are only added for directly
5382: include <code class="filename">buildlink3.mk</code> files.</p>
1.47 wiz 5383: <p>When providing a <code class="filename">buildlink3.mk</code> and
5384: including other <code class="filename">buildlink3.mk</code> files in it,
1.50 wiz 5385: please only add necessary ones, i.e., those whose libraries or
1.47 wiz 5386: header files are automatically exposed when the package is
5387: use.</p>
5388: <p>In particular, if only an executable
5389: (<code class="filename">bin/foo</code>) is linked against a library, that
5390: library does not need to be propagated in the
5391: <code class="filename">buildlink3.mk</code> file.</p>
5392: <p>The following steps should help you decide if a
5393: <code class="filename">buildlink3.mk</code> file needs to be included:
5394: </p>
5395: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
5396: <li class="listitem"><p>Look at the installed header files: What
5397: headers do they include? The packages providing these files
5398: must be buildlinked.</p></li>
1.49 wiz 5399: <li class="listitem"><p>Run <code class="filename">ldd</code> on all installed
5400: libraries and look against what other libraries they link.
5401: Some of the packages providing these probably need to be
5402: buildlinked; however, it's not automatic, since e.g. GTK on
5403: some systems pulls in the X libraries, so they will show up in
5404: the <code class="filename">ldd</code> output, while on others (like OS
1.50 wiz 5405: X) it won't. <code class="filename">ldd</code> output can thus only be
1.49 wiz 5406: used as a hint.</p></li>
1.47 wiz 5407: </ul></div>
5408: <p>
5409: </p>
1.1 dsieger 5410: </div>
1.41 asau 5411: <div class="sect2">
1.1 dsieger 5412: <div class="titlepage"><div><div><h3 class="title">
1.26 wiz 5413: <a name="updating-buildlink-depends"></a>14.2.2. Updating
1.1 dsieger 5414: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.26 wiz 5415: and
5416: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5417: in <code class="filename">buildlink3.mk</code> files</h3></div></div></div>
5418: <p>These two variables differ in that one describes source
5419: compatibility (API) and the other binary compatibility (ABI).
5420: The difference is that a change in the API breaks compilation of
5421: programs while changes in the ABI stop compiled programs from
5422: running.</p>
5423: <p>Changes to the
1.27 wiz 5424: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
1.26 wiz 5425: variable in a <code class="filename">buildlink3.mk</code> file happen
5426: very rarely. One possible reason is that all packages depending
5427: on this already need a newer version. In case it is bumped see
5428: the description below.</p>
5429: <p>The most common example of an ABI change is that the major
5430: version of a shared library is increased. In this case,
5431: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5432: should be adjusted to require at least the new package version.
5433: Then the packages that depend on this package need their
5434: <code class="varname">PKGREVISION</code>s increased and, if they have
5435: <code class="filename">buildlink3.mk</code> files, their
5436: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5437: adjusted, too. This is needed so pkgsrc will require the correct
5438: package dependency and not settle for an older one when building
5439: the source.</p>
1.10 hubertf 5440: <p>See <a class="xref" href="#dependencies" title="19.1.6. Handling dependencies">Section 19.1.6, “Handling dependencies”</a> for
1.26 wiz 5441: more information about dependencies on other packages,
5442: including the <code class="varname">BUILDLINK_ABI_DEPENDS</code> and
1.1 dsieger 5443: <code class="varname">ABI_DEPENDS</code> definitions.</p>
5444: <p>Please take careful consideration before adjusting
5445: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5446: or
5447: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5448: as we don't want to cause unneeded package deletions and
5449: rebuilds. In many cases, new versions of packages work just
5450: fine with older dependencies.</p>
5451: <p>Also it is not needed to set
1.26 wiz 5452: <code class="varname">BUILDLINK_ABI_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>
5453: when it is identical to
1.1 dsieger 5454: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>. </p>
5455: </div>
5456: </div>
1.41 asau 5457: <div class="sect1">
1.1 dsieger 5458: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5459: <a name="writing-builtin.mk"></a>14.3. Writing <code class="filename">builtin.mk</code> files</h2></div></div></div>
1.1 dsieger 5460: <p>Some packages in pkgsrc install headers and libraries that
5461: coincide with headers and libraries present in the base system.
5462: Aside from a <code class="filename">buildlink3.mk</code> file, these
5463: packages should also include a <code class="filename">builtin.mk</code>
5464: file that includes the necessary checks to decide whether using
5465: the built-in software or the pkgsrc software is
5466: appropriate.</p>
5467: <p>The only requirements of a builtin.mk file for
5468: <em class="replaceable"><code>pkg</code></em> are:</p>
1.23 wiz 5469: <div class="orderedlist"><ol class="orderedlist" type="1">
5470: <li class="listitem"><p>It should set
1.1 dsieger 5471: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
1.23 wiz 5472: to either <span class="quote">“<span class="quote">yes</span>”</span> or <span class="quote">“<span class="quote">no</span>”</span>
1.1 dsieger 5473: after it is included.</p></li>
1.23 wiz 5474: <li class="listitem"><p>It should <span class="emphasis"><em>not</em></span> override any
1.1 dsieger 5475: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
5476: which is already set before the
5477: <code class="filename">builtin.mk</code> file is included.</p></li>
1.23 wiz 5478: <li class="listitem"><p>It should be written to allow multiple inclusion. This
1.1 dsieger 5479: is <span class="emphasis"><em>very</em></span> important and takes careful
5480: attention to <code class="filename">Makefile</code> coding.</p></li>
5481: </ol></div>
1.41 asau 5482: <div class="sect2">
1.1 dsieger 5483: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5484: <a name="anatomy-of-builtin.mk"></a>14.3.1. Anatomy of a <code class="filename">builtin.mk</code> file</h3></div></div></div>
1.1 dsieger 5485: <p>The following is the recommended template for builtin.mk
5486: files:</p>
5487: <pre class="programlisting">
5488: .if !defined(IS_BUILTIN.foo)
5489: #
5490: # IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
5491: # genuinely exists in the system or not.
5492: #
5493: IS_BUILTIN.foo?= no
5494:
5495: # BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
5496: # version can be determined.
5497: #
5498: . if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
5499: BUILTIN_PKG.foo?= foo-1.0
5500: . endif
5501: .endif # IS_BUILTIN.foo
5502:
5503: .if !defined(USE_BUILTIN.foo)
5504: USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
5505: . if defined(BUILTIN_PKG.foo)
5506: . for _depend_ in ${BUILDLINK_API_DEPENDS.foo}
5507: . if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
5508: USE_BUILTIN.foo!= \
5509: ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo} \
5510: && ${ECHO} "yes" || ${ECHO} "no"
5511: . endif
5512: . endfor
5513: . endif
5514: .endif # USE_BUILTIN.foo
5515:
5516: CHECK_BUILTIN.foo?= no
5517: .if !empty(CHECK_BUILTIN.foo:M[nN][oO])
5518: #
5519: # Here we place code that depends on whether USE_BUILTIN.foo is set to
5520: # "yes" or "no".
5521: #
5522: .endif # CHECK_BUILTIN.foo
5523: </pre>
5524: <p>The first section sets
5525: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
5526: depending on if <em class="replaceable"><code>pkg</code></em> really exists
5527: in the base system. This should not be a base system software
5528: with similar functionality to <em class="replaceable"><code>pkg</code></em>;
1.23 wiz 5529: it should only be <span class="quote">“<span class="quote">yes</span>”</span> if the actual package is
1.1 dsieger 5530: included as part of the base system. This variable is only
5531: used internally within the <code class="filename">builtin.mk</code>
5532: file.</p>
5533: <p>The second section sets
5534: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
5535: to the version of <em class="replaceable"><code>pkg</code></em> in the base
5536: system if it exists (if
5537: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
1.23 wiz 5538: is <span class="quote">“<span class="quote">yes</span>”</span>). This variable is only used internally
1.1 dsieger 5539: within the <code class="filename">builtin.mk</code> file.</p>
5540: <p>The third section sets
5541: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
5542: and is <span class="emphasis"><em>required</em></span> in all
5543: <code class="filename">builtin.mk</code> files. The code in this
5544: section must make the determination whether the built-in
5545: software is adequate to satisfy the dependencies listed in
5546: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
5547: This is typically done by comparing
5548: <code class="varname">BUILTIN_PKG.<em class="replaceable"><code>pkg</code></em></code>
5549: against each of the dependencies in
5550: <code class="varname">BUILDLINK_API_DEPENDS.<em class="replaceable"><code>pkg</code></em></code>.
5551: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
5552: <span class="emphasis"><em>must</em></span> be set to the correct value by the
5553: end of the <code class="filename">builtin.mk</code> file. Note that
5554: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
1.23 wiz 5555: may be <span class="quote">“<span class="quote">yes</span>”</span> even if
1.1 dsieger 5556: <code class="varname">IS_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
1.23 wiz 5557: is <span class="quote">“<span class="quote">no</span>”</span> because we may make the determination
1.1 dsieger 5558: that the built-in version of the software is similar enough to
5559: be used as a replacement.</p>
5560: <p>The last section is guarded by
5561: <code class="varname">CHECK_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>,
5562: and includes code that uses the value of
5563: <code class="varname">USE_BUILTIN.<em class="replaceable"><code>pkg</code></em></code>
5564: set in the previous section. This typically includes, e.g.,
5565: adding additional dependency restrictions and listing additional
5566: files to symlink into <code class="filename">${BUILDLINK_DIR}</code> (via
5567: <code class="varname">BUILDLINK_FILES.<em class="replaceable"><code>pkg</code></em></code>).</p>
5568: </div>
1.41 asau 5569: <div class="sect2">
1.1 dsieger 5570: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5571: <a name="native-or-pkgsrc-preference"></a>14.3.2. Global preferences for native or pkgsrc software</h3></div></div></div>
1.1 dsieger 5572: <p>When building packages, it's possible to choose whether to set
5573: a global preference for using either the built-in (native)
5574: version or the pkgsrc version of software to satisfy a
5575: dependency. This is controlled by setting
5576: <code class="varname">PREFER_PKGSRC</code> and
5577: <code class="varname">PREFER_NATIVE</code>. These variables take values
1.23 wiz 5578: of either <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">no</span>”</span>, or a list of
1.1 dsieger 5579: packages. <code class="varname">PREFER_PKGSRC</code> tells pkgsrc to
5580: use the pkgsrc versions of software, while
5581: <code class="varname">PREFER_NATIVE</code> tells pkgsrc to use the
5582: built-in versions. Preferences are determined by the most
5583: specific instance of the package in either
5584: <code class="varname">PREFER_PKGSRC</code> or
5585: <code class="varname">PREFER_NATIVE</code>. If a package is specified
5586: in neither or in both variables, then
5587: <code class="varname">PREFER_PKGSRC</code> has precedence over
5588: <code class="varname">PREFER_NATIVE</code>. For example, to require
5589: using pkgsrc versions of software for all but the most basic
5590: bits on a NetBSD system, you can set:</p>
5591: <pre class="programlisting">
5592: PREFER_PKGSRC= yes
5593: PREFER_NATIVE= getopt skey tcp_wrappers
5594: </pre>
5595: <p>A package <span class="emphasis"><em>must</em></span> have a
5596: <code class="filename">builtin.mk</code>
5597: file to be listed in <code class="varname">PREFER_NATIVE</code>,
5598: otherwise it is simply ignored in that list.</p>
5599: </div>
5600: </div>
5601: </div>
1.41 asau 5602: <div class="chapter">
1.1 dsieger 5603: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 5604: <a name="pkginstall"></a>Chapter 15. The pkginstall framework</h2></div></div></div>
1.1 dsieger 5605: <div class="toc">
5606: <p><b>Table of Contents</b></p>
1.100 leot 5607: <dl class="toc">
1.6 rillig 5608: <dt><span class="sect1"><a href="#files-and-dirs-outside-prefix">15.1. Files and directories outside the installation prefix</a></span></dt>
1.1 dsieger 5609: <dd><dl>
1.6 rillig 5610: <dt><span class="sect2"><a href="#dirs-outside-prefix">15.1.1. Directory manipulation</a></span></dt>
5611: <dt><span class="sect2"><a href="#files-outside-prefix">15.1.2. File manipulation</a></span></dt>
1.1 dsieger 5612: </dl></dd>
1.6 rillig 5613: <dt><span class="sect1"><a href="#conf-files">15.2. Configuration files</a></span></dt>
1.1 dsieger 5614: <dd><dl>
1.23 wiz 5615: <dt><span class="sect2"><a href="#conf-files-sysconfdir">15.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</a></span></dt>
1.6 rillig 5616: <dt><span class="sect2"><a href="#conf-files-configure">15.2.2. Telling the software where configuration files are</a></span></dt>
5617: <dt><span class="sect2"><a href="#conf-files-patching">15.2.3. Patching installations</a></span></dt>
5618: <dt><span class="sect2"><a href="#conf-files-disable">15.2.4. Disabling handling of configuration files</a></span></dt>
5619: </dl></dd>
5620: <dt><span class="sect1"><a href="#rcd-scripts">15.3. System startup scripts</a></span></dt>
5621: <dd><dl><dt><span class="sect2"><a href="#rcd-scripts-disable">15.3.1. Disabling handling of system startup scripts</a></span></dt></dl></dd>
5622: <dt><span class="sect1"><a href="#users-and-groups">15.4. System users and groups</a></span></dt>
5623: <dt><span class="sect1"><a href="#shells">15.5. System shells</a></span></dt>
5624: <dd><dl><dt><span class="sect2"><a href="#shells-disable">15.5.1. Disabling shell registration</a></span></dt></dl></dd>
5625: <dt><span class="sect1"><a href="#fonts">15.6. Fonts</a></span></dt>
5626: <dd><dl><dt><span class="sect2"><a href="#fonts-disable">15.6.1. Disabling automatic update of the fonts databases</a></span></dt></dl></dd>
1.1 dsieger 5627: </dl>
5628: </div>
5629: <p>This chapter describes the framework known as
5630: <code class="literal">pkginstall</code>, whose key features are:</p>
1.41 asau 5631: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5632: <li class="listitem"><p>Generic installation and manipulation of directories and files
1.1 dsieger 5633: outside the pkgsrc-handled tree, <code class="varname">LOCALBASE</code>.</p></li>
1.23 wiz 5634: <li class="listitem"><p>Automatic handling of configuration files during installation,
1.1 dsieger 5635: provided that packages are correctly designed.</p></li>
1.23 wiz 5636: <li class="listitem"><p>Generation and installation of system startup scripts.</p></li>
5637: <li class="listitem"><p>Registration of system users and groups.</p></li>
5638: <li class="listitem"><p>Registration of system shells.</p></li>
5639: <li class="listitem"><p>Automatic updating of fonts databases.</p></li>
1.1 dsieger 5640: </ul></div>
5641: <p>The following sections inspect each of the above points in detail.</p>
5642: <p>You may be thinking that many of the things described here could be
5643: easily done with simple code in the package's post-installation target
5644: (<code class="literal">post-install</code>). <span class="emphasis"><em>This is incorrect</em></span>,
5645: as the code in them is only executed when building from source. Machines
5646: using binary packages could not benefit from it at all (as the code itself
5647: could be unavailable). Therefore, the only way to achieve any of the items
5648: described above is by means of the installation scripts, which are
5649: automatically generated by pkginstall.</p>
1.41 asau 5650: <div class="sect1">
1.1 dsieger 5651: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5652: <a name="files-and-dirs-outside-prefix"></a>15.1. Files and directories outside the installation prefix</h2></div></div></div>
1.1 dsieger 5653: <p>As you already know, the <code class="filename">PLIST</code> file holds a list
5654: of files and directories that belong to a package. The names used in it
5655: are relative to the installation prefix (<code class="filename">${PREFIX}</code>),
5656: which means that it cannot register files outside this directory (absolute
5657: path names are not allowed). Despite this restriction, some packages need
5658: to install files outside this location; e.g., under
5659: <code class="filename">${VARBASE}</code> or
5660: <code class="filename">${PKG_SYSCONFDIR}</code>. The only way to achieve this
5661: is to create such files during installation time by using
5662: installation scripts.</p>
5663: <p>The generic installation scripts are shell scripts that can
5664: contain arbitrary code. The list of scripts to execute is taken from
5665: the <code class="varname">INSTALL_FILE</code> variable, which defaults to
5666: <code class="filename">INSTALL</code>. A similar variable exists for package
5667: removal (<code class="varname">DEINSTALL_FILE</code>, whose default is
5668: <code class="filename">DEINSTALL</code>). These scripts can run arbitrary
5669: commands, so they have the potential to create and manage files
5670: anywhere in the file system.</p>
5671: <p>Using these general installation files is not recommended, but
5672: may be needed in some special cases. One reason for avoiding them is
5673: that the user has to trust the packager that there is no unwanted or
5674: simply erroneous code included in the installation script. Also,
5675: previously there were many similar scripts for the same functionality,
5676: and fixing a common error involved finding and changing all of
5677: them.</p>
5678: <p>The pkginstall framework offers another, standardized way. It
5679: provides generic scripts to abstract the manipulation of such files
5680: and directories based on variables set in the package's
5681: <code class="filename">Makefile</code>. The rest of this section describes
5682: these variables.</p>
1.41 asau 5683: <div class="sect2">
1.1 dsieger 5684: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5685: <a name="dirs-outside-prefix"></a>15.1.1. Directory manipulation</h3></div></div></div>
1.1 dsieger 5686: <p>The following variables can be set to request the creation of
5687: directories anywhere in the file system:</p>
1.41 asau 5688: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5689: <li class="listitem"><p><code class="varname">MAKE_DIRS</code> and <code class="varname">OWN_DIRS</code>
1.1 dsieger 5690: contain a list of directories that should be created and should attempt
5691: to be destroyed by the installation scripts. The difference between
5692: the two is that the latter prompts the administrator to remove any
5693: directories that may be left after deinstallation (because they were
5694: not empty), while the former does not.</p></li>
1.23 wiz 5695: <li class="listitem">
1.1 dsieger 5696: <p><code class="varname">MAKE_DIRS_PERMS</code> and
5697: <code class="varname">OWN_DIRS_PERMS</code> contain a list of tuples describing
5698: which directories should be created and should attempt to be destroyed
5699: by the installation scripts. Each tuple holds the following values,
5700: separated by spaces: the directory name, its owner, its group and its
5701: numerical mode. For example:</p>
5702: <pre class="programlisting">
5703: MAKE_DIRS_PERMS+= ${VARBASE}/foo/private ${ROOT_USER} ${ROOT_GROUP} 0700
5704: </pre>
5705: <p>The difference between the two is exactly the same as their
5706: non-<code class="varname">PERMS</code> counterparts.</p>
5707: </li>
5708: </ul></div>
5709: </div>
1.41 asau 5710: <div class="sect2">
1.1 dsieger 5711: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5712: <a name="files-outside-prefix"></a>15.1.2. File manipulation</h3></div></div></div>
1.1 dsieger 5713: <p>Creating non-empty files outside the installation prefix is tricky
5714: because the <code class="filename">PLIST</code> forces all files to be inside it.
5715: To overcome this problem, the only solution is to extract the file in the
5716: known place (i.e., inside the installation prefix) and copy it to the
5717: appropriate location during installation (done by the installation scripts
5718: generated by pkginstall). We will call the former the <span class="emphasis"><em>master
5719: file</em></span> in the following paragraphs, which describe the variables
5720: that can be used to automatically and consistently handle files outside the
5721: installation prefix:</p>
1.41 asau 5722: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5723: <li class="listitem">
1.1 dsieger 5724: <p><code class="varname">CONF_FILES</code> and
1.30 wiz 5725: <code class="varname">REQD_FILES</code> are pairs of master and target files.
1.1 dsieger 5726: During installation time, the master file is copied to the target one
5727: if and only if the latter does not exist. Upon deinstallation, the
5728: target file is removed provided that it was not modified by the
5729: installation.</p>
5730: <p>The difference between the two is that the latter prompts the
5731: administrator to remove any files that may be left after
5732: deinstallation (because they were not empty), while the former does
5733: not.</p>
5734: </li>
1.23 wiz 5735: <li class="listitem">
1.1 dsieger 5736: <p><code class="varname">CONF_FILES_PERMS</code> and
1.30 wiz 5737: <code class="varname">REQD_FILES_PERMS</code> contain tuples describing master
1.1 dsieger 5738: files as well as their target locations. For each of them, it also
5739: specifies their owner, their group and their numeric permissions, in
5740: this order. For example:</p>
5741: <pre class="programlisting">
1.30 wiz 5742: REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile ${ROOT_USER} ${ROOT_GROUP} 0700
1.1 dsieger 5743: </pre>
5744: <p>The difference between the two is exactly the same as their
5745: non-<code class="varname">PERMS</code> counterparts.</p>
5746: </li>
5747: </ul></div>
5748: </div>
5749: </div>
1.41 asau 5750: <div class="sect1">
1.1 dsieger 5751: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5752: <a name="conf-files"></a>15.2. Configuration files</h2></div></div></div>
1.1 dsieger 5753: <p>Configuration files are special in the sense that they are installed
5754: in their own specific directory, <code class="varname">PKG_SYSCONFDIR</code>, and
5755: need special treatment during installation (most of which is automated by
5756: pkginstall). The main concept you must bear in mind is that files marked
5757: as configuration files are automatically copied to the right place (somewhere
5758: inside <code class="varname">PKG_SYSCONFDIR</code>) during installation <span class="emphasis"><em>if
5759: and only if</em></span> they didn't exist before. Similarly, they will not
5760: be removed if they have local modifications. This ensures that
5761: administrators never lose any custom changes they may have made.</p>
1.41 asau 5762: <div class="sect2">
1.1 dsieger 5763: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5764: <a name="conf-files-sysconfdir"></a>15.2.1. How <code class="varname">PKG_SYSCONFDIR</code> is set</h3></div></div></div>
1.1 dsieger 5765: <p>As said before, the <code class="varname">PKG_SYSCONFDIR</code> variable
5766: specifies where configuration files shall be installed. Its contents are
5767: set based upon the following variables:</p>
1.41 asau 5768: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 5769: <li class="listitem"><p><code class="varname">PKG_SYSCONFBASE</code>: The configuration's root
1.1 dsieger 5770: directory. Defaults to <code class="filename">${PREFIX}/etc</code> although it may
5771: be overridden by the user to point to his preferred location (e.g.,
5772: <code class="filename">/etc</code>, <code class="filename">/etc/pkg</code>, etc.).
5773: Packages must not use it directly.</p></li>
1.23 wiz 5774: <li class="listitem">
1.1 dsieger 5775: <p><code class="varname">PKG_SYSCONFSUBDIR</code>: A subdirectory of
5776: <code class="varname">PKG_SYSCONFBASE</code> under which the configuration files
5777: for the package being built shall be installed. The definition of this
5778: variable only makes sense in the package's
5779: <code class="filename">Makefile</code> (i.e., it is not user-customizable).</p>
5780: <p>As an example, consider the Apache package,
1.79 snj 5781: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/README.html" target="_top"><code class="filename">www/apache24</code></a>, which places its
1.1 dsieger 5782: configuration files under the
5783: <code class="filename">httpd/</code> subdirectory of
5784: <code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package
5785: Makefile.</p>
5786: </li>
1.23 wiz 5787: <li class="listitem"><p><code class="varname">PKG_SYSCONFVAR</code>: Specifies the name of the
1.1 dsieger 5788: variable that holds this package's configuration directory (if
5789: different from <code class="varname">PKG_SYSCONFBASE</code>). It defaults to
5790: <code class="varname">PKGBASE</code>'s value, and is always prefixed with
5791: <code class="literal">PKG_SYSCONFDIR</code>.</p></li>
1.23 wiz 5792: <li class="listitem"><p><code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code>: Holds the
1.1 dsieger 5793: directory where the configuration files for the package identified by
5794: <code class="varname">PKG_SYSCONFVAR</code>'s shall be placed.</p></li>
5795: </ul></div>
5796: <p>Based on the above variables, pkginstall determines the value of
5797: <code class="varname">PKG_SYSCONFDIR</code>, which is the <span class="emphasis"><em>only</em></span>
5798: variable that can be used within a package to refer to its configuration
5799: directory. The algorithm used to set its value is basically the
5800: following:</p>
1.23 wiz 5801: <div class="orderedlist"><ol class="orderedlist" type="1">
5802: <li class="listitem"><p>If <code class="varname">PKG_SYSCONFDIR.${PKG_SYSCONFVAR}</code> is set,
1.1 dsieger 5803: its value is used.</p></li>
1.23 wiz 5804: <li class="listitem"><p>If the previous variable is not defined but
1.1 dsieger 5805: <code class="varname">PKG_SYSCONFSUBDIR</code> is set in the package's
5806: <code class="filename">Makefile</code>, the resulting value is
5807: <code class="filename">${PKG_SYSCONFBASE}/${PKG_SYSCONFSUBDIR}</code>.</p></li>
1.23 wiz 5808: <li class="listitem"><p>Otherwise, it is set to
1.1 dsieger 5809: <code class="filename">${PKG_SYSCONFBASE}</code>.</p></li>
5810: </ol></div>
5811: <p>It is worth mentioning that <code class="filename">${PKG_SYSCONFDIR}</code> is
1.16 jnemeth 5812: automatically added to <code class="filename">OWN_DIRS</code>. See <a class="xref" href="#dirs-outside-prefix" title="15.1.1. Directory manipulation">Section 15.1.1, “Directory manipulation”</a> what this means. This does not apply to
5813: subdirectories of <code class="filename">${PKG_SYSCONFDIR}</code>, they still have to
5814: be created with OWN_DIRS or MAKE_DIRS.</p>
1.1 dsieger 5815: </div>
1.41 asau 5816: <div class="sect2">
1.1 dsieger 5817: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5818: <a name="conf-files-configure"></a>15.2.2. Telling the software where configuration files are</h3></div></div></div>
1.1 dsieger 5819: <p>Given that pkgsrc (and users!) expect configuration files to be in a
5820: known place, you need to teach each package where it shall install its
5821: files. In some cases you will have to patch the package Makefiles to
5822: achieve it. If you are lucky, though, it may be as easy as passing an
5823: extra flag to the configuration script; this is the case of GNU Autoconf-
5824: generated files:</p>
5825: <pre class="programlisting">
5826: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
5827: </pre>
5828: <p>Note that this specifies where the package has to <span class="emphasis"><em>look
5829: for</em></span> its configuration files, not where they will be originally
5830: installed (although the difference is never explicit,
5831: unfortunately).</p>
5832: </div>
1.41 asau 5833: <div class="sect2">
1.1 dsieger 5834: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5835: <a name="conf-files-patching"></a>15.2.3. Patching installations</h3></div></div></div>
1.1 dsieger 5836: <p>As said before, pkginstall automatically handles configuration files.
5837: This means that <span class="strong"><strong>the packages themselves must not
5838: touch the contents of <code class="filename">${PKG_SYSCONFDIR}</code>
5839: directly</strong></span>. Bad news is that many software installation scripts
5840: will, out of the box, mess with the contents of that directory. So what is
5841: the correct procedure to fix this issue?</p>
5842: <p>You must teach the package (usually by manually patching it) to
5843: install any configuration files under the examples hierarchy,
5844: <code class="filename">share/examples/${PKGBASE}/</code>. This way, the
5845: <code class="filename">PLIST</code> registers them and the administrator always
5846: has the original copies available.</p>
5847: <p>Once the required configuration files are in place (i.e., under the
5848: examples hierarchy), the pkginstall framework can use them as master copies
5849: during the package installation to update what is in
5850: <code class="filename">${PKG_SYSCONFDIR}</code>. To achieve this, the variables
5851: <code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are
1.10 hubertf 5852: used. Check out <a class="xref" href="#files-outside-prefix" title="15.1.2. File manipulation">Section 15.1.2, “File manipulation”</a> for information
1.1 dsieger 5853: about their syntax and their purpose. Here is an example, taken from the
1.79 snj 5854: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/README.html" target="_top"><code class="filename">mail/mutt</code></a> package:</p>
1.1 dsieger 5855: <pre class="programlisting">
5856: EGDIR= ${PREFIX}/share/doc/mutt/samples
5857: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
5858: </pre>
5859: <p>Note that the <code class="varname">EGDIR</code> variable is specific to that
5860: package and has no meaning outside it.</p>
5861: </div>
1.41 asau 5862: <div class="sect2">
1.1 dsieger 5863: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5864: <a name="conf-files-disable"></a>15.2.4. Disabling handling of configuration files</h3></div></div></div>
1.1 dsieger 5865: <p>The automatic copying of config files can be toggled by setting the
5866: environment variable <code class="varname">PKG_CONFIG</code> prior to package
5867: installation.</p>
5868: </div>
5869: </div>
1.41 asau 5870: <div class="sect1">
1.1 dsieger 5871: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5872: <a name="rcd-scripts"></a>15.3. System startup scripts</h2></div></div></div>
1.1 dsieger 5873: <p>System startup scripts are special files because they must be
5874: installed in a place known by the underlying OS, usually outside the
1.10 hubertf 5875: installation prefix. Therefore, the same rules described in <a class="xref" href="#files-and-dirs-outside-prefix" title="15.1. Files and directories outside the installation prefix">Section 15.1, “Files and directories outside the installation prefix”</a> apply, and the same solutions
1.1 dsieger 5876: can be used. However, pkginstall provides a special mechanism to handle
5877: these files.</p>
5878: <p>In order to provide system startup scripts, the package has
5879: to:</p>
1.23 wiz 5880: <div class="orderedlist"><ol class="orderedlist" type="1">
5881: <li class="listitem"><p>Store the script inside <code class="filename">${FILESDIR}</code>, with
1.1 dsieger 5882: the <code class="literal">.sh</code> suffix appended. Considering the
1.79 snj 5883: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/cups/README.html" target="_top"><code class="filename">print/cups</code></a> package as an example, it has a
1.1 dsieger 5884: <code class="filename">cupsd.sh</code> in its files directory.</p></li>
1.23 wiz 5885: <li class="listitem">
1.1 dsieger 5886: <p>Tell pkginstall to handle it, appending the name of the script,
5887: without its extension, to the <code class="varname">RCD_SCRIPTS</code> variable.
5888: Continuing the previous example:</p>
5889: <pre class="programlisting">
5890: RCD_SCRIPTS+= cupsd
5891: </pre>
5892: </li>
5893: </ol></div>
5894: <p>Once this is done, pkginstall will do the following steps for each
5895: script in an automated fashion:</p>
1.23 wiz 5896: <div class="orderedlist"><ol class="orderedlist" type="1">
5897: <li class="listitem"><p>Process the file found in the files directory applying all the
1.1 dsieger 5898: substitutions described in the <code class="filename">FILES_SUBST</code>
5899: variable.</p></li>
1.23 wiz 5900: <li class="listitem"><p>Copy the script from the files directory to the examples
1.1 dsieger 5901: hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>. Note
5902: that this master file must be explicitly registered in the
5903: <code class="filename">PLIST</code>.</p></li>
1.23 wiz 5904: <li class="listitem"><p>Add code to the installation scripts to copy the startup script
1.1 dsieger 5905: from the examples hierarchy into the system-wide startup scripts
5906: directory.</p></li>
5907: </ol></div>
1.41 asau 5908: <div class="sect2">
1.1 dsieger 5909: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5910: <a name="rcd-scripts-disable"></a>15.3.1. Disabling handling of system startup scripts</h3></div></div></div>
1.1 dsieger 5911: <p>The automatic copying of config files can be toggled by setting the
5912: environment variable <code class="varname">PKG_RCD_SCRIPTS</code> prior to package
5913: installation. Note that the scripts will be always copied inside the
5914: examples hierarchy, <code class="filename">${PREFIX}/share/examples/rc.d/</code>, no
5915: matter what the value of this variable is.</p>
5916: </div>
5917: </div>
1.41 asau 5918: <div class="sect1">
1.1 dsieger 5919: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5920: <a name="users-and-groups"></a>15.4. System users and groups</h2></div></div></div>
1.1 dsieger 5921: <p>If a package needs to create special users and/or groups during
5922: installation, it can do so by using the pkginstall framework.</p>
5923: <p>Users can be created by adding entries to the
5924: <code class="varname">PKG_USERS</code> variable. Each entry has the following
5925: syntax:</p>
5926: <pre class="programlisting">
5927: user:group
5928: </pre>
5929: <p>Further specification of user details may be done by setting
5930: per-user variables.
5931: <code class="varname">PKG_UID.<em class="replaceable"><code>user</code></em></code> is the
5932: numeric UID for the user.
5933: <code class="varname">PKG_GECOS.<em class="replaceable"><code>user</code></em></code> is the
5934: user's description or comment.
5935: <code class="varname">PKG_HOME.<em class="replaceable"><code>user</code></em></code> is the
5936: user's home directory, and defaults to
5937: <code class="filename">/nonexistent</code> if not specified.
5938: <code class="varname">PKG_SHELL.<em class="replaceable"><code>user</code></em></code> is the
5939: user's shell, and defaults to <code class="filename">/sbin/nologin</code> if
5940: not specified.</p>
5941: <p>Similarly, groups can be created by adding entries to the
5942: <code class="varname">PKG_GROUPS</code> variable, whose syntax is:</p>
5943: <pre class="programlisting">
5944: group
5945: </pre>
5946: <p>The numeric GID of the group may be set by defining
5947: <code class="varname">PKG_GID.<em class="replaceable"><code>group</code></em></code>.</p>
5948: <p>If a package needs to create the users and groups at an earlier
5949: stage, then it can set <code class="varname">USERGROUP_PHASE</code> to
5950: either <code class="literal">configure</code> or <code class="literal">build</code> to
5951: indicate the phase before which the users and groups are created. In
5952: this case, the numeric UIDs and GIDs of the created users and groups
5953: are automatically hardcoded into the final installation scripts.</p>
5954: </div>
1.41 asau 5955: <div class="sect1">
1.1 dsieger 5956: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5957: <a name="shells"></a>15.5. System shells</h2></div></div></div>
1.1 dsieger 5958: <p>Packages that install system shells should register them in the shell
5959: database, <code class="filename">/etc/shells</code>, to make things easier to the
5960: administrator. This must be done from the installation scripts to keep
5961: binary packages working on any system. pkginstall provides an easy way to
5962: accomplish this task.</p>
5963: <p>When a package provides a shell interpreter, it has to set the
5964: <code class="varname">PKG_SHELL</code> variable to its absolute file name. This will
5965: add some hooks to the installation scripts to handle it. Consider the
1.79 snj 5966: following example, taken from <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/zsh/README.html" target="_top"><code class="filename">shells/zsh</code></a>:</p>
1.1 dsieger 5967: <pre class="programlisting">
5968: PKG_SHELL= ${PREFIX}/bin/zsh
5969: </pre>
1.41 asau 5970: <div class="sect2">
1.1 dsieger 5971: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5972: <a name="shells-disable"></a>15.5.1. Disabling shell registration</h3></div></div></div>
1.1 dsieger 5973: <p>The automatic registration of shell interpreters can be disabled by
5974: the administrator by setting the <code class="filename">PKG_REGISTER_SHELLS</code>
5975: environment variable to <code class="literal">NO</code>.</p>
5976: </div>
5977: </div>
1.41 asau 5978: <div class="sect1">
1.1 dsieger 5979: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 5980: <a name="fonts"></a>15.6. Fonts</h2></div></div></div>
1.1 dsieger 5981: <p>Packages that install X11 fonts should update the database files
5982: that index the fonts within each fonts directory. This can easily be
5983: accomplished within the pkginstall framework.</p>
5984: <p>When a package installs X11 fonts, it must list the directories in
5985: which fonts are installed in the
5986: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code> variables,
1.23 wiz 5987: where <em class="replaceable"><code>type</code></em> can be one of <span class="quote">“<span class="quote">ttf</span>”</span>,
5988: <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
1.1 dsieger 5989: installation scripts to run the appropriate commands to update the fonts
5990: database files within each of those directories. For convenience, if the
5991: directory path is relative, it is taken to be relative to the package's
1.79 snj 5992: installation prefix. Consider the following example, taken from <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/fonts/dbz-ttf/README.html" target="_top"><code class="filename">fonts/dbz-ttf</code></a>:</p>
1.1 dsieger 5993: <pre class="programlisting">
1.67 wiz 5994: FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
1.1 dsieger 5995: </pre>
1.41 asau 5996: <div class="sect2">
1.1 dsieger 5997: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 5998: <a name="fonts-disable"></a>15.6.1. Disabling automatic update of the fonts databases</h3></div></div></div>
1.1 dsieger 5999: <p>The automatic update of fonts databases can be disabled by
6000: the administrator by setting the <code class="filename">PKG_UPDATE_FONTS_DB</code>
6001: environment variable to <code class="literal">NO</code>.</p>
6002: </div>
6003: </div>
6004: </div>
1.41 asau 6005: <div class="chapter">
1.1 dsieger 6006: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 6007: <a name="options"></a>Chapter 16. Options handling</h2></div></div></div>
1.1 dsieger 6008: <div class="toc">
6009: <p><b>Table of Contents</b></p>
1.100 leot 6010: <dl class="toc">
1.6 rillig 6011: <dt><span class="sect1"><a href="#global-default-options">16.1. Global default options</a></span></dt>
1.23 wiz 6012: <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>
1.6 rillig 6013: <dt><span class="sect1"><a href="#option-names">16.3. Option Names</a></span></dt>
1.7 rillig 6014: <dt><span class="sect1"><a href="#option-build">16.4. Determining the options of dependencies</a></span></dt>
1.1 dsieger 6015: </dl>
6016: </div>
6017: <p>Many packages have the ability to be built to support different
6018: sets of features. <code class="filename">bsd.options.mk</code> is a framework
6019: in pkgsrc that provides generic handling of those options that
6020: determine different ways in which the packages can be built. It's
6021: possible for the user to specify exactly which sets of options will be
6022: built into a package or to allow a set of global default options
6023: apply.</p>
1.7 rillig 6024: <p>There are two broad classes of behaviors that one might want to
6025: control via options. One is whether some particular feature is
6026: enabled in a program that will be built anyway, often by including or
6027: not including a dependency on some other package. The other is
6028: whether or not an additional program will be built as part of the
6029: package. Generally, it is better to make a split package for such
6030: additional programs instead of using options, because it enables
6031: binary packages to be built which can then be added separately. For
6032: example, the foo package might have minimal dependencies (those
6033: packages without which foo doesn't make sense), and then the foo-gfoo
6034: package might include the GTK frontend program gfoo. This is better
6035: than including a gtk option to foo that adds gfoo, because either that
6036: option is default, in which case binary users can't get foo without
6037: gfoo, or not default, in which case they can't get gfoo. With split
6038: packages, they can install foo without having GTK, and later decide to
6039: install gfoo (pulling in GTK at that time). This is an advantage to
6040: source users too, avoiding the need for rebuilds.</p>
6041: <p>Plugins with widely varying dependencies should usually be split
6042: instead of options.</p>
6043: <p>It is often more work to maintain split packages, especially if
6044: the upstream package does not support this. The decision of split
6045: vs. option should be made based on the likelihood that users will want
6046: or object to the various pieces, the size of the dependencies that are
6047: included, and the amount of work.</p>
6048: <p>A further consideration is licensing. Non-free parts, or parts
6049: that depend on non-free dependencies (especially plugins) should
6050: almost always be split if feasible.</p>
1.41 asau 6051: <div class="sect1">
1.1 dsieger 6052: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6053: <a name="global-default-options"></a>16.1. Global default options</h2></div></div></div>
1.1 dsieger 6054: <p>Global default options are listed in
6055: <code class="varname">PKG_DEFAULT_OPTIONS</code>, which is a list of the options
6056: that should be built into every package if that option is supported.
1.10 hubertf 6057: This variable should be set in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
1.1 dsieger 6058: </div>
1.41 asau 6059: <div class="sect1">
1.1 dsieger 6060: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6061: <a name="converting-to-options"></a>16.2. Converting packages to use <code class="filename">bsd.options.mk</code>
1.1 dsieger 6062: </h2></div></div></div>
6063: <p>The following example shows how
6064: <code class="filename">bsd.options.mk</code> should be used
6065: by the hypothetical ``wibble'' package, either in the package
6066: <code class="filename">Makefile</code>, or in a file,
6067: e.g. <code class="filename">options.mk</code>, that is included by the
6068: main package <code class="filename">Makefile</code>.</p>
6069: <pre class="programlisting">
6070: PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
6071: PKG_SUPPORTED_OPTIONS= wibble-foo ldap
6072: PKG_OPTIONS_OPTIONAL_GROUPS= database
6073: PKG_OPTIONS_GROUP.database= mysql pgsql
6074: PKG_SUGGESTED_OPTIONS= wibble-foo
6075: PKG_OPTIONS_LEGACY_VARS+= WIBBLE_USE_OPENLDAP:ldap
6076: PKG_OPTIONS_LEGACY_OPTS+= foo:wibble-foo
6077:
6078: .include "../../mk/bsd.prefs.mk"
6079:
6080: # this package was previously named wibble2
6081: .if defined(PKG_OPTIONS.wibble2)
6082: PKG_LEGACY_OPTIONS+= ${PKG_OPTIONS.wibble2}
6083: PKG_OPTIONS_DEPRECATED_WARNINGS+= \
6084: "Deprecated variable PKG_OPTIONS.wibble2 used, use ${PKG_OPTIONS_VAR} instead."
6085: .endif
6086:
6087: .include "../../mk/bsd.options.mk"
6088:
6089: # Package-specific option-handling
6090:
6091: ###
6092: ### FOO support
6093: ###
6094: .if !empty(PKG_OPTIONS:Mwibble-foo)
6095: CONFIGURE_ARGS+= --enable-foo
6096: .endif
6097:
6098: ###
6099: ### LDAP support
6100: ###
6101: .if !empty(PKG_OPTIONS:Mldap)
6102: . include "../../databases/openldap-client/buildlink3.mk"
6103: CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap-client}
6104: .endif
6105:
6106: ###
6107: ### database support
6108: ###
6109: .if !empty(PKG_OPTIONS:Mmysql)
6110: . include "../../mk/mysql.buildlink3.mk"
6111: .endif
6112: .if !empty(PKG_OPTIONS:Mpgsql)
6113: . include "../../mk/pgsql.buildlink3.mk"
6114: .endif
6115: </pre>
6116: <p>The first section contains the information about which build
6117: options are supported by the package, and any default options settings
6118: if needed.</p>
1.23 wiz 6119: <div class="orderedlist"><ol class="orderedlist" type="1">
6120: <li class="listitem"><p><code class="varname">PKG_OPTIONS_VAR</code> is the name of the
1.79 snj 6121: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> variable that the user can set to override the default
1.1 dsieger 6122: options. It should be set to
6123: PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em>. Do not set it to
6124: PKG_OPTIONS.${PKGBASE}, since <code class="varname">PKGBASE</code> is not defined
6125: at the point where the options are processed.</p></li>
1.23 wiz 6126: <li class="listitem"><p><code class="varname">PKG_SUPPORTED_OPTIONS</code> is a list of
1.1 dsieger 6127: build options supported by the package.</p></li>
1.23 wiz 6128: <li class="listitem"><p><code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code> is a
1.1 dsieger 6129: list of names of groups of mutually exclusive options. The options in
6130: each group are listed in
6131: <code class="varname">PKG_OPTIONS_GROUP.<em class="replaceable"><code>groupname</code></em></code>.
6132: The most specific setting of any option from the group takes
6133: precedence over all other options in the group. Options from the
6134: groups will be automatically added to
6135: <code class="varname">PKG_SUPPORTED_OPTIONS</code>.</p></li>
1.23 wiz 6136: <li class="listitem"><p><code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> is like
1.1 dsieger 6137: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, but building the
6138: packages will fail if no option from the group is
6139: selected.</p></li>
1.23 wiz 6140: <li class="listitem"><p><code class="varname">PKG_OPTIONS_NONEMPTY_SETS</code> is a list
1.1 dsieger 6141: of names of sets of options. At least one option from each set must
6142: be selected. The options in each set are listed in
6143: <code class="varname">PKG_OPTIONS_SET.<em class="replaceable"><code>setname</code></em></code>.
6144: Options from the sets will be automatically added to
6145: <code class="varname">PKG_SUPPORTED_OPTIONS</code>. Building the package will
6146: fail if no option from the set is selected.</p></li>
1.23 wiz 6147: <li class="listitem"><p><code class="varname">PKG_SUGGESTED_OPTIONS</code> is a list of
1.1 dsieger 6148: build options which are enabled by default.</p></li>
1.23 wiz 6149: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_VARS</code> is a list
1.1 dsieger 6150: of
1.23 wiz 6151: <span class="quote">“<span class="quote"><em class="replaceable"><code>USE_VARIABLE</code></em>:<em class="replaceable"><code>option</code></em></span>”</span>
1.10 hubertf 6152: pairs that map legacy <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> variables to
1.1 dsieger 6153: their option counterparts. Pairs should be added with
1.23 wiz 6154: <span class="quote">“<span class="quote">+=</span>”</span> to keep the listing of global legacy variables. A
1.1 dsieger 6155: warning will be issued if the user uses a legacy
6156: variable.</p></li>
1.23 wiz 6157: <li class="listitem"><p><code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> is a list
1.1 dsieger 6158: of
1.23 wiz 6159: <span class="quote">“<span class="quote"><em class="replaceable"><code>old-option</code></em>:<em class="replaceable"><code>new-option</code></em></span>”</span>
1.1 dsieger 6160: pairs that map options that have been renamed to their new
1.23 wiz 6161: counterparts. Pairs should be added with <span class="quote">“<span class="quote">+=</span>”</span> to keep
1.1 dsieger 6162: the listing of global legacy options. A warning will be issued if
6163: the user uses a legacy option.</p></li>
1.23 wiz 6164: <li class="listitem"><p><code class="varname">PKG_LEGACY_OPTIONS</code> is a list of
1.1 dsieger 6165: options implied by deprecated variables used. This can be used for
6166: cases that neither <code class="varname">PKG_OPTIONS_LEGACY_VARS</code> nor
6167: <code class="varname">PKG_OPTIONS_LEGACY_OPTS</code> can handle, e. g. when
6168: <code class="varname">PKG_OPTIONS_VAR</code> is renamed.</p></li>
1.23 wiz 6169: <li class="listitem"><p><code class="varname">PKG_OPTIONS_DEPRECATED_WARNINGS</code> is
1.1 dsieger 6170: a list of warnings about deprecated variables or options used, and
6171: what to use instead.</p></li>
6172: </ol></div>
6173: <p>A package should never modify
6174: <code class="varname">PKG_DEFAULT_OPTIONS</code> or the variable named in
6175: <code class="varname">PKG_OPTIONS_VAR</code>. These are strictly user-settable.
6176: To suggest a default set of options, use
6177: <code class="varname">PKG_SUGGESTED_OPTIONS</code>.</p>
6178: <p><code class="varname">PKG_OPTIONS_VAR</code> must be defined before
6179: including <code class="filename">bsd.options.mk</code>. If none of
6180: <code class="varname">PKG_SUPPORTED_OPTIONS</code>,
6181: <code class="varname">PKG_OPTIONS_OPTIONAL_GROUPS</code>, and
6182: <code class="varname">PKG_OPTIONS_REQUIRED_GROUPS</code> are defined (as can
6183: happen with platform-specific options if none of them is supported on
6184: the current platform), <code class="varname">PKG_OPTIONS</code> is set to the
6185: empty list and the package is otherwise treated as not using the
6186: options framework.</p>
6187: <p>After the inclusion of <code class="filename">bsd.options.mk</code>, the
6188: variable <code class="varname">PKG_OPTIONS</code> contains the list of selected
6189: build options, properly filtered to remove unsupported and duplicate
6190: options.</p>
6191: <p>The remaining sections contain the logic that is specific to
6192: each option. The correct way to check for an option is to check
6193: whether it is listed in <code class="varname">PKG_OPTIONS</code>:</p>
6194: <pre class="programlisting">
6195: .if !empty(PKG_OPTIONS:M<em class="replaceable"><code>option</code></em>)
6196: </pre>
6197: </div>
1.41 asau 6198: <div class="sect1">
1.1 dsieger 6199: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6200: <a name="option-names"></a>16.3. Option Names</h2></div></div></div>
1.1 dsieger 6201: <p>Options that enable similar features in different packages (like
6202: optional support for a library) should use a common name in all
6203: packages that support it (like the name of the library). If another
6204: package already has an option with the same meaning, use the same
6205: name.</p>
6206: <p>Options that enable features specific to one package, where it's
6207: unlikely that another (unrelated) package has the same (or a similar)
6208: optional feature, should use a name prefixed with
6209: <code class="varname"><em class="replaceable"><code>pkgname</code></em>-</code>.</p>
6210: <p>If a group of related packages share an optional feature
6211: specific to that group, prefix it with the name of the
1.23 wiz 6212: <span class="quote">“<span class="quote">main</span>”</span> package
1.1 dsieger 6213: (e. g. <code class="varname">djbware-errno-hack</code>).</p>
6214: <p>For new options, add a line to
6215: <code class="filename">mk/defaults/options.description</code>. Lines have two
6216: fields, separated by tab. The first field is the option name, the
6217: second its description. The description should be a whole sentence
6218: (starting with an uppercase letter and ending with a period) that
1.23 wiz 6219: describes what enabling the option does. E. g. <span class="quote">“<span class="quote">Enable ispell
6220: support.</span>”</span> The file is sorted by option names.</p>
1.1 dsieger 6221: </div>
1.41 asau 6222: <div class="sect1">
1.7 rillig 6223: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
6224: <a name="option-build"></a>16.4. Determining the options of dependencies</h2></div></div></div>
1.10 hubertf 6225: <p>When writing <a class="link" href="#buildlink3.mk"><code class="filename">buildlink3.mk</code></a> files, it is often necessary to list
1.7 rillig 6226: different dependencies based on the options with which the package was
6227: built. For querying these options, the file
6228: <code class="filename">pkgsrc/mk/pkg-build-options.mk</code> should be used. A
6229: typical example looks like this:</p>
6230: <pre class="programlisting">
6231: pkgbase := libpurple
6232: .include "../../mk/pkg-build-options.mk"
6233:
6234: .if !empty(PKG_BUILD_OPTIONS.libpurple:Mdbus)
6235: ...
6236: .endif
6237: </pre>
6238: <p>Including <code class="filename">pkg-build-options.mk</code> here will set
6239: the variable <code class="varname">PKG_BUILD_OPTIONS.libpurple</code> to the build
6240: options of the libpurple package, which can then be queried like
6241: <code class="varname">PKG_OPTIONS</code> in the <code class="filename">options.mk</code>
6242: file. See the file <code class="filename">pkg-build-options.mk</code> for more
6243: details.</p>
6244: </div>
1.1 dsieger 6245: </div>
1.41 asau 6246: <div class="chapter">
1.1 dsieger 6247: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 6248: <a name="build"></a>Chapter 17. The build process</h2></div></div></div>
1.1 dsieger 6249: <div class="toc">
6250: <p><b>Table of Contents</b></p>
1.100 leot 6251: <dl class="toc">
1.6 rillig 6252: <dt><span class="sect1"><a href="#build.intro">17.1. Introduction</a></span></dt>
6253: <dt><span class="sect1"><a href="#build.prefix">17.2. Program location</a></span></dt>
6254: <dt><span class="sect1"><a href="#build.builddirs">17.3. Directories used during the build process</a></span></dt>
6255: <dt><span class="sect1"><a href="#build.running">17.4. Running a phase</a></span></dt>
1.23 wiz 6256: <dt><span class="sect1"><a href="#build.fetch">17.5. The <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 6257: <dd><dl>
6258: <dt><span class="sect2"><a href="#build.fetch.what">17.5.1. What to fetch and where to get it from</a></span></dt>
6259: <dt><span class="sect2"><a href="#build.fetch.how">17.5.2. How are the files fetched?</a></span></dt>
6260: </dl></dd>
1.23 wiz 6261: <dt><span class="sect1"><a href="#build.checksum">17.6. The <span class="emphasis"><em>checksum</em></span> phase</a></span></dt>
6262: <dt><span class="sect1"><a href="#build.extract">17.7. The <span class="emphasis"><em>extract</em></span> phase</a></span></dt>
6263: <dt><span class="sect1"><a href="#build.patch">17.8. The <span class="emphasis"><em>patch</em></span> phase</a></span></dt>
6264: <dt><span class="sect1"><a href="#build.tools">17.9. The <span class="emphasis"><em>tools</em></span> phase</a></span></dt>
6265: <dt><span class="sect1"><a href="#build.wrapper">17.10. The <span class="emphasis"><em>wrapper</em></span> phase</a></span></dt>
6266: <dt><span class="sect1"><a href="#build.configure">17.11. The <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
6267: <dt><span class="sect1"><a href="#build.build">17.12. The <span class="emphasis"><em>build</em></span> phase</a></span></dt>
6268: <dt><span class="sect1"><a href="#build.test">17.13. The <span class="emphasis"><em>test</em></span> phase</a></span></dt>
6269: <dt><span class="sect1"><a href="#build.install">17.14. The <span class="emphasis"><em>install</em></span> phase</a></span></dt>
6270: <dt><span class="sect1"><a href="#build.package">17.15. The <span class="emphasis"><em>package</em></span> phase</a></span></dt>
1.6 rillig 6271: <dt><span class="sect1"><a href="#build.clean">17.16. Cleaning up</a></span></dt>
6272: <dt><span class="sect1"><a href="#build.helpful-targets">17.17. Other helpful targets</a></span></dt>
1.1 dsieger 6273: </dl>
6274: </div>
1.41 asau 6275: <div class="sect1">
1.1 dsieger 6276: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6277: <a name="build.intro"></a>17.1. Introduction</h2></div></div></div>
1.1 dsieger 6278: <p>This chapter gives a detailed description on how a package is
6279: built. Building a package is separated into different
6280: <span class="emphasis"><em>phases</em></span> (for example <code class="varname">fetch</code>,
6281: <code class="varname">build</code>, <code class="varname">install</code>), all of which are
1.18 snj 6282: described in the following sections. Each phase is split into
1.1 dsieger 6283: so-called <span class="emphasis"><em>stages</em></span>, which take the name of the
6284: containing phase, prefixed by one of <code class="varname">pre-</code>,
6285: <code class="varname">do-</code> or <code class="varname">post-</code>. (Examples are
6286: <code class="varname">pre-configure</code>, <code class="varname">post-build</code>.) Most
6287: of the actual work is done in the <code class="varname">do-*</code> stages.</p>
6288: <p>Never override the regular targets (like
6289: <code class="varname">fetch</code>), if you have to, override the
6290: <code class="varname">do-*</code> ones instead.</p>
6291: <p>The basic steps for building a program are always the same. First
6292: the program's source (<span class="emphasis"><em>distfile</em></span>) must be brought to
6293: the local system and then extracted. After any pkgsrc-specific patches
6294: to compile properly are applied, the software can be configured, then
6295: built (usually by compiling), and finally the generated binaries, etc.
6296: can be put into place on the system.</p>
6297: <p>To get more details about what is happening at each step,
6298: you can set the <code class="varname">PKG_VERBOSE</code> variable, or the
6299: <code class="varname">PATCH_DEBUG</code> variable if you are just interested
6300: in more details about the <span class="emphasis"><em>patch</em></span> step.</p>
6301: </div>
1.41 asau 6302: <div class="sect1">
1.1 dsieger 6303: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6304: <a name="build.prefix"></a>17.2. Program location</h2></div></div></div>
1.1 dsieger 6305: <p>Before outlining the process performed by the NetBSD package system in
6306: the next section, here's a brief discussion on where programs are
6307: installed, and which variables influence this.</p>
6308: <p>The automatic variable <code class="varname">PREFIX</code> indicates
6309: where all files of the final program shall be installed. It is
6310: usually set to <code class="varname">LOCALBASE</code>
6311: (<code class="filename">/usr/pkg</code>), or <code class="varname">CROSSBASE</code>
6312: for pkgs in the <code class="filename">cross</code> category. The value of
6313: <code class="varname">PREFIX</code> needs to be put
6314: into the various places in the program's source where paths to
1.10 hubertf 6315: these files are encoded. See <a class="xref" href="#components.patches" title="11.3. patches/*">Section 11.3, “patches/*”</a> and <a class="xref" href="#fixes.libtool" title="19.3.1. Shared libraries - libtool">Section 19.3.1, “Shared libraries - libtool”</a> for more details.</p>
1.1 dsieger 6316: <p>When choosing which of these variables to use,
6317: follow the following rules:</p>
1.41 asau 6318: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 6319: <li class="listitem"><p><code class="varname">PREFIX</code> always points to the location
1.1 dsieger 6320: where the current pkg will be installed. When referring to a
6321: pkg's own installation path, use
1.23 wiz 6322: <span class="quote">“<span class="quote">${PREFIX}</span>”</span>.</p></li>
6323: <li class="listitem"><p><code class="varname">LOCALBASE</code> is where all non-X11 pkgs
1.1 dsieger 6324: are installed. If you need to construct a -I or -L argument
6325: to the compiler to find includes and libraries installed by
1.23 wiz 6326: another non-X11 pkg, use <span class="quote">“<span class="quote">${LOCALBASE}</span>”</span>. The name
1.1 dsieger 6327: <code class="varname">LOCALBASE</code> stems from FreeBSD, which
6328: installed all packages in <code class="filename">/usr/local</code>. As
6329: pkgsrc leaves <code class="filename">/usr/local</code> for the system
6330: administrator, this variable is a misnomer.</p></li>
1.23 wiz 6331: <li class="listitem"><p><code class="varname">X11BASE</code> is where the actual X11
1.1 dsieger 6332: distribution (from xsrc, etc.) is installed. When looking for
6333: <span class="emphasis"><em>standard</em></span> X11 includes (not those
1.23 wiz 6334: installed by a package), use <span class="quote">“<span class="quote">${X11BASE}</span>”</span>.</p></li>
1.99 sevan 6335: <li class="listitem"><p>X11-based packages using imake must set
6336: <code class="varname">USE_IMAKE</code> to be installed correctly under
6337: <code class="varname">LOCALBASE</code>.</p></li>
1.23 wiz 6338: <li class="listitem">
1.99 sevan 6339: <p>To determine the prefix of an
1.1 dsieger 6340: installed package, the <code class="varname">EVAL_PREFIX</code>
6341: definition can be used. It takes pairs in the format
1.79 snj 6342: <span class="quote">“<span class="quote">DIRNAME=<package></span>”</span>, and the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
1.1 dsieger 6343: variable <code class="varname">DIRNAME</code> will be set to the prefix
6344: of the installed package <package>, or
1.99 sevan 6345: <span class="quote">“<span class="quote">${PREFIX}</span>”</span> if the package is not
1.1 dsieger 6346: installed.</p>
6347: <p>This is best illustrated by example.</p>
6348: <p>The following lines are taken from
6349: <code class="filename">pkgsrc/wm/scwm/Makefile</code>:</p>
6350: <pre class="programlisting">
6351: EVAL_PREFIX+= GTKDIR=gtk+
6352: CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE:Q}
6353: CONFIGURE_ARGS+= --with-gtk-prefix=${GTKDIR:Q}
6354: CONFIGURE_ARGS+= --enable-multibyte
6355: </pre>
6356: <p>Specific defaults can be defined for the packages
6357: evaluated using <code class="varname">EVAL_PREFIX</code>, by using a
6358: definition of the form:</p>
6359: <pre class="programlisting">
6360: GTKDIR_DEFAULT= ${LOCALBASE}
6361: </pre>
6362: <p>where <code class="varname">GTKDIR</code> corresponds
6363: to the first definition in
6364: the <code class="varname">EVAL_PREFIX</code> pair.</p>
6365: </li>
1.23 wiz 6366: <li class="listitem"><p>Within <code class="filename">${PREFIX}</code>, packages should
1.79 snj 6367: install files according to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?hier+7+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">hier</span>(7)</span></a>, with the exception that
1.1 dsieger 6368: manual pages go into <code class="filename">${PREFIX}/man</code>, not
6369: <code class="filename">${PREFIX}/share/man</code>.</p></li>
6370: </ul></div>
6371: </div>
1.41 asau 6372: <div class="sect1">
1.1 dsieger 6373: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6374: <a name="build.builddirs"></a>17.3. Directories used during the build process</h2></div></div></div>
1.14 jmcneill 6375: <p>When building a package, various directories are used to store
1.1 dsieger 6376: source files, temporary files, pkgsrc-internal files, and so on. These
6377: directories are explained here.</p>
6378: <p>Some of the directory variables contain relative pathnames. There
6379: are two common base directories for these relative directories:
6380: <code class="varname">PKGSRCDIR/PKGPATH</code> is used for directories that are
6381: pkgsrc-specific. <code class="varname">WRKSRC</code> is used for directories
6382: inside the package itself.</p>
1.41 asau 6383: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6384: <dt><span class="term"><code class="varname">PKGSRCDIR</code></span></dt>
6385: <dd><p>This is an absolute pathname that points to the pkgsrc
6386: root directory. Generally, you don't need
6387: it.</p></dd>
6388: <dt><span class="term"><code class="varname">PKGDIR</code></span></dt>
6389: <dd><p>This is an absolute pathname that points to the
6390: current package.</p></dd>
6391: <dt><span class="term"><code class="varname">PKGPATH</code></span></dt>
6392: <dd><p>This is a pathname relative to
6393: <code class="varname">PKGSRCDIR</code> that points to the current
6394: package.</p></dd>
6395: <dt><span class="term"><code class="varname">WRKDIR</code></span></dt>
6396: <dd><p>This is an absolute pathname pointing to the directory
6397: where all work takes place. The distfiles are extracted to this
6398: directory. It also contains temporary directories and log files used by
6399: the various pkgsrc frameworks, like <span class="emphasis"><em>buildlink</em></span> or
6400: the <span class="emphasis"><em>wrappers</em></span>.</p></dd>
6401: <dt><span class="term"><code class="varname">WRKSRC</code></span></dt>
6402: <dd><p>This is an absolute pathname pointing to the directory
6403: where the distfiles are extracted. It is usually a direct subdirectory
6404: of <code class="varname">WRKDIR</code>, and often it's the only directory entry
6405: that isn't hidden. This variable may be changed by a package
6406: <code class="filename">Makefile</code>.</p></dd>
6407: </dl></div>
1.14 jmcneill 6408: <p>The <code class="varname">CREATE_WRKDIR_SYMLINK</code> definition takes either
6409: the value <span class="emphasis"><em>yes</em></span> or <span class="emphasis"><em>no</em></span> and defaults
1.15 rillig 6410: to <span class="emphasis"><em>no</em></span>. It indicates whether a symbolic link to the
1.14 jmcneill 6411: <code class="varname">WRKDIR</code> is to be created in the pkgsrc entry's directory.
6412: If users would like to have their pkgsrc trees behave in a
6413: read-only manner, then the value of
6414: <code class="varname">CREATE_WRKDIR_SYMLINK</code> should be set to
6415: <span class="emphasis"><em>no</em></span>.</p>
1.1 dsieger 6416: </div>
1.41 asau 6417: <div class="sect1">
1.1 dsieger 6418: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6419: <a name="build.running"></a>17.4. Running a phase</h2></div></div></div>
1.10 hubertf 6420: <p>You can run a particular phase by typing <span class="command"><strong>make
1.1 dsieger 6421: phase</strong></span>, where <span class="emphasis"><em>phase</em></span> is the name of the
6422: phase. This will automatically run all phases that are required for this
6423: phase. The default phase is <code class="varname">build</code>, that is, when you
1.10 hubertf 6424: run <span class="command"><strong>make</strong></span> without parameters in a package directory,
1.1 dsieger 6425: the package will be built, but not installed.</p>
6426: </div>
1.41 asau 6427: <div class="sect1">
1.1 dsieger 6428: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6429: <a name="build.fetch"></a>17.5. The <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
1.1 dsieger 6430: <p>The first step in building a package is to fetch the
6431: distribution files (distfiles) from the sites that are providing
6432: them. This is the task of the <span class="emphasis"><em>fetch</em></span>
6433: phase.</p>
1.41 asau 6434: <div class="sect2">
1.1 dsieger 6435: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 6436: <a name="build.fetch.what"></a>17.5.1. What to fetch and where to get it from</h3></div></div></div>
1.1 dsieger 6437: <p>In simple cases, <code class="varname">MASTER_SITES</code>
6438: defines all URLs from where the distfile, whose name is
6439: derived from the <code class="varname">DISTNAME</code> variable, is
6440: fetched. The more complicated cases are described
6441: below.</p>
6442: <p>The variable <code class="varname">DISTFILES</code> specifies
6443: the list of distfiles that have to be fetched. Its value
1.66 asau 6444: defaults to <code class="literal">${DEFAULT_DISTFILES}</code> and
6445: its value is <code class="literal">${DISTNAME}${EXTRACT_SUFX}</code>,
1.1 dsieger 6446: so that most packages don't need to define it at all.
6447: <code class="varname">EXTRACT_SUFX</code> is
6448: <code class="literal">.tar.gz</code> by default, but can be changed
6449: freely. Note that if your package requires additional
6450: distfiles to the default one, you cannot just append the
6451: additional filenames using the <code class="literal">+=</code>
6452: operator, but you have write for example:</p>
6453: <pre class="programlisting">
1.66 asau 6454: DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
1.1 dsieger 6455: </pre>
6456: <p>Each distfile is fetched from a list of sites, usually
6457: <code class="varname">MASTER_SITES</code>. If the package has multiple
6458: <code class="varname">DISTFILES</code> or multiple
6459: <code class="varname">PATCHFILES</code> from different sites, you can
6460: set
6461: <code class="varname">SITES.<em class="replaceable"><code>distfile</code></em></code>
6462: to the list of URLs where the file
6463: <code class="filename"><em class="replaceable"><code>distfile</code></em></code>
6464: (including the suffix) can be found.</p>
6465: <pre class="programlisting">
6466: DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
6467: DISTFILES+= foo-file.tar.gz
6468: SITES.foo-file.tar.gz= \
6469: http://www.somewhere.com/somehow/ \
6470: http://www.somewhereelse.com/mirror/somehow/
6471: </pre>
6472: <p>When actually fetching the distfiles, each item from
6473: <code class="varname">MASTER_SITES</code> or
6474: <code class="varname">SITES.*</code> gets the name of each distfile
6475: appended to it, without an intermediate slash. Therefore,
6476: all site values have to end with a slash or other separator
6477: character. This allows for example to set
6478: <code class="varname">MASTER_SITES</code> to a URL of a CGI script
6479: that gets the name of the distfile as a parameter. In this
6480: case, the definition would look like:</p>
6481: <pre class="programlisting">
6482: MASTER_SITES= http://www.example.com/download.cgi?file=
6483: </pre>
1.22 jakllsch 6484: <p> The exception to this rule are URLs starting with a dash.
1.66 asau 6485: In that case the URL is taken as is, fetched and the result
6486: stored under the name of the distfile. You can use this style
6487: for the case when the download URL style does not match the
6488: above common case. For example, if permanent download URL is a
6489: redirector to the real download URL, or the download file name
6490: is offered by an HTTP Content-Disposition header. In the
6491: following example, <code class="filename">foo-1.0.0.tar.gz</code> will be
6492: created instead of the default
6493: <code class="filename">v1.0.0.tar.gz</code>.</p>
6494: <pre class="programlisting">
6495: DISTNAME= foo-1.0.0
6496: MASTER_SITES= -http://www.example.com/archive/v1.0.0.tar.gz
6497: </pre>
1.1 dsieger 6498: <p>There are some predefined values for
6499: <code class="varname">MASTER_SITES</code>, which can be used in
6500: packages. The names of the variables should speak for
6501: themselves.</p>
6502: <pre class="programlisting">
6503: ${MASTER_SITE_APACHE}
6504: ${MASTER_SITE_BACKUP}
6505: ${MASTER_SITE_CYGWIN}
6506: ${MASTER_SITE_DEBIAN}
6507: ${MASTER_SITE_FREEBSD}
6508: ${MASTER_SITE_FREEBSD_LOCAL}
6509: ${MASTER_SITE_GENTOO}
6510: ${MASTER_SITE_GNOME}
6511: ${MASTER_SITE_GNU}
6512: ${MASTER_SITE_GNUSTEP}
1.66 asau 6513: ${MASTER_SITE_HASKELL_HACKAGE}
1.1 dsieger 6514: ${MASTER_SITE_IFARCHIVE}
6515: ${MASTER_SITE_KDE}
6516: ${MASTER_SITE_MOZILLA}
1.66 asau 6517: ${MASTER_SITE_MOZILLA_ALL}
6518: ${MASTER_SITE_MOZILLA_ESR}
1.1 dsieger 6519: ${MASTER_SITE_MYSQL}
1.66 asau 6520: ${MASTER_SITE_NETLIB}
1.1 dsieger 6521: ${MASTER_SITE_OPENOFFICE}
1.98 ryoon 6522: ${MASTER_SITE_OSDN}
1.1 dsieger 6523: ${MASTER_SITE_PERL_CPAN}
6524: ${MASTER_SITE_PGSQL}
1.66 asau 6525: ${MASTER_SITE_RUBYGEMS}
1.1 dsieger 6526: ${MASTER_SITE_R_CRAN}
6527: ${MASTER_SITE_SOURCEFORGE}
6528: ${MASTER_SITE_SUNSITE}
6529: ${MASTER_SITE_SUSE}
6530: ${MASTER_SITE_TEX_CTAN}
6531: ${MASTER_SITE_XCONTRIB}
6532: ${MASTER_SITE_XEMACS}
1.66 asau 6533: ${MASTER_SITE_XORG}
1.1 dsieger 6534: </pre>
6535: <p>Some explanations for the less self-explaining ones:
6536: <code class="varname">MASTER_SITE_BACKUP</code> contains backup sites
1.26 wiz 6537: 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
1.25 spz 6538: 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>
1.1 dsieger 6539: <p>If you choose one of these predefined sites, you may
6540: want to specify a subdirectory of that site. Since these
6541: macros may expand to more than one actual site, you
6542: <span class="emphasis"><em>must</em></span> use the following construct to
6543: specify a subdirectory:</p>
6544: <pre class="programlisting">
6545: MASTER_SITES= ${MASTER_SITE_GNU:=subdirectory/name/}
6546: MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/}
6547: </pre>
6548: <p>Note the trailing slash after the subdirectory
6549: name.</p>
6550: </div>
1.41 asau 6551: <div class="sect2">
1.1 dsieger 6552: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 6553: <a name="build.fetch.how"></a>17.5.2. How are the files fetched?</h3></div></div></div>
1.1 dsieger 6554: <p>The <span class="emphasis"><em>fetch</em></span> phase makes sure that
6555: all the distfiles exist in a local directory
6556: (<code class="varname">DISTDIR</code>, which can be set by the pkgsrc
6557: user). If the files do not exist, they are fetched using
6558: commands of the form</p>
6559: <pre class="programlisting">
6560: ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
6561: </pre>
6562: <p>where <code class="literal">${site}</code> varies through
6563: several possibilities in turn: first,
6564: <code class="varname">MASTER_SITE_OVERRIDE</code> is tried, then the
6565: sites specified in either <code class="varname">SITES.file</code> if
6566: defined, else <code class="varname">MASTER_SITES</code> or
6567: <code class="varname">PATCH_SITES</code>, as applies, then finally the
6568: value of <code class="varname">MASTER_SITE_BACKUP</code>. The order of
6569: all except the first and the last can be optionally sorted
6570: by the user, via setting either
6571: <code class="varname">MASTER_SORT_RANDOM</code>, and
6572: <code class="varname">MASTER_SORT_AWK</code> or
6573: <code class="varname">MASTER_SORT_REGEX</code>.</p>
1.16 jnemeth 6574: <p> The specific command and arguments used depend on the
6575: <code class="varname">FETCH_USING</code> parameter. The example above is
6576: for <code class="literal">FETCH_USING=custom</code>.</p>
1.1 dsieger 6577: <p>The distfiles mirror run by the NetBSD Foundation uses the
6578: <span class="emphasis"><em>mirror-distfiles</em></span> target to mirror the
6579: distfiles, if they are freely distributable. Packages setting
6580: <code class="varname">NO_SRC_ON_FTP</code> (usually to
1.23 wiz 6581: <span class="quote">“<span class="quote">${RESTRICTED}</span>”</span>) will not have their distfiles
1.1 dsieger 6582: mirrored.</p>
6583: </div>
6584: </div>
1.41 asau 6585: <div class="sect1">
1.1 dsieger 6586: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6587: <a name="build.checksum"></a>17.6. The <span class="emphasis"><em>checksum</em></span> phase</h2></div></div></div>
1.1 dsieger 6588: <p>After the distfile(s) are fetched, their checksum is
6589: generated and compared with the checksums stored in the
6590: distinfo file. If the checksums don't match, the build is
6591: aborted. This is to ensure the same distfile is used for
6592: building, and that the distfile wasn't changed, e.g. by some
6593: malign force, deliberately changed distfiles on the master
6594: distribution site or network lossage.</p>
6595: </div>
1.41 asau 6596: <div class="sect1">
1.1 dsieger 6597: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6598: <a name="build.extract"></a>17.7. The <span class="emphasis"><em>extract</em></span> phase</h2></div></div></div>
1.1 dsieger 6599: <p>When the distfiles are present on the local system, they
6600: need to be extracted, as they usually come in the form of some
6601: compressed archive format.</p>
6602: <p>By default, all <code class="varname">DISTFILES</code> are
6603: extracted. If you only need some of them, you can set the
6604: <code class="varname">EXTRACT_ONLY</code> variable to the list of those
6605: files.</p>
6606: <p>Extracting the files is usually done by a little
6607: program, <code class="filename">mk/extract/extract</code>, which
6608: already knows how to extract various archive formats, so most
6609: likely you will not need to change anything here. But if you
6610: need, the following variables may help you:</p>
1.41 asau 6611: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6612: <dt><span class="term"><code class="varname">EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}</code></span></dt>
6613: <dd><p>Use these variables to override the default
6614: options for an extract command, which are defined in
6615: <code class="filename">mk/extract/extract</code>.</p></dd>
6616: <dt><span class="term"><code class="varname">EXTRACT_USING</code></span></dt>
6617: <dd><p>This variable can be set to
1.14 jmcneill 6618: <code class="literal">bsdtar</code>, <code class="literal">gtar</code>, <code class="literal">nbtar</code>
6619: (which is the default value), <code class="literal">pax</code>, or an
1.1 dsieger 6620: absolute pathname pointing to the command with which tar
1.14 jmcneill 6621: archives should be extracted. It is preferred to choose bsdtar over gtar
6622: if NetBSD's pax-as-tar is not good enough.</p></dd>
1.1 dsieger 6623: </dl></div>
6624: <p>If the <code class="filename">extract</code> program doesn't
6625: serve your needs, you can also override the
6626: <code class="varname">EXTRACT_CMD</code> variable, which holds the
6627: command used for extracting the files. This command is
6628: executed in the <code class="filename">${WRKSRC}</code>
6629: directory. During execution of this command, the shell
6630: variable <code class="varname">extract_file</code> holds the absolute
6631: pathname of the file that is going to be extracted.</p>
6632: <p>And if that still does not suffice, you can override the
6633: <code class="varname">do-extract</code> target in the package
6634: Makefile.</p>
6635: </div>
1.41 asau 6636: <div class="sect1">
1.1 dsieger 6637: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6638: <a name="build.patch"></a>17.8. The <span class="emphasis"><em>patch</em></span> phase</h2></div></div></div>
1.1 dsieger 6639: <p>After extraction, all the patches named by the
6640: <code class="varname">PATCHFILES</code>, those present in the patches
6641: subdirectory of the package as well as in
6642: $LOCALPATCHES/$PKGPATH (e.g.
6643: <code class="filename">/usr/local/patches/graphics/png</code>) are
6644: applied. Patchfiles ending in <code class="filename">.Z</code> or
6645: <code class="filename">.gz</code> are uncompressed before they are
6646: applied, files ending in <code class="filename">.orig</code> or
6647: <code class="filename">.rej</code> are ignored. Any special options to
1.79 snj 6648: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
1.10 hubertf 6649: <code class="varname">PATCH_DIST_ARGS</code>. See <a class="xref" href="#components.patches" title="11.3. patches/*">Section 11.3, “patches/*”</a> for more details.</p>
1.79 snj 6650: <p>By default <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given special args to make
1.1 dsieger 6651: it fail if the patches apply with some lines of fuzz. Please
6652: fix (regen) the patches so that they apply cleanly. The
6653: rationale behind this is that patches that don't apply cleanly
6654: may end up being applied in the wrong place, and cause severe
6655: harm there.</p>
6656: </div>
1.41 asau 6657: <div class="sect1">
1.1 dsieger 6658: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6659: <a name="build.tools"></a>17.9. The <span class="emphasis"><em>tools</em></span> phase</h2></div></div></div>
1.10 hubertf 6660: <p>This is covered in <a class="xref" href="#tools" title="Chapter 18. Tools needed for building or running">Chapter 18, <i>Tools needed for building or running</i></a>.
1.1 dsieger 6661: </p>
6662: </div>
1.41 asau 6663: <div class="sect1">
1.1 dsieger 6664: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6665: <a name="build.wrapper"></a>17.10. The <span class="emphasis"><em>wrapper</em></span> phase</h2></div></div></div>
1.1 dsieger 6666: <p>This phase creates wrapper programs for the compilers and
6667: linkers. The following variables can be used to tweak the
6668: wrappers.</p>
1.41 asau 6669: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6670: <dt><span class="term"><code class="varname">ECHO_WRAPPER_MSG</code></span></dt>
6671: <dd><p>The command used to print progress
6672: messages. Does nothing by default. Set to
6673: <code class="literal">${ECHO}</code> to see the progress
6674: messages.</p></dd>
6675: <dt><span class="term"><code class="varname">WRAPPER_DEBUG</code></span></dt>
6676: <dd><p>This variable can be set to
6677: <code class="literal">yes</code> (default) or <code class="literal">no</code>,
6678: depending on whether you want additional information in the
6679: wrapper log file.</p></dd>
6680: <dt><span class="term"><code class="varname">WRAPPER_UPDATE_CACHE</code></span></dt>
6681: <dd><p>This variable can be set to
6682: <code class="literal">yes</code> or <code class="literal">no</code>, depending
6683: on whether the wrapper should use its cache, which will
6684: improve the speed. The default value is
6685: <code class="literal">yes</code>, but is forced to
6686: <code class="literal">no</code> if the platform does not support
6687: it.</p></dd>
6688: <dt><span class="term"><code class="varname">WRAPPER_REORDER_CMDS</code></span></dt>
6689: <dd><p>A list of reordering commands. A reordering
6690: command has the form
6691: <code class="literal">reorder:l:<em class="replaceable"><code>lib1</code></em>:<em class="replaceable"><code>lib2</code></em></code>.
6692: It ensures that that
6693: <code class="literal">-l<em class="replaceable"><code>lib1</code></em></code> occurs
6694: before <code class="literal">-l<em class="replaceable"><code>lib2</code></em></code>.
6695: </p></dd>
6696: <dt><span class="term"><code class="varname">WRAPPER_TRANSFORM_CMDS</code></span></dt>
6697: <dd><p>A list of transformation commands. [TODO:
6698: investigate further]</p></dd>
6699: </dl></div>
6700: </div>
1.41 asau 6701: <div class="sect1">
1.1 dsieger 6702: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6703: <a name="build.configure"></a>17.11. The <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
1.1 dsieger 6704: <p>Most pieces of software need information on the header
6705: files, system calls, and library routines which are available
6706: on the platform they run on. The process of determining this
6707: information is known as configuration, and is usually
6708: automated. In most cases, a script is supplied with the
6709: distfiles, and its invocation results in generation of header
6710: files, Makefiles, etc.</p>
6711: <p>If the package contains a configure script, this can be
6712: invoked by setting <code class="varname">HAS_CONFIGURE</code> to
1.23 wiz 6713: <span class="quote">“<span class="quote">yes</span>”</span>. If the configure script is a GNU autoconf
1.1 dsieger 6714: script, you should set <code class="varname">GNU_CONFIGURE</code> to
1.23 wiz 6715: <span class="quote">“<span class="quote">yes</span>”</span> instead. What happens in the
1.1 dsieger 6716: <span class="emphasis"><em>configure</em></span> phase is roughly:</p>
6717: <pre class="programlisting">
6718: .for d in ${CONFIGURE_DIRS}
6719: cd ${WRKSRC} \
6720: && cd ${d} \
6721: && env ${CONFIGURE_ENV} ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
6722: .endfor
6723: </pre>
6724: <p><code class="varname">CONFIGURE_DIRS</code> (default:
1.23 wiz 6725: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
1.1 dsieger 6726: <code class="varname">WRKSRC</code>. In each of these directories, the
6727: configure script is run with the environment
6728: <code class="varname">CONFIGURE_ENV</code> and arguments
6729: <code class="varname">CONFIGURE_ARGS</code>. The variables
6730: <code class="varname">CONFIGURE_ENV</code>,
6731: <code class="varname">CONFIGURE_SCRIPT</code> (default:
1.23 wiz 6732: <span class="quote">“<span class="quote">./configure</span>”</span>) and
1.1 dsieger 6733: <code class="varname">CONFIGURE_ARGS</code> may all be changed by the
6734: package.</p>
1.37 wiz 6735: <p>If the program uses the Perl way of configuration (mainly Perl
6736: modules, but not only), i.e. a file called
6737: <code class="filename">Makefile.PL</code>, it should include
6738: <code class="filename">../../lang/perl5/module.mk</code>. To set any parameter for
6739: <code class="filename">Makefile.PL</code> use the <code class="varname">MAKE_PARAMS</code>
6740: variable (e.g., <code class="literal">MAKE_PARAMS+=foo=bar</code></p>
1.1 dsieger 6741: <p>If the program uses an <code class="filename">Imakefile</code>
6742: for configuration, the appropriate steps can be invoked by
6743: setting <code class="varname">USE_IMAKE</code> to
1.99 sevan 6744: <span class="quote">“<span class="quote">yes</span>”</span>. If you only need xmkmf, add it to <code class="varname">USE_TOOLS</code>.
6745: You can add variables to xmkmf's environment by adding them to the
1.1 dsieger 6746: <code class="varname">SCRIPTS_ENV</code> variable.</p>
1.11 rillig 6747: <p>If the program uses <code class="filename">cmake</code>
6748: for configuration, the appropriate steps can be invoked by
1.23 wiz 6749: setting <code class="varname">USE_CMAKE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.
1.11 rillig 6750: You can add variables to cmake's environment by adding them to the
6751: <code class="varname">CONFIGURE_ENV</code> variable and arguments to cmake
6752: by adding them to the <code class="varname">CMAKE_ARGS</code> variable.
6753: The top directory argument is given by the
6754: <code class="varname">CMAKE_ARG_PATH</code> variable, that defaults to
1.23 wiz 6755: <span class="quote">“<span class="quote">.</span>”</span> (relative to <code class="varname">CONFIGURE_DIRS</code>)</p>
1.1 dsieger 6756: <p>If there is no configure step at all, set
1.23 wiz 6757: <code class="varname">NO_CONFIGURE</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 6758: </div>
1.41 asau 6759: <div class="sect1">
1.1 dsieger 6760: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6761: <a name="build.build"></a>17.12. The <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.1 dsieger 6762: <p>For building a package, a rough equivalent of the
6763: following code is executed.</p>
6764: <pre class="programlisting">
6765: .for d in ${BUILD_DIRS}
6766: cd ${WRKSRC} \
6767: && cd ${d} \
6768: && env ${MAKE_ENV} \
6769: ${MAKE_PROGRAM} ${BUILD_MAKE_FLAGS} \
6770: -f ${MAKE_FILE} \
6771: ${BUILD_TARGET}
6772: .endfor
6773: </pre>
6774: <p><code class="varname">BUILD_DIRS</code> (default:
1.23 wiz 6775: <span class="quote">“<span class="quote">.</span>”</span>) is a list of pathnames relative to
1.1 dsieger 6776: <code class="varname">WRKSRC</code>. In each of these directories,
6777: <code class="varname">MAKE_PROGRAM</code> is run with the environment
6778: <code class="varname">MAKE_ENV</code> and arguments
6779: <code class="varname">BUILD_MAKE_FLAGS</code>. The variables
6780: <code class="varname">MAKE_ENV</code>,
6781: <code class="varname">BUILD_MAKE_FLAGS</code>,
6782: <code class="varname">MAKE_FILE</code> and
6783: <code class="varname">BUILD_TARGET</code> may all be changed by the
6784: package.</p>
6785: <p>The default value of <code class="varname">MAKE_PROGRAM</code> is
1.23 wiz 6786: <span class="quote">“<span class="quote">gmake</span>”</span> if <code class="varname">USE_TOOLS</code> contains
6787: <span class="quote">“<span class="quote">gmake</span>”</span>, <span class="quote">“<span class="quote">make</span>”</span> otherwise. The
1.1 dsieger 6788: default value of <code class="varname">MAKE_FILE</code> is
1.23 wiz 6789: <span class="quote">“<span class="quote">Makefile</span>”</span>, and <code class="varname">BUILD_TARGET</code>
6790: defaults to <span class="quote">“<span class="quote">all</span>”</span>.</p>
1.1 dsieger 6791: <p>If there is no build step at all, set
1.23 wiz 6792: <code class="varname">NO_BUILD</code> to <span class="quote">“<span class="quote">yes</span>”</span>.</p>
1.1 dsieger 6793: </div>
1.41 asau 6794: <div class="sect1">
1.1 dsieger 6795: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6796: <a name="build.test"></a>17.13. The <span class="emphasis"><em>test</em></span> phase</h2></div></div></div>
1.1 dsieger 6797: <p>[TODO]</p>
6798: </div>
1.41 asau 6799: <div class="sect1">
1.1 dsieger 6800: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6801: <a name="build.install"></a>17.14. The <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
1.1 dsieger 6802: <p>Once the build stage has completed, the final step is to
6803: install the software in public directories, so users can
6804: access the programs and files.</p>
6805: <p>In the <span class="emphasis"><em>install</em></span> phase, a rough
6806: equivalent of the following code is executed. Additionally,
6807: before and after this code, much magic is performed to do
6808: consistency checks, registering the package, and so on.</p>
6809: <pre class="programlisting">
6810: .for d in ${INSTALL_DIRS}
6811: cd ${WRKSRC} \
6812: && cd ${d} \
6813: && env ${MAKE_ENV} \
6814: ${MAKE_PROGRAM} ${INSTALL_MAKE_FLAGS} \
6815: -f ${MAKE_FILE} \
6816: ${INSTALL_TARGET}
6817: .endfor
6818: </pre>
6819: <p>The variable's meanings are analogous to the ones in the
6820: <span class="emphasis"><em>build</em></span> phase.
6821: <code class="varname">INSTALL_DIRS</code> defaults to
6822: <code class="varname">BUILD_DIRS</code>. <code class="varname">INSTALL_TARGET</code>
1.23 wiz 6823: is <span class="quote">“<span class="quote">install</span>”</span> by default, plus
6824: <span class="quote">“<span class="quote">install.man</span>”</span> if <code class="varname">USE_IMAKE</code> is
1.1 dsieger 6825: defined and <code class="varname">NO_INSTALL_MANPAGES</code> is not
6826: defined.</p>
6827: <p>In the <span class="emphasis"><em>install</em></span> phase, the following
6828: variables are useful. They are all variations of the
1.79 snj 6829: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that have the owner, group and
1.1 dsieger 6830: permissions preset. <code class="varname">INSTALL</code> is the plain
6831: install command. The specialized variants, together with their
6832: intended use, are:</p>
1.41 asau 6833: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6834: <dt><span class="term"><code class="varname">INSTALL_PROGRAM_DIR</code></span></dt>
6835: <dd><p>directories that contain
6836: binaries</p></dd>
6837: <dt><span class="term"><code class="varname">INSTALL_SCRIPT_DIR</code></span></dt>
6838: <dd><p>directories that contain
6839: scripts</p></dd>
6840: <dt><span class="term"><code class="varname">INSTALL_LIB_DIR</code></span></dt>
6841: <dd><p>directories that contain shared and static
6842: libraries</p></dd>
6843: <dt><span class="term"><code class="varname">INSTALL_DATA_DIR</code></span></dt>
6844: <dd><p>directories that contain data
6845: files</p></dd>
6846: <dt><span class="term"><code class="varname">INSTALL_MAN_DIR</code></span></dt>
6847: <dd><p>directories that contain man
6848: pages</p></dd>
1.100 leot 6849: <dt><span class="term"><code class="varname">INSTALL_GAME_DIR</code></span></dt>
6850: <dd><p>directories that contain data files for games
6851: </p></dd>
1.1 dsieger 6852: <dt><span class="term"><code class="varname">INSTALL_PROGRAM</code></span></dt>
6853: <dd><p>binaries that can be stripped from debugging
6854: symbols</p></dd>
6855: <dt><span class="term"><code class="varname">INSTALL_SCRIPT</code></span></dt>
6856: <dd><p>binaries that cannot be
6857: stripped</p></dd>
6858: <dt><span class="term"><code class="varname">INSTALL_GAME</code></span></dt>
6859: <dd><p>game
6860: binaries</p></dd>
6861: <dt><span class="term"><code class="varname">INSTALL_LIB</code></span></dt>
6862: <dd><p>shared and static
6863: libraries</p></dd>
6864: <dt><span class="term"><code class="varname">INSTALL_DATA</code></span></dt>
6865: <dd><p>data files</p></dd>
6866: <dt><span class="term"><code class="varname">INSTALL_GAME_DATA</code></span></dt>
6867: <dd><p>data files for
6868: games</p></dd>
6869: <dt><span class="term"><code class="varname">INSTALL_MAN</code></span></dt>
6870: <dd><p>man pages</p></dd>
6871: </dl></div>
6872: <p>Some other variables are:</p>
1.41 asau 6873: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6874: <dt><span class="term"><code class="varname">INSTALLATION_DIRS</code></span></dt>
6875: <dd><p>A list of directories relative to
6876: <code class="varname">PREFIX</code> that are created by pkgsrc at the
6877: beginning of the <span class="emphasis"><em>install</em></span> phase.
6878: The package is supposed to create all needed directories itself
6879: before installing files to it and list all other directories here.
6880: </p></dd>
6881: </dl></div>
6882: <p>In the rare cases that a package shouldn't install anything,
1.23 wiz 6883: set <code class="varname">NO_INSTALL</code> to <span class="quote">“<span class="quote">yes</span>”</span>. This is
1.1 dsieger 6884: mostly relevant for packages in the <code class="filename">regress</code>
6885: category.</p>
6886: </div>
1.41 asau 6887: <div class="sect1">
1.1 dsieger 6888: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6889: <a name="build.package"></a>17.15. The <span class="emphasis"><em>package</em></span> phase</h2></div></div></div>
1.1 dsieger 6890: <p>Once the install stage has completed, a binary package of
6891: the installed files can be built. These binary packages can be
6892: used for quick installation without previous compilation, e.g. by
1.10 hubertf 6893: the <span class="command"><strong>make bin-install</strong></span> or by using
6894: <span class="command"><strong>pkg_add</strong></span>.</p>
1.1 dsieger 6895: <p>By default, the binary packages are created in
6896: <code class="filename">${PACKAGES}/All</code> and symlinks are created in
6897: <code class="filename">${PACKAGES}/<em class="replaceable"><code>category</code></em></code>,
6898: one for each category in the <code class="varname">CATEGORIES</code>
6899: variable. <code class="varname">PACKAGES</code> defaults to
6900: <code class="filename">pkgsrc/packages</code>.</p>
6901: </div>
1.41 asau 6902: <div class="sect1">
1.1 dsieger 6903: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6904: <a name="build.clean"></a>17.16. Cleaning up</h2></div></div></div>
1.1 dsieger 6905: <p>Once you're finished with a package, you can clean the work
1.10 hubertf 6906: directory by running <span class="command"><strong>make clean</strong></span>. If you want
1.1 dsieger 6907: to clean the work directories of all dependencies too, use
1.10 hubertf 6908: <span class="command"><strong>make clean-depends</strong></span>.</p>
1.1 dsieger 6909: </div>
1.41 asau 6910: <div class="sect1">
1.1 dsieger 6911: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 6912: <a name="build.helpful-targets"></a>17.17. Other helpful targets</h2></div></div></div>
1.41 asau 6913: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6914: <dt><span class="term">pre/post-*</span></dt>
6915: <dd><p>For any of the main targets described in the
6916: previous section, two auxiliary targets exist with
1.23 wiz 6917: <span class="quote">“<span class="quote">pre-</span>”</span> and <span class="quote">“<span class="quote">post-</span>”</span> used as a
1.1 dsieger 6918: prefix for the main target's name. These targets are
6919: invoked before and after the main target is called,
6920: allowing extra configuration or installation steps be
6921: performed from a package's Makefile, for example, which
6922: a program's configure script or install target
6923: omitted.</p></dd>
6924: <dt><span class="term">do-*</span></dt>
6925: <dd><p>Should one of the main targets do the wrong thing,
6926: and should there be no variable to fix this, you can
6927: redefine it with the do-* target. (Note that redefining
6928: the target itself instead of the do-* target is a bad
6929: idea, as the pre-* and post-* targets won't be called
6930: anymore, etc.) You will not usually need to do
6931: this.</p></dd>
6932: <dt><span class="term">reinstall</span></dt>
6933: <dd>
1.10 hubertf 6934: <p>If you did a <span class="command"><strong>make install</strong></span> and
1.1 dsieger 6935: you noticed some file was not installed properly, you
6936: can repeat the installation with this target, which will
1.23 wiz 6937: ignore the <span class="quote">“<span class="quote">already installed</span>”</span> flag.</p>
1.1 dsieger 6938: <p>This is the default value of
6939: <code class="varname">DEPENDS_TARGET</code> except in the case of
1.10 hubertf 6940: <span class="command"><strong>make update</strong></span> and <span class="command"><strong>make
1.1 dsieger 6941: package</strong></span>, where the defaults are
1.23 wiz 6942: <span class="quote">“<span class="quote">package</span>”</span> and <span class="quote">“<span class="quote">update</span>”</span>,
1.1 dsieger 6943: respectively.</p>
6944: </dd>
6945: <dt><span class="term">deinstall</span></dt>
6946: <dd>
1.79 snj 6947: <p>This target does a <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> in the
1.1 dsieger 6948: current directory, effectively de-installing the
6949: package. The following variables can be used to tune the
6950: behaviour:</p>
1.41 asau 6951: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 6952: <dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt>
1.79 snj 6953: <dd><p>Add a "-v" to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
1.1 dsieger 6954: <dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt>
6955: <dd><p>Remove all packages that require (depend on)
6956: the given package. This can be used to remove any
6957: packages that may have been pulled in by a given
1.10 hubertf 6958: package, e.g. if <span class="command"><strong>make deinstall
1.1 dsieger 6959: DEINSTALLDEPENDS=1</strong></span> is done in
6960: <code class="filename">pkgsrc/x11/kde</code>, this is
6961: likely to remove whole KDE. Works by adding
1.79 snj 6962: <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
1.1 dsieger 6963: command line.</p></dd>
6964: </dl></div>
6965: </dd>
6966: <dt><span class="term">bin-install</span></dt>
6967: <dd><p>Install a binary package from local disk and via FTP
6968: from a list of sites (see the
6969: <code class="varname">BINPKG_SITES</code> variable), and do a
1.10 hubertf 6970: <span class="command"><strong>make package</strong></span> if no binary package is
1.1 dsieger 6971: available anywhere. The arguments given to
1.10 hubertf 6972: <span class="command"><strong>pkg_add</strong></span> can be set via
1.1 dsieger 6973: <code class="varname">BIN_INSTALL_FLAGS</code> e.g., to do verbose
6974: operation, etc.</p></dd>
1.95 wiz 6975: <dt><span class="term">install-clean</span></dt>
6976: <dd><p>This target removes the state files for the "install" and later
6977: phases so that the "install" target may be re-invoked. This can be
6978: used after editing the PLIST to install the package without
6979: rebuilding it.</p></dd>
6980: <dt><span class="term">build-clean</span></dt>
6981: <dd><p>This target removes the state files for the "build" and later
6982: phases so that the "build" target may be re-invoked.</p></dd>
1.1 dsieger 6983: <dt><span class="term">update</span></dt>
6984: <dd>
6985: <p>This target causes the current package to be
6986: updated to the latest version. The package and all
6987: depending packages first get de-installed, then current
6988: versions of the corresponding packages get compiled and
6989: installed. This is similar to manually noting which
6990: packages are currently installed, then performing a
1.10 hubertf 6991: series of <span class="command"><strong>make deinstall</strong></span> and
6992: <span class="command"><strong>make install</strong></span> (or whatever
1.1 dsieger 6993: <code class="varname">UPDATE_TARGET</code> is set to) for these
6994: packages.</p>
1.23 wiz 6995: <p>You can use the <span class="quote">“<span class="quote">update</span>”</span> target to
1.10 hubertf 6996: resume package updating in case a previous <span class="command"><strong>make
1.1 dsieger 6997: update</strong></span> was interrupted for some reason.
6998: However, in this case, make sure you don't call
1.10 hubertf 6999: <span class="command"><strong>make clean</strong></span> or otherwise remove the
1.1 dsieger 7000: list of dependent packages in <code class="varname">WRKDIR</code>.
7001: Otherwise, you lose the ability to automatically update
7002: the current package along with the dependent packages
7003: you have installed.</p>
1.10 hubertf 7004: <p>Resuming an interrupted <span class="command"><strong>make
1.1 dsieger 7005: update</strong></span> will only work as long as the package
7006: tree remains unchanged. If the source code for one of
7007: the packages to be updated has been changed, resuming
1.10 hubertf 7008: <span class="command"><strong>make update</strong></span> will most certainly
1.1 dsieger 7009: fail!</p>
7010: <p>The following variables can be used either on the
1.10 hubertf 7011: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
7012: alter the behaviour of <span class="command"><strong>make
1.1 dsieger 7013: update</strong></span>:</p>
1.41 asau 7014: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 7015: <dt><span class="term"><code class="varname">UPDATE_TARGET</code></span></dt>
7016: <dd><p>Install target to recursively use for the
7017: updated package and the dependent packages.
7018: Defaults to <code class="varname">DEPENDS_TARGET</code> if
1.23 wiz 7019: set, <span class="quote">“<span class="quote">install</span>”</span> otherwise for
1.10 hubertf 7020: <span class="command"><strong>make update</strong></span>. Other good
1.23 wiz 7021: targets are <span class="quote">“<span class="quote">package</span>”</span> or
7022: <span class="quote">“<span class="quote">bin-install</span>”</span>. Do not set this to
7023: <span class="quote">“<span class="quote">update</span>”</span> or you will get stuck in an
1.1 dsieger 7024: endless loop!</p></dd>
7025: <dt><span class="term"><code class="varname">NOCLEAN</code></span></dt>
7026: <dd><p>Don't clean up after updating. Useful if
7027: you want to leave the work sources of the updated
7028: packages around for inspection or other purposes.
7029: Be sure you eventually clean up the source tree
1.23 wiz 7030: (see the <span class="quote">“<span class="quote">clean-update</span>”</span> target below)
1.1 dsieger 7031: or you may run into troubles with old source code
7032: still lying around on your next
1.10 hubertf 7033: <span class="command"><strong>make</strong></span> or <span class="command"><strong>make
1.1 dsieger 7034: update</strong></span>.</p></dd>
7035: <dt><span class="term"><code class="varname">REINSTALL</code></span></dt>
7036: <dd><p>Deinstall each package before installing
7037: (making <code class="varname">DEPENDS_TARGET</code>). This
7038: may be necessary if the
1.23 wiz 7039: <span class="quote">“<span class="quote">clean-update</span>”</span> target (see below) was
1.10 hubertf 7040: called after interrupting a running <span class="command"><strong>make
1.1 dsieger 7041: update</strong></span>.</p></dd>
7042: <dt><span class="term"><code class="varname">DEPENDS_TARGET</code></span></dt>
7043: <dd><p>Allows you to disable recursion and hardcode
7044: the target for packages. The default is
1.23 wiz 7045: <span class="quote">“<span class="quote">update</span>”</span> for the update target,
1.1 dsieger 7046: facilitating a recursive update of prerequisite
7047: packages. Only set
7048: <code class="varname">DEPENDS_TARGET</code> if you want to
7049: disable recursive updates. Use
7050: <code class="varname">UPDATE_TARGET</code> instead to just
7051: set a specific target for each package to be
1.10 hubertf 7052: installed during <span class="command"><strong>make update</strong></span>
1.1 dsieger 7053: (see above).</p></dd>
7054: </dl></div>
7055: </dd>
7056: <dt><span class="term">clean-update</span></dt>
7057: <dd>
7058: <p>Clean the source tree for all packages that would
1.10 hubertf 7059: get updated if <span class="command"><strong>make update</strong></span> was called
1.1 dsieger 7060: from the current directory. This target should not be
7061: used if the current package (or any of its depending
7062: packages) have already been de-installed (e.g., after
1.10 hubertf 7063: calling <span class="command"><strong>make update</strong></span>) or you may lose
1.1 dsieger 7064: some packages you intended to update. As a rule of
7065: thumb: only use this target <span class="emphasis"><em>before</em></span>
1.10 hubertf 7066: the first time you run <span class="command"><strong>make update</strong></span>
1.1 dsieger 7067: and only if you have a dirty package tree (e.g., if you
7068: used <code class="varname">NOCLEAN</code>).</p>
7069: <p>If you are unsure about whether your tree is
1.10 hubertf 7070: clean, you can either perform a <span class="command"><strong>make
1.1 dsieger 7071: clean</strong></span> at the top of the tree, or use the
7072: following sequence of commands from the directory of the
7073: package you want to update (<span class="emphasis"><em>before</em></span>
1.10 hubertf 7074: running <span class="command"><strong>make update</strong></span> for the first
1.1 dsieger 7075: time, otherwise you lose all the packages you wanted to
7076: update!):</p>
7077: <pre class="screen">
7078: <code class="prompt">#</code> <strong class="userinput"><code>make clean-update</code></strong>
7079: <code class="prompt">#</code> <strong class="userinput"><code>make clean CLEANDEPENDS=YES</code></strong>
7080: <code class="prompt">#</code> <strong class="userinput"><code>make update</code></strong>
7081: </pre>
7082: <p>The following variables can be used either on the
1.10 hubertf 7083: command line or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to alter the behaviour of
7084: <span class="command"><strong>make clean-update</strong></span>:</p>
1.41 asau 7085: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 7086: <dt><span class="term"><code class="varname">CLEAR_DIRLIST</code></span></dt>
1.10 hubertf 7087: <dd><p>After <span class="command"><strong>make clean</strong></span>, do not
1.1 dsieger 7088: reconstruct the list of directories to update for
1.10 hubertf 7089: this package. Only use this if <span class="command"><strong>make
1.1 dsieger 7090: update</strong></span> successfully installed all
7091: packages you wanted to update. Normally, this is
1.10 hubertf 7092: done automatically on <span class="command"><strong>make
1.1 dsieger 7093: update</strong></span>, but may have been suppressed by
7094: the <code class="varname">NOCLEAN</code> variable (see
7095: above).</p></dd>
7096: </dl></div>
7097: </dd>
7098: <dt><span class="term">replace</span></dt>
7099: <dd>
7100: <p>Update the installation of the current package. This
7101: differs from update in that it does not replace dependent
1.79 snj 7102: packages. You will need to install <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html" target="_top"><code class="filename">pkgtools/pkg_tarup</code></a> for this
1.1 dsieger 7103: target to work.</p>
7104: <p><span class="emphasis"><em>Be careful when using this
7105: target!</em></span> There are no guarantees that dependent
7106: packages will still work, in particular they will most
1.10 hubertf 7107: certainly break if you <span class="command"><strong>make replace</strong></span> a
1.1 dsieger 7108: library package whose shared library major version changed
7109: between your installed version and the new one. For this
7110: reason, this target is not officially supported and only
7111: recommended for advanced users.</p>
7112: </dd>
7113: <dt><span class="term">info</span></dt>
1.79 snj 7114: <dd><p>This target invokes <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a> for the current
1.1 dsieger 7115: package. You can use this to check which version of a
7116: package is installed.</p></dd>
7117: <dt><span class="term">index</span></dt>
7118: <dd>
7119: <p>This is a top-level command, i.e. it should be used in
7120: the <code class="filename">pkgsrc</code> directory. It creates a
7121: database of all packages in the local pkgsrc tree, including
7122: dependencies, comment, maintainer, and some other useful
7123: information. Individual entries are created by running
1.10 hubertf 7124: <span class="command"><strong>make describe</strong></span> in the packages'
1.1 dsieger 7125: directories. This index file is saved as
7126: <code class="filename">pkgsrc/INDEX</code>. It can be displayed in
1.10 hubertf 7127: verbose format by running <span class="command"><strong>make
1.1 dsieger 7128: print-index</strong></span>. You can search in it with
1.10 hubertf 7129: <span class="command"><strong>make search
1.1 dsieger 7130: key=<em class="replaceable"><code>something</code></em></strong></span>. You can
7131: extract a list of all packages that depend on a particular
1.10 hubertf 7132: one by running <span class="command"><strong>make show-deps
1.1 dsieger 7133: PKG=<em class="replaceable"><code>somepackage</code></em></strong></span>.</p>
7134: <p>Running this command takes a very long time, some
7135: hours even on fast machines!</p>
7136: </dd>
7137: <dt><span class="term">readme</span></dt>
7138: <dd>
7139: <p>This target generates a
7140: <code class="filename">README.html</code> file, which can be
1.79 snj 7141: viewed using a browser such as <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html" target="_top"><code class="filename">www/firefox</code></a> or <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/links/README.html" target="_top"><code class="filename">www/links</code></a>. The generated files
1.1 dsieger 7142: contain references to any packages which are in the
7143: <code class="varname">PACKAGES</code> directory on the local
7144: host. The generated files can be made to refer to URLs
7145: based on <code class="varname">FTP_PKG_URL_HOST</code> and
7146: <code class="varname">FTP_PKG_URL_DIR</code>. For example, if I
7147: wanted to generate <code class="filename">README.html</code>
7148: files which pointed to binary packages on the local
7149: machine, in the directory
7150: <code class="filename">/usr/packages</code>, set
7151: <code class="varname">FTP_PKG_URL_HOST=file://localhost</code> and
7152: <code class="varname">FTP_PKG_URL_DIR=/usr/packages</code>. The
7153: <code class="varname">${PACKAGES}</code> directory and its
7154: subdirectories will be searched for all the binary
7155: packages.</p>
7156: <p>The target can be run at the toplevel or in category
7157: directories, in which case it descends recursively.</p>
7158: </dd>
7159: <dt><span class="term">readme-all</span></dt>
7160: <dd><p>This is a top-level command, run it in
7161: <code class="filename">pkgsrc</code>. Use this target to create a
7162: file <code class="filename">README-all.html</code> which contains a
7163: list of all packages currently available in the NetBSD
7164: Packages Collection, together with the category they belong
7165: to and a short description. This file is compiled from the
7166: <code class="filename">pkgsrc/*/README.html</code> files, so be sure
1.10 hubertf 7167: to run this <span class="emphasis"><em>after</em></span> a <span class="command"><strong>make
1.1 dsieger 7168: readme</strong></span>.</p></dd>
7169: <dt><span class="term">cdrom-readme</span></dt>
7170: <dd><p>This is very much the same as the
1.23 wiz 7171: <span class="quote">“<span class="quote">readme</span>”</span> target (see above), but is to be
1.1 dsieger 7172: used when generating a pkgsrc tree to be written to a
7173: CD-ROM. This target also produces
7174: <code class="filename">README.html</code> files, and can be made
7175: to refer to URLs based on
7176: <code class="varname">CDROM_PKG_URL_HOST</code> and
7177: <code class="varname">CDROM_PKG_URL_DIR</code>.</p></dd>
7178: <dt><span class="term">show-distfiles</span></dt>
7179: <dd><p>This target shows which distfiles and patchfiles
7180: are needed to build the package
7181: (<code class="varname">ALLFILES</code>, which contains all
7182: <code class="varname">DISTFILES</code> and
7183: <code class="varname">PATCHFILES</code>, but not
7184: <code class="filename">patches/*</code>).</p></dd>
7185: <dt><span class="term">show-downlevel</span></dt>
7186: <dd><p>This target shows nothing if the package is not
7187: installed. If a version of this package is installed,
7188: but is not the version provided in this version of
7189: pkgsrc, then a warning message is displayed. This target
7190: can be used to show which of your installed packages are
7191: downlevel, and so the old versions can be deleted, and
7192: the current ones added.</p></dd>
7193: <dt><span class="term">show-pkgsrc-dir</span></dt>
7194: <dd><p>This target shows the directory in the pkgsrc
7195: hierarchy from which the package can be built and
7196: installed. This may not be the same directory as the one
7197: from which the package was installed. This target is
7198: intended to be used by people who may wish to upgrade
7199: many packages on a single host, and can be invoked from
7200: the top-level pkgsrc Makefile by using the
1.23 wiz 7201: <span class="quote">“<span class="quote">show-host-specific-pkgs</span>”</span> target.</p></dd>
1.1 dsieger 7202: <dt><span class="term">show-installed-depends</span></dt>
7203: <dd><p>This target shows which installed packages match
7204: the current package's <code class="varname">DEPENDS</code>. Useful
7205: if out of date dependencies are causing build
7206: problems.</p></dd>
1.95 wiz 7207: <dt><span class="term">print-build-depends-list</span></dt>
7208: <dd><p>This target shows the list of packages that the current package
7209: depends on for building.</p></dd>
7210: <dt><span class="term">print-run-depends-list</span></dt>
7211: <dd><p>This target shows the list of packages that the current package
7212: depends on for running.</p></dd>
1.1 dsieger 7213: <dt><span class="term">check-shlibs</span></dt>
7214: <dd><p>After a package is installed, check all its
7215: binaries and (on ELF platforms) shared libraries to see
7216: if they find the shared libs they need. Run by default
1.10 hubertf 7217: 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>
1.1 dsieger 7218: <dt><span class="term">print-PLIST</span></dt>
7219: <dd>
1.23 wiz 7220: <p>After a <span class="quote">“<span class="quote">make install</span>”</span> from a new or
1.1 dsieger 7221: upgraded pkg, this prints out an attempt to generate a
1.10 hubertf 7222: new <code class="filename">PLIST</code> from a <span class="command"><strong>find
1.1 dsieger 7223: -newer work/.extract_done</strong></span>. An attempt is made
7224: to care for shared libs etc., but it is
7225: <span class="emphasis"><em>strongly</em></span> recommended to review the
7226: result before putting it into
7227: <code class="filename">PLIST</code>. On upgrades, it's useful to
7228: diff the output of this command against an already
7229: existing <code class="filename">PLIST</code> file.</p>
1.79 snj 7230: <p>If the package installs files via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a> or
1.1 dsieger 7231: other methods that don't update file access times, be
7232: sure to add these files manually to your
1.23 wiz 7233: <code class="filename">PLIST</code>, as the <span class="quote">“<span class="quote">find
7234: -newer</span>”</span> command used by this target won't catch
1.1 dsieger 7235: them!</p>
1.23 wiz 7236: <p>See <a class="xref" href="#print-PLIST" title="13.3. Tweaking output of make print-PLIST">Section 13.3, “Tweaking output of <span class="command"><strong>make print-PLIST</strong></span>”</a> for more
1.1 dsieger 7237: information on this target.</p>
7238: </dd>
7239: <dt><span class="term">bulk-package</span></dt>
7240: <dd>
7241: <p>Used to do bulk builds. If an appropriate binary
7242: package already exists, no action is taken. If not, this
7243: target will compile, install and package it (and its
7244: depends, if <code class="varname">PKG_DEPENDS</code> is set
1.66 asau 7245: properly. See <a class="xref" href="#bulk" title="Chapter 7. Creating binary packages for everything in pkgsrc (bulk builds)">Chapter 7, <i>Creating binary packages for everything in pkgsrc (bulk
7246: builds)</i></a>).
1.1 dsieger 7247: After creating the binary package, the sources, the
7248: just-installed package and its required packages are
7249: removed, preserving free disk space.</p>
7250: <p><span class="emphasis"><em>Beware that this target may deinstall
7251: all packages installed on a system!</em></span></p>
7252: </dd>
7253: <dt><span class="term">bulk-install</span></dt>
7254: <dd>
7255: <p>Used during bulk-installs to install required
7256: packages. If an up-to-date binary package is available,
1.79 snj 7257: it will be installed via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a>. If not,
1.10 hubertf 7258: <span class="command"><strong>make bulk-package</strong></span> will be executed,
1.1 dsieger 7259: but the installed binary won't be removed.</p>
7260: <p>A binary package is considered
1.23 wiz 7261: <span class="quote">“<span class="quote">up-to-date</span>”</span> to be installed via
1.79 snj 7262: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> if:</p>
1.41 asau 7263: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7264: <li class="listitem"><p>None of the package's files
1.1 dsieger 7265: (<code class="filename">Makefile</code>, ...) were modified
7266: since it was built.</p></li>
1.23 wiz 7267: <li class="listitem"><p>None of the package's required (binary)
1.1 dsieger 7268: packages were modified since it was built.</p></li>
7269: </ul></div>
7270: <p><span class="emphasis"><em>Beware that this target may deinstall
7271: all packages installed on a system!</em></span></p>
7272: </dd>
7273: </dl></div>
7274: </div>
7275: </div>
1.41 asau 7276: <div class="chapter">
1.1 dsieger 7277: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 7278: <a name="tools"></a>Chapter 18. Tools needed for building or running</h2></div></div></div>
1.1 dsieger 7279: <div class="toc">
7280: <p><b>Table of Contents</b></p>
1.100 leot 7281: <dl class="toc">
1.6 rillig 7282: <dt><span class="sect1"><a href="#pkgsrc-tools">18.1. Tools for pkgsrc builds</a></span></dt>
7283: <dt><span class="sect1"><a href="#package-tools">18.2. Tools needed by packages</a></span></dt>
7284: <dt><span class="sect1"><a href="#platform-tools">18.3. Tools provided by platforms</a></span></dt>
7285: <dt><span class="sect1"><a href="#tools.questions">18.4. Questions regarding the tools</a></span></dt>
1.1 dsieger 7286: </dl>
7287: </div>
7288: <p>The <code class="varname">USE_TOOLS</code> definition is used both internally
7289: by pkgsrc and also for individual packages to define what commands
7290: are needed for building a package (like <code class="varname">BUILD_DEPENDS</code>)
7291: or for later run-time of an installed packaged (such as
7292: <code class="varname">DEPENDS</code>).
7293: If the native system provides an adequate tool, then in many cases, a pkgsrc
7294: package will not be used.</p>
7295: <p>When building a package, the replacement tools are
7296: made available in a directory (as symlinks or wrapper scripts)
7297: that is early in the executable search path. Just like the buildlink
7298: system, this helps with consistent builds.</p>
7299: <p>A tool may be needed to help build a specific package. For example,
7300: perl, GNU make (gmake) or yacc may be needed.</p>
7301: <p>Also a tool may be needed, for example, because the native system's supplied
7302: tool may be inefficient for building a package with pkgsrc.
7303: For example, a package may need GNU awk, bison (instead of
7304: yacc) or a better sed.</p>
7305: <p>The tools used by a package can be listed by running
1.10 hubertf 7306: <span class="command"><strong>make show-tools</strong></span>.</p>
1.41 asau 7307: <div class="sect1">
1.1 dsieger 7308: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 7309: <a name="pkgsrc-tools"></a>18.1. Tools for pkgsrc builds</h2></div></div></div>
1.1 dsieger 7310: <p>The default set of tools used by pkgsrc is defined in
7311: <code class="filename">bsd.pkg.mk</code>. This includes standard Unix tools,
1.10 hubertf 7312: such as: <span class="command"><strong>cat</strong></span>, <span class="command"><strong>awk</strong></span>,
7313: <span class="command"><strong>chmod</strong></span>, <span class="command"><strong>test</strong></span>, and so on.
1.1 dsieger 7314: These can be seen by running:
1.10 hubertf 7315: <span class="command"><strong>make show-var VARNAME=USE_TOOLS</strong></span>.</p>
1.1 dsieger 7316: <p>If a package needs a specific program to build
7317: then the <code class="varname">USE_TOOLS</code> variable can be used
7318: to define the tools needed.</p>
7319: </div>
1.41 asau 7320: <div class="sect1">
1.1 dsieger 7321: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 7322: <a name="package-tools"></a>18.2. Tools needed by packages</h2></div></div></div>
1.28 wiz 7323: <p>In the following examples, the :run means that it is needed at
7324: run-time (and becomes a DEPENDS).
1.1 dsieger 7325: The default is a build dependency which can be set with
7326: :build. (So in this example, it is the same as gmake:build
7327: and pkg-config:build.)</p>
7328: <pre class="programlisting">
7329: USE_TOOLS+= gmake perl:run pkg-config
7330: </pre>
7331: <p>When using the tools framework, a
7332: <code class="varname">TOOLS_PATH.foo</code> variable is defined
7333: which contains the full path to the appropriate tool. For example,
1.23 wiz 7334: <code class="varname">TOOLS_PATH.bash</code> could be <span class="quote">“<span class="quote">/bin/bash</span>”</span>
1.1 dsieger 7335: on Linux systems.</p>
7336: <p>If you always need a pkgsrc version of the
7337: tool at run-time, then just use <code class="varname">DEPENDS</code> instead.
7338: </p>
7339: </div>
1.41 asau 7340: <div class="sect1">
1.1 dsieger 7341: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 7342: <a name="platform-tools"></a>18.3. Tools provided by platforms</h2></div></div></div>
1.1 dsieger 7343: <p>When improving or porting pkgsrc to a new platform, have a look
7344: at (or create) the corresponding platform specific make file fragment under
7345: <code class="filename">pkgsrc/mk/tools/tools.${OPSYS}.mk</code> which defines
7346: the name of the common tools. For example:</p>
7347: <pre class="programlisting">
7348: .if exists(/usr/bin/bzcat)
7349: TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
7350: .elif exists(/usr/bin/bzip2)
7351: TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
7352: .endif
7353:
7354: TOOLS_PLATFORM.true?= true # shell builtin
7355: </pre>
7356: </div>
1.41 asau 7357: <div class="sect1">
1.1 dsieger 7358: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 7359: <a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div>
1.41 asau 7360: <div class="qandaset">
1.101 ! sevan 7361: <a name="idp2122672132"></a><dl>
1.6 rillig 7362: <dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a>
1.1 dsieger 7363: </dt>
1.6 rillig 7364: <dt>18.4.2. <a href="#tools.listall">How do I get a list of all available
1.1 dsieger 7365: tools?</a>
7366: </dt>
1.6 rillig 7367: <dt>18.4.3. <a href="#tools.used">How can I get a list of all the tools that a
1.1 dsieger 7368: package is using while being built? I want to know whether it
7369: uses sed or not.</a>
7370: </dt>
7371: </dl>
1.41 asau 7372: <table border="0" style="width: 100%;">
7373: <colgroup>
1.1 dsieger 7374: <col align="left" width="1%">
1.23 wiz 7375: <col>
1.41 asau 7376: </colgroup>
1.1 dsieger 7377: <tbody>
1.41 asau 7378: <tr class="question">
1.1 dsieger 7379: <td align="left" valign="top">
1.101 ! sevan 7380: <a name="tools.new"></a><a name="idp2122671764"></a><p><b>18.4.1.</b></p>
1.1 dsieger 7381: </td>
7382: <td align="left" valign="top"><p>How do I add a new tool?</p></td>
7383: </tr>
7384: <tr class="answer">
7385: <td align="left" valign="top"></td>
7386: <td align="left" valign="top"><p>TODO</p></td>
7387: </tr>
1.41 asau 7388: <tr class="question">
1.1 dsieger 7389: <td align="left" valign="top">
1.101 ! sevan 7390: <a name="tools.listall"></a><a name="idp2122671028"></a><p><b>18.4.2.</b></p>
1.1 dsieger 7391: </td>
7392: <td align="left" valign="top"><p>How do I get a list of all available
7393: tools?</p></td>
7394: </tr>
7395: <tr class="answer">
7396: <td align="left" valign="top"></td>
7397: <td align="left" valign="top"><p>TODO</p></td>
7398: </tr>
1.41 asau 7399: <tr class="question">
1.1 dsieger 7400: <td align="left" valign="top">
1.101 ! sevan 7401: <a name="tools.used"></a><a name="idp2122670276"></a><p><b>18.4.3.</b></p>
1.1 dsieger 7402: </td>
7403: <td align="left" valign="top"><p>How can I get a list of all the tools that a
7404: package is using while being built? I want to know whether it
7405: uses sed or not.</p></td>
7406: </tr>
7407: <tr class="answer">
7408: <td align="left" valign="top"></td>
7409: <td align="left" valign="top"><p>Currently, you can't. (TODO: But I want to be able
7410: to do it.)</p></td>
7411: </tr>
7412: </tbody>
7413: </table>
7414: </div>
7415: </div>
7416: </div>
1.41 asau 7417: <div class="chapter">
1.1 dsieger 7418: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 7419: <a name="fixes"></a>Chapter 19. Making your package work</h2></div></div></div>
1.1 dsieger 7420: <div class="toc">
7421: <p><b>Table of Contents</b></p>
1.100 leot 7422: <dl class="toc">
1.6 rillig 7423: <dt><span class="sect1"><a href="#general-operation">19.1. General operation</a></span></dt>
1.1 dsieger 7424: <dd><dl>
1.6 rillig 7425: <dt><span class="sect2"><a href="#portability-of-packages">19.1.1. Portability of packages</a></span></dt>
1.23 wiz 7426: <dt><span class="sect2"><a href="#pulling-vars-from-etc-mk.conf">19.1.2. How to pull in user-settable variables from <code class="filename">mk.conf</code></a></span></dt>
1.6 rillig 7427: <dt><span class="sect2"><a href="#user-interaction">19.1.3. User interaction</a></span></dt>
7428: <dt><span class="sect2"><a href="#handling-licenses">19.1.4. Handling licenses</a></span></dt>
7429: <dt><span class="sect2"><a href="#restricted-packages">19.1.5. Restricted packages</a></span></dt>
7430: <dt><span class="sect2"><a href="#dependencies">19.1.6. Handling dependencies</a></span></dt>
7431: <dt><span class="sect2"><a href="#conflicts">19.1.7. Handling conflicts with other packages</a></span></dt>
7432: <dt><span class="sect2"><a href="#not-building-packages">19.1.8. Packages that cannot or should not be built</a></span></dt>
7433: <dt><span class="sect2"><a href="#undeletable-packages">19.1.9. Packages which should not be deleted, once installed</a></span></dt>
7434: <dt><span class="sect2"><a href="#security-handling">19.1.10. Handling packages with security problems</a></span></dt>
7435: <dt><span class="sect2"><a href="#bumping-pkgrevision">19.1.11. How to handle incrementing versions when fixing an existing package</a></span></dt>
7436: <dt><span class="sect2"><a href="#fixes.subst">19.1.12. Substituting variable text in the package files (the SUBST framework)</a></span></dt>
7437: </dl></dd>
1.23 wiz 7438: <dt><span class="sect1"><a href="#fixes.fetch">19.2. Fixing problems in the <span class="emphasis"><em>fetch</em></span> phase</a></span></dt>
1.6 rillig 7439: <dd><dl>
7440: <dt><span class="sect2"><a href="#no-plain-download">19.2.1. Packages whose distfiles aren't available for plain downloading</a></span></dt>
7441: <dt><span class="sect2"><a href="#modified-distfiles-same-name">19.2.2. How to handle modified distfiles with the 'old' name</a></span></dt>
1.88 tnn 7442: <dt><span class="sect2"><a href="#build.fetch.github">19.2.3. Packages hosted on github.com</a></span></dt>
1.6 rillig 7443: </dl></dd>
1.23 wiz 7444: <dt><span class="sect1"><a href="#fixes.configure">19.3. Fixing problems in the <span class="emphasis"><em>configure</em></span> phase</a></span></dt>
1.6 rillig 7445: <dd><dl>
7446: <dt><span class="sect2"><a href="#fixes.libtool">19.3.1. Shared libraries - libtool</a></span></dt>
7447: <dt><span class="sect2"><a href="#using-libtool">19.3.2. Using libtool on GNU packages that already support libtool</a></span></dt>
7448: <dt><span class="sect2"><a href="#autoconf-automake">19.3.3. GNU Autoconf/Automake</a></span></dt>
7449: </dl></dd>
7450: <dt><span class="sect1"><a href="#programming-languages">19.4. Programming languages</a></span></dt>
7451: <dd><dl>
7452: <dt><span class="sect2"><a href="#basic-programming-languages">19.4.1. C, C++, and Fortran</a></span></dt>
7453: <dt><span class="sect2"><a href="#java-programming-language">19.4.2. Java</a></span></dt>
7454: <dt><span class="sect2"><a href="#perl-scripts">19.4.3. Packages containing perl scripts</a></span></dt>
1.40 wiz 7455: <dt><span class="sect2"><a href="#shell-scripts">19.4.4. Packages containing shell scripts</a></span></dt>
7456: <dt><span class="sect2"><a href="#other-programming-languages">19.4.5. Other programming languages</a></span></dt>
1.6 rillig 7457: </dl></dd>
1.23 wiz 7458: <dt><span class="sect1"><a href="#fixes.build">19.5. Fixing problems in the <span class="emphasis"><em>build</em></span> phase</a></span></dt>
1.6 rillig 7459: <dd><dl>
7460: <dt><span class="sect2"><a href="#fixes.build.cpp">19.5.1. Compiling C and C++ code conditionally</a></span></dt>
7461: <dt><span class="sect2"><a href="#compiler-bugs">19.5.2. How to handle compiler bugs</a></span></dt>
1.23 wiz 7462: <dt><span class="sect2"><a href="#undefined-reference">19.5.3. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span></a></span></dt>
1.6 rillig 7463: <dt><span class="sect2"><a href="#out-of-memory">19.5.4. Running out of memory</a></span></dt>
7464: </dl></dd>
1.23 wiz 7465: <dt><span class="sect1"><a href="#fixes.install">19.6. Fixing problems in the <span class="emphasis"><em>install</em></span> phase</a></span></dt>
1.6 rillig 7466: <dd><dl>
7467: <dt><span class="sect2"><a href="#install-scripts">19.6.1. Creating needed directories</a></span></dt>
7468: <dt><span class="sect2"><a href="#where-to-install-documentation">19.6.2. Where to install documentation</a></span></dt>
7469: <dt><span class="sect2"><a href="#installing-score-files">19.6.3. Installing highscore files</a></span></dt>
7470: <dt><span class="sect2"><a href="#destdir-support">19.6.4. Adding DESTDIR support to packages</a></span></dt>
7471: <dt><span class="sect2"><a href="#hardcoded-paths">19.6.5. Packages with hardcoded paths to other interpreters</a></span></dt>
7472: <dt><span class="sect2"><a href="#perl-modules">19.6.6. Packages installing perl modules</a></span></dt>
7473: <dt><span class="sect2"><a href="#faq.info-files">19.6.7. Packages installing info files</a></span></dt>
7474: <dt><span class="sect2"><a href="#manpages">19.6.8. Packages installing man pages</a></span></dt>
1.7 rillig 7475: <dt><span class="sect2"><a href="#gconf-data-files">19.6.9. Packages installing GConf data files</a></span></dt>
1.18 snj 7476: <dt><span class="sect2"><a href="#scrollkeeper-data-files">19.6.10. Packages installing scrollkeeper/rarian data files</a></span></dt>
1.6 rillig 7477: <dt><span class="sect2"><a href="#x11-fonts">19.6.11. Packages installing X11 fonts</a></span></dt>
7478: <dt><span class="sect2"><a href="#gtk2-modules">19.6.12. Packages installing GTK2 modules</a></span></dt>
7479: <dt><span class="sect2"><a href="#sgml-xml-data">19.6.13. Packages installing SGML or XML data</a></span></dt>
7480: <dt><span class="sect2"><a href="#mime-database">19.6.14. Packages installing extensions to the MIME database</a></span></dt>
7481: <dt><span class="sect2"><a href="#intltool">19.6.15. Packages using intltool</a></span></dt>
7482: <dt><span class="sect2"><a href="#startup-scripts">19.6.16. Packages installing startup scripts</a></span></dt>
7483: <dt><span class="sect2"><a href="#tex-packages">19.6.17. Packages installing TeX modules</a></span></dt>
7484: <dt><span class="sect2"><a href="#emulation-packages">19.6.18. Packages supporting running binaries in
1.1 dsieger 7485: emulation</a></span></dt>
1.6 rillig 7486: <dt><span class="sect2"><a href="#hicolor-theme">19.6.19. Packages installing hicolor theme icons</a></span></dt>
7487: <dt><span class="sect2"><a href="#desktop-files">19.6.20. Packages installing desktop files</a></span></dt>
1.1 dsieger 7488: </dl></dd>
1.6 rillig 7489: <dt><span class="sect1"><a href="#punting">19.7. Marking packages as having problems</a></span></dt>
1.1 dsieger 7490: </dl>
7491: </div>
1.41 asau 7492: <div class="sect1">
1.1 dsieger 7493: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 7494: <a name="general-operation"></a>19.1. General operation</h2></div></div></div>
1.41 asau 7495: <div class="sect2">
1.1 dsieger 7496: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7497: <a name="portability-of-packages"></a>19.1.1. Portability of packages</h3></div></div></div>
1.1 dsieger 7498: <p>One appealing feature of pkgsrc is that it runs on many
7499: different platforms. As a result, it is important to ensure,
7500: where possible, that packages in pkgsrc are portable. This
7501: chapter mentions some particular details you should pay
7502: attention to while working on pkgsrc.</p>
7503: </div>
1.41 asau 7504: <div class="sect2">
1.1 dsieger 7505: <div class="titlepage"><div><div><h3 class="title">
1.10 hubertf 7506: <a name="pulling-vars-from-etc-mk.conf"></a>19.1.2. How to pull in user-settable variables from <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>
1.1 dsieger 7507: </h3></div></div></div>
7508: <p>The pkgsrc user can configure pkgsrc by overriding several
7509: variables in the file pointed to by <code class="varname">MAKECONF</code>,
1.10 hubertf 7510: which is <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> by default. When you
1.1 dsieger 7511: want to use those variables in the preprocessor directives of
1.79 snj 7512: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> (for example <code class="literal">.if</code> or
1.1 dsieger 7513: <code class="literal">.for</code>), you need to include the file
7514: <code class="filename">../../mk/bsd.prefs.mk</code> before, which in turn
7515: loads the user preferences.</p>
7516: <p>But note that some variables may not be completely defined
7517: after <code class="filename">../../mk/bsd.prefs.mk</code> has been
7518: included, as they may contain references to variables that are
7519: not yet defined. In shell commands this is no problem, since
7520: variables are actually macros, which are only expanded when they
7521: are used. But in the preprocessor directives mentioned above and
7522: in dependency lines (of the form <code class="literal">target:
7523: dependencies</code>) the variables are expanded at load
7524: time.</p>
1.41 asau 7525: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 7526: <h3 class="title">Note</h3>
7527: <p>Currently there is no exhaustive list of all
7528: variables that tells you whether they can be used at load time
7529: or only at run time, but it is in preparation.</p>
7530: </div>
7531: </div>
1.41 asau 7532: <div class="sect2">
1.1 dsieger 7533: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7534: <a name="user-interaction"></a>19.1.3. User interaction</h3></div></div></div>
1.1 dsieger 7535: <p>Occasionally, packages require interaction from the user,
7536: and this can be in a number of ways:</p>
1.41 asau 7537: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7538: <li class="listitem"><p>When fetching the distfiles, some packages require user
1.1 dsieger 7539: interaction such as entering username/password or accepting a
7540: license on a web page.</p></li>
1.23 wiz 7541: <li class="listitem"><p>When extracting the distfiles, some packages may ask for
1.1 dsieger 7542: passwords.</p></li>
1.23 wiz 7543: <li class="listitem"><p>help to configure the package before it is built</p></li>
7544: <li class="listitem"><p>help during the build process</p></li>
7545: <li class="listitem"><p>help during the installation of a package</p></li>
1.1 dsieger 7546: </ul></div>
7547: <p>The <code class="varname">INTERACTIVE_STAGE</code> definition is
7548: provided to notify the pkgsrc mechanism of an interactive stage
7549: which will be needed, and this should be set in the package's
7550: <code class="filename">Makefile</code>, e.g.:</p>
7551: <pre class="programlisting">
7552: INTERACTIVE_STAGE= build
7553: </pre>
7554: <p>Multiple interactive stages can be specified:</p>
7555: <pre class="programlisting">
7556: INTERACTIVE_STAGE= configure install
7557: </pre>
7558: <p>The user can then decide to skip this package by setting the
7559: <code class="varname">BATCH</code> variable.</p>
7560: </div>
1.41 asau 7561: <div class="sect2">
1.1 dsieger 7562: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7563: <a name="handling-licenses"></a>19.1.4. Handling licenses</h3></div></div></div>
1.1 dsieger 7564: <p>Authors of software can choose the licence under which
7565: software can be copied. This is due to copyright law, and reasons
7566: for license choices are outside the scope of pkgsrc. The pkgsrc
7567: system recognizes that there are a number of licenses which some
7568: users may find objectionable or difficult or impossible to comply
7569: with. The Free Software Foundation has declared some licenses
7570: "Free", and the Open Source Initiative has a definition of "Open
7571: Source". The pkgsrc system, as a policy choice, does not label
7572: packages which have licenses that are Free or Open Source.
7573: However, packages without a license meeting either of those tests
7574: are labeled with a license tag denoting the license. Note that a
7575: package with no license to copy trivially does not meet either the
7576: Free or Open Source test.</p>
7577: <p>For packages which are not Free or Open Source, pkgsrc will
7578: not build the package unless the user has indicated to pkgsrc that
7579: packages with that particular license may be built. Note that
7580: this documentation avoids the term "accepted the license". The
7581: pkgsrc system is merely providing a mechanism to avoid
7582: accidentally building a package with a non-free license;
7583: judgement and responsibility remain with the user. (Installation
7584: of binary packages are not currently subject to this mechanism;
7585: this is a bug.)</p>
7586: <p>One might want to only install packages with a BSD license,
1.19 jnemeth 7587: or the GPL, and not the other. The free licenses are added to the
7588: default <code class="varname">ACCEPTABLE_LICENSES</code> variable. The
7589: user can override the default by setting the
7590: <code class="varname">ACCEPTABLE_LICENSES</code> variable with "=" instead
7591: of "+=". The licenses accepted by default are:
7592: </p>
7593: <pre class="programlisting">
1.48 rodent 7594: apache-1.1 apache-2.0
7595: arphic-public
7596: artistic artistic-2.0
7597: boost-license
7598: cc-by-sa-v3.0
1.55 ryoon 7599: cc0-1.0-universal
1.48 rodent 7600: cddl-1.0
7601: cpl-1.0
7602: epl-v1.0
7603: gnu-fdl-v1.1 gnu-fdl-v1.2 gnu-fdl-v1.3
7604: gnu-gpl-v1
7605: gnu-gpl-v2 gnu-lgpl-v2 gnu-lgpl-v2.1
7606: gnu-gpl-v3 gnu-lgpl-v3
7607: ibm-public-license-1.0
7608: ipafont
7609: isc
7610: lppl-1.3c
7611: lucent
7612: miros
7613: mit
7614: mpl-1.0 mpl-1.1 mpl-2.0
7615: mplusfont
7616: ofl-v1.0 ofl-v1.1
7617: original-bsd modified-bsd 2-clause-bsd
7618: php
7619: png-license
7620: postgresql-license
7621: public-domain
7622: python-software-foundation
7623: qpl-v1.0
1.52 rodent 7624: sgi-free-software-b-v2.0
1.48 rodent 7625: sleepycat-public
7626: unlicense
7627: x11
7628: zlib
7629: zpl
1.19 jnemeth 7630: </pre>
7631: <p>
7632: </p>
1.1 dsieger 7633: <p>The license tag mechanism is intended to address
7634: copyright-related issues surrounding building, installing and
7635: using a package, and not to address redistribution issues (see
7636: <code class="varname">RESTRICTED</code> and
1.19 jnemeth 7637: <code class="varname">NO_SRC_ON_FTP</code>, etc.).
7638: Packages with redistribution restrictions should set these
7639: tags.</p>
1.1 dsieger 7640: <p>Denoting that a package may be copied according to a
7641: particular license is done by placing the license in
7642: <code class="filename">pkgsrc/licenses</code> and setting the
7643: <code class="varname">LICENSE</code> variable to a string identifying the
1.79 snj 7644: license, e.g. in <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/xv/README.html" target="_top"><code class="filename">graphics/xv</code></a>:</p>
1.1 dsieger 7645: <pre class="programlisting">
7646: LICENSE= xv-license
7647: </pre>
7648: <p>When trying to build, the user will get a notice that the
7649: package is covered by a license which has not been placed in the
7650: <code class="varname">ACCEPTABLE_LICENSES</code> variable:</p>
7651: <pre class="programlisting">
7652: <code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
7653: ===> xv-3.10anb9 has an unacceptable license: xv-license.
7654: ===> To view the license, enter "/usr/bin/make show-license".
7655: ===> To indicate acceptance, add this line to your /etc/mk.conf:
7656: ===> ACCEPTABLE_LICENSES+=xv-license
7657: *** Error code 1
7658: </pre>
1.10 hubertf 7659: <p>The license can be viewed with <span class="command"><strong>make
1.1 dsieger 7660: show-license</strong></span>, and if the user so chooses, the line
1.10 hubertf 7661: printed above can be added to <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> to
1.1 dsieger 7662: convey to pkgsrc that it should not in the future fail because of
7663: that license:</p>
7664: <pre class="programlisting">
7665: ACCEPTABLE_LICENSES+=xv-license
7666: </pre>
1.48 rodent 7667: <p>When adding a package with a new license, the following steps
7668: are required:</p>
7669: <div class="orderedlist"><ol class="orderedlist" type="1">
7670: <li class="listitem">
7671: <p>Check if the file can avoid the -license filename tag as described above by referencing <a class="ulink" href="http://www.gnu.org/licenses/license-list.html" target="_top">Various Licenses and Comments about Them</a> and <a class="ulink" href="http://opensource.org/licenses/alphabetical" target="_top">Licenses by Name | Open Source Initiative</a>. If this is the case, additionally add the license filename to:</p>
7672: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
7673: <li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in <code class="filename">pkgsrc/mk/license.mk</code></p></li>
7674: <li class="listitem"><p>default_acceptable_licenses in <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
1.52 rodent 7675: <li class="listitem"><p>the ACCEPTABLE_LICENSES list in <code class="filename">pkgsrc/doc/guide/files/fixes.xml</code></p></li>
1.48 rodent 7676: </ul></div>
7677: <p>with the proper syntax as demonstrated in those files, respectively.</p>
7678: </li>
7679: <li class="listitem"><p>The license text should be added to <code class="filename">pkgsrc/licenses</code> for displaying. A list of known licenses can be seen in this directory.</p></li>
7680: </ol></div>
1.1 dsieger 7681: <p>When the license changes (in a way other than formatting),
7682: please make sure that the new license has a different name (e.g.,
7683: append the version number if it exists, or the date). Just
7684: because a user told pkgsrc to build programs under a previous
7685: version of a license does not mean that pkgsrc should build
7686: programs under the new licenses. The higher-level point is that
7687: pkgsrc does not evaluate licenses for reasonableness; the only
7688: test is a mechanistic test of whether a particular text has been
7689: approved by either of two bodies.</p>
7690: <p>The use of <code class="varname">LICENSE=shareware</code>,
7691: <code class="varname">LICENSE=no-commercial-use</code>, and similar language
7692: is deprecated because it does not crisply refer to a particular
7693: license text. Another problem with such usage is that it does not
7694: enable a user to tell pkgsrc to proceed for a single package
7695: without also telling pkgsrc to proceed for all packages with that
7696: tag.</p>
7697: </div>
1.41 asau 7698: <div class="sect2">
1.1 dsieger 7699: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7700: <a name="restricted-packages"></a>19.1.5. Restricted packages</h3></div></div></div>
1.1 dsieger 7701: <p>Some licenses restrict how software may be re-distributed.
7702: Because a license tag is required unless the package is Free or
7703: Open Source, all packages with restrictions should have license
7704: tags. By declaring the restrictions, package tools can
7705: automatically refrain from e.g. placing binary packages on FTP
7706: sites.</p>
7707: <p>There are four restrictions that may be encoded, which are
7708: the cross product of sources (distfiles) and binaries not being
7709: placed on FTP sites and CD-ROMs. Because this is rarely the exact
7710: language in any license, and because non-Free licenses tend to be
7711: different from each other, pkgsrc adopts a definition of FTP and
7712: CD-ROM. Pkgsrc uses "FTP" to mean that the source or binary file
7713: should not be made available over the Internet at no charge.
7714: Pkgsrc uses "CD-ROM" to mean that the source or binary may not be
7715: made available on some kind of media, together with other source
7716: and binary packages, and which is sold for a distribution charge.
7717: </p>
7718: <p>In order to encode these restrictions, the package system
7719: defines five make variables that can be set to note these
7720: restrictions:</p>
1.41 asau 7721: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 7722: <li class="listitem">
1.1 dsieger 7723: <p><code class="varname">RESTRICTED</code></p>
7724: <p>This variable should be set whenever a restriction
7725: exists (regardless of its kind). Set this variable to a
7726: string containing the reason for the restriction. It should
7727: be understood that those wanting to understand the restriction
7728: will have to read the license, and perhaps seek advice of
7729: counsel.</p>
7730: </li>
1.23 wiz 7731: <li class="listitem">
1.1 dsieger 7732: <p><code class="varname">NO_BIN_ON_CDROM</code></p>
7733: <p>Binaries may not be placed on CD-ROM containing other
7734: binary packages, for which a distribution charge may be made.
7735: In this case, set this variable to
7736: <code class="varname">${RESTRICTED}</code>.</p>
7737: </li>
1.23 wiz 7738: <li class="listitem">
1.1 dsieger 7739: <p><code class="varname">NO_BIN_ON_FTP</code></p>
7740: <p>Binaries may not made available on the Internet without
7741: charge. In this case, set this variable to
7742: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7743: binary packages will not be included on ftp.NetBSD.org.</p>
7744: </li>
1.23 wiz 7745: <li class="listitem">
1.1 dsieger 7746: <p><code class="varname">NO_SRC_ON_CDROM</code></p>
7747: <p>Distfiles may not be placed on CD-ROM, together with
7748: other distfiles, for which a fee may be charged. In this
7749: case, set this variable to <code class="varname">${RESTRICTED}</code>.
7750: </p>
7751: </li>
1.23 wiz 7752: <li class="listitem">
1.1 dsieger 7753: <p><code class="varname">NO_SRC_ON_FTP</code></p>
7754: <p>Distfiles may not made available via FTP at no charge.
7755: In this case, set this variable to
7756: <code class="varname">${RESTRICTED}</code>. If this variable is set,
7757: the distfile(s) will not be mirrored on ftp.NetBSD.org.</p>
7758: </li>
7759: </ul></div>
1.32 wiz 7760: <p>Please note that packages will to be removed from pkgsrc
7761: when the distfiles are not distributable and cannot be obtained
7762: for a period of one full quarter branch. Packages with manual /
7763: interactive fetch must have a maintainer and it is his/her
7764: responsibility to ensure this.</p>
1.1 dsieger 7765: </div>
1.41 asau 7766: <div class="sect2">
1.1 dsieger 7767: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7768: <a name="dependencies"></a>19.1.6. Handling dependencies</h3></div></div></div>
1.1 dsieger 7769: <p>Your package may depend on some other package being present
7770: - and there are various ways of expressing this dependency.
7771: pkgsrc supports the <code class="varname">BUILD_DEPENDS</code> and
7772: <code class="varname">DEPENDS</code> definitions, the
7773: <code class="varname">USE_TOOLS</code> definition, as well as dependencies
7774: via <code class="filename">buildlink3.mk</code>, which is the preferred way
7775: to handle dependencies, and which uses the variables named above.
1.10 hubertf 7776: See <a class="xref" href="#buildlink" title="Chapter 14. Buildlink methodology">Chapter 14, <i>Buildlink methodology</i></a> for more information.</p>
1.1 dsieger 7777: <p>The basic difference between the two variables is as
7778: follows: The <code class="varname">DEPENDS</code> definition registers
7779: that pre-requisite in the binary package so it will be pulled in
7780: when the binary package is later installed, whilst the
7781: <code class="varname">BUILD_DEPENDS</code> definition does not, marking a
7782: dependency that is only needed for building the package.</p>
7783: <p>This means that if you only need a package present whilst
7784: you are building, it should be noted as a
7785: <code class="varname">BUILD_DEPENDS</code>.</p>
7786: <p>The format for a <code class="varname">BUILD_DEPENDS</code> and a
7787: <code class="varname">DEPENDS</code> definition is:</p>
7788: <pre class="programlisting">
7789: <pre-req-package-name>:../../<category>/<pre-req-package>
7790: </pre>
1.23 wiz 7791: <p>Please note that the <span class="quote">“<span class="quote">pre-req-package-name</span>”</span>
1.1 dsieger 7792: may include any of the wildcard version numbers recognized by
1.79 snj 7793: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
1.23 wiz 7794: <div class="orderedlist"><ol class="orderedlist" type="1">
7795: <li class="listitem">
1.1 dsieger 7796: <p>If your package needs another package's binaries or
1.54 wiz 7797: libraries to build and run, and if that package has a
1.1 dsieger 7798: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7799: <pre class="programlisting">
7800: .include "../../graphics/jpeg/buildlink3.mk"
7801: </pre>
7802: </li>
1.23 wiz 7803: <li class="listitem">
1.54 wiz 7804: <p>If your package needs another package's binaries or
7805: libraries only for building, and if that package has a
7806: <code class="filename">buildlink3.mk</code> file available, use it:</p>
7807: <pre class="programlisting">
7808: .include "../../graphics/jpeg/buildlink3.mk"
7809: </pre>
7810: <p>but set
7811: <code class="varname">BUILDLINK_DEPMETHOD.<em class="replaceable"><code>jpeg</code></em>?=build</code>
7812: to make it a build dependency only. This case is rather
7813: rare.</p>
7814: </li>
7815: <li class="listitem">
1.25 spz 7816: <p>If your package needs binaries from another package to build,
7817: use the <code class="varname">BUILD_DEPENDS</code> definition:</p>
1.1 dsieger 7818: <pre class="programlisting">
1.25 spz 7819: BUILD_DEPENDS+= scons-[0-9]*:../../devel/scons
1.1 dsieger 7820: </pre>
7821: </li>
1.25 spz 7822: <li class="listitem"><p>If your package needs a library with which to link and
7823: there is no <code class="filename">buildlink3.mk</code> file
7824: available, create one. Using
7825: <code class="varname">DEPENDS</code> won't be sufficient because the
7826: include files and libraries will be hidden from the compiler.</p></li>
1.23 wiz 7827: <li class="listitem">
1.25 spz 7828: <p>If your package needs some executable to be able to run
7829: correctly and if there's no
7830: <code class="filename">buildlink3.mk</code> file, this is specified
7831: using the <code class="varname">DEPENDS</code> variable. The
1.79 snj 7832: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/lyx/README.html" target="_top"><code class="filename">print/lyx</code></a> package needs to
1.25 spz 7833: be able to execute the latex binary from the teTeX package
7834: when it runs, and that is specified:</p>
1.1 dsieger 7835: <pre class="programlisting">
1.25 spz 7836: DEPENDS+= teTeX-[0-9]*:../../print/teTeX
1.1 dsieger 7837: </pre>
1.25 spz 7838: </li>
7839: <li class="listitem">
7840: <p>You can use wildcards in package dependencies. Note that
7841: such wildcard dependencies are retained when creating binary
7842: packages. The dependency is checked when installing the binary
7843: package and any package which matches the pattern will be
7844: used. Wildcard dependencies should be used with care.</p>
1.23 wiz 7845: <p>The <span class="quote">“<span class="quote">-[0-9]*</span>”</span> should be used instead of
7846: <span class="quote">“<span class="quote">-*</span>”</span> to avoid potentially ambiguous matches
7847: such as <span class="quote">“<span class="quote">tk-postgresql</span>”</span> matching a
7848: <span class="quote">“<span class="quote">tk-*</span>”</span> <code class="varname">DEPENDS</code>.</p>
1.1 dsieger 7849: <p>Wildcards can also be used to specify that a package
7850: will only build against a certain minimum version of a
7851: pre-requisite:</p>
7852: <pre class="programlisting">
1.25 spz 7853: DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
1.1 dsieger 7854: </pre>
1.25 spz 7855: <p>This means that the package will build using version 6.0
7856: of ImageMagick or newer. Such a dependency may be warranted
7857: if, for example, the command line options of an executable
7858: have changed.</p>
7859: <p>If you need to depend on minimum versions of libraries,
7860: see the buildlink section of the pkgsrc guide.</p>
1.1 dsieger 7861: <p>For security fixes, please update the package
1.10 hubertf 7862: vulnerabilities file. See <a class="xref" href="#security-handling" title="19.1.10. Handling packages with security problems">Section 19.1.10, “Handling packages with security problems”</a> for more
1.1 dsieger 7863: information.</p>
7864: </li>
7865: </ol></div>
7866: <p>If your package needs files from another package to build,
7867: add the relevant distribution files to
7868: <code class="varname">DISTFILES</code>, so they will be extracted
1.79 snj 7869: automatically. See the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/ghostscript/README.html" target="_top"><code class="filename">print/ghostscript</code></a> package for an example.
1.1 dsieger 7870: (It relies on the jpeg sources being present in source form
7871: during the build.)</p>
7872: </div>
1.41 asau 7873: <div class="sect2">
1.1 dsieger 7874: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7875: <a name="conflicts"></a>19.1.7. Handling conflicts with other packages</h3></div></div></div>
1.1 dsieger 7876: <p>Your package may conflict with other packages a user might
7877: already have installed on his system, e.g. if your package
7878: installs the same set of files as another package in the pkgsrc
1.80 wiz 7879: tree or has the same <code class="varname">PKGNAME</code>.</p>
7880: <p>These cases are handled automatically by the packaging tools
7881: at package installation time and do not need to be handled
7882: manually.</p>
7883: <p>In case the conflicts can not be recognized automatically
7884: (e.g., packages using the same config file location but no other
7885: shared files), you can set <code class="varname">CONFLICTS</code> to a
1.1 dsieger 7886: space-separated list of packages (including version string) your
7887: package conflicts with.</p>
1.80 wiz 7888: <p>For example, if both <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/bar/README.html" target="_top"><code class="filename">foo/bar</code></a>
7889: and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/baz/README.html" target="_top"><code class="filename">foo/baz</code></a>
7890: use the same config file, you would set in
7891: <code class="filename">foo/bar/Makefile</code>:</p>
1.1 dsieger 7892: <pre class="programlisting">
1.80 wiz 7893: CONFLICTS= baz-[0-9]*
1.1 dsieger 7894: </pre>
1.80 wiz 7895: <p>and in <code class="filename">pkgsrc/foo/baz/Makefile</code>:</p>
1.1 dsieger 7896: <pre class="programlisting">
1.80 wiz 7897: CONFLICTS= bar-[0-9]*
1.1 dsieger 7898: </pre>
7899: </div>
1.41 asau 7900: <div class="sect2">
1.1 dsieger 7901: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7902: <a name="not-building-packages"></a>19.1.8. Packages that cannot or should not be built</h3></div></div></div>
1.1 dsieger 7903: <p>There are several reasons why a package might be
7904: instructed to not build under certain circumstances. If the
7905: package builds and runs on most platforms, the exceptions
1.83 dholland 7906: should be noted with <code class="varname">BROKEN_ON_PLATFORM</code>. If
7907: the package builds and runs on a small handful of platforms,
7908: set <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> instead.
7909: Both <code class="varname">BROKEN_ON_PLATFORM</code> and
7910: <code class="varname">BROKEN_EXCEPT_ON_PLATFORM</code> are OS triples
7911: (OS-version-platform) that can use glob-style
7912: wildcards.</p>
7913: <p>If a package is not appropriate for some platforms (as
7914: oopposed to merely broken), a different set of variables should be
7915: used as this affects failure reporting and statistics.
7916: If the package is appropriate for most platforms, the exceptions
1.1 dsieger 7917: should be noted with <code class="varname">NOT_FOR_PLATFORM</code>. If
1.83 dholland 7918: the package is appropriate for only a small handful of platforms
7919: (often exactly one), set <code class="varname">ONLY_FOR_PLATFORM</code> instead.
1.1 dsieger 7920: Both <code class="varname">ONLY_FOR_PLATFORM</code> and
7921: <code class="varname">NOT_FOR_PLATFORM</code> are OS triples
7922: (OS-version-platform) that can use glob-style
7923: wildcards.</p>
7924: <p>Some packages are tightly bound to a specific version of an
1.79 snj 7925: operating system, e.g. LKMs or <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/lsof/README.html" target="_top"><code class="filename">sysutils/lsof</code></a>. Such binary packages are not
1.1 dsieger 7926: backwards compatible with other versions of the OS, and should be
7927: uploaded to a version specific directory on the FTP server. Mark
7928: these packages by setting <code class="varname">OSVERSION_SPECIFIC</code> to
1.23 wiz 7929: <span class="quote">“<span class="quote">yes</span>”</span>. This variable is not currently used by any of
1.1 dsieger 7930: the package system internals, but may be used in the
7931: future.</p>
7932: <p>If the package should be skipped (for example, because it
7933: provides functionality already provided by the system), set
7934: <code class="varname">PKG_SKIP_REASON</code> to a descriptive message. If
7935: the package should fail because some preconditions are not met,
7936: set <code class="varname">PKG_FAIL_REASON</code> to a descriptive
7937: message.</p>
7938: </div>
1.41 asau 7939: <div class="sect2">
1.1 dsieger 7940: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7941: <a name="undeletable-packages"></a>19.1.9. Packages which should not be deleted, once installed</h3></div></div></div>
1.1 dsieger 7942: <p>To ensure that a package may not be deleted, once it has been
7943: installed, the <code class="varname">PKG_PRESERVE</code> definition should
7944: be set in the package Makefile. This will be carried into any
7945: binary package that is made from this pkgsrc entry. A
1.23 wiz 7946: <span class="quote">“<span class="quote">preserved</span>”</span> package will
1.79 snj 7947: not be deleted using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
1.23 wiz 7948: <span class="quote">“<span class="quote">-f</span>”</span> option is used.</p>
1.1 dsieger 7949: </div>
1.41 asau 7950: <div class="sect2">
1.1 dsieger 7951: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7952: <a name="security-handling"></a>19.1.10. Handling packages with security problems</h3></div></div></div>
1.1 dsieger 7953: <p>When a vulnerability is found, this should be noted in
7954: <code class="filename">localsrc/security/advisories/pkg-vulnerabilities</code>,
1.31 wiz 7955: and after committing that file, ask pkgsrc-security@NetBSD.org to
7956: update the file on ftp.NetBSD.org.</p>
1.1 dsieger 7957: <p>After fixing the vulnerability by a patch, its
1.31 wiz 7958: <code class="varname">PKGREVISION</code> should be increased (this is of
7959: course not necessary if the problem is fixed by using a newer
7960: release of the software), and the pattern in the
7961: pkg-vulnerabilities file must be updated.</p>
1.1 dsieger 7962: <p>Also, if the fix should be applied to the stable pkgsrc
7963: branch, be sure to submit a pullup request!</p>
7964: <p>Binary packages already on ftp.NetBSD.org will be handled
7965: semi-automatically by a weekly cron job.</p>
7966: </div>
1.41 asau 7967: <div class="sect2">
1.1 dsieger 7968: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 7969: <a name="bumping-pkgrevision"></a>19.1.11. How to handle incrementing versions when fixing an existing package</h3></div></div></div>
1.1 dsieger 7970: <p>When making fixes to an existing package it can be useful
7971: to change the version number in <code class="varname">PKGNAME</code>. To
7972: avoid conflicting with future versions by the original author, a
1.23 wiz 7973: <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 7974: on package versions by setting <code class="varname">PKGREVISION=1</code>
1.23 wiz 7975: (2, ...). The <span class="quote">“<span class="quote">nb</span>”</span> is treated like a
7976: <span class="quote">“<span class="quote">.</span>”</span> by the package tools. e.g.</p>
1.1 dsieger 7977: <pre class="programlisting">
7978: DISTNAME= foo-17.42
7979: PKGREVISION= 9
7980: </pre>
7981: <p>will result in a <code class="varname">PKGNAME</code> of
1.23 wiz 7982: <span class="quote">“<span class="quote">foo-17.42nb9</span>”</span>. If you want to use the original
7983: value of <code class="varname">PKGNAME</code> without the <span class="quote">“<span class="quote">nbX</span>”</span>
1.1 dsieger 7984: suffix, e.g. for setting <code class="varname">DIST_SUBDIR</code>, use
7985: <code class="varname">PKGNAME_NOREV</code>.</p>
7986: <p>When a new release of the package is released, the
7987: <code class="varname">PKGREVISION</code> should be removed, e.g. on a new
7988: minor release of the above package, things should be like:</p>
7989: <pre class="programlisting">
7990: DISTNAME= foo-17.43
7991: </pre>
7992: <p><code class="varname">PKGREVISION</code> should be incremented for any
7993: non-trivial change in the resulting binary package. Without a
7994: <code class="varname">PKGREVISION</code> bump, someone with the previous
7995: version installed has no way of knowing that their package is out
7996: of date. Thus, changes without increasing
7997: <code class="varname">PKGREVISION</code> are essentially labeled "this is so
7998: trivial that no reasonable person would want to upgrade", and this
7999: is the rough test for when increasing
8000: <code class="varname">PKGREVISION</code> is appropriate. Examples of
8001: changes that do not merit increasing
8002: <code class="varname">PKGREVISION</code> are:</p>
1.41 asau 8003: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8004: <li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>,
1.14 jmcneill 8005: <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>,
1.1 dsieger 8006: or comments in Makefile.</p></li>
1.23 wiz 8007: <li class="listitem"><p>
1.1 dsieger 8008: Changing build variables if the resulting binary package is the same.</p></li>
1.23 wiz 8009: <li class="listitem"><p>
1.1 dsieger 8010: Changing <code class="filename">DESCR</code>.</p></li>
1.23 wiz 8011: <li class="listitem"><p>
1.1 dsieger 8012: Adding <code class="varname">PKG_OPTIONS</code> if the default options don't change.</p></li>
8013: </ul></div>
8014: <p>Examples of changes that do merit an increase to
8015: <code class="varname">PKGREVISION</code> include:</p>
1.41 asau 8016: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8017: <li class="listitem"><p>
1.1 dsieger 8018: Security fixes</p></li>
1.23 wiz 8019: <li class="listitem"><p>
1.1 dsieger 8020: Changes or additions to a patch file</p></li>
1.23 wiz 8021: <li class="listitem"><p>
1.1 dsieger 8022: Changes to the <code class="filename">PLIST</code></p></li>
1.23 wiz 8023: <li class="listitem"><p>A dependency is changed or renamed.</p></li>
1.1 dsieger 8024: </ul></div>
8025: <p>PKGREVISION must also be incremented when dependencies have ABI
8026: changes.</p>
8027: </div>
1.41 asau 8028: <div class="sect2">
1.1 dsieger 8029: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8030: <a name="fixes.subst"></a>19.1.12. Substituting variable text in the package files (the SUBST framework)</h3></div></div></div>
1.1 dsieger 8031: <p>When you want to replace the same text in multiple files
8032: or when the replacement text varies, patches alone cannot help.
8033: This is where the SUBST framework comes in. It provides an
8034: easy-to-use interface for replacing text in files.
8035: Example:</p>
8036: <pre class="programlisting">
8037: SUBST_CLASSES+= fix-paths
8038: SUBST_STAGE.fix-paths= pre-configure
8039: SUBST_MESSAGE.fix-paths= Fixing absolute paths.
8040: SUBST_FILES.fix-paths= src/*.c
8041: SUBST_FILES.fix-paths+= scripts/*.sh
8042: SUBST_SED.fix-paths= -e 's,"/usr/local,"${PREFIX},g'
8043: SUBST_SED.fix-paths+= -e 's,"/var/log,"${VARBASE}/log,g'
8044: </pre>
8045: <p><code class="varname">SUBST_CLASSES</code> is a list of identifiers
8046: that are used to identify the different SUBST blocks that are
8047: defined. The SUBST framework is heavily used by pkgsrc, so it is
8048: important to always use the <code class="literal">+=</code> operator with
8049: this variable. Otherwise some substitutions may be
8050: skipped.</p>
8051: <p>The remaining variables of each SUBST block are
8052: parameterized with the identifier from the first line
8053: (<code class="literal">fix-paths</code> in this case.) They can be seen as
8054: parameters to a function call.</p>
8055: <p><code class="varname">SUBST_STAGE.*</code> specifies the stage at
8056: which the replacement will take place. All combinations of
8057: <code class="literal">pre-</code>, <code class="literal">do-</code> and
8058: <code class="literal">post-</code> together with a phase name are
8059: possible, though only few are actually used. Most commonly used
8060: are <code class="literal">post-patch</code> and
8061: <code class="literal">pre-configure</code>. Of these two,
8062: <code class="literal">pre-configure</code> should be preferred because
1.10 hubertf 8063: then it is possible to run <span class="command"><strong>bmake patch</strong></span> and
1.1 dsieger 8064: have the state after applying the patches but before making any
8065: other changes. This is especially useful when you are debugging
8066: a package in order to create new patches for it. Similarly,
8067: <code class="literal">post-build</code> is preferred over
8068: <code class="literal">pre-install</code>, because the install phase should
8069: generally be kept as simple as possible. When you use
8070: <code class="literal">post-build</code>, you have the same files in the
8071: working directory that will be installed later, so you can check
8072: if the substitution has succeeded.</p>
8073: <p><code class="varname">SUBST_MESSAGE.*</code> is an optional text
8074: that is printed just before the substitution is done.</p>
8075: <p><code class="varname">SUBST_FILES.*</code> is the list of shell
8076: globbing patterns that specifies the files in which the
8077: substitution will take place. The patterns are interpreted
8078: relatively to the <code class="varname">WRKSRC</code> directory.</p>
8079: <p><code class="varname">SUBST_SED.*</code> is a list of arguments to
1.79 snj 8080: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sed+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> that specify the actual substitution. Every sed
1.1 dsieger 8081: command should be prefixed with <code class="literal">-e</code>, so that
8082: all SUBST blocks look uniform.</p>
8083: <p>There are some more variables, but they are so seldomly
8084: used that they are only documented in the
8085: <code class="filename">mk/subst.mk</code> file.</p>
8086: </div>
8087: </div>
1.41 asau 8088: <div class="sect1">
1.1 dsieger 8089: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 8090: <a name="fixes.fetch"></a>19.2. Fixing problems in the <span class="emphasis"><em>fetch</em></span> phase</h2></div></div></div>
1.41 asau 8091: <div class="sect2">
1.1 dsieger 8092: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8093: <a name="no-plain-download"></a>19.2.1. Packages whose distfiles aren't available for plain downloading</h3></div></div></div>
1.1 dsieger 8094: <p>If you need to download from a dynamic URL you can set
1.10 hubertf 8095: <code class="varname">DYNAMIC_MASTER_SITES</code> and a <span class="command"><strong>make
1.1 dsieger 8096: fetch</strong></span> will call <code class="filename">files/getsite.sh</code>
8097: with the name of each file to download as an argument, expecting
8098: it to output the URL of the directory from which to download
1.79 snj 8099: it. <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/ns-cult3d/README.html" target="_top"><code class="filename">graphics/ns-cult3d</code></a> is an
1.1 dsieger 8100: example of this usage.</p>
8101: <p>If the download can't be automated, because the user must
8102: submit personal information to apply for a password, or must pay
8103: for the source, or whatever, you can set
8104: <code class="varname">FETCH_MESSAGE</code> to a list of lines that are
8105: displayed to the user before aborting the build. Example:</p>
8106: <pre class="programlisting">
8107: FETCH_MESSAGE= "Please download the files"
8108: FETCH_MESSAGE+= " "${DISTFILES:Q}
8109: FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
8110: </pre>
8111: </div>
1.41 asau 8112: <div class="sect2">
1.1 dsieger 8113: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8114: <a name="modified-distfiles-same-name"></a>19.2.2. How to handle modified distfiles with the 'old' name</h3></div></div></div>
1.1 dsieger 8115: <p>Sometimes authors of a software package make some
8116: modifications after the software was released, and they put up a
8117: new distfile without changing the package's version number. If a
8118: package is already in pkgsrc at that time, the checksum will
8119: no longer match. The contents of the new distfile should be
8120: compared against the old one before changing anything, to make
8121: sure the distfile was really updated on purpose, and that
8122: no trojan horse or so crept in.
8123: Please mention that the distfiles were compared and what was found
1.53 rodent 8124: in your commit message.</p>
8125: <p>Then, the correct way to work around this is to
1.1 dsieger 8126: set <code class="varname">DIST_SUBDIR</code> to a unique directory name,
8127: usually based on <code class="varname">PKGNAME_NOREV</code>. All
8128: <code class="varname">DISTFILES</code> and
8129: <code class="varname">PATCHFILES</code> for this package will be put in that
8130: subdirectory of the local distfiles directory.
1.10 hubertf 8131: (See <a class="xref" href="#bumping-pkgrevision" title="19.1.11. How to handle incrementing versions when fixing an existing package">Section 19.1.11, “How to handle incrementing versions when fixing an existing package”</a> for more details.)
1.1 dsieger 8132: In case this
8133: happens more often, <code class="varname">PKGNAME</code> can be used (thus
8134: including the <code class="filename">nbX</code> suffix) or a date stamp
1.53 rodent 8135: can be appended, like <code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>.</p>
8136: <p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's name does not contain a version and the distfile is apt to change. In cases where the likelihood of this is very small, <code class="varname">DIST_SUBDIR</code> might not be required. Additionally, <code class="varname">DIST_SUBDIR</code> must not be removed unless the distfile name changes, even if a package is being moved or renamed.</p>
8137: <p>Do not forget regenerating the <code class="filename">distinfo</code> file
1.1 dsieger 8138: after that, since it contains the <code class="varname">DIST_SUBDIR</code>
8139: path in the filenames.
1.53 rodent 8140: Also, increase the PKGREVISION if the installed package is different.
1.1 dsieger 8141: Furthermore, a mail to the package's authors seems appropriate
8142: telling them that changing distfiles after releases without
8143: changing the file names is not good practice.</p>
8144: </div>
1.88 tnn 8145: <div class="sect2">
8146: <div class="titlepage"><div><div><h3 class="title">
8147: <a name="build.fetch.github"></a>19.2.3. Packages hosted on github.com</h3></div></div></div>
1.90 tnn 8148: <p>Helper methods exist for packages hosted on github.com which will often have distfile names that clash with other packages, for example <code class="filename">1.0.tar.gz</code>. Use one of the three recipes from below:
8149: </p>
1.88 tnn 8150: <div class="sect3">
8151: <div class="titlepage"><div><div><h4 class="title">
8152: <a name="build.fetch.github.tag"></a>19.2.3.1. Fetch based on a tagged release</h4></div></div></div>
8153: <p>
8154: If your distfile URL looks similar to <code class="literal">http://github.com/username/exampleproject/archive/v1.0.zip</code>, then you are packaging a tagged release.
8155: </p>
8156: <pre class="programlisting">
8157: DISTNAME= exampleproject-1.0
1.90 tnn 8158: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8159: #GITHUB_PROJECT= # can be omitted if same as DISTNAME
8160: GITHUB_TAG= v${PKGVERSION_NOREV}
1.88 tnn 8161: EXTRACT_SUFX= .zip
8162: </pre>
8163: </div>
8164: <div class="sect3">
8165: <div class="titlepage"><div><div><h4 class="title">
8166: <a name="build.fetch.github.commit"></a>19.2.3.2. Fetch based on a specific commit</h4></div></div></div>
8167: <p>
8168: If your distfile URL looks similar to <code class="literal">http://github.com/example/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz</code>, then you are packaging a specific commit not tied to a release.
8169: </p>
8170: <pre class="programlisting">
8171: DISTNAME= example-1.0
1.90 tnn 8172: MASTER_SITES= ${MASTER_SITE_GITHUB:example/}
8173: #GITHUB_PROJECT= # can be omitted if same as DISTNAME
8174: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
1.88 tnn 8175: </pre>
8176: </div>
8177: <div class="sect3">
8178: <div class="titlepage"><div><div><h4 class="title">
8179: <a name="build.fetch.github.release"></a>19.2.3.3. Fetch based on release</h4></div></div></div>
8180: <p>
8181: If your distfile URL looks similar to <code class="literal">http://github.com/username/exampleproject/releases/download/rel-1.6/offensive-1.6.zip</code>, then you are packaging a release.
8182: </p>
8183: <pre class="programlisting">
8184: DISTNAME= offensive-1.6
1.90 tnn 8185: PKGNAME= ${DISTNAME:S/offensive/proper/}
8186: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
8187: GITHUB_PROJECT= exampleproject
8188: GITHUB_RELEASE= rel-${PKGVERSION_NOREV} # usually just set this to ${DISTNAME}
8189: EXTRACT_SUFX= .zip
1.88 tnn 8190: </pre>
8191: </div>
8192: </div>
1.1 dsieger 8193: </div>
1.41 asau 8194: <div class="sect1">
1.1 dsieger 8195: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 8196: <a name="fixes.configure"></a>19.3. Fixing problems in the <span class="emphasis"><em>configure</em></span> phase</h2></div></div></div>
1.41 asau 8197: <div class="sect2">
1.1 dsieger 8198: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8199: <a name="fixes.libtool"></a>19.3.1. Shared libraries - libtool</h3></div></div></div>
1.1 dsieger 8200: <p>pkgsrc supports many different machines, with different
8201: object formats like a.out and ELF, and varying abilities to do
8202: shared library and dynamic loading at all. To accompany this,
8203: varying commands and options have to be passed to the
8204: compiler, linker, etc. to get the Right Thing, which can be
8205: pretty annoying especially if you don't have all the machines
8206: at your hand to test things. The
1.79 snj 8207: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool/README.html" target="_top"><code class="filename">devel/libtool</code></a> pkg
1.23 wiz 8208: can help here, as it just <span class="quote">“<span class="quote">knows</span>”</span> how to build
1.1 dsieger 8209: both static and dynamic libraries from a set of source files,
8210: thus being platform-independent.</p>
8211: <p>Here's how to use libtool in a package in seven simple
8212: steps:</p>
1.23 wiz 8213: <div class="orderedlist"><ol class="orderedlist" type="1">
8214: <li class="listitem"><p>Add <code class="varname">USE_LIBTOOL=yes</code> to the package
1.1 dsieger 8215: Makefile.</p></li>
1.23 wiz 8216: <li class="listitem"><p>For library objects, use <span class="quote">“<span class="quote">${LIBTOOL} --mode=compile
8217: ${CC}</span>”</span> in place of <span class="quote">“<span class="quote">${CC}</span>”</span>. You could even
1.1 dsieger 8218: add it to the definition of <code class="varname">CC</code>, if only
8219: libraries are being built in a given Makefile. This one command
8220: will build both PIC and non-PIC library objects, so you need not
8221: have separate shared and non-shared library rules.</p></li>
1.23 wiz 8222: <li class="listitem">
1.1 dsieger 8223: <p>For the linking of the library, remove any
1.23 wiz 8224: <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
8225: -Bshareable</span>”</span> commands, and instead use:</p>
1.1 dsieger 8226: <pre class="programlisting">
8227: ${LIBTOOL} --mode=link \
8228: ${CC} -o ${.TARGET:.a=.la} \
8229: ${OBJS:.o=.lo} \
8230: -rpath ${PREFIX}/lib \
8231: -version-info major:minor
8232: </pre>
8233: <p>Note that the library is changed to have a
8234: <code class="filename">.la</code> extension, and the objects are
8235: changed to have a <code class="filename">.lo</code>
8236: extension. Change <code class="varname">OBJS</code> as
8237: necessary. This automatically creates all of the
8238: <code class="filename">.a</code>,
8239: <code class="filename">.so.major.minor</code>, and ELF symlinks (if
8240: necessary) in the build directory. Be sure to include
1.23 wiz 8241: <span class="quote">“<span class="quote">-version-info</span>”</span>, especially when major and
1.1 dsieger 8242: minor are zero, as libtool will otherwise strip off the
8243: shared library version.</p>
8244: <p>From the libtool manual:</p>
8245: <pre class="programlisting">
8246: So, libtool library versions are described by three integers:
8247:
8248: CURRENT
8249: The most recent interface number that this library implements.
8250:
8251: REVISION
8252: The implementation number of the CURRENT interface.
8253:
8254: AGE
8255: The difference between the newest and oldest interfaces that
8256: this library implements. In other words, the library implements
8257: all the interface numbers in the range from number `CURRENT -
8258: AGE' to `CURRENT'.
8259:
8260: If two libraries have identical CURRENT and AGE numbers, then the
8261: dynamic linker chooses the library with the greater REVISION number.
8262: </pre>
1.23 wiz 8263: <p>The <span class="quote">“<span class="quote">-release</span>”</span> option will produce
1.1 dsieger 8264: different results for a.out and ELF (excluding symlinks)
8265: in only one case. An ELF library of the form
1.23 wiz 8266: <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 8267: will have a symlink of
1.23 wiz 8268: <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 8269: on an a.out platform. This is handled
8270: automatically.</p>
1.23 wiz 8271: <p>The <span class="quote">“<span class="quote">-rpath argument</span>”</span> is the install
1.1 dsieger 8272: directory of the library being built.</p>
8273: <p>In the <code class="filename">PLIST</code>, include only the
8274: <code class="filename">.la</code> file, the other files will be
8275: added automatically.</p>
8276: </li>
1.23 wiz 8277: <li class="listitem">
1.1 dsieger 8278: <p>When linking shared object (<code class="filename">.so</code>)
1.79 snj 8279: files, i.e. files that are loaded via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?dlopen+3+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">dlopen</span>(3)</span></a>, NOT
1.23 wiz 8280: shared libraries, use <span class="quote">“<span class="quote">-module
8281: -avoid-version</span>”</span> to prevent them getting version
1.1 dsieger 8282: tacked on.</p>
8283: <p>The <code class="filename">PLIST</code> file gets the
8284: <code class="filename">foo.so</code> entry.</p>
8285: </li>
1.23 wiz 8286: <li class="listitem">
1.1 dsieger 8287: <p>When linking programs that depend on these libraries
8288: <span class="emphasis"><em>before</em></span> they are installed, preface
1.79 snj 8289: the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cc+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8290: --mode=link</span>”</span>, and it will find the correct
1.1 dsieger 8291: libraries (static or shared), but please be aware that
8292: libtool will not allow you to specify a relative path in
1.23 wiz 8293: -L (such as <span class="quote">“<span class="quote">-L../somelib</span>”</span>), because it
1.1 dsieger 8294: expects you to change that argument to be the
8295: <code class="filename">.la</code> file. e.g.</p>
8296: <pre class="programlisting">
8297: ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
8298: </pre>
8299: <p>should be changed to:</p>
8300: <pre class="programlisting">
8301: ${LIBTOOL} --mode=link ${CC} -o <em class="replaceable"><code>someprog</code></em> <em class="replaceable"><code>../somelib/somelib.la</code></em>
8302: </pre>
8303: <p>and it will do the right thing with the libraries.</p>
8304: </li>
1.23 wiz 8305: <li class="listitem">
1.79 snj 8306: <p>When installing libraries, preface the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a>
8307: or <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cp+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span class="quote">“<span class="quote">${LIBTOOL}
1.23 wiz 8308: --mode=install</span>”</span>, and change the library name to
1.1 dsieger 8309: <code class="filename">.la</code>. e.g.</p>
8310: <pre class="programlisting">
1.22 jakllsch 8311: ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib
1.1 dsieger 8312: </pre>
8313: <p>This will install the static <code class="filename">.a</code>,
8314: shared library, any needed symlinks, and run
1.79 snj 8315: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ldconfig+8+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
1.1 dsieger 8316: </li>
1.23 wiz 8317: <li class="listitem"><p>In your <code class="filename">PLIST</code>, include only
1.1 dsieger 8318: the <code class="filename">.la</code>
8319: file (this is a change from previous behaviour).</p></li>
8320: </ol></div>
8321: </div>
1.41 asau 8322: <div class="sect2">
1.1 dsieger 8323: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8324: <a name="using-libtool"></a>19.3.2. Using libtool on GNU packages that already support libtool</h3></div></div></div>
1.1 dsieger 8325: <p>Add <code class="varname">USE_LIBTOOL=yes</code> to the
8326: package Makefile. This will override the package's own libtool
8327: in most cases. For older libtool using packages, libtool is
8328: made by ltconfig script during the do-configure step; you can
1.10 hubertf 8329: check the libtool script location by doing <span class="command"><strong>make
1.1 dsieger 8330: configure; find work*/ -name libtool</strong></span>.</p>
8331: <p><code class="varname">LIBTOOL_OVERRIDE</code> specifies which libtool
8332: scripts, relative to <code class="varname">WRKSRC</code>, to override. By
1.23 wiz 8333: default, it is set to <span class="quote">“<span class="quote">libtool */libtool
8334: */*/libtool</span>”</span>. If this does not match the location of the
1.1 dsieger 8335: package's libtool script(s), set it as appropriate.</p>
8336: <p>If you do not need <code class="filename">*.a</code> static
8337: libraries built and installed, then use
8338: <code class="varname">SHLIBTOOL_OVERRIDE</code> instead.</p>
8339: <p>If your package makes use of the platform-independent library
8340: for loading dynamic shared objects, that comes with libtool
8341: (libltdl), you should include devel/libltdl/buildlink3.mk.</p>
8342: <p>Some packages use libtool incorrectly so that the package
8343: may not work or build in some circumstances. Some of the more
8344: common errors are:</p>
1.41 asau 8345: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8346: <li class="listitem">
1.1 dsieger 8347: <p>The inclusion of a shared object (-module) as a dependent library in an
8348: executable or library. This in itself isn't a problem if one of two things
8349: has been done:</p>
1.23 wiz 8350: <div class="orderedlist"><ol class="orderedlist" type="1">
8351: <li class="listitem"><p>The shared object is named correctly, i.e.
1.1 dsieger 8352: <code class="filename">libfoo.la</code>, not
8353: <code class="filename">foo.la</code></p></li>
1.23 wiz 8354: <li class="listitem"><p>The -dlopen option is used when linking an executable.</p></li>
1.1 dsieger 8355: </ol></div>
8356: </li>
1.23 wiz 8357: <li class="listitem"><p>The use of libltdl without the correct calls to initialisation routines.
1.1 dsieger 8358: The function lt_dlinit() should be called and the macro
8359: <code class="varname">LTDL_SET_PRELOADED_SYMBOLS</code> included in
8360: executables.</p></li>
8361: </ul></div>
8362: </div>
1.41 asau 8363: <div class="sect2">
1.1 dsieger 8364: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8365: <a name="autoconf-automake"></a>19.3.3. GNU Autoconf/Automake</h3></div></div></div>
1.1 dsieger 8366: <p>If a package needs GNU autoconf or automake to be executed
8367: to regenerate the configure script and Makefile.in makefile
8368: templates, then they should be executed in a pre-configure
8369: target.</p>
8370: <p>For packages that need only autoconf:</p>
8371: <pre class="programlisting">
8372: AUTOCONF_REQD= 2.50 # if default version is not good enough
8373: USE_TOOLS+= autoconf # use "autoconf213" for autoconf-2.13
8374: ...
8375:
8376: pre-configure:
8377: cd ${WRKSRC} && autoconf
8378:
8379: ...
8380: </pre>
8381: <p>and for packages that need automake and autoconf:</p>
8382: <pre class="programlisting">
8383: AUTOMAKE_REQD= 1.7.1 # if default version is not good enough
8384: USE_TOOLS+= automake # use "automake14" for automake-1.4
8385: ...
8386:
8387: pre-configure:
8388: set -e; cd ${WRKSRC}; \
8389: aclocal; autoheader; automake -a --foreign -i; autoconf
8390:
8391: ...
8392: </pre>
8393: <p>Packages which use GNU Automake will almost certainly
8394: require GNU Make.</p>
8395: <p>There are times when the configure process makes
8396: additional changes to the generated files, which then causes
8397: the build process to try to re-execute the automake sequence.
8398: This is prevented by touching various files in the configure
8399: stage. If this causes problems with your package you can set
8400: <code class="varname">AUTOMAKE_OVERRIDE=NO</code> in the package
8401: Makefile.</p>
8402: </div>
8403: </div>
1.41 asau 8404: <div class="sect1">
1.1 dsieger 8405: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 8406: <a name="programming-languages"></a>19.4. Programming languages</h2></div></div></div>
1.41 asau 8407: <div class="sect2">
1.1 dsieger 8408: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8409: <a name="basic-programming-languages"></a>19.4.1. C, C++, and Fortran</h3></div></div></div>
1.1 dsieger 8410: <p>Compilers for the C, C++, and Fortran languages comes with
8411: the NetBSD base system. By default, pkgsrc assumes that a package
8412: is written in C and will hide all other compilers (via the wrapper
1.10 hubertf 8413: framework, see <a class="xref" href="#buildlink" title="Chapter 14. Buildlink methodology">Chapter 14, <i>Buildlink methodology</i></a>).</p>
1.1 dsieger 8414: <p>To declare which language's compiler a package needs, set
8415: the <code class="varname">USE_LANGUAGES</code> variable. Allowed values
1.23 wiz 8416: currently are <span class="quote">“<span class="quote">c</span>”</span>, <span class="quote">“<span class="quote">c++</span>”</span>, and
8417: <span class="quote">“<span class="quote">fortran</span>”</span> (and any combination). The default is
8418: <span class="quote">“<span class="quote">c</span>”</span>. Packages using GNU configure scripts, even if
1.1 dsieger 8419: written in C++, usually need a C compiler for the configure
8420: phase.</p>
8421: </div>
1.41 asau 8422: <div class="sect2">
1.1 dsieger 8423: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8424: <a name="java-programming-language"></a>19.4.2. Java</h3></div></div></div>
1.1 dsieger 8425: <p>If a program is written in Java, use the Java framework in
8426: pkgsrc. The package must include
8427: <code class="filename">../../mk/java-vm.mk</code>. This Makefile fragment
8428: provides the following variables:</p>
1.41 asau 8429: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8430: <li class="listitem"><p><code class="varname">USE_JAVA</code> defines if a build
1.1 dsieger 8431: dependency on the JDK is added. If
1.23 wiz 8432: <code class="varname">USE_JAVA</code> is set to <span class="quote">“<span class="quote">run</span>”</span>, then
1.1 dsieger 8433: there is only a runtime dependency on the JDK. The default is
1.23 wiz 8434: <span class="quote">“<span class="quote">yes</span>”</span>, which also adds a build dependency on the
1.1 dsieger 8435: JDK.</p></li>
1.23 wiz 8436: <li class="listitem"><p>Set <code class="varname">USE_JAVA2</code> to declare that
1.1 dsieger 8437: a package needs a Java2 implementation. The supported values
1.23 wiz 8438: are <span class="quote">“<span class="quote">yes</span>”</span>, <span class="quote">“<span class="quote">1.4</span>”</span>, and
8439: <span class="quote">“<span class="quote">1.5</span>”</span>. <span class="quote">“<span class="quote">yes</span>”</span> accepts any Java2
8440: implementation, <span class="quote">“<span class="quote">1.4</span>”</span> insists on versions 1.4 or
8441: above, and <span class="quote">“<span class="quote">1.5</span>”</span> only accepts versions 1.5 or
1.1 dsieger 8442: above. This variable is not set by default.</p></li>
1.24 wiz 8443: <li class="listitem"><p><code class="varname">PKG_JAVA_HOME</code> is
8444: automatically set to the runtime location of the used Java
8445: implementation dependency. It may be used to set
8446: <code class="varname">JAVA_HOME</code> to a good value if the program
8447: needs this variable to be defined.
8448: </p></li>
1.1 dsieger 8449: </ul></div>
8450: </div>
1.41 asau 8451: <div class="sect2">
1.1 dsieger 8452: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8453: <a name="perl-scripts"></a>19.4.3. Packages containing perl scripts</h3></div></div></div>
1.1 dsieger 8454: <p>If your package contains interpreted perl scripts, add
1.23 wiz 8455: <span class="quote">“<span class="quote">perl</span>”</span> to the <code class="varname">USE_TOOLS</code> variable
1.1 dsieger 8456: and set <code class="varname">REPLACE_PERL</code> to ensure that the proper
8457: interpreter path is set. <code class="varname">REPLACE_PERL</code> should
8458: contain a list of scripts, relative to <code class="varname">WRKSRC</code>,
1.74 wiz 8459: that you want adjusted. Every occurrence of
8460: <code class="filename">*/bin/perl</code> in a she-bang line will be
8461: replaced with the full path to the perl executable.</p>
1.1 dsieger 8462: <p>If a particular version of perl is needed, set the
8463: <code class="varname">PERL5_REQD</code> variable to the version number. The
1.23 wiz 8464: default is <span class="quote">“<span class="quote">5.0</span>”</span>.</p>
1.10 hubertf 8465: <p>See <a class="xref" href="#perl-modules" title="19.6.6. Packages installing perl modules">Section 19.6.6, “Packages installing perl modules”</a> for information
1.1 dsieger 8466: about handling perl modules.</p>
8467: </div>
1.41 asau 8468: <div class="sect2">
1.1 dsieger 8469: <div class="titlepage"><div><div><h3 class="title">
1.40 wiz 8470: <a name="shell-scripts"></a>19.4.4. Packages containing shell scripts</h3></div></div></div>
8471: <p><code class="varname">REPLACE_SH</code>,
8472: <code class="varname">REPLACE_BASH</code>, <code class="varname">REPLACE_CSH</code>,
8473: and <code class="varname">REPLACE_KSH</code> can be used to replace shell
8474: hash bangs in files. Please use the appropriate one, prefering
8475: <code class="varname">REPLACE_SH</code> in case this shell is sufficient.
1.74 wiz 8476: Each should contain a list of scripts, relative to
8477: <code class="varname">WRKSRC</code>, that you want adjusted. Every
8478: occurrence of the matching shell in a she-bang line will be
8479: replaced with the full path to the shell executable.
1.40 wiz 8480: When using <code class="varname">REPLACE_BASH</code>, don't forget to add
8481: <code class="filename">bash</code> to <code class="varname">USE_TOOLS</code>.</p>
8482: </div>
1.41 asau 8483: <div class="sect2">
1.40 wiz 8484: <div class="titlepage"><div><div><h3 class="title">
8485: <a name="other-programming-languages"></a>19.4.5. Other programming languages</h3></div></div></div>
1.1 dsieger 8486: <p>Currently, there is no special handling for other languages
8487: in pkgsrc. If a compiler package provides a
8488: <code class="filename">buildlink3.mk</code> file, include that, otherwise
8489: just add a (build) dependency on the appropriate compiler
8490: package.</p>
8491: </div>
8492: </div>
1.41 asau 8493: <div class="sect1">
1.1 dsieger 8494: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 8495: <a name="fixes.build"></a>19.5. Fixing problems in the <span class="emphasis"><em>build</em></span> phase</h2></div></div></div>
1.1 dsieger 8496: <p>The most common failures when building a package are that
8497: some platforms do not provide certain header files, functions or
8498: libraries, or they provide the functions in a library that the
8499: original package author didn't know. To work around this, you
8500: can rewrite the source code in most cases so that it does not
8501: use the missing functions or provides a replacement function.</p>
1.41 asau 8502: <div class="sect2">
1.1 dsieger 8503: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8504: <a name="fixes.build.cpp"></a>19.5.1. Compiling C and C++ code conditionally</h3></div></div></div>
1.1 dsieger 8505: <p>If a package already comes with a GNU configure script, the
8506: preferred way to fix the build failure is to change the
8507: configure script, not the code. In the other cases, you can
8508: utilize the C preprocessor, which defines certain macros
8509: depending on the operating system and hardware architecture it
8510: compiles for. These macros can be queried using for example
8511: <code class="varname">#if defined(__i386)</code>. Almost every operating
8512: system, hardware architecture and compiler has its own macro.
8513: For example, if the macros <code class="varname">__GNUC__</code>,
8514: <code class="varname">__i386__</code> and <code class="varname">__NetBSD__</code>
8515: are all defined, you know that you are using NetBSD on an i386
8516: compatible CPU, and your compiler is GCC.</p>
8517: <p>The list of the following macros for hardware and
8518: operating system depends on the compiler that is used. For
8519: example, if you want to conditionally compile code on Solaris,
8520: don't use <code class="varname">__sun__</code>, as the SunPro compiler
8521: does not define it. Use <code class="varname">__sun</code> instead.</p>
1.41 asau 8522: <div class="sect3">
1.1 dsieger 8523: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 8524: <a name="fixes.build.cpp.os"></a>19.5.1.1. C preprocessor macros to identify the operating system</h4></div></div></div>
1.1 dsieger 8525: <p>To distinguish between 4.4 BSD-derived systems and the
8526: rest of the world, you should use the following code.</p>
8527: <pre class="programlisting">
8528: #include <sys/param.h>
8529: #if (defined(BSD) && BSD >= 199306)
8530: /* BSD-specific code goes here */
8531: #else
8532: /* non-BSD-specific code goes here */
8533: #endif
8534: </pre>
8535: <p>If this distinction is not fine enough, you can also test
8536: for the following macros.</p>
8537: <pre class="programlisting">
1.45 obache 8538: Cygwin __CYGWIN__
8539: DragonFly __DragonFly__
1.1 dsieger 8540: FreeBSD __FreeBSD__
1.45 obache 8541: Haiku __HAIKU__
1.1 dsieger 8542: Interix __INTERIX
8543: IRIX __sgi (TODO: get a definite source for this)
8544: Linux linux, __linux, __linux__
1.83 dholland 8545: Mac OS X __APPLE__
1.45 obache 8546: MirBSD __MirBSD__ (__OpenBSD__ is also defined)
8547: Minix3 __minix
1.1 dsieger 8548: NetBSD __NetBSD__
8549: OpenBSD __OpenBSD__
8550: Solaris sun, __sun
8551: </pre>
8552: </div>
1.41 asau 8553: <div class="sect3">
1.1 dsieger 8554: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 8555: <a name="fixes.build.cpp.arch"></a>19.5.1.2. C preprocessor macros to identify the hardware architecture</h4></div></div></div>
1.1 dsieger 8556: <pre class="programlisting">
8557: i386 i386, __i386, __i386__
8558: MIPS __mips
8559: SPARC sparc, __sparc
8560: </pre>
8561: </div>
1.41 asau 8562: <div class="sect3">
1.1 dsieger 8563: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 8564: <a name="fixes.build.cpp.compiler"></a>19.5.1.3. C preprocessor macros to identify the compiler</h4></div></div></div>
1.1 dsieger 8565: <pre class="programlisting">
8566: GCC __GNUC__ (major version), __GNUC_MINOR__
8567: MIPSpro _COMPILER_VERSION (0x741 for MIPSpro 7.41)
8568: SunPro __SUNPRO_C (0x570 for Sun C 5.7)
8569: SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8)
8570: </pre>
8571: </div>
8572: </div>
1.41 asau 8573: <div class="sect2">
1.1 dsieger 8574: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8575: <a name="compiler-bugs"></a>19.5.2. How to handle compiler bugs</h3></div></div></div>
1.1 dsieger 8576: <p>Some source files trigger bugs in the compiler, based on
8577: combinations of compiler version and architecture and almost
8578: always relation to optimisation being enabled. Common symptoms
8579: are gcc internal errors or never finishing compiling a
8580: file.</p>
8581: <p>Typically, a workaround involves testing the
8582: <code class="varname">MACHINE_ARCH</code> and compiler version, disabling
8583: optimisation for that combination of file,
1.87 tnn 8584: <code class="varname">MACHINE_ARCH</code> and compiler.</p>
8585: <p>This used to be a big problem in the past, but is rarely
8586: needed now as compiler technology has matured. If you still need
8587: to add a compiler specific workaround, please do so in the file
8588: <code class="filename">hacks.mk</code> and describe the symptom and
8589: compiler version as detailed as possible.</p>
1.1 dsieger 8590: </div>
1.41 asau 8591: <div class="sect2">
1.1 dsieger 8592: <div class="titlepage"><div><div><h3 class="title">
1.23 wiz 8593: <a name="undefined-reference"></a>19.5.3. Undefined reference to <span class="quote">“<span class="quote">...</span>”</span>
8594: </h3></div></div></div>
1.1 dsieger 8595: <p>This error message often means that a package did not
8596: link to a shared library it needs. The following functions are
8597: known to cause this error message over and over.</p>
8598: <div class="informaltable">
8599: <a name="undefined-reference-functions"></a><table border="1">
8600: <colgroup>
8601: <col>
8602: <col>
8603: <col>
8604: </colgroup>
8605: <thead><tr>
8606: <th>Function</th>
8607: <th>Library</th>
8608: <th>Affected platforms</th>
8609: </tr></thead>
8610: <tbody>
8611: <tr>
8612: <td>accept, bind, connect</td>
8613: <td>-lsocket</td>
8614: <td>Solaris</td>
8615: </tr>
8616: <tr>
8617: <td>crypt</td>
8618: <td>-lcrypt</td>
8619: <td>DragonFly, NetBSD</td>
8620: </tr>
8621: <tr>
8622: <td>dlopen, dlsym</td>
8623: <td>-ldl</td>
8624: <td>Linux</td>
8625: </tr>
8626: <tr>
8627: <td>gethost*</td>
8628: <td>-lnsl</td>
8629: <td>Solaris</td>
8630: </tr>
8631: <tr>
8632: <td>inet_aton</td>
8633: <td>-lresolv</td>
8634: <td>Solaris</td>
8635: </tr>
8636: <tr>
8637: <td>nanosleep, sem_*, timer_*</td>
8638: <td>-lrt</td>
8639: <td>Solaris</td>
8640: </tr>
8641: <tr>
8642: <td>openpty</td>
8643: <td>-lutil</td>
8644: <td>Linux</td>
8645: </tr>
8646: </tbody>
8647: </table>
8648: </div>
8649: <p>To fix these linker errors, it is often sufficient to say
8650: <code class="literal">LIBS.<em class="replaceable"><code>OperatingSystem</code></em>+=
8651: -l<em class="replaceable"><code>foo</code></em></code> to the package
1.10 hubertf 8652: <code class="filename">Makefile</code> and then say <span class="command"><strong>bmake clean;
1.1 dsieger 8653: bmake</strong></span>.</p>
1.41 asau 8654: <div class="sect3">
1.1 dsieger 8655: <div class="titlepage"><div><div><h4 class="title">
1.6 rillig 8656: <a name="undefined-reference-sunpro"></a>19.5.3.1. Special issue: The SunPro compiler</h4></div></div></div>
1.1 dsieger 8657: <p>When you are using the SunPro compiler, there is another
8658: possibility. That compiler cannot handle the following code:</p>
8659: <pre class="programlisting">
8660: extern int extern_func(int);
8661:
8662: static inline int
8663: inline_func(int x)
8664: {
8665: return extern_func(x);
8666: }
8667:
8668: int main(void)
8669: {
8670: return 0;
8671: }
8672: </pre>
8673: <p>It generates the code for <code class="function">inline_func</code> even if
8674: that function is never used. This code then refers to
8675: <code class="function">extern_func</code>, which can usually not be resolved. To
8676: solve this problem you can try to tell the package to disable inlining
8677: of functions.</p>
8678: </div>
8679: </div>
1.41 asau 8680: <div class="sect2">
1.1 dsieger 8681: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8682: <a name="out-of-memory"></a>19.5.4. Running out of memory</h3></div></div></div>
1.1 dsieger 8683: <p>Sometimes packages fail to build because the compiler runs
8684: into an operating system specific soft limit. With the
8685: <code class="varname">UNLIMIT_RESOURCES</code> variable pkgsrc can be told
1.94 wiz 8686: to unlimit the resources. Currently, the allowed values are any combination of
8687: <span class="quote">“<span class="quote">cputime</span>”</span>, <span class="quote">“<span class="quote">datasize</span>”</span>,
8688: <span class="quote">“<span class="quote">memorysize</span>”</span>, and <span class="quote">“<span class="quote">stacksize</span>”</span>.
1.1 dsieger 8689: Setting this variable is similar to running the shell builtin
1.10 hubertf 8690: <span class="command"><strong>ulimit</strong></span> command to raise the maximum data
1.1 dsieger 8691: segment size or maximum stack size of a process, respectively, to
8692: their hard limits.</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.6 rillig 8697: <a name="fixes.install"></a>19.6. Fixing problems in the <span class="emphasis"><em>install</em></span> phase</h2></div></div></div>
1.41 asau 8698: <div class="sect2">
1.1 dsieger 8699: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8700: <a name="install-scripts"></a>19.6.1. Creating needed directories</h3></div></div></div>
1.10 hubertf 8701: <p>The BSD-compatible <span class="command"><strong>install</strong></span> supplied
1.1 dsieger 8702: with some operating systems cannot create more than one
8703: directory at a time. As such, you should call
8704: <code class="literal">${INSTALL_*_DIR}</code> like this:</p>
8705: <pre class="programlisting">
8706: ${INSTALL_DATA_DIR} ${PREFIX}/dir1
8707: ${INSTALL_DATA_DIR} ${PREFIX}/dir2
8708: </pre>
1.23 wiz 8709: <p>You can also just append <span class="quote">“<span class="quote"><code class="literal">dir1
8710: dir2</code></span>”</span> to the
1.1 dsieger 8711: <code class="varname">INSTALLATION_DIRS</code> variable, which will
8712: automatically do the right thing.</p>
8713: </div>
1.41 asau 8714: <div class="sect2">
1.1 dsieger 8715: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8716: <a name="where-to-install-documentation"></a>19.6.2. Where to install documentation</h3></div></div></div>
1.1 dsieger 8717: <p>In general, documentation should be installed into
8718: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
8719: <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code> (the latter
8720: includes the version number of the package).</p>
8721: <p>Many modern packages using GNU autoconf allow to set the
8722: directory where HTML documentation is installed with the
1.23 wiz 8723: <span class="quote">“<span class="quote">--with-html-dir</span>”</span> option. Sometimes using this flag
1.1 dsieger 8724: is needed because otherwise the documentation ends up in
8725: <code class="filename">${PREFIX}/share/doc/html</code> or other
8726: places.</p>
8727: <p>An exception to the above is that library API documentation
1.79 snj 8728: generated with the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/textproc/gtk-doc/README.html" target="_top"><code class="filename">textproc/gtk-doc</code></a> tools, for use by special
1.1 dsieger 8729: browsers (devhelp) should be left at their default location, which
8730: is <code class="filename">${PREFIX}/share/gtk-doc</code>. Such
8731: documentation can be recognized from files ending in
8732: <code class="filename">.devhelp</code> or <code class="filename">.devhelp2</code>.
8733: (It is also acceptable to install such files in
8734: <code class="filename">${PREFIX}/share/doc/${PKGBASE}</code> or
8735: <code class="filename">${PREFIX}/share/doc/${PKGNAME}</code>; the
8736: <code class="filename">.devhelp*</code> file must be directly in that
8737: directory then, no additional subdirectory level is allowed in
8738: this case. This is usually achieved by using
1.23 wiz 8739: <span class="quote">“<span class="quote">--with-html-dir=${PREFIX}/share/doc</span>”</span>.
1.1 dsieger 8740: <code class="filename">${PREFIX}/share/gtk-doc</code> is preferred
8741: though.)</p>
8742: </div>
1.41 asau 8743: <div class="sect2">
1.1 dsieger 8744: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8745: <a name="installing-score-files"></a>19.6.3. Installing highscore files</h3></div></div></div>
1.1 dsieger 8746: <p>Certain packages, most of them in the games category, install
8747: a score file that allows all users on the system to record their
8748: highscores. In order for this to work, the binaries need to be
8749: installed setgid and the score files owned by the appropriate
1.35 wiz 8750: group and/or owner (traditionally the "games" user/group). Set
8751: <code class="varname">USE_GAMESGROUP</code> to yes to support this. The
1.1 dsieger 8752: following variables, documented in more detail in
8753: <code class="filename">mk/defaults/mk.conf</code>, control this
1.35 wiz 8754: behaviour: <code class="varname">GAMEDATAMODE</code>,
8755: <code class="varname">GAMEDIRMODE</code>, <code class="varname">GAMES_GROUP</code>,
1.100 leot 8756: <code class="varname">GAMEMODE</code>, <code class="varname">GAME_USER</code>.
8757: Other useful variables are: <code class="varname">GAMEDIR_PERMS</code>,
8758: <code class="varname">GAMEDATA_PERMS</code> and
8759: <code class="varname">SETGID_GAMES_PERMS</code>.</p>
8760: <p>An example that illustrates some of the variables described above is
8761: <code class="filename">games/moon-buggy</code>. <code class="varname">OWN_DIRS_PERMS</code> is
8762: used to properly set directory permissions of the directory where the
8763: scorefile is saved, <code class="varname">REQD_FILES_PERMS</code> is used to create a
8764: dummy scorefile (<code class="filename">mbscore</code>) with the proper permissions
8765: and <code class="varname">SPECIAL_PERMS</code> is used to install setgid the game
8766: binary:</p>
8767: <pre class="programlisting">
8768: USE_GAMESGROUP= yes
8769:
8770: BUILD_DEFS+= VARBASE
8771:
8772: OWN_DIRS_PERMS+= ${VARBASE}/games/moon-buggy ${GAMEDIR_PERMS}
8773: REQD_FILES_PERMS+= /dev/null ${VARBASE}/games/moon-buggy/mbscore ${GAMEDATA_PERMS}
8774: SPECIAL_PERMS+= ${PREFIX}/bin/moon-buggy ${SETGID_GAMES_PERMS}
8775: </pre>
8776: <p>Various <code class="varname">INSTALL_*</code> variables are also available:
8777: <code class="varname">INSTALL_GAME</code> to install setgid game binaries,
8778: <code class="varname">INSTALL_GAME_DIR</code> to install game directories that are
8779: needed to be accessed by setgid games and
8780: <code class="varname">INSTALL_GAME_DATA</code> to install scorefiles.</p>
1.14 jmcneill 8781: <p>A package should therefore never hard code file ownership or
1.100 leot 8782: access permissions but rely on <code class="varname">*_PERMS</code> as described above
8783: or alternatively on <code class="varname">INSTALL_GAME</code>,
8784: <code class="varname">INSTALL_GAME_DATA</code> and
8785: <code class="varname">INSTALL_GAME_DIR</code> to set these correctly.</p>
1.1 dsieger 8786: </div>
1.41 asau 8787: <div class="sect2">
1.1 dsieger 8788: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8789: <a name="destdir-support"></a>19.6.4. Adding DESTDIR support to packages</h3></div></div></div>
1.14 jmcneill 8790: <p><code class="varname">DESTDIR</code> support means that a package
8791: installs into a staging directory, not the final location of the
8792: files. Then a binary package is created which can be used for
8793: installation as usual. There are two ways: Either the package must
1.23 wiz 8794: install as root (<span class="quote">“<span class="quote">destdir</span>”</span>) or the package can
8795: install as non-root user (<span class="quote">“<span class="quote">user-destdir</span>”</span>).</p>
1.41 asau 8796: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 8797: <li class="listitem"><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be
1.38 wiz 8798: set to <span class="quote">“<span class="quote">none</span>”</span>, <span class="quote">“<span class="quote">destdir</span>”</span>, or
8799: <span class="quote">“<span class="quote">user-destdir</span>”</span>. By default <code class="varname">PKG_DESTDIR_SUPPORT</code>
8800: is set to <span class="quote">“<span class="quote">user-destdir</span>”</span> to help catching more
8801: potential packaging problems. If bsd.prefs.mk is included in the Makefile,
1.14 jmcneill 8802: <code class="varname">PKG_DESTDIR_SUPPORT</code> needs to be set before
8803: the inclusion.</p></li>
1.23 wiz 8804: <li class="listitem"><p>All installation operations have to be prefixed with
1.4 rillig 8805: <code class="filename">${DESTDIR}</code>.</p></li>
1.23 wiz 8806: <li class="listitem"><p>automake gets this DESTDIR mostly right
1.4 rillig 8807: automatically. Many manual rules and pre/post-install often are
8808: incorrect; fix them.</p></li>
1.23 wiz 8809: <li class="listitem"><p>If files are installed with special owner/group
1.17 imil 8810: use <code class="varname">SPECIAL_PERMS</code>.</p></li>
1.23 wiz 8811: <li class="listitem"><p>In general, packages should support
1.4 rillig 8812: <code class="varname">UNPRIVILEGED</code> to be able to use
8813: DESTDIR.</p></li>
8814: </ul></div>
8815: </div>
1.41 asau 8816: <div class="sect2">
1.4 rillig 8817: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8818: <a name="hardcoded-paths"></a>19.6.5. Packages with hardcoded paths to other interpreters</h3></div></div></div>
1.1 dsieger 8819: <p>Your package may also contain scripts with hardcoded paths to
8820: other interpreters besides (or as well as) perl. To correct the
8821: full pathname to the script interpreter, you need to set the
8822: following definitions in your <code class="filename">Makefile</code> (we
1.10 hubertf 8823: shall use <span class="command"><strong>tclsh</strong></span> in this example):</p>
1.1 dsieger 8824: <pre class="programlisting">
8825: REPLACE_INTERPRETER+= tcl
8826: REPLACE.tcl.old= .*/bin/tclsh
8827: REPLACE.tcl.new= ${PREFIX}/bin/tclsh
8828: REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed,
8829: # relative to ${WRKSRC}, just as in REPLACE_PERL
8830: </pre>
1.41 asau 8831: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 8832: <h3 class="title">Note</h3>
8833: <p>Before March 2006, these variables were called
8834: <code class="varname">_REPLACE.*</code> and
8835: <code class="varname">_REPLACE_FILES.*</code>.</p>
8836: </div>
8837: </div>
1.41 asau 8838: <div class="sect2">
1.1 dsieger 8839: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8840: <a name="perl-modules"></a>19.6.6. Packages installing perl modules</h3></div></div></div>
1.1 dsieger 8841: <p>Makefiles of packages providing perl5 modules should include
8842: the Makefile fragment
8843: <code class="filename">../../lang/perl5/module.mk</code>. It provides a
1.10 hubertf 8844: <span class="command"><strong>do-configure</strong></span> target for the standard perl
1.1 dsieger 8845: configuration for such modules as well as various hooks to tune
8846: this configuration. See comments in this file for
8847: details.</p>
8848: <p>Perl5 modules will install into different places depending
8849: on the version of perl used during the build process. To
8850: address this, pkgsrc will append lines to the
8851: <code class="filename">PLIST</code> corresponding to the files listed in
8852: the installed <code class="filename">.packlist</code> file generated by
8853: most perl5 modules. This is invoked by defining
8854: <code class="varname">PERL5_PACKLIST</code> to a space-separated list of
1.47 wiz 8855: packlist files relative to <code class="varname">PERL5_PACKLIST_DIR</code>
8856: (<code class="varname">PERL5_INSTALLVENDORARCH</code> by default),
8857: e.g.:</p>
1.1 dsieger 8858: <pre class="programlisting">
1.47 wiz 8859: PERL5_PACKLIST= auto/Pg/.packlist
1.1 dsieger 8860: </pre>
1.47 wiz 8861: <p>The perl5 config variables
8862: <code class="varname">installarchlib</code>,
8863: <code class="varname">installscript</code>,
8864: <code class="varname">installvendorbin</code>,
8865: <code class="varname">installvendorscript</code>,
8866: <code class="varname">installvendorarch</code>,
8867: <code class="varname">installvendorlib</code>,
8868: <code class="varname">installvendorman1dir</code>, and
8869: <code class="varname">installvendorman3dir</code> represent those
8870: locations in which components of perl5 modules may be installed,
8871: provided as variable with uppercase and prefixed with
8872: <code class="varname">PERL5_</code>, e.g. <code class="varname">PERL5_INSTALLARCHLIB</code>
8873: and may be used by perl5 packages that don't have a packlist.
8874: These variables are also substituted for in the
8875: <code class="filename">PLIST</code> as uppercase prefixed with
8876: <code class="varname">PERL5_SUB_</code>.</p>
1.1 dsieger 8877: </div>
1.41 asau 8878: <div class="sect2">
1.1 dsieger 8879: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8880: <a name="faq.info-files"></a>19.6.7. Packages installing info files</h3></div></div></div>
1.1 dsieger 8881: <p>Some packages install info files or use the
1.23 wiz 8882: <span class="quote">“<span class="quote">makeinfo</span>”</span> or <span class="quote">“<span class="quote">install-info</span>”</span>
1.1 dsieger 8883: commands. <code class="varname">INFO_FILES</code> should be defined in
8884: the package Makefile so that <code class="filename">INSTALL</code> and
8885: <code class="filename">DEINSTALL</code> scripts will be generated to
8886: handle registration of the info files in the Info directory
1.23 wiz 8887: file. The <span class="quote">“<span class="quote">install-info</span>”</span> command used for the info
1.1 dsieger 8888: files registration is either provided by the system, or by a
8889: special purpose package automatically added as dependency if
8890: needed.</p>
8891: <p><code class="varname">PKGINFODIR</code> is the directory under
8892: <code class="filename">${PREFIX}</code> where info files are primarily
8893: located. <code class="varname">PKGINFODIR</code> defaults to
1.23 wiz 8894: <span class="quote">“<span class="quote">info</span>”</span> and can be overridden by the user.</p>
1.1 dsieger 8895: <p>The info files for the package should be listed in the
8896: package <code class="filename">PLIST</code>; however any split info files
8897: need not be listed.</p>
1.23 wiz 8898: <p>A package which needs the <span class="quote">“<span class="quote">makeinfo</span>”</span> command
8899: at build time must add <span class="quote">“<span class="quote">makeinfo</span>”</span> to
1.1 dsieger 8900: <code class="varname">USE_TOOLS</code> in its Makefile. If a minimum
1.23 wiz 8901: version of the <span class="quote">“<span class="quote">makeinfo</span>”</span> command is needed it
1.1 dsieger 8902: should be noted with the <code class="varname">TEXINFO_REQD</code>
8903: variable in the package <code class="filename">Makefile</code>. By
8904: default, a minimum version of 3.12 is required. If the system
1.10 hubertf 8905: does not provide a <span class="command"><strong>makeinfo</strong></span> command or if it
1.1 dsieger 8906: does not match the required minimum, a build dependency on the
1.79 snj 8907: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/gtexinfo/README.html" target="_top"><code class="filename">devel/gtexinfo</code></a> package will
1.1 dsieger 8908: be added automatically.</p>
8909: <p>The build and installation process of the software provided
8910: by the package should not use the
1.10 hubertf 8911: <span class="command"><strong>install-info</strong></span> command as the registration of
1.1 dsieger 8912: info files is the task of the package
8913: <code class="filename">INSTALL</code> script, and it must use the
1.10 hubertf 8914: appropriate <span class="command"><strong>makeinfo</strong></span> command.</p>
1.1 dsieger 8915: <p>To achieve this goal, the pkgsrc infrastructure creates
1.10 hubertf 8916: overriding scripts for the <span class="command"><strong>install-info</strong></span> and
8917: <span class="command"><strong>makeinfo</strong></span> commands in a directory listed early
1.1 dsieger 8918: in <code class="varname">PATH</code>.</p>
1.10 hubertf 8919: <p>The script overriding <span class="command"><strong>install-info</strong></span> has
1.1 dsieger 8920: no effect except the logging of a message. The script overriding
1.10 hubertf 8921: <span class="command"><strong>makeinfo</strong></span> logs a message and according to the
1.1 dsieger 8922: value of <code class="varname">TEXINFO_REQD</code> either runs the appropriate
1.10 hubertf 8923: <span class="command"><strong>makeinfo</strong></span> command or exit on error.</p>
1.1 dsieger 8924: </div>
1.41 asau 8925: <div class="sect2">
1.1 dsieger 8926: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 8927: <a name="manpages"></a>19.6.8. Packages installing man pages</h3></div></div></div>
1.1 dsieger 8928: <p>All packages that install manual pages should install them
8929: into the same directory, so that there is one common place to look
8930: for them. In pkgsrc, this place is
8931: <code class="literal">${PREFIX}/${PKGMANDIR}</code>, and this expression
8932: should be used in packages. The default for
8933: <code class="varname">PKGMANDIR</code> is
1.23 wiz 8934: <span class="quote">“<span class="quote"><code class="filename">man</code></span>”</span>. Another often-used value
8935: is <span class="quote">“<span class="quote"><code class="filename">share/man</code></span>”</span>.</p>
1.41 asau 8936: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 8937: <h3 class="title">Note</h3>
8938: <p>The support for a custom <code class="varname">PKGMANDIR</code>
8939: is far from complete.</p>
8940: </div>
8941: <p>The <code class="filename">PLIST</code> files can just use
8942: <code class="filename">man/</code> as the top level directory for the man
8943: page file entries, and the pkgsrc framework will convert as
8944: needed. In all other places, the correct
8945: <code class="varname">PKGMANDIR</code> must be used.</p>
8946: <p>Packages that are
8947: configured with <code class="varname">GNU_CONFIGURE</code> set as
1.23 wiz 8948: <span class="quote">“<span class="quote">yes</span>”</span>, by default will use the
1.1 dsieger 8949: <code class="filename">./configure</code>
8950: --mandir switch to set where the man pages should be installed.
8951: The path is <code class="varname">GNU_CONFIGURE_MANDIR</code> which defaults
8952: to <code class="varname">${PREFIX}/${PKGMANDIR}</code>.</p>
8953: <p>Packages that use <code class="varname">GNU_CONFIGURE</code> but do not
8954: use --mandir, can set <code class="varname">CONFIGURE_HAS_MANDIR</code>
1.23 wiz 8955: to <span class="quote">“<span class="quote">no</span>”</span>.
1.1 dsieger 8956: Or if the <code class="filename">./configure</code> script uses
8957: a non-standard use of --mandir, you can set
8958: <code class="varname">GNU_CONFIGURE_MANDIR</code> as needed.</p>
1.10 hubertf 8959: <p>See <a class="xref" href="#manpage-compression" title="13.5. Man page compression">Section 13.5, “Man page compression”</a> for
1.1 dsieger 8960: information on installation of compressed manual pages.</p>
8961: </div>
1.41 asau 8962: <div class="sect2">
1.1 dsieger 8963: <div class="titlepage"><div><div><h3 class="title">
1.7 rillig 8964: <a name="gconf-data-files"></a>19.6.9. Packages installing GConf data files</h3></div></div></div>
1.1 dsieger 8965: <p>If a package installs <code class="filename">.schemas</code> or
1.7 rillig 8966: <code class="filename">.entries</code> files, used by GConf,
1.1 dsieger 8967: you need to take some extra steps to make sure they get registered
8968: in the database:</p>
1.23 wiz 8969: <div class="orderedlist"><ol class="orderedlist" type="1">
8970: <li class="listitem"><p>Include <code class="filename">../../devel/GConf/schemas.mk</code>
1.1 dsieger 8971: instead of its <code class="filename">buildlink3.mk</code> file. This
1.7 rillig 8972: takes care of rebuilding the GConf database at installation and
1.1 dsieger 8973: deinstallation time, and tells the package where to install
1.7 rillig 8974: GConf data files using some standard configure arguments. It
1.1 dsieger 8975: also disallows any access to the database directly from the
8976: package.</p></li>
1.23 wiz 8977: <li class="listitem"><p>Ensure that the package installs its
1.1 dsieger 8978: <code class="filename">.schemas</code> files under
8979: <code class="filename">${PREFIX}/share/gconf/schemas</code>. If they get
8980: installed under <code class="filename">${PREFIX}/etc</code>, you will
8981: need to manually patch the package.</p></li>
1.23 wiz 8982: <li class="listitem"><p>Check the PLIST and remove any entries under the etc/gconf
1.1 dsieger 8983: directory, as they will be handled automatically. See
1.84 wiz 8984: <a class="xref" href="#faq.conf" title="9.13. How do I change the location of configuration files?">Section 9.13, “How do I change the location of configuration files?”</a> for more information.</p></li>
1.23 wiz 8985: <li class="listitem"><p>Define the <code class="varname">GCONF_SCHEMAS</code> variable in
1.1 dsieger 8986: your <code class="filename">Makefile</code> with a list of all
8987: <code class="filename">.schemas</code> files installed by the package, if
8988: any. Names must not contain any directories in them.</p></li>
1.23 wiz 8989: <li class="listitem"><p>Define the <code class="varname">GCONF_ENTRIES</code> variable in
1.1 dsieger 8990: your <code class="filename">Makefile</code> with a
8991: list of all <code class="filename">.entries</code> files installed by the
8992: package, if any. Names must not contain any directories in
8993: them.</p></li>
8994: </ol></div>
8995: </div>
1.41 asau 8996: <div class="sect2">
1.1 dsieger 8997: <div class="titlepage"><div><div><h3 class="title">
1.18 snj 8998: <a name="scrollkeeper-data-files"></a>19.6.10. Packages installing scrollkeeper/rarian data files</h3></div></div></div>
1.1 dsieger 8999: <p>If a package installs <code class="filename">.omf</code> files, used by
1.18 snj 9000: scrollkeeper/rarian, you need to take some extra steps to make sure they
1.1 dsieger 9001: get registered in the database:</p>
1.23 wiz 9002: <div class="orderedlist"><ol class="orderedlist" type="1">
9003: <li class="listitem"><p>Include
1.18 snj 9004: <code class="filename">../../mk/omf-scrollkeeper.mk</code>
9005: instead of rarian's <code class="filename">buildlink3.mk</code> file. This
1.1 dsieger 9006: takes care of rebuilding the scrollkeeper database at
9007: installation and deinstallation time, and disallows any access
9008: to it directly from the package.</p></li>
1.23 wiz 9009: <li class="listitem"><p>Check the PLIST and remove any entries under the
1.1 dsieger 9010: <code class="filename">libdata/scrollkeeper</code> directory, as they
9011: will be handled automatically.</p></li>
1.23 wiz 9012: <li class="listitem"><p>Remove the <code class="filename">share/omf</code> directory from
1.18 snj 9013: the PLIST. It will be handled by rarian. (<span class="command"><strong>make
9014: print-PLIST</strong></span> does this automatically.)</p></li>
1.1 dsieger 9015: </ol></div>
9016: </div>
1.41 asau 9017: <div class="sect2">
1.1 dsieger 9018: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9019: <a name="x11-fonts"></a>19.6.11. Packages installing X11 fonts</h3></div></div></div>
1.1 dsieger 9020: <p>If a package installs font files, you will need to rebuild
9021: the fonts database in the directory where they get installed at
9022: installation and deinstallation time. This can be automatically
9023: done by using the pkginstall framework.</p>
9024: <p>You can list the directories where fonts are installed in the
9025: <code class="varname">FONTS_DIRS.<em class="replaceable"><code>type</code></em></code>
9026: variables, where <em class="replaceable"><code>type</code></em> can be one of
1.23 wiz 9027: <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 9028: Also make sure that the database file
9029: <code class="filename">fonts.dir</code> is not listed in the PLIST.</p>
9030: <p>Note that you should not create new directories for fonts;
9031: instead use the standard ones to avoid that the user needs to
9032: manually configure his X server to find them.</p>
9033: </div>
1.41 asau 9034: <div class="sect2">
1.1 dsieger 9035: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9036: <a name="gtk2-modules"></a>19.6.12. Packages installing GTK2 modules</h3></div></div></div>
1.1 dsieger 9037: <p>If a package installs GTK2 immodules or loaders, you need to
9038: take some extra steps to get them registered in the GTK2 database
9039: properly:</p>
1.23 wiz 9040: <div class="orderedlist"><ol class="orderedlist" type="1">
9041: <li class="listitem"><p>Include
1.1 dsieger 9042: <code class="filename">../../x11/gtk2/modules.mk</code> instead of its
9043: <code class="filename">buildlink3.mk</code> file. This takes care of
9044: rebuilding the database at installation and deinstallation time.</p></li>
1.23 wiz 9045: <li class="listitem"><p>Set <code class="varname">GTK2_IMMODULES=YES</code> if
1.1 dsieger 9046: your package installs GTK2 immodules.</p></li>
1.23 wiz 9047: <li class="listitem"><p>Set <code class="varname">GTK2_LOADERS=YES</code> if your package installs
1.1 dsieger 9048: GTK2 loaders.</p></li>
1.23 wiz 9049: <li class="listitem">
1.1 dsieger 9050: <p>Patch the package to not touch any of the GTK2
9051: databases directly. These are:</p>
1.41 asau 9052: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9053: <li class="listitem"><p><code class="filename">libdata/gtk-2.0/gdk-pixbuf.loaders</code></p></li>
9054: <li class="listitem"><p><code class="filename">libdata/gtk-2.0/gtk.immodules</code></p></li>
1.1 dsieger 9055: </ul></div>
9056: </li>
1.23 wiz 9057: <li class="listitem"><p>Check the <code class="filename">PLIST</code> and remove
1.1 dsieger 9058: any entries under the <code class="filename">libdata/gtk-2.0</code>
9059: directory, as they will be handled automatically.</p></li>
9060: </ol></div>
9061: </div>
1.41 asau 9062: <div class="sect2">
1.1 dsieger 9063: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9064: <a name="sgml-xml-data"></a>19.6.13. Packages installing SGML or XML data</h3></div></div></div>
1.1 dsieger 9065: <p>If a package installs SGML or XML data files that need to be
9066: registered in system-wide catalogs (like DTDs, sub-catalogs,
9067: etc.), you need to take some extra steps:</p>
1.23 wiz 9068: <div class="orderedlist"><ol class="orderedlist" type="1">
9069: <li class="listitem"><p>Include
1.1 dsieger 9070: <code class="filename">../../textproc/xmlcatmgr/catalogs.mk</code> in
9071: your <code class="filename">Makefile</code>, which takes care of
9072: registering those files in system-wide catalogs at
9073: installation and deinstallation time.</p></li>
1.23 wiz 9074: <li class="listitem"><p>Set <code class="varname">SGML_CATALOGS</code> to the full path of
1.1 dsieger 9075: any SGML catalogs installed by the package.</p></li>
1.23 wiz 9076: <li class="listitem"><p>Set <code class="varname">XML_CATALOGS</code> to the full path of
1.1 dsieger 9077: any XML catalogs installed by the package.</p></li>
1.23 wiz 9078: <li class="listitem"><p>Set <code class="varname">SGML_ENTRIES</code> to individual entries
1.1 dsieger 9079: to be added to the SGML catalog. These come in groups of
9080: three strings; see xmlcatmgr(1) for more information
9081: (specifically, arguments recognized by the 'add' action).
9082: Note that you will normally not use this variable.</p></li>
1.23 wiz 9083: <li class="listitem"><p>Set <code class="varname">XML_ENTRIES</code> to individual entries
1.1 dsieger 9084: to be added to the XML catalog. These come in groups of three
9085: strings; see xmlcatmgr(1) for more information (specifically,
9086: arguments recognized by the 'add' action). Note that you will
9087: normally not use this variable.</p></li>
9088: </ol></div>
9089: </div>
1.41 asau 9090: <div class="sect2">
1.1 dsieger 9091: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9092: <a name="mime-database"></a>19.6.14. Packages installing extensions to the MIME database</h3></div></div></div>
1.1 dsieger 9093: <p>If a package provides extensions to the MIME database by
9094: installing <code class="filename">.xml</code> files inside
9095: <code class="filename">${PREFIX}/share/mime/packages</code>, you
9096: need to take some extra steps to ensure that the database is kept
9097: consistent with respect to these new files:</p>
1.23 wiz 9098: <div class="orderedlist"><ol class="orderedlist" type="1">
9099: <li class="listitem"><p>Include
1.1 dsieger 9100: <code class="filename">../../databases/shared-mime-info/mimedb.mk</code>
9101: (avoid using the <code class="filename">buildlink3.mk</code> file from
9102: this same directory, which is reserved for inclusion from
9103: other <code class="filename">buildlink3.mk</code> files). It takes
9104: care of rebuilding the MIME database at installation and
9105: deinstallation time, and disallows any access to it directly
9106: from the package.</p></li>
1.23 wiz 9107: <li class="listitem"><p>Check the PLIST and remove any entries under the
1.1 dsieger 9108: <code class="filename">share/mime</code> directory,
9109: <span class="emphasis"><em>except</em></span> for files saved under
9110: <code class="filename">share/mime/packages</code>. The former are
9111: handled automatically by
9112: the update-mime-database program, but the latter are
9113: package-dependent and must be removed by the package that
9114: installed them in the first place.</p></li>
1.23 wiz 9115: <li class="listitem"><p>Remove any <code class="filename">share/mime/*</code> directories
1.1 dsieger 9116: from the PLIST. They will be handled by the shared-mime-info
9117: package.</p></li>
9118: </ol></div>
9119: </div>
1.41 asau 9120: <div class="sect2">
1.1 dsieger 9121: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9122: <a name="intltool"></a>19.6.15. Packages using intltool</h3></div></div></div>
1.1 dsieger 9123: <p>If a package uses intltool during its build, add
9124: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>,
9125: which forces it to use the intltool package provided by pkgsrc,
9126: instead of the one bundled with the distribution file.</p>
9127: <p>This tracks intltool's build-time dependencies and uses the
9128: latest available version; this way, the package benefits of any
9129: bug fixes that may have appeared since it was released.</p>
9130: </div>
1.41 asau 9131: <div class="sect2">
1.1 dsieger 9132: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9133: <a name="startup-scripts"></a>19.6.16. Packages installing startup scripts</h3></div></div></div>
1.1 dsieger 9134: <p>If a package contains a rc.d script, it won't be copied into
9135: the startup directory by default, but you can enable it, by adding
9136: the option <code class="varname">PKG_RCD_SCRIPTS=YES</code> in
1.10 hubertf 9137: <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>. This option will copy the scripts
1.1 dsieger 9138: into <code class="filename">/etc/rc.d</code> when a package is installed, and
9139: it will automatically remove the scripts when the package is
9140: deinstalled.</p>
9141: </div>
1.41 asau 9142: <div class="sect2">
1.1 dsieger 9143: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9144: <a name="tex-packages"></a>19.6.17. Packages installing TeX modules</h3></div></div></div>
1.1 dsieger 9145: <p>If a package installs TeX packages into the texmf tree,
9146: the <code class="filename">ls-R</code> database of the tree needs to be
9147: updated.</p>
1.41 asau 9148: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9149: <h3 class="title">Note</h3>
1.22 jakllsch 9150: <p>Except the main TeX packages such as kpathsea,
1.1 dsieger 9151: packages should install files
1.22 jakllsch 9152: into <code class="filename">${PREFIX}/share/texmf-dist</code>,
9153: not <code class="filename">${PREFIX}/share/texmf</code>.</p>
1.1 dsieger 9154: </div>
1.23 wiz 9155: <div class="orderedlist"><ol class="orderedlist" type="1">
9156: <li class="listitem"><p>Include
1.22 jakllsch 9157: <code class="filename">../../print/kpathsea/texmf.mk</code>. This
1.1 dsieger 9158: takes care of rebuilding the <code class="filename">ls-R</code>
9159: database at installation and deinstallation time.</p></li>
1.23 wiz 9160: <li class="listitem">
1.1 dsieger 9161: <p>If your package installs files into a texmf
9162: tree other than the one
1.22 jakllsch 9163: at <code class="filename">${PREFIX}/share/texmf-dist</code>,
9164: set <code class="varname">TEX_TEXMF_DIRS</code> to the list of all texmf
1.1 dsieger 9165: trees that need database update.</p>
9166: <p>If your package also installs font map files that need
1.10 hubertf 9167: to be registered using <span class="command"><strong>updmap</strong></span>,
1.29 dholland 9168: include <code class="filename">../../print/tex-tetex/map.mk</code> and
1.22 jakllsch 9169: set <code class="varname">TEX_MAP_FILES</code> and/or
9170: <code class="varname">TEX_MIXEDMAP_FILES</code> to the list of all
1.10 hubertf 9171: such font map files. Then <span class="command"><strong>updmap</strong></span> will
1.1 dsieger 9172: be run automatically at installation/deinstallation to
9173: enable/disable font map files for TeX output
9174: drivers.</p>
9175: </li>
1.23 wiz 9176: <li class="listitem"><p>Make sure that none of <code class="filename">ls-R</code>
1.1 dsieger 9177: databases are included in <code class="filename">PLIST</code>, as
1.29 dholland 9178: they will be removed only by the kpathsea package.</p></li>
1.1 dsieger 9179: </ol></div>
9180: </div>
1.41 asau 9181: <div class="sect2">
1.1 dsieger 9182: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9183: <a name="emulation-packages"></a>19.6.18. Packages supporting running binaries in
1.1 dsieger 9184: emulation</h3></div></div></div>
9185: <p>There are some packages that provide libraries and
9186: executables for running binaries from a one operating system
9187: on a different one (if the latter supports it). One example
9188: is running Linux binaries on NetBSD.</p>
1.79 snj 9189: <p>The <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/rpm2pkg/README.html" target="_top"><code class="filename">pkgtools/rpm2pkg</code></a>
1.1 dsieger 9190: helps in extracting and packaging Linux rpm packages.</p>
9191: <p>The <code class="varname">CHECK_SHLIBS</code> can be set to no to
1.10 hubertf 9192: avoid the <span class="command"><strong>check-shlibs</strong></span> target, which tests
1.1 dsieger 9193: if all libraries for each installed executable can be found by
9194: the dynamic linker. Since the standard dynamic linker is run,
9195: this fails for emulation packages, because the libraries used
9196: by the emulation are not in the standard directories.</p>
9197: </div>
1.41 asau 9198: <div class="sect2">
1.1 dsieger 9199: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9200: <a name="hicolor-theme"></a>19.6.19. Packages installing hicolor theme icons</h3></div></div></div>
1.1 dsieger 9201: <p>If a package installs images under the
9202: <code class="filename">share/icons/hicolor</code> and/or updates the
9203: <code class="filename">share/icons/hicolor/icon-theme.cache</code>
9204: database, you need to take some extra steps to make sure that the
9205: shared theme directory is handled appropriately and that the cache
9206: database is rebuilt:</p>
1.23 wiz 9207: <div class="orderedlist"><ol class="orderedlist" type="1">
9208: <li class="listitem"><p>Include
1.1 dsieger 9209: <code class="filename">../../graphics/hicolor-icon-theme/buildlink3.mk</code>.</p></li>
1.23 wiz 9210: <li class="listitem"><p>Check the <code class="filename">PLIST</code> and remove the
1.1 dsieger 9211: entry that refers to the theme cache.</p></li>
1.23 wiz 9212: <li class="listitem"><p>Ensure that the PLIST does not remove the shared icon
1.1 dsieger 9213: directories from the <code class="filename">share/icons/hicolor</code>
9214: hierarchy because they will be handled automatically.</p></li>
9215: </ol></div>
9216: <p>The best way to verify that the PLIST is correct with
9217: respect to the last two points is to regenerate it using
1.10 hubertf 9218: <span class="command"><strong>make print-PLIST</strong></span>.</p>
1.1 dsieger 9219: </div>
1.41 asau 9220: <div class="sect2">
1.1 dsieger 9221: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 9222: <a name="desktop-files"></a>19.6.20. Packages installing desktop files</h3></div></div></div>
1.1 dsieger 9223: <p>If a package installs <code class="filename">.desktop</code> files
9224: under <code class="filename">share/applications</code> and these include
1.53 rodent 9225: MIME information (MimeType key), you need to take extra steps to
9226: ensure that they are registered into the MIME database:</p>
1.23 wiz 9227: <div class="orderedlist"><ol class="orderedlist" type="1">
9228: <li class="listitem"><p>Include
1.1 dsieger 9229: <code class="filename">../../sysutils/desktop-file-utils/desktopdb.mk</code>.</p></li>
1.23 wiz 9230: <li class="listitem"><p>Check the PLIST and remove the entry that refers to the
1.1 dsieger 9231: <code class="filename">share/applications/mimeinfo.cache</code> file.
9232: It will be handled automatically.</p></li>
9233: </ol></div>
9234: <p>The best way to verify that the PLIST is correct with
1.10 hubertf 9235: respect to the last point is to regenerate it using <span class="command"><strong>make
1.1 dsieger 9236: print-PLIST</strong></span>.</p>
9237: </div>
9238: </div>
1.41 asau 9239: <div class="sect1">
1.1 dsieger 9240: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9241: <a name="punting"></a>19.7. Marking packages as having problems</h2></div></div></div>
1.1 dsieger 9242: <p>In some cases one does not have the time to solve a problem
1.22 jakllsch 9243: immediately. In this case, one can plainly mark a package as broken. For
9244: this, one just sets the variable <code class="varname">BROKEN</code> to the
9245: reason why the package is broken (similar to the
9246: <code class="varname">RESTRICTED</code> variable). A user trying to build
9247: the package will immediately be shown this message, and the build
9248: will not be even tried.</p>
9249: <p><code class="varname">BROKEN</code> packages are removed from pkgsrc in irregular
1.1 dsieger 9250: intervals.</p>
9251: </div>
9252: </div>
1.41 asau 9253: <div class="chapter">
1.1 dsieger 9254: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 9255: <a name="debug"></a>Chapter 20. Debugging</h2></div></div></div>
1.1 dsieger 9256: <p>To check out all the gotchas when building a package, here are
9257: the steps that I do in order to get a package working. Please note
9258: this is basically the same as what was explained in the previous
9259: sections, only with some debugging aids.</p>
1.41 asau 9260: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9261: <li class="listitem"><p>Be sure to set <code class="varname">PKG_DEVELOPER=yes</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p></li>
9262: <li class="listitem">
1.79 snj 9263: <p>Install <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a>,
1.1 dsieger 9264: create a directory for a new package, change into it, then run
1.10 hubertf 9265: <span class="command"><strong>url2pkg</strong></span>:</p>
1.1 dsieger 9266: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>mkdir /usr/pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>examplepkg</code></em></code></strong>
9267: <code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc/<em class="replaceable"><code>category</code></em>/<em class="replaceable"><code>examplepkg</code></em></code></strong>
9268: <code class="prompt">%</code> <strong class="userinput"><code>url2pkg http://www.example.com/path/to/distfile.tar.gz</code></strong></pre>
9269: </li>
1.23 wiz 9270: <li class="listitem"><p>Edit the <code class="filename">Makefile</code> as requested.</p></li>
9271: <li class="listitem"><p>Fill in the <code class="filename">DESCR</code> file</p></li>
9272: <li class="listitem"><p>Run <span class="command"><strong>make configure</strong></span></p></li>
9273: <li class="listitem"><p>Add any dependencies glimpsed from documentation and the
1.1 dsieger 9274: configure step to the package's
9275: <code class="filename">Makefile</code>.</p></li>
1.23 wiz 9276: <li class="listitem">
1.1 dsieger 9277: <p>Make the package compile, doing multiple rounds of</p>
9278: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>make</code></strong>
9279: <code class="prompt">%</code> <strong class="userinput"><code>pkgvi ${WRKSRC}/some/file/that/does/not/compile</code></strong>
9280: <code class="prompt">%</code> <strong class="userinput"><code>mkpatches</code></strong>
9281: <code class="prompt">%</code> <strong class="userinput"><code>patchdiff</code></strong>
9282: <code class="prompt">%</code> <strong class="userinput"><code>mv ${WRKDIR}/.newpatches/* patches</code></strong>
9283: <code class="prompt">%</code> <strong class="userinput"><code>make mps</code></strong>
9284: <code class="prompt">%</code> <strong class="userinput"><code>make clean</code></strong></pre>
9285: <p>Doing this step as non-root user will ensure that no files
9286: are modified that shouldn't be, especially during the build
1.10 hubertf 9287: phase. <span class="command"><strong>mkpatches</strong></span>,
9288: <span class="command"><strong>patchdiff</strong></span> and <span class="command"><strong>pkgvi</strong></span> are
1.79 snj 9289: from the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html" target="_top"><code class="filename">pkgtools/pkgdiff</code></a>
1.1 dsieger 9290: package.</p>
9291: </li>
1.23 wiz 9292: <li class="listitem"><p>Look at the <code class="filename">Makefile</code>, fix if
9293: necessary; see <a class="xref" href="#components.Makefile" title="11.1. Makefile">Section 11.1, “<code class="filename">Makefile</code>”</a>.</p></li>
9294: <li class="listitem">
1.1 dsieger 9295: <p>Generate a <code class="filename">PLIST</code>:</p>
9296: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
9297: <code class="prompt">#</code> <strong class="userinput"><code>make print-PLIST >PLIST</code></strong>
9298: <code class="prompt">#</code> <strong class="userinput"><code>make deinstall</code></strong>
9299: <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
9300: <code class="prompt">#</code> <strong class="userinput"><code>make deinstall</code></strong></pre>
9301: <p>You usually need to be <code class="username">root</code> to do
9302: this. Look if there are any files left:</p>
9303: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make print-PLIST</code></strong></pre>
9304: <p>If this reveals any files that are missing in
9305: <code class="filename">PLIST</code>, add them.</p>
9306: </li>
1.23 wiz 9307: <li class="listitem">
1.1 dsieger 9308: <p>Now that the <code class="filename">PLIST</code> is OK, install the
9309: package again and make a binary package:</p>
9310: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make reinstall</code></strong>
9311: <code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong></pre>
9312: </li>
1.23 wiz 9313: <li class="listitem">
1.1 dsieger 9314: <p>Delete the installed package:</p>
9315: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>pkg_delete <em class="replaceable"><code>examplepkg</code></em></code></strong></pre>
9316: </li>
1.23 wiz 9317: <li class="listitem">
1.10 hubertf 9318: <p>Repeat the above <span class="command"><strong>make print-PLIST</strong></span>
1.1 dsieger 9319: command, which shouldn't find anything now:</p>
9320: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make print-PLIST</code></strong></pre>
9321: </li>
1.23 wiz 9322: <li class="listitem">
1.1 dsieger 9323: <p>Reinstall the binary package:</p>
9324: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>pkg_add .../<em class="replaceable"><code>examplepkg</code></em>.tgz</code></strong></pre>
9325: </li>
1.23 wiz 9326: <li class="listitem"><p>Play with it. Make sure everything works.</p></li>
9327: <li class="listitem">
1.79 snj 9328: <p>Run <span class="command"><strong>pkglint</strong></span> from <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>, and fix the problems it
1.1 dsieger 9329: reports:</p>
9330: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>pkglint</code></strong></pre>
9331: </li>
1.23 wiz 9332: <li class="listitem"><p>Submit (or commit, if you have cvs access); see <a class="xref" href="#submit" title="Chapter 21. Submitting and Committing">Chapter 21, <i>Submitting and Committing</i></a>.</p></li>
1.1 dsieger 9333: </ul></div>
9334: </div>
1.41 asau 9335: <div class="chapter">
1.1 dsieger 9336: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 9337: <a name="submit"></a>Chapter 21. Submitting and Committing</h2></div></div></div>
1.1 dsieger 9338: <div class="toc">
9339: <p><b>Table of Contents</b></p>
1.100 leot 9340: <dl class="toc">
1.6 rillig 9341: <dt><span class="sect1"><a href="#submitting-binary-packages">21.1. Submitting binary packages</a></span></dt>
9342: <dt><span class="sect1"><a href="#submitting-your-package">21.2. Submitting source packages (for non-NetBSD-developers)</a></span></dt>
9343: <dt><span class="sect1"><a href="#general-notes-for-changes">21.3. General notes when adding, updating, or removing packages</a></span></dt>
1.33 wiz 9344: <dt><span class="sect1"><a href="#committing-importing">21.4. Committing: Adding a package to CVS</a></span></dt>
1.6 rillig 9345: <dt><span class="sect1"><a href="#updating-package">21.5. Updating a package to a newer version</a></span></dt>
1.20 snj 9346: <dt><span class="sect1"><a href="#renaming-package">21.6. Renaming a package in pkgsrc</a></span></dt>
9347: <dt><span class="sect1"><a href="#moving-package">21.7. Moving a package in pkgsrc</a></span></dt>
1.1 dsieger 9348: </dl>
9349: </div>
1.41 asau 9350: <div class="sect1">
1.1 dsieger 9351: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9352: <a name="submitting-binary-packages"></a>21.1. Submitting binary packages</h2></div></div></div>
1.1 dsieger 9353: <p>Our policy is that we accept binaries only from pkgsrc
9354: developers to guarantee that the packages don't contain any
9355: trojan horses etc. This is not to annoy anyone but rather to
9356: protect our users! You're still free to put up your home-made
9357: binary packages and tell the world where to get them. NetBSD
9358: developers doing bulk builds and wanting to upload them please
1.66 asau 9359: see <a class="xref" href="#bulk" title="Chapter 7. Creating binary packages for everything in pkgsrc (bulk builds)">Chapter 7, <i>Creating binary packages for everything in pkgsrc (bulk
9360: builds)</i></a>.</p>
1.1 dsieger 9361: </div>
1.41 asau 9362: <div class="sect1">
1.1 dsieger 9363: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9364: <a name="submitting-your-package"></a>21.2. Submitting source packages (for non-NetBSD-developers)</h2></div></div></div>
1.1 dsieger 9365: <p>First, check that your package is complete, compiles and
1.10 hubertf 9366: runs well; see <a class="xref" href="#debug" title="Chapter 20. Debugging">Chapter 20, <i>Debugging</i></a> and the rest of this
1.79 snj 9367: document. Next, generate an uuencoded gzipped <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span></a>
1.1 dsieger 9368: archive that contains all files that make up the package.
9369: Finally, send this package to the pkgsrc bug tracking system,
1.79 snj 9370: either with the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> command, or if you don't have
1.1 dsieger 9371: that, go to the web page
1.10 hubertf 9372: <a class="ulink" href="http://www.NetBSD.org/support/send-pr.html" target="_top">http://www.NetBSD.org/support/send-pr.html</a>,
1.21 snj 9373: which contains some instructions and a link to a form where you
9374: can submit packages. The
1.79 snj 9375: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/gtk-send-pr/README.html" target="_top"><code class="filename">sysutils/gtk-send-pr</code></a> package is
1.21 snj 9376: also available as a substitute for either of the above two tools.
9377: </p>
1.1 dsieger 9378: <p>In the form of the problem report, the category should be
1.23 wiz 9379: <span class="quote">“<span class="quote">pkg</span>”</span>, the synopsis should include the package name
1.1 dsieger 9380: and version number, and the description field should contain a
9381: short description of your package (contents of the COMMENT
9382: variable or DESCR file are OK). The uuencoded package data should
1.23 wiz 9383: go into the <span class="quote">“<span class="quote">fix</span>”</span> field.</p>
1.1 dsieger 9384: <p>If you want to submit several packages, please send a
9385: separate PR for each one, it's easier for us to track things
9386: that way.</p>
9387: <p>Alternatively, you can also import new packages into
1.23 wiz 9388: pkgsrc-wip (<span class="quote">“<span class="quote">pkgsrc work-in-progress</span>”</span>); see the
1.10 hubertf 9389: homepage at <a class="ulink" href="http://pkgsrc-wip.sourceforge.net/" target="_top">http://pkgsrc-wip.sourceforge.net/</a>
1.1 dsieger 9390: for details.</p>
9391: </div>
1.41 asau 9392: <div class="sect1">
1.1 dsieger 9393: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9394: <a name="general-notes-for-changes"></a>21.3. General notes when adding, updating, or removing packages</h2></div></div></div>
1.1 dsieger 9395: <p>Please note all package additions, updates, moves, and
9396: removals in <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code>. It's very
9397: important to keep this file up to date and conforming to the
9398: existing format, because it will be used by scripts to
1.10 hubertf 9399: automatically update pages on <a class="ulink" href="http://www.NetBSD.org/" target="_top">www.NetBSD.org</a> and other
1.1 dsieger 9400: sites. Additionally, check the
9401: <code class="filename">pkgsrc/doc/TODO</code> file and remove the entry
9402: for the package you updated or removed, in case it was mentioned
9403: there.</p>
9404: <p>When the <code class="varname">PKGREVISION</code> of a package is
9405: bumped, the change should appear in
9406: <code class="filename">pkgsrc/doc/CHANGES-<em class="replaceable"><code>YYYY</code></em></code> if it is security
9407: related or otherwise relevant. Mass bumps that result from a
9408: dependency being updated should not be mentioned. In all other
9409: cases it's the developer's decision.</p>
9410: <p>There is a make target that helps in creating proper
1.10 hubertf 9411: <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code> entries: <span class="command"><strong>make
1.1 dsieger 9412: changes-entry</strong></span>. It uses the optional <code class="varname">CTYPE</code>
9413: and <code class="varname">NETBSD_LOGIN_NAME</code> variables. The general
9414: usage is to first make sure that your <code class="filename">CHANGES-<em class="replaceable"><code>YYYY</code></em></code>
9415: file is up-to-date (to avoid having to resolve conflicts later-on)
1.10 hubertf 9416: and then to <span class="command"><strong>cd</strong></span> to the package directory. For
9417: package updates, <span class="command"><strong>make changes-entry</strong></span> is enough.
1.1 dsieger 9418: For new packages, or package moves or removals, set the
9419: <code class="varname">CTYPE</code> variable on the command line to "Added",
9420: "Moved", or "Removed". You can set <code class="varname">NETBSD_LOGIN_NAME</code>
1.10 hubertf 9421: in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> if your local login name is
1.22 jakllsch 9422: not the same as your NetBSD login name. The target also automatically
9423: removes possibly existing entries for the package in the
9424: <code class="filename">TODO</code> file. Don't forget to commit
1.66 asau 9425: the changes, e.g. by using <span class="command"><strong>make commit-changes-entry</strong></span>!
1.22 jakllsch 9426: If you are not using a checkout directly from cvs.NetBSD.org, but e.g.
9427: a local copy of the repository, you can set USE_NETBSD_REPO=yes. This
9428: makes the cvs commands use the main repository.
9429: </p>
1.1 dsieger 9430: </div>
1.41 asau 9431: <div class="sect1">
1.1 dsieger 9432: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.33 wiz 9433: <a name="committing-importing"></a>21.4. Committing: Adding a package to CVS</h2></div></div></div>
1.1 dsieger 9434: <p>This section is only of interest for pkgsrc developers with write
1.33 wiz 9435: access to the pkgsrc repository.</p>
9436: <p>When the package is finished, <span class="quote">“<span class="quote">cvs add</span>”</span> the files.
9437: Start by adding the directory and then files in the directory. Don't
9438: forget to add the new package to the category's
9439: <code class="filename">Makefile</code>. Make sure you don't forget any files;
9440: you can check by running <span class="quote">“<span class="quote">cvs status</span>”</span>. An example:</p>
9441: <pre class="programlisting">
9442: <code class="prompt">$</code> cd .../pkgsrc/category
9443: <code class="prompt">$</code> cvs add pkgname
9444: <code class="prompt">$</code> cd pkgname
9445: <code class="prompt">$</code> cvs add DESCR Makefile PLIST distinfo buildlink3.mk patches
9446: <code class="prompt">$</code> cvs add patches/p*
9447: <code class="prompt">$</code> cvs status | less
1.34 wiz 9448: <code class="prompt">$</code> cvs commit
1.33 wiz 9449: <code class="prompt">$</code> cd ..
9450: <code class="prompt">$</code> vi Makefile # add SUBDIRS+=pkgname line
1.34 wiz 9451: <code class="prompt">$</code> cvs commit Makefile
1.66 asau 9452: <code class="prompt">$</code> cd pkgname
1.73 jnemeth 9453: <code class="prompt">$</code> make CTYPE=Added commit-changes-entry
1.33 wiz 9454: </pre>
1.1 dsieger 9455: <p>The commit message of the initial import should include part of the
9456: <code class="filename">DESCR</code> file, so people reading the mailing lists know
9457: what the package is/does.</p>
1.33 wiz 9458: <p>Also mention the new package in
9459: <code class="filename">pkgsrc/doc/CHANGES-20xx</code>.</p>
9460: <p>Previously, <span class="quote">“<span class="quote">cvs import</span>”</span> was suggested, but it was
9461: much easier to get wrong than <span class="quote">“<span class="quote">cvs add</span>”</span>.</p>
1.1 dsieger 9462: </div>
1.41 asau 9463: <div class="sect1">
1.1 dsieger 9464: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9465: <a name="updating-package"></a>21.5. Updating a package to a newer version</h2></div></div></div>
1.1 dsieger 9466: <p>Please always put a concise, appropriate and relevant summary of the
9467: changes between old and new versions into the commit log when updating
9468: a package. There are various reasons for this:</p>
1.41 asau 9469: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9470: <li class="listitem"><p>A URL is volatile, and can change over time. It may go away completely
1.1 dsieger 9471: or its information may be overwritten by newer information.</p></li>
1.23 wiz 9472: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 9473: repository is very useful for people who use either cvs or anoncvs.</p></li>
1.23 wiz 9474: <li class="listitem"><p>Having the change information between old and new versions in our CVS
1.1 dsieger 9475: repository is very useful for people who read the pkgsrc-changes mailing
9476: list, so that they can make tactical decisions about when to upgrade
9477: the package.</p></li>
9478: </ul></div>
9479: <p>Please also recognize that, just because a new version of a package
9480: has been released, it should not automatically be upgraded in the CVS
9481: repository. We prefer to be conservative in the packages that are
9482: included in pkgsrc - development or beta packages are not really the
9483: best thing for most places in which pkgsrc is used. Please use your
9484: judgement about what should go into pkgsrc, and bear in mind that
9485: stability is to be preferred above new and possibly untested features.</p>
9486: </div>
1.41 asau 9487: <div class="sect1">
1.1 dsieger 9488: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.20 snj 9489: <a name="renaming-package"></a>21.6. Renaming a package in pkgsrc</h2></div></div></div>
9490: <p>Renaming packages is not recommended.</p>
9491: <p>When renaming packages, be sure to fix any references to old name
9492: in other Makefiles, options, buildlink files, etc.</p>
9493: <p>Also When renaming a package, please define
9494: <code class="varname">SUPERSEDES</code> to the package name and dewey version
9495: pattern(s) of the previous package name.
9496: This may be repeated for multiple renames.
9497: The new package would be an exact replacement.
9498: </p>
1.23 wiz 9499: <p>Note that <span class="quote">“<span class="quote">successor</span>”</span> in the
1.20 snj 9500: CHANGES-<em class="replaceable"><code>YYYY</code></em> file doesn't necessarily
9501: mean that it <span class="emphasis"><em>supersedes</em></span>, as that successor may
9502: not be an exact replacement but is a suggestion for the replaced
9503: functionality.</p>
9504: </div>
1.41 asau 9505: <div class="sect1">
1.20 snj 9506: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
9507: <a name="moving-package"></a>21.7. Moving a package in pkgsrc</h2></div></div></div>
9508: <p>It is preferred that packages are not renamed or moved, but if needed
9509: please follow these steps.
9510: </p>
1.23 wiz 9511: <div class="orderedlist"><ol class="orderedlist" type="1">
9512: <li class="listitem"><p>Make a copy of the directory somewhere else.</p></li>
9513: <li class="listitem">
1.1 dsieger 9514: <p>Remove all CVS dirs.</p>
9515: <p>Alternatively to the first two steps you can also do:</p>
9516: <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>
9517: <p>and use that for further work.</p>
9518: </li>
1.23 wiz 9519: <li class="listitem"><p>Fix <code class="varname">CATEGORIES</code> and any
9520: <code class="varname">DEPENDS</code> paths that just did <span class="quote">“<span class="quote">../package</span>”</span>
9521: instead of <span class="quote">“<span class="quote">../../category/package</span>”</span>.</p></li>
9522: <li class="listitem"><p>In the modified package's Makefile, consider setting
1.20 snj 9523: <code class="varname">PREV_PKGPATH</code> to the previous category/package
9524: pathname. The <code class="varname">PREV_PKGPATH</code> can be used by tools
9525: for doing an update using pkgsrc building; for example, it can
1.79 snj 9526: search the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_summary+5+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a> database for <code class="varname">PREV_PKGPATH</code>
1.20 snj 9527: (if no <code class="varname">SUPERSEDES</code>) and then use the corresponding
9528: new <code class="varname">PKGPATH</code> for that moved package. Note that
9529: it may have multiple matches, so the tool should also check on the
9530: <code class="varname">PKGBASE</code> too. The <code class="varname">PREV_PKGPATH</code>
9531: probably has no value unless <code class="varname">SUPERSEDES</code> is not
9532: set, i.e. <code class="varname">PKGBASE</code> stays the same. </p></li>
1.23 wiz 9533: <li class="listitem"><p><span class="command"><strong>cvs import</strong></span> the modified package in the new
1.1 dsieger 9534: place.</p></li>
1.23 wiz 9535: <li class="listitem">
1.1 dsieger 9536: <p>Check if any package depends on it:
9537: </p>
9538: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cd /usr/pkgsrc</code></strong>
9539: <code class="prompt">%</code> <strong class="userinput"><code>grep /package */*/Makefile* */*/buildlink*</code></strong></pre>
9540: </li>
1.23 wiz 9541: <li class="listitem"><p>Fix paths in packages from step 5 to point to new location.</p></li>
9542: <li class="listitem"><p><span class="command"><strong>cvs rm (-f)</strong></span> the package at the old location.</p></li>
9543: <li class="listitem"><p>Remove from <code class="filename">oldcategory/Makefile</code>.</p></li>
9544: <li class="listitem"><p>Add to <code class="filename">newcategory/Makefile</code>.</p></li>
9545: <li class="listitem">
1.1 dsieger 9546: <p>Commit the changed and removed files:</p>
9547: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile</code></strong></pre>
9548: <p>(and any packages from step 5, of course).</p>
9549: </li>
9550: </ol></div>
9551: </div>
9552: </div>
1.41 asau 9553: <div class="chapter">
1.1 dsieger 9554: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 9555: <a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div>
1.1 dsieger 9556: <p>This section contains the answers to questions that may
9557: arise when you are writing a package. If you don't find your
9558: question answered here, first have a look in the other chapters,
9559: and if you still don't have the answer, ask on the
9560: <code class="literal">pkgsrc-users</code> mailing list.</p>
1.41 asau 9561: <div class="qandaset">
1.101 ! sevan 9562: <a name="idp2125340516"></a><dl>
1.6 rillig 9563: <dt>22.1. <a href="#devfaq.makeflags">What is the difference between
1.1 dsieger 9564: MAKEFLAGS, .MAKEFLAGS and
9565: MAKE_FLAGS?</a>
9566: </dt>
1.6 rillig 9567: <dt>22.2. <a href="#devfaq.make">What is the difference between
1.1 dsieger 9568: MAKE, GMAKE and
9569: MAKE_PROGRAM?</a>
9570: </dt>
1.6 rillig 9571: <dt>22.3. <a href="#devfaq.cc">What is the difference between
1.1 dsieger 9572: CC, PKG_CC and
9573: PKGSRC_COMPILER?</a>
9574: </dt>
1.6 rillig 9575: <dt>22.4. <a href="#devfaq.bl3flags">What is the difference between
1.1 dsieger 9576: BUILDLINK_LDFLAGS,
9577: BUILDLINK_LDADD and
9578: BUILDLINK_LIBS?</a>
9579: </dt>
1.6 rillig 9580: <dt>22.5. <a href="#devfaq.bl3prefix">Why does make show-var
1.1 dsieger 9581: VARNAME=BUILDLINK_PREFIX.foo
9582: say it's empty?</a>
9583: </dt>
1.6 rillig 9584: <dt>22.6. <a href="#devfaq.master_sites">What does
1.1 dsieger 9585: ${MASTER_SITE_SOURCEFORGE:=package/} mean? I
9586: don't understand the := inside
9587: it.</a>
9588: </dt>
1.6 rillig 9589: <dt>22.7. <a href="#devfaq.mailinglists">Which mailing lists are there for package
1.1 dsieger 9590: developers?</a>
9591: </dt>
1.6 rillig 9592: <dt>22.8. <a href="#devfaq.documentation">Where is the pkgsrc
1.1 dsieger 9593: documentation?</a>
9594: </dt>
1.6 rillig 9595: <dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill. What shall I
1.1 dsieger 9596: do?</a>
9597: </dt>
9598: </dl>
1.41 asau 9599: <table border="0" style="width: 100%;">
9600: <colgroup>
1.1 dsieger 9601: <col align="left" width="1%">
1.23 wiz 9602: <col>
1.41 asau 9603: </colgroup>
1.1 dsieger 9604: <tbody>
1.41 asau 9605: <tr class="question">
1.1 dsieger 9606: <td align="left" valign="top">
1.101 ! sevan 9607: <a name="devfaq.makeflags"></a><a name="idp2125339444"></a><p><b>22.1.</b></p>
1.1 dsieger 9608: </td>
9609: <td align="left" valign="top"><p>What is the difference between
9610: <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
9611: <code class="varname">MAKE_FLAGS</code>?</p></td>
9612: </tr>
9613: <tr class="answer">
9614: <td align="left" valign="top"></td>
9615: <td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed
1.79 snj 9616: to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while
1.1 dsieger 9617: <code class="varname">MAKE_FLAGS</code> are the flags that are passed to
9618: the <code class="varname">MAKE_PROGRAM</code> when building the
9619: package. [FIXME: What is .MAKEFLAGS for?]</p></td>
9620: </tr>
1.41 asau 9621: <tr class="question">
1.1 dsieger 9622: <td align="left" valign="top">
1.101 ! sevan 9623: <a name="devfaq.make"></a><a name="idp2125343316"></a><p><b>22.2.</b></p>
1.1 dsieger 9624: </td>
9625: <td align="left" valign="top"><p>What is the difference between
9626: <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
9627: <code class="varname">MAKE_PROGRAM</code>?</p></td>
9628: </tr>
9629: <tr class="answer">
9630: <td align="left" valign="top"></td>
9631: <td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the
1.79 snj 9632: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
1.1 dsieger 9633: infrastructure. <code class="varname">GMAKE</code> is the path to GNU
9634: Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to
9635: use that. <code class="varname">MAKE_PROGRAM</code> is the path to the
9636: Make program that is used for building the
9637: package.</p></td>
9638: </tr>
1.41 asau 9639: <tr class="question">
1.1 dsieger 9640: <td align="left" valign="top">
1.101 ! sevan 9641: <a name="devfaq.cc"></a><a name="idp2125346084"></a><p><b>22.3.</b></p>
1.1 dsieger 9642: </td>
9643: <td align="left" valign="top"><p>What is the difference between
9644: <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
9645: <code class="varname">PKGSRC_COMPILER</code>?</p></td>
9646: </tr>
9647: <tr class="answer">
9648: <td align="left" valign="top"></td>
9649: <td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C
9650: compiler, which can be configured by the pkgsrc user.
9651: <code class="varname">PKG_CC</code> is the path to the compiler wrapper.
9652: <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a
9653: path to a compiler, but the type of compiler that should be
9654: used. See <code class="filename">mk/compiler.mk</code> for more
9655: information about the latter variable.</p></td>
9656: </tr>
1.41 asau 9657: <tr class="question">
1.1 dsieger 9658: <td align="left" valign="top">
1.101 ! sevan 9659: <a name="devfaq.bl3flags"></a><a name="idp2125348756"></a><p><b>22.4.</b></p>
1.1 dsieger 9660: </td>
9661: <td align="left" valign="top"><p>What is the difference between
9662: <code class="varname">BUILDLINK_LDFLAGS</code>,
9663: <code class="varname">BUILDLINK_LDADD</code> and
9664: <code class="varname">BUILDLINK_LIBS</code>?</p></td>
9665: </tr>
9666: <tr class="answer">
9667: <td align="left" valign="top"></td>
9668: <td align="left" valign="top"><p>[FIXME]</p></td>
9669: </tr>
1.41 asau 9670: <tr class="question">
1.1 dsieger 9671: <td align="left" valign="top">
1.101 ! sevan 9672: <a name="devfaq.bl3prefix"></a><a name="idp2125350180"></a><p><b>22.5.</b></p>
1.1 dsieger 9673: </td>
1.10 hubertf 9674: <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
1.1 dsieger 9675: VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
9676: say it's empty?</p></td>
9677: </tr>
9678: <tr class="answer">
9679: <td align="left" valign="top"></td>
9680: <td align="left" valign="top"><p>For optimization reasons, some variables are only
1.23 wiz 9681: available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To
9682: <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append
1.10 hubertf 9683: <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
1.1 dsieger 9684: command.</p></td>
9685: </tr>
1.41 asau 9686: <tr class="question">
1.1 dsieger 9687: <td align="left" valign="top">
1.101 ! sevan 9688: <a name="devfaq.master_sites"></a><a name="idp2125352388"></a><p><b>22.6.</b></p>
1.1 dsieger 9689: </td>
9690: <td align="left" valign="top"><p>What does
9691: <code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
9692: don't understand the <code class="literal">:=</code> inside
9693: it.</p></td>
9694: </tr>
9695: <tr class="answer">
9696: <td align="left" valign="top"></td>
9697: <td align="left" valign="top"><p>The <code class="literal">:=</code> is not really an
9698: assignment operator, like you might expect at first sight.
9699: Instead, it is a degenerate form of
9700: <code class="literal">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
1.79 snj 9701: which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which you
1.1 dsieger 9702: may have seen as in <code class="literal">${SRCS:.c=.o}</code>. In the
9703: case of <code class="varname">MASTER_SITE_*</code>,
9704: <em class="replaceable"><code>old_string</code></em> is the empty string and
9705: <em class="replaceable"><code>new_string</code></em> is
9706: <code class="literal">package/</code>. That's where the
9707: <code class="literal">:</code> and the <code class="literal">=</code> fall
9708: together.</p></td>
9709: </tr>
1.41 asau 9710: <tr class="question">
1.1 dsieger 9711: <td align="left" valign="top">
1.101 ! sevan 9712: <a name="devfaq.mailinglists"></a><a name="idp2125357620"></a><p><b>22.7.</b></p>
1.1 dsieger 9713: </td>
9714: <td align="left" valign="top"><p>Which mailing lists are there for package
9715: developers?</p></td>
9716: </tr>
9717: <tr class="answer">
9718: <td align="left" valign="top"></td>
1.41 asau 9719: <td align="left" valign="top"><div class="variablelist"><dl class="variablelist">
1.10 hubertf 9720: <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt>
1.1 dsieger 9721: <dd><p>This is a list for technical discussions related
9722: to pkgsrc development, e.g. soliciting feedback for changes to
9723: pkgsrc infrastructure, proposed new features, questions related
9724: to porting pkgsrc to a new platform, advice for maintaining a
9725: package, patches that affect many packages, help requests moved
9726: from pkgsrc-users when an infrastructure bug is found,
9727: etc.</p></dd>
1.10 hubertf 9728: <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt>
1.1 dsieger 9729: <dd><p>All bug reports in category "pkg" sent with
1.79 snj 9730: <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here
1.1 dsieger 9731: directly; use one of the other mailing
9732: lists.</p></dd>
9733: </dl></div></td>
9734: </tr>
1.41 asau 9735: <tr class="question">
1.1 dsieger 9736: <td align="left" valign="top">
1.101 ! sevan 9737: <a name="devfaq.documentation"></a><a name="idp2125360516"></a><p><b>22.8.</b></p>
1.1 dsieger 9738: </td>
9739: <td align="left" valign="top"><p>Where is the pkgsrc
9740: documentation?</p></td>
9741: </tr>
9742: <tr class="answer">
9743: <td align="left" valign="top"></td>
9744: <td align="left" valign="top">
9745: <p>There are many places where you can find
9746: documentation about pkgsrc:</p>
1.41 asau 9747: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9748: <li class="listitem"><p>The pkgsrc guide (this document) is a collection
1.1 dsieger 9749: of chapters that explain large parts of pkgsrc, but some
9750: chapters tend to be outdated. Which ones they are is hard to
9751: say.</p></li>
1.23 wiz 9752: <li class="listitem"><p>On the mailing list archives (see <a class="ulink" href="http://mail-index.NetBSD.org/" target="_top">http://mail-index.NetBSD.org/</a>), you can find discussions
1.1 dsieger 9753: about certain features, announcements of new parts of the pkgsrc
9754: infrastructure and sometimes even announcements that a certain
9755: feature has been marked as obsolete. The benefit here is that
9756: each message has a date appended to it.</p></li>
1.23 wiz 9757: <li class="listitem"><p>Many of the files in the
1.1 dsieger 9758: <code class="filename">mk/</code> directory start with a comment that
9759: describes the purpose of the file and how it can be used by the
9760: pkgsrc user and package authors. An easy way to find this
1.10 hubertf 9761: documentation is to run <span class="command"><strong>bmake
1.1 dsieger 9762: help</strong></span>.</p></li>
1.23 wiz 9763: <li class="listitem"><p>The CVS log messages are a rich source of
1.1 dsieger 9764: information, but they tend to be highly abbreviated, especially
9765: for actions that occur often. Some contain a detailed
9766: description of what has changed, but they are geared towards the
9767: other pkgsrc developers, not towards an average pkgsrc user.
9768: They also only document <span class="emphasis"><em>changes</em></span>, so if you
9769: don't know what has been before, these messages may not be worth
9770: too much to you.</p></li>
1.23 wiz 9771: <li class="listitem"><p>Some parts of pkgsrc are only <span class="quote">“<span class="quote">implicitly
9772: documented</span>”</span>, that is the documentation exists only in the
1.1 dsieger 9773: mind of the developer who wrote the code. To get this
1.10 hubertf 9774: information, use the <span class="command"><strong>cvs annotate</strong></span> command
1.1 dsieger 9775: to see who has written it and ask on the
9776: <code class="literal">tech-pkg</code> mailing list, so that others can
9777: find your questions later (see above). To be sure that the
9778: developer in charge reads the mail, you may CC him or
9779: her.</p></li>
9780: </ul></div>
9781: </td>
9782: </tr>
1.41 asau 9783: <tr class="question">
1.1 dsieger 9784: <td align="left" valign="top">
1.101 ! sevan 9785: <a name="devfaq.too-much-time"></a><a name="idp2125365940"></a><p><b>22.9.</b></p>
1.1 dsieger 9786: </td>
9787: <td align="left" valign="top"><p>I have a little time to kill. What shall I
9788: do?</p></td>
9789: </tr>
9790: <tr class="answer">
9791: <td align="left" valign="top"></td>
9792: <td align="left" valign="top">
9793: <p>This is not really an FAQ yet, but here's the answer
9794: anyway.</p>
1.41 asau 9795: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9796: <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
1.79 snj 9797: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It
1.1 dsieger 9798: will tell you about newer versions of installed packages that are
9799: available, but not yet updated in pkgsrc.</p></li>
1.23 wiz 9800: <li class="listitem"><p>Browse <code class="filename">pkgsrc/doc/TODO</code>
1.14 jmcneill 9801: — it contains a list of suggested new packages and a list of
1.1 dsieger 9802: cleanups and enhancements for pkgsrc that would be nice to
9803: have.</p></li>
1.23 wiz 9804: <li class="listitem"><p>Review packages for which review was requested on
1.71 wiz 9805: the <a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a>
1.1 dsieger 9806: mailing list.</p></li>
9807: </ul></div>
9808: </td>
9809: </tr>
9810: </tbody>
9811: </table>
9812: </div>
9813: </div>
1.41 asau 9814: <div class="chapter">
1.1 dsieger 9815: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 9816: <a name="gnome"></a>Chapter 23. GNOME packaging and porting</h2></div></div></div>
1.1 dsieger 9817: <div class="toc">
9818: <p><b>Table of Contents</b></p>
1.100 leot 9819: <dl class="toc">
1.6 rillig 9820: <dt><span class="sect1"><a href="#meta-packages">23.1. Meta packages</a></span></dt>
9821: <dt><span class="sect1"><a href="#new-package">23.2. Packaging a GNOME application</a></span></dt>
9822: <dt><span class="sect1"><a href="#full-update">23.3. Updating GNOME to a newer version</a></span></dt>
9823: <dt><span class="sect1"><a href="#patching">23.4. Patching guidelines</a></span></dt>
1.1 dsieger 9824: </dl>
9825: </div>
1.10 hubertf 9826: <p>Quoting <a class="ulink" href="http://www.gnome.org/" target="_top">GNOME's web
1.1 dsieger 9827: site</a>:</p>
9828: <div class="blockquote"><blockquote class="blockquote"><p>The GNOME project provides two things: The GNOME desktop
9829: environment, an intuitive and attractive desktop for users, and the
9830: GNOME development platform, an extensive framework for building
9831: applications that integrate into the rest of the desktop.</p></blockquote></div>
9832: <p>pkgsrc provides a seamless way to automatically build and install
9833: a complete GNOME environment <span class="emphasis"><em>under many different
9834: platforms</em></span>. We can say with confidence that pkgsrc is one of
9835: the most advanced build and packaging systems for GNOME due to its
9836: included technologies buildlink3, the wrappers and tools framework and
9837: automatic configuration file management. Lots of efforts are put into
9838: achieving a completely clean deinstallation of installed software
9839: components.</p>
1.10 hubertf 9840: <p>Given that pkgsrc is <a class="ulink" href="http://www.NetBSD.org/" target="_top">NetBSD</a>'s official packaging system,
1.1 dsieger 9841: the above also means that great efforts are put into making GNOME work
1.10 hubertf 9842: under this operating system. Recently, <a class="ulink" href="http://www.dragonflybsd.org/" target="_top">DragonFly BSD</a> also adopted
1.1 dsieger 9843: pkgsrc as its preferred packaging system, contributing lots of
9844: portability fixes to make GNOME build and install under it.</p>
9845: <p>This chapter is aimed at pkgsrc developers and other people
9846: interested in helping our GNOME porting and packaging efforts. It
9847: provides instructions on how to manage the existing packages and some
9848: important information regarding their internals.</p>
1.41 asau 9849: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 9850: <h3 class="title">We need your help!</h3>
9851: <p>Should you have some spare cycles to devote to NetBSD, pkgsrc
9852: and GNOME and are willing to learn new exciting stuff, please jump
1.10 hubertf 9853: straight to the <a class="ulink" href="http://www.NetBSD.org/contrib/projects.html#gnome" target="_top">pending
1.1 dsieger 9854: work</a> list! There is still a long way to go to get a
9855: fully-functional GNOME desktop under NetBSD and we need your help to
9856: achieve it!</p>
9857: </div>
1.41 asau 9858: <div class="sect1">
1.1 dsieger 9859: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9860: <a name="meta-packages"></a>23.1. Meta packages</h2></div></div></div>
1.1 dsieger 9861: <p>pkgsrc includes three GNOME-related meta packages:</p>
1.41 asau 9862: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.79 snj 9863: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html" target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>: Provides
1.1 dsieger 9864: the core GNOME desktop environment. It only includes the necessary
9865: bits to get it to boot correctly, although it may lack important
9866: functionality for daily operation. The idea behind this package is
9867: to let end users build their own configurations on top of this one,
9868: first installing this meta package to achieve a functional setup and
9869: then adding individual applications.</p></li>
1.79 snj 9870: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html" target="_top"><code class="filename">meta-pkgs/gnome</code></a>: Provides a
1.1 dsieger 9871: complete installation of the GNOME platform and desktop as defined
9872: by the GNOME project; this is based on the components distributed in
9873: the <code class="filename">platform/x.y/x.y.z/sources</code> and
9874: <code class="filename">desktop/x.y/x.y.z/sources</code> directories of the
9875: official FTP server. Developer-only tools found in those
9876: directories are not installed unless required by some other
9877: component to work properly. Similarly, packages from the bindings
9878: set (<code class="filename">bindings/x.y/x.y.z/sources</code>) are not pulled
9879: in unless required as a dependency for an end-user component. This
1.79 snj 9880: package "extends" <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html" target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>.</p></li>
9881: <li class="listitem"><p><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html" target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a>:
1.1 dsieger 9882: Installs all the tools required to build a GNOME component when
9883: fetched from the CVS repository. These are required to let the
1.10 hubertf 9884: <span class="command"><strong>autogen.sh</strong></span> scripts work appropriately.</p></li>
1.1 dsieger 9885: </ul></div>
9886: <p>In all these packages, the <code class="varname">DEPENDS</code> lines are
9887: sorted in a way that eases updates: a package may depend on other
9888: packages listed before it but not on any listed after it. It is very
9889: important to keep this order to ease updates so... <span class="emphasis"><em>do not
9890: change it to alphabetical sorting!</em></span></p>
9891: </div>
1.41 asau 9892: <div class="sect1">
1.1 dsieger 9893: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9894: <a name="new-package"></a>23.2. Packaging a GNOME application</h2></div></div></div>
1.1 dsieger 9895: <p>Almost all GNOME applications are written in C and use a common
9896: set of tools as their build system. Things get different with the new
9897: bindings to other languages (such as Python), but the following will
9898: give you a general idea on the minimum required tools:</p>
1.41 asau 9899: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 9900: <li class="listitem">
1.1 dsieger 9901: <p>Almost all GNOME applications use the GNU Autotools as their
9902: build system. As a general rule you will need to tell this to your
9903: package:</p>
9904: <pre class="programlisting">
9905: GNU_CONFIGURE=yes
9906: USE_LIBTOOL=yes
9907: USE_TOOLS+=gmake
9908: </pre>
9909: </li>
1.23 wiz 9910: <li class="listitem">
1.1 dsieger 9911: <p>If the package uses pkg-config to detect dependencies, add this
9912: tool to the list of required utilities:</p>
9913: <pre class="programlisting">USE_TOOLS+=pkg-config</pre>
1.79 snj 9914: <p>Also use <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/verifypc/README.html" target="_top"><code class="filename">pkgtools/verifypc</code></a> at
1.1 dsieger 9915: the end of the build process to ensure that you did not miss to
9916: specify any dependency in your package and that the version
9917: requirements are all correct.</p>
9918: </li>
1.23 wiz 9919: <li class="listitem"><p>If the package uses intltool, be sure to add
1.1 dsieger 9920: <code class="literal">intltool</code> to the <code class="varname">USE_TOOLS</code>
9921: to handle dependencies and to force the package to use the latest
9922: available version.</p></li>
1.23 wiz 9923: <li class="listitem">
1.1 dsieger 9924: <p>If the package uses gtk-doc (a documentation generation
9925: utility), do <span class="emphasis"><em>not</em></span> add a dependency on it. The
9926: tool is rather big and the distfile should come with pregenerated
9927: documentation anyway; if it does not, it is a bug that you ought to
9928: report. For such packages you should disable gtk-doc (unless it is
9929: the default):</p>
9930: <pre class="programlisting">CONFIGURE_ARGS+=--disable-gtk-doc</pre>
9931: <p>The default location of installed HTML files
9932: (<code class="filename">share/gtk-doc/<package-name></code>) is correct
9933: and should not be changed unless the package insists on installing
9934: them somewhere else. Otherwise programs as
1.10 hubertf 9935: <span class="command"><strong>devhelp</strong></span> will not be able to open them. You can
1.1 dsieger 9936: do that with an entry similar to:</p>
9937: <pre class="programlisting">CONFIGURE_ARGS+=--with-html-dir=${PREFIX}/share/gtk-doc/...</pre>
9938: </li>
9939: </ul></div>
9940: <p>GNOME uses multiple <span class="emphasis"><em>shared</em></span> directories and
9941: files under the installation prefix to maintain databases. In this
9942: context, shared means that those exact same directories and files are
9943: used among several different packages, leading to conflicts in the
9944: <code class="filename">PLIST</code>. pkgsrc currently includes functionality to
9945: handle the most common cases, so you have to forget about using
9946: <code class="literal">@unexec ${RMDIR}</code> lines in your file lists and
9947: omitting shared files from them. If you find yourself doing those,
9948: <span class="emphasis"><em>your package is most likely incorrect</em></span>.</p>
9949: <p>The following table lists the common situations that result in
9950: using shared directories or files. For each of them, the appropriate
9951: solution is given. After applying the solution be sure to
9952: <span class="emphasis"><em>regenerate the package's file list</em></span> with
1.10 hubertf 9953: <span class="command"><strong>make print-PLIST</strong></span> and ensure it is correct.</p>
1.1 dsieger 9954: <div class="table">
1.6 rillig 9955: <a name="plist-handling"></a><p class="title"><b>Table 23.1. PLIST handling for GNOME packages</b></p>
1.1 dsieger 9956: <div class="table-contents"><table summary="PLIST handling for GNOME packages" border="1">
9957: <colgroup>
9958: <col>
9959: <col>
9960: </colgroup>
9961: <thead><tr>
9962: <th>If the package...</th>
9963: <th>Then...</th>
9964: </tr></thead>
9965: <tbody>
9966: <tr>
9967: <td>Installs OMF files under <code class="filename">share/omf</code>.</td>
1.18 snj 9968: <td>See <a class="xref" href="#scrollkeeper-data-files" title="19.6.10. Packages installing scrollkeeper/rarian data files">Section 19.6.10, “Packages installing scrollkeeper/rarian data files”</a>.</td>
1.1 dsieger 9969: </tr>
9970: <tr>
9971: <td>Installs icons under the
9972: <code class="filename">share/icons/hicolor</code> hierarchy or updates
9973: <code class="filename">share/icons/hicolor/icon-theme.cache</code>.</td>
1.10 hubertf 9974: <td>See <a class="xref" href="#hicolor-theme" title="19.6.19. Packages installing hicolor theme icons">Section 19.6.19, “Packages installing hicolor theme icons”</a>.</td>
1.1 dsieger 9975: </tr>
9976: <tr>
9977: <td>Installs files under
9978: <code class="filename">share/mime/packages</code>.</td>
1.10 hubertf 9979: <td>See <a class="xref" href="#mime-database" title="19.6.14. Packages installing extensions to the MIME database">Section 19.6.14, “Packages installing extensions to the MIME database”</a>.</td>
1.1 dsieger 9980: </tr>
9981: <tr>
9982: <td>Installs <code class="filename">.desktop</code> files under
9983: <code class="filename">share/applications</code> and these include MIME
9984: information.</td>
1.10 hubertf 9985: <td>See <a class="xref" href="#desktop-files" title="19.6.20. Packages installing desktop files">Section 19.6.20, “Packages installing desktop files”</a>.</td>
1.1 dsieger 9986: </tr>
9987: </tbody>
9988: </table></div>
9989: </div>
9990: <br class="table-break">
9991: </div>
1.41 asau 9992: <div class="sect1">
1.1 dsieger 9993: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 9994: <a name="full-update"></a>23.3. Updating GNOME to a newer version</h2></div></div></div>
1.1 dsieger 9995: <p>When seeing GNOME as a whole, there are two kinds of
9996: updates:</p>
1.41 asau 9997: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 9998: <dt><span class="term">Major update</span></dt>
9999: <dd>
10000: <p>Given that there is still a very long way for GNOME 3 (if it
10001: ever appears), we consider a major update one that goes from a
10002: <code class="literal">2.X</code> version to a <code class="literal">2.Y</code> one,
10003: where <code class="literal">Y</code> is even and greater than
10004: <code class="literal">X</code>. These are hard to achieve because they
10005: introduce lots of changes in the components' code and almost all
10006: GNOME distfiles are updated to newer versions. Some of them can
10007: even break API and ABI compatibility with the previous major
10008: version series. As a result, the update needs to be done all at
10009: once to minimize breakage.</p>
10010: <p>A major update typically consists of around 80 package
10011: updates and the addition of some new ones.</p>
10012: </dd>
10013: <dt><span class="term">Minor update</span></dt>
10014: <dd>
10015: <p>We consider a minor update one that goes from a
10016: <code class="literal">2.A.X</code> version to a <code class="literal">2.A.Y</code>
10017: one where <code class="literal">Y</code> is greater than
10018: <code class="literal">X</code>. These are easy to achieve because they do
10019: not update all GNOME components, can be done in an incremental way
10020: and do not break API nor ABI compatibility.</p>
10021: <p>A minor update typically consists of around 50 package
10022: updates, although the numbers here may vary a lot.</p>
10023: </dd>
10024: </dl></div>
10025: <p>In order to update the GNOME components in pkgsrc to a new stable
10026: release (either major or minor), the following steps should be
10027: followed:</p>
1.23 wiz 10028: <div class="orderedlist"><ol class="orderedlist" type="1">
10029: <li class="listitem">
1.1 dsieger 10030: <p>Get a list of all the tarballs that form the new release by
10031: using the following commands. These will leave the full list of the
1.18 snj 10032: components' distfiles into the <code class="filename">list.txt</code>
1.1 dsieger 10033: file:</p>
10034: <pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
10035: ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
10036: awk '{ print $9 }' >list.txt</code></strong>
10037: <code class="prompt">%</code> <strong class="userinput"><code>echo ls "*.tar.bz2" | \
10038: ftp -V ftp://ftp.gnome.org/pub/gnome/desktop/x.y/x.y.z/sources/ | \
10039: awk '{ print $9 }' >>list.txt</code></strong></pre>
10040: </li>
1.23 wiz 10041: <li class="listitem"><p>Open each meta package's <code class="filename">Makefile</code> and
1.1 dsieger 10042: bump their version to the release you are updating them to. The
10043: three meta packages should be always consistent with versioning.
10044: Obviously remove any <code class="varname">PKGREVISION</code>s that might be
10045: in them.</p></li>
1.23 wiz 10046: <li class="listitem">
1.1 dsieger 10047: <p>For each meta package, update all its
10048: <code class="varname">DEPENDS</code> lines to match the latest versions as
10049: shown by the above commands. Do <span class="emphasis"><em>not</em></span> list any
10050: newer version (even if found in the FTP) because the meta packages
10051: are supposed to list the exact versions that form a specific GNOME
10052: release. Exceptions are permitted here if a newer version solves a
10053: serious issue in the overall desktop experience; these typically
10054: come in the form of a revision bump in pkgsrc, not in newer versions
10055: from the developers.</p>
10056: <p>Packages not listed in the <code class="filename">list.txt</code> file
10057: should be updated to the latest version available (if found in
10058: pkgsrc). This is the case, for example, of the dependencies on the
1.79 snj 10059: GNU Autotools in the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html" target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a> meta package.</p>
1.1 dsieger 10060: </li>
1.23 wiz 10061: <li class="listitem">
1.1 dsieger 10062: <p>Generate a patch from the modified meta packages and extract the
10063: list of "new" lines. This will provide you an outline on what
10064: packages need to be updated in pkgsrc and in what order:</p>
10065: <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>
10066: </li>
1.23 wiz 10067: <li class="listitem"><p>For major desktop updates it is recommended to zap all your
1.1 dsieger 10068: installed packages and start over from scratch at this point.</p></li>
1.23 wiz 10069: <li class="listitem"><p>Now comes the longest step by far: iterate over the contents
1.1 dsieger 10070: of <code class="filename">todo.txt</code> and update the packages listed in
10071: it in order. For major desktop updates none of these should be
10072: committed until the entire set is completed because there are chances
10073: of breaking not-yet-updated packages.</p></li>
1.23 wiz 10074: <li class="listitem"><p>Once the packages are up to date and working, commit them to
1.1 dsieger 10075: the tree one by one with appropriate log messages. At the end,
10076: commit the three meta package updates and all the corresponding
10077: changes to the <code class="filename">doc/CHANGES-<YEAR></code> and
10078: <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>
10079: </ol></div>
10080: </div>
1.41 asau 10081: <div class="sect1">
1.1 dsieger 10082: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10083: <a name="patching"></a>23.4. Patching guidelines</h2></div></div></div>
1.1 dsieger 10084: <p>GNOME is a very big component in pkgsrc which approaches 100
10085: packages. Please, it is very important that you always, always,
10086: <span class="strong"><strong>always</strong></span> feed back any portability
1.10 hubertf 10087: fixes you do to a GNOME package to the mainstream developers (see <a class="xref" href="#components.patches.feedback" title="11.3.5. Feedback to the author">Section 11.3.5, “Feedback to the author”</a>). This is the only way to get
1.1 dsieger 10088: their attention on portability issues and to ensure that future versions
10089: can be built out-of-the box on NetBSD. The less custom patches in
10090: pkgsrc, the easier further updates are. Those developers in charge of
10091: issuing major GNOME updates will be grateful if you do that.</p>
1.10 hubertf 10092: <p>The most common places to report bugs are the <a class="ulink" href="http://bugzilla.gnome.org/" target="_top">GNOME's Bugzilla</a> and the <a class="ulink" href="http://bugzilla.freedesktop.org/" target="_top">freedesktop.org's
1.1 dsieger 10093: Bugzilla</a>. Not all components use these to track bugs, but most
10094: of them do. Do not be short on your reports: always provide detailed
10095: explanations of the current failure, how it can be improved to achieve
10096: maximum portability and, if at all possible, provide a patch against CVS
10097: head. The more verbose you are, the higher chances of your patch being
10098: accepted.</p>
10099: <p>Also, please avoid using preprocessor magic to fix portability
10100: issues. While the FreeBSD GNOME people are doing a great job in porting
10101: GNOME to their operating system, the official GNOME sources are now
10102: plagued by conditionals that check for <code class="varname">__FreeBSD__</code>
10103: and similar macros. This hurts portability. Please see our patching
1.10 hubertf 10104: guidelines (<a class="xref" href="#components.patches.guidelines" title="11.3.4. Patching guidelines">Section 11.3.4, “Patching guidelines”</a>) for more
1.1 dsieger 10105: details.</p>
10106: </div>
10107: </div>
10108: </div>
1.41 asau 10109: <div class="part">
1.1 dsieger 10110: <div class="titlepage"><div><div><h1 class="title">
10111: <a name="infrastructure"></a>Part III. The pkgsrc infrastructure internals</h1></div></div></div>
1.41 asau 10112: <div class="partintro">
1.1 dsieger 10113: <div></div>
10114: <p>This part of the guide deals with everything
10115: from the infrastructure that is behind the interfaces described
10116: in the developer's guide. A casual package maintainer should not
10117: need anything from this part.</p>
10118: <div class="toc">
10119: <p><b>Table of Contents</b></p>
1.100 leot 10120: <dl class="toc">
1.6 rillig 10121: <dt><span class="chapter"><a href="#infr.design">24. Design of the pkgsrc infrastructure</a></span></dt>
1.1 dsieger 10122: <dd><dl>
1.6 rillig 10123: <dt><span class="sect1"><a href="#infr.vardef">24.1. The meaning of variable definitions</a></span></dt>
10124: <dt><span class="sect1"><a href="#infr.vardef.problems">24.2. Avoiding problems before they arise</a></span></dt>
10125: <dt><span class="sect1"><a href="#infr.var">24.3. Variable evaluation</a></span></dt>
1.1 dsieger 10126: <dd><dl>
1.6 rillig 10127: <dt><span class="sect2"><a href="#infr.var.load">24.3.1. At load time</a></span></dt>
10128: <dt><span class="sect2"><a href="#infr.var.run">24.3.2. At runtime</a></span></dt>
1.1 dsieger 10129: </dl></dd>
1.6 rillig 10130: <dt><span class="sect1"><a href="#infr.varspec">24.4. How can variables be specified?</a></span></dt>
10131: <dt><span class="sect1"><a href="#infr.design.intf">24.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10132: <dd><dl>
1.6 rillig 10133: <dt><span class="sect2"><a href="#infr.design.intf.proc">24.5.1. Procedures with parameters</a></span></dt>
10134: <dt><span class="sect2"><a href="#infr.design.intf.action">24.5.2. Actions taken on behalf of parameters</a></span></dt>
1.1 dsieger 10135: </dl></dd>
1.6 rillig 10136: <dt><span class="sect1"><a href="#infr.order">24.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10137: <dd><dl>
1.23 wiz 10138: <dt><span class="sect2"><a href="#infr.order.prefs">24.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
10139: <dt><span class="sect2"><a href="#infr.order.pkg">24.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.1 dsieger 10140: </dl></dd>
10141: </dl></dd>
1.6 rillig 10142: <dt><span class="chapter"><a href="#regression">25. Regression tests</a></span></dt>
1.1 dsieger 10143: <dd><dl>
1.6 rillig 10144: <dt><span class="sect1"><a href="#regression.descr">25.1. The regression tests framework</a></span></dt>
10145: <dt><span class="sect1"><a href="#regression.run">25.2. Running the regression tests</a></span></dt>
10146: <dt><span class="sect1"><a href="#regression.new">25.3. Adding a new regression test</a></span></dt>
1.1 dsieger 10147: <dd><dl>
1.6 rillig 10148: <dt><span class="sect2"><a href="#regression.fun.override">25.3.1. Overridable functions</a></span></dt>
10149: <dt><span class="sect2"><a href="#regression.fun.helper">25.3.2. Helper functions</a></span></dt>
1.1 dsieger 10150: </dl></dd>
10151: </dl></dd>
1.6 rillig 10152: <dt><span class="chapter"><a href="#porting">26. Porting pkgsrc</a></span></dt>
1.1 dsieger 10153: <dd><dl>
1.6 rillig 10154: <dt><span class="sect1"><a href="#porting.opsys">26.1. Porting pkgsrc to a new operating system</a></span></dt>
10155: <dt><span class="sect1"><a href="#porting.compiler">26.2. Adding support for a new compiler</a></span></dt>
1.1 dsieger 10156: </dl></dd>
10157: </dl>
10158: </div>
10159: </div>
1.41 asau 10160: <div class="chapter">
1.1 dsieger 10161: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 10162: <a name="infr.design"></a>Chapter 24. Design of the pkgsrc infrastructure</h2></div></div></div>
1.1 dsieger 10163: <div class="toc">
10164: <p><b>Table of Contents</b></p>
1.100 leot 10165: <dl class="toc">
1.6 rillig 10166: <dt><span class="sect1"><a href="#infr.vardef">24.1. The meaning of variable definitions</a></span></dt>
10167: <dt><span class="sect1"><a href="#infr.vardef.problems">24.2. Avoiding problems before they arise</a></span></dt>
10168: <dt><span class="sect1"><a href="#infr.var">24.3. Variable evaluation</a></span></dt>
1.1 dsieger 10169: <dd><dl>
1.6 rillig 10170: <dt><span class="sect2"><a href="#infr.var.load">24.3.1. At load time</a></span></dt>
10171: <dt><span class="sect2"><a href="#infr.var.run">24.3.2. At runtime</a></span></dt>
1.1 dsieger 10172: </dl></dd>
1.6 rillig 10173: <dt><span class="sect1"><a href="#infr.varspec">24.4. How can variables be specified?</a></span></dt>
10174: <dt><span class="sect1"><a href="#infr.design.intf">24.5. Designing interfaces for Makefile fragments</a></span></dt>
1.1 dsieger 10175: <dd><dl>
1.6 rillig 10176: <dt><span class="sect2"><a href="#infr.design.intf.proc">24.5.1. Procedures with parameters</a></span></dt>
10177: <dt><span class="sect2"><a href="#infr.design.intf.action">24.5.2. Actions taken on behalf of parameters</a></span></dt>
1.1 dsieger 10178: </dl></dd>
1.6 rillig 10179: <dt><span class="sect1"><a href="#infr.order">24.6. The order in which files are loaded</a></span></dt>
1.1 dsieger 10180: <dd><dl>
1.23 wiz 10181: <dt><span class="sect2"><a href="#infr.order.prefs">24.6.1. The order in <code class="filename">bsd.prefs.mk</code></a></span></dt>
10182: <dt><span class="sect2"><a href="#infr.order.pkg">24.6.2. The order in <code class="filename">bsd.pkg.mk</code></a></span></dt>
1.1 dsieger 10183: </dl></dd>
10184: </dl>
10185: </div>
10186: <p>The pkgsrc infrastructure consists of many small Makefile
10187: fragments. Each such fragment needs a properly specified
10188: interface. This chapter explains how such an interface looks
10189: like.</p>
1.41 asau 10190: <div class="sect1">
1.1 dsieger 10191: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10192: <a name="infr.vardef"></a>24.1. The meaning of variable definitions</h2></div></div></div>
1.1 dsieger 10193: <p>Whenever a variable is defined in the pkgsrc
10194: infrastructure, the location and the way of definition provide
10195: much information about the intended use of that variable.
10196: Additionally, more documentation may be found in a header
10197: comment or in this pkgsrc guide.</p>
10198: <p>A special file is
10199: <code class="filename">mk/defaults/mk.conf</code>, which lists all
10200: variables that are intended to be user-defined. They are either
10201: defined using the <code class="literal">?=</code> operator or they are
10202: left undefined because defining them to anything would
1.23 wiz 10203: effectively mean <span class="quote">“<span class="quote">yes</span>”</span>. All these variables may be
1.1 dsieger 10204: overridden by the pkgsrc user in the <code class="varname">MAKECONF</code>
10205: file.</p>
10206: <p>Outside this file, the following conventions apply:
10207: Variables that are defined using the <code class="literal">?=</code>
10208: operator may be overridden by a package.</p>
10209: <p>Variables that are defined using the <code class="literal">=</code>
10210: operator may be used read-only at run-time.</p>
10211: <p>Variables whose name starts with an underscore must not be
10212: accessed outside the pkgsrc infrastructure at all. They may
10213: change without further notice.</p>
1.41 asau 10214: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 10215: <h3 class="title">Note</h3>
10216: <p>These conventions are currently not applied
10217: consistently to the complete pkgsrc
10218: infrastructure.</p>
10219: </div>
10220: </div>
1.41 asau 10221: <div class="sect1">
1.1 dsieger 10222: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10223: <a name="infr.vardef.problems"></a>24.2. Avoiding problems before they arise</h2></div></div></div>
1.1 dsieger 10224: <p>All variables that contain lists of things should default
10225: to being empty. Two examples that do not follow this rule are
10226: <code class="varname">USE_LANGUAGES</code> and
10227: <code class="varname">DISTFILES</code>. These variables cannot simply be
10228: modified using the <code class="literal">+=</code> operator in package
10229: <code class="filename">Makefile</code>s (or other files included by
10230: them), since there is no guarantee whether the variable is
10231: already set or not, and what its value is. In the case of
1.23 wiz 10232: <code class="varname">DISTFILES</code>, the packages <span class="quote">“<span class="quote">know</span>”</span>
1.1 dsieger 10233: the default value and just define it as in the following
10234: example.</p>
10235: <pre class="programlisting">
10236: DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz
10237: </pre>
10238: <p>Because of the selection of this default value, the same
10239: value appears in many package Makefiles. Similarly for
10240: <code class="varname">USE_LANGUAGES</code>, but in this case the default
1.23 wiz 10241: value (<span class="quote">“<span class="quote"><code class="literal">c</code></span>”</span>) is so short that it
1.1 dsieger 10242: doesn't stand out. Nevertheless it is mentioned in many
10243: files.</p>
10244: </div>
1.41 asau 10245: <div class="sect1">
1.1 dsieger 10246: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10247: <a name="infr.var"></a>24.3. Variable evaluation</h2></div></div></div>
1.41 asau 10248: <div class="sect2">
1.1 dsieger 10249: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10250: <a name="infr.var.load"></a>24.3.1. At load time</h3></div></div></div>
1.1 dsieger 10251: <p>Variable evaluation takes place either at load time or at
10252: runtime, depending on the context in which they occur. The
10253: contexts where variables are evaluated at load time are:</p>
1.41 asau 10254: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10255: <li class="listitem"><p>The right hand side of the <code class="literal">:=</code>
1.1 dsieger 10256: and <code class="literal">!=</code> operators,</p></li>
1.23 wiz 10257: <li class="listitem"><p>Make directives like <code class="literal">.if</code> or
1.1 dsieger 10258: <code class="literal">.for</code>,</p></li>
1.23 wiz 10259: <li class="listitem"><p>Dependency lines.</p></li>
1.1 dsieger 10260: </ul></div>
10261: <p>A special exception are references to the iteration
10262: variables of <code class="literal">.for</code> loops, which are expanded
10263: inline, no matter in which context they appear.</p>
10264: <p>As the values of variables may change during load time,
10265: care must be taken not to evaluate them by accident. Typical
10266: examples for variables that should not be evaluated at load time
10267: are <code class="varname">DEPENDS</code> and
10268: <code class="varname">CONFIGURE_ARGS</code>. To make the effect more
10269: clear, here is an example:</p>
10270: <pre class="programlisting">
10271: CONFIGURE_ARGS= # none
10272: CFLAGS= -O
10273: CONFIGURE_ARGS+= CFLAGS=${CFLAGS:Q}
10274:
10275: CONFIGURE_ARGS:= ${CONFIGURE_ARGS}
10276:
10277: CFLAGS+= -Wall
10278: </pre>
10279: <p>This code shows how the use of the <code class="literal">:=</code>
10280: operator can quickly lead to unexpected results. The first
10281: paragraph is fairly common code. The second paragraph evaluates
10282: the <code class="varname">CONFIGURE_ARGS</code> variable, which results in
10283: <code class="literal">CFLAGS=-O</code>. In the third paragraph, the
10284: <code class="literal">-Wall</code> is appended to the
10285: <code class="varname">CFLAGS</code>, but this addition will not appear in
10286: <code class="varname">CONFIGURE_ARGS</code>. In actual code, the three
10287: paragraphs from above typically occur in completely unrelated
10288: files.</p>
10289: </div>
1.41 asau 10290: <div class="sect2">
1.1 dsieger 10291: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10292: <a name="infr.var.run"></a>24.3.2. At runtime</h3></div></div></div>
1.1 dsieger 10293: <p>After all the files have been loaded, the values of the
10294: variables cannot be changed anymore. Variables that are used in
10295: the shell commands are expanded at this point.</p>
10296: </div>
10297: </div>
1.41 asau 10298: <div class="sect1">
1.1 dsieger 10299: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10300: <a name="infr.varspec"></a>24.4. How can variables be specified?</h2></div></div></div>
1.1 dsieger 10301: <p>There are many ways in which the definition and use of a
10302: variable can be restricted in order to detect bugs and
10303: violations of the (mostly unwritten) policies. See the
10304: <code class="literal">pkglint</code> developer's documentation for further
10305: details.</p>
10306: </div>
1.41 asau 10307: <div class="sect1">
1.1 dsieger 10308: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10309: <a name="infr.design.intf"></a>24.5. Designing interfaces for Makefile fragments</h2></div></div></div>
1.1 dsieger 10310: <p>Most of the <code class="filename">.mk</code> files fall into one
10311: of the following classes. Cases where a file falls into more
10312: than one class should be avoided as it often leads to subtle
10313: bugs.</p>
1.41 asau 10314: <div class="sect2">
1.1 dsieger 10315: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10316: <a name="infr.design.intf.proc"></a>24.5.1. Procedures with parameters</h3></div></div></div>
1.1 dsieger 10317: <p>In a traditional imperative programming language some of
10318: the <code class="filename">.mk</code> files could be described as
1.14 jmcneill 10319: procedures. They take some input parameters and—after
10320: inclusion—provide a result in output parameters. Since all
1.1 dsieger 10321: variables in <code class="filename">Makefile</code>s have global scope
10322: care must be taken not to use parameter names that have already
10323: another meaning. For example, <code class="varname">PKGNAME</code> is a
10324: bad choice for a parameter name.</p>
10325: <p>Procedures are completely evaluated at preprocessing time.
10326: That is, when calling a procedure all input parameters must be
10327: completely resolvable. For example,
10328: <code class="varname">CONFIGURE_ARGS</code> should never be an input
10329: parameter since it is very likely that further text will be
10330: added after calling the procedure, which would effectively apply
10331: the procedure to only a part of the variable. Also, references
10332: to other variables wit will be modified after calling the
10333: procedure.</p>
10334: <p>A procedure can declare its output parameters either as
10335: suitable for use in preprocessing directives or as only
10336: available at runtime. The latter alternative is for variables
10337: that contain references to other runtime variables.</p>
10338: <p>Procedures shall be written such that it is possible to
10339: call the procedure more than once. That is, the file must not
10340: contain multiple-inclusion guards.</p>
10341: <p>Examples for procedures are
10342: <code class="filename">mk/bsd.options.mk</code> and
10343: <code class="filename">mk/buildlink3/bsd.builtin.mk</code>. To express
10344: that the parameters are evaluated at load time, they should be
10345: assigned using the <code class="literal">:=</code> operator, which should
10346: be used only for this purpose.</p>
10347: </div>
1.41 asau 10348: <div class="sect2">
1.1 dsieger 10349: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10350: <a name="infr.design.intf.action"></a>24.5.2. Actions taken on behalf of parameters</h3></div></div></div>
1.1 dsieger 10351: <p>Action files take some input parameters and may define
10352: runtime variables. They shall not define loadtime variables.
10353: There are action files that are included implicitly by the
10354: pkgsrc infrastructure, while other must be included
10355: explicitly.</p>
10356: <p>An example for action files is
10357: <code class="filename">mk/subst.mk</code>.</p>
10358: </div>
10359: </div>
1.41 asau 10360: <div class="sect1">
1.1 dsieger 10361: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10362: <a name="infr.order"></a>24.6. The order in which files are loaded</h2></div></div></div>
1.1 dsieger 10363: <p>Package <code class="filename">Makefile</code>s usually consist of
10364: a set of variable definitions, and include the file
10365: <code class="filename">../../mk/bsd.pkg.mk</code> in the very last line.
10366: Before that, they may also include various other
10367: <code class="filename">*.mk</code> files if they need to query the
10368: availability of certain features like the type of compiler or
10369: the X11 implementation. Due to the heavy use of preprocessor
10370: directives like <code class="literal">.if</code> and
10371: <code class="literal">.for</code>, the order in which the files are loaded
10372: matters.</p>
10373: <p>This section describes at which point the various files
10374: are loaded and gives reasons for that order.</p>
1.41 asau 10375: <div class="sect2">
1.1 dsieger 10376: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10377: <a name="infr.order.prefs"></a>24.6.1. The order in <code class="filename">bsd.prefs.mk</code>
1.1 dsieger 10378: </h3></div></div></div>
10379: <p>The very first action in <code class="filename">bsd.prefs.mk</code>
10380: is to define some essential variables like
10381: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code> and
10382: <code class="varname">MACHINE_ARCH</code>.</p>
10383: <p>Then, the user settings are loaded from the file specified
1.10 hubertf 10384: 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 10385: After that, those variables
1.1 dsieger 10386: that have not been overridden by the user are loaded from
10387: <code class="filename">mk/defaults/mk.conf</code>.</p>
10388: <p>After the user settings, the system settings and platform
10389: settings are loaded, which may override the user
10390: settings.</p>
10391: <p>Then, the tool definitions are loaded. The tool wrappers
10392: are not yet in effect. This only happens when building a
10393: package, so the proper variables must be used instead of the
10394: direct tool names.</p>
10395: <p>As the last steps, some essential variables from the
10396: wrapper and the package system flavor are loaded, as well as the
10397: variables that have been cached in earlier phases of a package
10398: build.</p>
10399: </div>
1.41 asau 10400: <div class="sect2">
1.1 dsieger 10401: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10402: <a name="infr.order.pkg"></a>24.6.2. The order in <code class="filename">bsd.pkg.mk</code>
1.1 dsieger 10403: </h3></div></div></div>
10404: <p>First, <code class="filename">bsd.prefs.mk</code> is loaded.</p>
10405: <p>Then, the various <code class="filename">*-vars.mk</code> files are
10406: loaded, which fill default values for those variables that have
10407: not been defined by the package. These variables may later
10408: be used even in unrelated files.</p>
10409: <p>Then, the file <code class="filename">bsd.pkg.error.mk</code>
10410: provides the target <code class="literal">error-check</code> that is added
10411: as a special dependency to all other targets that use
10412: <code class="varname">DELAYED_ERROR_MSG</code> or
10413: <code class="varname">DELAYED_WARNING_MSG</code>.</p>
10414: <p>Then, the package-specific hacks from
10415: <code class="filename">hacks.mk</code> are included.</p>
10416: <p>Then, various other files follow. Most of them don't have
10417: any dependencies on what they need to have included before or
10418: after them, though some do.</p>
10419: <p>The code to check <code class="varname">PKG_FAIL_REASON</code> and
10420: <code class="varname">PKG_SKIP_REASON</code> is then executed, which
10421: restricts the use of these variables to all the files that have
10422: been included before. Appearances in later files will be
10423: silently ignored.</p>
10424: <p>Then, the files for the main targets are included, in the
10425: order of later execution, though the actual order should not
10426: matter.</p>
10427: <p>At last, some more files are included that don't set any
10428: interesting variables but rather just define make targets to be
10429: executed.</p>
10430: </div>
10431: </div>
10432: </div>
1.41 asau 10433: <div class="chapter">
1.1 dsieger 10434: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 10435: <a name="regression"></a>Chapter 25. Regression tests</h2></div></div></div>
1.1 dsieger 10436: <div class="toc">
10437: <p><b>Table of Contents</b></p>
1.100 leot 10438: <dl class="toc">
1.6 rillig 10439: <dt><span class="sect1"><a href="#regression.descr">25.1. The regression tests framework</a></span></dt>
10440: <dt><span class="sect1"><a href="#regression.run">25.2. Running the regression tests</a></span></dt>
10441: <dt><span class="sect1"><a href="#regression.new">25.3. Adding a new regression test</a></span></dt>
1.1 dsieger 10442: <dd><dl>
1.6 rillig 10443: <dt><span class="sect2"><a href="#regression.fun.override">25.3.1. Overridable functions</a></span></dt>
10444: <dt><span class="sect2"><a href="#regression.fun.helper">25.3.2. Helper functions</a></span></dt>
1.1 dsieger 10445: </dl></dd>
10446: </dl>
10447: </div>
10448: <p>The pkgsrc infrastructure consists of a large codebase,
10449: and there are many corners where every little bit of a file is
10450: well thought out, making pkgsrc likely to fail as soon as
10451: anything is changed near those parts. To prevent most changes
10452: from breaking anything, a suite of regression tests should go
10453: along with every important part of the pkgsrc infrastructure.
10454: This chapter describes how regression tests work in pkgsrc and
10455: how you can add new tests.</p>
1.41 asau 10456: <div class="sect1">
1.1 dsieger 10457: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10458: <a name="regression.descr"></a>25.1. The regression tests framework</h2></div></div></div>
1.1 dsieger 10459: <p></p>
10460: </div>
1.41 asau 10461: <div class="sect1">
1.1 dsieger 10462: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10463: <a name="regression.run"></a>25.2. Running the regression tests</h2></div></div></div>
1.79 snj 10464: <p>You first need to install the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_regress/README.html" target="_top"><code class="filename">pkgtools/pkg_regress</code></a> package, which
1.10 hubertf 10465: provides the <span class="command"><strong>pkg_regress</strong></span> command. Then you
1.1 dsieger 10466: can simply run that command, which will run all tests in the
10467: <code class="filename">regress</code> category.</p>
10468: </div>
1.41 asau 10469: <div class="sect1">
1.1 dsieger 10470: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10471: <a name="regression.new"></a>25.3. Adding a new regression test</h2></div></div></div>
1.1 dsieger 10472: <p>Every directory in the <code class="filename">regress</code>
10473: category that contains a file called <code class="filename">spec</code>
10474: is considered a regression test. This file is a shell program
1.10 hubertf 10475: that is included by the <span class="command"><strong>pkg_regress</strong></span> command.
1.1 dsieger 10476: The following functions can be overridden to suit your
10477: needs.</p>
1.41 asau 10478: <div class="sect2">
1.1 dsieger 10479: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10480: <a name="regression.fun.override"></a>25.3.1. Overridable functions</h3></div></div></div>
1.1 dsieger 10481: <p>These functions do not take any parameters. They are all
1.23 wiz 10482: called in <span class="quote">“<span class="quote">set -e</span>”</span> mode, so you should be careful
1.1 dsieger 10483: to check the exitcodes of any commands you run in the
10484: test.</p>
1.41 asau 10485: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 10486: <dt><span class="term"><code class="varname">do_setup()</code></span></dt>
10487: <dd><p>This function prepares the environment for the
10488: test. By default it does nothing.</p></dd>
10489: <dt><span class="term"><code class="varname">do_test()</code></span></dt>
10490: <dd><p>This function runs the actual test. By default,
10491: it calls <code class="varname">TEST_MAKE</code> with the arguments
10492: <code class="varname">MAKEARGS_TEST</code> and writes its output including
10493: error messages into the file
10494: <code class="varname">TEST_OUTFILE</code>.</p></dd>
10495: <dt><span class="term"><code class="varname">check_result()</code></span></dt>
10496: <dd><p>This function is run after the test and is
10497: typically used to compare the actual output from the one that is
10498: expected. It can make use of the various helper functions from
10499: the next section.</p></dd>
10500: <dt><span class="term"><code class="varname">do_cleanup()</code></span></dt>
10501: <dd><p>This function cleans everything up after the
10502: test has been run. By default it does nothing.</p></dd>
10503: </dl></div>
10504: </div>
1.41 asau 10505: <div class="sect2">
1.1 dsieger 10506: <div class="titlepage"><div><div><h3 class="title">
1.6 rillig 10507: <a name="regression.fun.helper"></a>25.3.2. Helper functions</h3></div></div></div>
1.41 asau 10508: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 10509: <dt><span class="term"><code class="varname">exit_status(expected)</code></span></dt>
10510: <dd><p>This function compares the exitcode of the
1.10 hubertf 10511: <span class="command"><strong>do_test()</strong></span> function with its first parameter.
1.1 dsieger 10512: If they differ, the test will fail.</p></dd>
10513: <dt><span class="term"><code class="varname">output_require(regex...)</code></span></dt>
10514: <dd><p>This function checks for each of its parameters
1.10 hubertf 10515: if the output from <span class="command"><strong>do_test()</strong></span> matches the
1.1 dsieger 10516: extended regular expression. If it does not, the test will
10517: fail.</p></dd>
10518: <dt><span class="term"><code class="varname">output_prohibit(regex...)</code></span></dt>
10519: <dd><p>This function checks for each of its parameters
1.10 hubertf 10520: if the output from <span class="command"><strong>do_test()</strong></span> does
1.1 dsieger 10521: <span class="emphasis"><em>not</em></span> match the extended regular expression.
10522: If any of the regular expressions matches, the test will
10523: fail.</p></dd>
10524: </dl></div>
10525: </div>
10526: </div>
10527: </div>
1.41 asau 10528: <div class="chapter">
1.1 dsieger 10529: <div class="titlepage"><div><div><h2 class="title">
1.6 rillig 10530: <a name="porting"></a>Chapter 26. Porting pkgsrc</h2></div></div></div>
1.1 dsieger 10531: <div class="toc">
10532: <p><b>Table of Contents</b></p>
1.100 leot 10533: <dl class="toc">
1.6 rillig 10534: <dt><span class="sect1"><a href="#porting.opsys">26.1. Porting pkgsrc to a new operating system</a></span></dt>
10535: <dt><span class="sect1"><a href="#porting.compiler">26.2. Adding support for a new compiler</a></span></dt>
1.1 dsieger 10536: </dl>
10537: </div>
10538: <p>The pkgsrc system has already been ported to many
10539: operating systems, hardware architectures and compilers. This
10540: chapter explains the necessary steps to make pkgsrc even more
10541: portable.</p>
1.41 asau 10542: <div class="sect1">
1.1 dsieger 10543: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10544: <a name="porting.opsys"></a>26.1. Porting pkgsrc to a new operating system</h2></div></div></div>
1.1 dsieger 10545: <p>To port pkgsrc to a new operating system (called
10546: <code class="literal">MyOS</code> in this example), you need to touch the
10547: following files:</p>
1.41 asau 10548: <div class="variablelist"><dl class="variablelist">
1.1 dsieger 10549: <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>
10550: <dd><p>This file contains some basic definitions, for
10551: example the name of the C
10552: compiler.</p></dd>
10553: <dt><span class="term"><code class="filename">mk/bsd.prefs.mk</code></span></dt>
10554: <dd><p>Insert code that defines the variables
10555: <code class="varname">OPSYS</code>, <code class="varname">OS_VERSION</code>,
10556: <code class="varname">LOWER_OS_VERSION</code>,
10557: <code class="varname">LOWER_VENDOR</code>,
10558: <code class="varname">MACHINE_ARCH</code>, <code class="varname">OBJECT_FMT</code>,
10559: <code class="varname">APPEND_ELF</code>, and the other variables that
10560: appear in this file.</p></dd>
10561: <dt><span class="term"><code class="filename">mk/platform/<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10562: <dd><p>This file contains the platform-specific
10563: definitions that are used by pkgsrc. Start by copying one of the
10564: other files and edit it to your
10565: needs.</p></dd>
10566: <dt><span class="term"><code class="filename">mk/tools/tools.<em class="replaceable"><code>MyOS</code></em>.mk</code></span></dt>
10567: <dd><p>This file defines the paths to all the tools
10568: that are needed by one or the other package in pkgsrc, as well
10569: as by pkgsrc itself. Find out where these tools are on your
10570: platform and add them.</p></dd>
10571: </dl></div>
10572: <p>Now, you should be able to build some basic packages, like
1.79 snj 10573: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/perl5/README.html" target="_top"><code class="filename">lang/perl5</code></a>, <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a>.</p>
1.1 dsieger 10574: </div>
1.41 asau 10575: <div class="sect1">
1.1 dsieger 10576: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.6 rillig 10577: <a name="porting.compiler"></a>26.2. Adding support for a new compiler</h2></div></div></div>
1.1 dsieger 10578: <p>TODO</p>
10579: </div>
10580: </div>
10581: </div>
1.41 asau 10582: <div class="appendix">
10583: <div class="titlepage"><div><div><h1 class="title">
10584: <a name="examples"></a>Appendix A. A simple example package: bison</h1></div></div></div>
1.1 dsieger 10585: <div class="toc">
10586: <p><b>Table of Contents</b></p>
1.100 leot 10587: <dl class="toc">
1.1 dsieger 10588: <dt><span class="sect1"><a href="#example-files">A.1. files</a></span></dt>
10589: <dd><dl>
10590: <dt><span class="sect2"><a href="#example-Makefile">A.1.1. Makefile</a></span></dt>
10591: <dt><span class="sect2"><a href="#example-descr">A.1.2. DESCR</a></span></dt>
10592: <dt><span class="sect2"><a href="#example-plist">A.1.3. PLIST</a></span></dt>
1.23 wiz 10593: <dt><span class="sect2"><a href="#checking-package-with-pkglint">A.1.4. Checking a package with <span class="command"><strong>pkglint</strong></span></a></span></dt>
1.1 dsieger 10594: </dl></dd>
10595: <dt><span class="sect1"><a href="#steps-for-b-i-p">A.2. Steps for building, installing, packaging</a></span></dt>
10596: </dl>
10597: </div>
10598: <p>We checked to find a piece of software that wasn't in the packages
10599: collection, and picked GNU bison. Quite why someone would want to have
1.10 hubertf 10600: <span class="command"><strong>bison</strong></span> when Berkeley <span class="command"><strong>yacc</strong></span> is already
1.1 dsieger 10601: present in the tree is beyond us, but it's useful for the purposes of
10602: this exercise.</p>
1.41 asau 10603: <div class="sect1">
1.1 dsieger 10604: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10605: <a name="example-files"></a>A.1. files</h2></div></div></div>
1.41 asau 10606: <div class="sect2">
1.1 dsieger 10607: <div class="titlepage"><div><div><h3 class="title">
10608: <a name="example-Makefile"></a>A.1.1. Makefile</h3></div></div></div>
10609: <pre class="programlisting">
10610: # $NetBSD$
10611: #
10612:
10613: DISTNAME= bison-1.25
10614: CATEGORIES= devel
10615: MASTER_SITES= ${MASTER_SITE_GNU}
10616:
1.29 dholland 10617: MAINTAINER= pkgsrc-users@NetBSD.org
1.1 dsieger 10618: HOMEPAGE= http://www.gnu.org/software/bison/bison.html
10619: COMMENT= GNU yacc clone
10620:
10621: GNU_CONFIGURE= yes
1.46 wiz 10622: INFO_FILES= yes
1.1 dsieger 10623:
10624: .include "../../mk/bsd.pkg.mk"
10625: </pre>
10626: </div>
1.41 asau 10627: <div class="sect2">
1.1 dsieger 10628: <div class="titlepage"><div><div><h3 class="title">
10629: <a name="example-descr"></a>A.1.2. DESCR</h3></div></div></div>
10630: <pre class="programlisting">
10631: GNU version of yacc. Can make re-entrant parsers, and numerous other
1.79 snj 10632: improvements. Why you would want this when Berkeley <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?yacc+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">yacc</span>(1)</span></a> is part
1.1 dsieger 10633: of the NetBSD source tree is beyond me.
10634: </pre>
10635: </div>
1.41 asau 10636: <div class="sect2">
1.1 dsieger 10637: <div class="titlepage"><div><div><h3 class="title">
10638: <a name="example-plist"></a>A.1.3. PLIST</h3></div></div></div>
10639: <pre class="programlisting">
10640: @comment $NetBSD$
10641: bin/bison
10642: man/man1/bison.1.gz
10643: share/bison.simple
10644: share/bison.hairy
10645: </pre>
10646: </div>
1.41 asau 10647: <div class="sect2">
1.1 dsieger 10648: <div class="titlepage"><div><div><h3 class="title">
1.10 hubertf 10649: <a name="checking-package-with-pkglint"></a>A.1.4. Checking a package with <span class="command"><strong>pkglint</strong></span>
1.1 dsieger 10650: </h3></div></div></div>
10651: <p>The NetBSD package system comes with
1.79 snj 10652: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>
1.1 dsieger 10653: which helps to check the contents of these
10654: files. After installation it is quite easy to use, just change to the
10655: directory of the package you wish to examine and execute
1.10 hubertf 10656: <span class="command"><strong>pkglint</strong></span>:</p>
1.1 dsieger 10657: <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>pkglint</code></strong>
10658: looks fine.</pre>
10659: <p>Depending on the supplied command line arguments (see pkglint(1)),
1.10 hubertf 10660: more checks will be performed. Use e.g. <span class="command"><strong>pkglint -Call
1.1 dsieger 10661: -Wall</strong></span> for a very thorough check.</p>
10662: </div>
10663: </div>
1.41 asau 10664: <div class="sect1">
1.1 dsieger 10665: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10666: <a name="steps-for-b-i-p"></a>A.2. Steps for building, installing, packaging</h2></div></div></div>
10667: <p>Create the directory where the package lives,
10668: plus any auxiliary directories:</p>
10669: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /usr/pkgsrc/lang</code></strong>
10670: <code class="prompt">#</code> <strong class="userinput"><code>mkdir bison</code></strong>
10671: <code class="prompt">#</code> <strong class="userinput"><code>cd bison</code></strong>
10672: <code class="prompt">#</code> <strong class="userinput"><code>mkdir patches</code></strong></pre>
10673: <p>Create <code class="filename">Makefile</code>, <code class="filename">DESCR</code> and
1.10 hubertf 10674: <code class="filename">PLIST</code> (see <a class="xref" href="#components" title="Chapter 11. Package components - files, directories and contents">Chapter 11, <i>Package components - files, directories and contents</i></a>)
1.1 dsieger 10675: then continue with fetching the distfile:</p>
10676: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make fetch</code></strong>
10677: >> bison-1.25.tar.gz doesn't seem to exist on this system.
10678: >> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
10679: Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10680: ftp: Error retrieving file: 500 Internal error
10681:
10682: >> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
10683: Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10684: ftp: Error retrieving file: 500 Internal error
10685:
10686: >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
10687: Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
10688: Successfully retrieved file.</pre>
10689: <p>Generate the checksum of the distfile into
10690: <code class="filename">distinfo</code>:</p>
10691: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make makedistinfo</code></strong></pre>
10692: <p>Now compile:</p>
10693: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
10694: >> Checksum OK for bison-1.25.tar.gz.
10695: ===> Extracting for bison-1.25
10696: ===> Patching for bison-1.25
10697: ===> Ignoring empty patch directory
10698: ===> Configuring for bison-1.25
10699: creating cache ./config.cache
10700: checking for gcc... cc
10701: checking whether we are using GNU C... yes
10702: checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
10703: checking how to run the C preprocessor... cc -E
10704: checking for minix/config.h... no
10705: checking for POSIXized ISC... no
10706: checking whether cross-compiling... no
10707: checking for ANSI C header files... yes
10708: checking for string.h... yes
10709: checking for stdlib.h... yes
10710: checking for memory.h... yes
10711: checking for working const... yes
10712: checking for working alloca.h... no
10713: checking for alloca... yes
10714: checking for strerror... yes
10715: updating cache ./config.cache
10716: creating ./config.status
10717: creating Makefile
10718: ===> Building for bison-1.25
10719: 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
10720: 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
10721: 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
10722: 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
10723: 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
10724: 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
10725: 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
10726: 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
10727: 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
10728: 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
10729: 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
10730: 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
10731: 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
10732: 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
10733: 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
10734: 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
10735: 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
10736: 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
10737: 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
10738: 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
10739: 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
10740: 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
10741: ./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
10742: rm -f bison.s1
10743: sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1</pre>
10744: <p>Everything seems OK, so install the files:</p>
10745: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
10746: >> Checksum OK for bison-1.25.tar.gz.
10747: ===> Installing for bison-1.25
10748: sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
10749: rm -f /usr/pkg/bin/bison
10750: cd /usr/pkg/share; rm -f bison.simple bison.hairy
10751: rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
10752: install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
10753: /usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
10754: /usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
10755: cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
10756: /usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
10757: ===> Registering installation for bison-1.25</pre>
10758: <p>You can now use bison, and also - if you decide so - remove it with
1.10 hubertf 10759: <span class="command"><strong>pkg_delete bison</strong></span>. Should you decide that you want a
1.1 dsieger 10760: binary package, do this now:</p>
10761: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
10762: >> Checksum OK for bison-1.25.tar.gz.
10763: ===> Building package for bison-1.25
10764: Creating package bison-1.25.tgz
10765: Registering depends:.
10766: Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'</pre>
10767: <p>Now that you don't need the source and object files
10768: any more, clean up:</p>
10769: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make clean</code></strong>
10770: ===> Cleaning for bison-1.25</pre>
10771: </div>
10772: </div>
1.41 asau 10773: <div class="appendix">
10774: <div class="titlepage"><div><div><h1 class="title">
10775: <a name="logs"></a>Appendix B. Build logs</h1></div></div></div>
1.1 dsieger 10776: <div class="toc">
10777: <p><b>Table of Contents</b></p>
1.100 leot 10778: <dl class="toc">
1.1 dsieger 10779: <dt><span class="sect1"><a href="#logs.building">B.1. Building figlet</a></span></dt>
10780: <dt><span class="sect1"><a href="#logs.package">B.2. Packaging figlet</a></span></dt>
10781: </dl>
10782: </div>
1.41 asau 10783: <div class="sect1">
1.1 dsieger 10784: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10785: <a name="logs.building"></a>B.1. Building figlet</h2></div></div></div>
10786: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make</code></strong>
10787: ===> Checking for vulnerabilities in figlet-2.2.1nb2
10788: => figlet221.tar.gz doesn't seem to exist on this system.
10789: => Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
10790: => [172219 bytes]
10791: Connected to ftp.plig.net.
10792: 220 ftp.plig.org NcFTPd Server (licensed copy) ready.
10793: 331 Guest login ok, send your complete e-mail address as password.
10794: 230-You are user #5 of 500 simultaneous users allowed.
10795: 230-
10796: 230- ___ _ _ _
10797: 230- | _| |_ ___ ___| |_|___ ___ ___ ___
10798: 230- | _| _| . |_| . | | | . |_| . | _| . |
10799: 230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
10800: 230- |_| |_| |___| |___|
10801: 230-
10802: 230-** Welcome to ftp.plig.org **
10803: 230-
10804: 230-Please note that all transfers from this FTP site are logged. If you
10805: 230-do not like this, please disconnect now.
10806: 230-
1.18 snj 10807: 230-This archive is available via
1.1 dsieger 10808: 230-
10809: 230-HTTP: http://ftp.plig.org/
10810: 230-FTP: ftp://ftp.plig.org/ (max 500 connections)
10811: 230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
10812: 230-
10813: 230-Please email comments, bug reports and requests for packages to be
10814: 230-mirrored to ftp-admin@plig.org.
10815: 230-
10816: 230-
10817: 230 Logged in anonymously.
10818: Remote system type is UNIX.
10819: Using binary mode to transfer files.
10820: 200 Type okay.
10821: 250 "/pub" is new cwd.
10822: 250-"/pub/figlet" is new cwd.
10823: 250-
10824: 250-Welcome to the figlet archive at ftp.figlet.org
10825: 250-
10826: 250- ftp://ftp.figlet.org/pub/figlet/
10827: 250-
10828: 250-The official FIGlet web page is:
10829: 250- http://www.figlet.org/
10830: 250-
10831: 250-If you have questions, please mailto:info@figlet.org. If you want to
10832: 250-contribute a font or something else, you can email us.
10833: 250
10834: 250 "/pub/figlet/program" is new cwd.
10835: 250 "/pub/figlet/program/unix" is new cwd.
10836: local: figlet221.tar.gz remote: figlet221.tar.gz
10837: 502 Unimplemented command.
10838: 227 Entering Passive Mode (195,40,6,41,246,104)
10839: 150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
10840: 38% |************** | 65800 64.16 KB/s 00:01 ETA
10841: 226 Transfer completed.
10842: 172219 bytes received in 00:02 (75.99 KB/s)
10843: 221 Goodbye.
10844: => Checksum OK for figlet221.tar.gz.
10845: ===> Extracting for figlet-2.2.1nb2
10846: ===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
10847: ===> Patching for figlet-2.2.1nb2
10848: ===> Applying pkgsrc patches for figlet-2.2.1nb2
10849: ===> Overriding tools for figlet-2.2.1nb2
10850: ===> Creating toolchain wrappers for figlet-2.2.1nb2
10851: ===> Configuring for figlet-2.2.1nb2
10852: ===> Building for figlet-2.2.1nb2
10853: gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
10854: chmod a+x figlet
10855: gcc -O2 -o chkfont chkfont.c
10856: => Unwrapping files-to-be-installed.
10857: <code class="prompt">#</code>
10858: <code class="prompt">#</code> <strong class="userinput"><code>make install</code></strong>
10859: ===> Checking for vulnerabilities in figlet-2.2.1nb2
10860: ===> Installing for figlet-2.2.1nb2
10861: install -d -o root -g wheel -m 755 /usr/pkg/bin
10862: install -d -o root -g wheel -m 755 /usr/pkg/man/man6
10863: mkdir -p /usr/pkg/share/figlet
10864: cp figlet /usr/pkg/bin
10865: cp chkfont /usr/pkg/bin
10866: chmod 555 figlist showfigfonts
10867: cp figlist /usr/pkg/bin
10868: cp showfigfonts /usr/pkg/bin
10869: cp fonts/*.flf /usr/pkg/share/figlet
10870: cp fonts/*.flc /usr/pkg/share/figlet
10871: cp figlet.6 /usr/pkg/man/man6
10872: ===> Registering installation for figlet-2.2.1nb2
10873: <code class="prompt">#</code></pre>
10874: </div>
1.41 asau 10875: <div class="sect1">
1.1 dsieger 10876: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
10877: <a name="logs.package"></a>B.2. Packaging figlet</h2></div></div></div>
10878: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>make package</code></strong>
10879: ===> Checking for vulnerabilities in figlet-2.2.1nb2
10880: ===> Packaging figlet-2.2.1nb2
10881: ===> Building binary package for figlet-2.2.1nb2
10882: Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
10883: Using SrcDir value of /usr/pkg
10884: Registering depends:.
10885: <code class="prompt">#</code></pre>
10886: </div>
10887: </div>
1.41 asau 10888: <div class="appendix">
10889: <div class="titlepage"><div><div><h1 class="title">
10890: <a name="ftp-layout"></a>Appendix C. Directory layout of the pkgsrc FTP server</h1></div></div></div>
1.1 dsieger 10891: <div class="toc">
10892: <p><b>Table of Contents</b></p>
1.100 leot 10893: <dl class="toc">
1.23 wiz 10894: <dt><span class="sect1"><a href="#ftp-distfiles">C.1. <code class="filename">distfiles</code>: The distributed source files</a></span></dt>
10895: <dt><span class="sect1"><a href="#ftp-misc">C.2. <code class="filename">misc</code>: Miscellaneous things</a></span></dt>
10896: <dt><span class="sect1"><a href="#ftp-packages">C.3. <code class="filename">packages</code>: Binary packages</a></span></dt>
10897: <dt><span class="sect1"><a href="#ftp-reports">C.4. <code class="filename">reports</code>: Bulk build reports</a></span></dt>
10898: <dt><span class="sect1"><a href="#ftp-source">C.5. <code class="filename">current</code>,
10899: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 10900: source packages</a></span></dt>
10901: </dl>
10902: </div>
10903: <p>As in other big projects, the directory layout of pkgsrc
10904: is quite complex for newbies. This chapter explains where you
10905: find things on the FTP server. The base directory on
1.10 hubertf 10906: <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>.
1.1 dsieger 10907: On other servers it may be different, but inside this directory,
10908: everything should look the same, no matter on which server you
10909: are. This directory contains some subdirectories, which are
10910: explained below.</p>
1.41 asau 10911: <div class="sect1">
1.1 dsieger 10912: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.22 jakllsch 10913: <a name="ftp-distfiles"></a>C.1. <code class="filename">distfiles</code>: The distributed source files</h2></div></div></div>
1.1 dsieger 10914: <p>The directory <code class="filename">distfiles</code> contains lots
10915: of archive files from all pkgsrc packages, which are mirrored
10916: here. The subdirectories are called after their package names
10917: and are used when the distributed files have names that don't
10918: explicitly contain a version number or are otherwise too generic
10919: (for example <code class="filename">release.tar.gz</code>).</p>
10920: </div>
1.41 asau 10921: <div class="sect1">
1.1 dsieger 10922: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.22 jakllsch 10923: <a name="ftp-misc"></a>C.2. <code class="filename">misc</code>: Miscellaneous things</h2></div></div></div>
1.1 dsieger 10924: <p>This directory contains things that individual pkgsrc
10925: developers find worth publishing.</p>
10926: </div>
1.41 asau 10927: <div class="sect1">
1.1 dsieger 10928: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.22 jakllsch 10929: <a name="ftp-packages"></a>C.3. <code class="filename">packages</code>: Binary packages</h2></div></div></div>
1.3 rillig 10930: <p>This directory contains binary packages for the various
10931: platforms that are supported by pkgsrc.
10932: 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>
1.41 asau 10933: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 10934: <li class="listitem"><p><code class="varname">OPSYS</code> is the name of the
1.9 rillig 10935: operating system for which the packages have been built. The
1.10 hubertf 10936: name is taken from the output of the <span class="command"><strong>uname</strong></span>
1.9 rillig 10937: command, so it may differ from the one you are used to
10938: hear.</p></li>
1.23 wiz 10939: <li class="listitem"><p><code class="varname">ARCH</code> is the hardware
1.8 rillig 10940: architecture of the platform for which the packages have been
1.10 hubertf 10941: built. It also includes the <code class="varname">ABI</code> (Application
10942: Binary Interface) for platforms that have several of
10943: them.</p></li>
1.23 wiz 10944: <li class="listitem"><p><code class="varname">OSVERSION</code> is the version of
1.8 rillig 10945: the operating system. For version numbers that change often (for
10946: example NetBSD-current), the often-changing part should be
10947: replaced with an <code class="literal">x</code>, for example
10948: <code class="literal">4.99.x</code>.</p></li>
1.23 wiz 10949: <li class="listitem"><p><code class="varname">TAG</code> is either
1.22 jakllsch 10950: <code class="literal">20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>
1.8 rillig 10951: for a stable branch, or <code class="literal">head</code> for packages
10952: built from the HEAD branch. The latter should only be used when
10953: the packages are updated on a regular basis. Otherwise the date
10954: from checking out pkgsrc should be appended, for example
10955: <code class="literal">head_20071015</code>.</p></li>
1.3 rillig 10956: </ul></div>
10957: <p>The rationale for exactly this scheme is that the pkgsrc users looking for binary packages
10958: can quickly click through the directories on the
10959: server and find the best binary packages for their machines. Since they
10960: usually know the operating system and the hardware architecture, OPSYS
10961: and ARCH are placed first. After these choices, they can select the
10962: best combination of OSVERSION and TAG together, since it is usually the
10963: case that packages stay compatible between different version of the
10964: operating system.</p>
10965: <p>In each of these directories, there is a
10966: whole binary packages collection for a specific platform. It has a directory called
1.1 dsieger 10967: <code class="filename">All</code> which contains all binary packages.
10968: Besides that, there are various category directories that
10969: contain symbolic links to the real binary packages.</p>
10970: </div>
1.41 asau 10971: <div class="sect1">
1.1 dsieger 10972: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.22 jakllsch 10973: <a name="ftp-reports"></a>C.4. <code class="filename">reports</code>: Bulk build reports</h2></div></div></div>
1.8 rillig 10974: <p>Here are the reports from bulk builds, for those who want
10975: to fix packages that didn't build on some of the platforms. The
1.23 wiz 10976: structure of subdirectories should look like the one in <a class="xref" href="#ftp-packages" title="C.3. packages: Binary packages">Section C.3, “<code class="filename">packages</code>: Binary packages”</a>.</p>
1.8 rillig 10977: </div>
1.41 asau 10978: <div class="sect1">
1.8 rillig 10979: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
1.22 jakllsch 10980: <a name="ftp-source"></a>C.5. <code class="filename">current</code>,
10981: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em></code>:
1.1 dsieger 10982: source packages</h2></div></div></div>
1.23 wiz 10983: <p>These directories contain the <span class="quote">“<span class="quote">real</span>”</span> pkgsrc,
1.1 dsieger 10984: that is the files that define how to create binary packages from
10985: source archives.</p>
10986: <p>The directory <code class="filename">pkgsrc</code> contains a
10987: snapshot of the CVS repository, which is updated regularly. The
10988: file <code class="filename">pkgsrc.tar.gz</code> contains the same as the
10989: directory, ready to be downloaded as a whole.</p>
10990: <p>In the directories for the quarterly branches, there is an
10991: additional file called
1.22 jakllsch 10992: <code class="filename">pkgsrc-20<em class="replaceable"><code>xx</code></em>Q<em class="replaceable"><code>y</code></em>.tar.gz</code>,
1.1 dsieger 10993: which contains the state of pkgsrc when it was branched.</p>
10994: </div>
10995: </div>
1.41 asau 10996: <div class="appendix">
10997: <div class="titlepage"><div><div><h1 class="title">
10998: <a name="editing"></a>Appendix D. Editing guidelines for the pkgsrc guide</h1></div></div></div>
1.1 dsieger 10999: <div class="toc">
11000: <p><b>Table of Contents</b></p>
1.100 leot 11001: <dl class="toc">
1.1 dsieger 11002: <dt><span class="sect1"><a href="#targets">D.1. Make targets</a></span></dt>
11003: <dt><span class="sect1"><a href="#procedure">D.2. Procedure</a></span></dt>
11004: </dl>
11005: </div>
11006: <p>This section contains information on editing the pkgsrc
11007: guide itself.</p>
1.41 asau 11008: <div class="sect1">
1.1 dsieger 11009: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11010: <a name="targets"></a>D.1. Make targets</h2></div></div></div>
11011: <p>The pkgsrc guide's source code is stored in
11012: <code class="filename">pkgsrc/doc/guide/files</code>, and several files
11013: are created from it:</p>
1.41 asau 11014: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
1.23 wiz 11015: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.txt</code></p></li>
11016: <li class="listitem"><p><code class="filename">pkgsrc/doc/pkgsrc.html</code></p></li>
11017: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/docs/pkgsrc/" target="_top">http://www.NetBSD.org/docs/pkgsrc/</a></p></li>
11018: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf" target="_top">http://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf</a>:
1.1 dsieger 11019: The PDF version of the pkgsrc guide.</p></li>
1.23 wiz 11020: <li class="listitem"><p><a class="ulink" href="http://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps" target="_top">http://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps</a>:
1.1 dsieger 11021: PostScript version of the pkgsrc guide.</p></li>
11022: </ul></div>
11023: </div>
1.41 asau 11024: <div class="sect1">
1.1 dsieger 11025: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
11026: <a name="procedure"></a>D.2. Procedure</h2></div></div></div>
11027: <p>The procedure to edit the pkgsrc guide is:</p>
1.23 wiz 11028: <div class="procedure"><ol class="procedure" type="1">
1.41 asau 11029: <li class="step"><p>Make sure you have the packages needed to
1.1 dsieger 11030: regenerate the pkgsrc guide (and other XML-based NetBSD
1.45 obache 11031: documentation) installed. These are automatically installed when
1.79 snj 11032: you install the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/pkgsrc-guide-tools/README.html" target="_top"><code class="filename">meta-pkgs/pkgsrc-guide-tools</code></a> package.</p></li>
1.41 asau 11033: <li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the
1.1 dsieger 11034: right directory. All further steps will take place
11035: here.</p></li>
1.41 asau 11036: <li class="step"><p>Edit the XML file(s) in
1.1 dsieger 11037: <code class="filename">files/</code>.</p></li>
1.41 asau 11038: <li class="step"><p>Run <span class="command"><strong>bmake</strong></span> to check the pkgsrc
1.1 dsieger 11039: guide for valid XML and to build the final output files. If you
11040: get any errors at this stage, you can just edit the files, as
11041: there are only symbolic links in the working directory, pointing
11042: to the files in <code class="filename">files/</code>.</p></li>
1.41 asau 11043: <li class="step"><p><span class="command"><strong>(cd files && cvs
1.1 dsieger 11044: commit)</strong></span></p></li>
1.41 asau 11045: <li class="step"><p>Run <span class="command"><strong>bmake clean && bmake</strong></span> to
1.1 dsieger 11046: regenerate the output files with the proper RCS
11047: Ids.</p></li>
1.41 asau 11048: <li class="step">
1.10 hubertf 11049: <p>Run <span class="command"><strong>bmake regen</strong></span> to install and
1.1 dsieger 11050: commit the files in both <code class="filename">pkgsrc/doc</code> and
11051: <code class="filename">htdocs</code>.</p>
1.41 asau 11052: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
1.1 dsieger 11053: <h3 class="title">Note</h3>
11054: <p>If you have added, removed or renamed some chapters,
1.10 hubertf 11055: you need to synchronize them using <span class="command"><strong>cvs add</strong></span> or
11056: <span class="command"><strong>cvs delete</strong></span> in the htdocs
1.1 dsieger 11057: directory.</p>
11058: </div>
11059: </li>
11060: </ol></div>
11061: </div>
11062: </div>
11063: </div></body>
11064: </html>
CVSweb <webmaster@jp.NetBSD.org>