 @@ -1,14 +1,14 @@
-<!-- $NetBSD: configuring.xml,v 1.32 2009/01/28 23:31:39 abs Exp $ -->
+<!-- $NetBSD: configuring.xml,v 1.33 2009/03/05 13:08:02 imil Exp $ -->
 <chapter id="configuring">
   <title>Configuring pkgsrc</title>
 <anchor id="mk.conf" />
 <para>The whole pkgsrc system is configured in a single file, usually
 called <filename>mk.conf</filename>. In which directory pkgsrc looks for
 that file depends on the installation. On NetBSD, when you use
 &man.make.1; from the base system, it is in the directory
 <filename>/etc/</filename>. In all other cases the default location is
 <literal>${PREFIX}/etc/</literal>, depending on where you told the
 bootstrap program to install the binary packages.</para>
 @@ -153,26 +153,65 @@ works.
     support. <varname>USE_DESTDIR=full</varname> needs <filename
     role="pkg">pkgtools/pkg_install</filename> version 20070802 (or
     newer). It might become the default DESTDIR support later.</para>
     <para>DESTDIR support changes the behaviour of various targets
     slightly. To install a package after building it, use
     <literal>package-install</literal>. <literal>package</literal> and
     <literal>install</literal> don't do that any
     longer. <literal>package-install</literal> can be used as
     <varname>DEPENDS_TARGET</varname>.  <literal>bin-install</literal>
     will ask for the root password to install the package and fail,
     <literal>package-install</literal> will ask again.</para>
     <para>With basic DESTDIR support, <userinput>make
     clean</userinput> needs to be run as root.</para>
     <para>Considering the <filename>foo/bar</filename> package,
     DESTDIR full support can be tested using the following commands
 <programlisting>
 &uprompt; id
 uid=1000(myusername) gid=100(users) groups=100(users),0(wheel)
 &uprompt; mkdir $HOME/packages
 &uprompt; cd $PKGSRCDIR/foo/bar
 </programlisting>
     Verify <varname>DESTDIR</varname> full support, no root privileges
     should be needed
 <programlisting>
 &uprompt; make USE_DESTDIR=full install
 </programlisting>
     Create a package without root privileges
 <programlisting>
 &uprompt; make USE_DESTDIR=full PACKAGES=$HOME/packages package
 </programlisting>
     For the following command, you must be able to gain root
     privileges using &man.su.1;
 <programlisting>
 &uprompt; make USE_DESTDIR=full PACKAGES=$HOME/packages package-install
 </programlisting>
     Then, as a simple user
 <programlisting>
 &uprompt; make clean
 </programlisting>
     </para>
   </sect1>
 <sect1 id="conf.compiler">
 <title>Selecting and configuring the compiler</title>
   <sect2 id="selecting-the-compiler">
     <title>Selecting the compiler</title>
     <para>By default, pkgsrc will use GCC to build packages.  This may be
     overridden by setting the following variables in /etc/mk.conf:</para>
     <variablelist>
       <varlistentry>

 @@ -1,14 +1,14 @@
-<!-- $NetBSD: creating.xml,v 1.7 2007/06/01 11:07:24 rillig Exp $ -->
+<!-- $NetBSD: creating.xml,v 1.8 2009/03/05 13:08:02 imil Exp $ -->
 <chapter id="creating">
 <title>Creating a new pkgsrc package from scratch</title>
 <para>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.</para>
 <procedure>
 <step><para>First, install the packages <filename
 role="pkg">pkgtools/url2pkg</filename> and <filename
 @@ -117,26 +117,79 @@ package from the set of installed files.
 <command>url2pkg</command>, including dependencies.</para>
 </sect2>
 <sect2 id="creating.kde-app">
 <title>KDE applications</title>
 <para>KDE applications should always include
 <filename>meta-pkgs/kde3/kde3.mk</filename>, which contains numerous
 settings that are typical of KDE packages.</para>
 </sect2>
 <sect2 id="creating.python-module">
 <title>Python modules and programs</title>
 <para>Python modules and programs packages are easily created using a
 set of predefined variables.</para>
 <para>Most Python packages use either <quote>distutils</quote> or
 easy-setup (<quote>eggs</quote>).
 If the software uses <quote>distutils</quote>, set the
 <varname>PYDISTUTILSPKG</varname> variable to <quote>yes</quote> so
 pkgsrc will make use of this framework.
 <quote>distutils</quote> uses a script called <filename>setup.py</filename>,
 if the <quote>distutils</quote> driver is not called
 <filename>setup.py</filename>, set the <varname>PYSETUP</varname> variable
 to the name of the script.</para>
 <para>
 If the default Python versions are not supported by the software, set the
 <varname>PYTHON_VERSIONS_ACCEPTED</varname> variable to the Python versions
 the software is known to work with, from the most recent to the older
 one, e.g.
 <programlisting>
 PYTHON_VERSIONS_ACCEPTED=       25 24 23
 </programlisting></para>
 <para>
 If the packaged software is a Python module, include
 <quote><filename>../../lang/python/extension.mk</filename></quote>.
 In this case, the package directory should be called
 <quote>py-software</quote> and <varname>PKGNAME</varname> should be set to
 <quote>${PYPKGPREFIX}-${DISTNAME}</quote>, e.g.
 <programlisting>
 DISTNAME=   foopymodule-1.2.10
 PKGNAME=    ${PYPKGPREFIX}-${DISTNAME}
 </programlisting></para>
 <para>If it is an application, also include
 <quote><filename>../../lang/python/application.mk</filename></quote>
 before <quote>extension.mk</quote>.</para>
 <para>If the packaged software, either it is an application or a module, is
 egg-aware, you only need to include
 <quote><filename>../../lang/python/egg.mk</filename></quote>.</para>
 <para>In order to correctly set the path to the Python interpreter, use the
 <varname>REPLACE_PYTHON</varname> variable and set it to the list of files
 that must be corrected. For example :
 <programlisting>
 REPLACE_PYTHON=   ${WRKSRC}/*.py
 </programlisting></para>
 </sect2>
 </sect1>
 <sect1 id="creating.examples">
 <title>Examples</title>
 <sect2 id="creating.nvu">
 <title>How the www/nvu package came into pkgsrc</title>
 <sect3 id="creating.nvu.init">
 <title>The initial package</title>
 <para>Looking at the file <filename>pkgsrc/doc/TODO</filename>, I saw
 that the <quote>nvu</quote> package has not yet been imported into