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