 @@ -177,26 +177,27 @@ builds)
 <dt><span class="sect1"><a href="#ufaq-cflags">9.15. Why do some packages ignore my CFLAGS?</a></span></dt>
 <dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build.  What shall I do?</a></span></dt>
 <dt><span class="sect1"><a href="#faq.rcs-conflicts">9.17. What does Makefile appears to contain unresolved cvs/rcs/??? merge conflicts mean?</a></span></dt>
 </dl></dd>
 </dl></dd>
 <dt><span class="part"><a href="#developers-guide">II. The pkgsrc developer's guide</a></span></dt>
 <dd><dl>
 <dt><span class="chapter"><a href="#creating">10. Creating a new pkgsrc package from scratch</a></span></dt>
 <dd><dl>
 <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
 <dd><dl>
 <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
 <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE applications</a></span></dt>
 <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
 </dl></dd>
 <dt><span class="chapter"><a href="#components">11. Package components - files, directories and contents</a></span></dt>
 <dd><dl>
 <dt><span class="sect1"><a href="#components.Makefile">11.1. Makefile</a></span></dt>
 <dt><span class="sect1"><a href="#components.distinfo">11.2. distinfo</a></span></dt>
 <dt><span class="sect1"><a href="#components.patches">11.3. patches/*</a></span></dt>
 <dd><dl>
 <dt><span class="sect2"><a href="#components.patch.structure">11.3.1. Structure of a single patch file</a></span></dt>
 <dt><span class="sect2"><a href="#components.patches.caveats">11.3.2. Creating patch files</a></span></dt>
 <dt><span class="sect2"><a href="#components.patches.sources">11.3.3. Sources where the patch files come from</a></span></dt>
 @@ -2224,26 +2225,73 @@ works.
     get the full support with fallback to basic
     support. <code class="varname">USE_DESTDIR=full</code> needs <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html" target="_top"><code class="filename">pkgtools/pkg_install</code></a> version 20070802 (or
     newer). It might become the default DESTDIR support later.</p>
 <p>DESTDIR support changes the behaviour of various targets
     slightly. To install a package after building it, use
     <code class="literal">package-install</code>. <code class="literal">package</code> and
     <code class="literal">install</code> don't do that any
     longer. <code class="literal">package-install</code> can be used as
     <code class="varname">DEPENDS_TARGET</code>.  <code class="literal">bin-install</code>
     will ask for the root password to install the package and fail,
     <code class="literal">package-install</code> will ask again.</p>
 <p>With basic DESTDIR support, <strong class="userinput"><code>make
     clean</code></strong> needs to be run as root.</p>
 <p>Considering the <code class="filename">foo/bar</code> package,
     DESTDIR full support can be tested using the following commands
 </p>
 <pre class="programlisting">
 <code class="prompt">$</code> id
 uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
 <code class="prompt">$</code> mkdir $HOME/packages
 <code class="prompt">$</code> cd $PKGSRCDIR/foo/bar
 </pre>
 <p>
     Verify <code class="varname">DESTDIR</code> full support, no root privileges
     should be needed
 </p>
 <pre class="programlisting">
 <code class="prompt">$</code> make USE_DESTDIR=full install
 </pre>
 <p>
     Create a package without root privileges
 </p>
 <pre class="programlisting">
 <code class="prompt">$</code> make USE_DESTDIR=full PACKAGES=$HOME/packages package
 </pre>
 <p>
     For the following command, you must be able to gain root
     privileges using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
 </p>
 <pre class="programlisting">
 <code class="prompt">$</code> make USE_DESTDIR=full PACKAGES=$HOME/packages package-install
 </pre>
 <p>
     Then, as a simple user
 </p>
 <pre class="programlisting">
 <code class="prompt">$</code> make clean
 </pre>
 <p>
     </p>
 </div>
 <div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="conf.compiler"></a>5.4.�Selecting and configuring the compiler</h2></div></div></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="selecting-the-compiler"></a>5.4.1.�Selecting the compiler</h3></div></div></div>
 <p>By default, pkgsrc will use GCC to build packages.  This may be
     overridden by setting the following variables in /etc/mk.conf:</p>
 <div class="variablelist"><dl>
 <dt><span class="term"><code class="varname">PKGSRC_COMPILER</code>:</span></dt>
 <dd>
 <p>This is a list of values specifying the chain of
 @@ -3617,26 +3665,27 @@ anymore, you can remove that file and ru
 <p>This part of the book deals with creating and
 	modifying packages. It starts with a &#8220;<span class="quote">HOWTO</span>&#8221;-like
 	guide on creating a new package. The remaining chapters are more
 	like a reference manual for pkgsrc.</p>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
 <dt><span class="chapter"><a href="#creating">10. Creating a new pkgsrc package from scratch</a></span></dt>
 <dd><dl>
 <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
 <dd><dl>
 <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
 <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE applications</a></span></dt>
 <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
 </dl></dd>
 <dt><span class="chapter"><a href="#components">11. Package components - files, directories and contents</a></span></dt>
 <dd><dl>
 <dt><span class="sect1"><a href="#components.Makefile">11.1. Makefile</a></span></dt>
 <dt><span class="sect1"><a href="#components.distinfo">11.2. distinfo</a></span></dt>
 <dt><span class="sect1"><a href="#components.patches">11.3. patches/*</a></span></dt>
 <dd><dl>
 <dt><span class="sect2"><a href="#components.patch.structure">11.3.1. Structure of a single patch file</a></span></dt>
 <dt><span class="sect2"><a href="#components.patches.caveats">11.3.2. Creating patch files</a></span></dt>
 <dt><span class="sect2"><a href="#components.patches.sources">11.3.3. Sources where the patch files come from</a></span></dt>
 @@ -3841,26 +3890,27 @@ anymore, you can remove that file and ru
 </dl>
 </div>
 </div>
 <div class="chapter" lang="en">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="creating"></a>Chapter�10.�Creating a new pkgsrc package from scratch</h2></div></div></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
 <dt><span class="sect1"><a href="#creating.common">10.1. Common types of packages</a></span></dt>
 <dd><dl>
 <dt><span class="sect2"><a href="#creating.perl-module">10.1.1. Perl modules</a></span></dt>
 <dt><span class="sect2"><a href="#creating.kde-app">10.1.2. KDE applications</a></span></dt>
 <dt><span class="sect2"><a href="#creating.python-module">10.1.3. Python modules and programs</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="#creating.examples">10.2. Examples</a></span></dt>
 <dd><dl><dt><span class="sect2"><a href="#creating.nvu">10.2.1. How the www/nvu package came into pkgsrc</a></span></dt></dl></dd>
 </dl>
 </div>
 <p>When you find a package that is not yet in pkgsrc, you
 most likely have a URL from where you can download the source
 code. Starting with this URL, creating a package involves only a
 few steps.</p>
 <div class="procedure"><ol type="1">
 <li><p>First, install the packages <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html" target="_top"><code class="filename">pkgtools/url2pkg</code></a> and <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html" target="_top"><code class="filename">pkgtools/pkglint</code></a>.</p></li>
 <li><p>Then, choose one of the top-level directories as the
 category in which you want to place your package. You can also create a
 @@ -3945,26 +3995,74 @@ package from the set of installed files.
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="creating.perl-module"></a>10.1.1.�Perl modules</h3></div></div></div>
 <p>Simple Perl modules are handled automatically by
 <span class="command"><strong>url2pkg</strong></span>, including dependencies.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="creating.kde-app"></a>10.1.2.�KDE applications</h3></div></div></div>
 <p>KDE applications should always include
 <code class="filename">meta-pkgs/kde3/kde3.mk</code>, which contains numerous
 settings that are typical of KDE packages.</p>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="creating.python-module"></a>10.1.3.�Python modules and programs</h3></div></div></div>
 <p>Python modules and programs packages are easily created using a
 set of predefined variables.</p>
 <p>Most Python packages use either &#8220;<span class="quote">distutils</span>&#8221; or
 easy-setup (&#8220;<span class="quote">eggs</span>&#8221;).
 If the software uses &#8220;<span class="quote">distutils</span>&#8221;, set the
 <code class="varname">PYDISTUTILSPKG</code> variable to &#8220;<span class="quote">yes</span>&#8221; so
 pkgsrc will make use of this framework.
 &#8220;<span class="quote">distutils</span>&#8221; uses a script called <code class="filename">setup.py</code>,
 if the &#8220;<span class="quote">distutils</span>&#8221; driver is not called
 <code class="filename">setup.py</code>, set the <code class="varname">PYSETUP</code> variable
 to the name of the script.</p>
 <p>
 If the default Python versions are not supported by the software, set the
 <code class="varname">PYTHON_VERSIONS_ACCEPTED</code> variable to the Python versions
 the software is known to work with, from the most recent to the older
 one, e.g.
 </p>
 <pre class="programlisting">
 PYTHON_VERSIONS_ACCEPTED=       25 24 23
 </pre>
 <p>
 If the packaged software is a Python module, include
 &#8220;<span class="quote"><code class="filename">../../lang/python/extension.mk</code></span>&#8221;.
 In this case, the package directory should be called
 &#8220;<span class="quote">py-software</span>&#8221; and <code class="varname">PKGNAME</code> should be set to
 &#8220;<span class="quote">${PYPKGPREFIX}-${DISTNAME}</span>&#8221;, e.g.
 </p>
 <pre class="programlisting">
 DISTNAME=   foopymodule-1.2.10
 PKGNAME=    ${PYPKGPREFIX}-${DISTNAME}
 </pre>
 <p>If it is an application, also include
 &#8220;<span class="quote"><code class="filename">../../lang/python/application.mk</code></span>&#8221;
 before &#8220;<span class="quote">extension.mk</span>&#8221;.</p>
 <p>If the packaged software, either it is an application or a module, is
 egg-aware, you only need to include
 &#8220;<span class="quote"><code class="filename">../../lang/python/egg.mk</code></span>&#8221;.</p>
 <p>In order to correctly set the path to the Python interpreter, use the
 <code class="varname">REPLACE_PYTHON</code> variable and set it to the list of files
 that must be corrected. For example :
 </p>
 <pre class="programlisting">
 REPLACE_PYTHON=   ${WRKSRC}/*.py
 </pre>
 </div>
 </div>
 <div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="creating.examples"></a>10.2.�Examples</h2></div></div></div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="creating.nvu"></a>10.2.1.�How the www/nvu package came into pkgsrc</h3></div></div></div>
 <div class="sect3" lang="en">
 <div class="titlepage"><div><div><h4 class="title">
 <a name="creating.nvu.init"></a>10.2.1.1.�The initial package</h4></div></div></div>
 <p>Looking at the file <code class="filename">pkgsrc/doc/TODO</code>, I saw
 that the &#8220;<span class="quote">nvu</span>&#8221; package has not yet been imported into
 pkgsrc. As the description says it has to do with the web, the obvious
 @@ -7526,48 +7624,48 @@ TOOLS_PLATFORM.true?=           true
 <dt>18.4.2. <a href="#tools.listall">How do I get a list of all available
 	tools?</a>
 </dt>
 <dt>18.4.3. <a href="#tools.used">How can I get a list of all the tools that a
 	package is using while being built? I want to know whether it
 	uses sed or not.</a>
 </dt>
 </dl>
 <table border="0" summary="Q and A Set">
 <col align="left" width="1%">
 <tbody>
 <tr class="question">
 <td align="left" valign="top">
-<a name="tools.new"></a><a name="id9503691"></a><p><b>18.4.1.</b></p>
+<a name="tools.new"></a><a name="id52054999"></a><p><b>18.4.1.</b></p>
 </td>
 <td align="left" valign="top"><p>How do I add a new tool?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>TODO</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="tools.listall"></a><a name="id9503700"></a><p><b>18.4.2.</b></p>
+<a name="tools.listall"></a><a name="id52055008"></a><p><b>18.4.2.</b></p>
 </td>
 <td align="left" valign="top"><p>How do I get a list of all available
 	tools?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>TODO</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="tools.used"></a><a name="id9503708"></a><p><b>18.4.3.</b></p>
+<a name="tools.used"></a><a name="id52055016"></a><p><b>18.4.3.</b></p>
 </td>
 <td align="left" valign="top"><p>How can I get a list of all the tools that a
 	package is using while being built? I want to know whether it
 	uses sed or not.</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>Currently, you can't. (TODO: But I want to be able
 	to do it.)</p></td>
 </tr>
 </tbody>
 </table>
 </div>
 @@ -8813,30 +8911,27 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2
     install as non-root user (&#8220;<span class="quote">user-destdir</span>&#8221;).</p>
 <div class="itemizedlist"><ul type="disc">
 <li><p><code class="varname">PKG_DESTDIR_SUPPORT</code> has to be
       set to &#8220;<span class="quote">destdir</span>&#8221; or &#8220;<span class="quote">user-destdir</span>&#8221;. If
       bsd.prefs.mk is included in the Makefile,
       <code class="varname">PKG_DESTDIR_SUPPORT</code> needs to be set before
       the inclusion.</p></li>
 <li><p>All installation operations have to be prefixed with
       <code class="filename">${DESTDIR}</code>.</p></li>
 <li><p>automake gets this DESTDIR mostly right
       automatically. Many manual rules and pre/post-install often are
       incorrect; fix them.</p></li>
 <li><p>If files are installed with special owner/group
-      either use @owner/@group in the <code class="filename">PLIST</code>
+      use <code class="varname">SPECIAL_PERMS</code>.</p></li>
       (preferred) or use <code class="varname">SPECIAL_PERMS</code>
       (discouraged). Note that @owner/@group are sticky during
       install, keep this in mind.</p></li>
 <li><p>In general, packages should support
       <code class="varname">UNPRIVILEGED</code> to be able to use
       DESTDIR.</p></li>
 </ul></div>
 </div>
 <div class="sect2" lang="en">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="hardcoded-paths"></a>19.6.5.�Packages with hardcoded paths to other interpreters</h3></div></div></div>
 <p>Your package may also contain scripts with hardcoded paths to
       other interpreters besides (or as well as) perl.  To correct the
       full pathname to the script interpreter, you need to set the
       following definitions in your <code class="filename">Makefile</code> (we
     shall use <span class="command"><strong>tclsh</strong></span> in this example):</p>
 @@ -9561,157 +9656,157 @@ place.
 </dt>
 <dt>22.8. <a href="#devfaq.documentation">Where is the pkgsrc
 	documentation?</a>
 </dt>
 <dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill.  What shall I
 do?</a>
 </dt>
 </dl>
 <table border="0" summary="Q and A Set">
 <col align="left" width="1%">
 <tbody>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.makeflags"></a><a name="id9508238"></a><p><b>22.1.</b></p>
+<a name="devfaq.makeflags"></a><a name="id52059900"></a><p><b>22.1.</b></p>
 </td>
 <td align="left" valign="top"><p>What is the difference between
 	<code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
 	<code class="varname">MAKE_FLAGS</code>?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed
 	to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while
 	<code class="varname">MAKE_FLAGS</code> are the flags that are passed to
 	the <code class="varname">MAKE_PROGRAM</code> when building the
 	package. [FIXME: What is .MAKEFLAGS for?]</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.make"></a><a name="id9508273"></a><p><b>22.2.</b></p>
+<a name="devfaq.make"></a><a name="id52059936"></a><p><b>22.2.</b></p>
 </td>
 <td align="left" valign="top"><p>What is the difference between
 	<code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
 	<code class="varname">MAKE_PROGRAM</code>?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the
 	<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
 	infrastructure. <code class="varname">GMAKE</code> is the path to GNU
 	Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to
 	use that. <code class="varname">MAKE_PROGRAM</code> is the path to the
 	Make program that is used for building the
 	package.</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.cc"></a><a name="id9508309"></a><p><b>22.3.</b></p>
+<a name="devfaq.cc"></a><a name="id52059974"></a><p><b>22.3.</b></p>
 </td>
 <td align="left" valign="top"><p>What is the difference between
 	<code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
 	<code class="varname">PKGSRC_COMPILER</code>?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C
 	compiler, which can be configured by the pkgsrc user.
 	<code class="varname">PKG_CC</code> is the path to the compiler wrapper.
 	<code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a
 	path to a compiler, but the type of compiler that should be
 	used. See <code class="filename">mk/compiler.mk</code> for more
 	information about the latter variable.</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.bl3flags"></a><a name="id9508344"></a><p><b>22.4.</b></p>
+<a name="devfaq.bl3flags"></a><a name="id52060009"></a><p><b>22.4.</b></p>
 </td>
 <td align="left" valign="top"><p>What is the difference between
 	<code class="varname">BUILDLINK_LDFLAGS</code>,
 	<code class="varname">BUILDLINK_LDADD</code> and
 	<code class="varname">BUILDLINK_LIBS</code>?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>[FIXME]</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.bl3prefix"></a><a name="id9508362"></a><p><b>22.5.</b></p>
+<a name="devfaq.bl3prefix"></a><a name="id52060097"></a><p><b>22.5.</b></p>
 </td>
 <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
 	VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
 	say it's empty?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>For optimization reasons, some variables are only
 	available in the &#8220;<span class="quote">wrapper</span>&#8221; phase and later. To
 	&#8220;<span class="quote">simulate</span>&#8221; the wrapper phase, append
 	<span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
 	command.</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.master_sites"></a><a name="id9508389"></a><p><b>22.6.</b></p>
+<a name="devfaq.master_sites"></a><a name="id52060122"></a><p><b>22.6.</b></p>
 </td>
 <td align="left" valign="top"><p>What does
 	<code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
 	don't understand the <code class="literal">:=</code> inside
 	it.</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><p>The <code class="literal">:=</code> is not really an
 	assignment operator, like you might expect at first sight.
 	Instead, it is a degenerate form of
 	<code class="literal">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
 	which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which you
 	may have seen as in <code class="literal">${SRCS:.c=.o}</code>. In the
 	case of <code class="varname">MASTER_SITE_*</code>,
 	<em class="replaceable"><code>old_string</code></em> is the empty string and
 	<em class="replaceable"><code>new_string</code></em> is
 	<code class="literal">package/</code>. That's where the
 	<code class="literal">:</code> and the <code class="literal">=</code> fall
 	together.</p></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.mailinglists"></a><a name="id9508456"></a><p><b>22.7.</b></p>
+<a name="devfaq.mailinglists"></a><a name="id52060325"></a><p><b>22.7.</b></p>
 </td>
 <td align="left" valign="top"><p>Which mailing lists are there for package
 	developers?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top"><div class="variablelist"><dl>
 <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt>
 <dd><p>This is a list for technical discussions related
 	to pkgsrc development, e.g. soliciting feedback for changes to
 	pkgsrc infrastructure, proposed new features, questions related
 	to porting pkgsrc to a new platform, advice for maintaining a
 	package, patches that affect many packages, help requests moved
 	from pkgsrc-users when an infrastructure bug is found,
 	etc.</p></dd>
 <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt>
 <dd><p>All bug reports in category "pkg" sent with
 	<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here
 	directly; use one of the other mailing
 	lists.</p></dd>
 </dl></div></td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.documentation"></a><a name="id9508487"></a><p><b>22.8.</b></p>
+<a name="devfaq.documentation"></a><a name="id52060359"></a><p><b>22.8.</b></p>
 </td>
 <td align="left" valign="top"><p>Where is the pkgsrc
 	documentation?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top">
 <p>There are many places where you can find
 	documentation about pkgsrc:</p>
 <div class="itemizedlist"><ul type="disc">
 <li><p>The pkgsrc guide (this document) is a collection
 	of chapters that explain large parts of pkgsrc, but some
 	chapters tend to be outdated. Which ones they are is hard to
 @@ -9739,27 +9834,27 @@ do?
 	documented</span>&#8221;, that is the documentation exists only in the
 	mind of the developer who wrote the code. To get this
 	information, use the <span class="command"><strong>cvs annotate</strong></span> command
 	to see who has written it and ask on the
 	<code class="literal">tech-pkg</code> mailing list, so that others can
 	find your questions later (see above). To be sure that the
 	developer in charge reads the mail, you may CC him or
 	her.</p></li>
 </ul></div>
 </td>
 </tr>
 <tr class="question">
 <td align="left" valign="top">
-<a name="devfaq.too-much-time"></a><a name="id9508541"></a><p><b>22.9.</b></p>
+<a name="devfaq.too-much-time"></a><a name="id52060413"></a><p><b>22.9.</b></p>
 </td>
 <td align="left" valign="top"><p>I have a little time to kill.  What shall I
 do?</p></td>
 </tr>
 <tr class="answer">
 <td align="left" valign="top"></td>
 <td align="left" valign="top">
 <p>This is not really an FAQ yet, but here's the answer
 anyway.</p>
 <div class="itemizedlist"><ul type="disc">
 <li><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
     <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package).  It
     will tell you about newer versions of installed packages that are

 @@ -157,26 +157,27 @@ I. The pkgsrc user's guide
 .15. Why do some packages ignore my CFLAGS?
 .16. A package does not build. What shall I do?
 .17. What does Makefile appears to contain unresolved cvs/rcs/???
             merge conflicts mean?
 II. The pkgsrc developer's guide
 . Creating a new pkgsrc package from scratch
 .1. Common types of packages
 .1.1. Perl modules
 .1.2. KDE applications
 .1.3. Python modules and programs
 .2. Examples
 .2.1. How the www/nvu package came into pkgsrc
 . Package components - files, directories and contents
 .1. Makefile
 .2. distinfo
 .3. patches/*
 .3.1. Structure of a single patch file
 .3.2. Creating patch files
 @@ -1956,26 +1957,50 @@ touched. DESTDIR support exists in two v
 To use the DESTDIR support, set either USE_DESTDIR=yes to use the basic support
 for packages that offer it or USE_DESTDIR=full to get the full support with
 fallback to basic support. USE_DESTDIR=full needs pkgtools/pkg_install version
 20070802 (or newer). It might become the default DESTDIR support later.
 DESTDIR support changes the behaviour of various targets slightly. To install a
 package after building it, use package-install. package and install don't do
 that any longer. package-install can be used as DEPENDS_TARGET. bin-install
 will ask for the root password to install the package and fail, package-install
 will ask again.
 With basic DESTDIR support, make clean needs to be run as root.
 Considering the foo/bar package, DESTDIR full support can be tested using the
 following commands
 $ id
 uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
 $ mkdir $HOME/packages
 $ cd $PKGSRCDIR/foo/bar
 Verify DESTDIR full support, no root privileges should be needed
 $ make USE_DESTDIR=full install
 Create a package without root privileges
 $ make USE_DESTDIR=full PACKAGES=$HOME/packages package
 For the following command, you must be able to gain root privileges using su(1)
 $ make USE_DESTDIR=full PACKAGES=$HOME/packages package-install
 Then, as a simple user
 $ make clean
 .4. Selecting and configuring the compiler
 .4.1. Selecting the compiler
 By default, pkgsrc will use GCC to build packages. This may be overridden by
 setting the following variables in /etc/mk.conf:
 PKGSRC_COMPILER:
     This is a list of values specifying the chain of compilers to invoke when
     building packages. Valid values are:
       * distcc: distributed C/C++ (chainable)
 @@ -3182,26 +3207,27 @@ Part II. The pkgsrc developer's guide
 This part of the book deals with creating and modifying packages. It starts
 with a "HOWTO"-like guide on creating a new package. The remaining chapters are
 more like a reference manual for pkgsrc.
 Table of Contents
 . Creating a new pkgsrc package from scratch
 .1. Common types of packages
 .1.1. Perl modules
 .1.2. KDE applications
 .1.3. Python modules and programs
 .2. Examples
 .2.1. How the www/nvu package came into pkgsrc
 . Package components - files, directories and contents
 .1. Makefile
 .2. distinfo
 .3. patches/*
 .3.1. Structure of a single patch file
 .3.2. Creating patch files
 @@ -3408,26 +3434,27 @@ Table of Contents
 .1. Meta packages
 .2. Packaging a GNOME application
 .3. Updating GNOME to a newer version
 .4. Patching guidelines
 Chapter 10. Creating a new pkgsrc package from scratch
 Table of Contents
 .1. Common types of packages
 .1.1. Perl modules
 .1.2. KDE applications
 .1.3. Python modules and programs
 .2. Examples
 .2.1. How the www/nvu package came into pkgsrc
 When you find a package that is not yet in pkgsrc, you most likely have a URL
 from where you can download the source code. Starting with this URL, creating a
 package involves only a few steps.
 . First, install the packages pkgtools/url2pkg and pkgtools/pkglint.
 . Then, choose one of the top-level directories as the category in which you
     want to place your package. You can also create a directory of your own
 @@ -3500,26 +3527,62 @@ package involves only a few steps.
 .1. Common types of packages
 .1.1. Perl modules
 Simple Perl modules are handled automatically by url2pkg, including
 dependencies.
 .1.2. KDE applications
 KDE applications should always include meta-pkgs/kde3/kde3.mk, which contains
 numerous settings that are typical of KDE packages.
 .1.3. Python modules and programs
 Python modules and programs packages are easily created using a set of
 predefined variables.
 Most Python packages use either "distutils" or easy-setup ("eggs"). If the
 software uses "distutils", set the PYDISTUTILSPKG variable to "yes" so pkgsrc
 will make use of this framework. "distutils" uses a script called setup.py, if
 the "distutils" driver is not called setup.py, set the PYSETUP variable to the
 name of the script.
 If the default Python versions are not supported by the software, set the
 PYTHON_VERSIONS_ACCEPTED variable to the Python versions the software is known
 to work with, from the most recent to the older one, e.g.
 PYTHON_VERSIONS_ACCEPTED=       25 24 23
 If the packaged software is a Python module, include "../../lang/python/
 extension.mk". In this case, the package directory should be called
 "py-software" and PKGNAME should be set to "${PYPKGPREFIX}-${DISTNAME}", e.g.
 DISTNAME=   foopymodule-1.2.10
 PKGNAME=    ${PYPKGPREFIX}-${DISTNAME}
 If it is an application, also include "../../lang/python/application.mk" before
 "extension.mk".
 If the packaged software, either it is an application or a module, is
 egg-aware, you only need to include "../../lang/python/egg.mk".
 In order to correctly set the path to the Python interpreter, use the
 REPLACE_PYTHON variable and set it to the list of files that must be corrected.
 For example :
 REPLACE_PYTHON=   ${WRKSRC}/*.py
 .2. Examples
 .2.1. How the www/nvu package came into pkgsrc
 .2.1.1. The initial package
 Looking at the file pkgsrc/doc/TODO, I saw that the "nvu" package has not yet
 been imported into pkgsrc. As the description says it has to do with the web,
 the obvious choice for the category is "www".
 $ mkdir www/nvu
 $ cd www/nvu
 @@ -7416,29 +7479,27 @@ final location of the files. Then a bina
 for installation as usual. There are two ways: Either the package must install
 as root ("destdir") or the package can install as non-root user
 ("user-destdir").
   * PKG_DESTDIR_SUPPORT has to be set to "destdir" or "user-destdir". If
     bsd.prefs.mk is included in the Makefile, PKG_DESTDIR_SUPPORT needs to be
     set before the inclusion.
   * All installation operations have to be prefixed with ${DESTDIR}.
   * automake gets this DESTDIR mostly right automatically. Many manual rules
     and pre/post-install often are incorrect; fix them.
-  * If files are installed with special owner/group either use @owner/@group in
+  * If files are installed with special owner/group use SPECIAL_PERMS.
     the PLIST (preferred) or use SPECIAL_PERMS (discouraged). Note that @owner/
     @group are sticky during install, keep this in mind.
   * In general, packages should support UNPRIVILEGED to be able to use DESTDIR.
 .6.5. Packages with hardcoded paths to other interpreters
 Your package may also contain scripts with hardcoded paths to other
 interpreters besides (or as well as) perl. To correct the full pathname to the
 script interpreter, you need to set the following definitions in your Makefile
 (we shall use tclsh in this example):
 REPLACE_INTERPRETER+=   tcl
 REPLACE.tcl.old=        .*/bin/tclsh
 REPLACE.tcl.new=        ${PREFIX}/bin/tclsh