From f4f0105892fd84985aadf6ab2bc2a9e4edd0bd1c Mon Sep 17 00:00:00 2001 From: rillig Date: Fri, 9 Jan 2009 11:04:27 +0000 Subject: regen --- doc/pkgsrc.html | 395 +++++++++++++++++++++++++++++++------------------------- 1 file changed, 218 insertions(+), 177 deletions(-) (limited to 'doc/pkgsrc.html') diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html index 91e975b65f1..68e8bd4a519 100644 --- a/doc/pkgsrc.html +++ b/doc/pkgsrc.html @@ -117,8 +117,8 @@
5.4. Selecting and configuring the compiler
5.4.1. Selecting the compiler
-
5.4.2. Additional flags to the compiler (CFLAGS)
-
5.4.3. Additional flags to the linker (LDFLAGS)
+
5.4.2. Additional flags to the compiler (CFLAGS)
+
5.4.3. Additional flags to the linker (LDFLAGS)
5.5. Developer/advanced settings
5.6. Selecting Build Options
@@ -145,14 +145,17 @@ builds)
7.3.8. Uploading results of a bulk build
7.4. Running a pbulk-style bulk build
-
7.4.1. Configuration
+
+
7.4.1. Preparation
+
7.4.2. Configuration
+
7.5. Creating a multiple CD-ROM packages collection
7.5.1. Example of cdpack
8. Directory layout of the installed files
-
8.1. File system layout in ${LOCALBASE}
-
8.2. File system layout in ${VARBASE}
+
8.1. File system layout in ${LOCALBASE}
+
8.2. File system layout in ${VARBASE}
9. Frequently Asked Questions
@@ -163,17 +166,17 @@ builds)
9.5. How to resume transfers when fetching distfiles?
9.6. How can I install/use modular X.org from pkgsrc?
9.7. How to fetch files from behind a firewall
-
9.8. How do I tell make fetch to do passive FTP?
+
9.8. How do I tell make fetch to do passive FTP?
9.9. How to fetch all distfiles at once
-
9.10. What does “Don't know how to make -/usr/share/tmac/tmac.andoc” mean?
-
9.11. What does “Could not find bsd.own.mk” mean?
+
9.10. What does Don't know how to make +/usr/share/tmac/tmac.andoc mean?
+
9.11. What does Could not find bsd.own.mk mean?
9.12. Using 'sudo' with pkgsrc
9.13. How do I change the location of configuration files?
9.14. Automated security checks
-
9.15. Why do some packages ignore my CFLAGS?
+
9.15. Why do some packages ignore my CFLAGS?
9.16. A package does not build. What shall I do?
-
9.17. What does “Makefile appears to contain unresolved cvs/rcs/??? merge conflicts” mean?
+
9.17. What does Makefile appears to contain unresolved cvs/rcs/??? merge conflicts mean?
II. The pkgsrc developer's guide
@@ -190,8 +193,8 @@ builds)
11. Package components - files, directories and contents
-
11.1. Makefile
-
11.2. distinfo
+
11.1. Makefile
+
11.2. distinfo
11.3. patches/*
11.3.1. Structure of a single patch file
@@ -207,13 +210,13 @@ builds)
11.5.2. Files affecting the build process
11.5.3. Files affecting nothing at all
-
11.6. work*
-
11.7. files/*
+
11.6. work*
+
11.7. files/*
-
12. Programming in Makefiles
+
12. Programming in Makefiles
12.1. Caveats
-
12.2. Makefile variables
+
12.2. Makefile variables
12.2.1. Naming conventions
12.3. Code snippets
@@ -227,25 +230,25 @@ builds)
13. PLIST issues
13.1. RCS ID
-
13.2. Semi-automatic PLIST generation
-
13.3. Tweaking output of make print-PLIST
+
13.2. Semi-automatic PLIST generation
+
13.3. Tweaking output of make print-PLIST
13.4. Variable substitution in PLIST
13.5. Man page compression
-
13.6. Changing PLIST source with PLIST_SRC
+
13.6. Changing PLIST source with PLIST_SRC
13.7. Platform-specific and differing PLISTs
13.8. Sharing directories between packages
14. Buildlink methodology
14.1. Converting packages to use buildlink3
-
14.2. Writing buildlink3.mk files
+
14.2. Writing buildlink3.mk files
14.2.1. Anatomy of a buildlink3.mk file
-
14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
+
14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
-
14.3. Writing builtin.mk files
+
14.3. Writing builtin.mk files
-
14.3.1. Anatomy of a builtin.mk file
+
14.3.1. Anatomy of a builtin.mk file
14.3.2. Global preferences for native or pkgsrc software
@@ -258,7 +261,7 @@ builds)
15.2. Configuration files
-
15.2.1. How PKG_SYSCONFDIR is set
+
15.2.1. How PKG_SYSCONFDIR is set
15.2.2. Telling the software where configuration files are
15.2.3. Patching installations
15.2.4. Disabling handling of configuration files
@@ -274,7 +277,7 @@ builds)
16. Options handling
16.1. Global default options
-
16.2. Converting packages to use bsd.options.mk
+
16.2. Converting packages to use bsd.options.mk
16.3. Option Names
16.4. Determining the options of dependencies
@@ -284,21 +287,21 @@ builds)
17.2. Program location
17.3. Directories used during the build process
17.4. Running a phase
-
17.5. The fetch phase
+
17.5. The fetch phase
17.5.1. What to fetch and where to get it from
17.5.2. How are the files fetched?
-
17.6. The checksum phase
-
17.7. The extract phase
-
17.8. The patch phase
-
17.9. The tools phase
-
17.10. The wrapper phase
-
17.11. The configure phase
-
17.12. The build phase
-
17.13. The test phase
-
17.14. The install phase
-
17.15. The package phase
+
17.6. The checksum phase
+
17.7. The extract phase
+
17.8. The patch phase
+
17.9. The tools phase
+
17.10. The wrapper phase
+
17.11. The configure phase
+
17.12. The build phase
+
17.13. The test phase
+
17.14. The install phase
+
17.15. The package phase
17.16. Cleaning up
17.17. Other helpful targets
@@ -314,7 +317,7 @@ builds)
19.1. General operation
19.1.1. Portability of packages
-
19.1.2. How to pull in user-settable variables from mk.conf
+
19.1.2. How to pull in user-settable variables from ???
19.1.3. User interaction
19.1.4. Handling licenses
19.1.5. Restricted packages
@@ -326,12 +329,12 @@ builds)
19.1.11. How to handle incrementing versions when fixing an existing package
19.1.12. Substituting variable text in the package files (the SUBST framework)
-
19.2. Fixing problems in the fetch phase
+
19.2. Fixing problems in the fetch phase
19.2.1. Packages whose distfiles aren't available for plain downloading
19.2.2. How to handle modified distfiles with the 'old' name
-
19.3. Fixing problems in the configure phase
+
19.3. Fixing problems in the configure phase
19.3.1. Shared libraries - libtool
19.3.2. Using libtool on GNU packages that already support libtool
@@ -344,14 +347,14 @@ builds)
19.4.3. Packages containing perl scripts
19.4.4. Other programming languages
-
19.5. Fixing problems in the build phase
+
19.5. Fixing problems in the build phase
19.5.1. Compiling C and C++ code conditionally
19.5.2. How to handle compiler bugs
-
19.5.3. Undefined reference to “...”
+
19.5.3. Undefined reference to ...
19.5.4. Running out of memory
-
19.6. Fixing problems in the install phase
+
19.6. Fixing problems in the install phase
19.6.1. Creating needed directories
19.6.2. Where to install documentation
@@ -415,8 +418,8 @@ builds)
24.6. The order in which files are loaded
-
24.6.1. The order in bsd.prefs.mk
-
24.6.2. The order in bsd.pkg.mk
+
24.6.1. The order in bsd.prefs.mk
+
24.6.2. The order in bsd.pkg.mk
25. Regression tests
@@ -442,7 +445,7 @@ builds)
A.1.1. Makefile
A.1.2. DESCR
A.1.3. PLIST
-
A.1.4. Checking a package with pkglint
+
A.1.4. Checking a package with pkglint
A.2. Steps for building, installing, packaging
@@ -453,14 +456,14 @@ builds)
C. Directory layout of the pkgsrc FTP server
-
C.1. bootstrap-pkgsrc: Bootstrap kits
-
C.2. distfiles: The distributed source files
-
C.3. iso: Currently empty
-
C.4. misc: Miscellaneous things
-
C.5. packages: Binary packages
-
C.6. reports: Bulk build reports
-
C.7. current, -pkgsrc-200xQy: +
C.1. bootstrap-pkgsrc: Bootstrap kits
+
C.2. distfiles: The distributed source files
+
C.3. iso: Currently empty
+
C.4. misc: Miscellaneous things
+
C.5. packages: Binary packages
+
C.6. reports: Bulk build reports
+
C.7. current, +pkgsrc-200xQy: source packages
D. Editing guidelines for the pkgsrc guide
@@ -828,8 +831,8 @@ minutes!

5.4. Selecting and configuring the compiler
5.4.1. Selecting the compiler
-
5.4.2. Additional flags to the compiler (CFLAGS)
-
5.4.3. Additional flags to the linker (LDFLAGS)
+
5.4.2. Additional flags to the compiler (CFLAGS)
+
5.4.3. Additional flags to the linker (LDFLAGS)
5.5. Developer/advanced settings
5.6. Selecting Build Options
@@ -856,14 +859,17 @@ builds)
7.3.8. Uploading results of a bulk build
7.4. Running a pbulk-style bulk build
-
7.4.1. Configuration
+
+
7.4.1. Preparation
+
7.4.2. Configuration
+
7.5. Creating a multiple CD-ROM packages collection
7.5.1. Example of cdpack
8. Directory layout of the installed files
-
8.1. File system layout in ${LOCALBASE}
-
8.2. File system layout in ${VARBASE}
+
8.1. File system layout in ${LOCALBASE}
+
8.2. File system layout in ${VARBASE}
9. Frequently Asked Questions
@@ -874,17 +880,17 @@ builds)
9.5. How to resume transfers when fetching distfiles?
9.6. How can I install/use modular X.org from pkgsrc?
9.7. How to fetch files from behind a firewall
-
9.8. How do I tell make fetch to do passive FTP?
+
9.8. How do I tell make fetch to do passive FTP?
9.9. How to fetch all distfiles at once
-
9.10. What does “Don't know how to make -/usr/share/tmac/tmac.andoc” mean?
-
9.11. What does “Could not find bsd.own.mk” mean?
+
9.10. What does Don't know how to make +/usr/share/tmac/tmac.andoc mean?
+
9.11. What does Could not find bsd.own.mk mean?
9.12. Using 'sudo' with pkgsrc
9.13. How do I change the location of configuration files?
9.14. Automated security checks
-
9.15. Why do some packages ignore my CFLAGS?
+
9.15. Why do some packages ignore my CFLAGS?
9.16. A package does not build. What shall I do?
-
9.17. What does “Makefile appears to contain unresolved cvs/rcs/??? merge conflicts” mean?
+
9.17. What does Makefile appears to contain unresolved cvs/rcs/??? merge conflicts mean?
@@ -2085,8 +2091,8 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10.00
5.4. Selecting and configuring the compiler
5.4.1. Selecting the compiler
-
5.4.2. Additional flags to the compiler (CFLAGS)
-
5.4.3. Additional flags to the linker (LDFLAGS)
+
5.4.2. Additional flags to the compiler (CFLAGS)
+
5.4.3. Additional flags to the linker (LDFLAGS)
5.5. Developer/advanced settings
5.6. Selecting Build Options
@@ -2474,7 +2480,10 @@ builds)
7.3.8. Uploading results of a bulk build
7.4. Running a pbulk-style bulk build
-
7.4.1. Configuration
+
+
7.4.1. Preparation
+
7.4.2. Configuration
+
7.5. Creating a multiple CD-ROM packages collection
7.5.1. Example of cdpack
@@ -2540,10 +2549,11 @@ temporary filesystems, others must survive a sudden reboot.

7.3. Running an old-style bulk build

-
-

Warning

-

The rest of this section is rather old. Don't rely on it -too much.

+
+

Note

+

There are two ways of doing a bulk build. The old-style +one and the new-style “pbulk”. The latter is the recommended +way.

@@ -2824,7 +2834,7 @@ fi /usr/sandbox/usr/pkgsrc/packages and .../distfiles point somewhere appropriate. NFS- and/or nullfs-mounts may come in handy!

-

  • Edit mk.conf, see Section 7.3.1.2, “mk.conf”.

    • +

  • Edit mk.conf, see Section 7.3.1.2, “???”.

  • Adjust mk/bulk/build.conf to suit your needs.

    • When the chroot sandbox is set up, you can start @@ -2941,10 +2951,41 @@ nbftp% chmod 755 .

    7.4. Running a pbulk-style bulk build

    +

    Running a pbulk-style bulk build works roughly as follows:

    +
      +

    • First, build the pbulk infrastructure in a fresh pkgsrc location.

      • +

    • Then, build each of the packages from a clean installation directory using the infrastructure.

      • +

    -7.4.1. Configuration

    +7.4.1. Preparation
    +

    First, you need to create a pkgsrc installation for the pbulk infrastructure. No matter on which platform you are (even on NetBSD), you should bootstrap into its own directory. Let's take the directory /usr/pbulk-outer or $HOME/pbulk-outer for it. This installation will be bootstrapped and all the tools that are required for the bulk build will be installed there.

    +
    +$ cd /usr/pkgsrc
+$ ./bootstrap/bootstrap --prefix=/usr/pbulk --varbase=/usr/pbulk/var --workdir=/tmp/pbulk-bootstrap
+$ rm -rf /tmp/pbulk-bootstrap
+
    +

    Now the basic environment for the pbulk infrastructure is installed. The specific tools are still missing. This is a good time to edit the pkgsrc configuration file /usr/pbulk/etc/mk.conf to fit your needs. Typical things you might set now are:

    +
      +

    • PKG_DEVELOPER=yes, to enable many consistency checks,

      • +

    • WRKOBJDIR=/tmp/pbulk-outer, to keep /usr/pkgsrc free from any modifications,

      • +

    • DISTDIR=/distfiles, to have only one directory in which all distfiles (for the infrastructure and for the actual packages) are downloaded,

      • +

    • ACCEPTABLE_LICENSES+=..., to select some licenses additional to the usual Free/Open Source licenses that are acceptable to you,

      • +

    • _ACCEPTABLE=yes, to accept all licenses, no matter how restrictive they are.

      • +
    +

    Now you are ready to build the rest of the pbulk infrastructure.

    +
    +$ cd pkgtools/pbulk
+$ /usr/pbulk/bin/bmake install
+$ rm -rf /tmp/pbulk-outer
+
    +

    Now the pbulk infrastructure is built and installed. It still needs to be configured, and after some more preparation, we will be able to start the real bulk build.

    +
    +
    +

    +7.4.2. Configuration

    TODO; see pkgsrc/doc/HOWTO-pbulk for more information.

    +

    TODO: continue writing

    @@ -2999,8 +3040,8 @@ nbftp% chmod 755 .

    Table of Contents

    -
    8.1. File system layout in ${LOCALBASE}
    -
    8.2. File system layout in ${VARBASE}
    +
    8.1. File system layout in ${LOCALBASE}
    +
    8.2. File system layout in ${VARBASE}

    The files that are installed by pkgsrc are organized in a way that @@ -3147,17 +3188,17 @@ currently running.

    9.5. How to resume transfers when fetching distfiles?
    9.6. How can I install/use modular X.org from pkgsrc?
    9.7. How to fetch files from behind a firewall
    -
    9.8. How do I tell make fetch to do passive FTP?
    +
    9.8. How do I tell make fetch to do passive FTP?
    9.9. How to fetch all distfiles at once
    -
    9.10. What does “Don't know how to make -/usr/share/tmac/tmac.andoc” mean?
    -
    9.11. What does “Could not find bsd.own.mk” mean?
    +
    9.10. What does Don't know how to make +/usr/share/tmac/tmac.andoc mean?
    +
    9.11. What does Could not find bsd.own.mk mean?
    9.12. Using 'sudo' with pkgsrc
    9.13. How do I change the location of configuration files?
    9.14. Automated security checks
    -
    9.15. Why do some packages ignore my CFLAGS?
    +
    9.15. Why do some packages ignore my CFLAGS?
    9.16. A package does not build. What shall I do?
    -
    9.17. What does “Makefile appears to contain unresolved cvs/rcs/??? merge conflicts” mean?
    +
    9.17. What does Makefile appears to contain unresolved cvs/rcs/??? merge conflicts mean?

    This section contains hints, tips & tricks on special things in @@ -3588,8 +3629,8 @@ anymore, you can remove that file and run cvs -q u

    11. Package components - files, directories and contents
    -
    11.1. Makefile
    -
    11.2. distinfo
    +
    11.1. Makefile
    +
    11.2. distinfo
    11.3. patches/*
    11.3.1. Structure of a single patch file
    @@ -3605,13 +3646,13 @@ anymore, you can remove that file and run cvs -q u
    11.5.2. Files affecting the build process
    11.5.3. Files affecting nothing at all
    -
    11.6. work*
    -
    11.7. files/*
    +
    11.6. work*
    +
    11.7. files/*
    -
    12. Programming in Makefiles
    +
    12. Programming in Makefiles
    12.1. Caveats
    -
    12.2. Makefile variables
    +
    12.2. Makefile variables
    12.2.1. Naming conventions
    12.3. Code snippets
    @@ -3625,25 +3666,25 @@ anymore, you can remove that file and run cvs -q u
    13. PLIST issues
    13.1. RCS ID
    -
    13.2. Semi-automatic PLIST generation
    -
    13.3. Tweaking output of make print-PLIST
    +
    13.2. Semi-automatic PLIST generation
    +
    13.3. Tweaking output of make print-PLIST
    13.4. Variable substitution in PLIST
    13.5. Man page compression
    -
    13.6. Changing PLIST source with PLIST_SRC
    +
    13.6. Changing PLIST source with PLIST_SRC
    13.7. Platform-specific and differing PLISTs
    13.8. Sharing directories between packages
    14. Buildlink methodology
    14.1. Converting packages to use buildlink3
    -
    14.2. Writing buildlink3.mk files
    +
    14.2. Writing buildlink3.mk files
    14.2.1. Anatomy of a buildlink3.mk file
    -
    14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
    +
    14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
    -
    14.3. Writing builtin.mk files
    +
    14.3. Writing builtin.mk files
    -
    14.3.1. Anatomy of a builtin.mk file
    +
    14.3.1. Anatomy of a builtin.mk file
    14.3.2. Global preferences for native or pkgsrc software
    @@ -3656,7 +3697,7 @@ anymore, you can remove that file and run cvs -q u
    15.2. Configuration files
    -
    15.2.1. How PKG_SYSCONFDIR is set
    +
    15.2.1. How PKG_SYSCONFDIR is set
    15.2.2. Telling the software where configuration files are
    15.2.3. Patching installations
    15.2.4. Disabling handling of configuration files
    @@ -3672,7 +3713,7 @@ anymore, you can remove that file and run cvs -q u
    16. Options handling
    16.1. Global default options
    -
    16.2. Converting packages to use bsd.options.mk
    +
    16.2. Converting packages to use bsd.options.mk
    16.3. Option Names
    16.4. Determining the options of dependencies
    @@ -3682,21 +3723,21 @@ anymore, you can remove that file and run cvs -q u
    17.2. Program location
    17.3. Directories used during the build process
    17.4. Running a phase
    -
    17.5. The fetch phase
    +
    17.5. The fetch phase
    17.5.1. What to fetch and where to get it from
    17.5.2. How are the files fetched?
    -
    17.6. The checksum phase
    -
    17.7. The extract phase
    -
    17.8. The patch phase
    -
    17.9. The tools phase
    -
    17.10. The wrapper phase
    -
    17.11. The configure phase
    -
    17.12. The build phase
    -
    17.13. The test phase
    -
    17.14. The install phase
    -
    17.15. The package phase
    +
    17.6. The checksum phase
    +
    17.7. The extract phase
    +
    17.8. The patch phase
    +
    17.9. The tools phase
    +
    17.10. The wrapper phase
    +
    17.11. The configure phase
    +
    17.12. The build phase
    +
    17.13. The test phase
    +
    17.14. The install phase
    +
    17.15. The package phase
    17.16. Cleaning up
    17.17. Other helpful targets
    @@ -3712,7 +3753,7 @@ anymore, you can remove that file and run cvs -q u
    19.1. General operation
    19.1.1. Portability of packages
    -
    19.1.2. How to pull in user-settable variables from mk.conf
    +
    19.1.2. How to pull in user-settable variables from ???
    19.1.3. User interaction
    19.1.4. Handling licenses
    19.1.5. Restricted packages
    @@ -3724,12 +3765,12 @@ anymore, you can remove that file and run cvs -q u
    19.1.11. How to handle incrementing versions when fixing an existing package
    19.1.12. Substituting variable text in the package files (the SUBST framework)
    -
    19.2. Fixing problems in the fetch phase
    +
    19.2. Fixing problems in the fetch phase
    19.2.1. Packages whose distfiles aren't available for plain downloading
    19.2.2. How to handle modified distfiles with the 'old' name
    -
    19.3. Fixing problems in the configure phase
    +
    19.3. Fixing problems in the configure phase
    19.3.1. Shared libraries - libtool
    19.3.2. Using libtool on GNU packages that already support libtool
    @@ -3742,14 +3783,14 @@ anymore, you can remove that file and run cvs -q u
    19.4.3. Packages containing perl scripts
    19.4.4. Other programming languages
    -
    19.5. Fixing problems in the build phase
    +
    19.5. Fixing problems in the build phase
    19.5.1. Compiling C and C++ code conditionally
    19.5.2. How to handle compiler bugs
    -
    19.5.3. Undefined reference to “...”
    +
    19.5.3. Undefined reference to ...
    19.5.4. Running out of memory
    -
    19.6. Fixing problems in the install phase
    +
    19.6. Fixing problems in the install phase
    19.6.1. Creating needed directories
    19.6.2. Where to install documentation
    @@ -4136,8 +4177,8 @@ everything worked.

    Table of Contents

    -
    11.1. Makefile
    -
    11.2. distinfo
    +
    11.1. Makefile
    +
    11.2. distinfo
    11.3. patches/*
    11.3.1. Structure of a single patch file
    @@ -4153,8 +4194,8 @@ everything worked.

    11.5.2. Files affecting the build process
    11.5.3. Files affecting nothing at all
    -
    11.6. work*
    -
    11.7. files/*
    +
    11.6. work*
    +
    11.7. files/*

    Whenever you're preparing a package, there are a number of @@ -4219,7 +4260,7 @@ converters games mbone print x11 DYNAMIC_MASTER_SITES, DIST_SUBDIR, EXTRACT_SUFX and DISTFILES are discussed in detail in - Section 17.5, “The fetch phase”.

    + Section 17.5, “The fetch phase”.

    The second section contains information about separately downloaded patches, if any. @@ -4393,7 +4434,7 @@ converters games mbone print x11 directory to patches/.

    When you have finished a package, remember to generate the checksums for the patch files by using the make - makepatchsum command, see Section 11.2, “distinfo”.

    + makepatchsum     command, see Section 11.2, “distinfo”.

    When adding a patch that corrects a problem in the distfile (rather than e.g. enforcing pkgsrc's view of where man pages should go), send the patch as a bug report to the @@ -4721,7 +4762,7 @@ FILESDIR=${.CURDIR}/../xemacs/files

    Table of Contents

    12.1. Caveats
    -
    12.2. Makefile variables
    +
    12.2. Makefile variables
    12.2.1. Naming conventions
    12.3. Code snippets
    @@ -5047,11 +5088,11 @@ VAR:= ${VAR:N${_othervar_:C/-//}}

    Table of Contents

    13.1. RCS ID
    -
    13.2. Semi-automatic PLIST generation
    -
    13.3. Tweaking output of make print-PLIST
    +
    13.2. Semi-automatic PLIST generation
    +
    13.3. Tweaking output of make print-PLIST
    13.4. Variable substitution in PLIST
    13.5. Man page compression
    -
    13.6. Changing PLIST source with PLIST_SRC
    +
    13.6. Changing PLIST source with PLIST_SRC
    13.7. Platform-specific and differing PLISTs
    13.8. Sharing directories between packages
    @@ -5265,14 +5306,14 @@ USE_DIRS+= xdg-1.1

    Table of Contents

    14.1. Converting packages to use buildlink3
    -
    14.2. Writing buildlink3.mk files
    +
    14.2. Writing buildlink3.mk files
    14.2.1. Anatomy of a buildlink3.mk file
    -
    14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
    +
    14.2.2. Updating BUILDLINK_API_DEPENDS.pkg in buildlink3.mk files
    -
    14.3. Writing builtin.mk files
    +
    14.3. Writing builtin.mk files
    -
    14.3.1. Anatomy of a builtin.mk file
    +
    14.3.1. Anatomy of a builtin.mk file
    14.3.2. Global preferences for native or pkgsrc software
    @@ -5733,7 +5774,7 @@ PREFER_NATIVE= getopt skey tcp_wrappers
    15.2. Configuration files
    -
    15.2.1. How PKG_SYSCONFDIR is set
    +
    15.2.1. How PKG_SYSCONFDIR is set
    15.2.2. Telling the software where configuration files are
    15.2.3. Patching installations
    15.2.4. Disabling handling of configuration files
    @@ -6128,7 +6169,7 @@ environment variable to NO.

    Table of Contents

    16.1. Global default options
    -
    16.2. Converting packages to use bsd.options.mk
    +
    16.2. Converting packages to use bsd.options.mk
    16.3. Option Names
    16.4. Determining the options of dependencies
    @@ -6372,21 +6413,21 @@ details.

    17.2. Program location
    17.3. Directories used during the build process
    17.4. Running a phase
    -
    17.5. The fetch phase
    +
    17.5. The fetch phase
    17.5.1. What to fetch and where to get it from
    17.5.2. How are the files fetched?
    -
    17.6. The checksum phase
    -
    17.7. The extract phase
    -
    17.8. The patch phase
    -
    17.9. The tools phase
    -
    17.10. The wrapper phase
    -
    17.11. The configure phase
    -
    17.12. The build phase
    -
    17.13. The test phase
    -
    17.14. The install phase
    -
    17.15. The package phase
    +
    17.6. The checksum phase
    +
    17.7. The extract phase
    +
    17.8. The patch phase
    +
    17.9. The tools phase
    +
    17.10. The wrapper phase
    +
    17.11. The configure phase
    +
    17.12. The build phase
    +
    17.13. The test phase
    +
    17.14. The install phase
    +
    17.15. The package phase
    17.16. Cleaning up
    17.17. Other helpful targets
    @@ -6557,7 +6598,7 @@ GTKDIR_DEFAULT= ${LOCALBASE}

    The CREATE_WRKDIR_SYMLINK definition takes either the value yes or no and defaults - to yes. It indicates whether a symbolic link to the + to no. It indicates whether a symbolic link to the WRKDIR is to be created in the pkgsrc entry's directory. If users would like to have their pkgsrc trees behave in a read-only manner, then the value of @@ -7343,7 +7384,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site}${file} ${FETCH_AFTER_ARGS} PLIST, as the “find -newer” command used by this target won't catch them!

    -

    See Section 13.3, “Tweaking output of make print-PLIST” for more +

    See Section 13.3, “Tweaking output of make print-PLIST” for more information on this target.

    bulk-package
    @@ -7486,7 +7527,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

    18.4.1.

    +

    18.4.1.

    How do I add a new tool?

    @@ -7496,7 +7537,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

    18.4.2.

    +

    18.4.2.

    How do I get a list of all available tools?

    @@ -7507,7 +7548,7 @@ TOOLS_PLATFORM.true?= true # shell builtin -

    18.4.3.

    +

    18.4.3.

    How can I get a list of all the tools that a package is using while being built? I want to know whether it @@ -7532,7 +7573,7 @@ TOOLS_PLATFORM.true?= true # shell builtin

    19.1. General operation
    19.1.1. Portability of packages
    -
    19.1.2. How to pull in user-settable variables from mk.conf
    +
    19.1.2. How to pull in user-settable variables from ???
    19.1.3. User interaction
    19.1.4. Handling licenses
    19.1.5. Restricted packages
    @@ -7544,12 +7585,12 @@ TOOLS_PLATFORM.true?= true # shell builtin
    19.1.11. How to handle incrementing versions when fixing an existing package
    19.1.12. Substituting variable text in the package files (the SUBST framework)
    -
    19.2. Fixing problems in the fetch phase
    +
    19.2. Fixing problems in the fetch phase
    19.2.1. Packages whose distfiles aren't available for plain downloading
    19.2.2. How to handle modified distfiles with the 'old' name
    -
    19.3. Fixing problems in the configure phase
    +
    19.3. Fixing problems in the configure phase
    19.3.1. Shared libraries - libtool
    19.3.2. Using libtool on GNU packages that already support libtool
    @@ -7562,14 +7603,14 @@ TOOLS_PLATFORM.true?= true # shell builtin
    19.4.3. Packages containing perl scripts
    19.4.4. Other programming languages
    -
    19.5. Fixing problems in the build phase
    +
    19.5. Fixing problems in the build phase
    19.5.1. Compiling C and C++ code conditionally
    19.5.2. How to handle compiler bugs
    -
    19.5.3. Undefined reference to “...”
    +
    19.5.3. Undefined reference to ...
    19.5.4. Running out of memory
    -
    19.6. Fixing problems in the install phase
    +
    19.6. Fixing problems in the install phase
    19.6.1. Creating needed directories
    19.6.2. Where to install documentation
    @@ -8959,7 +9000,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist get registered in the database:

    1. Include - ../../textproc/rarian/omf.mk + ../../textproc/scrollkeeper/omf.mk instead of its buildlink3.mk file. This takes care of rebuilding the scrollkeeper database at installation and deinstallation time, and disallows any access @@ -9259,7 +9300,7 @@ PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Pg/.packlist package.

    2. Look at the Makefile, fix if - necessary; see Section 11.1, “Makefile”.

      3. + necessary; see Section 11.1, “Makefile”.

    3. Generate a PLIST:

      # make install
@@ -9521,7 +9562,7 @@ do?
 
 
 
-
      22.1.
      
+
      22.1.
      
 
 
      What is the difference between
 	MAKEFLAGS, .MAKEFLAGS and
@@ -9537,7 +9578,7 @@ do?
 
 
 
-
      22.2.
      
+
      22.2.
      
 
 
      What is the difference between
 	MAKE, GMAKE and
@@ -9555,7 +9596,7 @@ do?
 
 
 
-
      22.3.
      
+
      22.3.
      
 
 
      What is the difference between
 	CC, PKG_CC and
@@ -9573,7 +9614,7 @@ do?
 
 
 
-
      22.4.
      
+
      22.4.
      
 
 
      What is the difference between
 	BUILDLINK_LDFLAGS,
@@ -9586,7 +9627,7 @@ do?
 
 
 
-
      22.5.
      
+
      22.5.
      
 
 
      Why does make show-var
 	VARNAME=BUILDLINK_PREFIX.foo
@@ -9602,7 +9643,7 @@ do?
 
 
 
-
      22.6.
      
+
      22.6.
      
 
 
      What does
 	${MASTER_SITE_SOURCEFORGE:=package/} mean? I
@@ -9626,7 +9667,7 @@ do?
 
 
 
-
      22.7.
      
+
      22.7.
      
 
 
      Which mailing lists are there for package
 	developers?
      
@@ -9651,7 +9692,7 @@ do?
 
 
 
-
      22.8.
      
+
      22.8.
      
 
 
      Where is the pkgsrc
 	documentation?
      
@@ -9699,7 +9740,7 @@ do?
 
 
 
-
      22.9.
      
+
      22.9.
      
 
 
      I have a little time to kill.  What shall I
 do?
      
@@ -10052,8 +10093,8 @@ details.
    24.6. The order in which files are loaded
    -
    24.6.1. The order in bsd.prefs.mk
    -
    24.6.2. The order in bsd.pkg.mk
    +
    24.6.1. The order in bsd.prefs.mk
    +
    24.6.2. The order in bsd.pkg.mk
    25. Regression tests
    @@ -10095,8 +10136,8 @@ details.

    24.6. The order in which files are loaded
    -
    24.6.1. The order in bsd.prefs.mk
    -
    24.6.2. The order in bsd.pkg.mk
    +
    24.6.1. The order in bsd.prefs.mk
    +
    24.6.2. The order in bsd.pkg.mk
    @@ -10524,7 +10565,7 @@ CFLAGS+= -Wall
    A.1.1. Makefile
    A.1.2. DESCR
    A.1.3. PLIST
    -
    A.1.4. Checking a package with pkglint
    +
    A.1.4. Checking a package with pkglint
    A.2. Steps for building, installing, packaging
    @@ -10825,14 +10866,14 @@ Registering depends:.

    Table of Contents

    -
    C.1. bootstrap-pkgsrc: Bootstrap kits
    -
    C.2. distfiles: The distributed source files
    -
    C.3. iso: Currently empty
    -
    C.4. misc: Miscellaneous things
    -
    C.5. packages: Binary packages
    -
    C.6. reports: Bulk build reports
    -
    C.7. current, -pkgsrc-200xQy: +
    C.1. bootstrap-pkgsrc: Bootstrap kits
    +
    C.2. distfiles: The distributed source files
    +
    C.3. iso: Currently empty
    +
    C.4. misc: Miscellaneous things
    +
    C.5. packages: Binary packages
    +
    C.6. reports: Bulk build reports
    +
    C.7. current, +pkgsrc-200xQy: source packages
    @@ -10923,7 +10964,7 @@ source packages C.6. reports: Bulk build reports

    Here are the reports from bulk builds, for those who want to fix packages that didn't build on some of the platforms. The - structure of subdirectories should look like the one in Section C.5, “packages: Binary packages”.

    + structure of subdirectories should look like the one in Section C.5, “packages: Binary packages”.

    -- cgit v1.2.3