Fri May 3 20:55:23 2013 UTC ()
regen


(asau)
diff -r1.156 -r1.157 pkgsrc/doc/pkgsrc.html
diff -r1.159 -r1.160 pkgsrc/doc/pkgsrc.txt
cvs diff -r1.156 -r1.157 pkgsrc/doc/pkgsrc.html (expand / switch to unified diff)

--- pkgsrc/doc/pkgsrc.html 2013/04/21 15:21:17 1.156
+++ pkgsrc/doc/pkgsrc.html 2013/05/03 20:55:21 1.157
@@ -54,27 +54,27 @@ @@ -54,27 +54,27 @@
54<dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt> 54<dt><span class="sect2"><a href="#intro.platforms">1.1.2. Supported platforms</a></span></dt>
55</dl></dd> 55</dl></dd>
56<dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt> 56<dt><span class="sect1"><a href="#overview">1.2. Overview</a></span></dt>
57<dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt> 57<dt><span class="sect1"><a href="#terminology">1.3. Terminology</a></span></dt>
58<dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd> 58<dd><dl><dt><span class="sect2"><a href="#term.roles">1.3.1. Roles involved in pkgsrc</a></span></dt></dl></dd>
59<dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt> 59<dt><span class="sect1"><a href="#typography">1.4. Typography</a></span></dt>
60</dl></dd> 60</dl></dd>
61<dt><span class="part"><a href="#users-guide">I. The pkgsrc user's guide</a></span></dt> 61<dt><span class="part"><a href="#users-guide">I. The pkgsrc user's guide</a></span></dt>
62<dd><dl> 62<dd><dl>
63<dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt> 63<dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
64<dd><dl> 64<dd><dl>
65<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt> 65<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
66<dd><dl> 66<dd><dl>
67<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar file</a></span></dt> 67<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
68<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt> 68<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
69</dl></dd> 69</dl></dd>
70<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt> 70<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
71<dd><dl> 71<dd><dl>
72<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt> 72<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
73<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt> 73<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
74</dl></dd> 74</dl></dd>
75</dl></dd> 75</dl></dd>
76<dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt> 76<dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt>
77<dd><dl> 77<dd><dl>
78<dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt> 78<dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt>
79<dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt> 79<dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
80<dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt> 80<dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
@@ -789,27 +789,27 @@ minutes!

 @@ -789,27 +789,27 @@ minutes!

789 shell prompt, assuming they use the C-shell or tcsh.</p> 789 shell prompt, assuming they use the C-shell or tcsh.</p>
790</div> 790</div>
791</div> 791</div>
792<div class="part"> 792<div class="part">
793<div class="titlepage"><div><div><h1 class="title"> 793<div class="titlepage"><div><div><h1 class="title">
794<a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div> 794<a name="users-guide"></a>Part I. The pkgsrc user's guide</h1></div></div></div>
795<div class="toc"> 795<div class="toc">
796<p><b>Table of Contents</b></p> 796<p><b>Table of Contents</b></p>
797<dl> 797<dl>
798<dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt> 798<dt><span class="chapter"><a href="#getting">2. Where to get pkgsrc and how to keep it up-to-date</a></span></dt>
799<dd><dl> 799<dd><dl>
800<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt> 800<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
801<dd><dl> 801<dd><dl>
802<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar file</a></span></dt> 802<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
803<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt> 803<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
804</dl></dd> 804</dl></dd>
805<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt> 805<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
806<dd><dl> 806<dd><dl>
807<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt> 807<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
808<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt> 808<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
809</dl></dd> 809</dl></dd>
810</dl></dd> 810</dl></dd>
811<dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt> 811<dt><span class="chapter"><a href="#platforms">3. Using pkgsrc on systems other than NetBSD</a></span></dt>
812<dd><dl> 812<dd><dl>
813<dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt> 813<dt><span class="sect1"><a href="#binarydist">3.1. Binary distribution</a></span></dt>
814<dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt> 814<dt><span class="sect1"><a href="#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
815<dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt> 815<dt><span class="sect1"><a href="#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
@@ -913,27 +913,27 @@ builds) @@ -913,27 +913,27 @@ builds)
913<dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build. What shall I do?</a></span></dt> 913<dt><span class="sect1"><a href="#ufaq-fail">9.16. A package does not build. What shall I do?</a></span></dt>
914<dt><span class="sect1"><a href="#faq.rcs-conflicts">9.17. What does <span class="quote">&#8220;<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>&#8221;</span> mean?</a></span></dt> 914<dt><span class="sect1"><a href="#faq.rcs-conflicts">9.17. What does <span class="quote">&#8220;<span class="quote">Makefile appears to contain unresolved cvs/rcs/??? merge conflicts</span>&#8221;</span> mean?</a></span></dt>
915</dl></dd> 915</dl></dd>
916</dl> 916</dl>
917</div> 917</div>
918<div class="chapter"> 918<div class="chapter">
919<div class="titlepage"><div><div><h2 class="title"> 919<div class="titlepage"><div><div><h2 class="title">
920<a name="getting"></a>Chapter 2. Where to get pkgsrc and how to keep it up-to-date</h2></div></div></div> 920<a name="getting"></a>Chapter 2. Where to get pkgsrc and how to keep it up-to-date</h2></div></div></div>
921<div class="toc"> 921<div class="toc">
922<p><b>Table of Contents</b></p> 922<p><b>Table of Contents</b></p>
923<dl> 923<dl>
924<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt> 924<dt><span class="sect1"><a href="#getting-first">2.1. Getting pkgsrc for the first time</a></span></dt>
925<dd><dl> 925<dd><dl>
926<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar file</a></span></dt> 926<dt><span class="sect2"><a href="#getting-via-tar">2.1.1. As tar archive</a></span></dt>
927<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt> 927<dt><span class="sect2"><a href="#getting-via-cvs">2.1.2. Via anonymous CVS</a></span></dt>
928</dl></dd> 928</dl></dd>
929<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt> 929<dt><span class="sect1"><a href="#uptodate">2.2. Keeping pkgsrc up-to-date</a></span></dt>
930<dd><dl> 930<dd><dl>
931<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt> 931<dt><span class="sect2"><a href="#uptodate-tar">2.2.1. Via tar files</a></span></dt>
932<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt> 932<dt><span class="sect2"><a href="#uptodate-cvs">2.2.2. Via CVS</a></span></dt>
933</dl></dd> 933</dl></dd>
934</dl> 934</dl>
935</div> 935</div>
936<p>Before you download and extract the files, you need to decide 936<p>Before you download and extract the files, you need to decide
937where you want to extract them. When using pkgsrc as root user, pkgsrc 937where you want to extract them. When using pkgsrc as root user, pkgsrc
938is usually installed in <code class="filename">/usr/pkgsrc</code>. You are though 938is usually installed in <code class="filename">/usr/pkgsrc</code>. You are though
939free to install the sources and binary packages wherever you want in 939free to install the sources and binary packages wherever you want in
@@ -944,44 +944,60 @@ and dashes.

 @@ -944,44 +944,60 @@ and dashes.

944<div class="sect1"> 944<div class="sect1">
945<div class="titlepage"><div><div><h2 class="title" style="clear: both"> 945<div class="titlepage"><div><div><h2 class="title" style="clear: both">
946<a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div> 946<a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div>
947<p>Before you download any pkgsrc files, you should decide 947<p>Before you download any pkgsrc files, you should decide
948 whether you want the <span class="emphasis"><em>current</em></span> branch or the 948 whether you want the <span class="emphasis"><em>current</em></span> branch or the
949 <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a 949 <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a
950 quarterly basis from the current branch and only gets modified 950 quarterly basis from the current branch and only gets modified
951 for security updates. The names of the stable branches are built 951 for security updates. The names of the stable branches are built
952 from the year and the quarter, for example 952 from the year and the quarter, for example
953 <code class="literal">2009Q1</code>.</p> 953 <code class="literal">2009Q1</code>.</p>
954<p>The second step is to decide <span class="emphasis"><em>how</em></span> you 954<p>The second step is to decide <span class="emphasis"><em>how</em></span> you
955 want to download pkgsrc. You can get it as a tar file or via CVS. 955 want to download pkgsrc. You can get it as a tar file or via CVS.
956 Both ways are described here.</p> 956 Both ways are described here.</p>
 957<p>Note that tar archive contains CVS working copy.
 958 Thus you can switch to using CVS at any later time.</p>
 959<p>Note also that quarterly branch is not frozen in stone.
 960 It receives critical updates.</p>
957<div class="sect2"> 961<div class="sect2">
958<div class="titlepage"><div><div><h3 class="title"> 962<div class="titlepage"><div><div><h3 class="title">
959<a name="getting-via-tar"></a>2.1.1. As tar file</h3></div></div></div> 963<a name="getting-via-tar"></a>2.1.1. As tar archive</h3></div></div></div>
960<p>The primary download location for all pkgsrc files is 964<p>The primary download location for all pkgsrc files is
961 <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a>. There are a 965 <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/" target="_top">http://ftp.NetBSD.org/pub/pkgsrc/</a> or
962 number of subdirectories for different purposes, which are 966 <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a>
963 described in detail in <a class="xref" href="#ftp-layout" title="Appendix C. Directory layout of the pkgsrc FTP server">Appendix C, <i>Directory layout of the pkgsrc FTP server</i></a>.</p> 967 (it points to the same location).
964<p>The tar file for the current branch is in the directory 968 There are a number of subdirectories for different purposes,
965 <code class="filename">current</code> and is called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>. 969 which are described in detail in <a class="xref" href="#ftp-layout" title="Appendix C. Directory layout of the pkgsrc FTP server">Appendix C, <i>Directory layout of the pkgsrc FTP server</i></a>.</p>
 970<p>The tar archive for the current branch is in the directory
 971 <code class="filename">current</code> and is called <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.
966 It is autogenerated daily.</p> 972 It is autogenerated daily.</p>
 973<p>To save download time we provide bzip2- and
 974 xz-compressed archives which are published at
 975 <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.bz2" target="_top"><code class="filename">pkgsrc.tar.bz2</code></a>
 976 and
 977 <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.xz" target="_top"><code class="filename">pkgsrc.tar.xz</code></a>
 978 respectively.
 979 </p>
 980<p>You can fetch the same files using FTP.</p>
967<p>The tar file for the stable branch 2009Q1 is in the 981<p>The tar file for the stable branch 2009Q1 is in the
968 directory <code class="filename">pkgsrc-2009Q1</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2009Q1/pkgsrc-2009Q1.tar.gz" target="_top"><code class="filename">pkgsrc-2009Q1.tar.gz</code></a>.</p> 982 directory <code class="filename">pkgsrc-2009Q1</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2009Q1/pkgsrc-2009Q1.tar.gz" target="_top"><code class="filename">pkgsrc-2009Q1.tar.gz</code></a>.</p>
969<p>To download a pkgsrc stable tarball, run:</p> 983<p>To download a pkgsrc stable tarball, run:</p>
970<pre class="screen"> 984<pre class="screen">
971<code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>.tar.gz</code></strong></pre> 985<code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>.tar.gz</code></strong></pre>
972<p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the 986<p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the
973 stable branch to be downloaded, for example,  987 stable branch to be downloaded, for example,
974 <span class="quote">&#8220;<span class="quote">pkgsrc-2009Q1</span>&#8221;</span>.</p> 988 <span class="quote">&#8220;<span class="quote">pkgsrc-2009Q1</span>&#8221;</span>.</p>
 989<p>You can use fetch it also using "wget", "curl",
 990 or your web browser.</p>
975<p>Then, extract it with:</p> 991<p>Then, extract it with:</p>
976<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf <em class="replaceable"><code>pkgsrc-20xxQy</code></em>.tar.gz -C /usr</code></strong></pre> 992<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf <em class="replaceable"><code>pkgsrc-20xxQy</code></em>.tar.gz -C /usr</code></strong></pre>
977<p>This will create the directory <code class="filename">pkgsrc/</code> 993<p>This will create the directory <code class="filename">pkgsrc/</code>
978 in <code class="filename">/usr/</code> and all the package source will be  994 in <code class="filename">/usr/</code> and all the package source will be
979 stored under <code class="filename">/usr/pkgsrc/</code>.</p> 995 stored under <code class="filename">/usr/pkgsrc/</code>.</p>
980<p>To download pkgsrc-current, run:</p> 996<p>To download pkgsrc-current, run:</p>
981<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</code></strong></pre> 997<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz</code></strong></pre>
982</div> 998</div>
983<div class="sect2"> 999<div class="sect2">
984<div class="titlepage"><div><div><h3 class="title"> 1000<div class="titlepage"><div><div><h3 class="title">
985<a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div> 1001<a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div>
986<p>To fetch a specific pkgsrc stable branch, run:</p> 1002<p>To fetch a specific pkgsrc stable branch, run:</p>
987<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr &amp;&amp; cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r <em class="replaceable"><code>pkgsrc-20xxQy</code></em> -P pkgsrc</code></strong> 1003<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr &amp;&amp; cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r <em class="replaceable"><code>pkgsrc-20xxQy</code></em> -P pkgsrc</code></strong>
@@ -7632,67 +7648,67 @@ the name of the common tools. For exampl @@ -7632,67 +7648,67 @@ the name of the common tools. For exampl
7632.if exists(/usr/bin/bzcat) 7648.if exists(/usr/bin/bzcat)
7633TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat 7649TOOLS_PLATFORM.bzcat?= /usr/bin/bzcat
7634.elif exists(/usr/bin/bzip2) 7650.elif exists(/usr/bin/bzip2)
7635TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd 7651TOOLS_PLATFORM.bzcat?= /usr/bin/bzip2 -cd
7636.endif 7652.endif
7637 7653
7638TOOLS_PLATFORM.true?= true # shell builtin 7654TOOLS_PLATFORM.true?= true # shell builtin
7639</pre> 7655</pre>
7640</div> 7656</div>
7641<div class="sect1"> 7657<div class="sect1">
7642<div class="titlepage"><div><div><h2 class="title" style="clear: both"> 7658<div class="titlepage"><div><div><h2 class="title" style="clear: both">
7643<a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div> 7659<a name="tools.questions"></a>18.4. Questions regarding the tools</h2></div></div></div>
7644<div class="qandaset"> 7660<div class="qandaset">
7645<a name="idm76241488"></a><dl> 7661<a name="idm30189572"></a><dl>
7646<dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a> 7662<dt>18.4.1. <a href="#tools.new">How do I add a new tool?</a>
7647</dt> 7663</dt>
7648<dt>18.4.2. <a href="#tools.listall">How do I get a list of all available 7664<dt>18.4.2. <a href="#tools.listall">How do I get a list of all available
7649 tools?</a> 7665 tools?</a>
7650</dt> 7666</dt>
7651<dt>18.4.3. <a href="#tools.used">How can I get a list of all the tools that a 7667<dt>18.4.3. <a href="#tools.used">How can I get a list of all the tools that a
7652 package is using while being built? I want to know whether it 7668 package is using while being built? I want to know whether it
7653 uses sed or not.</a> 7669 uses sed or not.</a>
7654</dt> 7670</dt>
7655</dl> 7671</dl>
7656<table border="0" style="width: 100%;"> 7672<table border="0" style="width: 100%;">
7657<colgroup> 7673<colgroup>
7658<col align="left" width="1%"> 7674<col align="left" width="1%">
7659<col> 7675<col>
7660</colgroup> 7676</colgroup>
7661<tbody> 7677<tbody>
7662<tr class="question"> 7678<tr class="question">
7663<td align="left" valign="top"> 7679<td align="left" valign="top">
7664<a name="tools.new"></a><a name="idm76241104"></a><p><b>18.4.1.</b></p> 7680<a name="tools.new"></a><a name="idm30189380"></a><p><b>18.4.1.</b></p>
7665</td> 7681</td>
7666<td align="left" valign="top"><p>How do I add a new tool?</p></td> 7682<td align="left" valign="top"><p>How do I add a new tool?</p></td>
7667</tr> 7683</tr>
7668<tr class="answer"> 7684<tr class="answer">
7669<td align="left" valign="top"></td> 7685<td align="left" valign="top"></td>
7670<td align="left" valign="top"><p>TODO</p></td> 7686<td align="left" valign="top"><p>TODO</p></td>
7671</tr> 7687</tr>
7672<tr class="question"> 7688<tr class="question">
7673<td align="left" valign="top"> 7689<td align="left" valign="top">
7674<a name="tools.listall"></a><a name="idm76240080"></a><p><b>18.4.2.</b></p> 7690<a name="tools.listall"></a><a name="idm30188868"></a><p><b>18.4.2.</b></p>
7675</td> 7691</td>
7676<td align="left" valign="top"><p>How do I get a list of all available 7692<td align="left" valign="top"><p>How do I get a list of all available
7677 tools?</p></td> 7693 tools?</p></td>
7678</tr> 7694</tr>
7679<tr class="answer"> 7695<tr class="answer">
7680<td align="left" valign="top"></td> 7696<td align="left" valign="top"></td>
7681<td align="left" valign="top"><p>TODO</p></td> 7697<td align="left" valign="top"><p>TODO</p></td>
7682</tr> 7698</tr>
7683<tr class="question"> 7699<tr class="question">
7684<td align="left" valign="top"> 7700<td align="left" valign="top">
7685<a name="tools.used"></a><a name="idm76239056"></a><p><b>18.4.3.</b></p> 7701<a name="tools.used"></a><a name="idm30188356"></a><p><b>18.4.3.</b></p>
7686</td> 7702</td>
7687<td align="left" valign="top"><p>How can I get a list of all the tools that a 7703<td align="left" valign="top"><p>How can I get a list of all the tools that a
7688 package is using while being built? I want to know whether it 7704 package is using while being built? I want to know whether it
7689 uses sed or not.</p></td> 7705 uses sed or not.</p></td>
7690</tr> 7706</tr>
7691<tr class="answer"> 7707<tr class="answer">
7692<td align="left" valign="top"></td> 7708<td align="left" valign="top"></td>
7693<td align="left" valign="top"><p>Currently, you can't. (TODO: But I want to be able 7709<td align="left" valign="top"><p>Currently, you can't. (TODO: But I want to be able
7694 to do it.)</p></td> 7710 to do it.)</p></td>
7695</tr> 7711</tr>
7696</tbody> 7712</tbody>
7697</table> 7713</table>
7698</div> 7714</div>
@@ -9719,27 +9735,27 @@ place.

 @@ -9719,27 +9735,27 @@ place.

9719</li> 9735</li>
9720</ol></div> 9736</ol></div>
9721</div> 9737</div>
9722</div> 9738</div>
9723<div class="chapter"> 9739<div class="chapter">
9724<div class="titlepage"><div><div><h2 class="title"> 9740<div class="titlepage"><div><div><h2 class="title">
9725<a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div> 9741<a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div>
9726<p>This section contains the answers to questions that may 9742<p>This section contains the answers to questions that may
9727 arise when you are writing a package. If you don't find your 9743 arise when you are writing a package. If you don't find your
9728 question answered here, first have a look in the other chapters, 9744 question answered here, first have a look in the other chapters,
9729 and if you still don't have the answer, ask on the 9745 and if you still don't have the answer, ask on the
9730 <code class="literal">pkgsrc-users</code> mailing list.</p> 9746 <code class="literal">pkgsrc-users</code> mailing list.</p>
9731<div class="qandaset"> 9747<div class="qandaset">
9732<a name="idm77784272"></a><dl> 9748<a name="idm29880324"></a><dl>
9733<dt>22.1. <a href="#devfaq.makeflags">What is the difference between 9749<dt>22.1. <a href="#devfaq.makeflags">What is the difference between
9734 MAKEFLAGS, .MAKEFLAGS and 9750 MAKEFLAGS, .MAKEFLAGS and
9735 MAKE_FLAGS?</a> 9751 MAKE_FLAGS?</a>
9736</dt> 9752</dt>
9737<dt>22.2. <a href="#devfaq.make">What is the difference between 9753<dt>22.2. <a href="#devfaq.make">What is the difference between
9738 MAKE, GMAKE and 9754 MAKE, GMAKE and
9739 MAKE_PROGRAM?</a> 9755 MAKE_PROGRAM?</a>
9740</dt> 9756</dt>
9741<dt>22.3. <a href="#devfaq.cc">What is the difference between 9757<dt>22.3. <a href="#devfaq.cc">What is the difference between
9742 CC, PKG_CC and 9758 CC, PKG_CC and
9743 PKGSRC_COMPILER?</a> 9759 PKGSRC_COMPILER?</a>
9744</dt> 9760</dt>
9745<dt>22.4. <a href="#devfaq.bl3flags">What is the difference between 9761<dt>22.4. <a href="#devfaq.bl3flags">What is the difference between
@@ -9764,157 +9780,157 @@ place.

 @@ -9764,157 +9780,157 @@ place.

9764</dt> 9780</dt>
9765<dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill. What shall I 9781<dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill. What shall I
9766do?</a> 9782do?</a>
9767</dt> 9783</dt>
9768</dl> 9784</dl>
9769<table border="0" style="width: 100%;"> 9785<table border="0" style="width: 100%;">
9770<colgroup> 9786<colgroup>
9771<col align="left" width="1%"> 9787<col align="left" width="1%">
9772<col> 9788<col>
9773</colgroup> 9789</colgroup>
9774<tbody> 9790<tbody>
9775<tr class="question"> 9791<tr class="question">
9776<td align="left" valign="top"> 9792<td align="left" valign="top">
9777<a name="devfaq.makeflags"></a><a name="idm77783888"></a><p><b>22.1.</b></p> 9793<a name="devfaq.makeflags"></a><a name="idm29880132"></a><p><b>22.1.</b></p>
9778</td> 9794</td>
9779<td align="left" valign="top"><p>What is the difference between 9795<td align="left" valign="top"><p>What is the difference between
9780 <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and 9796 <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
9781 <code class="varname">MAKE_FLAGS</code>?</p></td> 9797 <code class="varname">MAKE_FLAGS</code>?</p></td>
9782</tr> 9798</tr>
9783<tr class="answer"> 9799<tr class="answer">
9784<td align="left" valign="top"></td> 9800<td align="left" valign="top"></td>
9785<td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed 9801<td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed
9786 to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while 9802 to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while
9787 <code class="varname">MAKE_FLAGS</code> are the flags that are passed to 9803 <code class="varname">MAKE_FLAGS</code> are the flags that are passed to
9788 the <code class="varname">MAKE_PROGRAM</code> when building the 9804 the <code class="varname">MAKE_PROGRAM</code> when building the
9789 package. [FIXME: What is .MAKEFLAGS for?]</p></td> 9805 package. [FIXME: What is .MAKEFLAGS for?]</p></td>
9790</tr> 9806</tr>
9791<tr class="question"> 9807<tr class="question">
9792<td align="left" valign="top"> 9808<td align="left" valign="top">
9793<a name="devfaq.make"></a><a name="idm77779920"></a><p><b>22.2.</b></p> 9809<a name="devfaq.make"></a><a name="idm29873860"></a><p><b>22.2.</b></p>
9794</td> 9810</td>
9795<td align="left" valign="top"><p>What is the difference between 9811<td align="left" valign="top"><p>What is the difference between
9796 <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and 9812 <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
9797 <code class="varname">MAKE_PROGRAM</code>?</p></td> 9813 <code class="varname">MAKE_PROGRAM</code>?</p></td>
9798</tr> 9814</tr>
9799<tr class="answer"> 9815<tr class="answer">
9800<td align="left" valign="top"></td> 9816<td align="left" valign="top"></td>
9801<td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the 9817<td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the
9802 <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc 9818 <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc
9803 infrastructure. <code class="varname">GMAKE</code> is the path to GNU 9819 infrastructure. <code class="varname">GMAKE</code> is the path to GNU
9804 Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to 9820 Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to
9805 use that. <code class="varname">MAKE_PROGRAM</code> is the path to the 9821 use that. <code class="varname">MAKE_PROGRAM</code> is the path to the
9806 Make program that is used for building the 9822 Make program that is used for building the
9807 package.</p></td> 9823 package.</p></td>
9808</tr> 9824</tr>
9809<tr class="question"> 9825<tr class="question">
9810<td align="left" valign="top"> 9826<td align="left" valign="top">
9811<a name="devfaq.cc"></a><a name="idm77775440"></a><p><b>22.3.</b></p> 9827<a name="devfaq.cc"></a><a name="idm29871620"></a><p><b>22.3.</b></p>
9812</td> 9828</td>
9813<td align="left" valign="top"><p>What is the difference between 9829<td align="left" valign="top"><p>What is the difference between
9814 <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and 9830 <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
9815 <code class="varname">PKGSRC_COMPILER</code>?</p></td> 9831 <code class="varname">PKGSRC_COMPILER</code>?</p></td>
9816</tr> 9832</tr>
9817<tr class="answer"> 9833<tr class="answer">
9818<td align="left" valign="top"></td> 9834<td align="left" valign="top"></td>
9819<td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C 9835<td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C
9820 compiler, which can be configured by the pkgsrc user. 9836 compiler, which can be configured by the pkgsrc user.
9821 <code class="varname">PKG_CC</code> is the path to the compiler wrapper. 9837 <code class="varname">PKG_CC</code> is the path to the compiler wrapper.
9822 <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a 9838 <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a
9823 path to a compiler, but the type of compiler that should be 9839 path to a compiler, but the type of compiler that should be
9824 used. See <code class="filename">mk/compiler.mk</code> for more 9840 used. See <code class="filename">mk/compiler.mk</code> for more
9825 information about the latter variable.</p></td> 9841 information about the latter variable.</p></td>
9826</tr> 9842</tr>
9827<tr class="question"> 9843<tr class="question">
9828<td align="left" valign="top"> 9844<td align="left" valign="top">
9829<a name="devfaq.bl3flags"></a><a name="idm77771344"></a><p><b>22.4.</b></p> 9845<a name="devfaq.bl3flags"></a><a name="idm29869444"></a><p><b>22.4.</b></p>
9830</td> 9846</td>
9831<td align="left" valign="top"><p>What is the difference between 9847<td align="left" valign="top"><p>What is the difference between
9832 <code class="varname">BUILDLINK_LDFLAGS</code>, 9848 <code class="varname">BUILDLINK_LDFLAGS</code>,
9833 <code class="varname">BUILDLINK_LDADD</code> and 9849 <code class="varname">BUILDLINK_LDADD</code> and
9834 <code class="varname">BUILDLINK_LIBS</code>?</p></td> 9850 <code class="varname">BUILDLINK_LIBS</code>?</p></td>
9835</tr> 9851</tr>
9836<tr class="answer"> 9852<tr class="answer">
9837<td align="left" valign="top"></td> 9853<td align="left" valign="top"></td>
9838<td align="left" valign="top"><p>[FIXME]</p></td> 9854<td align="left" valign="top"><p>[FIXME]</p></td>
9839</tr> 9855</tr>
9840<tr class="question"> 9856<tr class="question">
9841<td align="left" valign="top"> 9857<td align="left" valign="top">
9842<a name="devfaq.bl3prefix"></a><a name="idm77769040"></a><p><b>22.5.</b></p> 9858<a name="devfaq.bl3prefix"></a><a name="idm29868356"></a><p><b>22.5.</b></p>
9843</td> 9859</td>
9844<td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var 9860<td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
9845 VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> 9861 VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
9846 say it's empty?</p></td> 9862 say it's empty?</p></td>
9847</tr> 9863</tr>
9848<tr class="answer"> 9864<tr class="answer">
9849<td align="left" valign="top"></td> 9865<td align="left" valign="top"></td>
9850<td align="left" valign="top"><p>For optimization reasons, some variables are only 9866<td align="left" valign="top"><p>For optimization reasons, some variables are only
9851 available in the <span class="quote">&#8220;<span class="quote">wrapper</span>&#8221;</span> phase and later. To 9867 available in the <span class="quote">&#8220;<span class="quote">wrapper</span>&#8221;</span> phase and later. To
9852 <span class="quote">&#8220;<span class="quote">simulate</span>&#8221;</span> the wrapper phase, append 9868 <span class="quote">&#8220;<span class="quote">simulate</span>&#8221;</span> the wrapper phase, append
9853 <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above 9869 <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above
9854 command.</p></td> 9870 command.</p></td>
9855</tr> 9871</tr>
9856<tr class="question"> 9872<tr class="question">
9857<td align="left" valign="top"> 9873<td align="left" valign="top">
9858<a name="devfaq.master_sites"></a><a name="idm77765968"></a><p><b>22.6.</b></p> 9874<a name="devfaq.master_sites"></a><a name="idm29866756"></a><p><b>22.6.</b></p>
9859</td> 9875</td>
9860<td align="left" valign="top"><p>What does 9876<td align="left" valign="top"><p>What does
9861 <code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I 9877 <code class="literal">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
9862 don't understand the <code class="literal">:=</code> inside 9878 don't understand the <code class="literal">:=</code> inside
9863 it.</p></td> 9879 it.</p></td>
9864</tr> 9880</tr>
9865<tr class="answer"> 9881<tr class="answer">
9866<td align="left" valign="top"></td> 9882<td align="left" valign="top"></td>
9867<td align="left" valign="top"><p>The <code class="literal">:=</code> is not really an 9883<td align="left" valign="top"><p>The <code class="literal">:=</code> is not really an
9868 assignment operator, like you might expect at first sight. 9884 assignment operator, like you might expect at first sight.
9869 Instead, it is a degenerate form of 9885 Instead, it is a degenerate form of
9870 <code class="literal">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>, 9886 <code class="literal">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
9871 which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which you 9887 which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which you
9872 may have seen as in <code class="literal">${SRCS:.c=.o}</code>. In the 9888 may have seen as in <code class="literal">${SRCS:.c=.o}</code>. In the
9873 case of <code class="varname">MASTER_SITE_*</code>, 9889 case of <code class="varname">MASTER_SITE_*</code>,
9874 <em class="replaceable"><code>old_string</code></em> is the empty string and 9890 <em class="replaceable"><code>old_string</code></em> is the empty string and
9875 <em class="replaceable"><code>new_string</code></em> is 9891 <em class="replaceable"><code>new_string</code></em> is
9876 <code class="literal">package/</code>. That's where the 9892 <code class="literal">package/</code>. That's where the
9877 <code class="literal">:</code> and the <code class="literal">=</code> fall 9893 <code class="literal">:</code> and the <code class="literal">=</code> fall
9878 together.</p></td> 9894 together.</p></td>
9879</tr> 9895</tr>
9880<tr class="question"> 9896<tr class="question">
9881<td align="left" valign="top"> 9897<td align="left" valign="top">
9882<a name="devfaq.mailinglists"></a><a name="idm77749712"></a><p><b>22.7.</b></p> 9898<a name="devfaq.mailinglists"></a><a name="idm29862788"></a><p><b>22.7.</b></p>
9883</td> 9899</td>
9884<td align="left" valign="top"><p>Which mailing lists are there for package 9900<td align="left" valign="top"><p>Which mailing lists are there for package
9885 developers?</p></td> 9901 developers?</p></td>
9886</tr> 9902</tr>
9887<tr class="answer"> 9903<tr class="answer">
9888<td align="left" valign="top"></td> 9904<td align="left" valign="top"></td>
9889<td align="left" valign="top"><div class="variablelist"><dl class="variablelist"> 9905<td align="left" valign="top"><div class="variablelist"><dl class="variablelist">
9890<dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt> 9906<dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt>
9891<dd><p>This is a list for technical discussions related 9907<dd><p>This is a list for technical discussions related
9892 to pkgsrc development, e.g. soliciting feedback for changes to 9908 to pkgsrc development, e.g. soliciting feedback for changes to
9893 pkgsrc infrastructure, proposed new features, questions related 9909 pkgsrc infrastructure, proposed new features, questions related
9894 to porting pkgsrc to a new platform, advice for maintaining a 9910 to porting pkgsrc to a new platform, advice for maintaining a
9895 package, patches that affect many packages, help requests moved 9911 package, patches that affect many packages, help requests moved
9896 from pkgsrc-users when an infrastructure bug is found, 9912 from pkgsrc-users when an infrastructure bug is found,
9897 etc.</p></dd> 9913 etc.</p></dd>
9898<dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt> 9914<dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt>
9899<dd><p>All bug reports in category "pkg" sent with 9915<dd><p>All bug reports in category "pkg" sent with
9900 <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here 9916 <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1+NetBSD-5.0.1+i386"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here
9901 directly; use one of the other mailing 9917 directly; use one of the other mailing
9902 lists.</p></dd> 9918 lists.</p></dd>
9903</dl></div></td> 9919</dl></div></td>
9904</tr> 9920</tr>
9905<tr class="question"> 9921<tr class="question">
9906<td align="left" valign="top"> 9922<td align="left" valign="top">
9907<a name="devfaq.documentation"></a><a name="idm77746000"></a><p><b>22.8.</b></p> 9923<a name="devfaq.documentation"></a><a name="idm29860740"></a><p><b>22.8.</b></p>
9908</td> 9924</td>
9909<td align="left" valign="top"><p>Where is the pkgsrc 9925<td align="left" valign="top"><p>Where is the pkgsrc
9910 documentation?</p></td> 9926 documentation?</p></td>
9911</tr> 9927</tr>
9912<tr class="answer"> 9928<tr class="answer">
9913<td align="left" valign="top"></td> 9929<td align="left" valign="top"></td>
9914<td align="left" valign="top"> 9930<td align="left" valign="top">
9915<p>There are many places where you can find 9931<p>There are many places where you can find
9916 documentation about pkgsrc:</p> 9932 documentation about pkgsrc:</p>
9917<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> 9933<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9918<li class="listitem"><p>The pkgsrc guide (this document) is a collection 9934<li class="listitem"><p>The pkgsrc guide (this document) is a collection
9919 of chapters that explain large parts of pkgsrc, but some 9935 of chapters that explain large parts of pkgsrc, but some
9920 chapters tend to be outdated. Which ones they are is hard to 9936 chapters tend to be outdated. Which ones they are is hard to
@@ -9942,27 +9958,27 @@ do? @@ -9942,27 +9958,27 @@ do?
9942 documented</span>&#8221;</span>, that is the documentation exists only in the 9958 documented</span>&#8221;</span>, that is the documentation exists only in the
9943 mind of the developer who wrote the code. To get this 9959 mind of the developer who wrote the code. To get this
9944 information, use the <span class="command"><strong>cvs annotate</strong></span> command 9960 information, use the <span class="command"><strong>cvs annotate</strong></span> command
9945 to see who has written it and ask on the 9961 to see who has written it and ask on the
9946 <code class="literal">tech-pkg</code> mailing list, so that others can 9962 <code class="literal">tech-pkg</code> mailing list, so that others can
9947 find your questions later (see above). To be sure that the 9963 find your questions later (see above). To be sure that the
9948 developer in charge reads the mail, you may CC him or 9964 developer in charge reads the mail, you may CC him or
9949 her.</p></li> 9965 her.</p></li>
9950</ul></div> 9966</ul></div>
9951</td> 9967</td>
9952</tr> 9968</tr>
9953<tr class="question"> 9969<tr class="question">
9954<td align="left" valign="top"> 9970<td align="left" valign="top">
9955<a name="devfaq.too-much-time"></a><a name="idm77739472"></a><p><b>22.9.</b></p> 9971<a name="devfaq.too-much-time"></a><a name="idm29857476"></a><p><b>22.9.</b></p>
9956</td> 9972</td>
9957<td align="left" valign="top"><p>I have a little time to kill. What shall I 9973<td align="left" valign="top"><p>I have a little time to kill. What shall I
9958do?</p></td> 9974do?</p></td>
9959</tr> 9975</tr>
9960<tr class="answer"> 9976<tr class="answer">
9961<td align="left" valign="top"></td> 9977<td align="left" valign="top"></td>
9962<td align="left" valign="top"> 9978<td align="left" valign="top">
9963<p>This is not really an FAQ yet, but here's the answer 9979<p>This is not really an FAQ yet, but here's the answer
9964anyway.</p> 9980anyway.</p>
9965<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> 9981<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
9966<li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the 9982<li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
9967 <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 9983 <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
9968 will tell you about newer versions of installed packages that are 9984 will tell you about newer versions of installed packages that are
cvs diff -r1.159 -r1.160 pkgsrc/doc/pkgsrc.txt (expand / switch to unified diff)

--- pkgsrc/doc/pkgsrc.txt 2013/04/21 15:21:17 1.159
+++ pkgsrc/doc/pkgsrc.txt 2013/05/03 20:55:22 1.160
@@ -37,27 +37,27 @@ Table of Contents @@ -37,27 +37,27 @@ Table of Contents
37 1.2. Overview 37 1.2. Overview
38 1.3. Terminology 38 1.3. Terminology
39 39
40 1.3.1. Roles involved in pkgsrc 40 1.3.1. Roles involved in pkgsrc
41 41
42 1.4. Typography 42 1.4. Typography
43 43
44I. The pkgsrc user's guide 44I. The pkgsrc user's guide
45 45
46 2. Where to get pkgsrc and how to keep it up-to-date 46 2. Where to get pkgsrc and how to keep it up-to-date
47 47
48 2.1. Getting pkgsrc for the first time 48 2.1. Getting pkgsrc for the first time
49 49
50 2.1.1. As tar file 50 2.1.1. As tar archive
51 2.1.2. Via anonymous CVS 51 2.1.2. Via anonymous CVS
52 52
53 2.2. Keeping pkgsrc up-to-date 53 2.2. Keeping pkgsrc up-to-date
54 54
55 2.2.1. Via tar files 55 2.2.1. Via tar files
56 2.2.2. Via CVS 56 2.2.2. Via CVS
57 57
58 3. Using pkgsrc on systems other than NetBSD 58 3. Using pkgsrc on systems other than NetBSD
59 59
60 3.1. Binary distribution 60 3.1. Binary distribution
61 3.2. Bootstrapping pkgsrc 61 3.2. Bootstrapping pkgsrc
62 3.3. Platform-specific notes 62 3.3. Platform-specific notes
63 63
@@ -689,27 +689,27 @@ infrastructure developers @@ -689,27 +689,27 @@ infrastructure developers
689When giving examples for commands, shell prompts are used to show if the 689When giving examples for commands, shell prompts are used to show if the
690command should/can be issued as root, or if "normal" user privileges are 690command should/can be issued as root, or if "normal" user privileges are
691sufficient. We use a # for root's shell prompt, and a % for users' shell 691sufficient. We use a # for root's shell prompt, and a % for users' shell
692prompt, assuming they use the C-shell or tcsh. 692prompt, assuming they use the C-shell or tcsh.
693 693
694Part I. The pkgsrc user's guide 694Part I. The pkgsrc user's guide
695 695
696Table of Contents 696Table of Contents
697 697
6982. Where to get pkgsrc and how to keep it up-to-date 6982. Where to get pkgsrc and how to keep it up-to-date
699 699
700 2.1. Getting pkgsrc for the first time 700 2.1. Getting pkgsrc for the first time
701 701
702 2.1.1. As tar file 702 2.1.1. As tar archive
703 2.1.2. Via anonymous CVS 703 2.1.2. Via anonymous CVS
704 704
705 2.2. Keeping pkgsrc up-to-date 705 2.2. Keeping pkgsrc up-to-date
706 706
707 2.2.1. Via tar files 707 2.2.1. Via tar files
708 2.2.2. Via CVS 708 2.2.2. Via CVS
709 709
7103. Using pkgsrc on systems other than NetBSD 7103. Using pkgsrc on systems other than NetBSD
711 711
712 3.1. Binary distribution 712 3.1. Binary distribution
713 3.2. Bootstrapping pkgsrc 713 3.2. Bootstrapping pkgsrc
714 3.3. Platform-specific notes 714 3.3. Platform-specific notes
715 715
@@ -807,72 +807,86 @@ Table of Contents @@ -807,72 +807,86 @@ Table of Contents
807 9.13. How do I change the location of configuration files? 807 9.13. How do I change the location of configuration files?
808 9.14. Automated security checks 808 9.14. Automated security checks
809 9.15. Why do some packages ignore my CFLAGS? 809 9.15. Why do some packages ignore my CFLAGS?
810 9.16. A package does not build. What shall I do? 810 9.16. A package does not build. What shall I do?
811 9.17. What does "Makefile appears to contain unresolved cvs/rcs/??? merge 811 9.17. What does "Makefile appears to contain unresolved cvs/rcs/??? merge
812 conflicts" mean? 812 conflicts" mean?
813 813
814Chapter 2. Where to get pkgsrc and how to keep it up-to-date 814Chapter 2. Where to get pkgsrc and how to keep it up-to-date
815 815
816Table of Contents 816Table of Contents
817 817
8182.1. Getting pkgsrc for the first time 8182.1. Getting pkgsrc for the first time
819 819
820 2.1.1. As tar file 820 2.1.1. As tar archive
821 2.1.2. Via anonymous CVS 821 2.1.2. Via anonymous CVS
822 822
8232.2. Keeping pkgsrc up-to-date 8232.2. Keeping pkgsrc up-to-date
824 824
825 2.2.1. Via tar files 825 2.2.1. Via tar files
826 2.2.2. Via CVS 826 2.2.2. Via CVS
827 827
828Before you download and extract the files, you need to decide where you want to 828Before you download and extract the files, you need to decide where you want to
829extract them. When using pkgsrc as root user, pkgsrc is usually installed in / 829extract them. When using pkgsrc as root user, pkgsrc is usually installed in /
830usr/pkgsrc. You are though free to install the sources and binary packages 830usr/pkgsrc. You are though free to install the sources and binary packages
831wherever you want in your filesystem, provided that the pathname does not 831wherever you want in your filesystem, provided that the pathname does not
832contain white-space or other characters that are interpreted specially by the 832contain white-space or other characters that are interpreted specially by the
833shell and some other programs. A safe bet is to use only letters, digits, 833shell and some other programs. A safe bet is to use only letters, digits,
834underscores and dashes. 834underscores and dashes.
835 835
8362.1. Getting pkgsrc for the first time 8362.1. Getting pkgsrc for the first time
837 837
838Before you download any pkgsrc files, you should decide whether you want the  838Before you download any pkgsrc files, you should decide whether you want the
839current branch or the stable branch. The latter is forked on a quarterly basis 839current branch or the stable branch. The latter is forked on a quarterly basis
840from the current branch and only gets modified for security updates. The names 840from the current branch and only gets modified for security updates. The names
841of the stable branches are built from the year and the quarter, for example 841of the stable branches are built from the year and the quarter, for example
8422009Q1. 8422009Q1.
843 843
844The second step is to decide how you want to download pkgsrc. You can get it as 844The second step is to decide how you want to download pkgsrc. You can get it as
845a tar file or via CVS. Both ways are described here. 845a tar file or via CVS. Both ways are described here.
846 846
8472.1.1. As tar file 847Note that tar archive contains CVS working copy. Thus you can switch to using
 848CVS at any later time.
848 849
849The primary download location for all pkgsrc files is ftp://ftp.NetBSD.org/pub/ 850Note also that quarterly branch is not frozen in stone. It receives critical
850pkgsrc/. There are a number of subdirectories for different purposes, which are 851updates.
 852
 8532.1.1. As tar archive
 854
 855The primary download location for all pkgsrc files is http://ftp.NetBSD.org/pub
 856/pkgsrc/ or ftp://ftp.NetBSD.org/pub/pkgsrc/ (it points to the same location).
 857There are a number of subdirectories for different purposes, which are
851described in detail in Appendix C, Directory layout of the pkgsrc FTP server. 858described in detail in Appendix C, Directory layout of the pkgsrc FTP server.
852 859
853The tar file for the current branch is in the directory current and is called 860The tar archive for the current branch is in the directory current and is
854pkgsrc.tar.gz. It is autogenerated daily. 861called pkgsrc.tar.gz. It is autogenerated daily.
 862
 863To save download time we provide bzip2- and xz-compressed archives which are
 864published at pkgsrc.tar.bz2 and pkgsrc.tar.xz respectively.
 865
 866You can fetch the same files using FTP.
855 867
856The tar file for the stable branch 2009Q1 is in the directory pkgsrc-2009Q1 and 868The tar file for the stable branch 2009Q1 is in the directory pkgsrc-2009Q1 and
857is also called pkgsrc-2009Q1.tar.gz. 869is also called pkgsrc-2009Q1.tar.gz.
858 870
859To download a pkgsrc stable tarball, run: 871To download a pkgsrc stable tarball, run:
860 872
861$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-20xxQy/pkgsrc-20xxQy.tar.gz 873$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-20xxQy/pkgsrc-20xxQy.tar.gz
862 874
863Where pkgsrc-20xxQy is the stable branch to be downloaded, for example, " 875Where pkgsrc-20xxQy is the stable branch to be downloaded, for example, "
864pkgsrc-2009Q1". 876pkgsrc-2009Q1".
865 877
 878You can use fetch it also using "wget", "curl", or your web browser.
 879
866Then, extract it with: 880Then, extract it with:
867 881
868$ tar -xzf pkgsrc-20xxQy.tar.gz -C /usr 882$ tar -xzf pkgsrc-20xxQy.tar.gz -C /usr
869 883
870This will create the directory pkgsrc/ in /usr/ and all the package source will 884This will create the directory pkgsrc/ in /usr/ and all the package source will
871be stored under /usr/pkgsrc/. 885be stored under /usr/pkgsrc/.
872 886
873To download pkgsrc-current, run: 887To download pkgsrc-current, run:
874 888
875$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz 889$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz
876 890
8772.1.2. Via anonymous CVS 8912.1.2. Via anonymous CVS
878 892