% make show-var VARNAME=LOCALBASE @@ -1552,11 +1552,11 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10 created yourself (see next section), that you put into pkgsrc/packages manually or that is located on a remote FTP server, you can use the "bin-install" target. This target will - install a binary package - if available - via pkg_add(1), + install a binary package - if available - via pkg_add(1), else do a make package. The list of remote FTP sites searched is kept in the variable BINPKG_SITES, which defaults to - ftp.NetBSD.org. Any flags that should be added to pkg_add(1) + ftp.NetBSD.org. Any flags that should be added to pkg_add(1) can be put into BIN_INSTALL_FLAGS. See pkgsrc/mk/defaults/mk.conf for more details.

@@ -1595,7 +1595,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10

The whole pkgsrc system is configured in a single file, usually called mk.conf. In which directory pkgsrc looks for that file depends on the installation. On NetBSD, when you use -make(1) from the base system, it is in the directory +make(1) from the base system, it is in the directory /etc/. In all other cases the default location is ${PREFIX}/etc/, depending on where you told the bootstrap program to install the binary packages.

@@ -1741,7 +1741,7 @@ uid=1000(myusername) gid=100(users) grou

For the following command, you must be able to gain root - privileges using su(1) + privileges using su(1)

@@ -1982,7 +1982,7 @@ PKG_OPTIONS.apache=     suexec

6.1. Building a single binary package

wrong: @@ -4060,11 +4060,11 @@ correct: wrong will exist, although there was an error message in the first run. On the other hand, running make correct gives an error message twice, as expected.

You might remember that make(1) sometimes removes +

You might remember that make(1) sometimes removes ${.TARGET} in case of error, but this only happens when it is interrupted, for example by pressing ^C. This does not happen - when one of the commands fails (like false(1) above).

+ when one of the commands fails (like false(1) above).

EMPTY= # empty @@ -4266,7 +4266,7 @@ the following code: $ “packing list”, i.e. a list of files that belong to the package (relative to the ${PREFIX} directory it's been installed in) plus some additional statements - - see the pkg_create(1) man page for a full list. + - see the pkg_create(1) man page for a full list. This chapter addresses some issues that need attention when dealing with the PLIST file (or files, see below!). @@ -4280,7 +4280,7 @@ the following code: $


@@ -4410,7 +4410,7 @@ adding the RCS ID the space should be om
 To use one or more files as source for the PLIST used
     in generating the binary package, set the variable
     PLIST_SRC to the names of that file(s).
-    The files are later concatenated using cat(1), and the order of things is
+    The files are later concatenated using cat(1), and the order of things is
     important. The default for PLIST_SRC is
     ${PKGDIR}/PLIST.
 
@@ -5497,7 +5497,7 @@ options are supported by the package, an
 if needed.
 
 PKG_OPTIONS_VAR is the name of the
-make(1) variable that the user can set to override the default
+make(1) variable that the user can set to override the default
 options.  It should be set to
 PKG_OPTIONS.pkgbase. Do not set it to
 PKG_OPTIONS.${PKGBASE}, since PKGBASE is not defined
@@ -5714,36 +5714,8 @@ details.
 
X11-based packages using imake must set
 	USE_IMAKE to be installed correctly under
 	LOCALBASE.
-
-To determine the prefix of an
-	installed package, the EVAL_PREFIX
-	definition can be used. It takes pairs in the format
-	“DIRNAME=<package>”, and the make(1)
-	variable DIRNAME will be set to the prefix
-	of the installed package <package>, or
-	“${PREFIX}” if the package is not
-	installed.
-This is best illustrated by example.
-The following lines are taken from
-	pkgsrc/wm/scwm/Makefile:
--EVAL_PREFIX+=           GTKDIR=gtk+
-CONFIGURE_ARGS+=        --with-guile-prefix=${LOCALBASE:Q}
-CONFIGURE_ARGS+=        --with-gtk-prefix=${GTKDIR:Q}
-CONFIGURE_ARGS+=        --enable-multibyte
-
-Specific defaults can be defined for the packages
-	evaluated using EVAL_PREFIX, by using a
-	definition of the form:
--GTKDIR_DEFAULT= ${LOCALBASE}
-
-where GTKDIR corresponds
-	to the first definition in
-	the EVAL_PREFIX pair.
-
 Within ${PREFIX}, packages should
-	install files according to hier(7), with the exception that
+	install files according to hier(7), with the exception that
 	manual pages go into ${PREFIX}/man, not
 	${PREFIX}/share/man.
 
@@ -6024,9 +5996,9 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
     .gz are uncompressed before they are
     applied, files ending in .orig or
     .rej are ignored. Any special options to
-    patch(1) can be handed in
+    patch(1) can be handed in
     PATCH_DIST_ARGS.  See Section 11.3, “patches/*” for more details.
-By default patch(1) is given special args to make
+
By default patch(1) is given special args to make
     it fail if the patches apply with some lines of fuzz. Please
     fix (regen) the patches so that they apply cleanly. The
     rationale behind this is that patches that don't apply cleanly
@@ -6205,7 +6177,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
     defined.
 In the install phase, the following
     variables are useful. They are all variations of the
-    install(1) command that have the owner, group and
+    install(1) command that have the owner, group and
     permissions preset. INSTALL is the plain
     install command. The specialized variants, together with their
     intended use, are:
@@ -6251,7 +6223,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 Some other variables are:
 
 INSTALL_UNSTRIPPED
-If set to yes, do not run strip(1)
+
If set to yes, do not run strip(1)
       when installing binaries. Any debugging sections and symbols present in
       binaries will be preserved.
       
@@ -6328,13 +6300,13 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 
 deinstall
 
-This target does a pkg_delete(1) in the
+
This target does a pkg_delete(1) in the
 	  current directory, effectively de-installing the
 	  package. The following variables can be used to tune the
 	  behaviour:
 
 PKG_VERBOSE
-Add a "-v" to the pkg_delete(1) command.
+Add a "-v" to the pkg_delete(1) command.
 DEINSTALLDEPENDS
 Remove all packages that require (depend on)
 		the given package.  This can be used to remove any
@@ -6343,7 +6315,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 		DEINSTALLDEPENDS=1 is done in
 		pkgsrc/x11/kde, this is
 		likely to remove whole KDE. Works by adding
-		“-R” to the pkg_delete(1)
+		“-R” to the pkg_delete(1)
 		command line.
 
 
@@ -6495,7 +6467,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 	  recommended for advanced users.
 
 info
-This target invokes pkg_info(1) for the current
+
This target invokes pkg_info(1) for the current
 	  package. You can use this to check which version of a
 	  package is installed.
 index
@@ -6611,7 +6583,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 	  PLIST. On upgrades, it's useful to
 	  diff the output of this command against an already
 	  existing PLIST file.
-If the package installs files via tar(1) or
+
If the package installs files via tar(1) or
 	  other methods that don't update file access times, be
 	  sure to add these files manually to your
 	  PLIST, as the “find
@@ -6638,12 +6610,12 @@ builds)).
 

 Used during bulk-installs to install required
 	  packages. If an up-to-date binary package is available,
-	  it will be installed via pkg_add(1). If not,
+	  it will be installed via pkg_add(1). If not,
 	  make bulk-package will be executed,
 	  but the installed binary won't be removed.
 A binary package is considered
 	  “up-to-date” to be installed via
-	  pkg_add(1) if:
+	  pkg_add(1) if:
 
 None of the package's files
 	      (Makefile, ...) were modified
@@ -6828,7 +6800,7 @@ TOOLS_PLATFORM.true?=           true    
     variables in the file pointed to by MAKECONF,
     which is mk.conf by default. When you
     want to use those variables in the preprocessor directives of
-    make(1) (for example .if or
+    make(1) (for example .if or
     .for), you need to include the file
     ../../mk/bsd.prefs.mk before, which in turn
     loads the user preferences.
@@ -7068,7 +7040,7 @@ ACCEPTABLE_LICENSES+=xv-license
 
 Please note that the “pre-req-package-name”
     may include any of the wildcard version numbers recognized by
-    pkg_info(1).
+    pkg_info(1).
 
 
 If your package needs another package's binaries or
@@ -7222,7 +7194,7 @@ CONFLICTS=      bar-[0-9]*
     be set in the package Makefile. This will be carried into any
     binary package that is made from this pkgsrc entry. A
     “preserved” package will
-    not be deleted using pkg_delete(1) unless the
+    not be deleted using pkg_delete(1) unless the
     “-f” option is used.
 
 
@@ -7355,7 +7327,7 @@ SUBST_SED.fix-paths+=           -e 's,"/
     substitution will take place. The patterns are interpreted
     relatively to the WRKSRC directory.
 SUBST_SED.* is a list of arguments to
-    sed(1) that specify the actual substitution. Every sed
+    sed(1) that specify the actual substitution. Every sed
     command should be prefixed with -e, so that
     all SUBST blocks look uniform.
 There are some more variables, but they are so seldomly
@@ -7554,7 +7526,7 @@ dynamic linker chooses the library with 
 
 
 When linking shared object (.so)
-	files, i.e. files that are loaded via dlopen(3), NOT
+	files, i.e. files that are loaded via dlopen(3), NOT
 	shared libraries, use “-module
 	-avoid-version” to prevent them getting version
 	tacked on.
@@ -7564,7 +7536,7 @@ dynamic linker chooses the library with 
 

 When linking programs that depend on these libraries
 	before they are installed, preface
-	the cc(1) or ld(1) line with “${LIBTOOL}
+	the cc(1) or ld(1) line with “${LIBTOOL}
 	--mode=link”, and it will find the correct
 	libraries (static or shared), but please be aware that
 	libtool will not allow you to specify a relative path in
@@ -7581,8 +7553,8 @@ ${LIBTOOL} --mode=link ${CC} -o and it will do the right thing with the libraries.

 

 
-When installing libraries, preface the install(1)
-	or cp(1) command with “${LIBTOOL}
+
When installing libraries, preface the install(1)
+	or cp(1) command with “${LIBTOOL}
 	--mode=install”, and change the library name to
 	.la. e.g.
 @@ -7590,7 +7562,7 @@ ${LIBTOOL} --mode=install ${BSD_INSTALL_
 
 This will install the static .a,
 	shared library, any needed symlinks, and run
-	ldconfig(8).
+	ldconfig(8).
 
 In your PLIST, include only
 	the .la
@@ -8642,10 +8614,10 @@ builds).
 21.2. Submitting source packages (for non-NetBSD-developers)

First, check that your package is complete, compiles and runs well; see Chapter 20, Debugging and the rest of this - document. Next, generate an uuencoded gzipped tar(1) + document. Next, generate an uuencoded gzipped tar(1) archive that contains all files that make up the package. Finally, send this package to the pkgsrc bug tracking system, - either with the send-pr(1) command, or if you don't have + either with the send-pr(1) command, or if you don't have that, go to the web page http://www.NetBSD.org/support/send-pr.html, which contains some instructions and a link to a form where you @@ -8801,7 +8773,7 @@ instead of “PREV_PKGPATH to the previous category/package pathname. The PREV_PKGPATH can be used by tools for doing an update using pkgsrc building; for example, it can -search the pkg_summary(5) database for PREV_PKGPATH +search the pkg_summary(5) database for PREV_PKGPATH (if no SUPERSEDES) and then use the corresponding new PKGPATH for that moved package. Note that it may have multiple matches, so the tool should also check on the @@ -8837,7 +8809,7 @@ place.
and if you still don't have the answer, ask on the pkgsrc-users mailing list.

-
+

22.1. What is the difference between MAKEFLAGS, .MAKEFLAGS and MAKE_FLAGS? @@ -8882,7 +8854,7 @@ do? -
22.1.
+
22.1.

What is the difference between MAKEFLAGS, .MAKEFLAGS and @@ -8891,14 +8863,14 @@ do?
MAKEFLAGS are the flags passed - to the pkgsrc-internal invocations of make(1), while + to the pkgsrc-internal invocations of make(1), while MAKE_FLAGS are the flags that are passed to the MAKE_PROGRAM when building the package. [FIXME: What is .MAKEFLAGS for?]
-
22.2.
+
22.2.

What is the difference between MAKE, GMAKE and @@ -8907,7 +8879,7 @@ do?
MAKE is the path to the - make(1) program that is used in the pkgsrc + make(1) program that is used in the pkgsrc infrastructure. GMAKE is the path to GNU Make, but you need to say USE_TOOLS+=gmake to use that. MAKE_PROGRAM is the path to the @@ -8916,7 +8888,7 @@ do? -
22.3.
+
22.3.

What is the difference between CC, PKG_CC and @@ -8934,7 +8906,7 @@ do? -
22.4.
+
22.4.

What is the difference between BUILDLINK_LDFLAGS, @@ -8947,7 +8919,7 @@ do? -
22.5.
+
22.5.

Why does make show-var VARNAME=BUILDLINK_PREFIX.foo @@ -8963,7 +8935,7 @@ do? -
22.6.
+
22.6.

What does ${MASTER_SITE_SOURCEFORGE:=package/} mean? I @@ -8976,7 +8948,7 @@ do? assignment operator, although it looks like it. Instead, it is a degenerate form of ${LIST:old_string=new_string}, - which is documented in the make(1) man page and which is + which is documented in the make(1) man page and which is commonly used in the form ${SRCS:.c=.o}. In the case of MASTER_SITE_*, old_string is the empty string and @@ -8987,7 +8959,7 @@ do? -
22.7.
+
22.7.

Which mailing lists are there for package developers?
@@ -9005,14 +8977,14 @@ do? etc.

pkgsrc-bugs

All bug reports in category "pkg" sent with - send-pr(1) appear here. Please do not report your bugs here + send-pr(1) appear here. Please do not report your bugs here directly; use one of the other mailing lists.

-
22.8.
+
22.8.

Where is the pkgsrc documentation?
@@ -9060,7 +9032,7 @@ do? -
22.9.
+
22.9.

I have a little time to kill. What shall I do?
@@ -9921,7 +9893,7 @@ INFO_FILES= yes A.1.2. DESCR

GNU version of yacc. Can make re-entrant parsers, and numerous other -improvements. Why you would want this when Berkeley yacc(1) is part +improvements. Why you would want this when Berkeley yacc(1) is part of the NetBSD source tree is beyond me.

9.12. Using 'sudo' with pkgsrc