The pkgsrc guide

This target generates a README.html file, which can be viewed using a browser such as - www/mozilla or + www/firefox or www/links. The generated files contain references to any packages which are in the PACKAGES directory on @@ -7555,10 +7551,24 @@ Changes to the PLIST

17.5.2. Where to install documentation

Documentation should be installed into +

In general, documentation should be installed into ${PREFIX}/share/doc/${PKGBASE} or ${PREFIX}/share/doc/${PKGNAME} (the latter includes the version number of the package).

Many modern packages using GNU autoconf allow to set the directory + where HTML documentation is installed with the “--with-html-dir” + option.

An exception to the above is that library API + documentation generated with the textproc/gtk-doc tools, for use by + special browsers (devhelp) should be left at their default + location, which is + ${PREFIX}/share/gtk-doc. Such + documentation can be recognized from files ending in + .devhelp or + .devhelp2. (It is also acceptable to + install such files in + ${PREFIX}/share/doc; no additional + subdirectory level is allowed in this case.)

@@ -8265,36 +8275,36 @@ place.
`pkgsrc-users` mailing list.

-
20.1. What is the difference between +
20.1. What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS?
-
20.2. What is the difference between +
20.2. What is the difference between MAKE, GMAKE and MAKE_PROGRAM?
-
20.3. What is the difference between +
20.3. What is the difference between CC, PKG_CC and PKGSRC_COMPILER?
-
20.4. What is the difference between +
20.4. What is the difference between BUILDLINK_LDFLAGS, BUILDLINK_LDADD and BUILDLINK_LIBS?
-
20.5. Why does make show-var +
20.5. Why does make show-var VARNAME=BUILDLINK_PREFIX.foo say it's empty?
-
20.6. What does +
20.6. What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I don't understand the := inside it.
-
20.7. Which mailing lists are there for package +
20.7. Which mailing lists are there for package developers?
-
20.8. Where is the pkgsrc +
20.8. Where is the pkgsrc documentation?

@@ -8303,14 +8313,14 @@ place.
-20.1. +20.1.
What is the difference between `MAKEFLAGS`, `.MAKEFLAGS` and `MAKE_FLAGS`?
- +
`MAKEFLAGS` are the flags passed to the pkgsrc-internal invocations of make(1), while `MAKE_FLAGS` are the flags that are passed to @@ -8319,14 +8329,14 @@ place.
-20.2. +20.2.
What is the difference between `MAKE`, `GMAKE` and `MAKE_PROGRAM`?
- +
`MAKE` is the path to the make(1) program that is used in the pkgsrc infrastructure. `GMAKE` is the path to GNU @@ -8337,14 +8347,14 @@ place.
-20.3. +20.3.
What is the difference between `CC`, `PKG_CC` and `PKGSRC_COMPILER`?
- +
`CC` is the path to the real C compiler, which can be configured by the pkgsrc user. `PKG_CC` is the path to the compiler wrapper. @@ -8355,7 +8365,7 @@ place.
-20.4. +20.4.
What is the difference between `BUILDLINK_LDFLAGS`, @@ -8363,19 +8373,19 @@ place.
`BUILDLINK_LIBS`?
- +
[FIXME]
-20.5. +20.5.
Why does make show-var VARNAME=BUILDLINK_PREFIX.`foo` say it's empty?
- +
For optimization reasons, some variables are only available in the “wrapper” phase and later. To “simulate” the wrapper phase, append @@ -8384,7 +8394,7 @@ place.
-20.6. +20.6.
What does `${MASTER_SITE_SOURCEFORGE:=package/}` mean? I @@ -8392,7 +8402,7 @@ place.
it.
- +
The `:=` is not really an assignment operator, like you might expect at first sight. Instead, it is a degenerate form of @@ -8408,13 +8418,13 @@ place.
-20.7. +20.7.
Which mailing lists are there for package developers?
- +

tech-pkg

This is a list for technical discussions related @@ -8433,13 +8443,13 @@ place.
-20.8. +20.8.
Where is the pkgsrc documentation?
- +
There are many places where you can find documentation about pkgsrc:
@@ -8692,8 +8702,8 @@ place.
21.5.1. Procedures with parameters

In a traditional imperative programming language some of the .mk files could be described as - procedures. They take some input parameters and—after - inclusion—provide a result in output parameters. Since all + procedures. They take some input parameters and—after + inclusion—provide a result in output parameters. Since all variables in Makefiles have global scope care must be taken not to use parameter names that have already another meaning. For example, PKGNAME is a @@ -9401,7 +9411,7 @@ source packages