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