Annotation of htdocs/docs/pkgsrc/pkgsrc.txt, revision 1.115
1.1 dsieger 1: The pkgsrc guide
2:
3: Documentation on the NetBSD packages system
4:
5: Alistair Crooks
6:
7: <agc@NetBSD.org>
8:
9: Hubert Feyrer
10:
11: <hubertf@NetBSD.org>
12:
13: The pkgsrc Developers
14:
1.107 jnemeth 15: Copyright 1994-2016 The NetBSD Foundation, Inc
1.1 dsieger 16:
1.108 rillig 17: $NetBSD: pkgsrc.xml,v 1.30 2016/06/11 18:14:42 rillig Exp $
1.1 dsieger 18:
19: Abstract
20:
21: pkgsrc is a centralized package management system for Unix-like operating
22: systems. This guide provides information for users and developers of pkgsrc. It
23: covers installation of binary and source packages, creation of binary and
24: source packages and a high-level overview about the infrastructure.
25:
26: -------------------------------------------------------------------------------
27:
28: Table of Contents
29:
30: 1. What is pkgsrc?
31:
32: 1.1. Introduction
33:
34: 1.1.1. Why pkgsrc?
35: 1.1.2. Supported platforms
36:
37: 1.2. Overview
38: 1.3. Terminology
39:
40: 1.3.1. Roles involved in pkgsrc
41:
42: 1.4. Typography
43:
44: I. The pkgsrc user's guide
45:
46: 2. Where to get pkgsrc and how to keep it up-to-date
47:
48: 2.1. Getting pkgsrc for the first time
49:
1.52 asau 50: 2.1.1. As tar archive
1.24 wiz 51: 2.1.2. Via anonymous CVS
1.1 dsieger 52:
53: 2.2. Keeping pkgsrc up-to-date
54:
55: 2.2.1. Via tar files
56: 2.2.2. Via CVS
57:
58: 3. Using pkgsrc on systems other than NetBSD
59:
60: 3.1. Binary distribution
61: 3.2. Bootstrapping pkgsrc
62: 3.3. Platform-specific notes
63:
64: 4. Using pkgsrc
65:
66: 4.1. Using binary packages
67:
68: 4.1.1. Finding binary packages
69: 4.1.2. Installing binary packages
70: 4.1.3. Deinstalling packages
71: 4.1.4. Getting information about installed packages
72: 4.1.5. Checking for security vulnerabilities in installed packages
73: 4.1.6. Finding if newer versions of your installed packages are in
74: pkgsrc
75: 4.1.7. Other administrative functions
76:
77: 4.2. Building packages from source
78:
79: 4.2.1. Requirements
80: 4.2.2. Fetching distfiles
81: 4.2.3. How to build and install
82:
83: 5. Configuring pkgsrc
84:
85: 5.1. General configuration
86: 5.2. Variables affecting the build process
1.9 rillig 87: 5.3. Variables affecting the installation process
1.4 rillig 88: 5.4. Selecting and configuring the compiler
1.1 dsieger 89:
1.4 rillig 90: 5.4.1. Selecting the compiler
91: 5.4.2. Additional flags to the compiler (CFLAGS)
92: 5.4.3. Additional flags to the linker (LDFLAGS)
1.1 dsieger 93:
1.4 rillig 94: 5.5. Developer/advanced settings
95: 5.6. Selecting Build Options
1.1 dsieger 96:
97: 6. Creating binary packages
98:
99: 6.1. Building a single binary package
100: 6.2. Settings for creation of binary packages
101:
1.6 rillig 102: 7. Creating binary packages for everything in pkgsrc (bulk builds)
103:
1.71 wiz 104: 7.1. Preparations
105: 7.2. Running a pbulk-style bulk build
1.6 rillig 106:
1.71 wiz 107: 7.2.1. Configuration
1.6 rillig 108:
1.71 wiz 109: 7.3. Requirements of a full bulk build
1.66 asau 110: 7.4. Creating a multiple CD-ROM packages collection
1.6 rillig 111:
1.66 asau 112: 7.4.1. Example of cdpack
1.6 rillig 113:
114: 8. Directory layout of the installed files
115:
116: 8.1. File system layout in ${LOCALBASE}
117: 8.2. File system layout in ${VARBASE}
118:
119: 9. Frequently Asked Questions
120:
121: 9.1. Are there any mailing lists for pkg-related discussion?
1.84 wiz 122: 9.2. Utilities for package management (pkgtools)
123: 9.3. How to use pkgsrc as non-root
124: 9.4. How to resume transfers when fetching distfiles?
125: 9.5. How can I install/use modular X.org from pkgsrc?
126: 9.6. How to fetch files from behind a firewall
127: 9.7. How to fetch files from HTTPS sites
128: 9.8. How do I tell make fetch to do passive FTP?
129: 9.9. How to fetch all distfiles at once
130: 9.10. What does "Don't know how to make /usr/share/tmac/tmac.andoc"
1.24 wiz 131: mean?
1.84 wiz 132: 9.11. What does "Could not find bsd.own.mk" mean?
133: 9.12. Using 'sudo' with pkgsrc
134: 9.13. How do I change the location of configuration files?
135: 9.14. Automated security checks
136: 9.15. Why do some packages ignore my CFLAGS?
137: 9.16. A package does not build. What shall I do?
138: 9.17. What does "Makefile appears to contain unresolved cvs/rcs/???
1.24 wiz 139: merge conflicts" mean?
1.1 dsieger 140:
141: II. The pkgsrc developer's guide
142:
1.6 rillig 143: 10. Creating a new pkgsrc package from scratch
1.1 dsieger 144:
1.6 rillig 145: 10.1. Common types of packages
1.1 dsieger 146:
1.6 rillig 147: 10.1.1. Perl modules
1.66 asau 148: 10.1.2. KDE3 applications
1.17 imil 149: 10.1.3. Python modules and programs
1.1 dsieger 150:
1.6 rillig 151: 10.2. Examples
1.1 dsieger 152:
1.6 rillig 153: 10.2.1. How the www/nvu package came into pkgsrc
1.1 dsieger 154:
1.6 rillig 155: 11. Package components - files, directories and contents
1.1 dsieger 156:
1.6 rillig 157: 11.1. Makefile
158: 11.2. distinfo
159: 11.3. patches/*
1.1 dsieger 160:
1.6 rillig 161: 11.3.1. Structure of a single patch file
162: 11.3.2. Creating patch files
163: 11.3.3. Sources where the patch files come from
164: 11.3.4. Patching guidelines
165: 11.3.5. Feedback to the author
1.1 dsieger 166:
1.6 rillig 167: 11.4. Other mandatory files
168: 11.5. Optional files
1.1 dsieger 169:
1.6 rillig 170: 11.5.1. Files affecting the binary package
171: 11.5.2. Files affecting the build process
172: 11.5.3. Files affecting nothing at all
1.1 dsieger 173:
1.6 rillig 174: 11.6. work*
175: 11.7. files/*
1.1 dsieger 176:
1.6 rillig 177: 12. Programming in Makefiles
1.1 dsieger 178:
1.6 rillig 179: 12.1. Caveats
180: 12.2. Makefile variables
1.1 dsieger 181:
1.6 rillig 182: 12.2.1. Naming conventions
1.1 dsieger 183:
1.6 rillig 184: 12.3. Code snippets
1.1 dsieger 185:
1.6 rillig 186: 12.3.1. Adding things to a list
1.108 rillig 187: 12.3.2. Echoing a string exacty as-is
188: 12.3.3. Passing CFLAGS to GNU configure scripts
189: 12.3.4. Handling possibly empty variables
1.1 dsieger 190:
1.6 rillig 191: 13. PLIST issues
1.1 dsieger 192:
1.6 rillig 193: 13.1. RCS ID
194: 13.2. Semi-automatic PLIST generation
195: 13.3. Tweaking output of make print-PLIST
196: 13.4. Variable substitution in PLIST
197: 13.5. Man page compression
198: 13.6. Changing PLIST source with PLIST_SRC
199: 13.7. Platform-specific and differing PLISTs
1.86 wiz 200: 13.8. Build-specific PLISTs
201: 13.9. Sharing directories between packages
1.1 dsieger 202:
1.6 rillig 203: 14. Buildlink methodology
1.1 dsieger 204:
1.6 rillig 205: 14.1. Converting packages to use buildlink3
206: 14.2. Writing buildlink3.mk files
1.1 dsieger 207:
1.6 rillig 208: 14.2.1. Anatomy of a buildlink3.mk file
1.27 wiz 209: 14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and
210: BUILDLINK_ABI_DEPENDS.pkg in buildlink3.mk files
1.1 dsieger 211:
1.6 rillig 212: 14.3. Writing builtin.mk files
1.1 dsieger 213:
1.6 rillig 214: 14.3.1. Anatomy of a builtin.mk file
215: 14.3.2. Global preferences for native or pkgsrc software
1.1 dsieger 216:
1.6 rillig 217: 15. The pkginstall framework
1.1 dsieger 218:
1.6 rillig 219: 15.1. Files and directories outside the installation prefix
1.1 dsieger 220:
1.6 rillig 221: 15.1.1. Directory manipulation
222: 15.1.2. File manipulation
1.1 dsieger 223:
1.6 rillig 224: 15.2. Configuration files
1.1 dsieger 225:
1.6 rillig 226: 15.2.1. How PKG_SYSCONFDIR is set
227: 15.2.2. Telling the software where configuration files are
228: 15.2.3. Patching installations
229: 15.2.4. Disabling handling of configuration files
1.1 dsieger 230:
1.6 rillig 231: 15.3. System startup scripts
1.1 dsieger 232:
1.6 rillig 233: 15.3.1. Disabling handling of system startup scripts
1.1 dsieger 234:
1.6 rillig 235: 15.4. System users and groups
236: 15.5. System shells
1.1 dsieger 237:
1.6 rillig 238: 15.5.1. Disabling shell registration
1.1 dsieger 239:
1.6 rillig 240: 15.6. Fonts
1.1 dsieger 241:
1.6 rillig 242: 15.6.1. Disabling automatic update of the fonts databases
1.1 dsieger 243:
1.6 rillig 244: 16. Options handling
1.1 dsieger 245:
1.6 rillig 246: 16.1. Global default options
247: 16.2. Converting packages to use bsd.options.mk
248: 16.3. Option Names
1.7 rillig 249: 16.4. Determining the options of dependencies
1.1 dsieger 250:
1.6 rillig 251: 17. The build process
1.1 dsieger 252:
1.6 rillig 253: 17.1. Introduction
254: 17.2. Program location
255: 17.3. Directories used during the build process
256: 17.4. Running a phase
257: 17.5. The fetch phase
1.1 dsieger 258:
1.6 rillig 259: 17.5.1. What to fetch and where to get it from
260: 17.5.2. How are the files fetched?
1.1 dsieger 261:
1.6 rillig 262: 17.6. The checksum phase
263: 17.7. The extract phase
264: 17.8. The patch phase
265: 17.9. The tools phase
266: 17.10. The wrapper phase
267: 17.11. The configure phase
268: 17.12. The build phase
269: 17.13. The test phase
270: 17.14. The install phase
271: 17.15. The package phase
272: 17.16. Cleaning up
273: 17.17. Other helpful targets
1.1 dsieger 274:
1.6 rillig 275: 18. Tools needed for building or running
1.1 dsieger 276:
1.6 rillig 277: 18.1. Tools for pkgsrc builds
278: 18.2. Tools needed by packages
279: 18.3. Tools provided by platforms
1.1 dsieger 280:
1.6 rillig 281: 19. Making your package work
1.1 dsieger 282:
1.6 rillig 283: 19.1. General operation
1.1 dsieger 284:
1.108 rillig 285: 19.1.1. How to pull in user-settable variables from mk.conf
286: 19.1.2. User interaction
287: 19.1.3. Handling licenses
288: 19.1.4. Restricted packages
289: 19.1.5. Handling dependencies
290: 19.1.6. Handling conflicts with other packages
291: 19.1.7. Packages that cannot or should not be built
292: 19.1.8. Packages which should not be deleted, once installed
293: 19.1.9. Handling packages with security problems
294: 19.1.10. How to handle incrementing versions when fixing an
1.1 dsieger 295: existing package
1.108 rillig 296: 19.1.11. Substituting variable text in the package files (the SUBST
1.1 dsieger 297: framework)
298:
1.108 rillig 299: 19.2. The fetch phase
1.1 dsieger 300:
1.6 rillig 301: 19.2.1. Packages whose distfiles aren't available for plain
1.1 dsieger 302: downloading
1.6 rillig 303: 19.2.2. How to handle modified distfiles with the 'old' name
1.88 tnn 304: 19.2.3. Packages hosted on github.com
1.1 dsieger 305:
1.108 rillig 306: 19.3. The configure phase
1.1 dsieger 307:
1.6 rillig 308: 19.3.1. Shared libraries - libtool
309: 19.3.2. Using libtool on GNU packages that already support libtool
310: 19.3.3. GNU Autoconf/Automake
311:
312: 19.4. Programming languages
313:
314: 19.4.1. C, C++, and Fortran
315: 19.4.2. Java
316: 19.4.3. Packages containing perl scripts
1.41 wiz 317: 19.4.4. Packages containing shell scripts
318: 19.4.5. Other programming languages
1.6 rillig 319:
1.108 rillig 320: 19.5. The build phase
1.6 rillig 321:
322: 19.5.1. Compiling C and C++ code conditionally
323: 19.5.2. How to handle compiler bugs
1.24 wiz 324: 19.5.3. Undefined reference to "..."
1.6 rillig 325: 19.5.4. Running out of memory
326:
1.108 rillig 327: 19.6. The install phase
1.6 rillig 328:
329: 19.6.1. Creating needed directories
330: 19.6.2. Where to install documentation
331: 19.6.3. Installing highscore files
332: 19.6.4. Adding DESTDIR support to packages
333: 19.6.5. Packages with hardcoded paths to other interpreters
334: 19.6.6. Packages installing perl modules
335: 19.6.7. Packages installing info files
336: 19.6.8. Packages installing man pages
1.7 rillig 337: 19.6.9. Packages installing GConf data files
1.18 mishka 338: 19.6.10. Packages installing scrollkeeper/rarian data files
1.6 rillig 339: 19.6.11. Packages installing X11 fonts
340: 19.6.12. Packages installing GTK2 modules
341: 19.6.13. Packages installing SGML or XML data
342: 19.6.14. Packages installing extensions to the MIME database
343: 19.6.15. Packages using intltool
344: 19.6.16. Packages installing startup scripts
345: 19.6.17. Packages installing TeX modules
346: 19.6.18. Packages supporting running binaries in emulation
347: 19.6.19. Packages installing hicolor theme icons
348: 19.6.20. Packages installing desktop files
349:
350: 19.7. Marking packages as having problems
351:
352: 20. Debugging
353: 21. Submitting and Committing
354:
355: 21.1. Submitting binary packages
356: 21.2. Submitting source packages (for non-NetBSD-developers)
357: 21.3. General notes when adding, updating, or removing packages
1.34 wiz 358: 21.4. Committing: Adding a package to CVS
1.6 rillig 359: 21.5. Updating a package to a newer version
1.21 snj 360: 21.6. Renaming a package in pkgsrc
361: 21.7. Moving a package in pkgsrc
1.6 rillig 362:
363: 22. Frequently Asked Questions
364: 23. GNOME packaging and porting
365:
366: 23.1. Meta packages
367: 23.2. Packaging a GNOME application
368: 23.3. Updating GNOME to a newer version
369: 23.4. Patching guidelines
1.1 dsieger 370:
371: III. The pkgsrc infrastructure internals
372:
1.6 rillig 373: 24. Design of the pkgsrc infrastructure
1.1 dsieger 374:
1.6 rillig 375: 24.1. The meaning of variable definitions
376: 24.2. Avoiding problems before they arise
377: 24.3. Variable evaluation
1.1 dsieger 378:
1.6 rillig 379: 24.3.1. At load time
380: 24.3.2. At runtime
1.1 dsieger 381:
1.6 rillig 382: 24.4. How can variables be specified?
383: 24.5. Designing interfaces for Makefile fragments
1.1 dsieger 384:
1.6 rillig 385: 24.5.1. Procedures with parameters
386: 24.5.2. Actions taken on behalf of parameters
1.1 dsieger 387:
1.6 rillig 388: 24.6. The order in which files are loaded
1.1 dsieger 389:
1.6 rillig 390: 24.6.1. The order in bsd.prefs.mk
391: 24.6.2. The order in bsd.pkg.mk
1.1 dsieger 392:
1.6 rillig 393: 25. Regression tests
1.1 dsieger 394:
1.108 rillig 395: 25.1. Running the regression tests
396: 25.2. Adding a new regression test
1.1 dsieger 397:
1.108 rillig 398: 25.2.1. Overridable functions
399: 25.2.2. Helper functions
1.1 dsieger 400:
1.6 rillig 401: 26. Porting pkgsrc
1.1 dsieger 402:
1.6 rillig 403: 26.1. Porting pkgsrc to a new operating system
1.1 dsieger 404:
405: A. A simple example package: bison
406:
407: A.1. files
408:
409: A.1.1. Makefile
410: A.1.2. DESCR
411: A.1.3. PLIST
412: A.1.4. Checking a package with pkglint
413:
414: A.2. Steps for building, installing, packaging
415:
416: B. Build logs
417:
418: B.1. Building figlet
419: B.2. Packaging figlet
420:
421: C. Directory layout of the pkgsrc FTP server
422:
1.23 jakllsch 423: C.1. distfiles: The distributed source files
424: C.2. misc: Miscellaneous things
425: C.3. packages: Binary packages
426: C.4. reports: Bulk build reports
427: C.5. current, pkgsrc-20xxQy: source packages
1.1 dsieger 428:
429: D. Editing guidelines for the pkgsrc guide
430:
431: D.1. Make targets
432: D.2. Procedure
433:
434: List of Tables
435:
436: 1.1. Platforms supported by pkgsrc
1.6 rillig 437: 11.1. Patching examples
438: 23.1. PLIST handling for GNOME packages
1.1 dsieger 439:
440: Chapter 1. What is pkgsrc?
441:
442: Table of Contents
443:
444: 1.1. Introduction
445:
446: 1.1.1. Why pkgsrc?
447: 1.1.2. Supported platforms
448:
449: 1.2. Overview
450: 1.3. Terminology
451:
452: 1.3.1. Roles involved in pkgsrc
453:
454: 1.4. Typography
455:
456: 1.1. Introduction
457:
458: There is a lot of software freely available for Unix-based systems, which is
459: usually available in form of the source code. Before such software can be used,
460: it needs to be configured to the local system, compiled and installed, and this
461: is exactly what The NetBSD Packages Collection (pkgsrc) does. pkgsrc also has
462: some basic commands to handle binary packages, so that not every user has to
463: build the packages for himself, which is a time-costly task.
464:
465: pkgsrc currently contains several thousand packages, including:
466:
1.104 sevan 467: * www/apache24 - The Apache web server
1.1 dsieger 468:
469: * www/firefox - The Firefox web browser
470:
471: * meta-pkgs/gnome - The GNOME Desktop Environment
472:
1.102 ryoon 473: * meta-pkgs/kde4 - The K Desktop Environment
1.1 dsieger 474:
1.108 rillig 475: ? just to name a few.
1.1 dsieger 476:
477: pkgsrc has built-in support for handling varying dependencies, such as pthreads
478: and X11, and extended features such as IPv6 support on a range of platforms.
479:
480: 1.1.1. Why pkgsrc?
481:
482: pkgsrc provides the following key features:
483:
484: * Easy building of software from source as well as the creation and
485: installation of binary packages. The source and latest patches are
486: retrieved from a master or mirror download site, checksum verified, then
487: built on your system. Support for binary-only distributions is available
488: for both native platforms and NetBSD emulated platforms.
489:
490: * All packages are installed in a consistent directory tree, including
491: binaries, libraries, man pages and other documentation.
492:
1.104 sevan 493: * Tracking of package dependencies automatically, including when performing
494: updates, to ensure required packages are installed. The configuration files
495: of various packages are handled automatically during updates, so local
496: changes are preserved.
1.1 dsieger 497:
498: * Like NetBSD, pkgsrc is designed with portability in mind and consists of
499: highly portable code. This allows the greatest speed of development when
1.26 spz 500: porting to a new platform. This portability also ensures that pkgsrc is
1.1 dsieger 501: consistent across all platforms.
502:
503: * The installation prefix, acceptable software licenses, international
504: encryption requirements and build-time options for a large number of
505: packages are all set in a simple, central configuration file.
506:
507: * The entire source (not including the distribution files) is freely
508: available under a BSD license, so you may extend and adapt pkgsrc to your
509: needs. Support for local packages and patches is available right out of the
510: box, so you can configure it specifically for your environment.
511:
512: The following principles are basic to pkgsrc:
513:
514: * "It should only work if it's right." ? That means, if a package contains
515: bugs, it's better to find them and to complain about them rather than to
516: just install the package and hope that it works. There are numerous checks
517: in pkgsrc that try to find such bugs: Static analysis tools (pkgtools/
518: pkglint), build-time checks (portability of shell scripts), and
519: post-installation checks (installed files, references to shared libraries,
520: script interpreters).
521:
522: * "If it works, it should work everywhere" ? Like NetBSD has been ported to
523: many hardware architectures, pkgsrc has been ported to many operating
524: systems. Care is taken that packages behave the same on all platforms.
525:
526: 1.1.2. Supported platforms
527:
528: pkgsrc consists of both a source distribution and a binary distribution for
529: these operating systems. After retrieving the required source or binaries, you
530: can be up and running with pkgsrc in just minutes!
531:
532: pkgsrc was derived from FreeBSD's ports system, and initially developed for
533: NetBSD only. Since then, pkgsrc has grown a lot, and now supports the following
534: platforms:
535:
536: Table 1.1. Platforms supported by pkgsrc
537:
1.92 sevan 538: +-----------------------------------------------------------------------------+
539: | Platform | Date Support | Notes |
540: | | Added | |
541: |--------------------------------------+---------------+----------------------|
542: |NetBSD | Aug 1997 | |
543: |--------------------------------------+---------------+----------------------|
544: |Solaris | Mar 1999 |README.Solaris |
545: |--------------------------------------+---------------+----------------------|
546: |Linux | Jun 1999 |README.Linux |
547: |--------------------------------------+---------------+----------------------|
548: |Darwin (Mac OS X) | Oct 2001 |README.MacOSX |
549: |--------------------------------------+---------------+----------------------|
550: |FreeBSD | Nov 2002 |README.FreeBSD |
551: |--------------------------------------+---------------+----------------------|
552: |OpenBSD | Nov 2002 |README.OpenBSD |
553: |--------------------------------------+---------------+----------------------|
554: |IRIX | Dec 2002 |README.IRIX |
555: | | |README.IRIX5.3 |
556: |--------------------------------------+---------------+----------------------|
557: |BSD/OS | Dec 2003 | |
558: |--------------------------------------+---------------+----------------------|
559: |AIX | Dec 2003 |README.AIX |
560: |--------------------------------------+---------------+----------------------|
561: |Interix (Microsoft Windows Services | Mar 2004 |README.Interix |
562: |for Unix) | | |
563: |--------------------------------------+---------------+----------------------|
564: |DragonFlyBSD | Oct 2004 | |
565: |--------------------------------------+---------------+----------------------|
566: |OSF/1 | Nov 2004 |README.OSF1 |
567: |--------------------------------------+---------------+----------------------|
568: |HP-UX | Apr 2007 |README.HPUX |
569: |--------------------------------------+---------------+----------------------|
570: |Haiku | Sep 2010 |README.Haiku |
571: |--------------------------------------+---------------+----------------------|
572: |MirBSD | Jan 2011 | |
573: |--------------------------------------+---------------+----------------------|
574: |Minix3 | Nov 2011 |README.Minix3 |
575: |--------------------------------------+---------------+----------------------|
576: |Cygwin | Mar 2013 |README.Cygwin |
577: |--------------------------------------+---------------+----------------------|
578: |GNU/kFreeBSD | Jul 2013 |README.GNUkFreeBSD |
1.104 sevan 579: |--------------------------------------+---------------+----------------------|
580: |Bitrig | Jun 2014 |README.Bitrig |
1.92 sevan 581: +-----------------------------------------------------------------------------+
1.1 dsieger 582:
583:
584: 1.2. Overview
585:
586: This document is divided into three parts. The first, The pkgsrc user's guide,
587: describes how one can use one of the packages in the Package Collection, either
588: by installing a precompiled binary package, or by building one's own copy using
589: the NetBSD package system. The second part, The pkgsrc developer's guide,
590: explains how to prepare a package so it can be easily built by other NetBSD
591: users without knowing about the package's building details. The third part, The
592: pkgsrc infrastructure internals is intended for those who want to understand
593: how pkgsrc is implemented.
594:
595: This document is available in various formats: HTML, PDF, PS, TXT.
596:
597: 1.3. Terminology
598:
599: There has been a lot of talk about "ports", "packages", etc. so far. Here is a
600: description of all the terminology used within this document.
601:
602: Package
603:
604: A set of files and building instructions that describe what's necessary to
605: build a certain piece of software using pkgsrc. Packages are traditionally
606: stored under /usr/pkgsrc.
607:
608: The NetBSD package system
609:
610: This is the former name of "pkgsrc". It is part of the NetBSD operating
611: system and can be bootstrapped to run on non-NetBSD operating systems as
612: well. It handles building (compiling), installing, and removing of
613: packages.
614:
615: Distfile
616:
617: This term describes the file or files that are provided by the author of
618: the piece of software to distribute his work. All the changes necessary to
619: build on NetBSD are reflected in the corresponding package. Usually the
620: distfile is in the form of a compressed tar-archive, but other types are
621: possible, too. Distfiles are usually stored below /usr/pkgsrc/distfiles.
622:
623: Port
624:
625: This is the term used by FreeBSD and OpenBSD people for what we call a
626: package. In NetBSD terminology, "port" refers to a different architecture.
627:
628: Precompiled/binary package
629:
630: A set of binaries built with pkgsrc from a distfile and stuffed together in
631: a single .tgz file so it can be installed on machines of the same machine
632: architecture without the need to recompile. Packages are usually generated
633: in /usr/pkgsrc/packages; there is also an archive on ftp.NetBSD.org.
634:
635: Sometimes, this is referred to by the term "package" too, especially in the
636: context of precompiled packages.
637:
638: Program
639:
640: The piece of software to be installed which will be constructed from all
641: the files in the distfile by the actions defined in the corresponding
642: package.
643:
644: 1.3.1. Roles involved in pkgsrc
645:
646: pkgsrc users
647:
648: The pkgsrc users are people who use the packages provided by pkgsrc.
649: Typically they are system administrators. The people using the software
650: that is inside the packages (maybe called "end users") are not covered by
651: the pkgsrc guide.
652:
653: There are two kinds of pkgsrc users: Some only want to install pre-built
654: binary packages. Others build the pkgsrc packages from source, either for
655: installing them directly or for building binary packages themselves. For
656: pkgsrc users Part I, "The pkgsrc user's guide" should provide all necessary
657: documentation.
658:
659: package maintainers
660:
661: A package maintainer creates packages as described in Part II, "The pkgsrc
662: developer's guide".
663:
664: infrastructure developers
665:
666: These people are involved in all those files that live in the mk/ directory
667: and below. Only these people should need to read through Part III, "The
668: pkgsrc infrastructure internals", though others might be curious, too.
669:
670: 1.4. Typography
671:
672: When giving examples for commands, shell prompts are used to show if the
673: command should/can be issued as root, or if "normal" user privileges are
1.115 ! sevan 674: sufficient. We use a # for root's shell prompt, a % for users' shell prompt,
! 675: assuming they use the C-shell or tcsh and a $ for bourne shell and derivatives.
1.1 dsieger 676:
677: Part I. The pkgsrc user's guide
678:
679: Table of Contents
680:
681: 2. Where to get pkgsrc and how to keep it up-to-date
682:
683: 2.1. Getting pkgsrc for the first time
684:
1.52 asau 685: 2.1.1. As tar archive
1.24 wiz 686: 2.1.2. Via anonymous CVS
1.1 dsieger 687:
688: 2.2. Keeping pkgsrc up-to-date
689:
690: 2.2.1. Via tar files
691: 2.2.2. Via CVS
692:
693: 3. Using pkgsrc on systems other than NetBSD
694:
695: 3.1. Binary distribution
696: 3.2. Bootstrapping pkgsrc
697: 3.3. Platform-specific notes
698:
699: 4. Using pkgsrc
700:
701: 4.1. Using binary packages
702:
703: 4.1.1. Finding binary packages
704: 4.1.2. Installing binary packages
705: 4.1.3. Deinstalling packages
706: 4.1.4. Getting information about installed packages
707: 4.1.5. Checking for security vulnerabilities in installed packages
708: 4.1.6. Finding if newer versions of your installed packages are in
709: pkgsrc
710: 4.1.7. Other administrative functions
711:
712: 4.2. Building packages from source
713:
714: 4.2.1. Requirements
715: 4.2.2. Fetching distfiles
716: 4.2.3. How to build and install
717:
718: 5. Configuring pkgsrc
719:
720: 5.1. General configuration
721: 5.2. Variables affecting the build process
1.9 rillig 722: 5.3. Variables affecting the installation process
1.4 rillig 723: 5.4. Selecting and configuring the compiler
1.1 dsieger 724:
1.4 rillig 725: 5.4.1. Selecting the compiler
726: 5.4.2. Additional flags to the compiler (CFLAGS)
727: 5.4.3. Additional flags to the linker (LDFLAGS)
1.1 dsieger 728:
1.4 rillig 729: 5.5. Developer/advanced settings
730: 5.6. Selecting Build Options
1.1 dsieger 731:
732: 6. Creating binary packages
733:
734: 6.1. Building a single binary package
735: 6.2. Settings for creation of binary packages
736:
1.6 rillig 737: 7. Creating binary packages for everything in pkgsrc (bulk builds)
738:
1.71 wiz 739: 7.1. Preparations
740: 7.2. Running a pbulk-style bulk build
1.6 rillig 741:
1.71 wiz 742: 7.2.1. Configuration
1.6 rillig 743:
1.71 wiz 744: 7.3. Requirements of a full bulk build
1.66 asau 745: 7.4. Creating a multiple CD-ROM packages collection
1.6 rillig 746:
1.66 asau 747: 7.4.1. Example of cdpack
1.6 rillig 748:
749: 8. Directory layout of the installed files
750:
751: 8.1. File system layout in ${LOCALBASE}
752: 8.2. File system layout in ${VARBASE}
753:
754: 9. Frequently Asked Questions
755:
756: 9.1. Are there any mailing lists for pkg-related discussion?
1.84 wiz 757: 9.2. Utilities for package management (pkgtools)
758: 9.3. How to use pkgsrc as non-root
759: 9.4. How to resume transfers when fetching distfiles?
760: 9.5. How can I install/use modular X.org from pkgsrc?
761: 9.6. How to fetch files from behind a firewall
762: 9.7. How to fetch files from HTTPS sites
763: 9.8. How do I tell make fetch to do passive FTP?
764: 9.9. How to fetch all distfiles at once
765: 9.10. What does "Don't know how to make /usr/share/tmac/tmac.andoc" mean?
766: 9.11. What does "Could not find bsd.own.mk" mean?
767: 9.12. Using 'sudo' with pkgsrc
768: 9.13. How do I change the location of configuration files?
769: 9.14. Automated security checks
770: 9.15. Why do some packages ignore my CFLAGS?
771: 9.16. A package does not build. What shall I do?
772: 9.17. What does "Makefile appears to contain unresolved cvs/rcs/??? merge
1.24 wiz 773: conflicts" mean?
1.1 dsieger 774:
775: Chapter 2. Where to get pkgsrc and how to keep it up-to-date
776:
777: Table of Contents
778:
779: 2.1. Getting pkgsrc for the first time
780:
1.52 asau 781: 2.1.1. As tar archive
1.24 wiz 782: 2.1.2. Via anonymous CVS
1.1 dsieger 783:
784: 2.2. Keeping pkgsrc up-to-date
785:
786: 2.2.1. Via tar files
787: 2.2.2. Via CVS
788:
789: Before you download and extract the files, you need to decide where you want to
790: extract them. When using pkgsrc as root user, pkgsrc is usually installed in /
791: usr/pkgsrc. You are though free to install the sources and binary packages
792: wherever you want in your filesystem, provided that the pathname does not
793: contain white-space or other characters that are interpreted specially by the
794: shell and some other programs. A safe bet is to use only letters, digits,
795: underscores and dashes.
796:
797: 2.1. Getting pkgsrc for the first time
798:
1.25 wiz 799: Before you download any pkgsrc files, you should decide whether you want the
1.1 dsieger 800: current branch or the stable branch. The latter is forked on a quarterly basis
801: from the current branch and only gets modified for security updates. The names
802: of the stable branches are built from the year and the quarter, for example
1.78 snj 803: 2014Q3.
1.1 dsieger 804:
805: The second step is to decide how you want to download pkgsrc. You can get it as
1.24 wiz 806: a tar file or via CVS. Both ways are described here.
1.1 dsieger 807:
1.52 asau 808: Note that tar archive contains CVS working copy. Thus you can switch to using
809: CVS at any later time.
1.1 dsieger 810:
1.52 asau 811: 2.1.1. As tar archive
812:
813: The primary download location for all pkgsrc files is http://ftp.NetBSD.org/pub
814: /pkgsrc/ or ftp://ftp.NetBSD.org/pub/pkgsrc/ (it points to the same location).
815: There are a number of subdirectories for different purposes, which are
1.1 dsieger 816: described in detail in Appendix C, Directory layout of the pkgsrc FTP server.
817:
1.52 asau 818: The tar archive for the current branch is in the directory current and is
819: called pkgsrc.tar.gz. It is autogenerated daily.
820:
821: To save download time we provide bzip2- and xz-compressed archives which are
822: published at pkgsrc.tar.bz2 and pkgsrc.tar.xz respectively.
823:
824: You can fetch the same files using FTP.
1.1 dsieger 825:
1.78 snj 826: The tar file for the stable branch 2014Q3 is in the directory pkgsrc-2014Q3 and
1.59 jnemeth 827: is also called pkgsrc.tar.gz.
1.1 dsieger 828:
1.12 weinem 829: To download a pkgsrc stable tarball, run:
830:
1.59 jnemeth 831: $ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-20xxQy/pkgsrc.tar.gz
1.12 weinem 832:
1.25 wiz 833: Where pkgsrc-20xxQy is the stable branch to be downloaded, for example, "
1.78 snj 834: pkgsrc-2014Q3".
1.12 weinem 835:
1.78 snj 836: If you prefer, you can also fetch it using "wget", "curl", or your web browser.
1.52 asau 837:
1.12 weinem 838: Then, extract it with:
839:
1.78 snj 840: $ tar -xzf pkgsrc.tar.gz -C /usr
1.12 weinem 841:
842: This will create the directory pkgsrc/ in /usr/ and all the package source will
843: be stored under /usr/pkgsrc/.
844:
845: To download pkgsrc-current, run:
846:
847: $ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz
1.1 dsieger 848:
1.24 wiz 849: 2.1.2. Via anonymous CVS
1.1 dsieger 850:
1.24 wiz 851: To fetch a specific pkgsrc stable branch, run:
1.1 dsieger 852:
1.40 wiz 853: $ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-20xxQy -P pkgsrc
1.1 dsieger 854:
1.25 wiz 855: Where pkgsrc-20xxQy is the stable branch to be checked out, for example, "
1.78 snj 856: pkgsrc-2014Q3"
1.13 weinem 857:
1.24 wiz 858: This will create the directory pkgsrc/ in your /usr/ directory and all the
859: package source will be stored under /usr/pkgsrc/.
860:
861: To fetch the pkgsrc current branch, run:
1.1 dsieger 862:
1.40 wiz 863: $ cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc
1.1 dsieger 864:
1.30 dholland 865: Refer to the list of available mirrors to choose a faster CVS mirror, if
866: needed.
1.1 dsieger 867:
1.24 wiz 868: If you get error messages from rsh, you need to set CVS_RSH variable. E.g.:
1.1 dsieger 869:
1.40 wiz 870: $ cd /usr && env CVS_RSH=ssh cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc
1.1 dsieger 871:
1.24 wiz 872: Refer to documentation on your command shell how to set CVS_RSH=ssh
873: permanently. For Bourne shells, you can set it in your .profile or better
874: globally in /etc/profile:
875:
876: # set CVS remote shell command
877: CVS_RSH=ssh
878: export CVS_RSH
1.12 weinem 879:
1.13 weinem 880: By default, CVS doesn't do things like most people would expect it to do. But
881: there is a way to convince CVS, by creating a file called .cvsrc in your home
1.12 weinem 882: directory and saving the following lines to it. This file will save you lots of
883: headache and some bug reports, so we strongly recommend it. You can find an
884: explanation of this file in the CVS documentation.
1.2 rillig 885:
886: # recommended CVS configuration file from the pkgsrc guide
1.40 wiz 887: cvs -q -z2
1.2 rillig 888: checkout -P
1.4 rillig 889: update -dP
890: diff -upN
1.2 rillig 891: rdiff -u
1.24 wiz 892: release -d
1.1 dsieger 893:
894: 2.2. Keeping pkgsrc up-to-date
895:
896: The preferred way to keep pkgsrc up-to-date is via CVS (which also works if you
897: have first installed it via a tar file). It saves bandwidth and hard disk
898: activity, compared to downloading the tar file again.
899:
900: 2.2.1. Via tar files
901:
902: Warning
903:
904: When updating from a tar file, you first need to completely remove the old
905: pkgsrc directory. Otherwise those files that have been removed from pkgsrc in
906: the mean time will not be removed on your local disk, resulting in
907: inconsistencies. When removing the old files, any changes that you have done to
908: the pkgsrc files will be lost after updating. Therefore updating via CVS is
909: strongly recommended.
910:
911: Note that by default the distfiles and the binary packages are saved in the
912: pkgsrc tree, so don't forget to rescue them before updating. You can also
1.78 snj 913: configure pkgsrc to store distfiles and packages in directories outside the
914: pkgsrc tree by setting the DISTDIR and PACKAGES variables. See Chapter 5,
915: Configuring pkgsrc for the details.
1.1 dsieger 916:
917: To update pkgsrc from a tar file, download the tar file as explained above.
918: Then, make sure that you have not made any changes to the files in the pkgsrc
919: directory. Remove the pkgsrc directory and extract the new tar file. Done.
920:
921: 2.2.2. Via CVS
922:
1.26 spz 923: To update pkgsrc via CVS, change to the pkgsrc directory and run cvs:
1.12 weinem 924:
1.26 spz 925: $ cd /usr/pkgsrc && cvs update -dP
926:
927: If you get error messages from rsh, you need to set CVS_RSH variable as
928: described above. E.g.:
929:
930: $ cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP
1.1 dsieger 931:
932: 2.2.2.1. Switching between different pkgsrc branches
933:
934: When updating pkgsrc, the CVS program keeps track of the branch you selected.
935: But if you, for whatever reason, want to switch from the stable branch to the
936: current one, you can do it by adding the option "-A" after the "update"
1.25 wiz 937: keyword. To switch from the current branch back to the stable branch, add the "
1.78 snj 938: -rpkgsrc-2014Q3" option.
1.1 dsieger 939:
940: 2.2.2.2. What happens to my changes when updating?
941:
942: When you update pkgsrc, the CVS program will only touch those files that are
943: registered in the CVS repository. That means that any packages that you created
944: on your own will stay unmodified. If you change files that are managed by CVS,
945: later updates will try to merge your changes with those that have been done by
946: others. See the CVS manual, chapter "update" for details.
947:
948: Chapter 3. Using pkgsrc on systems other than NetBSD
949:
950: Table of Contents
951:
952: 3.1. Binary distribution
953: 3.2. Bootstrapping pkgsrc
954: 3.3. Platform-specific notes
955:
956: 3.1. Binary distribution
957:
1.9 rillig 958: See Section 4.1, "Using binary packages".
1.1 dsieger 959:
960: 3.2. Bootstrapping pkgsrc
961:
1.44 asau 962: pkgsrc can be bootstrapped for use in two different modes: privileged and
963: unprivileged one. In unprivileged mode in contrast to privileged one all
1.45 asau 964: programs are installed under one particular user and cannot utilise privileged
1.44 asau 965: operations (packages don't create special users and all special file
966: permissions like setuid are ignored).
967:
1.1 dsieger 968: Installing the bootstrap kit from source should be as simple as:
969:
1.60 asau 970: # env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc
1.1 dsieger 971: # cd pkgsrc/bootstrap
972: # ./bootstrap
973:
974:
1.44 asau 975: To bootstrap in unprivileged mode pass "--unprivileged" flag to bootstrap
976:
977: By default, in privileged mode pkgsrc uses /usr/pkg for prefix where programs
978: will be installed in, and /var/db/pkg for the package database directory where
979: pkgsrc will do its internal bookkeeping, /var is used as varbase, where
980: packages install their persistent data. In unprivileged mode pkgsrc uses ~/pkg
981: for prefix, ~/pkg/var/db/pkg for the package database, and ~/pkg/var for
982: varbase.
983:
984: You can change default layout using command-line arguments. Run "./bootstrap
985: --help" to get details.
1.1 dsieger 986:
987: Note
988:
989: The bootstrap installs a bmake tool. Use this bmake when building via pkgsrc.
990: For examples in this guide, use bmake instead of "make".
991:
1.44 asau 992: Note
993:
994: It is possible to bootstrap multiple instances of pkgsrc using non-intersecting
995: directories. Use bmake corresponding to the installation you're working with to
996: build and install packages.
997:
1.1 dsieger 998: 3.3. Platform-specific notes
999:
1.111 sevan 1000: For platform-specific notes consult the README files found in the notes column
1001: of Table 1.1, "Platforms supported by pkgsrc"
1.1 dsieger 1002:
1003: Chapter 4. Using pkgsrc
1004:
1005: Table of Contents
1006:
1007: 4.1. Using binary packages
1008:
1009: 4.1.1. Finding binary packages
1010: 4.1.2. Installing binary packages
1011: 4.1.3. Deinstalling packages
1012: 4.1.4. Getting information about installed packages
1013: 4.1.5. Checking for security vulnerabilities in installed packages
1014: 4.1.6. Finding if newer versions of your installed packages are in pkgsrc
1015: 4.1.7. Other administrative functions
1016:
1017: 4.2. Building packages from source
1018:
1019: 4.2.1. Requirements
1020: 4.2.2. Fetching distfiles
1021: 4.2.3. How to build and install
1022:
1023: Basically, there are two ways of using pkgsrc. The first is to only install the
1024: package tools and to use binary packages that someone else has prepared. This
1025: is the "pkg" in pkgsrc. The second way is to install the "src" of pkgsrc, too.
1026: Then you are able to build your own packages, and you can still use binary
1027: packages from someone else.
1028:
1029: 4.1. Using binary packages
1030:
1.9 rillig 1031: On the ftp.NetBSD.org server and its mirrors, there are collections of binary
1032: packages, ready to be installed. These binary packages have been built using
1033: the default settings for the directories, that is:
1034:
1035: * /usr/pkg for LOCALBASE, where most of the files are installed,
1036:
1037: * /usr/pkg/etc for configuration files,
1038:
1039: * /var for VARBASE, where those files are installed that may change after
1040: installation.
1041:
1042: If you cannot use these directories for whatever reasons (maybe because you're
1043: not root), you cannot use these binary packages, but have to build the packages
1044: yourself, which is explained in Section 3.2, "Bootstrapping pkgsrc".
1.1 dsieger 1045:
1046: 4.1.1. Finding binary packages
1047:
1.5 weinem 1048: To install binary packages, you first need to know from where to get them. The
1049: first place where you should look is on the main pkgsrc FTP server in the
1050: directory /pub/pkgsrc/packages.
1051:
1052: This directory contains binary packages for multiple platforms. First, select
1053: your operating system. (Ignore the directories with version numbers attached to
1054: it, they just exist for legacy reasons.) Then, select your hardware
1055: architecture, and in the third step, the OS version and the "version" of
1.9 rillig 1056: pkgsrc.
1057:
1058: In this directory, you often find a file called bootstrap.tar.gz which contains
1059: the package management tools. If the file is missing, it is likely that your
1060: operating system already provides those tools. Download the file and extract it
1061: in the / directory. It will create the directories /usr/pkg (containing the
1062: tools for managing binary packages) and /var/db/pkg (the database of installed
1063: packages).
1.1 dsieger 1064:
1065: 4.1.2. Installing binary packages
1066:
1.85 wiz 1067: In the directory from the last section, there is a subdirectory called All/,
1.9 rillig 1068: which contains all the binary packages that are available for the platform,
1069: excluding those that may not be distributed via FTP or CDROM (depending on
1.24 wiz 1070: which medium you are using).
1.9 rillig 1071:
1072: To install packages directly from an FTP or HTTP server, run the following
1073: commands in a Bourne-compatible shell (be sure to su to root first):
1074:
1075: # PATH="/usr/pkg/sbin:$PATH"
1.85 wiz 1076: # PKG_PATH="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/OPSYS/ARCH/VERSIONS/All/"
1.9 rillig 1077: # export PATH PKG_PATH
1078:
1079: Instead of URLs, you can also use local paths, for example if you are
1080: installing from a set of CDROMs, DVDs or an NFS-mounted repository. If you want
1081: to install packages from multiple sources, you can separate them by a semicolon
1082: in PKG_PATH.
1083:
1084: After these preparations, installing a package is very easy:
1085:
1086: # pkg_add openoffice2
1087: # pkg_add kde-3.5.7
1088: # pkg_add ap2-php5-*
1.1 dsieger 1089:
1090: Note that any prerequisite packages needed to run the package in question will
1091: be installed, too, assuming they are present where you install from.
1092:
1.25 wiz 1093: Adding packages might install vulnerable packages. Thus you should run
1.24 wiz 1094: pkg_admin audit regularly, especially after installing new packages, and verify
1095: that the vulnerabilities are acceptable for your configuration.
1.1 dsieger 1096:
1097: After you've installed packages, be sure to have /usr/pkg/bin and /usr/pkg/sbin
1098: in your PATH so you can actually start the just installed program.
1099:
1100: 4.1.3. Deinstalling packages
1101:
1102: To deinstall a package, it does not matter whether it was installed from source
1103: code or from a binary package. The pkg_delete command does not know it anyway.
1104: To delete a package, you can just run pkg_delete package-name. The package name
1105: can be given with or without version number. Wildcards can also be used to
1106: deinstall a set of packages, for example *emacs*. Be sure to include them in
1107: quotes, so that the shell does not expand them before pkg_delete sees them.
1108:
1109: The -r option is very powerful: it removes all the packages that require the
1110: package in question and then removes the package itself. For example:
1111:
1112: # pkg_delete -r jpeg
1113:
1114:
1115: will remove jpeg and all the packages that used it; this allows upgrading the
1116: jpeg package.
1117:
1118: 4.1.4. Getting information about installed packages
1119:
1120: The pkg_info shows information about installed packages or binary package
1121: files.
1122:
1123: 4.1.5. Checking for security vulnerabilities in installed packages
1124:
1125: The NetBSD Security-Officer and Packages Groups maintain a list of known
1126: security vulnerabilities to packages which are (or have been) included in
1127: pkgsrc. The list is available from the NetBSD FTP site at ftp://ftp.NetBSD.org/
1128: pub/pkgsrc/distfiles/vulnerabilities.
1129:
1.23 jakllsch 1130: Through pkg_admin fetch-pkg-vulnerabilities, this list can be downloaded
1131: automatically, and a security audit of all packages installed on a system can
1132: take place.
1133:
1134: There are two components to auditing. The first step, pkg_admin
1135: fetch-pkg-vulnerabilities, is for downloading the list of vulnerabilities from
1136: the NetBSD FTP site. The second step, pkg_admin audit, checks to see if any of
1137: your installed packages are vulnerable. If a package is vulnerable, you will
1138: see output similar to the following:
1.1 dsieger 1139:
1140: Package samba-2.0.9 has a local-root-shell vulnerability, see
1141: http://www.samba.org/samba/whatsnew/macroexploit.html
1142:
1.23 jakllsch 1143: You may wish to have the vulnerabilities file downloaded daily so that it
1144: remains current. This may be done by adding an appropriate entry to the root
1145: users crontab(5) entry. For example the entry
1146:
1147: # download vulnerabilities file
1148: 0 3 * * * /usr/sbin/pkg_admin fetch-pkg-vulnerabilities >/dev/null 2>&1
1149:
1150:
1151: will update the vulnerability list every day at 3AM. You may wish to do this
1152: more often than once a day. In addition, you may wish to run the package audit
1153: from the daily security script. This may be accomplished by adding the
1154: following line to /etc/security.local:
1155:
1156: /usr/sbin/pkg_admin audit
1157:
1.1 dsieger 1158:
1159: 4.1.6. Finding if newer versions of your installed packages are in pkgsrc
1160:
1.12 weinem 1161: Install pkgtools/lintpkgsrc and run lintpkgsrc with the "-i" argument to check
1162: if your packages are up-to-date, e.g.
1.1 dsieger 1163:
1164: % lintpkgsrc -i
1165: ...
1166: Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
1167:
1168:
1169: You can then use make update to update the package on your system and rebuild
1170: any dependencies.
1171:
1172: 4.1.7. Other administrative functions
1173:
1174: The pkg_admin executes various administrative functions on the package system.
1175:
1176: 4.2. Building packages from source
1177:
1178: After obtaining pkgsrc, the pkgsrc directory now contains a set of packages,
1.25 wiz 1179: organized into categories. You can browse the online index of packages, or run
1.1 dsieger 1180: make readme from the pkgsrc directory to build local README.html files for all
1181: packages, viewable with any web browser such as www/lynx or www/firefox.
1182:
1183: The default prefix for installed packages is /usr/pkg. If you wish to change
1184: this, you should do so by setting LOCALBASE in mk.conf. You should not try to
1185: use multiple different LOCALBASE definitions on the same system (inside a
1186: chroot is an exception).
1187:
1188: The rest of this chapter assumes that the package is already in pkgsrc. If it
1189: is not, see Part II, "The pkgsrc developer's guide" for instructions how to
1190: create your own packages.
1191:
1192: 4.2.1. Requirements
1193:
1194: To build packages from source, you need a working C compiler. On NetBSD, you
1195: need to install the "comp" and the "text" distribution sets. If you want to
1196: build X11-related packages, the "xbase" and "xcomp" distribution sets are
1197: required, too.
1198:
1199: 4.2.2. Fetching distfiles
1200:
1201: The first step for building a package is downloading the distfiles (i.e. the
1202: unmodified source). If they have not yet been downloaded, pkgsrc will fetch
1203: them automatically.
1204:
1205: If you have all files that you need in the distfiles directory, you don't need
1206: to connect. If the distfiles are on CD-ROM, you can mount the CD-ROM on /cdrom
1207: and add:
1208:
1209: DISTDIR=/cdrom/pkgsrc/distfiles
1210:
1211: to your mk.conf.
1212:
1213: By default a list of distribution sites will be randomly intermixed to prevent
1214: huge load on servers which holding popular packages (for example,
1215: SourceForge.net mirrors). Thus, every time when you need to fetch yet another
1216: distfile all the mirrors will be tried in new (random) order. You can turn this
1217: feature off by setting MASTER_SORT_RANDOM=NO (for PKG_DEVELOPERs it's already
1218: disabled).
1219:
1220: You can overwrite some of the major distribution sites to fit to sites that are
1221: close to your own. By setting one or two variables you can modify the order in
1222: which the master sites are accessed. MASTER_SORT contains a whitespace
1223: delimited list of domain suffixes. MASTER_SORT_REGEX is even more flexible, it
1224: contains a whitespace delimited list of regular expressions. It has higher
1225: priority than MASTER_SORT. Have a look at pkgsrc/mk/defaults/mk.conf to find
1226: some examples. This may save some of your bandwidth and time.
1227:
1228: You can change these settings either in your shell's environment, or, if you
1.4 rillig 1229: want to keep the settings, by editing the mk.conf file, and adding the
1.1 dsieger 1230: definitions there.
1231:
1232: If a package depends on many other packages (such as meta-pkgs/kde3), the build
1233: process may alternate between periods of downloading source, and compiling. To
1234: ensure you have all the source downloaded initially you can run the command:
1235:
1236: % make fetch-list | sh
1237:
1238: which will output and run a set of shell commands to fetch the necessary files
1239: into the distfiles directory. You can also choose to download the files
1240: manually.
1241:
1242: 4.2.3. How to build and install
1243:
1244: Once the software has downloaded, any patches will be applied, then it will be
1245: compiled for you. This may take some time depending on your computer, and how
1246: many other packages the software depends on and their compile time.
1247:
1248: Note
1249:
1250: If using bootstrap or pkgsrc on a non-NetBSD system, use the pkgsrc bmake
1251: command instead of "make" in the examples in this guide.
1252:
1253: For example, type
1254:
1255: % cd misc/figlet
1256: % make
1257:
1258:
1259: at the shell prompt to build the various components of the package.
1260:
1261: The next stage is to actually install the newly compiled program onto your
1262: system. Do this by entering:
1263:
1264: % make install
1265:
1266:
1267: while you are still in the directory for whatever package you are installing.
1268:
1269: Installing the package on your system may require you to be root. However,
1270: pkgsrc has a just-in-time-su feature, which allows you to only become root for
1271: the actual installation step.
1272:
1273: That's it, the software should now be installed and setup for use. You can now
1274: enter:
1275:
1276: % make clean
1277:
1278:
1279: to remove the compiled files in the work directory, as you shouldn't need them
1280: any more. If other packages were also added to your system (dependencies) to
1281: allow your program to compile, you can tidy these up also with the command:
1282:
1283: % make clean-depends
1284:
1285:
1286: Taking the figlet utility as an example, we can install it on our system by
1287: building as shown in Appendix B, Build logs.
1288:
1289: The program is installed under the default root of the packages tree - /usr/
1290: pkg. Should this not conform to your tastes, set the LOCALBASE variable in your
1291: environment, and it will use that value as the root of your packages tree. So,
1292: to use /usr/local, set LOCALBASE=/usr/local in your environment. Please note
1293: that you should use a directory which is dedicated to packages and not shared
1294: with other programs (i.e., do not try and use LOCALBASE=/usr). Also, you should
1295: not try to add any of your own files or directories (such as src/, obj/, or
1296: pkgsrc/) below the LOCALBASE tree. This is to prevent possible conflicts
1297: between programs and other files installed by the package system and whatever
1298: else may have been installed there.
1299:
1.4 rillig 1300: Some packages look in mk.conf to alter some configuration options at build
1.1 dsieger 1301: time. Have a look at pkgsrc/mk/defaults/mk.conf to get an overview of what will
1302: be set there by default. Environment variables such as LOCALBASE can be set in
1.4 rillig 1303: mk.conf to save having to remember to set them each time you want to use
1.1 dsieger 1304: pkgsrc.
1305:
1306: Occasionally, people want to "look under the covers" to see what is going on
1307: when a package is building or being installed. This may be for debugging
1308: purposes, or out of simple curiosity. A number of utility values have been
1309: added to help with this.
1310:
1311: 1. If you invoke the make(1) command with PKG_DEBUG_LEVEL=2, then a huge
1312: amount of information will be displayed. For example,
1313:
1314: make patch PKG_DEBUG_LEVEL=2
1315:
1.25 wiz 1316: will show all the commands that are invoked, up to and including the "patch
1317: " stage.
1.1 dsieger 1318:
1319: 2. If you want to know the value of a certain make(1) definition, then the
1320: VARNAME definition should be used, in conjunction with the show-var target.
1321: e.g. to show the expansion of the make(1) variable LOCALBASE:
1322:
1323: % make show-var VARNAME=LOCALBASE
1324: /usr/pkg
1325: %
1326:
1327:
1328: If you want to install a binary package that you've either created yourself
1329: (see next section), that you put into pkgsrc/packages manually or that is
1330: located on a remote FTP server, you can use the "bin-install" target. This
1331: target will install a binary package - if available - via pkg_add(1), else do a
1332: make package. The list of remote FTP sites searched is kept in the variable
1333: BINPKG_SITES, which defaults to ftp.NetBSD.org. Any flags that should be added
1334: to pkg_add(1) can be put into BIN_INSTALL_FLAGS. See pkgsrc/mk/defaults/mk.conf
1335: for more details.
1336:
1337: A final word of warning: If you set up a system that has a non-standard setting
1338: for LOCALBASE, be sure to set that before any packages are installed, as you
1339: cannot use several directories for the same purpose. Doing so will result in
1340: pkgsrc not being able to properly detect your installed packages, and fail
1341: miserably. Note also that precompiled binary packages are usually built with
1342: the default LOCALBASE of /usr/pkg, and that you should not install any if you
1343: use a non-standard LOCALBASE.
1344:
1345: Chapter 5. Configuring pkgsrc
1346:
1347: Table of Contents
1348:
1349: 5.1. General configuration
1350: 5.2. Variables affecting the build process
1.9 rillig 1351: 5.3. Variables affecting the installation process
1.4 rillig 1352: 5.4. Selecting and configuring the compiler
1.1 dsieger 1353:
1.4 rillig 1354: 5.4.1. Selecting the compiler
1355: 5.4.2. Additional flags to the compiler (CFLAGS)
1356: 5.4.3. Additional flags to the linker (LDFLAGS)
1.1 dsieger 1357:
1.4 rillig 1358: 5.5. Developer/advanced settings
1359: 5.6. Selecting Build Options
1.1 dsieger 1360:
1361: The whole pkgsrc system is configured in a single file, usually called mk.conf.
1362: In which directory pkgsrc looks for that file depends on the installation. On
1363: NetBSD, when you use make(1) from the base system, it is in the directory /etc
1364: /. In all other cases the default location is ${PREFIX}/etc/, depending on
1365: where you told the bootstrap program to install the binary packages.
1366:
1367: The format of the configuration file is that of the usual BSD-style Makefiles.
1368: The whole pkgsrc configuration is done by setting variables in this file. Note
1369: that you can define all kinds of variables, and no special error checking (for
1.112 rillig 1370: example for spelling mistakes) takes place.
1.1 dsieger 1371:
1372: 5.1. General configuration
1373:
1.112 rillig 1374: The following variables apply to all pkgsrc packages. A complete list of the
1375: variables that can be configured by the user is available in mk/defaults/
1376: mk.conf, together with some comments that describe each variable's intent.
1.1 dsieger 1377:
1378: * LOCALBASE: Where packages will be installed. The default is /usr/pkg. Do
1379: not mix binary packages with different LOCALBASEs!
1380:
1381: * CROSSBASE: Where "cross" category packages will be installed. The default
1382: is ${LOCALBASE}/cross.
1383:
1.84 wiz 1384: * X11BASE: Where X11 is installed on the system. The default is /usr/X11R7.
1.1 dsieger 1385:
1386: * DISTDIR: Where to store the downloaded copies of the original source
1387: distributions used for building pkgsrc packages. The default is $
1388: {PKGSRCDIR}/distfiles.
1389:
1390: * PKG_DBDIR: Where the database about installed packages is stored. The
1391: default is /var/db/pkg.
1392:
1393: * MASTER_SITE_OVERRIDE: If set, override the packages' MASTER_SITES with this
1394: value.
1395:
1396: * MASTER_SITE_BACKUP: Backup location(s) for distribution files and patch
1397: files if not found locally or in ${MASTER_SITES} or ${PATCH_SITES}
1.26 spz 1398: respectively. The defaults are ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/$
1399: {DIST_SUBDIR}/ and ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/$
1.1 dsieger 1400: {DIST_SUBDIR}/.
1401:
1402: * BINPKG_SITES: List of sites carrying binary pkgs. rel and arch are replaced
1403: with OS release ("2.0", etc.) and architecture ("mipsel", etc.).
1404:
1.23 jakllsch 1405: * ACCEPTABLE_LICENSES: List of acceptable licenses. License names are
1406: case-sensitive. Whenever you try to build a package whose license is not in
1407: this list, you will get an error message. If the license condition is
1408: simple enough, the error message will include specific instructions on how
1409: to change this variable.
1.1 dsieger 1410:
1411: 5.2. Variables affecting the build process
1412:
1413: * PACKAGES: The top level directory for the binary packages. The default is $
1414: {PKGSRCDIR}/packages.
1415:
1416: * WRKOBJDIR: The top level directory where, if defined, the separate working
1417: directories will get created, and symbolically linked to from ${WRKDIR}
1418: (see below). This is useful for building packages on several architectures,
1419: then ${PKGSRCDIR} can be NFS-mounted while ${WRKOBJDIR} is local to every
1420: architecture. (It should be noted that PKGSRCDIR should not be set by the
1421: user ? it is an internal definition which refers to the root of the pkgsrc
1422: tree. It is possible to have many pkgsrc tree instances.)
1423:
1424: * LOCALPATCHES: Directory for local patches that aren't part of pkgsrc. See
1.6 rillig 1425: Section 11.3, "patches/*" for more information.
1.1 dsieger 1426:
1427: * PKGMAKECONF: Location of the mk.conf file used by a package's BSD-style
1428: Makefile. If this is not set, MAKECONF is set to /dev/null to avoid picking
1429: up settings used by builds in /usr/src.
1430:
1431: * DEPENDS_TARGET: By default, dependencies are only installed, and no binary
1.66 asau 1432: package is created for them. You can set this variable to package-install
1433: to automatically create binary packages after installing dependencies.
1.84 wiz 1434: Please note that the PKGSRC_KEEP_BIN_PKGS can be set to yes to preserve
1.80 wiz 1435: binary packages when using the install as well.
1.1 dsieger 1436:
1.9 rillig 1437: 5.3. Variables affecting the installation process
1.1 dsieger 1438:
1.107 jnemeth 1439: Packages have to support installation into a subdirectory of WRKDIR. This
1440: allows a package to be built, before the actual filesystem is touched. DESTDIR
1441: support exists in two variations:
1.4 rillig 1442:
1443: * Basic DESTDIR support means that the package installation and packaging is
1444: still run as root.
1445:
1446: * Full DESTDIR support can run the complete build, installation and packaging
1447: as normal user. Root privileges are only needed to add packages.
1448:
1449: With basic DESTDIR support, make clean needs to be run as root.
1450:
1.17 imil 1451: Considering the foo/bar package, DESTDIR full support can be tested using the
1452: following commands
1453:
1454: $ id
1455: uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
1456: $ mkdir $HOME/packages
1457: $ cd $PKGSRCDIR/foo/bar
1458:
1459: Verify DESTDIR full support, no root privileges should be needed
1460:
1.66 asau 1461: $ make stage-install
1.17 imil 1462:
1463: Create a package without root privileges
1464:
1.66 asau 1465: $ make PACKAGES=$HOME/packages package
1.17 imil 1466:
1467: For the following command, you must be able to gain root privileges using su(1)
1468:
1.66 asau 1469: $ make PACKAGES=$HOME/packages install
1.17 imil 1470:
1471: Then, as a simple user
1472:
1473: $ make clean
1474:
1.4 rillig 1475: 5.4. Selecting and configuring the compiler
1476:
1477: 5.4.1. Selecting the compiler
1.1 dsieger 1478:
1479: By default, pkgsrc will use GCC to build packages. This may be overridden by
1480: setting the following variables in /etc/mk.conf:
1481:
1482: PKGSRC_COMPILER:
1483:
1484: This is a list of values specifying the chain of compilers to invoke when
1485: building packages. Valid values are:
1486:
1.66 asau 1487: + ccc: Compaq C Compilers (Tru64)
1488:
1489: + ccache: compiler cache (chainable)
1490:
1491: + clang: Clang C and Objective-C compiler
1492:
1.42 asau 1493: + distcc: distributed C/C++ (chainable)
1.1 dsieger 1494:
1.66 asau 1495: + f2c: Fortran 77 to C compiler (chainable)
1496:
1497: + icc: Intel C++ Compiler (Linux)
1498:
1499: + ido: SGI IRIS Development Option cc (IRIX 5)
1.1 dsieger 1500:
1.42 asau 1501: + gcc: GNU C/C++ Compiler
1.1 dsieger 1502:
1.66 asau 1503: + hp: HP-UX C/aC++ compilers
1504:
1.42 asau 1505: + mipspro: Silicon Graphics, Inc. MIPSpro (n32/n64)
1.1 dsieger 1506:
1.66 asau 1507: + mipspro-ucode: Silicon Graphics, Inc. MIPSpro (o32)
1.1 dsieger 1508:
1.42 asau 1509: + sunpro: Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio
1.1 dsieger 1510:
1.66 asau 1511: + xlc: IBM's XL C/C++ compiler suite (Darwin/MacOSX)
1512:
1.1 dsieger 1513: The default is "gcc". You can use ccache and/or distcc with an appropriate
1514: PKGSRC_COMPILER setting, e.g. "ccache gcc". This variable should always be
1515: terminated with a value for a real compiler. Note that only one real
1516: compiler should be listed (e.g. "sunpro gcc" is not allowed).
1517:
1518: GCC_REQD:
1519:
1520: This specifies the minimum version of GCC to use when building packages. If
1521: the system GCC doesn't satisfy this requirement, then pkgsrc will build and
1522: install one of the GCC packages to use instead.
1523:
1.114 maya 1524: PYTHON_DEFAULT_VERSION:
1525:
1526: Specifies which version of python to use when several options are
1527: available.
1528:
1529: PKGSRC_FORTRAN:
1530:
1531: Specifies the fortran compiler to use. The default is g95, and gfortran is
1532: an alternative.
1533:
1534: GFORTRAN_VERSION:
1535:
1536: If PKGSRC_FORTRAN= gfortran is used, this option specifies which version to
1537: use.
1538:
1.4 rillig 1539: 5.4.2. Additional flags to the compiler (CFLAGS)
1.1 dsieger 1540:
1541: If you wish to set the CFLAGS variable, please make sure to use the += operator
1542: instead of the = operator:
1543:
1544: CFLAGS+= -your -flags
1545:
1546: Using CFLAGS= (i.e. without the "+") may lead to problems with packages that
1.16 jnemeth 1547: need to add their own flags. You may want to take a look at the devel/cpuflags
1.24 wiz 1548: package if you're interested in optimization specifically for the current CPU.
1.1 dsieger 1549:
1.4 rillig 1550: 5.4.3. Additional flags to the linker (LDFLAGS)
1.1 dsieger 1551:
1552: If you want to pass flags to the linker, both in the configure step and the
1553: build step, you can do this in two ways. Either set LDFLAGS or LIBS. The
1554: difference between the two is that LIBS will be appended to the command line,
1555: while LDFLAGS come earlier. LDFLAGS is pre-loaded with rpath settings for ELF
1556: machines depending on the setting of USE_IMAKE or the inclusion of mk/
1557: x11.buildlink3.mk. As with CFLAGS, if you do not wish to override these
1558: settings, use the += operator:
1559:
1560: LDFLAGS+= -your -linkerflags
1561:
1.4 rillig 1562: 5.5. Developer/advanced settings
1.1 dsieger 1563:
1564: * PKG_DEVELOPER: Run some sanity checks that package developers want:
1565:
1.42 asau 1566: + make sure patches apply with zero fuzz
1.1 dsieger 1567:
1.42 asau 1568: + run check-shlibs to see that all binaries will find their shared libs.
1.1 dsieger 1569:
1570: * PKG_DEBUG_LEVEL: The level of debugging output which is displayed whilst
1571: making and installing the package. The default value for this is 0, which
1572: will not display the commands as they are executed (normal, default, quiet
1573: operation); the value 1 will display all shell commands before their
1574: invocation, and the value 2 will display both the shell commands before
1.112 rillig 1575: their invocation, as well as their actual execution progress with set -x.
1.1 dsieger 1576:
1.4 rillig 1577: 5.6. Selecting Build Options
1.1 dsieger 1578:
1579: Some packages have build time options, usually to select between different
1580: dependencies, enable optional support for big dependencies or enable
1581: experimental features.
1582:
1583: To see which options, if any, a package supports, and which options are
1584: mutually exclusive, run make show-options, for example:
1585:
1586: The following options are supported by this package:
1587: ssl Enable SSL support.
1588: Exactly one of the following gecko options is required:
1589: firefox Use firefox as gecko rendering engine.
1590: mozilla Use mozilla as gecko rendering engine.
1591: At most one of the following database options may be selected:
1592: mysql Enable support for MySQL database.
1593: pgsql Enable support for PostgreSQL database.
1594:
1595: These options are enabled by default: firefox
1596: These options are currently enabled: mozilla ssl
1597:
1.4 rillig 1598: The following variables can be defined in mk.conf to select which options to
1599: enable for a package: PKG_DEFAULT_OPTIONS, which can be used to select or
1.1 dsieger 1600: disable options for all packages that support them, and PKG_OPTIONS.pkgbase,
1601: which can be used to select or disable options specifically for package pkgbase
1602: . Options listed in these variables are selected, options preceded by "-" are
1603: disabled. A few examples:
1604:
1.4 rillig 1605: $ grep "PKG.*OPTION" mk.conf
1.1 dsieger 1606: PKG_DEFAULT_OPTIONS= -arts -dvdread -esound
1607: PKG_OPTIONS.kdebase= debug -sasl
1608: PKG_OPTIONS.apache= suexec
1609:
1.11 rillig 1610: It is important to note that options that were specifically suggested by the
1.19 snj 1611: package maintainer must be explicitly removed if you do not wish to include the
1612: option. If you are unsure you can view the current state with make show-options
1613: .
1.11 rillig 1614:
1.1 dsieger 1615: The following settings are consulted in the order given, and the last setting
1616: that selects or disables an option is used:
1617:
1618: 1. the default options as suggested by the package maintainer
1619:
1620: 2. the options implied by the settings of legacy variables (see below)
1621:
1622: 3. PKG_DEFAULT_OPTIONS
1623:
1624: 4. PKG_OPTIONS.pkgbase
1625:
1626: For groups of mutually exclusive options, the last option selected is used, all
1627: others are automatically disabled. If an option of the group is explicitly
1628: disabled, the previously selected option, if any, is used. It is an error if no
1629: option from a required group of options is selected, and building the package
1630: will fail.
1631:
1632: Before the options framework was introduced, build options were selected by
1.4 rillig 1633: setting a variable (often named USE_FOO) in mk.conf for each option. To ease
1634: transition to the options framework for the user, these legacy variables are
1635: converted to the appropriate options setting (PKG_OPTIONS.pkgbase)
1636: automatically. A warning is issued to prompt the user to update mk.conf to use
1637: the options framework directly. Support for the legacy variables will be
1.1 dsieger 1638: removed eventually.
1639:
1640: Chapter 6. Creating binary packages
1641:
1642: Table of Contents
1643:
1644: 6.1. Building a single binary package
1645: 6.2. Settings for creation of binary packages
1646:
1647: 6.1. Building a single binary package
1648:
1649: Once you have built and installed a package, you can create a binary package
1650: which can be installed on another system with pkg_add(1). This saves having to
1651: build the same package on a group of hosts and wasting CPU time. It also
1652: provides a simple means for others to install your package, should you
1653: distribute it.
1654:
1655: To create a binary package, change into the appropriate directory in pkgsrc,
1656: and run make package:
1657:
1.112 rillig 1658: $ cd misc/figlet
1659: $ make package
1.1 dsieger 1660:
1661: This will build and install your package (if not already done), and then build
1662: a binary package from what was installed. You can then use the pkg_* tools to
1663: manipulate it. Binary packages are created by default in /usr/pkgsrc/packages,
1664: in the form of a gzipped tar file. See Section B.2, "Packaging figlet" for a
1665: continuation of the above misc/figlet example.
1666:
1.6 rillig 1667: See Chapter 21, Submitting and Committing for information on how to submit such
1.1 dsieger 1668: a binary package.
1669:
1670: 6.2. Settings for creation of binary packages
1671:
1.6 rillig 1672: See Section 17.17, "Other helpful targets".
1673:
1674: Chapter 7. Creating binary packages for everything in pkgsrc (bulk builds)
1675:
1676: Table of Contents
1677:
1.71 wiz 1678: 7.1. Preparations
1679: 7.2. Running a pbulk-style bulk build
1.6 rillig 1680:
1.71 wiz 1681: 7.2.1. Configuration
1.6 rillig 1682:
1.71 wiz 1683: 7.3. Requirements of a full bulk build
1.66 asau 1684: 7.4. Creating a multiple CD-ROM packages collection
1.6 rillig 1685:
1.66 asau 1686: 7.4.1. Example of cdpack
1.6 rillig 1687:
1.71 wiz 1688: For a number of reasons you may want to build binary packages for a large
1689: selected set of packages in pkgsrc or even for all pkgsrc packages. For
1690: instance, when you have multiple machines that should run the same software, it
1691: is wasted time if they all build their packages themselves from source. Or you
1692: may want to build a list of packages you want and check them before deploying
1693: onto production system. There is a way of getting a set of binary packages: The
1.112 rillig 1694: bulk build system, or pbulk ("p" stands for "parallel"). This chapter describes
1695: how to set it up.
1.71 wiz 1696:
1697: 7.1. Preparations
1698:
1699: First of all, you have to decide whether you build all packages or a limited
1700: set of them. Full bulk builds usually consume a lot more resources, both space
1701: and time, than builds for some practical sets of packages. There exists a
1702: number of particularly heavy packages that are not actually interesting to a
1703: wide audience. For a limited bulk builds you need to make a list of packages
1.112 rillig 1704: you want to build. Note that all their dependencies will be built, so you don't
1705: need to track them manually.
1.71 wiz 1706:
1707: During bulk builds various packages are installed and deinstalled in /usr/pkg
1708: (or whatever LOCALBASE is), so make sure that you don't need any package during
1.112 rillig 1709: the builds. Essentially, you should provide a fresh system, either a chroot
1.71 wiz 1710: environment or something even more restrictive, depending on what the operating
1711: system provides, or dedicate the whole physical machine. As a useful side
1712: effect this makes sure that bulk builds cannot break anything in your system.
1713: There have been numerous cases where certain packages tried to install files
1714: outside the LOCALBASE or wanted to edit some files in /etc.
1.6 rillig 1715:
1.71 wiz 1716: 7.2. Running a pbulk-style bulk build
1.6 rillig 1717:
1.15 rillig 1718: Running a pbulk-style bulk build works roughly as follows:
1719:
1720: * First, build the pbulk infrastructure in a fresh pkgsrc location.
1721:
1722: * Then, build each of the packages from a clean installation directory using
1723: the infrastructure.
1724:
1.71 wiz 1725: 7.2.1. Configuration
1.6 rillig 1726:
1.112 rillig 1727: To simplify configuration, we provide the helper script mk/pbulk/pbulk.sh.
1.6 rillig 1728:
1.68 asau 1729: In order to use it, prepare a clear system (real one, chroot environment, jail,
1730: zone, virtual machine). Configure network access to fetch distribution files.
1.112 rillig 1731: Create a user with name "pbulk".
1.68 asau 1732:
1733: Fetch and extract pkgsrc. Use a command like one of these:
1734:
1.72 wiz 1735: # (cd /usr && ftp -o - http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)
1736: # (cd /usr && fetch -o - http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz | tar -zxf-)
1737: # (cd /usr && cvs -Q -z3 -d anoncvs@anoncvs.NetBSD.org:/cvsroot get -P pkgsrc)
1.68 asau 1738:
1739: Or any other way that fits (e.g., curl, wget).
1740:
1741: Deploy and configure pbulk tools, e.g.:
1742:
1743: # sh pbulk.sh -n # native (NetBSD)
1744: # sh pbulk.sh -n -c mk.conf.frag # native, apply settings from given mk.conf fragment
1745: # sh pbulk.sh -nlc mk.conf.frag # native, apply settings, configure for limited build
1746:
1747: Note
1748:
1749: mk.conf.frag is a fragment of mk.conf that contains settings you want to apply
1750: to packages you build. For instance,
1751:
1.112 rillig 1752: PKG_DEVELOPER= yes # perform more checks
1753: X11_TYPE= modular # use pkgsrc X11
1754: SKIP_LICENSE_CHECK= yes # accept all licences (useful
1755: # when building all packages)
1.68 asau 1756:
1757: If configured for limited list, replace the list in /usr/pbulk/etc/pbulk.list
1.112 rillig 1758: with your list of packages, one per line without empty lines or comments. E.g.:
1.68 asau 1759:
1760: www/firefox
1761: mail/thunderbird
1762: misc/libreoffice4
1763:
1.69 asau 1764: At this point you can also review configuration in /usr/pbulk/etc and make
1765: final amendments, if wanted.
1766:
1.68 asau 1767: Start it:
1768:
1769: # /usr/pbulk/bin/bulkbuild
1770:
1771: After it finishes, you'll have /mnt filled with distribution files, binary
1772: packages, and reports, plain text summary in /mnt/bulklog/meta/report.txt
1773:
1774: Note
1775:
1776: The pbulk.sh script does not cover all possible use cases. While being ready to
1777: run, it serves as a good starting point to understand and build more complex
1778: setups. The script is kept small enough for better understanding.
1779:
1780: Note
1781:
1782: The pbulk.sh script supports running unprivileged bulk build and helps
1783: configuring distributed bulk builds.
1.15 rillig 1784:
1.71 wiz 1785: 7.3. Requirements of a full bulk build
1786:
1787: A complete bulk build requires lots of disk space. Some of the disk space can
1788: be read-only, some other must be writable. Some can be on remote filesystems
1789: (such as NFS) and some should be local. Some can be temporary filesystems,
1790: others must survive a sudden reboot.
1791:
1792: * 40 GB for the distfiles (read-write, remote, temporary)
1793:
1794: * 30 GB for the binary packages (read-write, remote, permanent)
1795:
1796: * 1 GB for the pkgsrc tree (read-only, remote, permanent)
1797:
1798: * 5 GB for LOCALBASE (read-write, local, temporary)
1799:
1800: * 10 GB for the log files (read-write, remote, permanent)
1801:
1802: * 5 GB for temporary files (read-write, local, temporary)
1803:
1.66 asau 1804: 7.4. Creating a multiple CD-ROM packages collection
1.1 dsieger 1805:
1806: After your pkgsrc bulk-build has completed, you may wish to create a CD-ROM set
1807: of the resulting binary packages to assist in installing packages on other
1808: machines. The pkgtools/cdpack package provides a simple tool for creating the
1809: ISO 9660 images. cdpack arranges the packages on the CD-ROMs in a way that
1810: keeps all the dependencies for a given package on the same CD as that package.
1811:
1.66 asau 1812: 7.4.1. Example of cdpack
1.1 dsieger 1813:
1814: Complete documentation for cdpack is found in the cdpack(1) man page. The
1815: following short example assumes that the binary packages are left in /usr/
1816: pkgsrc/packages/All and that sufficient disk space exists in /u2 to hold the
1817: ISO 9660 images.
1818:
1819: # mkdir /u2/images
1820: # pkg_add /usr/pkgsrc/packages/All/cdpack
1821: # cdpack /usr/pkgsrc/packages/All /u2/images
1822:
1823:
1824: If you wish to include a common set of files (COPYRIGHT, README, etc.) on each
1825: CD in the collection, then you need to create a directory which contains these
1826: files. e.g.
1827:
1828: # mkdir /tmp/common
1829: # echo "This is a README" > /tmp/common/README
1830: # echo "Another file" > /tmp/common/COPYING
1831: # mkdir /tmp/common/bin
1832: # echo "#!/bin/sh" > /tmp/common/bin/myscript
1833: # echo "echo Hello world" >> /tmp/common/bin/myscript
1834: # chmod 755 /tmp/common/bin/myscript
1835:
1836:
1837: Now create the images:
1838:
1839: # cdpack -x /tmp/common /usr/pkgsrc/packages/All /u2/images
1840:
1841: Each image will contain README, COPYING, and bin/myscript in their root
1842: directories.
1843:
1.6 rillig 1844: Chapter 8. Directory layout of the installed files
1.1 dsieger 1845:
1846: Table of Contents
1847:
1.6 rillig 1848: 8.1. File system layout in ${LOCALBASE}
1849: 8.2. File system layout in ${VARBASE}
1.1 dsieger 1850:
1851: The files that are installed by pkgsrc are organized in a way that is similar
1852: to what you find in the /usr directory of the base system. But some details are
1853: different. This is because pkgsrc initially came from FreeBSD and had adopted
1854: its file system hierarchy. Later it was largely influenced by NetBSD. But no
1855: matter which operating system you are using pkgsrc with, you can expect the
1856: same layout for pkgsrc.
1857:
1858: There are mainly four root directories for pkgsrc, which are all configurable
1859: in the bootstrap/bootstrap script. When pkgsrc has been installed as root, the
1860: default locations are:
1861:
1862: LOCALBASE= /usr/pkg
1863: PKG_SYSCONFBASE= /usr/pkg/etc
1864: VARBASE= /var
1865: PKG_DBDIR= /var/db/pkg
1866:
1867: In unprivileged mode (when pkgsrc has been installed as any other user), the
1868: default locations are:
1869:
1870: LOCALBASE= ${HOME}/pkg
1871: PKG_SYSCONFBASE= ${HOME}/pkg/etc
1872: VARBASE= ${HOME}/pkg/var
1873: PKG_DBDIR= ${HOME}/pkg/var/db/pkg
1874:
1875: What these four directories are for, and what they look like is explained
1876: below.
1877:
1.25 wiz 1878: * LOCALBASE corresponds to the /usr directory in the base system. It is the "
1879: main" directory where the files are installed and contains the well-known
1.1 dsieger 1880: subdirectories like bin, include, lib, share and sbin.
1881:
1882: * VARBASE corresponds to /var in the base system. Some programs (especially
1883: games, network daemons) need write access to it during normal operation.
1884:
1885: * PKG_SYSCONFDIR corresponds to /etc in the base system. It contains
1886: configuration files of the packages, as well as pkgsrc's mk.conf itself.
1887:
1.6 rillig 1888: 8.1. File system layout in ${LOCALBASE}
1.1 dsieger 1889:
1890: The following directories exist in a typical pkgsrc installation in $
1891: {LOCALBASE}.
1892:
1893: bin
1894:
1895: Contains executable programs that are intended to be directly used by the
1896: end user.
1897:
1898: emul
1899:
1900: Contains files for the emulation layers of various other operating systems,
1901: especially for NetBSD.
1902:
1903: etc (the usual location of ${PKG_SYSCONFDIR})
1904:
1905: Contains the configuration files.
1906:
1907: include
1908:
1909: Contains headers for the C and C++ programming languages.
1910:
1911: info
1912:
1913: Contains GNU info files of various packages.
1914:
1915: lib
1916:
1917: Contains shared and static libraries.
1918:
1919: libdata
1920:
1921: Contains data files that don't change after installation. Other data files
1922: belong into ${VARBASE}.
1923:
1924: libexec
1925:
1926: Contains programs that are not intended to be used by end users, such as
1927: helper programs or network daemons.
1928:
1929: libexec/cgi-bin
1930:
1931: Contains programs that are intended to be executed as CGI scripts by a web
1932: server.
1933:
1934: man (the usual value of ${PKGMANDIR})
1935:
1936: Contains brief documentation in form of manual pages.
1937:
1938: sbin
1939:
1940: Contains programs that are intended to be used only by the super-user.
1941:
1942: share
1943:
1944: Contains platform-independent data files that don't change after
1945: installation.
1946:
1947: share/doc
1948:
1949: Contains documentation files provided by the packages.
1950:
1951: share/examples
1952:
1953: Contains example files provided by the packages. Among others, the original
1954: configuration files are saved here and copied to ${PKG_SYSCONFDIR} during
1955: installation.
1956:
1957: share/examples/rc.d
1958:
1959: Contains the original files for rc.d scripts.
1960:
1961: var (the usual location of ${VARBASE})
1962:
1963: Contains files that may be modified after installation.
1964:
1.6 rillig 1965: 8.2. File system layout in ${VARBASE}
1.1 dsieger 1966:
1967: db/pkg (the usual location of ${PKG_DBDIR})
1968:
1969: Contains information about the currently installed packages.
1970:
1971: games
1972:
1973: Contains highscore files.
1974:
1975: log
1976:
1977: Contains log files.
1978:
1979: run
1980:
1981: Contains informational files about daemons that are currently running.
1982:
1.6 rillig 1983: Chapter 9. Frequently Asked Questions
1.1 dsieger 1984:
1985: Table of Contents
1986:
1.6 rillig 1987: 9.1. Are there any mailing lists for pkg-related discussion?
1.84 wiz 1988: 9.2. Utilities for package management (pkgtools)
1989: 9.3. How to use pkgsrc as non-root
1990: 9.4. How to resume transfers when fetching distfiles?
1991: 9.5. How can I install/use modular X.org from pkgsrc?
1992: 9.6. How to fetch files from behind a firewall
1993: 9.7. How to fetch files from HTTPS sites
1994: 9.8. How do I tell make fetch to do passive FTP?
1995: 9.9. How to fetch all distfiles at once
1996: 9.10. What does "Don't know how to make /usr/share/tmac/tmac.andoc" mean?
1997: 9.11. What does "Could not find bsd.own.mk" mean?
1998: 9.12. Using 'sudo' with pkgsrc
1999: 9.13. How do I change the location of configuration files?
2000: 9.14. Automated security checks
2001: 9.15. Why do some packages ignore my CFLAGS?
2002: 9.16. A package does not build. What shall I do?
2003: 9.17. What does "Makefile appears to contain unresolved cvs/rcs/??? merge
1.24 wiz 2004: conflicts" mean?
1.1 dsieger 2005:
2006: This section contains hints, tips & tricks on special things in pkgsrc that we
2007: didn't find a better place for in the previous chapters, and it contains items
2008: for both pkgsrc users and developers.
2009:
1.6 rillig 2010: 9.1. Are there any mailing lists for pkg-related discussion?
1.1 dsieger 2011:
2012: The following mailing lists may be of interest to pkgsrc users:
2013:
2014: * pkgsrc-users: This is a general purpose list for most issues regarding
2015: pkgsrc, regardless of platform, e.g. soliciting user help for pkgsrc
2016: configuration, unexpected build failures, using particular packages,
2017: upgrading pkgsrc installations, questions regarding the pkgsrc release
2018: branches, etc. General announcements or proposals for changes that impact
2019: the pkgsrc user community, e.g. major infrastructure changes, new features,
2020: package removals, etc., may also be posted.
2021:
2022: * pkgsrc-bulk: A list where the results of pkgsrc bulk builds are sent and
2023: discussed.
2024:
2025: * pkgsrc-changes: This list is for those who are interested in getting a
2026: commit message for every change committed to pkgsrc. It is also available
2027: in digest form, meaning one daily message containing all commit messages
2028: for changes to the package source tree in that 24 hour period.
2029:
2030: To subscribe, do:
2031:
2032: % echo subscribe listname | mail majordomo@NetBSD.org
2033:
2034: Archives for all these mailing lists are available from http://
2035: mail-index.NetBSD.org/.
2036:
1.84 wiz 2037: 9.2. Utilities for package management (pkgtools)
1.1 dsieger 2038:
2039: The directory pkgsrc/pkgtools contains a number of useful utilities for both
2040: users and developers of pkgsrc. This section attempts only to make the reader
2041: aware of the utilities and when they might be useful, and not to duplicate the
2042: documentation that comes with each package.
2043:
2044: Utilities used by pkgsrc (automatically installed when needed):
2045:
2046: * pkgtools/x11-links: Symlinks for use by buildlink.
2047:
2048: OS tool augmentation (automatically installed when needed):
2049:
2050: * pkgtools/digest: Calculates various kinds of checksums (including SHA1).
2051:
2052: * pkgtools/libnbcompat: Compatibility library for pkgsrc tools.
2053:
2054: * pkgtools/mtree: Installed on non-BSD systems due to lack of native mtree.
2055:
2056: * pkgtools/pkg_install: Up-to-date replacement for /usr/sbin/pkg_install, or
2057: for use on operating systems where pkg_install is not present.
2058:
2059: Utilities used by pkgsrc (not automatically installed):
2060:
2061: * pkgtools/pkg_tarup: Create a binary package from an already-installed
2062: package. Used by make replace to save the old package.
2063:
2064: * pkgtools/dfdisk: Adds extra functionality to pkgsrc, allowing it to fetch
2065: distfiles from multiple locations. It currently supports the following
2066: methods: multiple CD-ROMs and network FTP/HTTP connections.
2067:
2068: * devel/cpuflags: Determine the best compiler flags to optimise code for your
1.24 wiz 2069: current CPU and compiler.
1.1 dsieger 2070:
2071: Utilities for keeping track of installed packages, being up to date, etc:
2072:
1.65 wiz 2073: * pkgtools/pkgin: A package update tool similar to apt(1). Download, install,
2074: and upgrade binary packages easily.
2075:
1.1 dsieger 2076: * pkgtools/pkg_chk: Reports on packages whose installed versions do not match
2077: the latest pkgsrc entries.
2078:
2079: * pkgtools/pkgdep: Makes dependency graphs of packages, to aid in choosing a
2080: strategy for updating.
2081:
2082: * pkgtools/pkgdepgraph: Makes graphs from the output of pkgtools/pkgdep (uses
2083: graphviz).
2084:
1.12 weinem 2085: * pkgtools/pkglint: The pkglint(1) program checks a pkgsrc entry for errors.
2086:
2087: * pkgtools/lintpkgsrc: The lintpkgsrc(1) program does various checks on the
2088: complete pkgsrc system.
1.1 dsieger 2089:
2090: * pkgtools/pkgsurvey: Report what packages you have installed.
2091:
2092: Utilities for people maintaining or creating individual packages:
2093:
2094: * pkgtools/pkgdiff: Automate making and maintaining patches for a package
2095: (includes pkgdiff, pkgvi, mkpatches, etc.).
2096:
1.65 wiz 2097: * pkgtools/url2pkg: Aids in converting to pkgsrc.
1.1 dsieger 2098:
2099: Utilities for people maintaining pkgsrc (or: more obscure pkg utilities)
2100:
2101: * pkgtools/pkg_comp: Build packages in a chrooted area.
2102:
2103: * pkgtools/libkver: Spoof kernel version for chrooted cross builds.
2104:
1.84 wiz 2105: 9.3. How to use pkgsrc as non-root
1.1 dsieger 2106:
1.108 rillig 2107: To install packages from source as a non-root user, download pkgsrc as
2108: described in Chapter 2, Where to get pkgsrc and how to keep it up-to-date, cd
2109: into that directory and run the command ./bootstrap/bootstrap --unprivileged.
2110:
2111: This will install the binary part of pkgsrc to ~/pkg and put the pkgsrc
2112: configuration mk.conf into ~/pkg/etc.
2113:
2114: For more details, see mk/unprivileged.mk.
1.1 dsieger 2115:
1.84 wiz 2116: 9.4. How to resume transfers when fetching distfiles?
1.1 dsieger 2117:
2118: By default, resuming transfers in pkgsrc is disabled, but you can enable this
1.4 rillig 2119: feature by adding the option PKG_RESUME_TRANSFERS=YES into mk.conf. If, during
2120: a fetch step, an incomplete distfile is found, pkgsrc will try to resume it.
1.1 dsieger 2121:
1.61 wiz 2122: You can also use a different program than the platform default program by
2123: changing the FETCH_USING variable. You can specify the program by using of ftp,
2124: fetch, wget or curl. Alternatively, fetching can be disabled by using the value
2125: manual. A value of custom disables the system defaults and dependency tracking
2126: for the fetch program. In that case you have to provide FETCH_CMD,
2127: FETCH_BEFORE_ARGS, FETCH_RESUME_ARGS, FETCH_OUTPUT_ARGS, FETCH_AFTER_ARGS.
1.1 dsieger 2128:
1.16 jnemeth 2129: For example, if you want to use wget to download, you'll have to use something
2130: like:
1.1 dsieger 2131:
1.16 jnemeth 2132: FETCH_USING= wget
1.1 dsieger 2133:
1.84 wiz 2134: 9.5. How can I install/use modular X.org from pkgsrc?
1.1 dsieger 2135:
1.4 rillig 2136: If you want to use modular X.org from pkgsrc instead of your system's own X11
2137: (/usr/X11R6, /usr/openwin, ...) you will have to add the following line into
1.1 dsieger 2138: mk.conf:
2139:
1.4 rillig 2140: X11_TYPE=modular
1.1 dsieger 2141:
2142: Note
2143:
1.4 rillig 2144: The DragonFly operating system defaults to using modular X.org from pkgsrc.
1.1 dsieger 2145:
1.84 wiz 2146: 9.6. How to fetch files from behind a firewall
1.1 dsieger 2147:
2148: If you are sitting behind a firewall which does not allow direct connections to
2149: Internet hosts (i.e. non-NAT), you may specify the relevant proxy hosts. This
2150: is done using an environment variable in the form of a URL, e.g. in Amdahl, the
2151: machine "orpheus.amdahl.com" is one of the firewalls, and it uses port 80 as
2152: the proxy port number. So the proxy environment variables are:
2153:
2154: ftp_proxy=ftp://orpheus.amdahl.com:80/
2155: http_proxy=http://orpheus.amdahl.com:80/
2156:
1.84 wiz 2157: 9.7. How to fetch files from HTTPS sites
1.65 wiz 2158:
2159: Some fetch tools are not prepared to support HTTPS by default (for example, the
2160: one in NetBSD 6.0), or the one installed by the pkgsrc bootstrap (to avoid an
2161: openssl dependency that low in the dependency graph).
2162:
2163: Usually you won't notice, because distribution files are mirrored weekly to "
2164: ftp.NetBSD.org", but that might not be often enough if you are following
2165: pkgsrc-current. In that case, set FETCH_USING in your mk.conf file to "curl" or
2166: "wget", which are both compiled with HTTPS support by default. Of course, these
2167: tools need to be installed before you can use them this way.
2168:
1.84 wiz 2169: 9.8. How do I tell make fetch to do passive FTP?
1.1 dsieger 2170:
2171: This depends on which utility is used to retrieve distfiles. From bsd.pkg.mk,
2172: FETCH_CMD is assigned the first available command from the following list:
2173:
2174: * ${LOCALBASE}/bin/ftp
2175:
2176: * /usr/bin/ftp
2177:
2178: On a default NetBSD installation, this will be /usr/bin/ftp, which
2179: automatically tries passive connections first, and falls back to active
2180: connections if the server refuses to do passive. For the other tools, add the
1.4 rillig 2181: following to your mk.conf file: PASSIVE_FETCH=1.
1.1 dsieger 2182:
2183: Having that option present will prevent /usr/bin/ftp from falling back to
2184: active transfers.
2185:
1.84 wiz 2186: 9.9. How to fetch all distfiles at once
1.1 dsieger 2187:
2188: You would like to download all the distfiles in a single batch from work or
2189: university, where you can't run a make fetch. There is an archive of distfiles
2190: on ftp.NetBSD.org, but downloading the entire directory may not be appropriate.
2191:
2192: The answer here is to do a make fetch-list in /usr/pkgsrc or one of its
2193: subdirectories, carry the resulting list to your machine at work/school and use
2194: it there. If you don't have a NetBSD-compatible ftp(1) (like tnftp) at work,
2195: don't forget to set FETCH_CMD to something that fetches a URL:
2196:
2197: At home:
2198:
2199: % cd /usr/pkgsrc
2200: % make fetch-list FETCH_CMD=wget DISTDIR=/tmp/distfiles >/tmp/fetch.sh
2201: % scp /tmp/fetch.sh work:/tmp
2202:
2203: At work:
2204:
2205: % sh /tmp/fetch.sh
2206:
2207: then tar up /tmp/distfiles and take it home.
2208:
2209: If you have a machine running NetBSD, and you want to get all distfiles (even
2210: ones that aren't for your machine architecture), you can do so by using the
2211: above-mentioned make fetch-list approach, or fetch the distfiles directly by
2212: running:
2213:
2214: % make mirror-distfiles
2215:
2216: If you even decide to ignore NO_{SRC,BIN}_ON_{FTP,CDROM}, then you can get
2217: everything by running:
2218:
2219: % make fetch NO_SKIP=yes
2220:
1.84 wiz 2221: 9.10. What does "Don't know how to make /usr/share/tmac/tmac.andoc" mean?
1.1 dsieger 2222:
2223: When compiling the pkgtools/pkg_install package, you get the error from make
2224: that it doesn't know how to make /usr/share/tmac/tmac.andoc? This indicates
2225: that you don't have installed the "text" set (nroff, ...) from the NetBSD base
2226: distribution on your machine. It is recommended to do that to format man pages.
2227:
2228: In the case of the pkgtools/pkg_install package, you can get away with setting
1.4 rillig 2229: NOMAN=YES either in the environment or in mk.conf.
1.1 dsieger 2230:
1.84 wiz 2231: 9.11. What does "Could not find bsd.own.mk" mean?
1.1 dsieger 2232:
2233: You didn't install the compiler set, comp.tgz, when you installed your NetBSD
2234: machine. Please get and install it, by extracting it in /:
2235:
2236: # cd /
2237: # tar --unlink -zxvpf .../comp.tgz
2238:
2239: comp.tgz is part of every NetBSD release. Get the one that corresponds to your
2240: release (determine via uname -r).
2241:
1.84 wiz 2242: 9.12. Using 'sudo' with pkgsrc
1.1 dsieger 2243:
2244: When installing packages as non-root user and using the just-in-time su(1)
2245: feature of pkgsrc, it can become annoying to type in the root password for each
2246: required package installed. To avoid this, the sudo package can be used, which
2247: does password caching over a limited time. To use it, install sudo (either as
1.4 rillig 2248: binary package or from security/sudo) and then put the following into your
2249: mk.conf, somewhere after the definition of the LOCALBASE variable:
1.1 dsieger 2250:
2251: .if exists(${LOCALBASE}/bin/sudo)
2252: SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
2253: .endif
2254:
1.84 wiz 2255: 9.13. How do I change the location of configuration files?
1.1 dsieger 2256:
2257: As the system administrator, you can choose where configuration files are
2258: installed. The default settings make all these files go into ${PREFIX}/etc or
2259: some of its subdirectories; this may be suboptimal depending on your
2260: expectations (e.g., a read-only, NFS-exported PREFIX with a need of per-machine
2261: configuration of the provided packages).
2262:
2263: In order to change the defaults, you can modify the PKG_SYSCONFBASE variable
1.4 rillig 2264: (in mk.conf) to point to your preferred configuration directory; some common
2265: examples include /etc or /etc/pkg.
1.1 dsieger 2266:
2267: Furthermore, you can change this value on a per-package basis by setting the
2268: PKG_SYSCONFDIR.${PKG_SYSCONFVAR} variable. PKG_SYSCONFVAR's value usually
2269: matches the name of the package you would like to modify, that is, the contents
2270: of PKGBASE.
2271:
2272: Note that after changing these settings, you must rebuild and reinstall any
2273: affected packages.
2274:
1.84 wiz 2275: 9.14. Automated security checks
1.1 dsieger 2276:
2277: Please be aware that there can often be bugs in third-party software, and some
2278: of these bugs can leave a machine vulnerable to exploitation by attackers. In
2279: an effort to lessen the exposure, the NetBSD packages team maintains a database
2280: of known-exploits to packages which have at one time been included in pkgsrc.
2281: The database can be downloaded automatically, and a security audit of all
1.14 jmcneill 2282: packages installed on a system can take place. To do this, refer to the
2283: following two tools (installed as part of the pkgtools/pkg_install package):
1.1 dsieger 2284:
1.21 snj 2285: 1. pkg_admin fetch-pkg-vulnerabilities, an easy way to download a list of the
2286: security vulnerabilities information. This list is kept up to date by the
1.26 spz 2287: pkgsrc security team, and is distributed from the NetBSD ftp server:
1.1 dsieger 2288:
1.26 spz 2289: ftp://ftp.NetBSD.org/pkgsrc/distfiles/pkg-vulnerabilities
1.1 dsieger 2290:
1.21 snj 2291: 2. pkg_admin audit, an easy way to audit the current machine, checking each
1.24 wiz 2292: known vulnerability. If a vulnerable package is installed, it will be shown
2293: by output to stdout, including a description of the type of vulnerability,
2294: and a URL containing more information.
1.1 dsieger 2295:
1.14 jmcneill 2296: Use of these tools is strongly recommended! After "pkg_install" is installed,
2297: please read the package's message, which you can get by running pkg_info -D
2298: pkg_install.
1.1 dsieger 2299:
2300: If this package is installed, pkgsrc builds will use it to perform a security
2301: check before building any package. See Section 5.2, "Variables affecting the
2302: build process" for ways to control this check.
2303:
1.84 wiz 2304: 9.15. Why do some packages ignore my CFLAGS?
1.1 dsieger 2305:
2306: When you add your own preferences to the CFLAGS variable in your mk.conf, these
2307: flags are passed in environment variables to the ./configure scripts and to
2308: make(1). Some package authors ignore the CFLAGS from the environment variable
2309: by overriding them in the Makefiles of their package.
2310:
2311: Currently there is no solution to this problem. If you really need the package
2312: to use your CFLAGS you should run make patch in the package directory and then
2313: inspect any Makefile and Makefile.in for whether they define CFLAGS explicitly.
2314: Usually you can remove these lines. But be aware that some "smart" programmers
2315: write so bad code that it only works for the specific combination of CFLAGS
2316: they have chosen.
2317:
1.84 wiz 2318: 9.16. A package does not build. What shall I do?
1.1 dsieger 2319:
2320: 1. Make sure that your copy of pkgsrc is consistent. A case that occurs often
2321: is that people only update pkgsrc in parts, because of performance reasons.
2322: Since pkgsrc is one large system, not a collection of many small systems,
2323: there are sometimes changes that only work when the whole pkgsrc tree is
2324: updated.
2325:
1.25 wiz 2326: 2. Make sure that you don't have any CVS conflicts. Search for "<<<<<<" or "
2327: >>>>>>" in all your pkgsrc files.
1.1 dsieger 2328:
1.25 wiz 2329: 3. Make sure that you don't have old copies of the packages extracted. Run
1.1 dsieger 2330: make clean clean-depends to verify this.
2331:
1.108 rillig 2332: 4. If you are a package developer who wants to invest some work, have a look
2333: at Chapter 19, Making your package work.
2334:
2335: 5. If the problem still exists, write a mail to the pkgsrc-users mailing list.
1.1 dsieger 2336:
1.84 wiz 2337: 9.17. What does "Makefile appears to contain unresolved cvs/rcs/??? merge
1.1 dsieger 2338: conflicts" mean?
2339:
2340: You have modified a file from pkgsrc, and someone else has modified that same
2341: file afterwards in the CVS repository. Both changes are in the same region of
2342: the file, so when you updated pkgsrc, the cvs command marked the conflicting
2343: changes in the file. Because of these markers, the file is no longer a valid
2344: Makefile.
2345:
2346: Have a look at that file, and if you don't need your local changes anymore, you
2347: can remove that file and run cvs -q update -dP in that directory to download
2348: the current version.
2349:
2350: Part II. The pkgsrc developer's guide
2351:
2352: This part of the book deals with creating and modifying packages. It starts
2353: with a "HOWTO"-like guide on creating a new package. The remaining chapters are
2354: more like a reference manual for pkgsrc.
2355:
2356: Table of Contents
2357:
1.6 rillig 2358: 10. Creating a new pkgsrc package from scratch
1.1 dsieger 2359:
1.6 rillig 2360: 10.1. Common types of packages
1.1 dsieger 2361:
1.6 rillig 2362: 10.1.1. Perl modules
1.66 asau 2363: 10.1.2. KDE3 applications
1.17 imil 2364: 10.1.3. Python modules and programs
1.1 dsieger 2365:
1.6 rillig 2366: 10.2. Examples
1.1 dsieger 2367:
1.6 rillig 2368: 10.2.1. How the www/nvu package came into pkgsrc
1.1 dsieger 2369:
1.6 rillig 2370: 11. Package components - files, directories and contents
1.1 dsieger 2371:
1.6 rillig 2372: 11.1. Makefile
2373: 11.2. distinfo
2374: 11.3. patches/*
1.1 dsieger 2375:
1.6 rillig 2376: 11.3.1. Structure of a single patch file
2377: 11.3.2. Creating patch files
2378: 11.3.3. Sources where the patch files come from
2379: 11.3.4. Patching guidelines
2380: 11.3.5. Feedback to the author
1.1 dsieger 2381:
1.6 rillig 2382: 11.4. Other mandatory files
2383: 11.5. Optional files
1.1 dsieger 2384:
1.6 rillig 2385: 11.5.1. Files affecting the binary package
2386: 11.5.2. Files affecting the build process
2387: 11.5.3. Files affecting nothing at all
1.1 dsieger 2388:
1.6 rillig 2389: 11.6. work*
2390: 11.7. files/*
1.1 dsieger 2391:
1.6 rillig 2392: 12. Programming in Makefiles
1.1 dsieger 2393:
1.6 rillig 2394: 12.1. Caveats
2395: 12.2. Makefile variables
1.1 dsieger 2396:
1.6 rillig 2397: 12.2.1. Naming conventions
1.1 dsieger 2398:
1.6 rillig 2399: 12.3. Code snippets
1.1 dsieger 2400:
1.6 rillig 2401: 12.3.1. Adding things to a list
1.108 rillig 2402: 12.3.2. Echoing a string exacty as-is
2403: 12.3.3. Passing CFLAGS to GNU configure scripts
2404: 12.3.4. Handling possibly empty variables
1.1 dsieger 2405:
1.6 rillig 2406: 13. PLIST issues
1.1 dsieger 2407:
1.6 rillig 2408: 13.1. RCS ID
2409: 13.2. Semi-automatic PLIST generation
2410: 13.3. Tweaking output of make print-PLIST
2411: 13.4. Variable substitution in PLIST
2412: 13.5. Man page compression
2413: 13.6. Changing PLIST source with PLIST_SRC
2414: 13.7. Platform-specific and differing PLISTs
1.86 wiz 2415: 13.8. Build-specific PLISTs
2416: 13.9. Sharing directories between packages
1.1 dsieger 2417:
1.6 rillig 2418: 14. Buildlink methodology
1.1 dsieger 2419:
1.6 rillig 2420: 14.1. Converting packages to use buildlink3
2421: 14.2. Writing buildlink3.mk files
1.1 dsieger 2422:
1.6 rillig 2423: 14.2.1. Anatomy of a buildlink3.mk file
1.27 wiz 2424: 14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and BUILDLINK_ABI_DEPENDS.
2425: pkg in buildlink3.mk files
1.1 dsieger 2426:
1.6 rillig 2427: 14.3. Writing builtin.mk files
1.1 dsieger 2428:
1.6 rillig 2429: 14.3.1. Anatomy of a builtin.mk file
2430: 14.3.2. Global preferences for native or pkgsrc software
1.1 dsieger 2431:
1.6 rillig 2432: 15. The pkginstall framework
1.1 dsieger 2433:
1.6 rillig 2434: 15.1. Files and directories outside the installation prefix
1.1 dsieger 2435:
1.6 rillig 2436: 15.1.1. Directory manipulation
2437: 15.1.2. File manipulation
1.1 dsieger 2438:
1.6 rillig 2439: 15.2. Configuration files
1.1 dsieger 2440:
1.6 rillig 2441: 15.2.1. How PKG_SYSCONFDIR is set
2442: 15.2.2. Telling the software where configuration files are
2443: 15.2.3. Patching installations
2444: 15.2.4. Disabling handling of configuration files
1.1 dsieger 2445:
1.6 rillig 2446: 15.3. System startup scripts
1.1 dsieger 2447:
1.6 rillig 2448: 15.3.1. Disabling handling of system startup scripts
1.1 dsieger 2449:
1.6 rillig 2450: 15.4. System users and groups
2451: 15.5. System shells
1.1 dsieger 2452:
1.6 rillig 2453: 15.5.1. Disabling shell registration
1.1 dsieger 2454:
1.6 rillig 2455: 15.6. Fonts
1.1 dsieger 2456:
1.6 rillig 2457: 15.6.1. Disabling automatic update of the fonts databases
1.1 dsieger 2458:
1.6 rillig 2459: 16. Options handling
1.1 dsieger 2460:
1.6 rillig 2461: 16.1. Global default options
2462: 16.2. Converting packages to use bsd.options.mk
2463: 16.3. Option Names
1.7 rillig 2464: 16.4. Determining the options of dependencies
1.1 dsieger 2465:
1.6 rillig 2466: 17. The build process
1.1 dsieger 2467:
1.6 rillig 2468: 17.1. Introduction
2469: 17.2. Program location
2470: 17.3. Directories used during the build process
2471: 17.4. Running a phase
2472: 17.5. The fetch phase
1.1 dsieger 2473:
1.6 rillig 2474: 17.5.1. What to fetch and where to get it from
2475: 17.5.2. How are the files fetched?
1.1 dsieger 2476:
1.6 rillig 2477: 17.6. The checksum phase
2478: 17.7. The extract phase
2479: 17.8. The patch phase
2480: 17.9. The tools phase
2481: 17.10. The wrapper phase
2482: 17.11. The configure phase
2483: 17.12. The build phase
2484: 17.13. The test phase
2485: 17.14. The install phase
2486: 17.15. The package phase
2487: 17.16. Cleaning up
2488: 17.17. Other helpful targets
1.1 dsieger 2489:
1.6 rillig 2490: 18. Tools needed for building or running
1.1 dsieger 2491:
1.6 rillig 2492: 18.1. Tools for pkgsrc builds
2493: 18.2. Tools needed by packages
2494: 18.3. Tools provided by platforms
1.1 dsieger 2495:
1.6 rillig 2496: 19. Making your package work
1.1 dsieger 2497:
1.6 rillig 2498: 19.1. General operation
1.1 dsieger 2499:
1.108 rillig 2500: 19.1.1. How to pull in user-settable variables from mk.conf
2501: 19.1.2. User interaction
2502: 19.1.3. Handling licenses
2503: 19.1.4. Restricted packages
2504: 19.1.5. Handling dependencies
2505: 19.1.6. Handling conflicts with other packages
2506: 19.1.7. Packages that cannot or should not be built
2507: 19.1.8. Packages which should not be deleted, once installed
2508: 19.1.9. Handling packages with security problems
2509: 19.1.10. How to handle incrementing versions when fixing an existing
1.1 dsieger 2510: package
1.108 rillig 2511: 19.1.11. Substituting variable text in the package files (the SUBST
1.1 dsieger 2512: framework)
2513:
1.108 rillig 2514: 19.2. The fetch phase
1.1 dsieger 2515:
1.6 rillig 2516: 19.2.1. Packages whose distfiles aren't available for plain downloading
2517: 19.2.2. How to handle modified distfiles with the 'old' name
1.88 tnn 2518: 19.2.3. Packages hosted on github.com
1.1 dsieger 2519:
1.108 rillig 2520: 19.3. The configure phase
1.1 dsieger 2521:
1.6 rillig 2522: 19.3.1. Shared libraries - libtool
2523: 19.3.2. Using libtool on GNU packages that already support libtool
2524: 19.3.3. GNU Autoconf/Automake
2525:
2526: 19.4. Programming languages
2527:
2528: 19.4.1. C, C++, and Fortran
2529: 19.4.2. Java
2530: 19.4.3. Packages containing perl scripts
1.41 wiz 2531: 19.4.4. Packages containing shell scripts
2532: 19.4.5. Other programming languages
1.6 rillig 2533:
1.108 rillig 2534: 19.5. The build phase
1.6 rillig 2535:
2536: 19.5.1. Compiling C and C++ code conditionally
2537: 19.5.2. How to handle compiler bugs
1.24 wiz 2538: 19.5.3. Undefined reference to "..."
1.6 rillig 2539: 19.5.4. Running out of memory
2540:
1.108 rillig 2541: 19.6. The install phase
1.6 rillig 2542:
2543: 19.6.1. Creating needed directories
2544: 19.6.2. Where to install documentation
2545: 19.6.3. Installing highscore files
2546: 19.6.4. Adding DESTDIR support to packages
2547: 19.6.5. Packages with hardcoded paths to other interpreters
2548: 19.6.6. Packages installing perl modules
2549: 19.6.7. Packages installing info files
2550: 19.6.8. Packages installing man pages
1.7 rillig 2551: 19.6.9. Packages installing GConf data files
1.18 mishka 2552: 19.6.10. Packages installing scrollkeeper/rarian data files
1.6 rillig 2553: 19.6.11. Packages installing X11 fonts
2554: 19.6.12. Packages installing GTK2 modules
2555: 19.6.13. Packages installing SGML or XML data
2556: 19.6.14. Packages installing extensions to the MIME database
2557: 19.6.15. Packages using intltool
2558: 19.6.16. Packages installing startup scripts
2559: 19.6.17. Packages installing TeX modules
2560: 19.6.18. Packages supporting running binaries in emulation
2561: 19.6.19. Packages installing hicolor theme icons
2562: 19.6.20. Packages installing desktop files
2563:
2564: 19.7. Marking packages as having problems
2565:
2566: 20. Debugging
2567: 21. Submitting and Committing
2568:
2569: 21.1. Submitting binary packages
2570: 21.2. Submitting source packages (for non-NetBSD-developers)
2571: 21.3. General notes when adding, updating, or removing packages
1.34 wiz 2572: 21.4. Committing: Adding a package to CVS
1.6 rillig 2573: 21.5. Updating a package to a newer version
1.21 snj 2574: 21.6. Renaming a package in pkgsrc
2575: 21.7. Moving a package in pkgsrc
1.6 rillig 2576:
2577: 22. Frequently Asked Questions
2578: 23. GNOME packaging and porting
2579:
2580: 23.1. Meta packages
2581: 23.2. Packaging a GNOME application
2582: 23.3. Updating GNOME to a newer version
2583: 23.4. Patching guidelines
1.1 dsieger 2584:
1.6 rillig 2585: Chapter 10. Creating a new pkgsrc package from scratch
1.1 dsieger 2586:
2587: Table of Contents
2588:
1.6 rillig 2589: 10.1. Common types of packages
1.1 dsieger 2590:
1.6 rillig 2591: 10.1.1. Perl modules
1.66 asau 2592: 10.1.2. KDE3 applications
1.17 imil 2593: 10.1.3. Python modules and programs
1.1 dsieger 2594:
1.6 rillig 2595: 10.2. Examples
1.1 dsieger 2596:
1.6 rillig 2597: 10.2.1. How the www/nvu package came into pkgsrc
1.1 dsieger 2598:
2599: When you find a package that is not yet in pkgsrc, you most likely have a URL
2600: from where you can download the source code. Starting with this URL, creating a
2601: package involves only a few steps.
2602:
2603: 1. First, install the packages pkgtools/url2pkg and pkgtools/pkglint.
2604:
2605: 2. Then, choose one of the top-level directories as the category in which you
2606: want to place your package. You can also create a directory of your own
2607: (maybe called local). In that category directory, create another directory
2608: for your package and change into it.
2609:
2610: 3. Run the program url2pkg, which will ask you for a URL. Enter the URL of the
2611: distribution file (in most cases a .tar.gz file) and watch how the basic
2612: ingredients of your package are created automatically. The distribution
2613: file is extracted automatically to fill in some details in the Makefile
2614: that would otherwise have to be done manually.
2615:
2616: 4. Examine the extracted files to determine the dependencies of your package.
2617: Ideally, this is mentioned in some README file, but things may differ. For
2618: each of these dependencies, look where it exists in pkgsrc, and if there is
2619: a file called buildlink3.mk in that directory, add a line to your package
2620: Makefile which includes that file just before the last line. If the
1.26 spz 2621: buildlink3.mk file does not exist, it must be created first. The
2622: buildlink3.mk file makes sure that the package's include files and
2623: libraries are provided.
2624:
2625: If you just need binaries from a package, add a DEPENDS line to the
2626: Makefile, which specifies the version of the dependency and where it can be
2627: found in pkgsrc. This line should be placed in the third paragraph. If the
1.1 dsieger 2628: dependency is only needed for building the package, but not when using it,
2629: use BUILD_DEPENDS instead of DEPENDS. Your package may then look like this:
2630:
2631: [...]
2632:
1.66 asau 2633: BUILD_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
1.1 dsieger 2634: DEPENDS+= screen-[0-9]*:../../misc/screen
2635: DEPENDS+= screen>=4.0:../../misc/screen
2636:
2637: [...]
2638:
2639: .include "../../category/package/buildlink3.mk"
2640: .include "../../devel/glib2/buildlink3.mk"
2641: .include "../../mk/bsd.pkg.mk"
2642:
2643: 5. Run pkglint to see what things still need to be done to make your package a
2644: "good" one. If you don't know what pkglint's warnings want to tell you, try
2645: pkglint --explain or pkglint -e, which outputs additional explanations.
2646:
2647: 6. In many cases the package is not yet ready to build. You can find
1.6 rillig 2648: instructions for the most common cases in the next section, Section 10.1,
1.1 dsieger 2649: "Common types of packages". After you have followed the instructions over
2650: there, you can hopefully continue here.
2651:
2652: 7. Run bmake clean to clean the working directory from the extracted files.
2653: Besides these files, a lot of cache files and other system information has
2654: been saved in the working directory, which may become wrong after you
2655: edited the Makefile.
2656:
2657: 8. Now, run bmake to build the package. For the various things that can go
1.6 rillig 2658: wrong in this phase, consult Chapter 19, Making your package work.
1.1 dsieger 2659:
1.25 wiz 2660: 9. When the package builds fine, the next step is to install the package. Run
1.1 dsieger 2661: bmake install and hope that everything works.
2662:
2663: 10. Up to now, the file PLIST, which contains a list of the files that are
2664: installed by the package, is nearly empty. Run bmake print-PLIST >PLIST to
2665: generate a probably correct list. Check the file using your preferred text
2666: editor to see if the list of files looks plausible.
2667:
2668: 11. Run pkglint again to see if the generated PLIST contains garbage or not.
2669:
2670: 12. When you ran bmake install, the package has been registered in the database
2671: of installed files, but with an empty list of files. To fix this, run bmake
2672: deinstall and bmake install again. Now the package is registered with the
2673: list of files from PLIST.
2674:
2675: 13. Run bmake package to create a binary package from the set of installed
2676: files.
2677:
1.6 rillig 2678: 10.1. Common types of packages
1.1 dsieger 2679:
1.6 rillig 2680: 10.1.1. Perl modules
1.1 dsieger 2681:
2682: Simple Perl modules are handled automatically by url2pkg, including
2683: dependencies.
2684:
1.66 asau 2685: 10.1.2. KDE3 applications
1.1 dsieger 2686:
1.66 asau 2687: KDE3 applications should always include meta-pkgs/kde3/kde3.mk, which contains
2688: numerous settings that are typical of KDE3 packages.
1.1 dsieger 2689:
1.17 imil 2690: 10.1.3. Python modules and programs
2691:
2692: Python modules and programs packages are easily created using a set of
2693: predefined variables.
2694:
1.63 wiz 2695: If some Python versions are not supported by the software, set the
2696: PYTHON_VERSIONS_INCOMPATIBLE variable to the Python versions that are not
2697: supported, e.g.
1.17 imil 2698:
1.93 sevan 2699: PYTHON_VERSIONS_INCOMPATIBLE= 27
1.17 imil 2700:
1.103 wiz 2701: If the packaged software is a Python module, include one of ../../lang/python/
2702: egg.mk, ../../lang/python/distutils.mk, or ../../lang/python/extension.mk.
2703:
2704: Most Python packages use either "distutils" or easy-setup/setuptools ("eggs").
2705: if the packaged software is using setuptools, you only need to include "../../
2706: lang/python/egg.mk". Otherwise, if the software uses "distutils", include "..
2707: /../lang/python/distutils.mk". so pkgsrc will use this framework. "distutils"
2708: uses a script called setup.py, if the "distutils" driver is not called
2709: setup.py, set the PYSETUP variable to the name of the script.
2710:
2711: Either way, the package directory should be called "py-software" and PKGNAME
2712: should be set to "${PYPKGPREFIX}-${DISTNAME}", e.g.
1.17 imil 2713:
2714: DISTNAME= foopymodule-1.2.10
2715: PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
2716:
1.63 wiz 2717: If it is an application, include "../../lang/python/application.mk". In order
2718: to correctly set the path to the Python interpreter, use the REPLACE_PYTHON
2719: variable and set it to the list of files (paths relative to WRKSRC) that must
2720: be corrected. For example:
1.17 imil 2721:
1.63 wiz 2722: REPLACE_PYTHON= *.py
1.17 imil 2723:
1.63 wiz 2724: Some Python modules have separate distributions for Python-2.x and Python-3.x
2725: support. In pkgsrc this is handled by the versioned_dependencies.mk file. Set
2726: PYTHON_VERSIONED_DEPENDENCIES to the list of packages that should be depended
2727: upon and include "../../lang/python/versioned_dependencies.mk", then the pkgsrc
2728: infrastructure will depend on the appropriate package version. For example:
1.17 imil 2729:
1.110 wiz 2730: PYTHON_VERSIONED_DEPENDENCIES=dateutil
1.63 wiz 2731:
2732: Look inside versioned_dependencies.mk for a list of supported packages.
1.17 imil 2733:
1.6 rillig 2734: 10.2. Examples
1.1 dsieger 2735:
1.6 rillig 2736: 10.2.1. How the www/nvu package came into pkgsrc
1.1 dsieger 2737:
1.6 rillig 2738: 10.2.1.1. The initial package
1.1 dsieger 2739:
2740: Looking at the file pkgsrc/doc/TODO, I saw that the "nvu" package has not yet
2741: been imported into pkgsrc. As the description says it has to do with the web,
2742: the obvious choice for the category is "www".
2743:
2744: $ mkdir www/nvu
2745: $ cd www/nvu
2746:
2747: The web site says that the sources are available as a tar file, so I fed that
2748: URL to the url2pkg program:
2749:
2750: $ url2pkg http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
2751:
2752: My editor popped up, and I added a PKGNAME line below the DISTNAME line, as the
2753: package name should not have the word "sources" in it. I also filled in the
2754: MAINTAINER, HOMEPAGE and COMMENT fields. Then the package Makefile looked like
2755: that:
2756:
1.2 rillig 2757: # $NetBSD$
1.1 dsieger 2758: #
2759:
2760: DISTNAME= nvu-1.0-sources
2761: PKGNAME= nvu-1.0
2762: CATEGORIES= www
2763: MASTER_SITES= http://cvs.nvu.com/download/
2764: EXTRACT_SUFX= .tar.bz2
2765:
2766: MAINTAINER= rillig@NetBSD.org
2767: HOMEPAGE= http://cvs.nvu.com/
2768: COMMENT= Web Authoring System
2769:
2770: # url2pkg-marker (please do not remove this line.)
2771: .include "../../mk/bsd.pkg.mk"
2772:
2773: Then, I quit the editor and watched pkgsrc downloading a large source archive:
2774:
2775: url2pkg> Running "make makesum" ...
2776: => Required installed package digest>=20010302: digest-20060826 found
2777: => Fetching nvu-1.0-sources.tar.bz2
2778: Requesting http://cvs.nvu.com/download/nvu-1.0-sources.tar.bz2
2779: 100% |*************************************| 28992 KB 150.77 KB/s00:00 ETA
2780: 29687976 bytes retrieved in 03:12 (150.77 KB/s)
2781: url2pkg> Running "make extract" ...
2782: => Required installed package digest>=20010302: digest-20060826 found
2783: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
2784: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
2785: work.bacc -> /tmp/roland/pkgsrc/www/nvu/work.bacc
2786: ===> Installing dependencies for nvu-1.0
2787: ===> Overriding tools for nvu-1.0
2788: ===> Extracting for nvu-1.0
2789: url2pkg> Adjusting the Makefile.
2790:
2791: Remember to correct CATEGORIES, HOMEPAGE, COMMENT, and DESCR when you're done!
2792:
2793: Good luck! (See pkgsrc/doc/pkgsrc.txt for some more help :-)
2794:
1.6 rillig 2795: 10.2.1.2. Fixing all kinds of problems to make the package work
1.1 dsieger 2796:
2797: Now that the package has been extracted, let's see what's inside it. The
2798: package has a README.txt, but that only says something about mozilla, so it's
2799: probably useless for seeing what dependencies this package has. But since there
2800: is a GNU configure script in the package, let's hope that it will complain
2801: about everything it needs.
2802:
2803: $ bmake
2804: => Required installed package digest>=20010302: digest-20060826 found
2805: => Checksum SHA1 OK for nvu-1.0-sources.tar.bz2
2806: => Checksum RMD160 OK for nvu-1.0-sources.tar.bz2
2807: ===> Patching for nvu-1.0
2808: ===> Creating toolchain wrappers for nvu-1.0
2809: ===> Configuring for nvu-1.0
2810: [...]
2811: configure: error: Perl 5.004 or higher is required.
2812: [...]
2813: WARNING: Please add USE_TOOLS+=perl to the package Makefile.
2814: [...]
2815:
2816: That worked quite well. So I opened the package Makefile in my editor, and
2817: since it already has a USE_TOOLS line, I just appended "perl" to it. Since the
2818: dependencies of the package have changed now, and since a perl wrapper is
2819: automatically installed in the "tools" phase, I need to build the package from
2820: scratch.
2821:
2822: $ bmake clean
2823: ===> Cleaning for nvu-1.0
2824: $ bmake
2825: [...]
2826: *** /tmp/roland/pkgsrc/www/nvu/work.bacc/.tools/bin/make is not \
2827: GNU Make. You will not be able to build Mozilla without GNU Make.
2828: [...]
2829:
2830: So I added "gmake" to the USE_TOOLS line and tried again (from scratch).
2831:
2832: [...]
2833: checking for GTK - version >= 1.2.0... no
2834: *** Could not run GTK test program, checking why...
2835: [...]
2836:
2837: Now to the other dependencies. The first question is: Where is the GTK package
2838: hidden in pkgsrc?
2839:
2840: $ echo ../../*/gtk*
2841: [many packages ...]
2842: $ echo ../../*/gtk
2843: ../../x11/gtk
2844: $ echo ../../*/gtk2
2845: ../../x11/gtk2
2846: $ echo ../../*/gtk2/bui*
2847: ../../x11/gtk2/buildlink3.mk
2848:
2849: The first try was definitely too broad. The second one had exactly one result,
2850: which is very good. But there is one pitfall with GNOME packages. Before GNOME
2851: 2 had been released, there were already many GNOME 1 packages in pkgsrc. To be
2852: able to continue to use these packages, the GNOME 2 packages were imported as
2853: separate packages, and their names usually have a "2" appended. So I checked
2854: whether this was the case here, and indeed it was.
2855:
2856: Since the GTK2 package has a buildlink3.mk file, adding the dependency is very
2857: easy. I just inserted an .include line before the last line of the package
2858: Makefile, so that it now looks like this:
2859:
2860: [...]
2861: .include "../../x11/gtk2/buildlink3.mk"
2862: .include "../../mk/bsd.pkg.mk
2863:
2864: After another bmake clean && bmake, the answer was:
2865:
2866: [...]
2867: checking for gtk-config... /home/roland/pkg/bin/gtk-config
2868: checking for GTK - version >= 1.2.0... no
2869: *** Could not run GTK test program, checking why...
2870: *** The test program failed to compile or link. See the file config.log for the
2871: *** exact error that occured. This usually means GTK was incorrectly installed
2872: *** or that you have moved GTK since it was installed. In the latter case, you
2873: *** may want to edit the gtk-config script: /home/roland/pkg/bin/gtk-config
2874: configure: error: Test for GTK failed.
2875: [...]
2876:
2877: In this particular case, the assumption that "every package prefers GNOME 2"
2878: had been wrong. The first of the lines above told me that this package really
2879: wanted to have the GNOME 1 version of GTK. If the package had looked for GTK2,
2880: it would have looked for pkg-config instead of gtk-config. So I changed the x11
2881: /gtk2 to x11/gtk in the package Makefile, and tried again.
2882:
2883: [...]
1.59 jnemeth 2884: cc -o xpidl.o -c -DOSTYPE=\"NetBSD3\" -DOSARCH=\"NetBSD\" [...]
1.1 dsieger 2885: In file included from xpidl.c:42:
2886: xpidl.h:53:24: libIDL/IDL.h: No such file or directory
2887: In file included from xpidl.c:42:
2888: xpidl.h:132: error: parse error before "IDL_ns"
2889: [...]
2890:
2891: The package still does not find all of its dependencies. Now the question is:
2892: Which package provides the libIDL/IDL.h header file?
2893:
2894: $ echo ../../*/*idl*
2895: ../../devel/py-idle ../../wip/idled ../../x11/acidlaunch
2896: $ echo ../../*/*IDL*
2897: ../../net/libIDL
2898:
2899: Let's take the one from the second try. So I included the ../../net/libIDL/
2900: buildlink3.mk file and tried again. But the error didn't change. After digging
2901: through some of the code, I concluded that the build process of the package was
2902: broken and couldn't have ever worked, but since the Mozilla source tree is
2903: quite large, I didn't want to fix it. So I added the following to the package
2904: Makefile and tried again:
2905:
2906: CPPFLAGS+= -I${BUILDLINK_PREFIX.libIDL}/include/libIDL-2.0
2907: BUILDLINK_TRANSFORM+= -l:IDL:IDL-2
2908:
2909: The latter line is needed because the package expects the library libIDL.so,
2910: but only libIDL-2.so is available. So I told the compiler wrapper to rewrite
2911: that on the fly.
2912:
2913: The next problem was related to a recent change of the FreeType interface. I
2914: looked up in www/seamonkey which patch files were relevant for this issue and
2915: copied them to the patches directory. Then I retried, fixed the patches so that
2916: they applied cleanly and retried again. This time, everything worked.
2917:
1.6 rillig 2918: 10.2.1.3. Installing the package
1.1 dsieger 2919:
2920: $ bmake CHECK_FILES=no install
2921: [...]
2922: $ bmake print-PLIST >PLIST
2923: $ bmake deinstall
2924: $ bmake install
2925:
1.6 rillig 2926: Chapter 11. Package components - files, directories and contents
1.1 dsieger 2927:
2928: Table of Contents
2929:
1.6 rillig 2930: 11.1. Makefile
2931: 11.2. distinfo
2932: 11.3. patches/*
2933:
2934: 11.3.1. Structure of a single patch file
2935: 11.3.2. Creating patch files
2936: 11.3.3. Sources where the patch files come from
2937: 11.3.4. Patching guidelines
2938: 11.3.5. Feedback to the author
2939:
2940: 11.4. Other mandatory files
2941: 11.5. Optional files
2942:
2943: 11.5.1. Files affecting the binary package
2944: 11.5.2. Files affecting the build process
2945: 11.5.3. Files affecting nothing at all
1.1 dsieger 2946:
1.6 rillig 2947: 11.6. work*
2948: 11.7. files/*
1.1 dsieger 2949:
2950: Whenever you're preparing a package, there are a number of files involved which
2951: are described in the following sections.
2952:
1.6 rillig 2953: 11.1. Makefile
1.1 dsieger 2954:
2955: Building, installation and creation of a binary package are all controlled by
2956: the package's Makefile. The Makefile describes various things about a package,
2957: for example from where to get it, how to configure, build, and install it.
2958:
2959: A package Makefile contains several sections that describe the package.
2960:
2961: In the first section there are the following variables, which should appear
2962: exactly in the order given here. The order and grouping of the variables is
2963: mostly historical and has no further meaning.
2964:
2965: * DISTNAME is the basename of the distribution file to be downloaded from the
2966: package's website.
2967:
1.66 asau 2968: * PKGNAME is the name of the package, as used by pkgsrc. You need to provide
2969: it if DISTNAME (which is the default) is not a good name for the package in
2970: pkgsrc or DISTNAME is not provided (no distribution file is required).
2971: Usually it is the pkgsrc directory name together with the version number.
2972: It must match the regular expression ^[A-Za-z0-9][A-Za-z0-9-_.+]*$, that
2973: is, it starts with a letter or digit, and contains only letters, digits,
2974: dashes, underscores, dots and plus signs.
1.1 dsieger 2975:
2976: * CATEGORIES is a list of categories which the package fits in. You can
2977: choose any of the top-level directories of pkgsrc for it.
2978:
2979: Currently the following values are available for CATEGORIES. If more than
2980: one is used, they need to be separated by spaces:
2981:
2982: archivers cross geography meta-pkgs security
2983: audio databases graphics misc shells
2984: benchmarks devel ham multimedia sysutils
2985: biology editors inputmethod net textproc
2986: cad emulators lang news time
2987: chat finance mail parallel wm
2988: comms fonts math pkgtools www
2989: converters games mbone print x11
2990:
2991: * MASTER_SITES, DYNAMIC_MASTER_SITES, DIST_SUBDIR, EXTRACT_SUFX and DISTFILES
1.6 rillig 2992: are discussed in detail in Section 17.5, "The fetch phase".
1.1 dsieger 2993:
2994: The second section contains information about separately downloaded patches, if
2995: any.
2996:
2997: * PATCHFILES: Name(s) of additional files that contain distribution patches.
2998: There is no default. pkgsrc will look for them at PATCH_SITES. They will
2999: automatically be uncompressed before patching if the names end with .gz or
3000: .Z.
3001:
3002: * PATCH_SITES: Primary location(s) for distribution patch files (see
1.80 wiz 3003: PATCHFILES above) if not found locally.
3004:
3005: * PATCH_DIST_STRIP: an argument to patch(1) that sets the pathname strip
3006: count to help find the correct files to patch. It defaults to -p0.
1.1 dsieger 3007:
3008: The third section contains the following variables.
3009:
3010: * MAINTAINER is the email address of the person who feels responsible for
3011: this package, and who is most likely to look at problems or questions
3012: regarding this package which have been reported with send-pr(1). Other
1.14 jmcneill 3013: developers may contact the MAINTAINER before making changes to the package,
3014: but are not required to do so. When packaging a new program, set MAINTAINER
3015: to yourself. If you really can't maintain the package for future updates,
3016: set it to <pkgsrc-users@NetBSD.org>.
3017:
3018: * OWNER should be used instead of MAINTAINER when you do not want other
3019: developers to update or change the package without contacting you first. A
3020: package Makefile should contain one of MAINTAINER or OWNER, but not both.
1.1 dsieger 3021:
3022: * HOMEPAGE is a URL where users can find more information about the package.
3023:
3024: * COMMENT is a one-line description of the package (should not include the
3025: package name).
3026:
3027: Other variables that affect the build:
3028:
3029: * WRKSRC: The directory where the interesting distribution files of the
3030: package are found. The default is ${WRKDIR}/${DISTNAME}, which works for
3031: most packages.
3032:
3033: If a package doesn't create a subdirectory for itself (most GNU software
3034: does, for instance), but extracts itself in the current directory, you
3035: should set WRKSRC=${WRKDIR}.
3036:
3037: If a package doesn't create a subdirectory with the name of DISTNAME but
3038: some different name, set WRKSRC to point to the proper name in ${WRKDIR},
3039: for example WRKSRC=${WRKDIR}/${DISTNAME}/unix. See lang/tcl and x11/tk for
3040: other examples.
3041:
3042: The name of the working directory created by pkgsrc is taken from the
3043: WRKDIR_BASENAME variable. By default, its value is work. If you want to use
3044: the same pkgsrc tree for building different kinds of binary packages, you
3045: can change the variable according to your needs. Two other variables handle
3046: common cases of setting WRKDIR_BASENAME individually. If OBJHOSTNAME is
1.4 rillig 3047: defined in mk.conf, the first component of the host's name is attached to
3048: the directory name. If OBJMACHINE is defined, the platform name is
1.1 dsieger 3049: attached, which might look like work.i386 or work.sparc.
3050:
3051: Please pay attention to the following gotchas:
3052:
3053: * Add MANCOMPRESSED if man pages are installed in compressed form by the
3054: package. For packages using BSD-style makefiles which honor MANZ, there is
3055: MANCOMPRESSED_IF_MANZ.
3056:
3057: * Replace /usr/local with "${PREFIX}" in all files (see patches, below).
3058:
1.6 rillig 3059: * If the package installs any info files, see Section 19.6.7, "Packages
1.1 dsieger 3060: installing info files".
3061:
1.6 rillig 3062: 11.2. distinfo
1.1 dsieger 3063:
3064: The distinfo file contains the message digest, or checksum, of each distfile
3065: needed for the package. This ensures that the distfiles retrieved from the
3066: Internet have not been corrupted during transfer or altered by a malign force
1.108 rillig 3067: to introduce a security hole. To provide maximum security, all distfiles are
3068: protected using three different message digest algorithms (SHA1, RMD160,
3069: SHA512), as well as the file size.
1.1 dsieger 3070:
3071: The distinfo file also contains the checksums for all the patches found in the
1.6 rillig 3072: patches directory (see Section 11.3, "patches/*").
1.1 dsieger 3073:
1.108 rillig 3074: To regenerate the distinfo file, use the make distinfo command.
1.1 dsieger 3075:
3076: Some packages have different sets of distfiles depending on the platform, for
1.24 wiz 3077: example lang/openjdk7. These are kept in the same distinfo file and care should
3078: be taken when upgrading such a package to ensure distfile information is not
3079: lost.
1.1 dsieger 3080:
1.6 rillig 3081: 11.3. patches/*
1.1 dsieger 3082:
1.108 rillig 3083: Some packages don't work out-of-the box on the various platforms that are
3084: supported by pkgsrc. These packages need to be patched to make them work. The
3085: patch files can be found in the patches/ directory.
1.1 dsieger 3086:
3087: In the patch phase, these patches are applied to the files in WRKSRC directory
1.25 wiz 3088: after extracting them, in alphabetic order.
1.1 dsieger 3089:
1.6 rillig 3090: 11.3.1. Structure of a single patch file
1.1 dsieger 3091:
3092: The patch-* files should be in diff -bu format, and apply without a fuzz to
3093: avoid problems. (To force patches to apply with fuzz you can set
3094: PATCH_FUZZ_FACTOR=-F2). Furthermore, each patch should contain only changes for
3095: a single file, and no file should be patched by more than one patch file. This
3096: helps to keep future modifications simple.
3097:
3098: Each patch file is structured as follows: In the first line, there is the RCS
3099: Id of the patch itself. The second line should be empty for aesthetic reasons.
3100: After that, there should be a comment for each change that the patch does.
3101: There are a number of standard cases:
3102:
3103: * Patches for commonly known vulnerabilities should mention the vulnerability
3104: ID (CAN, CVE).
3105:
3106: * Patches that change source code should mention the platform and other
3107: environment (for example, the compiler) that the patch is needed for.
3108:
1.108 rillig 3109: The patch should be commented so that any developer who knows the code of the
3110: application can make some use of the patch. Special care should be taken for
3111: the upstream developers, since we generally want that they accept our patches,
3112: so we have less work in the future.
1.1 dsieger 3113:
1.6 rillig 3114: 11.3.2. Creating patch files
1.1 dsieger 3115:
3116: One important thing to mention is to pay attention that no RCS IDs get stored
3117: in the patch files, as these will cause problems when later checked into the
3118: NetBSD CVS tree. Use the pkgdiff command from the pkgtools/pkgdiff package to
3119: avoid these problems.
3120:
3121: For even more automation, we recommend using mkpatches from the same package to
3122: make a whole set of patches. You just have to backup files before you edit them
1.25 wiz 3123: to filename.orig, e.g. with cp -p filename filename.orig or, easier, by using
1.1 dsieger 3124: pkgvi again from the same package. If you upgrade a package this way, you can
1.25 wiz 3125: easily compare the new set of patches with the previously existing one with
3126: patchdiff. The files in patches are replaced by new files, so carefully check
3127: if you want to take all the changes.
1.1 dsieger 3128:
3129: When you have finished a package, remember to generate the checksums for the
1.6 rillig 3130: patch files by using the make makepatchsum command, see Section 11.2,
1.1 dsieger 3131: "distinfo".
3132:
3133: When adding a patch that corrects a problem in the distfile (rather than e.g.
3134: enforcing pkgsrc's view of where man pages should go), send the patch as a bug
3135: report to the maintainer. This benefits non-pkgsrc users of the package, and
3136: usually makes it possible to remove the patch in future version.
3137:
1.25 wiz 3138: The file names of the patch files are usually of the form patch-
3139: path_to_file__with__underscores.c. Many packages still use the previous
3140: convention patch-[a-z][a-z], but new patches should be of the form containing
3141: the filename. mkpatches included in pkgtools/pkgdiff takes care of the name
3142: automatically.
1.2 rillig 3143:
1.6 rillig 3144: 11.3.3. Sources where the patch files come from
1.1 dsieger 3145:
3146: If you want to share patches between multiple packages in pkgsrc, e.g. because
3147: they use the same distfiles, set PATCHDIR to the path where the patch files can
3148: be found, e.g.:
3149:
3150: PATCHDIR= ${.CURDIR}/../xemacs/patches
3151:
3152: Patch files that are distributed by the author or other maintainers can be
3153: listed in PATCHFILES.
3154:
3155: If it is desired to store any patches that should not be committed into pkgsrc,
3156: they can be kept outside the pkgsrc tree in the $LOCALPATCHES directory. The
3157: directory tree there is expected to have the same "category/package" structure
3158: as pkgsrc, and patches are expected to be stored inside these dirs (also known
3159: as $LOCALPATCHES/$PKGPATH). For example, if you want to keep a private patch
3160: for pkgsrc/graphics/png, keep it in $LOCALPATCHES/graphics/png/mypatch. All
3161: files in the named directory are expected to be patch files, and they are
3162: applied after pkgsrc patches are applied.
3163:
1.6 rillig 3164: 11.3.4. Patching guidelines
1.1 dsieger 3165:
3166: When fixing a portability issue in the code do not use preprocessor magic to
3167: check for the current operating system nor platform. Doing so hurts portability
3168: to other platforms because the OS-specific details are not abstracted
3169: appropriately.
3170:
3171: The general rule to follow is: instead of checking for the operating system the
3172: application is being built on, check for the specific features you need. For
3173: example, instead of assuming that kqueue is available under NetBSD and using
3174: the __NetBSD__ macro to conditionalize kqueue support, add a check that detects
3175: kqueue itself ? yes, this generally involves patching the configure script.
3176: There is absolutely nothing that prevents some OSes from adopting interfaces
3177: from other OSes (e.g. Linux implementing kqueue), something that the above
3178: checks cannot take into account.
3179:
3180: Of course, checking for features generally involves more work on the
3181: developer's side, but the resulting changes are cleaner and there are chances
3182: they will work on many other platforms. Not to mention that there are higher
3183: chances of being later integrated into the mainstream sources. Remember: It
3184: doesn't work unless it is right!
3185:
3186: Some typical examples:
3187:
1.6 rillig 3188: Table 11.1. Patching examples
1.1 dsieger 3189:
3190: +-------------------------------------------------------------------------------------------+
3191: | Where | Incorrect | Correct |
3192: |---------+--------------------------+------------------------------------------------------|
3193: | |case ${target_os} in | |
3194: |configure|netbsd*) have_kvm=yes ;; |AC_CHECK_LIB(kvm, kvm_open, have_kvm=yes, have_kvm=no)|
3195: |script |*) have_kvm=no ;; | |
3196: | |esac | |
3197: |---------+--------------------------+------------------------------------------------------|
1.2 rillig 3198: |C source |#if defined(__NetBSD__) |#if defined(HAVE_SYS_EVENT_H) |
3199: |file |# include <sys/event.h> |# include <sys/event.h> |
3200: | |#endif |#endif |
1.1 dsieger 3201: |---------+--------------------------+------------------------------------------------------|
3202: | |int |int |
3203: | |monitor_file(...) |monitor_file(...) |
3204: | |{ |{ |
3205: | |#if defined(__NetBSD__) |#if defined(HAVE_KQUEUE) |
3206: |C source | int fd = kqueue();| int fd = kqueue(); |
3207: |file | ... | ... |
3208: | |#else |#else |
3209: | | ... | ... |
3210: | |#endif |#endif |
3211: | |} |} |
3212: +-------------------------------------------------------------------------------------------+
3213:
3214:
3215: For more information, please read the Making packager-friendly software article
3216: (part 1, part 2). It summarizes multiple details on how to make software easier
3217: to package; all the suggestions in it were collected from our experience in
3218: pkgsrc work, so they are possibly helpful when creating patches too.
3219:
1.6 rillig 3220: 11.3.5. Feedback to the author
1.1 dsieger 3221:
3222: Always, always, always feed back any portability fixes or improvements you do
3223: to a package to the mainstream developers. This is the only way to get their
3224: attention on portability issues and to ensure that future versions can be built
3225: out-of-the box on NetBSD. Furthermore, any user that gets newer distfiles will
3226: get the fixes straight from the packaged code.
3227:
3228: This generally involves cleaning up the patches (because sometimes the patches
1.41 wiz 3229: that are added to pkgsrc are quick hacks), filing bug reports in the
1.1 dsieger 3230: appropriate trackers for the projects and working with the mainstream authors
3231: to accept your changes. It is extremely important that you do it so that the
3232: packages in pkgsrc are kept simple and thus further changes can be done without
3233: much hassle.
3234:
1.25 wiz 3235: When you have done this, please add a URL to the upstream bug report to the
3236: patch comment.
3237:
1.1 dsieger 3238: Support the idea of free software!
3239:
1.6 rillig 3240: 11.4. Other mandatory files
1.1 dsieger 3241:
3242: DESCR
3243:
3244: A multi-line description of the piece of software. This should include any
3245: credits where they are due. Please bear in mind that others do not share
3246: your sense of humour (or spelling idiosyncrasies), and that others will
3247: read everything that you write here.
3248:
3249: PLIST
3250:
3251: This file governs the files that are installed on your system: all the
3252: binaries, manual pages, etc. There are other directives which may be
3253: entered in this file, to control the creation and deletion of directories,
1.6 rillig 3254: and the location of inserted files. See Chapter 13, PLIST issues for more
1.1 dsieger 3255: information.
3256:
1.6 rillig 3257: 11.5. Optional files
1.1 dsieger 3258:
1.6 rillig 3259: 11.5.1. Files affecting the binary package
1.1 dsieger 3260:
3261: INSTALL
3262:
3263: This shell script is invoked twice by pkg_add(1). First time after package
3264: extraction and before files are moved in place, the second time after the
3265: files to install are moved in place. This can be used to do any custom
3266: procedures not possible with @exec commands in PLIST. See pkg_add(1) and
1.6 rillig 3267: pkg_create(1) for more information. See also Section 15.1, "Files and
1.29 wiz 3268: directories outside the installation prefix". Please note that you can
3269: modify variables in it easily by using FILES_SUBST in the package's
3270: Makefile:
3271:
3272: FILES_SUBST+= SOMEVAR="somevalue"
3273:
3274: replaces "@SOMEVAR@" with "somevalue" in the INSTALL. By default,
3275: substitution is performed for PREFIX, LOCALBASE, X11BASE, VARBASE, and a
3276: few others, type make help topic=FILES_SUBST for a complete list.
1.1 dsieger 3277:
3278: DEINSTALL
3279:
3280: This script is executed before and after any files are removed. It is this
3281: script's responsibility to clean up any additional messy details around the
3282: package's installation, since all pkg_delete knows is how to delete the
3283: files created in the original distribution. See pkg_delete(1) and
1.29 wiz 3284: pkg_create(1) for more information. The same methods to replace variables
3285: can be used as for the INSTALL file.
1.1 dsieger 3286:
3287: MESSAGE
3288:
3289: This file is displayed after installation of the package. Useful for things
3290: like legal notices on almost-free software and hints for updating config
3291: files after installing modules for apache, PHP etc. Please note that you
3292: can modify variables in it easily by using MESSAGE_SUBST in the package's
3293: Makefile:
3294:
3295: MESSAGE_SUBST+= SOMEVAR="somevalue"
3296:
3297: replaces "${SOMEVAR}" with "somevalue" in MESSAGE. By default, substitution
1.99 sevan 3298: is performed for PKGNAME, PKGBASE, PREFIX, LOCALBASE, X11BASE,
1.16 jnemeth 3299: PKG_SYSCONFDIR, ROOT_GROUP, and ROOT_USER.
1.1 dsieger 3300:
3301: You can display a different or additional files by setting the MESSAGE_SRC
3302: variable. Its default is MESSAGE, if the file exists.
3303:
3304: ALTERNATIVES
3305:
1.66 asau 3306: This file is used by the alternatives framework. It creates, configures,
3307: and destroys generic wrappers used to run programs with similar interfaces.
3308: See pkg_alternatives(8) from pkgtools/pkg_alternatives for more
3309: information.
3310:
3311: Each line of the file contains two filenames, first the wrapper and then
3312: the alternative provided by the package. Both paths are relative to PREFIX.
1.1 dsieger 3313:
1.6 rillig 3314: 11.5.2. Files affecting the build process
1.1 dsieger 3315:
3316: Makefile.common
3317:
3318: This file contains arbitrary things that could also go into a Makefile, but
3319: its purpose is to be used by more than one package. This file should only
3320: be used when the packages that will use the file are known in advance. For
3321: other purposes it is often better to write a *.mk file and give it a good
3322: name that describes what it does.
3323:
3324: buildlink3.mk
3325:
3326: This file contains the dependency information for the buildlink3 framework
1.6 rillig 3327: (see Chapter 14, Buildlink methodology).
1.1 dsieger 3328:
3329: hacks.mk
3330:
3331: This file contains workarounds for compiler bugs and similar things. It is
3332: included automatically by the pkgsrc infrastructure, so you don't need an
3333: extra .include line for it.
3334:
3335: options.mk
3336:
3337: This file contains the code for the package-specific options (see
1.6 rillig 3338: Chapter 16, Options handling) that can be selected by the user. If a
1.1 dsieger 3339: package has only one or two options, it is equally acceptable to put the
3340: code directly into the Makefile.
3341:
1.6 rillig 3342: 11.5.3. Files affecting nothing at all
1.1 dsieger 3343:
3344: README*
3345:
3346: These files do not take place in the creation of a package and thus are
3347: purely informative to the package developer.
3348:
3349: TODO
3350:
3351: This file contains things that need to be done to make the package even
3352: better.
3353:
1.6 rillig 3354: 11.6. work*
1.1 dsieger 3355:
3356: When you type make, the distribution files are unpacked into the directory
3357: denoted by WRKDIR. It can be removed by running make clean. Besides the
3358: sources, this directory is also used to keep various timestamp files. The
3359: directory gets removed completely on clean. The default is ${.CURDIR}/work or $
3360: {.CURDIR}/work.${MACHINE_ARCH} if OBJMACHINE is set.
3361:
1.6 rillig 3362: 11.7. files/*
1.1 dsieger 3363:
3364: If you have any files that you wish to be placed in the package prior to
3365: configuration or building, you could place these files here and use a ${CP}
3366: command in the "pre-configure" target to achieve this. Alternatively, you could
3367: simply diff the file against /dev/null and use the patch mechanism to manage
3368: the creation of this file.
3369:
3370: If you want to share files in this way with other packages, set the FILESDIR
3371: variable to point to the other package's files directory, e.g.:
3372:
3373: FILESDIR=${.CURDIR}/../xemacs/files
3374:
1.6 rillig 3375: Chapter 12. Programming in Makefiles
1.1 dsieger 3376:
3377: Table of Contents
3378:
1.6 rillig 3379: 12.1. Caveats
3380: 12.2. Makefile variables
1.1 dsieger 3381:
1.6 rillig 3382: 12.2.1. Naming conventions
1.1 dsieger 3383:
1.6 rillig 3384: 12.3. Code snippets
1.1 dsieger 3385:
1.6 rillig 3386: 12.3.1. Adding things to a list
1.108 rillig 3387: 12.3.2. Echoing a string exacty as-is
3388: 12.3.3. Passing CFLAGS to GNU configure scripts
3389: 12.3.4. Handling possibly empty variables
1.1 dsieger 3390:
3391: Pkgsrc consists of many Makefile fragments, each of which forms a well-defined
3392: part of the pkgsrc system. Using the make(1) system as a programming language
3393: for a big system like pkgsrc requires some discipline to keep the code correct
3394: and understandable.
3395:
3396: The basic ingredients for Makefile programming are variables (which are
3397: actually macros) and shell commands. Among these shell commands may even be
3398: more complex ones like awk(1) programs. To make sure that every shell command
3399: runs as intended it is necessary to quote all variables correctly when they are
3400: used.
3401:
3402: This chapter describes some patterns, that appear quite often in Makefiles,
3403: including the pitfalls that come along with them.
3404:
1.6 rillig 3405: 12.1. Caveats
1.1 dsieger 3406:
3407: * When you are creating a file as a target of a rule, always write the data
3408: to a temporary file first and finally rename that file. Otherwise there
3409: might occur an error in the middle of generating the file, and when the
3410: user runs make(1) for the second time, the file exists and will not be
3411: regenerated properly. Example:
3412:
3413: wrong:
3414: @echo "line 1" > ${.TARGET}
3415: @echo "line 2" >> ${.TARGET}
3416: @false
3417:
3418: correct:
3419: @echo "line 1" > ${.TARGET}.tmp
3420: @echo "line 2" >> ${.TARGET}.tmp
3421: @false
3422: @mv ${.TARGET}.tmp ${.TARGET}
3423:
3424: When you run make wrong twice, the file wrong will exist, although there
3425: was an error message in the first run. On the other hand, running make
3426: correct gives an error message twice, as expected.
3427:
3428: You might remember that make(1) sometimes removes ${.TARGET} in case of
3429: error, but this only happens when it is interrupted, for example by
3430: pressing ^C. This does not happen when one of the commands fails (like
3431: false(1) above).
3432:
1.6 rillig 3433: 12.2. Makefile variables
1.1 dsieger 3434:
3435: Makefile variables contain strings that can be processed using the five
3436: operators ``='', ``+='', ``?='', ``:='', and ``!='', which are described in the
3437: make(1) man page.
3438:
3439: When a variable's value is parsed from a Makefile, the hash character ``#'' and
3440: the backslash character ``\'' are handled specially. If a backslash is followed
3441: by a newline, any whitespace immediately in front of the backslash, the
3442: backslash, the newline, and any whitespace immediately behind the newline are
3443: replaced with a single space. A backslash character and an immediately
3444: following hash character are replaced with a single hash character. Otherwise,
3445: the backslash is passed as is. In a variable assignment, any hash character
3446: that is not preceded by a backslash starts a comment that continues upto the
3447: end of the logical line.
3448:
1.108 rillig 3449: The evaluation of variables either happens immediately or lazy. It happens
3450: immediately when the variable occurs on the right-hand side of the ``:='' or
3451: the ``!='' operator, in a .if condition or a .for loop. In the other cases, it
3452: is evaluated lazily.
1.1 dsieger 3453:
3454: Some of the modifiers split the string into words and then operate on the
3455: words, others operate on the string as a whole. When a string is split into
1.108 rillig 3456: words, it is split like in sh(1).
1.1 dsieger 3457:
3458: There are several types of variables that should be handled differently.
3459: Strings and two types of lists.
3460:
3461: * Strings can contain arbitrary characters. Nevertheless, you should restrict
3462: yourself to only using printable characters. Examples are PREFIX and
3463: COMMENT.
3464:
3465: * Internal lists are lists that are never exported to any shell command.
3466: Their elements are separated by whitespace. Therefore, the elements
3467: themselves cannot have embedded whitespace. Any other characters are
3468: allowed. Internal lists can be used in .for loops. Examples are DEPENDS and
3469: BUILD_DEPENDS.
3470:
3471: * External lists are lists that may be exported to a shell command. Their
3472: elements can contain any characters, including whitespace. That's why they
3473: cannot be used in .for loops. Examples are DISTFILES and MASTER_SITES.
3474:
1.6 rillig 3475: 12.2.1. Naming conventions
1.1 dsieger 3476:
3477: * All variable names starting with an underscore are reserved for use by the
3478: pkgsrc infrastructure. They shall not be used by package Makefiles.
3479:
3480: * In .for loops you should use lowercase variable names for the iteration
3481: variables.
3482:
3483: * All list variables should have a ``plural'' name, e.g. PKG_OPTIONS or
3484: DISTFILES.
3485:
1.6 rillig 3486: 12.3. Code snippets
1.1 dsieger 3487:
1.108 rillig 3488: 12.3.1. Adding things to a list
3489:
3490: When adding a string that possibly contains whitespace or quotes to a list
3491: (example 1), it must be quoted using the :Q modifier.
1.1 dsieger 3492:
1.108 rillig 3493: When adding another list to a list (example 2), it must not be quoted, since
3494: its elements are already quoted.
1.1 dsieger 3495:
1.108 rillig 3496: STRING= foo * bar `date`
3497: LIST= # empty
3498: ANOTHER_LIST= a=b c=d
1.1 dsieger 3499:
1.108 rillig 3500: LIST+= ${STRING:Q} # 1
3501: LIST+= ${ANOTHER_LIST} # 2
1.1 dsieger 3502:
1.108 rillig 3503: 12.3.2. Echoing a string exacty as-is
1.1 dsieger 3504:
1.108 rillig 3505: Echoing a string containing special characters needs special work.
1.1 dsieger 3506:
3507: STRING= foo bar < > * `date` $$HOME ' "
1.108 rillig 3508: EXAMPLE_ENV= string=${STRING:Q} x=multiple\ quoted\ words
1.1 dsieger 3509:
3510: all:
3511: echo ${STRING} # 1
1.108 rillig 3512: echo ${STRING:Q} # 2
3513: printf '%s\n' ${STRING:Q}'' # 3
3514: env ${EXAMPLE_ENV} sh -c 'echo "$$string"; echo "$$x"' # 4
1.1 dsieger 3515:
3516: Example 1 leads to a syntax error in the shell, as the characters are just
3517: copied.
3518:
1.108 rillig 3519: Example 2 quotes the string so that the shell interprets it correctly. But the
3520: echo command may additionally interpret strings with a leading dash or those
3521: containing backslashes.
3522:
3523: Example 3 can handle arbitrary strings, since printf(1) only interprets the
3524: format string, but not the next argument.
3525:
3526: In example 4, the EXAMPLE_ENV does not need to be quoted because the quoting
3527: has already been done when adding elements to the list.
3528:
3529: 12.3.3. Passing CFLAGS to GNU configure scripts
3530:
3531: When passing CFLAGS or similar variables to a GNU-style configure script
3532: (especially those that call other configure scripts), it must not have leading
3533: or trailing whitespace, since otherwise the configure script gets confused. To
3534: trim leading and trailing whitespace, use the :M modifier, as in the following
3535: example:
3536:
3537: CPPFLAGS= # empty
3538: CPPFLAGS+= -Wundef -DPREFIX=\"${PREFIX}\"
3539: CPPFLAGS+= ${MY_CPPFLAGS}
3540:
3541: CONFIGURE_ARGS+= CPPFLAGS=${CPPFLAGS:M*:Q}
3542:
3543: all:
3544: echo x${CPPFLAGS:Q}x # leading and trailing whitespace
3545: echo x${CONFIGURE_ARGS:Q}x # properly trimmed
3546:
3547: In this example, CPPFLAGS has both leading and trailing whitespace because the
3548: += operator always adds a space.
3549:
3550: 12.3.4. Handling possibly empty variables
3551:
3552: When a possibly empty variable is used in a shell program, it may lead to a
3553: syntax error.
3554:
3555: EGFILES= # empty
3556:
3557: install-examples: # produces a syntax error in the shell
3558: for egfile in ${EGFILES}; do \
3559: echo "Installing $$egfile"; \
3560: done
3561:
3562: The shell only sees the text for egfile in ; do, since ${EGFILES} is replaced
3563: with an empty string by make(1). To fix this syntax error, use one of the
3564: snippets below.
3565:
3566: EMPTY= # empty
3567:
3568: install-examples:
3569: for egfile in ${EGFILES} ""; do \
3570: [ -n "$$egfile" ] || continue; \
3571: echo "Installing $$egfile"; \
3572: done
3573:
3574: In this case, an empty string is appended to the iteration list (to prevent the
3575: syntax error) and filtered out later.
1.1 dsieger 3576:
1.108 rillig 3577: EGFILES= # empty
1.1 dsieger 3578:
1.108 rillig 3579: install-examples:
3580: .for egfile in ${EGFILES}
3581: echo "Installing ${egfile}"
3582: .endfor
3583:
3584: This variant only works when EGFILES does not contain filenames with spaces,
3585: since the .for loop splits on simple whitespace.
3586:
3587: To have a shell command test whether a make variable is empty, use the
3588: following code: ${TEST} -z ${POSSIBLY_EMPTY:Q}"".
1.1 dsieger 3589:
1.6 rillig 3590: Chapter 13. PLIST issues
1.1 dsieger 3591:
3592: Table of Contents
3593:
1.6 rillig 3594: 13.1. RCS ID
3595: 13.2. Semi-automatic PLIST generation
3596: 13.3. Tweaking output of make print-PLIST
3597: 13.4. Variable substitution in PLIST
3598: 13.5. Man page compression
3599: 13.6. Changing PLIST source with PLIST_SRC
3600: 13.7. Platform-specific and differing PLISTs
1.86 wiz 3601: 13.8. Build-specific PLISTs
3602: 13.9. Sharing directories between packages
1.1 dsieger 3603:
3604: The PLIST file contains a package's "packing list", i.e. a list of files that
3605: belong to the package (relative to the ${PREFIX} directory it's been installed
3606: in) plus some additional statements - see the pkg_create(1) man page for a full
3607: list. This chapter addresses some issues that need attention when dealing with
3608: the PLIST file (or files, see below!).
3609:
1.6 rillig 3610: 13.1. RCS ID
1.1 dsieger 3611:
3612: Be sure to add a RCS ID line as the first thing in any PLIST file you write:
3613:
1.2 rillig 3614: @comment $NetBSD$
1.1 dsieger 3615:
1.6 rillig 3616: 13.2. Semi-automatic PLIST generation
1.1 dsieger 3617:
3618: You can use the make print-PLIST command to output a PLIST that matches any new
1.6 rillig 3619: files since the package was extracted. See Section 17.17, "Other helpful
1.1 dsieger 3620: targets" for more information on this target.
3621:
1.6 rillig 3622: 13.3. Tweaking output of make print-PLIST
1.1 dsieger 3623:
3624: The PRINT_PLIST_AWK variable takes a set of AWK patterns and actions that are
3625: used to filter the output of print-PLIST. You can append any chunk of AWK
3626: scripting you like to it, but be careful with quoting.
3627:
3628: For example, to get all files inside the libdata/foo directory removed from the
3629: resulting PLIST:
3630:
3631: PRINT_PLIST_AWK+= /^libdata\/foo/ { next; }
3632:
1.6 rillig 3633: 13.4. Variable substitution in PLIST
1.1 dsieger 3634:
3635: A number of variables are substituted automatically in PLISTs when a package is
3636: installed on a system. This includes the following variables:
3637:
3638: ${MACHINE_ARCH}, ${MACHINE_GNU_ARCH}
3639:
3640: Some packages like emacs and perl embed information about which
3641: architecture they were built on into the pathnames where they install their
3642: files. To handle this case, PLIST will be preprocessed before actually
3643: used, and the symbol "${MACHINE_ARCH}" will be replaced by what uname -p
3644: gives. The same is done if the string ${MACHINE_GNU_ARCH} is embedded in
3645: PLIST somewhere - use this on packages that have GNU autoconf-created
3646: configure scripts.
3647:
3648: Legacy note
3649:
3650: There used to be a symbol "$ARCH" that was replaced by the output of uname
3651: -m, but that's no longer supported and has been removed.
3652:
3653: ${OPSYS}, ${LOWER_OPSYS}, ${OS_VERSION}
3654:
3655: Some packages want to embed the OS name and version into some paths. To do
3656: this, use these variables in the PLIST:
3657:
1.42 asau 3658: + ${OPSYS} - output of "uname -s"
1.1 dsieger 3659:
1.42 asau 3660: + ${LOWER_OPSYS} - lowercase common name (eg. "solaris")
1.1 dsieger 3661:
1.42 asau 3662: + ${OS_VERSION} - "uname -r"
1.1 dsieger 3663:
1.88 tnn 3664: For a list of values which are replaced by default, the output of make help
3665: topic=PLIST_SUBST as well as searching the pkgsrc/mk directory with grep for
3666: PLIST_SUBST should help.
1.1 dsieger 3667:
3668: If you want to change other variables not listed above, you can add variables
3669: and their expansions to this variable in the following way, similar to
1.6 rillig 3670: MESSAGE_SUBST (see Section 11.5, "Optional files"):
1.1 dsieger 3671:
3672: PLIST_SUBST+= SOMEVAR="somevalue"
3673:
3674: This replaces all occurrences of "${SOMEVAR}" in the PLIST with "somevalue".
3675:
1.19 snj 3676: The PLIST_VARS variable can be used to simplify the common case of
3677: conditionally including some PLIST entries. It can be done by adding
3678: PLIST_VARS+=foo and setting the corresponding PLIST.foo variable to yes if the
3679: entry should be included. This will substitute "${PLIST.foo}" in the PLIST with
3680: either """" or ""@comment "". For example, in Makefile:
1.18 mishka 3681:
3682: PLIST_VARS+= foo
3683: .if condition
3684: PLIST.foo= yes
3685: .else
3686:
3687: And then in PLIST:
3688:
3689: @comment $NetBSD$
3690: bin/bar
3691: man/man1/bar.1
3692: ${PLIST.foo}bin/foo
3693: ${PLIST.foo}man/man1/foo.1
3694: ${PLIST.foo}share/bar/foo.data
3695:
1.6 rillig 3696: 13.5. Man page compression
1.1 dsieger 3697:
3698: Man pages should be installed in compressed form if MANZ is set (in
3699: bsd.own.mk), and uncompressed otherwise. To handle this in the PLIST file, the
3700: suffix ".gz" is appended/removed automatically for man pages according to MANZ
3701: and MANCOMPRESSED being set or not, see above for details. This modification of
3702: the PLIST file is done on a copy of it, not PLIST itself.
3703:
1.6 rillig 3704: 13.6. Changing PLIST source with PLIST_SRC
1.1 dsieger 3705:
3706: To use one or more files as source for the PLIST used in generating the binary
3707: package, set the variable PLIST_SRC to the names of that file(s). The files are
3708: later concatenated using cat(1), and the order of things is important. The
3709: default for PLIST_SRC is ${PKGDIR}/PLIST.
3710:
1.6 rillig 3711: 13.7. Platform-specific and differing PLISTs
1.1 dsieger 3712:
3713: Some packages decide to install a different set of files based on the operating
3714: system being used. These differences can be automatically handled by using the
3715: following files:
3716:
3717: * PLIST.common
3718:
3719: * PLIST.${OPSYS}
3720:
3721: * PLIST.${MACHINE_ARCH}
3722:
3723: * PLIST.${OPSYS}-${MACHINE_ARCH}
3724:
3725: * PLIST.common_end
3726:
1.86 wiz 3727: 13.8. Build-specific PLISTs
3728:
3729: Some packages decide to generate hard-to-guess file names during installation
3730: that are hard to wire down.
3731:
3732: In such cases, you can set the GENERATE_PLIST variable to shell code terminated
3733: (with a semicolon) that will output PLIST entries which will be appended to the
3734: PLIST
3735:
3736: You can find one example in editors/xemacs:
3737:
1.111 sevan 3738: GENERATE_PLIST+= ${ECHO} bin/${DISTNAME}-`${WRKSRC}/src/xemacs -sd`.dmp ;
1.86 wiz 3739:
3740: which will append something like bin/xemacs-21.4.23-54e8ea71.dmp to the PLIST.
3741:
3742: 13.9. Sharing directories between packages
1.1 dsieger 3743:
3744: A "shared directory" is a directory where multiple (and unrelated) packages
1.23 jakllsch 3745: install files. These directories were problematic because you had to add
1.1 dsieger 3746: special tricks in the PLIST to conditionally remove them, or have some
3747: centralized package handle them.
3748:
1.23 jakllsch 3749: In pkgsrc, it is now easy: Each package should create directories and install
3750: files as needed; pkg_delete will remove any directories left empty after
3751: uninstalling a package.
1.1 dsieger 3752:
1.23 jakllsch 3753: If a package needs an empty directory to work, create the directory during
3754: installation as usual, and also add an entry to the PLIST:
1.1 dsieger 3755:
1.23 jakllsch 3756: @pkgdir path/to/empty/directory
1.1 dsieger 3757:
1.86 wiz 3758: or take a look at MAKE_DIRS and OWN_DIRS.
3759:
1.6 rillig 3760: Chapter 14. Buildlink methodology
1.1 dsieger 3761:
3762: Table of Contents
3763:
1.6 rillig 3764: 14.1. Converting packages to use buildlink3
3765: 14.2. Writing buildlink3.mk files
1.1 dsieger 3766:
1.6 rillig 3767: 14.2.1. Anatomy of a buildlink3.mk file
1.27 wiz 3768: 14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and BUILDLINK_ABI_DEPENDS.pkg in
3769: buildlink3.mk files
1.1 dsieger 3770:
1.6 rillig 3771: 14.3. Writing builtin.mk files
1.1 dsieger 3772:
1.6 rillig 3773: 14.3.1. Anatomy of a builtin.mk file
3774: 14.3.2. Global preferences for native or pkgsrc software
1.1 dsieger 3775:
3776: Buildlink is a framework in pkgsrc that controls what headers and libraries are
3777: seen by a package's configure and build processes. This is implemented in a two
3778: step process:
3779:
3780: 1. Symlink headers and libraries for dependencies into BUILDLINK_DIR, which by
3781: default is a subdirectory of WRKDIR.
3782:
3783: 2. Create wrapper scripts that are used in place of the normal compiler tools
3784: that translate -I${LOCALBASE}/include and -L${LOCALBASE}/lib into
3785: references to BUILDLINK_DIR. The wrapper scripts also make native compiler
3786: on some operating systems look like GCC, so that packages that expect GCC
3787: won't require modifications to build with those native compilers.
3788:
3789: This normalizes the environment in which a package is built so that the package
3790: may be built consistently despite what other software may be installed. Please
3791: note that the normal system header and library paths, e.g. /usr/include, /usr/
3792: lib, etc., are always searched -- buildlink3 is designed to insulate the
3793: package build from non-system-supplied software.
3794:
1.6 rillig 3795: 14.1. Converting packages to use buildlink3
1.1 dsieger 3796:
1.25 wiz 3797: The process of converting packages to use the buildlink3 framework ("bl3ifying"
3798: ) is fairly straightforward. The things to keep in mind are:
1.1 dsieger 3799:
3800: 1. Ensure that the build always calls the wrapper scripts instead of the
3801: actual toolchain. Some packages are tricky, and the only way to know for
3802: sure is the check ${WRKDIR}/.work.log to see if the wrappers are being
3803: invoked.
3804:
3805: 2. Don't override PREFIX from within the package Makefile, e.g. Java VMs,
3806: standalone shells, etc., because the code to symlink files into $
3807: {BUILDLINK_DIR} looks for files relative to "pkg_info -qp pkgname".
3808:
3809: 3. Remember that only the buildlink3.mk files that you list in a package's
3810: Makefile are added as dependencies for that package.
3811:
3812: If a dependency on a particular package is required for its libraries and
3813: headers, then we replace:
3814:
3815: DEPENDS+= foo>=1.1.0:../../category/foo
3816:
3817: with
3818:
3819: .include "../../category/foo/buildlink3.mk"
3820:
3821: The buildlink3.mk files usually define the required dependencies. If you need a
3822: newer version of the dependency when using buildlink3.mk files, then you can
3823: define it in your Makefile; for example:
3824:
3825: BUILDLINK_API_DEPENDS.foo+= foo>=1.1.0
3826: .include "../../category/foo/buildlink3.mk"
3827:
3828: There are several buildlink3.mk files in pkgsrc/mk that handle special package
3829: issues:
3830:
3831: * bdb.buildlink3.mk chooses either the native or a pkgsrc Berkeley DB
3832: implementation based on the values of BDB_ACCEPTED and BDB_DEFAULT.
3833:
3834: * curses.buildlink3.mk: If the system comes with neither Curses nor NCurses,
3835: this will take care to install the devel/ncurses package.
3836:
3837: * krb5.buildlink3.mk uses the value of KRB5_ACCEPTED to choose between adding
3838: a dependency on Heimdal or MIT-krb5 for packages that require a Kerberos 5
3839: implementation.
3840:
3841: * motif.buildlink3.mk checks for a system-provided Motif installation or adds
1.46 obache 3842: a dependency on x11/lesstif, x11/motif or x11/openmotif. The user can set
3843: MOTIF_TYPE to "dt", "lesstif", "motif" or "openmotif" to choose which Motif
3844: version will be used.
1.1 dsieger 3845:
1.57 wiz 3846: * readline.buildlink3.mk checks for a system-provided GNU readline or
3847: editline (libedit) installation, or adds a dependency on devel/readline,
3848: devel/editline. The user can set READLINE_DEFAULT to choose readline
1.56 ryoon 3849: implementation. If your package really needs GNU readline library, its
3850: Makefile should include devel/readline/buildlink3.mk instead of
3851: readline.buildlink3.mk.
3852:
1.1 dsieger 3853: * oss.buildlink3.mk defines several variables that may be used by packages
3854: that use the Open Sound System (OSS) API.
3855:
1.36 wiz 3856: * pgsql.buildlink3.mk will accept any of the Postgres versions in the
3857: variable PGSQL_VERSIONS_ACCEPTED and default to the version
3858: PGSQL_VERSION_DEFAULT. See the file for more information.
1.1 dsieger 3859:
3860: * pthread.buildlink3.mk uses the value of PTHREAD_OPTS and checks for native
3861: pthreads or adds a dependency on devel/pth as needed.
3862:
3863: * xaw.buildlink3.mk uses the value of XAW_TYPE to choose a particular Athena
3864: widgets library.
3865:
3866: The comments in those buildlink3.mk files provide a more complete description
3867: of how to use them properly.
3868:
1.6 rillig 3869: 14.2. Writing buildlink3.mk files
1.1 dsieger 3870:
3871: A package's buildlink3.mk file is included by Makefiles to indicate the need to
3872: compile and link against header files and libraries provided by the package. A
3873: buildlink3.mk file should always provide enough information to add the correct
3874: type of dependency relationship and include any other buildlink3.mk files that
3875: it needs to find headers and libraries that it needs in turn.
3876:
3877: To generate an initial buildlink3.mk file for further editing, Rene Hexel's
3878: pkgtools/createbuildlink package is highly recommended. For most packages, the
3879: following command will generate a good starting point for buildlink3.mk files:
3880:
3881: % cd pkgsrc/category/pkgdir
3882: % createbuildlink >buildlink3.mk
3883:
3884:
1.6 rillig 3885: 14.2.1. Anatomy of a buildlink3.mk file
1.1 dsieger 3886:
3887: The following real-life example buildlink3.mk is taken from pkgsrc/graphics/
3888: tiff:
3889:
1.19 snj 3890: # $NetBSD: buildlink3.mk,v 1.16 2009/03/20 19:24:45 joerg Exp $
1.1 dsieger 3891:
1.19 snj 3892: BUILDLINK_TREE+= tiff
1.1 dsieger 3893:
1.19 snj 3894: .if !defined(TIFF_BUILDLINK3_MK)
3895: TIFF_BUILDLINK3_MK:=
1.1 dsieger 3896:
1.19 snj 3897: BUILDLINK_API_DEPENDS.tiff+= tiff>=3.6.1
3898: BUILDLINK_ABI_DEPENDS.tiff+= tiff>=3.7.2nb1
1.1 dsieger 3899: BUILDLINK_PKGSRCDIR.tiff?= ../../graphics/tiff
3900:
3901: .include "../../devel/zlib/buildlink3.mk"
3902: .include "../../graphics/jpeg/buildlink3.mk"
1.19 snj 3903: .endif # TIFF_BUILDLINK3_MK
1.1 dsieger 3904:
1.19 snj 3905: BUILDLINK_TREE+= -tiff
1.1 dsieger 3906:
1.19 snj 3907: The header and footer manipulate BUILDLINK_TREE, which is common across all
3908: buildlink3.mk files and is used to track the dependency tree.
1.1 dsieger 3909:
1.19 snj 3910: The main section is protected from multiple inclusion and controls how the
1.1 dsieger 3911: dependency on pkg is added. Several important variables are set in the section:
3912:
3913: * BUILDLINK_API_DEPENDS.pkg is the actual dependency recorded in the
3914: installed package; this should always be set using += to ensure that we're
3915: appending to any pre-existing list of values. This variable should be set
1.27 wiz 3916: to the first version of the package that had an backwards-incompatible API
3917: change.
1.1 dsieger 3918:
3919: * BUILDLINK_PKGSRCDIR.pkg is the location of the pkg pkgsrc directory.
3920:
3921: * BUILDLINK_DEPMETHOD.pkg (not shown above) controls whether we use
3922: BUILD_DEPENDS or DEPENDS to add the dependency on pkg. The build dependency
3923: is selected by setting BUILDLINK_DEPMETHOD.pkg to "build". By default, the
3924: full dependency is used.
3925:
3926: * BUILDLINK_INCDIRS.pkg and BUILDLINK_LIBDIRS.pkg (not shown above) are lists
3927: of subdirectories of ${BUILDLINK_PREFIX.pkg} to add to the header and
3928: library search paths. These default to "include" and "lib" respectively.
3929:
3930: * BUILDLINK_CPPFLAGS.pkg (not shown above) is the list of preprocessor flags
3931: to add to CPPFLAGS, which are passed on to the configure and build phases.
3932: The "-I" option should be avoided and instead be handled using
3933: BUILDLINK_INCDIRS.pkg as above.
3934:
3935: The following variables are all optionally defined within this second section
3936: (protected against multiple inclusion) and control which package files are
3937: symlinked into ${BUILDLINK_DIR} and how their names are transformed during the
3938: symlinking:
3939:
3940: * BUILDLINK_FILES.pkg (not shown above) is a shell glob pattern relative to $
3941: {BUILDLINK_PREFIX.pkg} to be symlinked into ${BUILDLINK_DIR}, e.g. include/
3942: *.h.
3943:
3944: * BUILDLINK_FILES_CMD.pkg (not shown above) is a shell pipeline that outputs
3945: to stdout a list of files relative to ${BUILDLINK_PREFIX.pkg}. The
3946: resulting files are to be symlinked into ${BUILDLINK_DIR}. By default, this
3947: takes the +CONTENTS of a pkg and filters it through $
3948: {BUILDLINK_CONTENTS_FILTER.pkg}.
3949:
3950: * BUILDLINK_CONTENTS_FILTER.pkg (not shown above) is a filter command that
3951: filters +CONTENTS input into a list of files relative to $
1.84 wiz 3952: {BUILDLINK_PREFIX.pkg} on stdout. By default, BUILDLINK_CONTENTS_FILTER.pkg
3953: outputs the contents of the include and lib directories in the package
3954: +CONTENTS.
1.1 dsieger 3955:
3956: * BUILDLINK_FNAME_TRANSFORM.pkg (not shown above) is a list of sed arguments
3957: used to transform the name of the source filename into a destination
3958: filename, e.g. -e "s|/curses.h|/ncurses.h|g".
3959:
1.19 snj 3960: This section can additionally include any buildlink3.mk needed for pkg's
3961: library dependencies. Including these buildlink3.mk files means that the
3962: headers and libraries for these dependencies are also symlinked into $
3963: {BUILDLINK_DIR} whenever the pkg buildlink3.mk file is included. Dependencies
3964: are only added for directly include buildlink3.mk files.
1.1 dsieger 3965:
1.48 wiz 3966: When providing a buildlink3.mk and including other buildlink3.mk files in it,
1.51 wiz 3967: please only add necessary ones, i.e., those whose libraries or header files are
1.48 wiz 3968: automatically exposed when the package is use.
3969:
3970: In particular, if only an executable (bin/foo) is linked against a library,
3971: that library does not need to be propagated in the buildlink3.mk file.
3972:
3973: The following steps should help you decide if a buildlink3.mk file needs to be
3974: included:
3975:
3976: * Look at the installed header files: What headers do they include? The
3977: packages providing these files must be buildlinked.
3978:
1.50 wiz 3979: * Run ldd on all installed libraries and look against what other libraries
3980: they link. Some of the packages providing these probably need to be
3981: buildlinked; however, it's not automatic, since e.g. GTK on some systems
3982: pulls in the X libraries, so they will show up in the ldd output, while on
1.51 wiz 3983: others (like OS X) it won't. ldd output can thus only be used as a hint.
1.50 wiz 3984:
1.27 wiz 3985: 14.2.2. Updating BUILDLINK_API_DEPENDS.pkg and BUILDLINK_ABI_DEPENDS.pkg in
3986: buildlink3.mk files
1.1 dsieger 3987:
1.27 wiz 3988: These two variables differ in that one describes source compatibility (API) and
3989: the other binary compatibility (ABI). The difference is that a change in the
3990: API breaks compilation of programs while changes in the ABI stop compiled
3991: programs from running.
3992:
1.28 wiz 3993: Changes to the BUILDLINK_API_DEPENDS.pkg variable in a buildlink3.mk file
3994: happen very rarely. One possible reason is that all packages depending on this
3995: already need a newer version. In case it is bumped see the description below.
1.27 wiz 3996:
3997: The most common example of an ABI change is that the major version of a shared
3998: library is increased. In this case, BUILDLINK_ABI_DEPENDS.pkg should be
3999: adjusted to require at least the new package version. Then the packages that
4000: depend on this package need their PKGREVISIONs increased and, if they have
4001: buildlink3.mk files, their BUILDLINK_ABI_DEPENDS.pkg adjusted, too. This is
4002: needed so pkgsrc will require the correct package dependency and not settle for
4003: an older one when building the source.
1.1 dsieger 4004:
1.108 rillig 4005: See Section 19.1.5, "Handling dependencies" for more information about
1.1 dsieger 4006: dependencies on other packages, including the BUILDLINK_ABI_DEPENDS and
4007: ABI_DEPENDS definitions.
4008:
4009: Please take careful consideration before adjusting BUILDLINK_API_DEPENDS.pkg or
4010: BUILDLINK_ABI_DEPENDS.pkg as we don't want to cause unneeded package deletions
4011: and rebuilds. In many cases, new versions of packages work just fine with older
4012: dependencies.
4013:
4014: Also it is not needed to set BUILDLINK_ABI_DEPENDS.pkg when it is identical to
4015: BUILDLINK_API_DEPENDS.pkg.
4016:
1.6 rillig 4017: 14.3. Writing builtin.mk files
1.1 dsieger 4018:
4019: Some packages in pkgsrc install headers and libraries that coincide with
4020: headers and libraries present in the base system. Aside from a buildlink3.mk
4021: file, these packages should also include a builtin.mk file that includes the
4022: necessary checks to decide whether using the built-in software or the pkgsrc
4023: software is appropriate.
4024:
4025: The only requirements of a builtin.mk file for pkg are:
4026:
4027: 1. It should set USE_BUILTIN.pkg to either "yes" or "no" after it is included.
4028:
4029: 2. It should not override any USE_BUILTIN.pkg which is already set before the
4030: builtin.mk file is included.
4031:
4032: 3. It should be written to allow multiple inclusion. This is very important
4033: and takes careful attention to Makefile coding.
4034:
1.6 rillig 4035: 14.3.1. Anatomy of a builtin.mk file
1.1 dsieger 4036:
4037: The following is the recommended template for builtin.mk files:
4038:
4039: .if !defined(IS_BUILTIN.foo)
4040: #
4041: # IS_BUILTIN.foo is set to "yes" or "no" depending on whether "foo"
4042: # genuinely exists in the system or not.
4043: #
4044: IS_BUILTIN.foo?= no
4045:
4046: # BUILTIN_PKG.foo should be set here if "foo" is built-in and its package
4047: # version can be determined.
4048: #
4049: . if !empty(IS_BUILTIN.foo:M[yY][eE][sS])
4050: BUILTIN_PKG.foo?= foo-1.0
4051: . endif
4052: .endif # IS_BUILTIN.foo
4053:
4054: .if !defined(USE_BUILTIN.foo)
4055: USE_BUILTIN.foo?= ${IS_BUILTIN.foo}
4056: . if defined(BUILTIN_PKG.foo)
4057: . for _depend_ in ${BUILDLINK_API_DEPENDS.foo}
4058: . if !empty(USE_BUILTIN.foo:M[yY][eE][sS])
4059: USE_BUILTIN.foo!= \
4060: ${PKG_ADMIN} pmatch '${_depend_}' ${BUILTIN_PKG.foo} \
4061: && ${ECHO} "yes" || ${ECHO} "no"
4062: . endif
4063: . endfor
4064: . endif
4065: .endif # USE_BUILTIN.foo
4066:
4067: CHECK_BUILTIN.foo?= no
4068: .if !empty(CHECK_BUILTIN.foo:M[nN][oO])
4069: #
4070: # Here we place code that depends on whether USE_BUILTIN.foo is set to
4071: # "yes" or "no".
4072: #
4073: .endif # CHECK_BUILTIN.foo
4074:
4075: The first section sets IS_BUILTIN.pkg depending on if pkg really exists in the
4076: base system. This should not be a base system software with similar
4077: functionality to pkg; it should only be "yes" if the actual package is included
4078: as part of the base system. This variable is only used internally within the
4079: builtin.mk file.
4080:
4081: The second section sets BUILTIN_PKG.pkg to the version of pkg in the base
4082: system if it exists (if IS_BUILTIN.pkg is "yes"). This variable is only used
4083: internally within the builtin.mk file.
4084:
4085: The third section sets USE_BUILTIN.pkg and is required in all builtin.mk files.
4086: The code in this section must make the determination whether the built-in
4087: software is adequate to satisfy the dependencies listed in
4088: BUILDLINK_API_DEPENDS.pkg. This is typically done by comparing BUILTIN_PKG.pkg
1.25 wiz 4089: against each of the dependencies in BUILDLINK_API_DEPENDS.pkg. USE_BUILTIN.pkg
1.1 dsieger 4090: must be set to the correct value by the end of the builtin.mk file. Note that
4091: USE_BUILTIN.pkg may be "yes" even if IS_BUILTIN.pkg is "no" because we may make
4092: the determination that the built-in version of the software is similar enough
4093: to be used as a replacement.
4094:
4095: The last section is guarded by CHECK_BUILTIN.pkg, and includes code that uses
4096: the value of USE_BUILTIN.pkg set in the previous section. This typically
4097: includes, e.g., adding additional dependency restrictions and listing
4098: additional files to symlink into ${BUILDLINK_DIR} (via BUILDLINK_FILES.pkg).
4099:
1.6 rillig 4100: 14.3.2. Global preferences for native or pkgsrc software
1.1 dsieger 4101:
4102: When building packages, it's possible to choose whether to set a global
4103: preference for using either the built-in (native) version or the pkgsrc version
4104: of software to satisfy a dependency. This is controlled by setting
1.25 wiz 4105: PREFER_PKGSRC and PREFER_NATIVE. These variables take values of either "yes", "
4106: no", or a list of packages. PREFER_PKGSRC tells pkgsrc to use the pkgsrc
1.1 dsieger 4107: versions of software, while PREFER_NATIVE tells pkgsrc to use the built-in
4108: versions. Preferences are determined by the most specific instance of the
4109: package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in
4110: neither or in both variables, then PREFER_PKGSRC has precedence over
4111: PREFER_NATIVE. For example, to require using pkgsrc versions of software for
4112: all but the most basic bits on a NetBSD system, you can set:
4113:
4114: PREFER_PKGSRC= yes
4115: PREFER_NATIVE= getopt skey tcp_wrappers
4116:
4117: A package must have a builtin.mk file to be listed in PREFER_NATIVE, otherwise
4118: it is simply ignored in that list.
4119:
1.6 rillig 4120: Chapter 15. The pkginstall framework
1.1 dsieger 4121:
4122: Table of Contents
4123:
1.6 rillig 4124: 15.1. Files and directories outside the installation prefix
1.1 dsieger 4125:
1.6 rillig 4126: 15.1.1. Directory manipulation
4127: 15.1.2. File manipulation
1.1 dsieger 4128:
1.6 rillig 4129: 15.2. Configuration files
1.1 dsieger 4130:
1.6 rillig 4131: 15.2.1. How PKG_SYSCONFDIR is set
4132: 15.2.2. Telling the software where configuration files are
4133: 15.2.3. Patching installations
4134: 15.2.4. Disabling handling of configuration files
1.1 dsieger 4135:
1.6 rillig 4136: 15.3. System startup scripts
1.1 dsieger 4137:
1.6 rillig 4138: 15.3.1. Disabling handling of system startup scripts
1.1 dsieger 4139:
1.6 rillig 4140: 15.4. System users and groups
4141: 15.5. System shells
1.1 dsieger 4142:
1.6 rillig 4143: 15.5.1. Disabling shell registration
1.1 dsieger 4144:
1.6 rillig 4145: 15.6. Fonts
1.1 dsieger 4146:
1.6 rillig 4147: 15.6.1. Disabling automatic update of the fonts databases
1.1 dsieger 4148:
4149: This chapter describes the framework known as pkginstall, whose key features
4150: are:
4151:
4152: * Generic installation and manipulation of directories and files outside the
4153: pkgsrc-handled tree, LOCALBASE.
4154:
4155: * Automatic handling of configuration files during installation, provided
4156: that packages are correctly designed.
4157:
4158: * Generation and installation of system startup scripts.
4159:
4160: * Registration of system users and groups.
4161:
4162: * Registration of system shells.
4163:
4164: * Automatic updating of fonts databases.
4165:
4166: The following sections inspect each of the above points in detail.
4167:
4168: You may be thinking that many of the things described here could be easily done
4169: with simple code in the package's post-installation target (post-install). This
4170: is incorrect, as the code in them is only executed when building from source.
4171: Machines using binary packages could not benefit from it at all (as the code
4172: itself could be unavailable). Therefore, the only way to achieve any of the
4173: items described above is by means of the installation scripts, which are
4174: automatically generated by pkginstall.
4175:
1.6 rillig 4176: 15.1. Files and directories outside the installation prefix
1.1 dsieger 4177:
4178: As you already know, the PLIST file holds a list of files and directories that
4179: belong to a package. The names used in it are relative to the installation
4180: prefix (${PREFIX}), which means that it cannot register files outside this
4181: directory (absolute path names are not allowed). Despite this restriction, some
4182: packages need to install files outside this location; e.g., under ${VARBASE} or
4183: ${PKG_SYSCONFDIR}. The only way to achieve this is to create such files during
4184: installation time by using installation scripts.
4185:
4186: The generic installation scripts are shell scripts that can contain arbitrary
4187: code. The list of scripts to execute is taken from the INSTALL_FILE variable,
4188: which defaults to INSTALL. A similar variable exists for package removal
4189: (DEINSTALL_FILE, whose default is DEINSTALL). These scripts can run arbitrary
4190: commands, so they have the potential to create and manage files anywhere in the
4191: file system.
4192:
4193: Using these general installation files is not recommended, but may be needed in
4194: some special cases. One reason for avoiding them is that the user has to trust
4195: the packager that there is no unwanted or simply erroneous code included in the
4196: installation script. Also, previously there were many similar scripts for the
4197: same functionality, and fixing a common error involved finding and changing all
4198: of them.
4199:
4200: The pkginstall framework offers another, standardized way. It provides generic
4201: scripts to abstract the manipulation of such files and directories based on
4202: variables set in the package's Makefile. The rest of this section describes
4203: these variables.
4204:
1.6 rillig 4205: 15.1.1. Directory manipulation
1.1 dsieger 4206:
4207: The following variables can be set to request the creation of directories
4208: anywhere in the file system:
4209:
4210: * MAKE_DIRS and OWN_DIRS contain a list of directories that should be created
4211: and should attempt to be destroyed by the installation scripts. The
4212: difference between the two is that the latter prompts the administrator to
4213: remove any directories that may be left after deinstallation (because they
1.108 rillig 4214: were not empty), while the former does not. Example:
4215:
4216: MAKE_DIRS+= ${VARBASE}/foo/private
1.1 dsieger 4217:
4218: * MAKE_DIRS_PERMS and OWN_DIRS_PERMS contain a list of tuples describing
4219: which directories should be created and should attempt to be destroyed by
4220: the installation scripts. Each tuple holds the following values, separated
4221: by spaces: the directory name, its owner, its group and its numerical mode.
4222: For example:
4223:
1.108 rillig 4224: MAKE_DIRS_PERMS+= ${VARBASE}/foo/private \
4225: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
1.1 dsieger 4226:
4227: The difference between the two is exactly the same as their non-PERMS
4228: counterparts.
4229:
1.6 rillig 4230: 15.1.2. File manipulation
1.1 dsieger 4231:
4232: Creating non-empty files outside the installation prefix is tricky because the
4233: PLIST forces all files to be inside it. To overcome this problem, the only
4234: solution is to extract the file in the known place (i.e., inside the
4235: installation prefix) and copy it to the appropriate location during
4236: installation (done by the installation scripts generated by pkginstall). We
4237: will call the former the master file in the following paragraphs, which
4238: describe the variables that can be used to automatically and consistently
4239: handle files outside the installation prefix:
4240:
1.31 wiz 4241: * CONF_FILES and REQD_FILES are pairs of master and target files. During
1.1 dsieger 4242: installation time, the master file is copied to the target one if and only
4243: if the latter does not exist. Upon deinstallation, the target file is
4244: removed provided that it was not modified by the installation.
4245:
4246: The difference between the two is that the latter prompts the administrator
4247: to remove any files that may be left after deinstallation (because they
4248: were not empty), while the former does not.
4249:
1.31 wiz 4250: * CONF_FILES_PERMS and REQD_FILES_PERMS contain tuples describing master
1.1 dsieger 4251: files as well as their target locations. For each of them, it also
4252: specifies their owner, their group and their numeric permissions, in this
4253: order. For example:
4254:
1.108 rillig 4255: REQD_FILES_PERMS+= ${PREFIX}/share/somefile ${VARBASE}/somefile \
4256: ${REAL_ROOT_USER} ${REAL_ROOT_GROUP} 0700
1.1 dsieger 4257:
4258: The difference between the two is exactly the same as their non-PERMS
4259: counterparts.
4260:
1.6 rillig 4261: 15.2. Configuration files
1.1 dsieger 4262:
4263: Configuration files are special in the sense that they are installed in their
4264: own specific directory, PKG_SYSCONFDIR, and need special treatment during
4265: installation (most of which is automated by pkginstall). The main concept you
4266: must bear in mind is that files marked as configuration files are automatically
4267: copied to the right place (somewhere inside PKG_SYSCONFDIR) during installation
4268: if and only if they didn't exist before. Similarly, they will not be removed if
4269: they have local modifications. This ensures that administrators never lose any
4270: custom changes they may have made.
4271:
1.6 rillig 4272: 15.2.1. How PKG_SYSCONFDIR is set
1.1 dsieger 4273:
4274: As said before, the PKG_SYSCONFDIR variable specifies where configuration files
4275: shall be installed. Its contents are set based upon the following variables:
4276:
4277: * PKG_SYSCONFBASE: The configuration's root directory. Defaults to ${PREFIX}/
4278: etc although it may be overridden by the user to point to his preferred
4279: location (e.g., /etc, /etc/pkg, etc.). Packages must not use it directly.
4280:
4281: * PKG_SYSCONFSUBDIR: A subdirectory of PKG_SYSCONFBASE under which the
4282: configuration files for the package being built shall be installed. The
4283: definition of this variable only makes sense in the package's Makefile
4284: (i.e., it is not user-customizable).
4285:
1.68 asau 4286: As an example, consider the Apache package, www/apache24, which places its
1.1 dsieger 4287: configuration files under the httpd/ subdirectory of PKG_SYSCONFBASE. This
4288: should be set in the package Makefile.
4289:
4290: * PKG_SYSCONFVAR: Specifies the name of the variable that holds this
4291: package's configuration directory (if different from PKG_SYSCONFBASE). It
4292: defaults to PKGBASE's value, and is always prefixed with PKG_SYSCONFDIR.
4293:
4294: * PKG_SYSCONFDIR.${PKG_SYSCONFVAR}: Holds the directory where the
4295: configuration files for the package identified by PKG_SYSCONFVAR's shall be
4296: placed.
4297:
4298: Based on the above variables, pkginstall determines the value of
4299: PKG_SYSCONFDIR, which is the only variable that can be used within a package to
4300: refer to its configuration directory. The algorithm used to set its value is
4301: basically the following:
4302:
4303: 1. If PKG_SYSCONFDIR.${PKG_SYSCONFVAR} is set, its value is used.
4304:
4305: 2. If the previous variable is not defined but PKG_SYSCONFSUBDIR is set in the
4306: package's Makefile, the resulting value is ${PKG_SYSCONFBASE}/$
4307: {PKG_SYSCONFSUBDIR}.
4308:
4309: 3. Otherwise, it is set to ${PKG_SYSCONFBASE}.
4310:
4311: It is worth mentioning that ${PKG_SYSCONFDIR} is automatically added to
1.16 jnemeth 4312: OWN_DIRS. See Section 15.1.1, "Directory manipulation" what this means. This
4313: does not apply to subdirectories of ${PKG_SYSCONFDIR}, they still have to be
4314: created with OWN_DIRS or MAKE_DIRS.
1.1 dsieger 4315:
1.6 rillig 4316: 15.2.2. Telling the software where configuration files are
1.1 dsieger 4317:
4318: Given that pkgsrc (and users!) expect configuration files to be in a known
4319: place, you need to teach each package where it shall install its files. In some
4320: cases you will have to patch the package Makefiles to achieve it. If you are
4321: lucky, though, it may be as easy as passing an extra flag to the configuration
4322: script; this is the case of GNU Autoconf- generated files:
4323:
4324: CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
4325:
4326: Note that this specifies where the package has to look for its configuration
4327: files, not where they will be originally installed (although the difference is
4328: never explicit, unfortunately).
4329:
1.6 rillig 4330: 15.2.3. Patching installations
1.1 dsieger 4331:
4332: As said before, pkginstall automatically handles configuration files. This
4333: means that the packages themselves must not touch the contents of $
4334: {PKG_SYSCONFDIR} directly. Bad news is that many software installation scripts
4335: will, out of the box, mess with the contents of that directory. So what is the
4336: correct procedure to fix this issue?
4337:
4338: You must teach the package (usually by manually patching it) to install any
4339: configuration files under the examples hierarchy, share/examples/${PKGBASE}/.
4340: This way, the PLIST registers them and the administrator always has the
4341: original copies available.
4342:
4343: Once the required configuration files are in place (i.e., under the examples
4344: hierarchy), the pkginstall framework can use them as master copies during the
4345: package installation to update what is in ${PKG_SYSCONFDIR}. To achieve this,
4346: the variables CONF_FILES and CONF_FILES_PERMS are used. Check out
1.6 rillig 4347: Section 15.1.2, "File manipulation" for information about their syntax and
1.1 dsieger 4348: their purpose. Here is an example, taken from the mail/mutt package:
4349:
4350: EGDIR= ${PREFIX}/share/doc/mutt/samples
4351: CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
4352:
4353: Note that the EGDIR variable is specific to that package and has no meaning
4354: outside it.
4355:
1.6 rillig 4356: 15.2.4. Disabling handling of configuration files
1.1 dsieger 4357:
4358: The automatic copying of config files can be toggled by setting the environment
4359: variable PKG_CONFIG prior to package installation.
4360:
1.6 rillig 4361: 15.3. System startup scripts
1.1 dsieger 4362:
4363: System startup scripts are special files because they must be installed in a
4364: place known by the underlying OS, usually outside the installation prefix.
1.6 rillig 4365: Therefore, the same rules described in Section 15.1, "Files and directories
1.1 dsieger 4366: outside the installation prefix" apply, and the same solutions can be used.
4367: However, pkginstall provides a special mechanism to handle these files.
4368:
4369: In order to provide system startup scripts, the package has to:
4370:
4371: 1. Store the script inside ${FILESDIR}, with the .sh suffix appended.
4372: Considering the print/cups package as an example, it has a cupsd.sh in its
4373: files directory.
4374:
4375: 2. Tell pkginstall to handle it, appending the name of the script, without its
4376: extension, to the RCD_SCRIPTS variable. Continuing the previous example:
4377:
4378: RCD_SCRIPTS+= cupsd
4379:
4380: Once this is done, pkginstall will do the following steps for each script in an
4381: automated fashion:
4382:
4383: 1. Process the file found in the files directory applying all the
4384: substitutions described in the FILES_SUBST variable.
4385:
4386: 2. Copy the script from the files directory to the examples hierarchy, $
4387: {PREFIX}/share/examples/rc.d/. Note that this master file must be
4388: explicitly registered in the PLIST.
4389:
4390: 3. Add code to the installation scripts to copy the startup script from the
4391: examples hierarchy into the system-wide startup scripts directory.
4392:
1.6 rillig 4393: 15.3.1. Disabling handling of system startup scripts
1.1 dsieger 4394:
4395: The automatic copying of config files can be toggled by setting the environment
4396: variable PKG_RCD_SCRIPTS prior to package installation. Note that the scripts
4397: will be always copied inside the examples hierarchy, ${PREFIX}/share/examples/
4398: rc.d/, no matter what the value of this variable is.
4399:
1.6 rillig 4400: 15.4. System users and groups
1.1 dsieger 4401:
4402: If a package needs to create special users and/or groups during installation,
4403: it can do so by using the pkginstall framework.
4404:
4405: Users can be created by adding entries to the PKG_USERS variable. Each entry
4406: has the following syntax:
4407:
4408: user:group
4409:
4410: Further specification of user details may be done by setting per-user
4411: variables. PKG_UID.user is the numeric UID for the user. PKG_GECOS.user is the
4412: user's description or comment. PKG_HOME.user is the user's home directory, and
4413: defaults to /nonexistent if not specified. PKG_SHELL.user is the user's shell,
4414: and defaults to /sbin/nologin if not specified.
4415:
4416: Similarly, groups can be created by adding entries to the PKG_GROUPS variable,
4417: whose syntax is:
4418:
4419: group
4420:
4421: The numeric GID of the group may be set by defining PKG_GID.group.
4422:
4423: If a package needs to create the users and groups at an earlier stage, then it
4424: can set USERGROUP_PHASE to either configure or build to indicate the phase
4425: before which the users and groups are created. In this case, the numeric UIDs
4426: and GIDs of the created users and groups are automatically hardcoded into the
4427: final installation scripts.
4428:
1.6 rillig 4429: 15.5. System shells
1.1 dsieger 4430:
4431: Packages that install system shells should register them in the shell database,
4432: /etc/shells, to make things easier to the administrator. This must be done from
4433: the installation scripts to keep binary packages working on any system.
4434: pkginstall provides an easy way to accomplish this task.
4435:
4436: When a package provides a shell interpreter, it has to set the PKG_SHELL
4437: variable to its absolute file name. This will add some hooks to the
4438: installation scripts to handle it. Consider the following example, taken from
4439: shells/zsh:
4440:
4441: PKG_SHELL= ${PREFIX}/bin/zsh
4442:
1.6 rillig 4443: 15.5.1. Disabling shell registration
1.1 dsieger 4444:
4445: The automatic registration of shell interpreters can be disabled by the
4446: administrator by setting the PKG_REGISTER_SHELLS environment variable to NO.
4447:
1.6 rillig 4448: 15.6. Fonts
1.1 dsieger 4449:
4450: Packages that install X11 fonts should update the database files that index the
4451: fonts within each fonts directory. This can easily be accomplished within the
4452: pkginstall framework.
4453:
4454: When a package installs X11 fonts, it must list the directories in which fonts
4455: are installed in the FONTS_DIRS.type variables, where type can be one of "ttf",
4456: "type1" or "x11". This will add hooks to the installation scripts to run the
4457: appropriate commands to update the fonts database files within each of those
4458: directories. For convenience, if the directory path is relative, it is taken to
4459: be relative to the package's installation prefix. Consider the following
4460: example, taken from fonts/dbz-ttf:
4461:
1.67 wiz 4462: FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
1.1 dsieger 4463:
1.6 rillig 4464: 15.6.1. Disabling automatic update of the fonts databases
1.1 dsieger 4465:
4466: The automatic update of fonts databases can be disabled by the administrator by
4467: setting the PKG_UPDATE_FONTS_DB environment variable to NO.
4468:
1.6 rillig 4469: Chapter 16. Options handling
1.1 dsieger 4470:
4471: Table of Contents
4472:
1.6 rillig 4473: 16.1. Global default options
4474: 16.2. Converting packages to use bsd.options.mk
4475: 16.3. Option Names
1.7 rillig 4476: 16.4. Determining the options of dependencies
1.1 dsieger 4477:
4478: Many packages have the ability to be built to support different sets of
4479: features. bsd.options.mk is a framework in pkgsrc that provides generic
4480: handling of those options that determine different ways in which the packages
4481: can be built. It's possible for the user to specify exactly which sets of
4482: options will be built into a package or to allow a set of global default
4483: options apply.
4484:
1.7 rillig 4485: There are two broad classes of behaviors that one might want to control via
4486: options. One is whether some particular feature is enabled in a program that
4487: will be built anyway, often by including or not including a dependency on some
4488: other package. The other is whether or not an additional program will be built
4489: as part of the package. Generally, it is better to make a split package for
4490: such additional programs instead of using options, because it enables binary
4491: packages to be built which can then be added separately. For example, the foo
4492: package might have minimal dependencies (those packages without which foo
4493: doesn't make sense), and then the foo-gfoo package might include the GTK
4494: frontend program gfoo. This is better than including a gtk option to foo that
4495: adds gfoo, because either that option is default, in which case binary users
4496: can't get foo without gfoo, or not default, in which case they can't get gfoo.
4497: With split packages, they can install foo without having GTK, and later decide
4498: to install gfoo (pulling in GTK at that time). This is an advantage to source
4499: users too, avoiding the need for rebuilds.
4500:
4501: Plugins with widely varying dependencies should usually be split instead of
4502: options.
4503:
4504: It is often more work to maintain split packages, especially if the upstream
4505: package does not support this. The decision of split vs. option should be made
4506: based on the likelihood that users will want or object to the various pieces,
4507: the size of the dependencies that are included, and the amount of work.
4508:
4509: A further consideration is licensing. Non-free parts, or parts that depend on
4510: non-free dependencies (especially plugins) should almost always be split if
4511: feasible.
4512:
1.6 rillig 4513: 16.1. Global default options
1.1 dsieger 4514:
4515: Global default options are listed in PKG_DEFAULT_OPTIONS, which is a list of
4516: the options that should be built into every package if that option is
1.4 rillig 4517: supported. This variable should be set in mk.conf.
1.1 dsieger 4518:
1.6 rillig 4519: 16.2. Converting packages to use bsd.options.mk
1.1 dsieger 4520:
4521: The following example shows how bsd.options.mk should be used by the
4522: hypothetical ``wibble'' package, either in the package Makefile, or in a file,
4523: e.g. options.mk, that is included by the main package Makefile.
4524:
4525: PKG_OPTIONS_VAR= PKG_OPTIONS.wibble
4526: PKG_SUPPORTED_OPTIONS= wibble-foo ldap
4527: PKG_OPTIONS_OPTIONAL_GROUPS= database
4528: PKG_OPTIONS_GROUP.database= mysql pgsql
4529: PKG_SUGGESTED_OPTIONS= wibble-foo
4530: PKG_OPTIONS_LEGACY_VARS+= WIBBLE_USE_OPENLDAP:ldap
4531: PKG_OPTIONS_LEGACY_OPTS+= foo:wibble-foo
4532:
4533: .include "../../mk/bsd.prefs.mk"
4534:
4535: # this package was previously named wibble2
4536: .if defined(PKG_OPTIONS.wibble2)
4537: PKG_LEGACY_OPTIONS+= ${PKG_OPTIONS.wibble2}
4538: PKG_OPTIONS_DEPRECATED_WARNINGS+= \
4539: "Deprecated variable PKG_OPTIONS.wibble2 used, use ${PKG_OPTIONS_VAR} instead."
4540: .endif
4541:
4542: .include "../../mk/bsd.options.mk"
4543:
4544: # Package-specific option-handling
4545:
4546: ###
4547: ### FOO support
4548: ###
4549: .if !empty(PKG_OPTIONS:Mwibble-foo)
4550: CONFIGURE_ARGS+= --enable-foo
4551: .endif
4552:
4553: ###
4554: ### LDAP support
4555: ###
4556: .if !empty(PKG_OPTIONS:Mldap)
4557: . include "../../databases/openldap-client/buildlink3.mk"
4558: CONFIGURE_ARGS+= --enable-ldap=${BUILDLINK_PREFIX.openldap-client}
4559: .endif
4560:
4561: ###
4562: ### database support
4563: ###
4564: .if !empty(PKG_OPTIONS:Mmysql)
4565: . include "../../mk/mysql.buildlink3.mk"
4566: .endif
4567: .if !empty(PKG_OPTIONS:Mpgsql)
4568: . include "../../mk/pgsql.buildlink3.mk"
4569: .endif
4570:
4571: The first section contains the information about which build options are
4572: supported by the package, and any default options settings if needed.
4573:
4574: 1. PKG_OPTIONS_VAR is the name of the make(1) variable that the user can set
4575: to override the default options. It should be set to PKG_OPTIONS.pkgbase.
4576: Do not set it to PKG_OPTIONS.${PKGBASE}, since PKGBASE is not defined at
4577: the point where the options are processed.
4578:
4579: 2. PKG_SUPPORTED_OPTIONS is a list of build options supported by the package.
4580:
4581: 3. PKG_OPTIONS_OPTIONAL_GROUPS is a list of names of groups of mutually
4582: exclusive options. The options in each group are listed in
4583: PKG_OPTIONS_GROUP.groupname. The most specific setting of any option from
4584: the group takes precedence over all other options in the group. Options
4585: from the groups will be automatically added to PKG_SUPPORTED_OPTIONS.
4586:
4587: 4. PKG_OPTIONS_REQUIRED_GROUPS is like PKG_OPTIONS_OPTIONAL_GROUPS, but
4588: building the packages will fail if no option from the group is selected.
4589:
4590: 5. PKG_OPTIONS_NONEMPTY_SETS is a list of names of sets of options. At least
4591: one option from each set must be selected. The options in each set are
4592: listed in PKG_OPTIONS_SET.setname. Options from the sets will be
4593: automatically added to PKG_SUPPORTED_OPTIONS. Building the package will
4594: fail if no option from the set is selected.
4595:
4596: 6. PKG_SUGGESTED_OPTIONS is a list of build options which are enabled by
4597: default.
4598:
4599: 7. PKG_OPTIONS_LEGACY_VARS is a list of "USE_VARIABLE:option" pairs that map
1.4 rillig 4600: legacy mk.conf variables to their option counterparts. Pairs should be
1.1 dsieger 4601: added with "+=" to keep the listing of global legacy variables. A warning
4602: will be issued if the user uses a legacy variable.
4603:
4604: 8. PKG_OPTIONS_LEGACY_OPTS is a list of "old-option:new-option" pairs that map
4605: options that have been renamed to their new counterparts. Pairs should be
4606: added with "+=" to keep the listing of global legacy options. A warning
4607: will be issued if the user uses a legacy option.
4608:
4609: 9. PKG_LEGACY_OPTIONS is a list of options implied by deprecated variables
4610: used. This can be used for cases that neither PKG_OPTIONS_LEGACY_VARS nor
4611: PKG_OPTIONS_LEGACY_OPTS can handle, e. g. when PKG_OPTIONS_VAR is renamed.
4612:
4613: 10. PKG_OPTIONS_DEPRECATED_WARNINGS is a list of warnings about deprecated
4614: variables or options used, and what to use instead.
4615:
4616: A package should never modify PKG_DEFAULT_OPTIONS or the variable named in
4617: PKG_OPTIONS_VAR. These are strictly user-settable. To suggest a default set of
4618: options, use PKG_SUGGESTED_OPTIONS.
4619:
4620: PKG_OPTIONS_VAR must be defined before including bsd.options.mk. If none of
4621: PKG_SUPPORTED_OPTIONS, PKG_OPTIONS_OPTIONAL_GROUPS, and
4622: PKG_OPTIONS_REQUIRED_GROUPS are defined (as can happen with platform-specific
4623: options if none of them is supported on the current platform), PKG_OPTIONS is
4624: set to the empty list and the package is otherwise treated as not using the
4625: options framework.
4626:
4627: After the inclusion of bsd.options.mk, the variable PKG_OPTIONS contains the
4628: list of selected build options, properly filtered to remove unsupported and
4629: duplicate options.
4630:
4631: The remaining sections contain the logic that is specific to each option. The
4632: correct way to check for an option is to check whether it is listed in
4633: PKG_OPTIONS:
4634:
4635: .if !empty(PKG_OPTIONS:Moption)
4636:
1.6 rillig 4637: 16.3. Option Names
1.1 dsieger 4638:
4639: Options that enable similar features in different packages (like optional
4640: support for a library) should use a common name in all packages that support it
4641: (like the name of the library). If another package already has an option with
4642: the same meaning, use the same name.
4643:
4644: Options that enable features specific to one package, where it's unlikely that
4645: another (unrelated) package has the same (or a similar) optional feature,
4646: should use a name prefixed with pkgname-.
4647:
4648: If a group of related packages share an optional feature specific to that
4649: group, prefix it with the name of the "main" package (e. g.
4650: djbware-errno-hack).
4651:
4652: For new options, add a line to mk/defaults/options.description. Lines have two
4653: fields, separated by tab. The first field is the option name, the second its
4654: description. The description should be a whole sentence (starting with an
4655: uppercase letter and ending with a period) that describes what enabling the
4656: option does. E. g. "Enable ispell support." The file is sorted by option names.
4657:
1.7 rillig 4658: 16.4. Determining the options of dependencies
4659:
4660: When writing buildlink3.mk files, it is often necessary to list different
4661: dependencies based on the options with which the package was built. For
4662: querying these options, the file pkgsrc/mk/pkg-build-options.mk should be used.
4663: A typical example looks like this:
4664:
4665: pkgbase := libpurple
4666: .include "../../mk/pkg-build-options.mk"
4667:
4668: .if !empty(PKG_BUILD_OPTIONS.libpurple:Mdbus)
4669: ...
4670: .endif
4671:
4672: Including pkg-build-options.mk here will set the variable
4673: PKG_BUILD_OPTIONS.libpurple to the build options of the libpurple package,
4674: which can then be queried like PKG_OPTIONS in the options.mk file. See the file
4675: pkg-build-options.mk for more details.
4676:
1.6 rillig 4677: Chapter 17. The build process
1.1 dsieger 4678:
4679: Table of Contents
4680:
1.6 rillig 4681: 17.1. Introduction
4682: 17.2. Program location
4683: 17.3. Directories used during the build process
4684: 17.4. Running a phase
4685: 17.5. The fetch phase
4686:
4687: 17.5.1. What to fetch and where to get it from
4688: 17.5.2. How are the files fetched?
4689:
4690: 17.6. The checksum phase
4691: 17.7. The extract phase
4692: 17.8. The patch phase
4693: 17.9. The tools phase
4694: 17.10. The wrapper phase
4695: 17.11. The configure phase
4696: 17.12. The build phase
4697: 17.13. The test phase
4698: 17.14. The install phase
4699: 17.15. The package phase
4700: 17.16. Cleaning up
4701: 17.17. Other helpful targets
1.1 dsieger 4702:
1.6 rillig 4703: 17.1. Introduction
1.1 dsieger 4704:
4705: This chapter gives a detailed description on how a package is built. Building a
4706: package is separated into different phases (for example fetch, build, install),
1.19 snj 4707: all of which are described in the following sections. Each phase is split into
4708: so-called stages, which take the name of the containing phase, prefixed by one
4709: of pre-, do- or post-. (Examples are pre-configure, post-build.) Most of the
4710: actual work is done in the do-* stages.
1.1 dsieger 4711:
4712: Never override the regular targets (like fetch), if you have to, override the
4713: do-* ones instead.
4714:
4715: The basic steps for building a program are always the same. First the program's
4716: source (distfile) must be brought to the local system and then extracted. After
4717: any pkgsrc-specific patches to compile properly are applied, the software can
4718: be configured, then built (usually by compiling), and finally the generated
4719: binaries, etc. can be put into place on the system.
4720:
4721: To get more details about what is happening at each step, you can set the
4722: PKG_VERBOSE variable, or the PATCH_DEBUG variable if you are just interested in
4723: more details about the patch step.
4724:
1.6 rillig 4725: 17.2. Program location
1.1 dsieger 4726:
4727: Before outlining the process performed by the NetBSD package system in the next
4728: section, here's a brief discussion on where programs are installed, and which
4729: variables influence this.
4730:
4731: The automatic variable PREFIX indicates where all files of the final program
4732: shall be installed. It is usually set to LOCALBASE (/usr/pkg), or CROSSBASE for
4733: pkgs in the cross category. The value of PREFIX needs to be put into the
4734: various places in the program's source where paths to these files are encoded.
1.6 rillig 4735: See Section 11.3, "patches/*" and Section 19.3.1, "Shared libraries - libtool"
1.1 dsieger 4736: for more details.
4737:
4738: When choosing which of these variables to use, follow the following rules:
4739:
4740: * PREFIX always points to the location where the current pkg will be
1.25 wiz 4741: installed. When referring to a pkg's own installation path, use "${PREFIX}"
4742: .
1.1 dsieger 4743:
4744: * LOCALBASE is where all non-X11 pkgs are installed. If you need to construct
4745: a -I or -L argument to the compiler to find includes and libraries
4746: installed by another non-X11 pkg, use "${LOCALBASE}". The name LOCALBASE
4747: stems from FreeBSD, which installed all packages in /usr/local. As pkgsrc
4748: leaves /usr/local for the system administrator, this variable is a
4749: misnomer.
4750:
4751: * X11BASE is where the actual X11 distribution (from xsrc, etc.) is
4752: installed. When looking for standard X11 includes (not those installed by a
4753: package), use "${X11BASE}".
4754:
1.99 sevan 4755: * X11-based packages using imake must set USE_IMAKE to be installed correctly
4756: under LOCALBASE.
1.1 dsieger 4757:
1.99 sevan 4758: * To determine the prefix of an installed package, the EVAL_PREFIX definition
4759: can be used. It takes pairs in the format "DIRNAME=<package>", and the make
4760: (1) variable DIRNAME will be set to the prefix of the installed package
4761: <package>, or "${PREFIX}" if the package is not installed.
1.1 dsieger 4762:
4763: This is best illustrated by example.
4764:
4765: The following lines are taken from pkgsrc/wm/scwm/Makefile:
4766:
4767: EVAL_PREFIX+= GTKDIR=gtk+
4768: CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE:Q}
4769: CONFIGURE_ARGS+= --with-gtk-prefix=${GTKDIR:Q}
4770: CONFIGURE_ARGS+= --enable-multibyte
4771:
4772: Specific defaults can be defined for the packages evaluated using
4773: EVAL_PREFIX, by using a definition of the form:
4774:
4775: GTKDIR_DEFAULT= ${LOCALBASE}
4776:
4777: where GTKDIR corresponds to the first definition in the EVAL_PREFIX pair.
4778:
4779: * Within ${PREFIX}, packages should install files according to hier(7), with
4780: the exception that manual pages go into ${PREFIX}/man, not ${PREFIX}/share/
4781: man.
4782:
1.6 rillig 4783: 17.3. Directories used during the build process
1.1 dsieger 4784:
1.14 jmcneill 4785: When building a package, various directories are used to store source files,
1.1 dsieger 4786: temporary files, pkgsrc-internal files, and so on. These directories are
4787: explained here.
4788:
4789: Some of the directory variables contain relative pathnames. There are two
4790: common base directories for these relative directories: PKGSRCDIR/PKGPATH is
4791: used for directories that are pkgsrc-specific. WRKSRC is used for directories
4792: inside the package itself.
4793:
4794: PKGSRCDIR
4795:
4796: This is an absolute pathname that points to the pkgsrc root directory.
4797: Generally, you don't need it.
4798:
4799: PKGDIR
4800:
4801: This is an absolute pathname that points to the current package.
4802:
4803: PKGPATH
4804:
4805: This is a pathname relative to PKGSRCDIR that points to the current
4806: package.
4807:
4808: WRKDIR
4809:
4810: This is an absolute pathname pointing to the directory where all work takes
4811: place. The distfiles are extracted to this directory. It also contains
4812: temporary directories and log files used by the various pkgsrc frameworks,
4813: like buildlink or the wrappers.
4814:
4815: WRKSRC
4816:
4817: This is an absolute pathname pointing to the directory where the distfiles
4818: are extracted. It is usually a direct subdirectory of WRKDIR, and often
4819: it's the only directory entry that isn't hidden. This variable may be
4820: changed by a package Makefile.
4821:
1.14 jmcneill 4822: The CREATE_WRKDIR_SYMLINK definition takes either the value yes or no and
1.15 rillig 4823: defaults to no. It indicates whether a symbolic link to the WRKDIR is to be
1.14 jmcneill 4824: created in the pkgsrc entry's directory. If users would like to have their
4825: pkgsrc trees behave in a read-only manner, then the value of
4826: CREATE_WRKDIR_SYMLINK should be set to no.
4827:
1.6 rillig 4828: 17.4. Running a phase
1.1 dsieger 4829:
4830: You can run a particular phase by typing make phase, where phase is the name of
4831: the phase. This will automatically run all phases that are required for this
4832: phase. The default phase is build, that is, when you run make without
4833: parameters in a package directory, the package will be built, but not
4834: installed.
4835:
1.6 rillig 4836: 17.5. The fetch phase
1.1 dsieger 4837:
4838: The first step in building a package is to fetch the distribution files
1.25 wiz 4839: (distfiles) from the sites that are providing them. This is the task of the
1.1 dsieger 4840: fetch phase.
4841:
1.6 rillig 4842: 17.5.1. What to fetch and where to get it from
1.1 dsieger 4843:
4844: In simple cases, MASTER_SITES defines all URLs from where the distfile, whose
4845: name is derived from the DISTNAME variable, is fetched. The more complicated
4846: cases are described below.
4847:
4848: The variable DISTFILES specifies the list of distfiles that have to be fetched.
1.66 asau 4849: Its value defaults to ${DEFAULT_DISTFILES} and its value is ${DISTNAME}$
4850: {EXTRACT_SUFX}, so that most packages don't need to define it at all.
4851: EXTRACT_SUFX is .tar.gz by default, but can be changed freely. Note that if
4852: your package requires additional distfiles to the default one, you cannot just
4853: append the additional filenames using the += operator, but you have write for
4854: example:
1.1 dsieger 4855:
1.66 asau 4856: DISTFILES= ${DEFAULT_DISTFILES} additional-files.tar.gz
1.1 dsieger 4857:
4858: Each distfile is fetched from a list of sites, usually MASTER_SITES. If the
4859: package has multiple DISTFILES or multiple PATCHFILES from different sites, you
4860: can set SITES.distfile to the list of URLs where the file distfile (including
4861: the suffix) can be found.
4862:
4863: DISTFILES= ${DISTNAME}${EXTRACT_SUFX}
4864: DISTFILES+= foo-file.tar.gz
4865: SITES.foo-file.tar.gz= \
4866: http://www.somewhere.com/somehow/ \
4867: http://www.somewhereelse.com/mirror/somehow/
4868:
4869: When actually fetching the distfiles, each item from MASTER_SITES or SITES.*
4870: gets the name of each distfile appended to it, without an intermediate slash.
4871: Therefore, all site values have to end with a slash or other separator
4872: character. This allows for example to set MASTER_SITES to a URL of a CGI script
4873: that gets the name of the distfile as a parameter. In this case, the definition
4874: would look like:
4875:
4876: MASTER_SITES= http://www.example.com/download.cgi?file=
4877:
1.23 jakllsch 4878: The exception to this rule are URLs starting with a dash. In that case the URL
4879: is taken as is, fetched and the result stored under the name of the distfile.
1.66 asau 4880: You can use this style for the case when the download URL style does not match
4881: the above common case. For example, if permanent download URL is a redirector
4882: to the real download URL, or the download file name is offered by an HTTP
4883: Content-Disposition header. In the following example, foo-1.0.0.tar.gz will be
4884: created instead of the default v1.0.0.tar.gz.
4885:
4886: DISTNAME= foo-1.0.0
4887: MASTER_SITES= -http://www.example.com/archive/v1.0.0.tar.gz
1.23 jakllsch 4888:
1.1 dsieger 4889: There are some predefined values for MASTER_SITES, which can be used in
4890: packages. The names of the variables should speak for themselves.
4891:
4892: ${MASTER_SITE_APACHE}
4893: ${MASTER_SITE_BACKUP}
4894: ${MASTER_SITE_CYGWIN}
4895: ${MASTER_SITE_DEBIAN}
4896: ${MASTER_SITE_FREEBSD}
4897: ${MASTER_SITE_FREEBSD_LOCAL}
4898: ${MASTER_SITE_GENTOO}
4899: ${MASTER_SITE_GNOME}
4900: ${MASTER_SITE_GNU}
4901: ${MASTER_SITE_GNUSTEP}
1.66 asau 4902: ${MASTER_SITE_HASKELL_HACKAGE}
1.1 dsieger 4903: ${MASTER_SITE_IFARCHIVE}
4904: ${MASTER_SITE_KDE}
4905: ${MASTER_SITE_MOZILLA}
1.66 asau 4906: ${MASTER_SITE_MOZILLA_ALL}
4907: ${MASTER_SITE_MOZILLA_ESR}
1.1 dsieger 4908: ${MASTER_SITE_MYSQL}
1.66 asau 4909: ${MASTER_SITE_NETLIB}
1.1 dsieger 4910: ${MASTER_SITE_OPENOFFICE}
1.98 ryoon 4911: ${MASTER_SITE_OSDN}
1.1 dsieger 4912: ${MASTER_SITE_PERL_CPAN}
4913: ${MASTER_SITE_PGSQL}
1.66 asau 4914: ${MASTER_SITE_RUBYGEMS}
1.1 dsieger 4915: ${MASTER_SITE_R_CRAN}
4916: ${MASTER_SITE_SOURCEFORGE}
4917: ${MASTER_SITE_SUNSITE}
4918: ${MASTER_SITE_SUSE}
4919: ${MASTER_SITE_TEX_CTAN}
4920: ${MASTER_SITE_XCONTRIB}
4921: ${MASTER_SITE_XEMACS}
1.66 asau 4922: ${MASTER_SITE_XORG}
1.1 dsieger 4923:
4924: Some explanations for the less self-explaining ones: MASTER_SITE_BACKUP
4925: contains backup sites for packages that are maintained in ftp://ftp.NetBSD.org/
1.27 wiz 4926: pub/pkgsrc/distfiles/${DIST_SUBDIR}. MASTER_SITE_LOCAL contains local package
1.26 spz 4927: source distributions that are maintained in ftp://ftp.NetBSD.org/pub/pkgsrc/
4928: distfiles/LOCAL_PORTS/.
1.1 dsieger 4929:
4930: If you choose one of these predefined sites, you may want to specify a
4931: subdirectory of that site. Since these macros may expand to more than one
4932: actual site, you must use the following construct to specify a subdirectory:
4933:
4934: MASTER_SITES= ${MASTER_SITE_GNU:=subdirectory/name/}
4935: MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=project_name/}
4936:
4937: Note the trailing slash after the subdirectory name.
4938:
1.6 rillig 4939: 17.5.2. How are the files fetched?
1.1 dsieger 4940:
4941: The fetch phase makes sure that all the distfiles exist in a local directory
4942: (DISTDIR, which can be set by the pkgsrc user). If the files do not exist, they
4943: are fetched using commands of the form
4944:
4945: ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS}
4946:
4947: where ${site} varies through several possibilities in turn: first,
4948: MASTER_SITE_OVERRIDE is tried, then the sites specified in either SITES.file if
4949: defined, else MASTER_SITES or PATCH_SITES, as applies, then finally the value
4950: of MASTER_SITE_BACKUP. The order of all except the first and the last can be
4951: optionally sorted by the user, via setting either MASTER_SORT_RANDOM, and
4952: MASTER_SORT_AWK or MASTER_SORT_REGEX.
4953:
1.16 jnemeth 4954: The specific command and arguments used depend on the FETCH_USING parameter.
4955: The example above is for FETCH_USING=custom.
4956:
1.1 dsieger 4957: The distfiles mirror run by the NetBSD Foundation uses the mirror-distfiles
4958: target to mirror the distfiles, if they are freely distributable. Packages
4959: setting NO_SRC_ON_FTP (usually to "${RESTRICTED}") will not have their
4960: distfiles mirrored.
4961:
1.6 rillig 4962: 17.6. The checksum phase
1.1 dsieger 4963:
4964: After the distfile(s) are fetched, their checksum is generated and compared
4965: with the checksums stored in the distinfo file. If the checksums don't match,
4966: the build is aborted. This is to ensure the same distfile is used for building,
4967: and that the distfile wasn't changed, e.g. by some malign force, deliberately
4968: changed distfiles on the master distribution site or network lossage.
4969:
1.6 rillig 4970: 17.7. The extract phase
1.1 dsieger 4971:
4972: When the distfiles are present on the local system, they need to be extracted,
4973: as they usually come in the form of some compressed archive format.
4974:
4975: By default, all DISTFILES are extracted. If you only need some of them, you can
4976: set the EXTRACT_ONLY variable to the list of those files.
4977:
4978: Extracting the files is usually done by a little program, mk/extract/extract,
4979: which already knows how to extract various archive formats, so most likely you
4980: will not need to change anything here. But if you need, the following variables
4981: may help you:
4982:
4983: EXTRACT_OPTS_{BIN,LHA,PAX,RAR,TAR,ZIP,ZOO}
4984:
4985: Use these variables to override the default options for an extract command,
4986: which are defined in mk/extract/extract.
4987:
4988: EXTRACT_USING
4989:
1.14 jmcneill 4990: This variable can be set to bsdtar, gtar, nbtar (which is the default
4991: value), pax, or an absolute pathname pointing to the command with which tar
4992: archives should be extracted. It is preferred to choose bsdtar over gtar if
4993: NetBSD's pax-as-tar is not good enough.
1.1 dsieger 4994:
4995: If the extract program doesn't serve your needs, you can also override the
4996: EXTRACT_CMD variable, which holds the command used for extracting the files.
4997: This command is executed in the ${WRKSRC} directory. During execution of this
4998: command, the shell variable extract_file holds the absolute pathname of the
4999: file that is going to be extracted.
5000:
5001: And if that still does not suffice, you can override the do-extract target in
5002: the package Makefile.
5003:
1.6 rillig 5004: 17.8. The patch phase
1.1 dsieger 5005:
5006: After extraction, all the patches named by the PATCHFILES, those present in the
5007: patches subdirectory of the package as well as in $LOCALPATCHES/$PKGPATH (e.g.
5008: /usr/local/patches/graphics/png) are applied. Patchfiles ending in .Z or .gz
5009: are uncompressed before they are applied, files ending in .orig or .rej are
5010: ignored. Any special options to patch(1) can be handed in PATCH_DIST_ARGS. See
1.6 rillig 5011: Section 11.3, "patches/*" for more details.
1.1 dsieger 5012:
5013: By default patch(1) is given special args to make it fail if the patches apply
5014: with some lines of fuzz. Please fix (regen) the patches so that they apply
5015: cleanly. The rationale behind this is that patches that don't apply cleanly may
5016: end up being applied in the wrong place, and cause severe harm there.
5017:
1.6 rillig 5018: 17.9. The tools phase
1.1 dsieger 5019:
1.6 rillig 5020: This is covered in Chapter 18, Tools needed for building or running.
1.1 dsieger 5021:
1.6 rillig 5022: 17.10. The wrapper phase
1.1 dsieger 5023:
5024: This phase creates wrapper programs for the compilers and linkers. The
5025: following variables can be used to tweak the wrappers.
5026:
5027: ECHO_WRAPPER_MSG
5028:
5029: The command used to print progress messages. Does nothing by default. Set
5030: to ${ECHO} to see the progress messages.
5031:
5032: WRAPPER_DEBUG
5033:
5034: This variable can be set to yes (default) or no, depending on whether you
5035: want additional information in the wrapper log file.
5036:
5037: WRAPPER_UPDATE_CACHE
5038:
5039: This variable can be set to yes or no, depending on whether the wrapper
5040: should use its cache, which will improve the speed. The default value is
5041: yes, but is forced to no if the platform does not support it.
5042:
5043: WRAPPER_REORDER_CMDS
5044:
5045: A list of reordering commands. A reordering command has the form reorder:l:
5046: lib1:lib2. It ensures that that -llib1 occurs before -llib2.
5047:
5048: WRAPPER_TRANSFORM_CMDS
5049:
5050: A list of transformation commands. [TODO: investigate further]
5051:
1.6 rillig 5052: 17.11. The configure phase
1.1 dsieger 5053:
5054: Most pieces of software need information on the header files, system calls, and
5055: library routines which are available on the platform they run on. The process
5056: of determining this information is known as configuration, and is usually
5057: automated. In most cases, a script is supplied with the distfiles, and its
5058: invocation results in generation of header files, Makefiles, etc.
5059:
5060: If the package contains a configure script, this can be invoked by setting
5061: HAS_CONFIGURE to "yes". If the configure script is a GNU autoconf script, you
5062: should set GNU_CONFIGURE to "yes" instead. What happens in the configure phase
5063: is roughly:
5064:
5065: .for d in ${CONFIGURE_DIRS}
5066: cd ${WRKSRC} \
5067: && cd ${d} \
5068: && env ${CONFIGURE_ENV} ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}
5069: .endfor
5070:
5071: CONFIGURE_DIRS (default: ".") is a list of pathnames relative to WRKSRC. In
5072: each of these directories, the configure script is run with the environment
5073: CONFIGURE_ENV and arguments CONFIGURE_ARGS. The variables CONFIGURE_ENV,
5074: CONFIGURE_SCRIPT (default: "./configure") and CONFIGURE_ARGS may all be changed
5075: by the package.
5076:
1.38 wiz 5077: If the program uses the Perl way of configuration (mainly Perl modules, but not
5078: only), i.e. a file called Makefile.PL, it should include ../../lang/perl5/
5079: module.mk. To set any parameter for Makefile.PL use the MAKE_PARAMS variable
5080: (e.g., MAKE_PARAMS+=foo=bar
5081:
1.1 dsieger 5082: If the program uses an Imakefile for configuration, the appropriate steps can
1.99 sevan 5083: be invoked by setting USE_IMAKE to "yes". If you only need xmkmf, add it to
5084: USE_TOOLS. You can add variables to xmkmf's environment by adding them to the
5085: SCRIPTS_ENV variable.
1.1 dsieger 5086:
1.11 rillig 5087: If the program uses cmake for configuration, the appropriate steps can be
5088: invoked by setting USE_CMAKE to "yes". You can add variables to cmake's
5089: environment by adding them to the CONFIGURE_ENV variable and arguments to cmake
5090: by adding them to the CMAKE_ARGS variable. The top directory argument is given
5091: by the CMAKE_ARG_PATH variable, that defaults to "." (relative to
5092: CONFIGURE_DIRS)
5093:
1.1 dsieger 5094: If there is no configure step at all, set NO_CONFIGURE to "yes".
5095:
1.6 rillig 5096: 17.12. The build phase
1.1 dsieger 5097:
5098: For building a package, a rough equivalent of the following code is executed.
5099:
5100: .for d in ${BUILD_DIRS}
5101: cd ${WRKSRC} \
5102: && cd ${d} \
5103: && env ${MAKE_ENV} \
5104: ${MAKE_PROGRAM} ${BUILD_MAKE_FLAGS} \
5105: -f ${MAKE_FILE} \
5106: ${BUILD_TARGET}
5107: .endfor
5108:
5109: BUILD_DIRS (default: ".") is a list of pathnames relative to WRKSRC. In each of
5110: these directories, MAKE_PROGRAM is run with the environment MAKE_ENV and
5111: arguments BUILD_MAKE_FLAGS. The variables MAKE_ENV, BUILD_MAKE_FLAGS, MAKE_FILE
5112: and BUILD_TARGET may all be changed by the package.
5113:
1.25 wiz 5114: The default value of MAKE_PROGRAM is "gmake" if USE_TOOLS contains "gmake", "
5115: make" otherwise. The default value of MAKE_FILE is "Makefile", and BUILD_TARGET
5116: defaults to "all".
1.1 dsieger 5117:
5118: If there is no build step at all, set NO_BUILD to "yes".
5119:
1.6 rillig 5120: 17.13. The test phase
1.1 dsieger 5121:
5122: [TODO]
5123:
1.6 rillig 5124: 17.14. The install phase
1.1 dsieger 5125:
5126: Once the build stage has completed, the final step is to install the software
5127: in public directories, so users can access the programs and files.
5128:
5129: In the install phase, a rough equivalent of the following code is executed.
5130: Additionally, before and after this code, much magic is performed to do
5131: consistency checks, registering the package, and so on.
5132:
5133: .for d in ${INSTALL_DIRS}
5134: cd ${WRKSRC} \
5135: && cd ${d} \
5136: && env ${MAKE_ENV} \
5137: ${MAKE_PROGRAM} ${INSTALL_MAKE_FLAGS} \
5138: -f ${MAKE_FILE} \
5139: ${INSTALL_TARGET}
5140: .endfor
5141:
5142: The variable's meanings are analogous to the ones in the build phase.
5143: INSTALL_DIRS defaults to BUILD_DIRS. INSTALL_TARGET is "install" by default,
5144: plus "install.man" if USE_IMAKE is defined and NO_INSTALL_MANPAGES is not
5145: defined.
5146:
5147: In the install phase, the following variables are useful. They are all
5148: variations of the install(1) command that have the owner, group and permissions
5149: preset. INSTALL is the plain install command. The specialized variants,
5150: together with their intended use, are:
5151:
5152: INSTALL_PROGRAM_DIR
5153:
5154: directories that contain binaries
5155:
5156: INSTALL_SCRIPT_DIR
5157:
5158: directories that contain scripts
5159:
5160: INSTALL_LIB_DIR
5161:
5162: directories that contain shared and static libraries
5163:
5164: INSTALL_DATA_DIR
5165:
5166: directories that contain data files
5167:
5168: INSTALL_MAN_DIR
5169:
5170: directories that contain man pages
5171:
1.100 leot 5172: INSTALL_GAME_DIR
5173:
5174: directories that contain data files for games
5175:
1.1 dsieger 5176: INSTALL_PROGRAM
5177:
5178: binaries that can be stripped from debugging symbols
5179:
5180: INSTALL_SCRIPT
5181:
5182: binaries that cannot be stripped
5183:
5184: INSTALL_GAME
5185:
5186: game binaries
5187:
5188: INSTALL_LIB
5189:
5190: shared and static libraries
5191:
5192: INSTALL_DATA
5193:
5194: data files
5195:
5196: INSTALL_GAME_DATA
5197:
5198: data files for games
5199:
5200: INSTALL_MAN
5201:
5202: man pages
5203:
5204: Some other variables are:
5205:
1.106 tnn 5206: INSTALL_UNSTRIPPED
5207:
5208: If set to yes, do not run strip(1) when installing binaries. Any debugging
5209: sections and symbols present in binaries will be preserved.
5210:
1.1 dsieger 5211: INSTALLATION_DIRS
5212:
5213: A list of directories relative to PREFIX that are created by pkgsrc at the
5214: beginning of the install phase. The package is supposed to create all
5215: needed directories itself before installing files to it and list all other
5216: directories here.
5217:
1.25 wiz 5218: In the rare cases that a package shouldn't install anything, set NO_INSTALL to
1.1 dsieger 5219: "yes". This is mostly relevant for packages in the regress category.
5220:
1.6 rillig 5221: 17.15. The package phase
1.1 dsieger 5222:
5223: Once the install stage has completed, a binary package of the installed files
5224: can be built. These binary packages can be used for quick installation without
5225: previous compilation, e.g. by the make bin-install or by using pkg_add.
5226:
5227: By default, the binary packages are created in ${PACKAGES}/All and symlinks are
5228: created in ${PACKAGES}/category, one for each category in the CATEGORIES
5229: variable. PACKAGES defaults to pkgsrc/packages.
5230:
1.6 rillig 5231: 17.16. Cleaning up
1.1 dsieger 5232:
5233: Once you're finished with a package, you can clean the work directory by
5234: running make clean. If you want to clean the work directories of all
5235: dependencies too, use make clean-depends.
5236:
1.6 rillig 5237: 17.17. Other helpful targets
1.1 dsieger 5238:
5239: pre/post-*
5240:
5241: For any of the main targets described in the previous section, two
5242: auxiliary targets exist with "pre-" and "post-" used as a prefix for the
5243: main target's name. These targets are invoked before and after the main
5244: target is called, allowing extra configuration or installation steps be
5245: performed from a package's Makefile, for example, which a program's
5246: configure script or install target omitted.
5247:
5248: do-*
5249:
5250: Should one of the main targets do the wrong thing, and should there be no
5251: variable to fix this, you can redefine it with the do-* target. (Note that
5252: redefining the target itself instead of the do-* target is a bad idea, as
5253: the pre-* and post-* targets won't be called anymore, etc.) You will not
5254: usually need to do this.
5255:
5256: reinstall
5257:
5258: If you did a make install and you noticed some file was not installed
5259: properly, you can repeat the installation with this target, which will
5260: ignore the "already installed" flag.
5261:
5262: This is the default value of DEPENDS_TARGET except in the case of make
5263: update and make package, where the defaults are "package" and "update",
5264: respectively.
5265:
5266: deinstall
5267:
5268: This target does a pkg_delete(1) in the current directory, effectively
5269: de-installing the package. The following variables can be used to tune the
5270: behaviour:
5271:
5272: PKG_VERBOSE
5273:
5274: Add a "-v" to the pkg_delete(1) command.
5275:
5276: DEINSTALLDEPENDS
5277:
5278: Remove all packages that require (depend on) the given package. This
5279: can be used to remove any packages that may have been pulled in by a
5280: given package, e.g. if make deinstall DEINSTALLDEPENDS=1 is done in
1.25 wiz 5281: pkgsrc/x11/kde, this is likely to remove whole KDE. Works by adding "-R
5282: " to the pkg_delete(1) command line.
1.1 dsieger 5283:
5284: bin-install
5285:
5286: Install a binary package from local disk and via FTP from a list of sites
5287: (see the BINPKG_SITES variable), and do a make package if no binary package
5288: is available anywhere. The arguments given to pkg_add can be set via
5289: BIN_INSTALL_FLAGS e.g., to do verbose operation, etc.
5290:
1.95 wiz 5291: install-clean
5292:
5293: This target removes the state files for the "install" and later phases so
5294: that the "install" target may be re-invoked. This can be used after editing
5295: the PLIST to install the package without rebuilding it.
5296:
5297: build-clean
5298:
5299: This target removes the state files for the "build" and later phases so
5300: that the "build" target may be re-invoked.
5301:
1.1 dsieger 5302: update
5303:
5304: This target causes the current package to be updated to the latest version.
5305: The package and all depending packages first get de-installed, then current
5306: versions of the corresponding packages get compiled and installed. This is
5307: similar to manually noting which packages are currently installed, then
5308: performing a series of make deinstall and make install (or whatever
5309: UPDATE_TARGET is set to) for these packages.
5310:
5311: You can use the "update" target to resume package updating in case a
5312: previous make update was interrupted for some reason. However, in this
5313: case, make sure you don't call make clean or otherwise remove the list of
5314: dependent packages in WRKDIR. Otherwise, you lose the ability to
5315: automatically update the current package along with the dependent packages
5316: you have installed.
5317:
5318: Resuming an interrupted make update will only work as long as the package
5319: tree remains unchanged. If the source code for one of the packages to be
5320: updated has been changed, resuming make update will most certainly fail!
5321:
1.4 rillig 5322: The following variables can be used either on the command line or in
1.1 dsieger 5323: mk.conf to alter the behaviour of make update:
5324:
5325: UPDATE_TARGET
5326:
5327: Install target to recursively use for the updated package and the
5328: dependent packages. Defaults to DEPENDS_TARGET if set, "install"
1.25 wiz 5329: otherwise for make update. Other good targets are "package" or "
5330: bin-install". Do not set this to "update" or you will get stuck in an
1.1 dsieger 5331: endless loop!
5332:
5333: NOCLEAN
5334:
5335: Don't clean up after updating. Useful if you want to leave the work
5336: sources of the updated packages around for inspection or other
1.25 wiz 5337: purposes. Be sure you eventually clean up the source tree (see the "
5338: clean-update" target below) or you may run into troubles with old
1.1 dsieger 5339: source code still lying around on your next make or make update.
5340:
5341: REINSTALL
5342:
5343: Deinstall each package before installing (making DEPENDS_TARGET). This
5344: may be necessary if the "clean-update" target (see below) was called
5345: after interrupting a running make update.
5346:
5347: DEPENDS_TARGET
5348:
5349: Allows you to disable recursion and hardcode the target for packages.
5350: The default is "update" for the update target, facilitating a recursive
5351: update of prerequisite packages. Only set DEPENDS_TARGET if you want to
5352: disable recursive updates. Use UPDATE_TARGET instead to just set a
5353: specific target for each package to be installed during make update
5354: (see above).
5355:
5356: clean-update
5357:
5358: Clean the source tree for all packages that would get updated if make
5359: update was called from the current directory. This target should not be
5360: used if the current package (or any of its depending packages) have already
5361: been de-installed (e.g., after calling make update) or you may lose some
1.25 wiz 5362: packages you intended to update. As a rule of thumb: only use this target
1.1 dsieger 5363: before the first time you run make update and only if you have a dirty
5364: package tree (e.g., if you used NOCLEAN).
5365:
5366: If you are unsure about whether your tree is clean, you can either perform
5367: a make clean at the top of the tree, or use the following sequence of
5368: commands from the directory of the package you want to update (before
5369: running make update for the first time, otherwise you lose all the packages
5370: you wanted to update!):
5371:
5372: # make clean-update
5373: # make clean CLEANDEPENDS=YES
5374: # make update
5375:
5376:
1.4 rillig 5377: The following variables can be used either on the command line or in
1.1 dsieger 5378: mk.conf to alter the behaviour of make clean-update:
5379:
5380: CLEAR_DIRLIST
5381:
5382: After make clean, do not reconstruct the list of directories to update
5383: for this package. Only use this if make update successfully installed
5384: all packages you wanted to update. Normally, this is done automatically
5385: on make update, but may have been suppressed by the NOCLEAN variable
5386: (see above).
5387:
5388: replace
5389:
5390: Update the installation of the current package. This differs from update in
5391: that it does not replace dependent packages. You will need to install
5392: pkgtools/pkg_tarup for this target to work.
5393:
5394: Be careful when using this target! There are no guarantees that dependent
5395: packages will still work, in particular they will most certainly break if
5396: you make replace a library package whose shared library major version
5397: changed between your installed version and the new one. For this reason,
5398: this target is not officially supported and only recommended for advanced
5399: users.
5400:
5401: info
5402:
5403: This target invokes pkg_info(1) for the current package. You can use this
5404: to check which version of a package is installed.
5405:
5406: index
5407:
5408: This is a top-level command, i.e. it should be used in the pkgsrc
5409: directory. It creates a database of all packages in the local pkgsrc tree,
5410: including dependencies, comment, maintainer, and some other useful
5411: information. Individual entries are created by running make describe in the
5412: packages' directories. This index file is saved as pkgsrc/INDEX. It can be
5413: displayed in verbose format by running make print-index. You can search in
5414: it with make search key=something. You can extract a list of all packages
5415: that depend on a particular one by running make show-deps PKG=somepackage.
5416:
5417: Running this command takes a very long time, some hours even on fast
5418: machines!
5419:
5420: readme
5421:
5422: This target generates a README.html file, which can be viewed using a
5423: browser such as www/firefox or www/links. The generated files contain
5424: references to any packages which are in the PACKAGES directory on the local
5425: host. The generated files can be made to refer to URLs based on
5426: FTP_PKG_URL_HOST and FTP_PKG_URL_DIR. For example, if I wanted to generate
5427: README.html files which pointed to binary packages on the local machine, in
5428: the directory /usr/packages, set FTP_PKG_URL_HOST=file://localhost and
5429: FTP_PKG_URL_DIR=/usr/packages. The ${PACKAGES} directory and its
5430: subdirectories will be searched for all the binary packages.
5431:
5432: The target can be run at the toplevel or in category directories, in which
5433: case it descends recursively.
5434:
5435: readme-all
5436:
5437: This is a top-level command, run it in pkgsrc. Use this target to create a
5438: file README-all.html which contains a list of all packages currently
5439: available in the NetBSD Packages Collection, together with the category
5440: they belong to and a short description. This file is compiled from the
5441: pkgsrc/*/README.html files, so be sure to run this after a make readme.
5442:
5443: cdrom-readme
5444:
5445: This is very much the same as the "readme" target (see above), but is to be
5446: used when generating a pkgsrc tree to be written to a CD-ROM. This target
5447: also produces README.html files, and can be made to refer to URLs based on
5448: CDROM_PKG_URL_HOST and CDROM_PKG_URL_DIR.
5449:
5450: show-distfiles
5451:
5452: This target shows which distfiles and patchfiles are needed to build the
5453: package (ALLFILES, which contains all DISTFILES and PATCHFILES, but not
5454: patches/*).
5455:
5456: show-downlevel
5457:
5458: This target shows nothing if the package is not installed. If a version of
5459: this package is installed, but is not the version provided in this version
5460: of pkgsrc, then a warning message is displayed. This target can be used to
5461: show which of your installed packages are downlevel, and so the old
5462: versions can be deleted, and the current ones added.
5463:
5464: show-pkgsrc-dir
5465:
5466: This target shows the directory in the pkgsrc hierarchy from which the
5467: package can be built and installed. This may not be the same directory as
5468: the one from which the package was installed. This target is intended to be
5469: used by people who may wish to upgrade many packages on a single host, and
1.25 wiz 5470: can be invoked from the top-level pkgsrc Makefile by using the "
5471: show-host-specific-pkgs" target.
1.1 dsieger 5472:
5473: show-installed-depends
5474:
5475: This target shows which installed packages match the current package's
5476: DEPENDS. Useful if out of date dependencies are causing build problems.
5477:
1.95 wiz 5478: print-build-depends-list
5479:
5480: This target shows the list of packages that the current package depends on
5481: for building.
5482:
5483: print-run-depends-list
5484:
5485: This target shows the list of packages that the current package depends on
5486: for running.
5487:
1.1 dsieger 5488: check-shlibs
5489:
5490: After a package is installed, check all its binaries and (on ELF platforms)
5491: shared libraries to see if they find the shared libs they need. Run by
1.4 rillig 5492: default if PKG_DEVELOPER is set in mk.conf.
1.1 dsieger 5493:
5494: print-PLIST
5495:
5496: After a "make install" from a new or upgraded pkg, this prints out an
5497: attempt to generate a new PLIST from a find -newer work/.extract_done. An
5498: attempt is made to care for shared libs etc., but it is strongly
5499: recommended to review the result before putting it into PLIST. On upgrades,
5500: it's useful to diff the output of this command against an already existing
5501: PLIST file.
5502:
5503: If the package installs files via tar(1) or other methods that don't update
5504: file access times, be sure to add these files manually to your PLIST, as
5505: the "find -newer" command used by this target won't catch them!
5506:
1.6 rillig 5507: See Section 13.3, "Tweaking output of make print-PLIST" for more
1.1 dsieger 5508: information on this target.
5509:
5510: bulk-package
5511:
5512: Used to do bulk builds. If an appropriate binary package already exists, no
5513: action is taken. If not, this target will compile, install and package it
1.66 asau 5514: (and its depends, if PKG_DEPENDS is set properly. See Chapter 7, Creating
5515: binary packages for everything in pkgsrc (bulk builds)). After creating the
5516: binary package, the sources, the just-installed package and its required
5517: packages are removed, preserving free disk space.
1.1 dsieger 5518:
5519: Beware that this target may deinstall all packages installed on a system!
5520:
5521: bulk-install
5522:
5523: Used during bulk-installs to install required packages. If an up-to-date
1.25 wiz 5524: binary package is available, it will be installed via pkg_add(1). If not,
1.1 dsieger 5525: make bulk-package will be executed, but the installed binary won't be
5526: removed.
5527:
5528: A binary package is considered "up-to-date" to be installed via pkg_add(1)
5529: if:
5530:
1.42 asau 5531: + None of the package's files (Makefile, ...) were modified since it was
1.1 dsieger 5532: built.
5533:
1.42 asau 5534: + None of the package's required (binary) packages were modified since it
1.1 dsieger 5535: was built.
5536:
5537: Beware that this target may deinstall all packages installed on a system!
5538:
1.6 rillig 5539: Chapter 18. Tools needed for building or running
1.1 dsieger 5540:
5541: Table of Contents
5542:
1.6 rillig 5543: 18.1. Tools for pkgsrc builds
5544: 18.2. Tools needed by packages
5545: 18.3. Tools provided by platforms
1.1 dsieger 5546:
5547: The USE_TOOLS definition is used both internally by pkgsrc and also for
5548: individual packages to define what commands are needed for building a package
5549: (like BUILD_DEPENDS) or for later run-time of an installed packaged (such as
5550: DEPENDS). If the native system provides an adequate tool, then in many cases, a
5551: pkgsrc package will not be used.
5552:
5553: When building a package, the replacement tools are made available in a
5554: directory (as symlinks or wrapper scripts) that is early in the executable
5555: search path. Just like the buildlink system, this helps with consistent builds.
5556:
5557: A tool may be needed to help build a specific package. For example, perl, GNU
5558: make (gmake) or yacc may be needed.
5559:
5560: Also a tool may be needed, for example, because the native system's supplied
5561: tool may be inefficient for building a package with pkgsrc. For example, a
5562: package may need GNU awk, bison (instead of yacc) or a better sed.
5563:
5564: The tools used by a package can be listed by running make show-tools.
5565:
1.6 rillig 5566: 18.1. Tools for pkgsrc builds
1.1 dsieger 5567:
5568: The default set of tools used by pkgsrc is defined in bsd.pkg.mk. This includes
5569: standard Unix tools, such as: cat, awk, chmod, test, and so on. These can be
5570: seen by running: make show-var VARNAME=USE_TOOLS.
5571:
5572: If a package needs a specific program to build then the USE_TOOLS variable can
5573: be used to define the tools needed.
5574:
1.6 rillig 5575: 18.2. Tools needed by packages
1.1 dsieger 5576:
1.29 wiz 5577: In the following examples, the :run means that it is needed at run-time (and
5578: becomes a DEPENDS). The default is a build dependency which can be set with
5579: :build. (So in this example, it is the same as gmake:build and
5580: pkg-config:build.)
1.1 dsieger 5581:
5582: USE_TOOLS+= gmake perl:run pkg-config
5583:
5584: When using the tools framework, a TOOLS_PATH.foo variable is defined which
5585: contains the full path to the appropriate tool. For example, TOOLS_PATH.bash
5586: could be "/bin/bash" on Linux systems.
5587:
5588: If you always need a pkgsrc version of the tool at run-time, then just use
5589: DEPENDS instead.
5590:
1.6 rillig 5591: 18.3. Tools provided by platforms
1.1 dsieger 5592:
5593: When improving or porting pkgsrc to a new platform, have a look at (or create)
5594: the corresponding platform specific make file fragment under pkgsrc/mk/tools/
5595: tools.${OPSYS}.mk which defines the name of the common tools. For example:
5596:
5597: .if exists(/usr/bin/bzcat)
5598: TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
5599: .elif exists(/usr/bin/bzip2)
5600: TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
5601: .endif
5602:
5603: TOOLS_PLATFORM.true?= true # shell builtin
5604:
1.6 rillig 5605: Chapter 19. Making your package work
1.1 dsieger 5606:
5607: Table of Contents
5608:
1.6 rillig 5609: 19.1. General operation
1.1 dsieger 5610:
1.108 rillig 5611: 19.1.1. How to pull in user-settable variables from mk.conf
5612: 19.1.2. User interaction
5613: 19.1.3. Handling licenses
5614: 19.1.4. Restricted packages
5615: 19.1.5. Handling dependencies
5616: 19.1.6. Handling conflicts with other packages
5617: 19.1.7. Packages that cannot or should not be built
5618: 19.1.8. Packages which should not be deleted, once installed
5619: 19.1.9. Handling packages with security problems
5620: 19.1.10. How to handle incrementing versions when fixing an existing
1.1 dsieger 5621: package
1.108 rillig 5622: 19.1.11. Substituting variable text in the package files (the SUBST
1.1 dsieger 5623: framework)
5624:
1.108 rillig 5625: 19.2. The fetch phase
1.1 dsieger 5626:
1.6 rillig 5627: 19.2.1. Packages whose distfiles aren't available for plain downloading
5628: 19.2.2. How to handle modified distfiles with the 'old' name
1.88 tnn 5629: 19.2.3. Packages hosted on github.com
1.1 dsieger 5630:
1.108 rillig 5631: 19.3. The configure phase
1.1 dsieger 5632:
1.6 rillig 5633: 19.3.1. Shared libraries - libtool
5634: 19.3.2. Using libtool on GNU packages that already support libtool
5635: 19.3.3. GNU Autoconf/Automake
5636:
5637: 19.4. Programming languages
5638:
5639: 19.4.1. C, C++, and Fortran
5640: 19.4.2. Java
5641: 19.4.3. Packages containing perl scripts
1.41 wiz 5642: 19.4.4. Packages containing shell scripts
5643: 19.4.5. Other programming languages
1.6 rillig 5644:
1.108 rillig 5645: 19.5. The build phase
1.6 rillig 5646:
5647: 19.5.1. Compiling C and C++ code conditionally
5648: 19.5.2. How to handle compiler bugs
1.24 wiz 5649: 19.5.3. Undefined reference to "..."
1.6 rillig 5650: 19.5.4. Running out of memory
5651:
1.108 rillig 5652: 19.6. The install phase
1.6 rillig 5653:
5654: 19.6.1. Creating needed directories
5655: 19.6.2. Where to install documentation
5656: 19.6.3. Installing highscore files
5657: 19.6.4. Adding DESTDIR support to packages
5658: 19.6.5. Packages with hardcoded paths to other interpreters
5659: 19.6.6. Packages installing perl modules
5660: 19.6.7. Packages installing info files
5661: 19.6.8. Packages installing man pages
1.7 rillig 5662: 19.6.9. Packages installing GConf data files
1.18 mishka 5663: 19.6.10. Packages installing scrollkeeper/rarian data files
1.6 rillig 5664: 19.6.11. Packages installing X11 fonts
5665: 19.6.12. Packages installing GTK2 modules
5666: 19.6.13. Packages installing SGML or XML data
5667: 19.6.14. Packages installing extensions to the MIME database
5668: 19.6.15. Packages using intltool
5669: 19.6.16. Packages installing startup scripts
5670: 19.6.17. Packages installing TeX modules
5671: 19.6.18. Packages supporting running binaries in emulation
5672: 19.6.19. Packages installing hicolor theme icons
5673: 19.6.20. Packages installing desktop files
1.1 dsieger 5674:
1.6 rillig 5675: 19.7. Marking packages as having problems
1.1 dsieger 5676:
1.6 rillig 5677: 19.1. General operation
1.1 dsieger 5678:
5679: One appealing feature of pkgsrc is that it runs on many different platforms. As
5680: a result, it is important to ensure, where possible, that packages in pkgsrc
5681: are portable. This chapter mentions some particular details you should pay
5682: attention to while working on pkgsrc.
5683:
1.108 rillig 5684: 19.1.1. How to pull in user-settable variables from mk.conf
1.1 dsieger 5685:
5686: The pkgsrc user can configure pkgsrc by overriding several variables in the
1.4 rillig 5687: file pointed to by MAKECONF, which is mk.conf by default. When you want to use
5688: those variables in the preprocessor directives of make(1) (for example .if or
5689: .for), you need to include the file ../../mk/bsd.prefs.mk before, which in turn
5690: loads the user preferences.
1.1 dsieger 5691:
5692: But note that some variables may not be completely defined after ../../mk/
5693: bsd.prefs.mk has been included, as they may contain references to variables
1.108 rillig 5694: that are not yet defined. In shell commands (the lines in Makefile that are
5695: indented with a tab) this is no problem, since variables are only expanded when
5696: they are used. But in the preprocessor directives mentioned above and in
5697: dependency lines (of the form target: dependencies) the variables are expanded
5698: at load time.
1.1 dsieger 5699:
5700: Note
5701:
1.108 rillig 5702: To check whether a variable can be used at load time, run pkglint -Wall on your
5703: package.
1.1 dsieger 5704:
1.108 rillig 5705: 19.1.2. User interaction
1.1 dsieger 5706:
5707: Occasionally, packages require interaction from the user, and this can be in a
5708: number of ways:
5709:
5710: * When fetching the distfiles, some packages require user interaction such as
5711: entering username/password or accepting a license on a web page.
5712:
5713: * When extracting the distfiles, some packages may ask for passwords.
5714:
5715: * help to configure the package before it is built
5716:
5717: * help during the build process
5718:
5719: * help during the installation of a package
5720:
1.108 rillig 5721: A package can set the INTERACTIVE_STAGE variable to define which stages need
5722: interaction. This should be done in the package's Makefile, e.g.:
1.1 dsieger 5723:
5724: INTERACTIVE_STAGE= configure install
5725:
5726: The user can then decide to skip this package by setting the BATCH variable.
1.108 rillig 5727: Packages that require interaction are also excluded from bulk builds.
1.1 dsieger 5728:
1.108 rillig 5729: 19.1.3. Handling licenses
1.1 dsieger 5730:
5731: Authors of software can choose the licence under which software can be copied.
1.111 sevan 5732: The Free Software Foundation has declared some licenses "Free", and the Open
5733: Source Initiative has a definition of "Open Source".
5734:
5735: By default, pkgsrc allows packages with Free or Open Source licenses to be
5736: built. To allow packages with other licenses to be built as well, the pkgsrc
5737: user needs to add these licenses to the ACCEPTABLE_LICENSES variable in mk.conf
5738: . Note that this variable only affects which packages may be built, while the
5739: license terms often also restrict the actual use of the package and its
5740: redistribution.
1.1 dsieger 5741:
5742: One might want to only install packages with a BSD license, or the GPL, and not
1.20 jnemeth 5743: the other. The free licenses are added to the default ACCEPTABLE_LICENSES
1.111 sevan 5744: variable. The pkgsrc user can override the default by setting the
5745: ACCEPTABLE_LICENSES variable with "=" instead of "+=". The licenses accepted by
5746: default are defined in the DEFAULT_ACCEPTABLE_LICENSES variable in the file
5747: pkgsrc/mk/license.mk.
1.1 dsieger 5748:
5749: The license tag mechanism is intended to address copyright-related issues
5750: surrounding building, installing and using a package, and not to address
1.20 jnemeth 5751: redistribution issues (see RESTRICTED and NO_SRC_ON_FTP, etc.). Packages with
5752: redistribution restrictions should set these tags.
1.1 dsieger 5753:
5754: Denoting that a package may be copied according to a particular license is done
5755: by placing the license in pkgsrc/licenses and setting the LICENSE variable to a
5756: string identifying the license, e.g. in graphics/xv:
5757:
5758: LICENSE= xv-license
5759:
5760: When trying to build, the user will get a notice that the package is covered by
5761: a license which has not been placed in the ACCEPTABLE_LICENSES variable:
5762:
5763: % make
5764: ===> xv-3.10anb9 has an unacceptable license: xv-license.
5765: ===> To view the license, enter "/usr/bin/make show-license".
5766: ===> To indicate acceptance, add this line to your /etc/mk.conf:
5767: ===> ACCEPTABLE_LICENSES+=xv-license
5768: *** Error code 1
5769:
5770: The license can be viewed with make show-license, and if the user so chooses,
1.4 rillig 5771: the line printed above can be added to mk.conf to convey to pkgsrc that it
1.1 dsieger 5772: should not in the future fail because of that license:
5773:
5774: ACCEPTABLE_LICENSES+=xv-license
5775:
1.111 sevan 5776: The use of LICENSE=shareware, LICENSE=no-commercial-use, and similar language
5777: is deprecated because it does not crisply refer to a particular license text.
5778: Another problem with such usage is that it does not enable a user to tell
5779: pkgsrc to proceed for a single package without also telling pkgsrc to proceed
5780: for all packages with that tag.
5781:
5782: 19.1.3.1. Adding a package with a new license
1.1 dsieger 5783:
1.49 rodent 5784: When adding a package with a new license, the following steps are required:
5785:
1.111 sevan 5786: 1. Check whether the license qualifies as Free or Open Source by referencing
5787: Various Licenses and Comments about Them and Licenses by Name | Open Source
5788: Initiative. If this is the case, the filename in pkgsrc/licenses/ does not
5789: need the -license suffix, and the license name should be added to:
1.49 rodent 5790:
5791: + DEFAULT_ACCEPTABLE_LICENSES in pkgsrc/mk/license.mk
5792:
5793: + default_acceptable_licenses in pkgsrc/pkgtools/pkg_install/files/lib/
5794: license.c
5795:
5796: 2. The license text should be added to pkgsrc/licenses for displaying. A list
5797: of known licenses can be seen in this directory.
1.1 dsieger 5798:
1.111 sevan 5799: 19.1.3.2. Change to the license
1.1 dsieger 5800:
1.111 sevan 5801: When the license changes (in a way other than formatting), make sure that the
5802: new license has a different name (e.g., append the version number if it exists,
5803: or the date). Just because a user told pkgsrc to build programs under a
5804: previous version of a license does not mean that pkgsrc should build programs
5805: under the new licenses. The higher-level point is that pkgsrc does not evaluate
5806: licenses for reasonableness; the only test is a mechanistic test of whether a
5807: particular text has been approved by either of two bodies (FSF or OSI).
1.1 dsieger 5808:
1.108 rillig 5809: 19.1.4. Restricted packages
1.1 dsieger 5810:
1.111 sevan 5811: Some licenses restrict how software may be re-distributed. By declaring the
5812: restrictions, package tools can automatically refrain from e.g. placing binary
5813: packages on FTP sites.
5814:
5815: There are four possible restrictions, which are the cross product of sources
5816: (distfiles) and binaries not being placed on FTP sites and CD-ROMs. Because
5817: this is rarely the exact language in any license, and because non-Free licenses
5818: tend to be different from each other, pkgsrc adopts a definition of FTP and
5819: CD-ROM. "FTP" means making the source or binary file available over the
5820: Internet at no charge. "CD-ROM" means making the source or binary available on
5821: some kind of media, together with other source and binary packages, which is
5822: sold for a distribution charge.
1.1 dsieger 5823:
5824: In order to encode these restrictions, the package system defines five make
5825: variables that can be set to note these restrictions:
5826:
5827: * RESTRICTED
5828:
5829: This variable should be set whenever a restriction exists (regardless of
5830: its kind). Set this variable to a string containing the reason for the
5831: restriction. It should be understood that those wanting to understand the
5832: restriction will have to read the license, and perhaps seek advice of
5833: counsel.
5834:
5835: * NO_BIN_ON_CDROM
5836:
5837: Binaries may not be placed on CD-ROM containing other binary packages, for
5838: which a distribution charge may be made. In this case, set this variable to
5839: ${RESTRICTED}.
5840:
5841: * NO_BIN_ON_FTP
5842:
5843: Binaries may not made available on the Internet without charge. In this
5844: case, set this variable to ${RESTRICTED}. If this variable is set, binary
5845: packages will not be included on ftp.NetBSD.org.
5846:
5847: * NO_SRC_ON_CDROM
5848:
5849: Distfiles may not be placed on CD-ROM, together with other distfiles, for
5850: which a fee may be charged. In this case, set this variable to $
5851: {RESTRICTED}.
5852:
5853: * NO_SRC_ON_FTP
5854:
5855: Distfiles may not made available via FTP at no charge. In this case, set
5856: this variable to ${RESTRICTED}. If this variable is set, the distfile(s)
5857: will not be mirrored on ftp.NetBSD.org.
5858:
1.111 sevan 5859: Please note that packages will be removed from pkgsrc when the distfiles are
1.33 wiz 5860: not distributable and cannot be obtained for a period of one full quarter
1.111 sevan 5861: branch. Packages with manual/interactive fetch must have a maintainer and it is
5862: his/her responsibility to ensure this.
1.33 wiz 5863:
1.108 rillig 5864: 19.1.5. Handling dependencies
1.1 dsieger 5865:
5866: Your package may depend on some other package being present - and there are
5867: various ways of expressing this dependency. pkgsrc supports the BUILD_DEPENDS
5868: and DEPENDS definitions, the USE_TOOLS definition, as well as dependencies via
5869: buildlink3.mk, which is the preferred way to handle dependencies, and which
1.6 rillig 5870: uses the variables named above. See Chapter 14, Buildlink methodology for more
1.1 dsieger 5871: information.
5872:
5873: The basic difference between the two variables is as follows: The DEPENDS
5874: definition registers that pre-requisite in the binary package so it will be
5875: pulled in when the binary package is later installed, whilst the BUILD_DEPENDS
5876: definition does not, marking a dependency that is only needed for building the
5877: package.
5878:
5879: This means that if you only need a package present whilst you are building, it
5880: should be noted as a BUILD_DEPENDS.
5881:
5882: The format for a BUILD_DEPENDS and a DEPENDS definition is:
5883:
5884: <pre-req-package-name>:../../<category>/<pre-req-package>
5885:
5886: Please note that the "pre-req-package-name" may include any of the wildcard
5887: version numbers recognized by pkg_info(1).
5888:
1.55 wiz 5889: 1. If your package needs another package's binaries or libraries to build and
1.1 dsieger 5890: run, and if that package has a buildlink3.mk file available, use it:
5891:
5892: .include "../../graphics/jpeg/buildlink3.mk"
5893:
1.55 wiz 5894: 2. If your package needs another package's binaries or libraries only for
5895: building, and if that package has a buildlink3.mk file available, use it:
5896:
5897: .include "../../graphics/jpeg/buildlink3.mk"
5898:
5899: but set BUILDLINK_DEPMETHOD.jpeg?=build to make it a build dependency only.
5900: This case is rather rare.
5901:
5902: 3. If your package needs binaries from another package to build, use the
1.26 spz 5903: BUILD_DEPENDS definition:
1.1 dsieger 5904:
1.26 spz 5905: BUILD_DEPENDS+= scons-[0-9]*:../../devel/scons
1.1 dsieger 5906:
1.55 wiz 5907: 4. If your package needs a library with which to link and there is no
1.26 spz 5908: buildlink3.mk file available, create one. Using DEPENDS won't be sufficient
5909: because the include files and libraries will be hidden from the compiler.
1.1 dsieger 5910:
1.55 wiz 5911: 5. If your package needs some executable to be able to run correctly and if
1.26 spz 5912: there's no buildlink3.mk file, this is specified using the DEPENDS
5913: variable. The print/lyx package needs to be able to execute the latex
5914: binary from the teTeX package when it runs, and that is specified:
1.1 dsieger 5915:
1.26 spz 5916: DEPENDS+= teTeX-[0-9]*:../../print/teTeX
1.1 dsieger 5917:
1.55 wiz 5918: 6. You can use wildcards in package dependencies. Note that such wildcard
1.26 spz 5919: dependencies are retained when creating binary packages. The dependency is
5920: checked when installing the binary package and any package which matches
5921: the pattern will be used. Wildcard dependencies should be used with care.
1.1 dsieger 5922:
5923: The "-[0-9]*" should be used instead of "-*" to avoid potentially ambiguous
5924: matches such as "tk-postgresql" matching a "tk-*" DEPENDS.
5925:
5926: Wildcards can also be used to specify that a package will only build
5927: against a certain minimum version of a pre-requisite:
5928:
1.26 spz 5929: DEPENDS+= ImageMagick>=6.0:../../graphics/ImageMagick
1.1 dsieger 5930:
1.26 spz 5931: This means that the package will build using version 6.0 of ImageMagick or
5932: newer. Such a dependency may be warranted if, for example, the command line
5933: options of an executable have changed.
5934:
5935: If you need to depend on minimum versions of libraries, see the buildlink
5936: section of the pkgsrc guide.
1.1 dsieger 5937:
5938: For security fixes, please update the package vulnerabilities file. See
1.108 rillig 5939: Section 19.1.9, "Handling packages with security problems" for more
1.1 dsieger 5940: information.
5941:
5942: If your package needs files from another package to build, add the relevant
5943: distribution files to DISTFILES, so they will be extracted automatically. See
5944: the print/ghostscript package for an example. (It relies on the jpeg sources
5945: being present in source form during the build.)
5946:
1.108 rillig 5947: 19.1.6. Handling conflicts with other packages
1.1 dsieger 5948:
5949: Your package may conflict with other packages a user might already have
5950: installed on his system, e.g. if your package installs the same set of files as
1.80 wiz 5951: another package in the pkgsrc tree or has the same PKGNAME.
1.1 dsieger 5952:
1.80 wiz 5953: These cases are handled automatically by the packaging tools at package
5954: installation time and do not need to be handled manually.
1.1 dsieger 5955:
1.80 wiz 5956: In case the conflicts can not be recognized automatically (e.g., packages using
5957: the same config file location but no other shared files), you can set CONFLICTS
5958: to a space-separated list of packages (including version string) your package
5959: conflicts with.
1.1 dsieger 5960:
1.80 wiz 5961: For example, if both foo/bar and foo/baz use the same config file, you would
5962: set in foo/bar/Makefile:
1.1 dsieger 5963:
1.80 wiz 5964: CONFLICTS= baz-[0-9]*
1.1 dsieger 5965:
1.80 wiz 5966: and in pkgsrc/foo/baz/Makefile:
1.1 dsieger 5967:
1.80 wiz 5968: CONFLICTS= bar-[0-9]*
1.1 dsieger 5969:
1.108 rillig 5970: 19.1.7. Packages that cannot or should not be built
1.1 dsieger 5971:
5972: There are several reasons why a package might be instructed to not build under
5973: certain circumstances. If the package builds and runs on most platforms, the
1.83 dholland 5974: exceptions should be noted with BROKEN_ON_PLATFORM. If the package builds and
5975: runs on a small handful of platforms, set BROKEN_EXCEPT_ON_PLATFORM instead.
5976: Both BROKEN_ON_PLATFORM and BROKEN_EXCEPT_ON_PLATFORM are OS triples
5977: (OS-version-platform) that can use glob-style wildcards.
5978:
1.114 maya 5979: If a package is not appropriate for some platforms (as opposed to merely
1.83 dholland 5980: broken), a different set of variables should be used as this affects failure
5981: reporting and statistics. If the package is appropriate for most platforms, the
5982: exceptions should be noted with NOT_FOR_PLATFORM. If the package is appropriate
5983: for only a small handful of platforms (often exactly one), set
5984: ONLY_FOR_PLATFORM instead. Both ONLY_FOR_PLATFORM and NOT_FOR_PLATFORM are OS
5985: triples (OS-version-platform) that can use glob-style wildcards.
1.1 dsieger 5986:
5987: Some packages are tightly bound to a specific version of an operating system,
5988: e.g. LKMs or sysutils/lsof. Such binary packages are not backwards compatible
5989: with other versions of the OS, and should be uploaded to a version specific
5990: directory on the FTP server. Mark these packages by setting OSVERSION_SPECIFIC
5991: to "yes". This variable is not currently used by any of the package system
5992: internals, but may be used in the future.
5993:
5994: If the package should be skipped (for example, because it provides
5995: functionality already provided by the system), set PKG_SKIP_REASON to a
5996: descriptive message. If the package should fail because some preconditions are
5997: not met, set PKG_FAIL_REASON to a descriptive message.
5998:
1.108 rillig 5999: 19.1.8. Packages which should not be deleted, once installed
1.1 dsieger 6000:
6001: To ensure that a package may not be deleted, once it has been installed, the
6002: PKG_PRESERVE definition should be set in the package Makefile. This will be
1.25 wiz 6003: carried into any binary package that is made from this pkgsrc entry. A "
6004: preserved" package will not be deleted using pkg_delete(1) unless the "-f"
1.1 dsieger 6005: option is used.
6006:
1.108 rillig 6007: 19.1.9. Handling packages with security problems
1.1 dsieger 6008:
6009: When a vulnerability is found, this should be noted in localsrc/security/
1.32 wiz 6010: advisories/pkg-vulnerabilities, and after committing that file, ask
6011: pkgsrc-security@NetBSD.org to update the file on ftp.NetBSD.org.
1.1 dsieger 6012:
6013: After fixing the vulnerability by a patch, its PKGREVISION should be increased
6014: (this is of course not necessary if the problem is fixed by using a newer
1.32 wiz 6015: release of the software), and the pattern in the pkg-vulnerabilities file must
6016: be updated.
1.1 dsieger 6017:
6018: Also, if the fix should be applied to the stable pkgsrc branch, be sure to
6019: submit a pullup request!
6020:
6021: Binary packages already on ftp.NetBSD.org will be handled semi-automatically by
6022: a weekly cron job.
6023:
1.108 rillig 6024: 19.1.10. How to handle incrementing versions when fixing an existing package
1.1 dsieger 6025:
6026: When making fixes to an existing package it can be useful to change the version
6027: number in PKGNAME. To avoid conflicting with future versions by the original
6028: author, a "nb1", "nb2", ... suffix can be used on package versions by setting
6029: PKGREVISION=1 (2, ...). The "nb" is treated like a "." by the package tools.
6030: e.g.
6031:
6032: DISTNAME= foo-17.42
6033: PKGREVISION= 9
6034:
6035: will result in a PKGNAME of "foo-17.42nb9". If you want to use the original
6036: value of PKGNAME without the "nbX" suffix, e.g. for setting DIST_SUBDIR, use
6037: PKGNAME_NOREV.
6038:
6039: When a new release of the package is released, the PKGREVISION should be
6040: removed, e.g. on a new minor release of the above package, things should be
6041: like:
6042:
6043: DISTNAME= foo-17.43
6044:
6045: PKGREVISION should be incremented for any non-trivial change in the resulting
6046: binary package. Without a PKGREVISION bump, someone with the previous version
6047: installed has no way of knowing that their package is out of date. Thus,
6048: changes without increasing PKGREVISION are essentially labeled "this is so
6049: trivial that no reasonable person would want to upgrade", and this is the rough
6050: test for when increasing PKGREVISION is appropriate. Examples of changes that
6051: do not merit increasing PKGREVISION are:
6052:
1.14 jmcneill 6053: * Changing HOMEPAGE, MAINTAINER, OWNER, or comments in Makefile.
1.1 dsieger 6054:
6055: * Changing build variables if the resulting binary package is the same.
6056:
6057: * Changing DESCR.
6058:
6059: * Adding PKG_OPTIONS if the default options don't change.
6060:
6061: Examples of changes that do merit an increase to PKGREVISION include:
6062:
6063: * Security fixes
6064:
6065: * Changes or additions to a patch file
6066:
6067: * Changes to the PLIST
6068:
1.12 weinem 6069: * A dependency is changed or renamed.
6070:
1.1 dsieger 6071: PKGREVISION must also be incremented when dependencies have ABI changes.
6072:
1.108 rillig 6073: 19.1.11. Substituting variable text in the package files (the SUBST framework)
1.1 dsieger 6074:
6075: When you want to replace the same text in multiple files or when the
6076: replacement text varies, patches alone cannot help. This is where the SUBST
6077: framework comes in. It provides an easy-to-use interface for replacing text in
6078: files. Example:
6079:
6080: SUBST_CLASSES+= fix-paths
6081: SUBST_STAGE.fix-paths= pre-configure
6082: SUBST_MESSAGE.fix-paths= Fixing absolute paths.
6083: SUBST_FILES.fix-paths= src/*.c
6084: SUBST_FILES.fix-paths+= scripts/*.sh
6085: SUBST_SED.fix-paths= -e 's,"/usr/local,"${PREFIX},g'
6086: SUBST_SED.fix-paths+= -e 's,"/var/log,"${VARBASE}/log,g'
6087:
6088: SUBST_CLASSES is a list of identifiers that are used to identify the different
6089: SUBST blocks that are defined. The SUBST framework is heavily used by pkgsrc,
6090: so it is important to always use the += operator with this variable. Otherwise
6091: some substitutions may be skipped.
6092:
6093: The remaining variables of each SUBST block are parameterized with the
6094: identifier from the first line (fix-paths in this case.) They can be seen as
6095: parameters to a function call.
6096:
6097: SUBST_STAGE.* specifies the stage at which the replacement will take place. All
6098: combinations of pre-, do- and post- together with a phase name are possible,
6099: though only few are actually used. Most commonly used are post-patch and
6100: pre-configure. Of these two, pre-configure should be preferred because then it
6101: is possible to run bmake patch and have the state after applying the patches
6102: but before making any other changes. This is especially useful when you are
6103: debugging a package in order to create new patches for it. Similarly,
6104: post-build is preferred over pre-install, because the install phase should
6105: generally be kept as simple as possible. When you use post-build, you have the
6106: same files in the working directory that will be installed later, so you can
6107: check if the substitution has succeeded.
6108:
6109: SUBST_MESSAGE.* is an optional text that is printed just before the
6110: substitution is done.
6111:
6112: SUBST_FILES.* is the list of shell globbing patterns that specifies the files
6113: in which the substitution will take place. The patterns are interpreted
6114: relatively to the WRKSRC directory.
6115:
6116: SUBST_SED.* is a list of arguments to sed(1) that specify the actual
6117: substitution. Every sed command should be prefixed with -e, so that all SUBST
6118: blocks look uniform.
6119:
6120: There are some more variables, but they are so seldomly used that they are only
6121: documented in the mk/subst.mk file.
6122:
1.108 rillig 6123: 19.2. The fetch phase
1.1 dsieger 6124:
1.6 rillig 6125: 19.2.1. Packages whose distfiles aren't available for plain downloading
1.1 dsieger 6126:
6127: If you need to download from a dynamic URL you can set DYNAMIC_MASTER_SITES and
6128: a make fetch will call files/getsite.sh with the name of each file to download
6129: as an argument, expecting it to output the URL of the directory from which to
6130: download it. graphics/ns-cult3d is an example of this usage.
6131:
6132: If the download can't be automated, because the user must submit personal
6133: information to apply for a password, or must pay for the source, or whatever,
6134: you can set FETCH_MESSAGE to a list of lines that are displayed to the user
6135: before aborting the build. Example:
6136:
6137: FETCH_MESSAGE= "Please download the files"
6138: FETCH_MESSAGE+= " "${DISTFILES:Q}
6139: FETCH_MESSAGE+= "manually from "${MASTER_SITES:Q}"."
6140:
1.6 rillig 6141: 19.2.2. How to handle modified distfiles with the 'old' name
1.1 dsieger 6142:
6143: Sometimes authors of a software package make some modifications after the
6144: software was released, and they put up a new distfile without changing the
6145: package's version number. If a package is already in pkgsrc at that time, the
6146: checksum will no longer match. The contents of the new distfile should be
6147: compared against the old one before changing anything, to make sure the
6148: distfile was really updated on purpose, and that no trojan horse or so crept
6149: in. Please mention that the distfiles were compared and what was found in your
1.54 rodent 6150: commit message.
6151:
6152: Then, the correct way to work around this is to set DIST_SUBDIR to a unique
1.109 wiz 6153: directory name, usually based on PKGNAME_NOREV (but take care with python or
6154: ruby packages, where PKGNAME includes a variable prefix). All DISTFILES and
6155: PATCHFILES for this package will be put in that subdirectory of the local
6156: distfiles directory. (See Section 19.1.10, "How to handle incrementing versions
6157: when fixing an existing package" for more details.) In case this happens more
6158: often, PKGNAME can be used (thus including the nbX suffix) or a date stamp can
6159: be appended, like ${PKGNAME_NOREV}-YYYYMMDD.
1.54 rodent 6160:
6161: DIST_SUBDIR is also used when a distfile's name does not contain a version and
6162: the distfile is apt to change. In cases where the likelihood of this is very
6163: small, DIST_SUBDIR might not be required. Additionally, DIST_SUBDIR must not be
6164: removed unless the distfile name changes, even if a package is being moved or
6165: renamed.
6166:
6167: Do not forget regenerating the distinfo file after that, since it contains the
6168: DIST_SUBDIR path in the filenames. Also, increase the PKGREVISION if the
6169: installed package is different. Furthermore, a mail to the package's authors
6170: seems appropriate telling them that changing distfiles after releases without
6171: changing the file names is not good practice.
1.1 dsieger 6172:
1.88 tnn 6173: 19.2.3. Packages hosted on github.com
6174:
1.90 tnn 6175: Helper methods exist for packages hosted on github.com which will often have
6176: distfile names that clash with other packages, for example 1.0.tar.gz. Use one
6177: of the three recipes from below:
1.88 tnn 6178:
6179: 19.2.3.1. Fetch based on a tagged release
6180:
6181: If your distfile URL looks similar to http://github.com/username/exampleproject
6182: /archive/v1.0.zip, then you are packaging a tagged release.
6183:
6184: DISTNAME= exampleproject-1.0
1.90 tnn 6185: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
6186: #GITHUB_PROJECT= # can be omitted if same as DISTNAME
6187: GITHUB_TAG= v${PKGVERSION_NOREV}
1.88 tnn 6188: EXTRACT_SUFX= .zip
6189:
6190: 19.2.3.2. Fetch based on a specific commit
6191:
6192: If your distfile URL looks similar to http://github.com/example/example/archive
6193: /988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz, then you are packaging a
6194: specific commit not tied to a release.
6195:
6196: DISTNAME= example-1.0
1.107 jnemeth 6197: MASTER_SITES= ${MASTER_SITE_GITHUB:=example/}
1.90 tnn 6198: #GITHUB_PROJECT= # can be omitted if same as DISTNAME
6199: GITHUB_TAG= 988881adc9fc3655077dc2d4d757d480b5ea0e11
1.88 tnn 6200:
6201: 19.2.3.3. Fetch based on release
6202:
6203: If your distfile URL looks similar to http://github.com/username/exampleproject
6204: /releases/download/rel-1.6/offensive-1.6.zip, then you are packaging a release.
6205:
1.90 tnn 6206: DISTNAME= offensive-1.6
1.88 tnn 6207: PKGNAME= ${DISTNAME:S/offensive/proper/}
1.90 tnn 6208: MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
6209: GITHUB_PROJECT= exampleproject
6210: GITHUB_RELEASE= rel-${PKGVERSION_NOREV} # usually just set this to ${DISTNAME}
6211: EXTRACT_SUFX= .zip
1.88 tnn 6212:
1.108 rillig 6213: 19.3. The configure phase
1.1 dsieger 6214:
1.6 rillig 6215: 19.3.1. Shared libraries - libtool
1.1 dsieger 6216:
6217: pkgsrc supports many different machines, with different object formats like
6218: a.out and ELF, and varying abilities to do shared library and dynamic loading
6219: at all. To accompany this, varying commands and options have to be passed to
6220: the compiler, linker, etc. to get the Right Thing, which can be pretty annoying
6221: especially if you don't have all the machines at your hand to test things. The
6222: devel/libtool pkg can help here, as it just "knows" how to build both static
6223: and dynamic libraries from a set of source files, thus being
6224: platform-independent.
6225:
6226: Here's how to use libtool in a package in seven simple steps:
6227:
6228: 1. Add USE_LIBTOOL=yes to the package Makefile.
6229:
6230: 2. For library objects, use "${LIBTOOL} --mode=compile ${CC}" in place of "$
6231: {CC}". You could even add it to the definition of CC, if only libraries are
6232: being built in a given Makefile. This one command will build both PIC and
6233: non-PIC library objects, so you need not have separate shared and
6234: non-shared library rules.
6235:
6236: 3. For the linking of the library, remove any "ar", "ranlib", and "ld
6237: -Bshareable" commands, and instead use:
6238:
6239: ${LIBTOOL} --mode=link \
6240: ${CC} -o ${.TARGET:.a=.la} \
6241: ${OBJS:.o=.lo} \
6242: -rpath ${PREFIX}/lib \
6243: -version-info major:minor
6244:
6245: Note that the library is changed to have a .la extension, and the objects
6246: are changed to have a .lo extension. Change OBJS as necessary. This
6247: automatically creates all of the .a, .so.major.minor, and ELF symlinks (if
6248: necessary) in the build directory. Be sure to include "-version-info",
6249: especially when major and minor are zero, as libtool will otherwise strip
6250: off the shared library version.
6251:
6252: From the libtool manual:
6253:
6254: So, libtool library versions are described by three integers:
6255:
6256: CURRENT
6257: The most recent interface number that this library implements.
6258:
6259: REVISION
6260: The implementation number of the CURRENT interface.
6261:
6262: AGE
6263: The difference between the newest and oldest interfaces that
6264: this library implements. In other words, the library implements
6265: all the interface numbers in the range from number `CURRENT -
6266: AGE' to `CURRENT'.
6267:
6268: If two libraries have identical CURRENT and AGE numbers, then the
6269: dynamic linker chooses the library with the greater REVISION number.
6270:
6271: The "-release" option will produce different results for a.out and ELF
1.25 wiz 6272: (excluding symlinks) in only one case. An ELF library of the form "
6273: libfoo-release.so.x.y" will have a symlink of "libfoo.so.x.y" on an a.out
1.1 dsieger 6274: platform. This is handled automatically.
6275:
6276: The "-rpath argument" is the install directory of the library being built.
6277:
6278: In the PLIST, include only the .la file, the other files will be added
6279: automatically.
6280:
6281: 4. When linking shared object (.so) files, i.e. files that are loaded via
6282: dlopen(3), NOT shared libraries, use "-module -avoid-version" to prevent
6283: them getting version tacked on.
6284:
6285: The PLIST file gets the foo.so entry.
6286:
6287: 5. When linking programs that depend on these libraries before they are
6288: installed, preface the cc(1) or ld(1) line with "${LIBTOOL} --mode=link",
6289: and it will find the correct libraries (static or shared), but please be
6290: aware that libtool will not allow you to specify a relative path in -L
6291: (such as "-L../somelib"), because it expects you to change that argument to
6292: be the .la file. e.g.
6293:
6294: ${LIBTOOL} --mode=link ${CC} -o someprog -L../somelib -lsomelib
6295:
6296: should be changed to:
6297:
6298: ${LIBTOOL} --mode=link ${CC} -o someprog ../somelib/somelib.la
6299:
6300: and it will do the right thing with the libraries.
6301:
6302: 6. When installing libraries, preface the install(1) or cp(1) command with "$
6303: {LIBTOOL} --mode=install", and change the library name to .la. e.g.
6304:
1.23 jakllsch 6305: ${LIBTOOL} --mode=install ${BSD_INSTALL_LIB} ${SOMELIB:.a=.la} ${PREFIX}/lib
1.1 dsieger 6306:
6307: This will install the static .a, shared library, any needed symlinks, and
6308: run ldconfig(8).
6309:
6310: 7. In your PLIST, include only the .la file (this is a change from previous
6311: behaviour).
6312:
1.6 rillig 6313: 19.3.2. Using libtool on GNU packages that already support libtool
1.1 dsieger 6314:
6315: Add USE_LIBTOOL=yes to the package Makefile. This will override the package's
6316: own libtool in most cases. For older libtool using packages, libtool is made by
6317: ltconfig script during the do-configure step; you can check the libtool script
6318: location by doing make configure; find work*/ -name libtool.
6319:
6320: LIBTOOL_OVERRIDE specifies which libtool scripts, relative to WRKSRC, to
6321: override. By default, it is set to "libtool */libtool */*/libtool". If this
6322: does not match the location of the package's libtool script(s), set it as
6323: appropriate.
6324:
6325: If you do not need *.a static libraries built and installed, then use
6326: SHLIBTOOL_OVERRIDE instead.
6327:
6328: If your package makes use of the platform-independent library for loading
6329: dynamic shared objects, that comes with libtool (libltdl), you should include
6330: devel/libltdl/buildlink3.mk.
6331:
6332: Some packages use libtool incorrectly so that the package may not work or build
6333: in some circumstances. Some of the more common errors are:
6334:
6335: * The inclusion of a shared object (-module) as a dependent library in an
6336: executable or library. This in itself isn't a problem if one of two things
6337: has been done:
6338:
6339: 1. The shared object is named correctly, i.e. libfoo.la, not foo.la
6340:
6341: 2. The -dlopen option is used when linking an executable.
6342:
6343: * The use of libltdl without the correct calls to initialisation routines.
6344: The function lt_dlinit() should be called and the macro
6345: LTDL_SET_PRELOADED_SYMBOLS included in executables.
6346:
1.6 rillig 6347: 19.3.3. GNU Autoconf/Automake
1.1 dsieger 6348:
6349: If a package needs GNU autoconf or automake to be executed to regenerate the
6350: configure script and Makefile.in makefile templates, then they should be
6351: executed in a pre-configure target.
6352:
6353: For packages that need only autoconf:
6354:
6355: AUTOCONF_REQD= 2.50 # if default version is not good enough
6356: USE_TOOLS+= autoconf # use "autoconf213" for autoconf-2.13
6357: ...
6358:
6359: pre-configure:
6360: cd ${WRKSRC} && autoconf
6361:
6362: ...
6363:
6364: and for packages that need automake and autoconf:
6365:
6366: AUTOMAKE_REQD= 1.7.1 # if default version is not good enough
6367: USE_TOOLS+= automake # use "automake14" for automake-1.4
6368: ...
6369:
6370: pre-configure:
6371: set -e; cd ${WRKSRC}; \
6372: aclocal; autoheader; automake -a --foreign -i; autoconf
6373:
6374: ...
6375:
6376: Packages which use GNU Automake will almost certainly require GNU Make.
6377:
6378: There are times when the configure process makes additional changes to the
6379: generated files, which then causes the build process to try to re-execute the
6380: automake sequence. This is prevented by touching various files in the configure
6381: stage. If this causes problems with your package you can set AUTOMAKE_OVERRIDE=
6382: NO in the package Makefile.
6383:
1.6 rillig 6384: 19.4. Programming languages
1.1 dsieger 6385:
1.6 rillig 6386: 19.4.1. C, C++, and Fortran
1.1 dsieger 6387:
6388: Compilers for the C, C++, and Fortran languages comes with the NetBSD base
6389: system. By default, pkgsrc assumes that a package is written in C and will hide
1.6 rillig 6390: all other compilers (via the wrapper framework, see Chapter 14, Buildlink
1.1 dsieger 6391: methodology).
6392:
6393: To declare which language's compiler a package needs, set the USE_LANGUAGES
6394: variable. Allowed values currently are "c", "c++", and "fortran" (and any
6395: combination). The default is "c". Packages using GNU configure scripts, even if
6396: written in C++, usually need a C compiler for the configure phase.
6397:
1.6 rillig 6398: 19.4.2. Java
1.1 dsieger 6399:
6400: If a program is written in Java, use the Java framework in pkgsrc. The package
6401: must include ../../mk/java-vm.mk. This Makefile fragment provides the following
6402: variables:
6403:
6404: * USE_JAVA defines if a build dependency on the JDK is added. If USE_JAVA is
6405: set to "run", then there is only a runtime dependency on the JDK. The
6406: default is "yes", which also adds a build dependency on the JDK.
6407:
6408: * Set USE_JAVA2 to declare that a package needs a Java2 implementation. The
6409: supported values are "yes", "1.4", and "1.5". "yes" accepts any Java2
6410: implementation, "1.4" insists on versions 1.4 or above, and "1.5" only
6411: accepts versions 1.5 or above. This variable is not set by default.
6412:
1.25 wiz 6413: * PKG_JAVA_HOME is automatically set to the runtime location of the used Java
6414: implementation dependency. It may be used to set JAVA_HOME to a good value
6415: if the program needs this variable to be defined.
6416:
1.6 rillig 6417: 19.4.3. Packages containing perl scripts
1.1 dsieger 6418:
6419: If your package contains interpreted perl scripts, add "perl" to the USE_TOOLS
6420: variable and set REPLACE_PERL to ensure that the proper interpreter path is
6421: set. REPLACE_PERL should contain a list of scripts, relative to WRKSRC, that
1.74 wiz 6422: you want adjusted. Every occurrence of */bin/perl in a she-bang line will be
6423: replaced with the full path to the perl executable.
1.1 dsieger 6424:
6425: If a particular version of perl is needed, set the PERL5_REQD variable to the
6426: version number. The default is "5.0".
6427:
1.6 rillig 6428: See Section 19.6.6, "Packages installing perl modules" for information about
1.1 dsieger 6429: handling perl modules.
6430:
1.41 wiz 6431: 19.4.4. Packages containing shell scripts
6432:
6433: REPLACE_SH, REPLACE_BASH, REPLACE_CSH, and REPLACE_KSH can be used to replace
6434: shell hash bangs in files. Please use the appropriate one, prefering REPLACE_SH
1.74 wiz 6435: in case this shell is sufficient. Each should contain a list of scripts,
6436: relative to WRKSRC, that you want adjusted. Every occurrence of the matching
6437: shell in a she-bang line will be replaced with the full path to the shell
6438: executable. When using REPLACE_BASH, don't forget to add bash to USE_TOOLS.
1.41 wiz 6439:
6440: 19.4.5. Other programming languages
1.1 dsieger 6441:
6442: Currently, there is no special handling for other languages in pkgsrc. If a
6443: compiler package provides a buildlink3.mk file, include that, otherwise just
6444: add a (build) dependency on the appropriate compiler package.
6445:
1.108 rillig 6446: 19.5. The build phase
1.1 dsieger 6447:
6448: The most common failures when building a package are that some platforms do not
6449: provide certain header files, functions or libraries, or they provide the
6450: functions in a library that the original package author didn't know. To work
6451: around this, you can rewrite the source code in most cases so that it does not
6452: use the missing functions or provides a replacement function.
6453:
1.6 rillig 6454: 19.5.1. Compiling C and C++ code conditionally
1.1 dsieger 6455:
6456: If a package already comes with a GNU configure script, the preferred way to
6457: fix the build failure is to change the configure script, not the code. In the
6458: other cases, you can utilize the C preprocessor, which defines certain macros
6459: depending on the operating system and hardware architecture it compiles for.
6460: These macros can be queried using for example #if defined(__i386). Almost every
6461: operating system, hardware architecture and compiler has its own macro. For
6462: example, if the macros __GNUC__, __i386__ and __NetBSD__ are all defined, you
6463: know that you are using NetBSD on an i386 compatible CPU, and your compiler is
6464: GCC.
6465:
6466: The list of the following macros for hardware and operating system depends on
6467: the compiler that is used. For example, if you want to conditionally compile
6468: code on Solaris, don't use __sun__, as the SunPro compiler does not define it.
6469: Use __sun instead.
6470:
1.6 rillig 6471: 19.5.1.1. C preprocessor macros to identify the operating system
1.1 dsieger 6472:
6473: To distinguish between 4.4 BSD-derived systems and the rest of the world, you
6474: should use the following code.
6475:
6476: #include <sys/param.h>
6477: #if (defined(BSD) && BSD >= 199306)
6478: /* BSD-specific code goes here */
6479: #else
6480: /* non-BSD-specific code goes here */
6481: #endif
6482:
6483: If this distinction is not fine enough, you can also test for the following
6484: macros.
6485:
1.46 obache 6486: Cygwin __CYGWIN__
6487: DragonFly __DragonFly__
1.1 dsieger 6488: FreeBSD __FreeBSD__
1.46 obache 6489: Haiku __HAIKU__
1.1 dsieger 6490: Interix __INTERIX
6491: IRIX __sgi (TODO: get a definite source for this)
6492: Linux linux, __linux, __linux__
1.83 dholland 6493: Mac OS X __APPLE__
1.46 obache 6494: MirBSD __MirBSD__ (__OpenBSD__ is also defined)
6495: Minix3 __minix
1.1 dsieger 6496: NetBSD __NetBSD__
6497: OpenBSD __OpenBSD__
6498: Solaris sun, __sun
6499:
1.6 rillig 6500: 19.5.1.2. C preprocessor macros to identify the hardware architecture
1.1 dsieger 6501:
6502: i386 i386, __i386, __i386__
6503: MIPS __mips
6504: SPARC sparc, __sparc
6505:
1.6 rillig 6506: 19.5.1.3. C preprocessor macros to identify the compiler
1.1 dsieger 6507:
6508: GCC __GNUC__ (major version), __GNUC_MINOR__
6509: MIPSpro _COMPILER_VERSION (0x741 for MIPSpro 7.41)
6510: SunPro __SUNPRO_C (0x570 for Sun C 5.7)
6511: SunPro C++ __SUNPRO_CC (0x580 for Sun C++ 5.8)
6512:
1.6 rillig 6513: 19.5.2. How to handle compiler bugs
1.1 dsieger 6514:
6515: Some source files trigger bugs in the compiler, based on combinations of
6516: compiler version and architecture and almost always relation to optimisation
6517: being enabled. Common symptoms are gcc internal errors or never finishing
6518: compiling a file.
6519:
6520: Typically, a workaround involves testing the MACHINE_ARCH and compiler version,
1.87 tnn 6521: disabling optimisation for that combination of file, MACHINE_ARCH and compiler.
6522:
6523: This used to be a big problem in the past, but is rarely needed now as compiler
6524: technology has matured. If you still need to add a compiler specific
6525: workaround, please do so in the file hacks.mk and describe the symptom and
6526: compiler version as detailed as possible.
1.1 dsieger 6527:
1.6 rillig 6528: 19.5.3. Undefined reference to "..."
1.1 dsieger 6529:
6530: This error message often means that a package did not link to a shared library
6531: it needs. The following functions are known to cause this error message over
6532: and over.
6533:
6534: +-----------------------------------------------------+
6535: | Function |Library |Affected platforms|
6536: |-------------------------+--------+------------------|
6537: |accept, bind, connect |-lsocket|Solaris |
6538: |-------------------------+--------+------------------|
6539: |crypt |-lcrypt |DragonFly, NetBSD |
6540: |-------------------------+--------+------------------|
6541: |dlopen, dlsym |-ldl |Linux |
6542: |-------------------------+--------+------------------|
6543: |gethost* |-lnsl |Solaris |
6544: |-------------------------+--------+------------------|
6545: |inet_aton |-lresolv|Solaris |
6546: |-------------------------+--------+------------------|
6547: |nanosleep, sem_*, timer_*|-lrt |Solaris |
6548: |-------------------------+--------+------------------|
6549: |openpty |-lutil |Linux |
6550: +-----------------------------------------------------+
6551:
6552: To fix these linker errors, it is often sufficient to say LIBS.OperatingSystem+
6553: = -lfoo to the package Makefile and then say bmake clean; bmake.
6554:
1.6 rillig 6555: 19.5.3.1. Special issue: The SunPro compiler
1.1 dsieger 6556:
6557: When you are using the SunPro compiler, there is another possibility. That
6558: compiler cannot handle the following code:
6559:
6560: extern int extern_func(int);
6561:
6562: static inline int
6563: inline_func(int x)
6564: {
6565: return extern_func(x);
6566: }
6567:
6568: int main(void)
6569: {
6570: return 0;
6571: }
6572:
6573: It generates the code for inline_func even if that function is never used. This
6574: code then refers to extern_func, which can usually not be resolved. To solve
6575: this problem you can try to tell the package to disable inlining of functions.
6576:
1.6 rillig 6577: 19.5.4. Running out of memory
1.1 dsieger 6578:
6579: Sometimes packages fail to build because the compiler runs into an operating
6580: system specific soft limit. With the UNLIMIT_RESOURCES variable pkgsrc can be
1.94 wiz 6581: told to unlimit the resources. Currently, the allowed values are any
6582: combination of "cputime", "datasize", "memorysize", and "stacksize". Setting
6583: this variable is similar to running the shell builtin ulimit command to raise
6584: the maximum data segment size or maximum stack size of a process, respectively,
6585: to their hard limits.
1.1 dsieger 6586:
1.108 rillig 6587: 19.6. The install phase
1.1 dsieger 6588:
1.6 rillig 6589: 19.6.1. Creating needed directories
1.1 dsieger 6590:
6591: The BSD-compatible install supplied with some operating systems cannot create
6592: more than one directory at a time. As such, you should call ${INSTALL_*_DIR}
6593: like this:
6594:
6595: ${INSTALL_DATA_DIR} ${PREFIX}/dir1
6596: ${INSTALL_DATA_DIR} ${PREFIX}/dir2
6597:
6598: You can also just append "dir1 dir2" to the INSTALLATION_DIRS variable, which
6599: will automatically do the right thing.
6600:
1.6 rillig 6601: 19.6.2. Where to install documentation
1.1 dsieger 6602:
6603: In general, documentation should be installed into ${PREFIX}/share/doc/$
6604: {PKGBASE} or ${PREFIX}/share/doc/${PKGNAME} (the latter includes the version
6605: number of the package).
6606:
6607: Many modern packages using GNU autoconf allow to set the directory where HTML
6608: documentation is installed with the "--with-html-dir" option. Sometimes using
6609: this flag is needed because otherwise the documentation ends up in ${PREFIX}/
6610: share/doc/html or other places.
6611:
6612: An exception to the above is that library API documentation generated with the
6613: textproc/gtk-doc tools, for use by special browsers (devhelp) should be left at
6614: their default location, which is ${PREFIX}/share/gtk-doc. Such documentation
6615: can be recognized from files ending in .devhelp or .devhelp2. (It is also
6616: acceptable to install such files in ${PREFIX}/share/doc/${PKGBASE} or ${PREFIX}
6617: /share/doc/${PKGNAME}; the .devhelp* file must be directly in that directory
6618: then, no additional subdirectory level is allowed in this case. This is usually
6619: achieved by using "--with-html-dir=${PREFIX}/share/doc". ${PREFIX}/share/
6620: gtk-doc is preferred though.)
6621:
1.6 rillig 6622: 19.6.3. Installing highscore files
1.1 dsieger 6623:
6624: Certain packages, most of them in the games category, install a score file that
6625: allows all users on the system to record their highscores. In order for this to
6626: work, the binaries need to be installed setgid and the score files owned by the
1.36 wiz 6627: appropriate group and/or owner (traditionally the "games" user/group). Set
6628: USE_GAMESGROUP to yes to support this. The following variables, documented in
6629: more detail in mk/defaults/mk.conf, control this behaviour: GAMEDATAMODE,
1.100 leot 6630: GAMEDIRMODE, GAMES_GROUP, GAMEMODE, GAME_USER. Other useful variables are:
6631: GAMEDIR_PERMS, GAMEDATA_PERMS and SETGID_GAMES_PERMS.
6632:
6633: An example that illustrates some of the variables described above is games/
6634: moon-buggy. OWN_DIRS_PERMS is used to properly set directory permissions of the
6635: directory where the scorefile is saved, REQD_FILES_PERMS is used to create a
6636: dummy scorefile (mbscore) with the proper permissions and SPECIAL_PERMS is used
6637: to install setgid the game binary:
6638:
6639: USE_GAMESGROUP= yes
6640:
6641: BUILD_DEFS+= VARBASE
6642:
6643: OWN_DIRS_PERMS+= ${VARBASE}/games/moon-buggy ${GAMEDIR_PERMS}
6644: REQD_FILES_PERMS+= /dev/null ${VARBASE}/games/moon-buggy/mbscore ${GAMEDATA_PERMS}
6645: SPECIAL_PERMS+= ${PREFIX}/bin/moon-buggy ${SETGID_GAMES_PERMS}
6646:
6647: Various INSTALL_* variables are also available: INSTALL_GAME to install setgid
6648: game binaries, INSTALL_GAME_DIR to install game directories that are needed to
6649: be accessed by setgid games and INSTALL_GAME_DATA to install scorefiles.
1.1 dsieger 6650:
1.14 jmcneill 6651: A package should therefore never hard code file ownership or access permissions
1.100 leot 6652: but rely on *_PERMS as described above or alternatively on INSTALL_GAME,
6653: INSTALL_GAME_DATA and INSTALL_GAME_DIR to set these correctly.
1.1 dsieger 6654:
1.6 rillig 6655: 19.6.4. Adding DESTDIR support to packages
1.4 rillig 6656:
1.14 jmcneill 6657: DESTDIR support means that a package installs into a staging directory, not the
6658: final location of the files. Then a binary package is created which can be used
6659: for installation as usual. There are two ways: Either the package must install
1.25 wiz 6660: as root ("destdir") or the package can install as non-root user ("user-destdir"
6661: ).
1.14 jmcneill 6662:
1.113 leot 6663: * PKG_DESTDIR_SUPPORT has to be set to "destdir" or "user-destdir". By
6664: default PKG_DESTDIR_SUPPORT is set to "user-destdir" to help catching more
6665: potential packaging problems. If bsd.prefs.mk is included in the Makefile,
6666: PKG_DESTDIR_SUPPORT needs to be set before the inclusion.
1.14 jmcneill 6667:
1.4 rillig 6668: * All installation operations have to be prefixed with ${DESTDIR}.
6669:
6670: * automake gets this DESTDIR mostly right automatically. Many manual rules
6671: and pre/post-install often are incorrect; fix them.
6672:
1.17 imil 6673: * If files are installed with special owner/group use SPECIAL_PERMS.
1.4 rillig 6674:
6675: * In general, packages should support UNPRIVILEGED to be able to use DESTDIR.
6676:
1.6 rillig 6677: 19.6.5. Packages with hardcoded paths to other interpreters
1.1 dsieger 6678:
6679: Your package may also contain scripts with hardcoded paths to other
6680: interpreters besides (or as well as) perl. To correct the full pathname to the
6681: script interpreter, you need to set the following definitions in your Makefile
6682: (we shall use tclsh in this example):
6683:
6684: REPLACE_INTERPRETER+= tcl
6685: REPLACE.tcl.old= .*/bin/tclsh
6686: REPLACE.tcl.new= ${PREFIX}/bin/tclsh
6687: REPLACE_FILES.tcl= # list of tcl scripts which need to be fixed,
6688: # relative to ${WRKSRC}, just as in REPLACE_PERL
6689:
6690: Note
6691:
6692: Before March 2006, these variables were called _REPLACE.* and _REPLACE_FILES.*.
6693:
1.6 rillig 6694: 19.6.6. Packages installing perl modules
1.1 dsieger 6695:
6696: Makefiles of packages providing perl5 modules should include the Makefile
6697: fragment ../../lang/perl5/module.mk. It provides a do-configure target for the
6698: standard perl configuration for such modules as well as various hooks to tune
6699: this configuration. See comments in this file for details.
6700:
6701: Perl5 modules will install into different places depending on the version of
6702: perl used during the build process. To address this, pkgsrc will append lines
6703: to the PLIST corresponding to the files listed in the installed .packlist file
6704: generated by most perl5 modules. This is invoked by defining PERL5_PACKLIST to
1.48 wiz 6705: a space-separated list of packlist files relative to PERL5_PACKLIST_DIR
6706: (PERL5_INSTALLVENDORARCH by default), e.g.:
1.1 dsieger 6707:
1.48 wiz 6708: PERL5_PACKLIST= auto/Pg/.packlist
1.1 dsieger 6709:
1.48 wiz 6710: The perl5 config variables installarchlib, installscript, installvendorbin,
6711: installvendorscript, installvendorarch, installvendorlib, installvendorman1dir,
6712: and installvendorman3dir represent those locations in which components of perl5
6713: modules may be installed, provided as variable with uppercase and prefixed with
6714: PERL5_, e.g. PERL5_INSTALLARCHLIB and may be used by perl5 packages that don't
6715: have a packlist. These variables are also substituted for in the PLIST as
6716: uppercase prefixed with PERL5_SUB_.
1.1 dsieger 6717:
1.6 rillig 6718: 19.6.7. Packages installing info files
1.1 dsieger 6719:
6720: Some packages install info files or use the "makeinfo" or "install-info"
6721: commands. INFO_FILES should be defined in the package Makefile so that INSTALL
6722: and DEINSTALL scripts will be generated to handle registration of the info
6723: files in the Info directory file. The "install-info" command used for the info
6724: files registration is either provided by the system, or by a special purpose
6725: package automatically added as dependency if needed.
6726:
6727: PKGINFODIR is the directory under ${PREFIX} where info files are primarily
6728: located. PKGINFODIR defaults to "info" and can be overridden by the user.
6729:
6730: The info files for the package should be listed in the package PLIST; however
6731: any split info files need not be listed.
6732:
6733: A package which needs the "makeinfo" command at build time must add "makeinfo"
6734: to USE_TOOLS in its Makefile. If a minimum version of the "makeinfo" command is
6735: needed it should be noted with the TEXINFO_REQD variable in the package
6736: Makefile. By default, a minimum version of 3.12 is required. If the system does
6737: not provide a makeinfo command or if it does not match the required minimum, a
6738: build dependency on the devel/gtexinfo package will be added automatically.
6739:
6740: The build and installation process of the software provided by the package
6741: should not use the install-info command as the registration of info files is
1.25 wiz 6742: the task of the package INSTALL script, and it must use the appropriate
1.1 dsieger 6743: makeinfo command.
6744:
6745: To achieve this goal, the pkgsrc infrastructure creates overriding scripts for
6746: the install-info and makeinfo commands in a directory listed early in PATH.
6747:
6748: The script overriding install-info has no effect except the logging of a
6749: message. The script overriding makeinfo logs a message and according to the
6750: value of TEXINFO_REQD either runs the appropriate makeinfo command or exit on
6751: error.
6752:
1.6 rillig 6753: 19.6.8. Packages installing man pages
1.1 dsieger 6754:
6755: All packages that install manual pages should install them into the same
6756: directory, so that there is one common place to look for them. In pkgsrc, this
6757: place is ${PREFIX}/${PKGMANDIR}, and this expression should be used in
1.25 wiz 6758: packages. The default for PKGMANDIR is "man". Another often-used value is "
6759: share/man".
1.1 dsieger 6760:
6761: Note
6762:
6763: The support for a custom PKGMANDIR is far from complete.
6764:
6765: The PLIST files can just use man/ as the top level directory for the man page
6766: file entries, and the pkgsrc framework will convert as needed. In all other
6767: places, the correct PKGMANDIR must be used.
6768:
6769: Packages that are configured with GNU_CONFIGURE set as "yes", by default will
6770: use the ./configure --mandir switch to set where the man pages should be
6771: installed. The path is GNU_CONFIGURE_MANDIR which defaults to ${PREFIX}/$
6772: {PKGMANDIR}.
6773:
6774: Packages that use GNU_CONFIGURE but do not use --mandir, can set
6775: CONFIGURE_HAS_MANDIR to "no". Or if the ./configure script uses a non-standard
6776: use of --mandir, you can set GNU_CONFIGURE_MANDIR as needed.
6777:
1.6 rillig 6778: See Section 13.5, "Man page compression" for information on installation of
1.1 dsieger 6779: compressed manual pages.
6780:
1.7 rillig 6781: 19.6.9. Packages installing GConf data files
1.1 dsieger 6782:
1.7 rillig 6783: If a package installs .schemas or .entries files, used by GConf, you need to
1.1 dsieger 6784: take some extra steps to make sure they get registered in the database:
6785:
1.7 rillig 6786: 1. Include ../../devel/GConf/schemas.mk instead of its buildlink3.mk file.
6787: This takes care of rebuilding the GConf database at installation and
6788: deinstallation time, and tells the package where to install GConf data
1.1 dsieger 6789: files using some standard configure arguments. It also disallows any access
6790: to the database directly from the package.
6791:
6792: 2. Ensure that the package installs its .schemas files under ${PREFIX}/share/
6793: gconf/schemas. If they get installed under ${PREFIX}/etc, you will need to
6794: manually patch the package.
6795:
6796: 3. Check the PLIST and remove any entries under the etc/gconf directory, as
1.84 wiz 6797: they will be handled automatically. See Section 9.13, "How do I change the
1.1 dsieger 6798: location of configuration files?" for more information.
6799:
1.7 rillig 6800: 4. Define the GCONF_SCHEMAS variable in your Makefile with a list of all
1.1 dsieger 6801: .schemas files installed by the package, if any. Names must not contain any
6802: directories in them.
6803:
1.7 rillig 6804: 5. Define the GCONF_ENTRIES variable in your Makefile with a list of all
1.1 dsieger 6805: .entries files installed by the package, if any. Names must not contain any
6806: directories in them.
6807:
1.18 mishka 6808: 19.6.10. Packages installing scrollkeeper/rarian data files
1.1 dsieger 6809:
1.18 mishka 6810: If a package installs .omf files, used by scrollkeeper/rarian, you need to take
6811: some extra steps to make sure they get registered in the database:
1.1 dsieger 6812:
1.18 mishka 6813: 1. Include ../../mk/omf-scrollkeeper.mk instead of rarian's buildlink3.mk
6814: file. This takes care of rebuilding the scrollkeeper database at
6815: installation and deinstallation time, and disallows any access to it
6816: directly from the package.
1.1 dsieger 6817:
6818: 2. Check the PLIST and remove any entries under the libdata/scrollkeeper
6819: directory, as they will be handled automatically.
6820:
6821: 3. Remove the share/omf directory from the PLIST. It will be handled by
1.18 mishka 6822: rarian. (make print-PLIST does this automatically.)
1.1 dsieger 6823:
1.6 rillig 6824: 19.6.11. Packages installing X11 fonts
1.1 dsieger 6825:
6826: If a package installs font files, you will need to rebuild the fonts database
6827: in the directory where they get installed at installation and deinstallation
6828: time. This can be automatically done by using the pkginstall framework.
6829:
6830: You can list the directories where fonts are installed in the FONTS_DIRS.type
6831: variables, where type can be one of "ttf", "type1" or "x11". Also make sure
6832: that the database file fonts.dir is not listed in the PLIST.
6833:
6834: Note that you should not create new directories for fonts; instead use the
6835: standard ones to avoid that the user needs to manually configure his X server
6836: to find them.
6837:
1.6 rillig 6838: 19.6.12. Packages installing GTK2 modules
1.1 dsieger 6839:
6840: If a package installs GTK2 immodules or loaders, you need to take some extra
6841: steps to get them registered in the GTK2 database properly:
6842:
6843: 1. Include ../../x11/gtk2/modules.mk instead of its buildlink3.mk file. This
6844: takes care of rebuilding the database at installation and deinstallation
6845: time.
6846:
6847: 2. Set GTK2_IMMODULES=YES if your package installs GTK2 immodules.
6848:
6849: 3. Set GTK2_LOADERS=YES if your package installs GTK2 loaders.
6850:
6851: 4. Patch the package to not touch any of the GTK2 databases directly. These
6852: are:
6853:
1.42 asau 6854: + libdata/gtk-2.0/gdk-pixbuf.loaders
1.1 dsieger 6855:
1.42 asau 6856: + libdata/gtk-2.0/gtk.immodules
1.1 dsieger 6857:
6858: 5. Check the PLIST and remove any entries under the libdata/gtk-2.0 directory,
6859: as they will be handled automatically.
6860:
1.6 rillig 6861: 19.6.13. Packages installing SGML or XML data
1.1 dsieger 6862:
6863: If a package installs SGML or XML data files that need to be registered in
6864: system-wide catalogs (like DTDs, sub-catalogs, etc.), you need to take some
6865: extra steps:
6866:
6867: 1. Include ../../textproc/xmlcatmgr/catalogs.mk in your Makefile, which takes
6868: care of registering those files in system-wide catalogs at installation and
6869: deinstallation time.
6870:
6871: 2. Set SGML_CATALOGS to the full path of any SGML catalogs installed by the
6872: package.
6873:
6874: 3. Set XML_CATALOGS to the full path of any XML catalogs installed by the
6875: package.
6876:
6877: 4. Set SGML_ENTRIES to individual entries to be added to the SGML catalog.
6878: These come in groups of three strings; see xmlcatmgr(1) for more
6879: information (specifically, arguments recognized by the 'add' action). Note
6880: that you will normally not use this variable.
6881:
6882: 5. Set XML_ENTRIES to individual entries to be added to the XML catalog. These
6883: come in groups of three strings; see xmlcatmgr(1) for more information
6884: (specifically, arguments recognized by the 'add' action). Note that you
6885: will normally not use this variable.
6886:
1.6 rillig 6887: 19.6.14. Packages installing extensions to the MIME database
1.1 dsieger 6888:
6889: If a package provides extensions to the MIME database by installing .xml files
6890: inside ${PREFIX}/share/mime/packages, you need to take some extra steps to
6891: ensure that the database is kept consistent with respect to these new files:
6892:
6893: 1. Include ../../databases/shared-mime-info/mimedb.mk (avoid using the
6894: buildlink3.mk file from this same directory, which is reserved for
6895: inclusion from other buildlink3.mk files). It takes care of rebuilding the
6896: MIME database at installation and deinstallation time, and disallows any
6897: access to it directly from the package.
6898:
1.25 wiz 6899: 2. Check the PLIST and remove any entries under the share/mime directory,
1.1 dsieger 6900: except for files saved under share/mime/packages. The former are handled
6901: automatically by the update-mime-database program, but the latter are
6902: package-dependent and must be removed by the package that installed them in
6903: the first place.
6904:
6905: 3. Remove any share/mime/* directories from the PLIST. They will be handled by
6906: the shared-mime-info package.
6907:
1.6 rillig 6908: 19.6.15. Packages using intltool
1.1 dsieger 6909:
6910: If a package uses intltool during its build, add intltool to the USE_TOOLS,
6911: which forces it to use the intltool package provided by pkgsrc, instead of the
6912: one bundled with the distribution file.
6913:
6914: This tracks intltool's build-time dependencies and uses the latest available
6915: version; this way, the package benefits of any bug fixes that may have appeared
6916: since it was released.
6917:
1.6 rillig 6918: 19.6.16. Packages installing startup scripts
1.1 dsieger 6919:
6920: If a package contains a rc.d script, it won't be copied into the startup
6921: directory by default, but you can enable it, by adding the option
1.4 rillig 6922: PKG_RCD_SCRIPTS=YES in mk.conf. This option will copy the scripts into /etc/
6923: rc.d when a package is installed, and it will automatically remove the scripts
6924: when the package is deinstalled.
1.1 dsieger 6925:
1.6 rillig 6926: 19.6.17. Packages installing TeX modules
1.1 dsieger 6927:
6928: If a package installs TeX packages into the texmf tree, the ls-R database of
6929: the tree needs to be updated.
6930:
6931: Note
6932:
1.23 jakllsch 6933: Except the main TeX packages such as kpathsea, packages should install files
6934: into ${PREFIX}/share/texmf-dist, not ${PREFIX}/share/texmf.
1.1 dsieger 6935:
1.23 jakllsch 6936: 1. Include ../../print/kpathsea/texmf.mk. This takes care of rebuilding the
6937: ls-R database at installation and deinstallation time.
1.1 dsieger 6938:
1.23 jakllsch 6939: 2. If your package installs files into a texmf tree other than the one at $
6940: {PREFIX}/share/texmf-dist, set TEX_TEXMF_DIRS to the list of all texmf
6941: trees that need database update.
1.1 dsieger 6942:
6943: If your package also installs font map files that need to be registered
1.30 dholland 6944: using updmap, include ../../print/tex-tetex/map.mk and set TEX_MAP_FILES
6945: and/or TEX_MIXEDMAP_FILES to the list of all such font map files. Then
6946: updmap will be run automatically at installation/deinstallation to enable/
6947: disable font map files for TeX output drivers.
1.1 dsieger 6948:
6949: 3. Make sure that none of ls-R databases are included in PLIST, as they will
1.30 dholland 6950: be removed only by the kpathsea package.
1.1 dsieger 6951:
1.6 rillig 6952: 19.6.18. Packages supporting running binaries in emulation
1.1 dsieger 6953:
6954: There are some packages that provide libraries and executables for running
6955: binaries from a one operating system on a different one (if the latter supports
6956: it). One example is running Linux binaries on NetBSD.
6957:
6958: The pkgtools/rpm2pkg helps in extracting and packaging Linux rpm packages.
6959:
6960: The CHECK_SHLIBS can be set to no to avoid the check-shlibs target, which tests
6961: if all libraries for each installed executable can be found by the dynamic
6962: linker. Since the standard dynamic linker is run, this fails for emulation
6963: packages, because the libraries used by the emulation are not in the standard
6964: directories.
6965:
1.6 rillig 6966: 19.6.19. Packages installing hicolor theme icons
1.1 dsieger 6967:
6968: If a package installs images under the share/icons/hicolor and/or updates the
6969: share/icons/hicolor/icon-theme.cache database, you need to take some extra
6970: steps to make sure that the shared theme directory is handled appropriately and
6971: that the cache database is rebuilt:
6972:
6973: 1. Include ../../graphics/hicolor-icon-theme/buildlink3.mk.
6974:
6975: 2. Check the PLIST and remove the entry that refers to the theme cache.
6976:
6977: 3. Ensure that the PLIST does not remove the shared icon directories from the
6978: share/icons/hicolor hierarchy because they will be handled automatically.
6979:
6980: The best way to verify that the PLIST is correct with respect to the last two
6981: points is to regenerate it using make print-PLIST.
6982:
1.6 rillig 6983: 19.6.20. Packages installing desktop files
1.1 dsieger 6984:
6985: If a package installs .desktop files under share/applications and these include
1.54 rodent 6986: MIME information (MimeType key), you need to take extra steps to ensure that
6987: they are registered into the MIME database:
1.1 dsieger 6988:
6989: 1. Include ../../sysutils/desktop-file-utils/desktopdb.mk.
6990:
6991: 2. Check the PLIST and remove the entry that refers to the share/applications/
6992: mimeinfo.cache file. It will be handled automatically.
6993:
6994: The best way to verify that the PLIST is correct with respect to the last point
6995: is to regenerate it using make print-PLIST.
6996:
1.6 rillig 6997: 19.7. Marking packages as having problems
1.1 dsieger 6998:
1.23 jakllsch 6999: In some cases one does not have the time to solve a problem immediately. In
7000: this case, one can plainly mark a package as broken. For this, one just sets
7001: the variable BROKEN to the reason why the package is broken (similar to the
7002: RESTRICTED variable). A user trying to build the package will immediately be
7003: shown this message, and the build will not be even tried.
1.1 dsieger 7004:
1.23 jakllsch 7005: BROKEN packages are removed from pkgsrc in irregular intervals.
1.1 dsieger 7006:
1.6 rillig 7007: Chapter 20. Debugging
1.1 dsieger 7008:
7009: To check out all the gotchas when building a package, here are the steps that I
7010: do in order to get a package working. Please note this is basically the same as
7011: what was explained in the previous sections, only with some debugging aids.
7012:
1.4 rillig 7013: * Be sure to set PKG_DEVELOPER=yes in mk.conf.
1.1 dsieger 7014:
7015: * Install pkgtools/url2pkg, create a directory for a new package, change into
7016: it, then run url2pkg:
7017:
7018: % mkdir /usr/pkgsrc/category/examplepkg
7019: % cd /usr/pkgsrc/category/examplepkg
7020: % url2pkg http://www.example.com/path/to/distfile.tar.gz
7021:
7022: * Edit the Makefile as requested.
7023:
7024: * Fill in the DESCR file
7025:
7026: * Run make configure
7027:
7028: * Add any dependencies glimpsed from documentation and the configure step to
7029: the package's Makefile.
7030:
7031: * Make the package compile, doing multiple rounds of
7032:
7033: % make
7034: % pkgvi ${WRKSRC}/some/file/that/does/not/compile
7035: % mkpatches
7036: % patchdiff
7037: % mv ${WRKDIR}/.newpatches/* patches
7038: % make mps
7039: % make clean
7040:
7041: Doing this step as non-root user will ensure that no files are modified
7042: that shouldn't be, especially during the build phase. mkpatches, patchdiff
7043: and pkgvi are from the pkgtools/pkgdiff package.
7044:
1.6 rillig 7045: * Look at the Makefile, fix if necessary; see Section 11.1, "Makefile".
1.1 dsieger 7046:
7047: * Generate a PLIST:
7048:
7049: # make install
7050: # make print-PLIST >PLIST
7051: # make deinstall
7052: # make install
7053: # make deinstall
7054:
7055: You usually need to be root to do this. Look if there are any files left:
7056:
7057: # make print-PLIST
7058:
7059: If this reveals any files that are missing in PLIST, add them.
7060:
7061: * Now that the PLIST is OK, install the package again and make a binary
7062: package:
7063:
7064: # make reinstall
7065: # make package
7066:
7067: * Delete the installed package:
7068:
7069: # pkg_delete examplepkg
7070:
7071: * Repeat the above make print-PLIST command, which shouldn't find anything
7072: now:
7073:
7074: # make print-PLIST
7075:
7076: * Reinstall the binary package:
7077:
7078: # pkg_add .../examplepkg.tgz
7079:
7080: * Play with it. Make sure everything works.
7081:
7082: * Run pkglint from pkgtools/pkglint, and fix the problems it reports:
7083:
7084: # pkglint
7085:
1.6 rillig 7086: * Submit (or commit, if you have cvs access); see Chapter 21, Submitting and
1.1 dsieger 7087: Committing.
7088:
1.6 rillig 7089: Chapter 21. Submitting and Committing
1.1 dsieger 7090:
7091: Table of Contents
7092:
1.6 rillig 7093: 21.1. Submitting binary packages
7094: 21.2. Submitting source packages (for non-NetBSD-developers)
7095: 21.3. General notes when adding, updating, or removing packages
1.34 wiz 7096: 21.4. Committing: Adding a package to CVS
1.6 rillig 7097: 21.5. Updating a package to a newer version
1.21 snj 7098: 21.6. Renaming a package in pkgsrc
7099: 21.7. Moving a package in pkgsrc
1.1 dsieger 7100:
1.6 rillig 7101: 21.1. Submitting binary packages
1.1 dsieger 7102:
7103: Our policy is that we accept binaries only from pkgsrc developers to guarantee
7104: that the packages don't contain any trojan horses etc. This is not to annoy
7105: anyone but rather to protect our users! You're still free to put up your
7106: home-made binary packages and tell the world where to get them. NetBSD
1.66 asau 7107: developers doing bulk builds and wanting to upload them please see Chapter 7,
7108: Creating binary packages for everything in pkgsrc (bulk builds).
1.1 dsieger 7109:
1.6 rillig 7110: 21.2. Submitting source packages (for non-NetBSD-developers)
1.1 dsieger 7111:
7112: First, check that your package is complete, compiles and runs well; see
1.6 rillig 7113: Chapter 20, Debugging and the rest of this document. Next, generate an
1.1 dsieger 7114: uuencoded gzipped tar(1) archive that contains all files that make up the
7115: package. Finally, send this package to the pkgsrc bug tracking system, either
7116: with the send-pr(1) command, or if you don't have that, go to the web page
1.4 rillig 7117: http://www.NetBSD.org/support/send-pr.html, which contains some instructions
1.22 snj 7118: and a link to a form where you can submit packages. The sysutils/gtk-send-pr
7119: package is also available as a substitute for either of the above two tools.
1.1 dsieger 7120:
7121: In the form of the problem report, the category should be "pkg", the synopsis
7122: should include the package name and version number, and the description field
7123: should contain a short description of your package (contents of the COMMENT
1.25 wiz 7124: variable or DESCR file are OK). The uuencoded package data should go into the "
7125: fix" field.
1.1 dsieger 7126:
7127: If you want to submit several packages, please send a separate PR for each one,
7128: it's easier for us to track things that way.
7129:
7130: Alternatively, you can also import new packages into pkgsrc-wip ("pkgsrc
1.105 wiz 7131: work-in-progress"); see the homepage at http://pkgsrc.org/wip/ for details.
1.1 dsieger 7132:
1.6 rillig 7133: 21.3. General notes when adding, updating, or removing packages
1.1 dsieger 7134:
7135: Please note all package additions, updates, moves, and removals in pkgsrc/doc/
7136: CHANGES-YYYY. It's very important to keep this file up to date and conforming
7137: to the existing format, because it will be used by scripts to automatically
7138: update pages on www.NetBSD.org and other sites. Additionally, check the pkgsrc/
7139: doc/TODO file and remove the entry for the package you updated or removed, in
7140: case it was mentioned there.
7141:
7142: When the PKGREVISION of a package is bumped, the change should appear in pkgsrc
7143: /doc/CHANGES-YYYY if it is security related or otherwise relevant. Mass bumps
7144: that result from a dependency being updated should not be mentioned. In all
7145: other cases it's the developer's decision.
7146:
7147: There is a make target that helps in creating proper CHANGES-YYYY entries: make
7148: changes-entry. It uses the optional CTYPE and NETBSD_LOGIN_NAME variables. The
7149: general usage is to first make sure that your CHANGES-YYYY file is up-to-date
7150: (to avoid having to resolve conflicts later-on) and then to cd to the package
7151: directory. For package updates, make changes-entry is enough. For new packages,
7152: or package moves or removals, set the CTYPE variable on the command line to
1.4 rillig 7153: "Added", "Moved", or "Removed". You can set NETBSD_LOGIN_NAME in mk.conf if
1.23 jakllsch 7154: your local login name is not the same as your NetBSD login name. The target
7155: also automatically removes possibly existing entries for the package in the
7156: TODO file. Don't forget to commit the changes, e.g. by using make
1.66 asau 7157: commit-changes-entry! If you are not using a checkout directly from
1.23 jakllsch 7158: cvs.NetBSD.org, but e.g. a local copy of the repository, you can set
7159: USE_NETBSD_REPO=yes. This makes the cvs commands use the main repository.
1.1 dsieger 7160:
1.34 wiz 7161: 21.4. Committing: Adding a package to CVS
1.1 dsieger 7162:
7163: This section is only of interest for pkgsrc developers with write access to the
1.34 wiz 7164: pkgsrc repository.
7165:
7166: When the package is finished, "cvs add" the files. Start by adding the
7167: directory and then files in the directory. Don't forget to add the new package
7168: to the category's Makefile. Make sure you don't forget any files; you can check
7169: by running "cvs status". An example:
7170:
7171: $ cd .../pkgsrc/category
7172: $ cvs add pkgname
7173: $ cd pkgname
7174: $ cvs add DESCR Makefile PLIST distinfo buildlink3.mk patches
7175: $ cvs add patches/p*
7176: $ cvs status | less
1.35 wiz 7177: $ cvs commit
1.34 wiz 7178: $ cd ..
7179: $ vi Makefile # add SUBDIRS+=pkgname line
1.35 wiz 7180: $ cvs commit Makefile
1.66 asau 7181: $ cd pkgname
1.73 jnemeth 7182: $ make CTYPE=Added commit-changes-entry
1.1 dsieger 7183:
7184: The commit message of the initial import should include part of the DESCR file,
7185: so people reading the mailing lists know what the package is/does.
7186:
1.34 wiz 7187: Also mention the new package in pkgsrc/doc/CHANGES-20xx.
7188:
7189: Previously, "cvs import" was suggested, but it was much easier to get wrong
7190: than "cvs add".
1.1 dsieger 7191:
1.6 rillig 7192: 21.5. Updating a package to a newer version
1.1 dsieger 7193:
7194: Please always put a concise, appropriate and relevant summary of the changes
7195: between old and new versions into the commit log when updating a package. There
7196: are various reasons for this:
7197:
7198: * A URL is volatile, and can change over time. It may go away completely or
7199: its information may be overwritten by newer information.
7200:
7201: * Having the change information between old and new versions in our CVS
7202: repository is very useful for people who use either cvs or anoncvs.
7203:
7204: * Having the change information between old and new versions in our CVS
7205: repository is very useful for people who read the pkgsrc-changes mailing
7206: list, so that they can make tactical decisions about when to upgrade the
7207: package.
7208:
7209: Please also recognize that, just because a new version of a package has been
7210: released, it should not automatically be upgraded in the CVS repository. We
7211: prefer to be conservative in the packages that are included in pkgsrc -
7212: development or beta packages are not really the best thing for most places in
7213: which pkgsrc is used. Please use your judgement about what should go into
7214: pkgsrc, and bear in mind that stability is to be preferred above new and
7215: possibly untested features.
7216:
1.21 snj 7217: 21.6. Renaming a package in pkgsrc
7218:
7219: Renaming packages is not recommended.
7220:
7221: When renaming packages, be sure to fix any references to old name in other
7222: Makefiles, options, buildlink files, etc.
7223:
7224: Also When renaming a package, please define SUPERSEDES to the package name and
7225: dewey version pattern(s) of the previous package name. This may be repeated for
7226: multiple renames. The new package would be an exact replacement.
7227:
7228: Note that "successor" in the CHANGES-YYYY file doesn't necessarily mean that it
7229: supersedes, as that successor may not be an exact replacement but is a
7230: suggestion for the replaced functionality.
7231:
7232: 21.7. Moving a package in pkgsrc
7233:
7234: It is preferred that packages are not renamed or moved, but if needed please
7235: follow these steps.
1.1 dsieger 7236:
7237: 1. Make a copy of the directory somewhere else.
7238:
7239: 2. Remove all CVS dirs.
7240:
7241: Alternatively to the first two steps you can also do:
7242:
7243: % cvs -d user@cvs.NetBSD.org:/cvsroot export -D today pkgsrc/category/package
7244:
7245: and use that for further work.
7246:
1.25 wiz 7247: 3. Fix CATEGORIES and any DEPENDS paths that just did "../package" instead of
1.1 dsieger 7248: "../../category/package".
7249:
1.21 snj 7250: 4. In the modified package's Makefile, consider setting PREV_PKGPATH to the
7251: previous category/package pathname. The PREV_PKGPATH can be used by tools
7252: for doing an update using pkgsrc building; for example, it can search the
7253: pkg_summary(5) database for PREV_PKGPATH (if no SUPERSEDES) and then use
7254: the corresponding new PKGPATH for that moved package. Note that it may have
7255: multiple matches, so the tool should also check on the PKGBASE too. The
7256: PREV_PKGPATH probably has no value unless SUPERSEDES is not set, i.e.
7257: PKGBASE stays the same.
7258:
7259: 5. cvs import the modified package in the new place.
1.1 dsieger 7260:
1.21 snj 7261: 6. Check if any package depends on it:
1.1 dsieger 7262:
7263: % cd /usr/pkgsrc
7264: % grep /package */*/Makefile* */*/buildlink*
7265:
1.21 snj 7266: 7. Fix paths in packages from step 5 to point to new location.
1.1 dsieger 7267:
1.21 snj 7268: 8. cvs rm (-f) the package at the old location.
1.1 dsieger 7269:
1.21 snj 7270: 9. Remove from oldcategory/Makefile.
1.1 dsieger 7271:
1.21 snj 7272: 10. Add to newcategory/Makefile.
1.1 dsieger 7273:
1.21 snj 7274: 11. Commit the changed and removed files:
1.1 dsieger 7275:
7276: % cvs commit oldcategory/package oldcategory/Makefile newcategory/Makefile
7277:
7278: (and any packages from step 5, of course).
7279:
1.6 rillig 7280: Chapter 22. Frequently Asked Questions
1.1 dsieger 7281:
7282: This section contains the answers to questions that may arise when you are
7283: writing a package. If you don't find your question answered here, first have a
7284: look in the other chapters, and if you still don't have the answer, ask on the
7285: pkgsrc-users mailing list.
7286:
1.6 rillig 7287: 22.1. What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?
7288: 22.2. What is the difference between MAKE, GMAKE and MAKE_PROGRAM?
7289: 22.3. What is the difference between CC, PKG_CC and PKGSRC_COMPILER?
7290: 22.4. What is the difference between BUILDLINK_LDFLAGS, BUILDLINK_LDADD and
1.1 dsieger 7291: BUILDLINK_LIBS?
1.6 rillig 7292: 22.5. Why does make show-var VARNAME=BUILDLINK_PREFIX.foo say it's empty?
7293: 22.6. What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I don't understand
1.1 dsieger 7294: the := inside it.
1.6 rillig 7295: 22.7. Which mailing lists are there for package developers?
7296: 22.8. Where is the pkgsrc documentation?
7297: 22.9. I have a little time to kill. What shall I do?
1.1 dsieger 7298:
1.6 rillig 7299: 22.1. What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?
1.1 dsieger 7300:
7301: MAKEFLAGS are the flags passed to the pkgsrc-internal invocations of make
7302: (1), while MAKE_FLAGS are the flags that are passed to the MAKE_PROGRAM
7303: when building the package. [FIXME: What is .MAKEFLAGS for?]
7304:
1.6 rillig 7305: 22.2. What is the difference between MAKE, GMAKE and MAKE_PROGRAM?
1.1 dsieger 7306:
7307: MAKE is the path to the make(1) program that is used in the pkgsrc
7308: infrastructure. GMAKE is the path to GNU Make, but you need to say
7309: USE_TOOLS+=gmake to use that. MAKE_PROGRAM is the path to the Make
7310: program that is used for building the package.
7311:
1.6 rillig 7312: 22.3. What is the difference between CC, PKG_CC and PKGSRC_COMPILER?
1.1 dsieger 7313:
7314: CC is the path to the real C compiler, which can be configured by the
7315: pkgsrc user. PKG_CC is the path to the compiler wrapper. PKGSRC_COMPILER
7316: is not a path to a compiler, but the type of compiler that should be
7317: used. See mk/compiler.mk for more information about the latter variable.
7318:
1.6 rillig 7319: 22.4. What is the difference between BUILDLINK_LDFLAGS, BUILDLINK_LDADD and
1.1 dsieger 7320: BUILDLINK_LIBS?
7321:
7322: [FIXME]
7323:
1.6 rillig 7324: 22.5. Why does make show-var VARNAME=BUILDLINK_PREFIX.foo say it's empty?
1.1 dsieger 7325:
1.25 wiz 7326: For optimization reasons, some variables are only available in the "
7327: wrapper" phase and later. To "simulate" the wrapper phase, append
1.1 dsieger 7328: PKG_PHASE=wrapper to the above command.
7329:
1.6 rillig 7330: 22.6. What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I don't understand
1.1 dsieger 7331: the := inside it.
7332:
1.108 rillig 7333: The := is not really an assignment operator, although it looks like it.
7334: Instead, it is a degenerate form of ${LIST:old_string=new_string}, which
7335: is documented in the make(1) man page and which is commonly used in the
7336: form ${SRCS:.c=.o}. In the case of MASTER_SITE_*, old_string is the empty
7337: string and new_string is package/. That's where the : and the = fall
7338: together.
1.1 dsieger 7339:
1.6 rillig 7340: 22.7. Which mailing lists are there for package developers?
1.1 dsieger 7341:
7342: tech-pkg
7343:
7344: This is a list for technical discussions related to pkgsrc
7345: development, e.g. soliciting feedback for changes to pkgsrc
7346: infrastructure, proposed new features, questions related to porting
7347: pkgsrc to a new platform, advice for maintaining a package, patches
7348: that affect many packages, help requests moved from pkgsrc-users when
7349: an infrastructure bug is found, etc.
7350:
7351: pkgsrc-bugs
7352:
7353: All bug reports in category "pkg" sent with send-pr(1) appear here.
7354: Please do not report your bugs here directly; use one of the other
7355: mailing lists.
7356:
1.6 rillig 7357: 22.8. Where is the pkgsrc documentation?
1.1 dsieger 7358:
7359: There are many places where you can find documentation about pkgsrc:
7360:
7361: * The pkgsrc guide (this document) is a collection of chapters that
7362: explain large parts of pkgsrc, but some chapters tend to be outdated.
7363: Which ones they are is hard to say.
7364:
7365: * On the mailing list archives (see http://mail-index.NetBSD.org/), you
7366: can find discussions about certain features, announcements of new
7367: parts of the pkgsrc infrastructure and sometimes even announcements
7368: that a certain feature has been marked as obsolete. The benefit here
7369: is that each message has a date appended to it.
7370:
7371: * Many of the files in the mk/ directory start with a comment that
7372: describes the purpose of the file and how it can be used by the
7373: pkgsrc user and package authors. An easy way to find this
7374: documentation is to run bmake help.
7375:
7376: * The CVS log messages are a rich source of information, but they tend
7377: to be highly abbreviated, especially for actions that occur often.
7378: Some contain a detailed description of what has changed, but they are
7379: geared towards the other pkgsrc developers, not towards an average
7380: pkgsrc user. They also only document changes, so if you don't know
7381: what has been before, these messages may not be worth too much to
7382: you.
7383:
7384: * Some parts of pkgsrc are only "implicitly documented", that is the
7385: documentation exists only in the mind of the developer who wrote the
7386: code. To get this information, use the cvs annotate command to see
7387: who has written it and ask on the tech-pkg mailing list, so that
7388: others can find your questions later (see above). To be sure that the
7389: developer in charge reads the mail, you may CC him or her.
7390:
1.6 rillig 7391: 22.9. I have a little time to kill. What shall I do?
1.1 dsieger 7392:
7393: This is not really an FAQ yet, but here's the answer anyway.
7394:
7395: * Run pkg_chk -N (from the pkgtools/pkg_chk package). It will tell you
7396: about newer versions of installed packages that are available, but
7397: not yet updated in pkgsrc.
7398:
7399: * Browse pkgsrc/doc/TODO ? it contains a list of suggested new packages
7400: and a list of cleanups and enhancements for pkgsrc that would be nice
7401: to have.
7402:
1.71 wiz 7403: * Review packages for which review was requested on the tech-pkg
7404: mailing list.
1.1 dsieger 7405:
1.6 rillig 7406: Chapter 23. GNOME packaging and porting
1.1 dsieger 7407:
7408: Table of Contents
7409:
1.6 rillig 7410: 23.1. Meta packages
7411: 23.2. Packaging a GNOME application
7412: 23.3. Updating GNOME to a newer version
7413: 23.4. Patching guidelines
1.1 dsieger 7414:
7415: Quoting GNOME's web site:
7416:
7417: The GNOME project provides two things: The GNOME desktop environment, an
7418: intuitive and attractive desktop for users, and the GNOME development
7419: platform, an extensive framework for building applications that integrate
7420: into the rest of the desktop.
7421:
7422: pkgsrc provides a seamless way to automatically build and install a complete
7423: GNOME environment under many different platforms. We can say with confidence
7424: that pkgsrc is one of the most advanced build and packaging systems for GNOME
7425: due to its included technologies buildlink3, the wrappers and tools framework
7426: and automatic configuration file management. Lots of efforts are put into
7427: achieving a completely clean deinstallation of installed software components.
7428:
7429: Given that pkgsrc is NetBSD's official packaging system, the above also means
7430: that great efforts are put into making GNOME work under this operating system.
7431: Recently, DragonFly BSD also adopted pkgsrc as its preferred packaging system,
7432: contributing lots of portability fixes to make GNOME build and install under
7433: it.
7434:
7435: This chapter is aimed at pkgsrc developers and other people interested in
7436: helping our GNOME porting and packaging efforts. It provides instructions on
7437: how to manage the existing packages and some important information regarding
7438: their internals.
7439:
7440: We need your help!
7441:
7442: Should you have some spare cycles to devote to NetBSD, pkgsrc and GNOME and are
7443: willing to learn new exciting stuff, please jump straight to the pending work
7444: list! There is still a long way to go to get a fully-functional GNOME desktop
7445: under NetBSD and we need your help to achieve it!
7446:
1.6 rillig 7447: 23.1. Meta packages
1.1 dsieger 7448:
7449: pkgsrc includes three GNOME-related meta packages:
7450:
7451: * meta-pkgs/gnome-base: Provides the core GNOME desktop environment. It only
7452: includes the necessary bits to get it to boot correctly, although it may
7453: lack important functionality for daily operation. The idea behind this
7454: package is to let end users build their own configurations on top of this
7455: one, first installing this meta package to achieve a functional setup and
7456: then adding individual applications.
7457:
7458: * meta-pkgs/gnome: Provides a complete installation of the GNOME platform and
7459: desktop as defined by the GNOME project; this is based on the components
7460: distributed in the platform/x.y/x.y.z/sources and desktop/x.y/x.y.z/sources
7461: directories of the official FTP server. Developer-only tools found in those
7462: directories are not installed unless required by some other component to
7463: work properly. Similarly, packages from the bindings set (bindings/x.y/
7464: x.y.z/sources) are not pulled in unless required as a dependency for an
7465: end-user component. This package "extends" meta-pkgs/gnome-base.
7466:
7467: * meta-pkgs/gnome-devel: Installs all the tools required to build a GNOME
7468: component when fetched from the CVS repository. These are required to let
7469: the autogen.sh scripts work appropriately.
7470:
7471: In all these packages, the DEPENDS lines are sorted in a way that eases
7472: updates: a package may depend on other packages listed before it but not on any
1.25 wiz 7473: listed after it. It is very important to keep this order to ease updates so...
1.1 dsieger 7474: do not change it to alphabetical sorting!
7475:
1.6 rillig 7476: 23.2. Packaging a GNOME application
1.1 dsieger 7477:
7478: Almost all GNOME applications are written in C and use a common set of tools as
7479: their build system. Things get different with the new bindings to other
7480: languages (such as Python), but the following will give you a general idea on
7481: the minimum required tools:
7482:
7483: * Almost all GNOME applications use the GNU Autotools as their build system.
7484: As a general rule you will need to tell this to your package:
7485:
7486: GNU_CONFIGURE=yes
7487: USE_LIBTOOL=yes
7488: USE_TOOLS+=gmake
7489:
7490: * If the package uses pkg-config to detect dependencies, add this tool to the
7491: list of required utilities:
7492:
7493: USE_TOOLS+=pkg-config
7494:
7495: Also use pkgtools/verifypc at the end of the build process to ensure that
7496: you did not miss to specify any dependency in your package and that the
7497: version requirements are all correct.
7498:
7499: * If the package uses intltool, be sure to add intltool to the USE_TOOLS to
7500: handle dependencies and to force the package to use the latest available
7501: version.
7502:
7503: * If the package uses gtk-doc (a documentation generation utility), do not
7504: add a dependency on it. The tool is rather big and the distfile should come
7505: with pregenerated documentation anyway; if it does not, it is a bug that
7506: you ought to report. For such packages you should disable gtk-doc (unless
7507: it is the default):
7508:
7509: CONFIGURE_ARGS+=--disable-gtk-doc
7510:
7511: The default location of installed HTML files (share/gtk-doc/<package-name>)
7512: is correct and should not be changed unless the package insists on
7513: installing them somewhere else. Otherwise programs as devhelp will not be
7514: able to open them. You can do that with an entry similar to:
7515:
7516: CONFIGURE_ARGS+=--with-html-dir=${PREFIX}/share/gtk-doc/...
7517:
7518: GNOME uses multiple shared directories and files under the installation prefix
7519: to maintain databases. In this context, shared means that those exact same
7520: directories and files are used among several different packages, leading to
7521: conflicts in the PLIST. pkgsrc currently includes functionality to handle the
7522: most common cases, so you have to forget about using @unexec ${RMDIR} lines in
7523: your file lists and omitting shared files from them. If you find yourself doing
7524: those, your package is most likely incorrect.
7525:
7526: The following table lists the common situations that result in using shared
7527: directories or files. For each of them, the appropriate solution is given.
1.25 wiz 7528: After applying the solution be sure to regenerate the package's file list with
1.1 dsieger 7529: make print-PLIST and ensure it is correct.
7530:
1.6 rillig 7531: Table 23.1. PLIST handling for GNOME packages
1.1 dsieger 7532:
7533: +-----------------------------------------------------------------------------+
7534: | If the package... | Then... |
7535: |-------------------------------------------+---------------------------------|
1.6 rillig 7536: | |See Section 19.6.10, "Packages |
1.18 mishka 7537: |Installs OMF files under share/omf. |installing scrollkeeper/rarian |
7538: | |data files". |
1.1 dsieger 7539: |-------------------------------------------+---------------------------------|
1.6 rillig 7540: |Installs icons under the share/icons/ |See Section 19.6.19, "Packages |
1.1 dsieger 7541: |hicolor hierarchy or updates share/icons/ |installing hicolor theme icons". |
7542: |hicolor/icon-theme.cache. | |
7543: |-------------------------------------------+---------------------------------|
1.6 rillig 7544: | |See Section 19.6.14, "Packages |
1.1 dsieger 7545: |Installs files under share/mime/packages. |installing extensions to the MIME|
7546: | |database". |
7547: |-------------------------------------------+---------------------------------|
1.6 rillig 7548: |Installs .desktop files under share/ |See Section 19.6.20, "Packages |
1.1 dsieger 7549: |applications and these include MIME |installing desktop files". |
7550: |information. | |
7551: +-----------------------------------------------------------------------------+
7552:
7553:
1.6 rillig 7554: 23.3. Updating GNOME to a newer version
1.1 dsieger 7555:
7556: When seeing GNOME as a whole, there are two kinds of updates:
7557:
7558: Major update
7559:
7560: Given that there is still a very long way for GNOME 3 (if it ever appears),
7561: we consider a major update one that goes from a 2.X version to a 2.Y one,
7562: where Y is even and greater than X. These are hard to achieve because they
7563: introduce lots of changes in the components' code and almost all GNOME
7564: distfiles are updated to newer versions. Some of them can even break API
7565: and ABI compatibility with the previous major version series. As a result,
7566: the update needs to be done all at once to minimize breakage.
7567:
7568: A major update typically consists of around 80 package updates and the
7569: addition of some new ones.
7570:
7571: Minor update
7572:
7573: We consider a minor update one that goes from a 2.A.X version to a 2.A.Y
7574: one where Y is greater than X. These are easy to achieve because they do
7575: not update all GNOME components, can be done in an incremental way and do
7576: not break API nor ABI compatibility.
7577:
7578: A minor update typically consists of around 50 package updates, although
7579: the numbers here may vary a lot.
7580:
7581: In order to update the GNOME components in pkgsrc to a new stable release
7582: (either major or minor), the following steps should be followed:
7583:
7584: 1. Get a list of all the tarballs that form the new release by using the
1.19 snj 7585: following commands. These will leave the full list of the components'
1.1 dsieger 7586: distfiles into the list.txt file:
7587:
7588: % echo ls "*.tar.bz2" | \
7589: ftp -V ftp://ftp.gnome.org/pub/gnome/platform/x.y/x.y.z/sources/ | \
7590: awk '{ print $9 }' >list.txt
7591: % echo ls "*.tar.bz2" | \
7592: ftp -V ftp://ftp.gnome.org/pub/gnome/desktop/x.y/x.y.z/sources/ | \
7593: awk '{ print $9 }' >>list.txt
7594:
7595: 2. Open each meta package's Makefile and bump their version to the release you
7596: are updating them to. The three meta packages should be always consistent
7597: with versioning. Obviously remove any PKGREVISIONs that might be in them.
7598:
7599: 3. For each meta package, update all its DEPENDS lines to match the latest
7600: versions as shown by the above commands. Do not list any newer version
7601: (even if found in the FTP) because the meta packages are supposed to list
7602: the exact versions that form a specific GNOME release. Exceptions are
7603: permitted here if a newer version solves a serious issue in the overall
7604: desktop experience; these typically come in the form of a revision bump in
7605: pkgsrc, not in newer versions from the developers.
7606:
7607: Packages not listed in the list.txt file should be updated to the latest
7608: version available (if found in pkgsrc). This is the case, for example, of
7609: the dependencies on the GNU Autotools in the meta-pkgs/gnome-devel meta
7610: package.
7611:
7612: 4. Generate a patch from the modified meta packages and extract the list of
7613: "new" lines. This will provide you an outline on what packages need to be
7614: updated in pkgsrc and in what order:
7615:
7616: % cvs diff -u gnome-devel gnome-base gnome | grep '^+D' >todo.txt
7617:
7618: 5. For major desktop updates it is recommended to zap all your installed
7619: packages and start over from scratch at this point.
7620:
7621: 6. Now comes the longest step by far: iterate over the contents of todo.txt
7622: and update the packages listed in it in order. For major desktop updates
7623: none of these should be committed until the entire set is completed because
7624: there are chances of breaking not-yet-updated packages.
7625:
7626: 7. Once the packages are up to date and working, commit them to the tree one
7627: by one with appropriate log messages. At the end, commit the three meta
7628: package updates and all the corresponding changes to the doc/CHANGES-<YEAR>
7629: and pkgsrc/doc/TODO files.
7630:
1.6 rillig 7631: 23.4. Patching guidelines
1.1 dsieger 7632:
7633: GNOME is a very big component in pkgsrc which approaches 100 packages. Please,
7634: it is very important that you always, always, always feed back any portability
7635: fixes you do to a GNOME package to the mainstream developers (see
1.6 rillig 7636: Section 11.3.5, "Feedback to the author"). This is the only way to get their
1.1 dsieger 7637: attention on portability issues and to ensure that future versions can be built
7638: out-of-the box on NetBSD. The less custom patches in pkgsrc, the easier further
7639: updates are. Those developers in charge of issuing major GNOME updates will be
7640: grateful if you do that.
7641:
7642: The most common places to report bugs are the GNOME's Bugzilla and the
7643: freedesktop.org's Bugzilla. Not all components use these to track bugs, but
7644: most of them do. Do not be short on your reports: always provide detailed
7645: explanations of the current failure, how it can be improved to achieve maximum
7646: portability and, if at all possible, provide a patch against CVS head. The more
7647: verbose you are, the higher chances of your patch being accepted.
7648:
7649: Also, please avoid using preprocessor magic to fix portability issues. While
7650: the FreeBSD GNOME people are doing a great job in porting GNOME to their
7651: operating system, the official GNOME sources are now plagued by conditionals
7652: that check for __FreeBSD__ and similar macros. This hurts portability. Please
1.6 rillig 7653: see our patching guidelines (Section 11.3.4, "Patching guidelines") for more
1.1 dsieger 7654: details.
7655:
7656: Part III. The pkgsrc infrastructure internals
7657:
7658: This part of the guide deals with everything from the infrastructure that is
7659: behind the interfaces described in the developer's guide. A casual package
7660: maintainer should not need anything from this part.
7661:
7662: Table of Contents
7663:
1.6 rillig 7664: 24. Design of the pkgsrc infrastructure
1.1 dsieger 7665:
1.6 rillig 7666: 24.1. The meaning of variable definitions
7667: 24.2. Avoiding problems before they arise
7668: 24.3. Variable evaluation
1.1 dsieger 7669:
1.6 rillig 7670: 24.3.1. At load time
7671: 24.3.2. At runtime
1.1 dsieger 7672:
1.6 rillig 7673: 24.4. How can variables be specified?
7674: 24.5. Designing interfaces for Makefile fragments
1.1 dsieger 7675:
1.6 rillig 7676: 24.5.1. Procedures with parameters
7677: 24.5.2. Actions taken on behalf of parameters
1.1 dsieger 7678:
1.6 rillig 7679: 24.6. The order in which files are loaded
1.1 dsieger 7680:
1.6 rillig 7681: 24.6.1. The order in bsd.prefs.mk
7682: 24.6.2. The order in bsd.pkg.mk
1.1 dsieger 7683:
1.6 rillig 7684: 25. Regression tests
1.1 dsieger 7685:
1.108 rillig 7686: 25.1. Running the regression tests
7687: 25.2. Adding a new regression test
1.1 dsieger 7688:
1.108 rillig 7689: 25.2.1. Overridable functions
7690: 25.2.2. Helper functions
1.1 dsieger 7691:
1.6 rillig 7692: 26. Porting pkgsrc
1.1 dsieger 7693:
1.6 rillig 7694: 26.1. Porting pkgsrc to a new operating system
1.1 dsieger 7695:
1.6 rillig 7696: Chapter 24. Design of the pkgsrc infrastructure
1.1 dsieger 7697:
7698: Table of Contents
7699:
1.6 rillig 7700: 24.1. The meaning of variable definitions
7701: 24.2. Avoiding problems before they arise
7702: 24.3. Variable evaluation
1.1 dsieger 7703:
1.6 rillig 7704: 24.3.1. At load time
7705: 24.3.2. At runtime
1.1 dsieger 7706:
1.6 rillig 7707: 24.4. How can variables be specified?
7708: 24.5. Designing interfaces for Makefile fragments
1.1 dsieger 7709:
1.6 rillig 7710: 24.5.1. Procedures with parameters
7711: 24.5.2. Actions taken on behalf of parameters
1.1 dsieger 7712:
1.6 rillig 7713: 24.6. The order in which files are loaded
1.1 dsieger 7714:
1.6 rillig 7715: 24.6.1. The order in bsd.prefs.mk
7716: 24.6.2. The order in bsd.pkg.mk
1.1 dsieger 7717:
7718: The pkgsrc infrastructure consists of many small Makefile fragments. Each such
7719: fragment needs a properly specified interface. This chapter explains how such
7720: an interface looks like.
7721:
1.6 rillig 7722: 24.1. The meaning of variable definitions
1.1 dsieger 7723:
7724: Whenever a variable is defined in the pkgsrc infrastructure, the location and
7725: the way of definition provide much information about the intended use of that
7726: variable. Additionally, more documentation may be found in a header comment or
7727: in this pkgsrc guide.
7728:
7729: A special file is mk/defaults/mk.conf, which lists all variables that are
7730: intended to be user-defined. They are either defined using the ?= operator or
7731: they are left undefined because defining them to anything would effectively
7732: mean "yes". All these variables may be overridden by the pkgsrc user in the
7733: MAKECONF file.
7734:
7735: Outside this file, the following conventions apply: Variables that are defined
7736: using the ?= operator may be overridden by a package.
7737:
7738: Variables that are defined using the = operator may be used read-only at
7739: run-time.
7740:
7741: Variables whose name starts with an underscore must not be accessed outside the
7742: pkgsrc infrastructure at all. They may change without further notice.
7743:
7744: Note
7745:
7746: These conventions are currently not applied consistently to the complete pkgsrc
7747: infrastructure.
7748:
1.6 rillig 7749: 24.2. Avoiding problems before they arise
1.1 dsieger 7750:
7751: All variables that contain lists of things should default to being empty. Two
7752: examples that do not follow this rule are USE_LANGUAGES and DISTFILES. These
7753: variables cannot simply be modified using the += operator in package Makefiles
7754: (or other files included by them), since there is no guarantee whether the
7755: variable is already set or not, and what its value is. In the case of
7756: DISTFILES, the packages "know" the default value and just define it as in the
7757: following example.
7758:
7759: DISTFILES= ${DISTNAME}${EXTRACT_SUFX} additional-files.tar.gz
7760:
7761: Because of the selection of this default value, the same value appears in many
7762: package Makefiles. Similarly for USE_LANGUAGES, but in this case the default
7763: value ("c") is so short that it doesn't stand out. Nevertheless it is mentioned
7764: in many files.
7765:
1.6 rillig 7766: 24.3. Variable evaluation
1.1 dsieger 7767:
1.6 rillig 7768: 24.3.1. At load time
1.1 dsieger 7769:
7770: Variable evaluation takes place either at load time or at runtime, depending on
7771: the context in which they occur. The contexts where variables are evaluated at
7772: load time are:
7773:
7774: * The right hand side of the := and != operators,
7775:
7776: * Make directives like .if or .for,
7777:
7778: * Dependency lines.
7779:
7780: A special exception are references to the iteration variables of .for loops,
7781: which are expanded inline, no matter in which context they appear.
7782:
7783: As the values of variables may change during load time, care must be taken not
7784: to evaluate them by accident. Typical examples for variables that should not be
7785: evaluated at load time are DEPENDS and CONFIGURE_ARGS. To make the effect more
7786: clear, here is an example:
7787:
7788: CONFIGURE_ARGS= # none
7789: CFLAGS= -O
7790: CONFIGURE_ARGS+= CFLAGS=${CFLAGS:Q}
7791:
7792: CONFIGURE_ARGS:= ${CONFIGURE_ARGS}
7793:
7794: CFLAGS+= -Wall
7795:
7796: This code shows how the use of the := operator can quickly lead to unexpected
7797: results. The first paragraph is fairly common code. The second paragraph
7798: evaluates the CONFIGURE_ARGS variable, which results in CFLAGS=-O. In the third
7799: paragraph, the -Wall is appended to the CFLAGS, but this addition will not
7800: appear in CONFIGURE_ARGS. In actual code, the three paragraphs from above
7801: typically occur in completely unrelated files.
7802:
1.6 rillig 7803: 24.3.2. At runtime
1.1 dsieger 7804:
7805: After all the files have been loaded, the values of the variables cannot be
7806: changed anymore. Variables that are used in the shell commands are expanded at
7807: this point.
7808:
1.6 rillig 7809: 24.4. How can variables be specified?
1.1 dsieger 7810:
7811: There are many ways in which the definition and use of a variable can be
7812: restricted in order to detect bugs and violations of the (mostly unwritten)
1.108 rillig 7813: policies. A package can be checked with pkglint -Wall to see whether it meets
7814: these rules.
1.1 dsieger 7815:
1.6 rillig 7816: 24.5. Designing interfaces for Makefile fragments
1.1 dsieger 7817:
7818: Most of the .mk files fall into one of the following classes. Cases where a
7819: file falls into more than one class should be avoided as it often leads to
7820: subtle bugs.
7821:
1.6 rillig 7822: 24.5.1. Procedures with parameters
1.1 dsieger 7823:
7824: In a traditional imperative programming language some of the .mk files could be
1.23 jakllsch 7825: described as procedures. They take some input parameters and?after
7826: inclusion?provide a result in output parameters. Since all variables in
7827: Makefiles have global scope care must be taken not to use parameter names that
7828: have already another meaning. For example, PKGNAME is a bad choice for a
7829: parameter name.
1.1 dsieger 7830:
7831: Procedures are completely evaluated at preprocessing time. That is, when
7832: calling a procedure all input parameters must be completely resolvable. For
7833: example, CONFIGURE_ARGS should never be an input parameter since it is very
7834: likely that further text will be added after calling the procedure, which would
7835: effectively apply the procedure to only a part of the variable. Also,
1.108 rillig 7836: references to other variables will be modified after calling the procedure.
1.1 dsieger 7837:
7838: A procedure can declare its output parameters either as suitable for use in
7839: preprocessing directives or as only available at runtime. The latter
7840: alternative is for variables that contain references to other runtime
7841: variables.
7842:
7843: Procedures shall be written such that it is possible to call the procedure more
7844: than once. That is, the file must not contain multiple-inclusion guards.
7845:
7846: Examples for procedures are mk/bsd.options.mk and mk/buildlink3/bsd.builtin.mk.
7847: To express that the parameters are evaluated at load time, they should be
7848: assigned using the := operator, which should be used only for this purpose.
7849:
1.6 rillig 7850: 24.5.2. Actions taken on behalf of parameters
1.1 dsieger 7851:
7852: Action files take some input parameters and may define runtime variables. They
7853: shall not define loadtime variables. There are action files that are included
7854: implicitly by the pkgsrc infrastructure, while other must be included
7855: explicitly.
7856:
7857: An example for action files is mk/subst.mk.
7858:
1.6 rillig 7859: 24.6. The order in which files are loaded
1.1 dsieger 7860:
7861: Package Makefiles usually consist of a set of variable definitions, and include
7862: the file ../../mk/bsd.pkg.mk in the very last line. Before that, they may also
7863: include various other *.mk files if they need to query the availability of
7864: certain features like the type of compiler or the X11 implementation. Due to
7865: the heavy use of preprocessor directives like .if and .for, the order in which
7866: the files are loaded matters.
7867:
7868: This section describes at which point the various files are loaded and gives
7869: reasons for that order.
7870:
1.6 rillig 7871: 24.6.1. The order in bsd.prefs.mk
1.1 dsieger 7872:
7873: The very first action in bsd.prefs.mk is to define some essential variables
7874: like OPSYS, OS_VERSION and MACHINE_ARCH.
7875:
1.4 rillig 7876: Then, the user settings are loaded from the file specified in MAKECONF, which
7877: is usually mk.conf. After that, those variables that have not been overridden
7878: by the user are loaded from mk/defaults/mk.conf.
1.1 dsieger 7879:
7880: After the user settings, the system settings and platform settings are loaded,
7881: which may override the user settings.
7882:
7883: Then, the tool definitions are loaded. The tool wrappers are not yet in effect.
7884: This only happens when building a package, so the proper variables must be used
7885: instead of the direct tool names.
7886:
7887: As the last steps, some essential variables from the wrapper and the package
7888: system flavor are loaded, as well as the variables that have been cached in
7889: earlier phases of a package build.
7890:
1.6 rillig 7891: 24.6.2. The order in bsd.pkg.mk
1.1 dsieger 7892:
7893: First, bsd.prefs.mk is loaded.
7894:
7895: Then, the various *-vars.mk files are loaded, which fill default values for
7896: those variables that have not been defined by the package. These variables may
7897: later be used even in unrelated files.
7898:
7899: Then, the file bsd.pkg.error.mk provides the target error-check that is added
7900: as a special dependency to all other targets that use DELAYED_ERROR_MSG or
7901: DELAYED_WARNING_MSG.
7902:
7903: Then, the package-specific hacks from hacks.mk are included.
7904:
7905: Then, various other files follow. Most of them don't have any dependencies on
7906: what they need to have included before or after them, though some do.
7907:
7908: The code to check PKG_FAIL_REASON and PKG_SKIP_REASON is then executed, which
7909: restricts the use of these variables to all the files that have been included
7910: before. Appearances in later files will be silently ignored.
7911:
7912: Then, the files for the main targets are included, in the order of later
7913: execution, though the actual order should not matter.
7914:
7915: At last, some more files are included that don't set any interesting variables
7916: but rather just define make targets to be executed.
7917:
1.6 rillig 7918: Chapter 25. Regression tests
1.1 dsieger 7919:
7920: Table of Contents
7921:
1.108 rillig 7922: 25.1. Running the regression tests
7923: 25.2. Adding a new regression test
1.1 dsieger 7924:
1.108 rillig 7925: 25.2.1. Overridable functions
7926: 25.2.2. Helper functions
1.1 dsieger 7927:
7928: The pkgsrc infrastructure consists of a large codebase, and there are many
7929: corners where every little bit of a file is well thought out, making pkgsrc
7930: likely to fail as soon as anything is changed near those parts. To prevent most
7931: changes from breaking anything, a suite of regression tests should go along
7932: with every important part of the pkgsrc infrastructure. This chapter describes
7933: how regression tests work in pkgsrc and how you can add new tests.
7934:
1.108 rillig 7935: 25.1. Running the regression tests
1.1 dsieger 7936:
1.25 wiz 7937: You first need to install the pkgtools/pkg_regress package, which provides the
1.1 dsieger 7938: pkg_regress command. Then you can simply run that command, which will run all
7939: tests in the regress category.
7940:
1.108 rillig 7941: 25.2. Adding a new regression test
1.1 dsieger 7942:
7943: Every directory in the regress category that contains a file called spec is
7944: considered a regression test. This file is a shell program that is included by
7945: the pkg_regress command. The following functions can be overridden to suit your
7946: needs.
7947:
1.108 rillig 7948: 25.2.1. Overridable functions
1.1 dsieger 7949:
1.108 rillig 7950: These functions do not take any parameters. Although they are called in "set -e
7951: " mode, they don't stop at the first failing command. See this StackOverflow
7952: question for details.
1.1 dsieger 7953:
1.108 rillig 7954: do_setup
1.1 dsieger 7955:
7956: This function prepares the environment for the test. By default it does
7957: nothing.
7958:
1.108 rillig 7959: do_test
1.1 dsieger 7960:
7961: This function runs the actual test. By default, it calls TEST_MAKE with the
7962: arguments MAKEARGS_TEST and writes its output including error messages into
7963: the file TEST_OUTFILE.
7964:
1.108 rillig 7965: When defining this function, make sure that all output that needs to be
7966: checked is written to the correct output file. Example:
7967:
7968: do_test() {
7969: echo "Example output"
7970: } 1>$TEST_OUTFILE 2>&1
7971:
7972: check_result
1.1 dsieger 7973:
7974: This function is run after the test and is typically used to compare the
7975: actual output from the one that is expected. It can make use of the various
1.108 rillig 7976: helper functions from the next section. Example:
7977:
7978: check_result() {
7979: exit_status 0
7980: output_require "Example"
7981: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
7982: output_prohibit "no such file or directory"
7983: }
1.1 dsieger 7984:
1.108 rillig 7985: do_cleanup
1.1 dsieger 7986:
7987: This function cleans everything up after the test has been run. By default
7988: it does nothing.
7989:
1.108 rillig 7990: 25.2.2. Helper functions
1.1 dsieger 7991:
1.108 rillig 7992: exit_status expected
1.1 dsieger 7993:
1.108 rillig 7994: This function compares the exitcode of the do_test function with its first
7995: parameter. If they differ, the test will fail.
1.1 dsieger 7996:
1.108 rillig 7997: output_require regex...
1.1 dsieger 7998:
7999: This function checks for each of its parameters if the output from do_test
1.108 rillig 8000: matches the extended regular expression. If it does not, the test will
8001: fail. Example:
8002:
8003: output_require "looks fine"
8004: output_require "^[[:alpha:]+[[:space:]][[:alpha:]]{6}$"
1.1 dsieger 8005:
8006: output_prohibit(regex...)
8007:
8008: This function checks for each of its parameters if the output from do_test
8009: () does not match the extended regular expression. If any of the regular
8010: expressions matches, the test will fail.
8011:
1.6 rillig 8012: Chapter 26. Porting pkgsrc
1.1 dsieger 8013:
8014: Table of Contents
8015:
1.6 rillig 8016: 26.1. Porting pkgsrc to a new operating system
1.1 dsieger 8017:
8018: The pkgsrc system has already been ported to many operating systems, hardware
8019: architectures and compilers. This chapter explains the necessary steps to make
8020: pkgsrc even more portable.
8021:
1.6 rillig 8022: 26.1. Porting pkgsrc to a new operating system
1.1 dsieger 8023:
8024: To port pkgsrc to a new operating system (called MyOS in this example), you
8025: need to touch the following files:
8026:
8027: pkgtools/bootstrap-mk-files/files/mods/MyOS.sys.mk
8028:
8029: This file contains some basic definitions, for example the name of the C
8030: compiler.
8031:
8032: mk/bsd.prefs.mk
8033:
8034: Insert code that defines the variables OPSYS, OS_VERSION, LOWER_OS_VERSION,
8035: LOWER_VENDOR, MACHINE_ARCH, OBJECT_FMT, APPEND_ELF, and the other variables
8036: that appear in this file.
8037:
8038: mk/platform/MyOS.mk
8039:
8040: This file contains the platform-specific definitions that are used by
8041: pkgsrc. Start by copying one of the other files and edit it to your needs.
8042:
8043: mk/tools/tools.MyOS.mk
8044:
8045: This file defines the paths to all the tools that are needed by one or the
8046: other package in pkgsrc, as well as by pkgsrc itself. Find out where these
8047: tools are on your platform and add them.
8048:
8049: Now, you should be able to build some basic packages, like lang/perl5, shells/
8050: bash.
8051:
8052: Appendix A. A simple example package: bison
8053:
8054: Table of Contents
8055:
8056: A.1. files
8057:
8058: A.1.1. Makefile
8059: A.1.2. DESCR
8060: A.1.3. PLIST
8061: A.1.4. Checking a package with pkglint
8062:
8063: A.2. Steps for building, installing, packaging
8064:
8065: We checked to find a piece of software that wasn't in the packages collection,
1.25 wiz 8066: and picked GNU bison. Quite why someone would want to have bison when Berkeley
1.1 dsieger 8067: yacc is already present in the tree is beyond us, but it's useful for the
8068: purposes of this exercise.
8069:
8070: A.1. files
8071:
8072: A.1.1. Makefile
8073:
1.2 rillig 8074: # $NetBSD$
1.1 dsieger 8075: #
8076:
8077: DISTNAME= bison-1.25
8078: CATEGORIES= devel
8079: MASTER_SITES= ${MASTER_SITE_GNU}
8080:
1.30 dholland 8081: MAINTAINER= pkgsrc-users@NetBSD.org
1.1 dsieger 8082: HOMEPAGE= http://www.gnu.org/software/bison/bison.html
8083: COMMENT= GNU yacc clone
8084:
8085: GNU_CONFIGURE= yes
1.47 wiz 8086: INFO_FILES= yes
1.1 dsieger 8087:
8088: .include "../../mk/bsd.pkg.mk"
8089:
8090: A.1.2. DESCR
8091:
8092: GNU version of yacc. Can make re-entrant parsers, and numerous other
8093: improvements. Why you would want this when Berkeley yacc(1) is part
8094: of the NetBSD source tree is beyond me.
8095:
8096: A.1.3. PLIST
8097:
1.2 rillig 8098: @comment $NetBSD$
1.1 dsieger 8099: bin/bison
8100: man/man1/bison.1.gz
8101: share/bison.simple
8102: share/bison.hairy
8103:
8104: A.1.4. Checking a package with pkglint
8105:
8106: The NetBSD package system comes with pkgtools/pkglint which helps to check the
8107: contents of these files. After installation it is quite easy to use, just
8108: change to the directory of the package you wish to examine and execute pkglint:
8109:
8110: $ pkglint
8111: looks fine.
8112:
8113: Depending on the supplied command line arguments (see pkglint(1)), more checks
8114: will be performed. Use e.g. pkglint -Call -Wall for a very thorough check.
8115:
8116: A.2. Steps for building, installing, packaging
8117:
8118: Create the directory where the package lives, plus any auxiliary directories:
8119:
8120: # cd /usr/pkgsrc/lang
8121: # mkdir bison
8122: # cd bison
8123: # mkdir patches
8124:
1.6 rillig 8125: Create Makefile, DESCR and PLIST (see Chapter 11, Package components - files,
1.1 dsieger 8126: directories and contents) then continue with fetching the distfile:
8127:
8128: # make fetch
8129: >> bison-1.25.tar.gz doesn't seem to exist on this system.
8130: >> Attempting to fetch from ftp://prep.ai.mit.edu/pub/gnu//.
8131: Requesting ftp://prep.ai.mit.edu/pub/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
8132: ftp: Error retrieving file: 500 Internal error
8133:
8134: >> Attempting to fetch from ftp://wuarchive.wustl.edu/systems/gnu//.
8135: Requesting ftp://wuarchive.wustl.edu/systems/gnu//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
8136: ftp: Error retrieving file: 500 Internal error
8137:
8138: >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//.
8139: Requesting ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//bison-1.25.tar.gz (via ftp://orpheus.amdahl.com:80/)
8140: Successfully retrieved file.
8141:
8142: Generate the checksum of the distfile into distinfo:
8143:
8144: # make makedistinfo
8145:
8146: Now compile:
8147:
8148: # make
8149: >> Checksum OK for bison-1.25.tar.gz.
8150: ===> Extracting for bison-1.25
8151: ===> Patching for bison-1.25
8152: ===> Ignoring empty patch directory
8153: ===> Configuring for bison-1.25
8154: creating cache ./config.cache
8155: checking for gcc... cc
8156: checking whether we are using GNU C... yes
8157: checking for a BSD compatible install... /usr/bin/install -c -o bin -g bin
8158: checking how to run the C preprocessor... cc -E
8159: checking for minix/config.h... no
8160: checking for POSIXized ISC... no
8161: checking whether cross-compiling... no
8162: checking for ANSI C header files... yes
8163: checking for string.h... yes
8164: checking for stdlib.h... yes
8165: checking for memory.h... yes
8166: checking for working const... yes
8167: checking for working alloca.h... no
8168: checking for alloca... yes
8169: checking for strerror... yes
8170: updating cache ./config.cache
8171: creating ./config.status
8172: creating Makefile
8173: ===> Building for bison-1.25
8174: 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
8175: 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
8176: 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
8177: 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
8178: 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
8179: 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
8180: 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
8181: 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
8182: 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
8183: 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
8184: 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
8185: 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
8186: 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
8187: 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
8188: 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
8189: 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
8190: 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
8191: 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
8192: 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
8193: 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
8194: 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
8195: 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
8196: ./files.c:240: warning: mktemp() possibly used unsafely, consider using mkstemp()
8197: rm -f bison.s1
8198: sed -e "/^#line/ s|bison|/usr/pkg/share/bison|" < ./bison.simple > bison.s1
8199:
8200: Everything seems OK, so install the files:
8201:
8202: # make install
8203: >> Checksum OK for bison-1.25.tar.gz.
8204: ===> Installing for bison-1.25
8205: sh ./mkinstalldirs /usr/pkg/bin /usr/pkg/share /usr/pkg/info /usr/pkg/man/man1
8206: rm -f /usr/pkg/bin/bison
8207: cd /usr/pkg/share; rm -f bison.simple bison.hairy
8208: rm -f /usr/pkg/man/man1/bison.1 /usr/pkg/info/bison.info*
8209: install -c -o bin -g bin -m 555 bison /usr/pkg/bin/bison
8210: /usr/bin/install -c -o bin -g bin -m 644 bison.s1 /usr/pkg/share/bison.simple
8211: /usr/bin/install -c -o bin -g bin -m 644 ./bison.hairy /usr/pkg/share/bison.hairy
8212: cd .; for f in bison.info*; do /usr/bin/install -c -o bin -g bin -m 644 $f /usr/pkg/info/$f; done
8213: /usr/bin/install -c -o bin -g bin -m 644 ./bison.1 /usr/pkg/man/man1/bison.1
8214: ===> Registering installation for bison-1.25
8215:
8216: You can now use bison, and also - if you decide so - remove it with pkg_delete
8217: bison. Should you decide that you want a binary package, do this now:
8218:
8219: # make package
8220: >> Checksum OK for bison-1.25.tar.gz.
8221: ===> Building package for bison-1.25
8222: Creating package bison-1.25.tgz
8223: Registering depends:.
8224: Creating gzip'd tar ball in '/u/pkgsrc/lang/bison/bison-1.25.tgz'
8225:
8226: Now that you don't need the source and object files any more, clean up:
8227:
8228: # make clean
8229: ===> Cleaning for bison-1.25
8230:
8231: Appendix B. Build logs
8232:
8233: Table of Contents
8234:
8235: B.1. Building figlet
8236: B.2. Packaging figlet
8237:
8238: B.1. Building figlet
8239:
8240: # make
8241: ===> Checking for vulnerabilities in figlet-2.2.1nb2
8242: => figlet221.tar.gz doesn't seem to exist on this system.
8243: => Attempting to fetch figlet221.tar.gz from ftp://ftp.figlet.org/pub/figlet/program/unix/.
8244: => [172219 bytes]
8245: Connected to ftp.plig.net.
8246: 220 ftp.plig.org NcFTPd Server (licensed copy) ready.
8247: 331 Guest login ok, send your complete e-mail address as password.
8248: 230-You are user #5 of 500 simultaneous users allowed.
8249: 230-
8250: 230- ___ _ _ _
8251: 230- | _| |_ ___ ___| |_|___ ___ ___ ___
8252: 230- | _| _| . |_| . | | | . |_| . | _| . |
8253: 230- |_| |_| | _|_| _|_|_|_ |_|___|_| |_ |
8254: 230- |_| |_| |___| |___|
8255: 230-
8256: 230-** Welcome to ftp.plig.org **
8257: 230-
8258: 230-Please note that all transfers from this FTP site are logged. If you
8259: 230-do not like this, please disconnect now.
8260: 230-
1.19 snj 8261: 230-This archive is available via
1.1 dsieger 8262: 230-
8263: 230-HTTP: http://ftp.plig.org/
8264: 230-FTP: ftp://ftp.plig.org/ (max 500 connections)
8265: 230-RSYNC: rsync://ftp.plig.org/ (max 30 connections)
8266: 230-
8267: 230-Please email comments, bug reports and requests for packages to be
8268: 230-mirrored to ftp-admin@plig.org.
8269: 230-
8270: 230-
8271: 230 Logged in anonymously.
8272: Remote system type is UNIX.
8273: Using binary mode to transfer files.
8274: 200 Type okay.
8275: 250 "/pub" is new cwd.
8276: 250-"/pub/figlet" is new cwd.
8277: 250-
8278: 250-Welcome to the figlet archive at ftp.figlet.org
8279: 250-
8280: 250- ftp://ftp.figlet.org/pub/figlet/
8281: 250-
8282: 250-The official FIGlet web page is:
8283: 250- http://www.figlet.org/
8284: 250-
8285: 250-If you have questions, please mailto:info@figlet.org. If you want to
8286: 250-contribute a font or something else, you can email us.
8287: 250
8288: 250 "/pub/figlet/program" is new cwd.
8289: 250 "/pub/figlet/program/unix" is new cwd.
8290: local: figlet221.tar.gz remote: figlet221.tar.gz
8291: 502 Unimplemented command.
8292: 227 Entering Passive Mode (195,40,6,41,246,104)
8293: 150 Data connection accepted from 84.128.86.72:65131; transfer starting for figlet221.tar.gz (172219 bytes).
8294: 38% |************** | 65800 64.16 KB/s 00:01 ETA
8295: 226 Transfer completed.
8296: 172219 bytes received in 00:02 (75.99 KB/s)
8297: 221 Goodbye.
8298: => Checksum OK for figlet221.tar.gz.
8299: ===> Extracting for figlet-2.2.1nb2
8300: ===> Required installed package ccache-[0-9]*: ccache-2.3nb1 found
8301: ===> Patching for figlet-2.2.1nb2
8302: ===> Applying pkgsrc patches for figlet-2.2.1nb2
8303: ===> Overriding tools for figlet-2.2.1nb2
8304: ===> Creating toolchain wrappers for figlet-2.2.1nb2
8305: ===> Configuring for figlet-2.2.1nb2
8306: ===> Building for figlet-2.2.1nb2
8307: gcc -O2 -DDEFAULTFONTDIR=\"/usr/pkg/share/figlet\" -DDEFAULTFONTFILE=\"standard.flf\" figlet.c zipio.c crc.c inflate.c -o figlet
8308: chmod a+x figlet
8309: gcc -O2 -o chkfont chkfont.c
8310: => Unwrapping files-to-be-installed.
8311: #
8312: # make install
8313: ===> Checking for vulnerabilities in figlet-2.2.1nb2
8314: ===> Installing for figlet-2.2.1nb2
8315: install -d -o root -g wheel -m 755 /usr/pkg/bin
8316: install -d -o root -g wheel -m 755 /usr/pkg/man/man6
8317: mkdir -p /usr/pkg/share/figlet
8318: cp figlet /usr/pkg/bin
8319: cp chkfont /usr/pkg/bin
8320: chmod 555 figlist showfigfonts
8321: cp figlist /usr/pkg/bin
8322: cp showfigfonts /usr/pkg/bin
8323: cp fonts/*.flf /usr/pkg/share/figlet
8324: cp fonts/*.flc /usr/pkg/share/figlet
8325: cp figlet.6 /usr/pkg/man/man6
8326: ===> Registering installation for figlet-2.2.1nb2
8327: #
8328:
8329: B.2. Packaging figlet
8330:
8331: # make package
8332: ===> Checking for vulnerabilities in figlet-2.2.1nb2
8333: ===> Packaging figlet-2.2.1nb2
8334: ===> Building binary package for figlet-2.2.1nb2
8335: Creating package /home/cvs/pkgsrc/packages/i386/All/figlet-2.2.1nb2.tgz
8336: Using SrcDir value of /usr/pkg
8337: Registering depends:.
8338: #
8339:
8340: Appendix C. Directory layout of the pkgsrc FTP server
8341:
8342: Table of Contents
8343:
1.23 jakllsch 8344: C.1. distfiles: The distributed source files
8345: C.2. misc: Miscellaneous things
8346: C.3. packages: Binary packages
8347: C.4. reports: Bulk build reports
8348: C.5. current, pkgsrc-20xxQy: source packages
1.1 dsieger 8349:
8350: As in other big projects, the directory layout of pkgsrc is quite complex for
8351: newbies. This chapter explains where you find things on the FTP server. The
8352: base directory on ftp.NetBSD.org is /pub/pkgsrc/. On other servers it may be
8353: different, but inside this directory, everything should look the same, no
8354: matter on which server you are. This directory contains some subdirectories,
8355: which are explained below.
8356:
1.23 jakllsch 8357: C.1. distfiles: The distributed source files
1.1 dsieger 8358:
8359: The directory distfiles contains lots of archive files from all pkgsrc
8360: packages, which are mirrored here. The subdirectories are called after their
8361: package names and are used when the distributed files have names that don't
8362: explicitly contain a version number or are otherwise too generic (for example
8363: release.tar.gz).
8364:
1.23 jakllsch 8365: C.2. misc: Miscellaneous things
1.1 dsieger 8366:
8367: This directory contains things that individual pkgsrc developers find worth
8368: publishing.
8369:
1.23 jakllsch 8370: C.3. packages: Binary packages
1.1 dsieger 8371:
1.3 rillig 8372: This directory contains binary packages for the various platforms that are
8373: supported by pkgsrc. Each subdirectory is of the form OPSYS/ARCH/OSVERSION_TAG.
8374: The meaning of these variables is:
8375:
8376: * OPSYS is the name of the operating system for which the packages have been
1.9 rillig 8377: built. The name is taken from the output of the uname command, so it may
8378: differ from the one you are used to hear.
1.3 rillig 8379:
1.8 rillig 8380: * ARCH is the hardware architecture of the platform for which the packages
1.10 hubertf 8381: have been built. It also includes the ABI (Application Binary Interface)
8382: for platforms that have several of them.
1.3 rillig 8383:
1.8 rillig 8384: * OSVERSION is the version of the operating system. For version numbers that
8385: change often (for example NetBSD-current), the often-changing part should
8386: be replaced with an x, for example 4.99.x.
1.3 rillig 8387:
1.23 jakllsch 8388: * TAG is either 20xxQy for a stable branch, or head for packages built from
1.8 rillig 8389: the HEAD branch. The latter should only be used when the packages are
8390: updated on a regular basis. Otherwise the date from checking out pkgsrc
8391: should be appended, for example head_20071015.
1.3 rillig 8392:
8393: The rationale for exactly this scheme is that the pkgsrc users looking for
8394: binary packages can quickly click through the directories on the server and
8395: find the best binary packages for their machines. Since they usually know the
8396: operating system and the hardware architecture, OPSYS and ARCH are placed
8397: first. After these choices, they can select the best combination of OSVERSION
8398: and TAG together, since it is usually the case that packages stay compatible
8399: between different version of the operating system.
8400:
8401: In each of these directories, there is a whole binary packages collection for a
8402: specific platform. It has a directory called All which contains all binary
8403: packages. Besides that, there are various category directories that contain
8404: symbolic links to the real binary packages.
1.1 dsieger 8405:
1.23 jakllsch 8406: C.4. reports: Bulk build reports
1.8 rillig 8407:
8408: Here are the reports from bulk builds, for those who want to fix packages that
8409: didn't build on some of the platforms. The structure of subdirectories should
1.23 jakllsch 8410: look like the one in Section C.3, "packages: Binary packages".
1.8 rillig 8411:
1.23 jakllsch 8412: C.5. current, pkgsrc-20xxQy: source packages
1.1 dsieger 8413:
8414: These directories contain the "real" pkgsrc, that is the files that define how
8415: to create binary packages from source archives.
8416:
8417: The directory pkgsrc contains a snapshot of the CVS repository, which is
8418: updated regularly. The file pkgsrc.tar.gz contains the same as the directory,
8419: ready to be downloaded as a whole.
8420:
8421: In the directories for the quarterly branches, there is an additional file
1.23 jakllsch 8422: called pkgsrc-20xxQy.tar.gz, which contains the state of pkgsrc when it was
1.1 dsieger 8423: branched.
8424:
8425: Appendix D. Editing guidelines for the pkgsrc guide
8426:
8427: Table of Contents
8428:
8429: D.1. Make targets
8430: D.2. Procedure
8431:
8432: This section contains information on editing the pkgsrc guide itself.
8433:
8434: D.1. Make targets
8435:
8436: The pkgsrc guide's source code is stored in pkgsrc/doc/guide/files, and several
8437: files are created from it:
8438:
8439: * pkgsrc/doc/pkgsrc.txt
8440:
8441: * pkgsrc/doc/pkgsrc.html
8442:
1.2 rillig 8443: * http://www.NetBSD.org/docs/pkgsrc/
1.1 dsieger 8444:
1.2 rillig 8445: * http://www.NetBSD.org/docs/pkgsrc/pkgsrc.pdf: The PDF version of the pkgsrc
8446: guide.
1.1 dsieger 8447:
1.2 rillig 8448: * http://www.NetBSD.org/docs/pkgsrc/pkgsrc.ps: PostScript version of the
8449: pkgsrc guide.
1.1 dsieger 8450:
8451: D.2. Procedure
8452:
8453: The procedure to edit the pkgsrc guide is:
8454:
8455: 1. Make sure you have the packages needed to regenerate the pkgsrc guide (and
1.46 obache 8456: other XML-based NetBSD documentation) installed. These are automatically
8457: installed when you install the meta-pkgs/pkgsrc-guide-tools package.
1.1 dsieger 8458:
8459: 2. Run cd doc/guide to get to the right directory. All further steps will take
8460: place here.
8461:
8462: 3. Edit the XML file(s) in files/.
8463:
8464: 4. Run bmake to check the pkgsrc guide for valid XML and to build the final
8465: output files. If you get any errors at this stage, you can just edit the
8466: files, as there are only symbolic links in the working directory, pointing
8467: to the files in files/.
8468:
8469: 5. (cd files && cvs commit)
8470:
8471: 6. Run bmake clean && bmake to regenerate the output files with the proper RCS
8472: Ids.
8473:
8474: 7. Run bmake regen to install and commit the files in both pkgsrc/doc and
8475: htdocs.
8476:
8477: Note
8478:
8479: If you have added, removed or renamed some chapters, you need to
8480: synchronize them using cvs add or cvs delete in the htdocs directory.
8481:
CVSweb <webmaster@jp.NetBSD.org>