| @@ -917,78 +917,73 @@ free to install the sources and binary p | | | @@ -917,78 +917,73 @@ free to install the sources and binary p |
917 | your filesystem, provided that the pathname does not contain white-space | | 917 | your filesystem, provided that the pathname does not contain white-space |
918 | or other characters that are interpreted specially by the shell and some | | 918 | or other characters that are interpreted specially by the shell and some |
919 | other programs. A safe bet is to use only letters, digits, underscores | | 919 | other programs. A safe bet is to use only letters, digits, underscores |
920 | and dashes.</p> | | 920 | and dashes.</p> |
921 | <div class="sect1"> | | 921 | <div class="sect1"> |
922 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | | 922 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> |
923 | <a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div> | | 923 | <a name="getting-first"></a>2.1. Getting pkgsrc for the first time</h2></div></div></div> |
924 | <p>Before you download any pkgsrc files, you should decide | | 924 | <p>Before you download any pkgsrc files, you should decide |
925 | whether you want the <span class="emphasis"><em>current</em></span> branch or the | | 925 | whether you want the <span class="emphasis"><em>current</em></span> branch or the |
926 | <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a | | 926 | <span class="emphasis"><em>stable</em></span> branch. The latter is forked on a |
927 | quarterly basis from the current branch and only gets modified | | 927 | quarterly basis from the current branch and only gets modified |
928 | for security updates. The names of the stable branches are built | | 928 | for security updates. The names of the stable branches are built |
929 | from the year and the quarter, for example | | 929 | from the year and the quarter, for example |
930 | <code class="literal">2016Q4</code>.</p> | | 930 | <code class="literal">2017Q3</code>.</p> |
931 | <p>The second step is to decide <span class="emphasis"><em>how</em></span> you | | 931 | <p>The second step is to decide <span class="emphasis"><em>how</em></span> you |
932 | want to download pkgsrc. You can get it as a tar file or via CVS. | | 932 | want to download pkgsrc. You can get it as a tar file or via CVS. |
933 | Both ways are described here.</p> | | 933 | Both ways are described here.</p> |
934 | <p>Note that tar archive contains CVS working copy. | | 934 | <p>Note that tar archive contains CVS working copy. |
935 | Thus you can switch to using CVS at any later time.</p> | | 935 | Thus you can switch to using CVS at any later time.</p> |
936 | <div class="sect2"> | | 936 | <div class="sect2"> |
937 | <div class="titlepage"><div><div><h3 class="title"> | | 937 | <div class="titlepage"><div><div><h3 class="title"> |
938 | <a name="getting-via-tar"></a>2.1.1. As tar archive</h3></div></div></div> | | 938 | <a name="getting-via-tar"></a>2.1.1. As tar archive</h3></div></div></div> |
939 | <p>The primary download location for all pkgsrc files is | | 939 | <p>The primary download location for all pkgsrc files is |
940 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/" target="_top">http://ftp.NetBSD.org/pub/pkgsrc/</a> or | | 940 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/" target="_top">http://ftp.NetBSD.org/pub/pkgsrc/</a> or |
941 | <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a> | | 941 | <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/" target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/</a> |
942 | (it points to the same location). | | 942 | (it points to the same location). |
943 | There are a number of subdirectories for different purposes, | | 943 | There are a number of subdirectories for different purposes, |
944 | 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> | | 944 | 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> |
945 | <p>The tar archive for the current branch is in the directory | | 945 | <p>The tar archive for the current branch is in the directory |
946 | <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>. | | 946 | <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>. |
947 | It is autogenerated weekly.</p> | | 947 | It is autogenerated weekly.</p> |
948 | <p>To save download time we provide bzip2- and | | 948 | <p>To save download time we provide bzip2- and |
949 | xz-compressed archives which are published at | | 949 | xz-compressed archives which are published at |
950 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.bz2" target="_top"><code class="filename">pkgsrc.tar.bz2</code></a> | | 950 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.bz2" target="_top"><code class="filename">pkgsrc.tar.bz2</code></a> |
951 | and | | 951 | and |
952 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.xz" target="_top"><code class="filename">pkgsrc.tar.xz</code></a> | | 952 | <a class="ulink" href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.xz" target="_top"><code class="filename">pkgsrc.tar.xz</code></a> |
953 | respectively. | | 953 | respectively. |
954 | </p> | | 954 | </p> |
955 | <p>You can fetch the same files using FTP.</p> | | 955 | <p>You can fetch the same files using FTP.</p> |
956 | <p>The tar file for the stable branch 2016Q4 is in the | | 956 | <p>The tar file for the stable branch 2017Q3 is in the |
957 | directory <code class="filename">pkgsrc-2016Q4</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2016Q4/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p> | | 957 | directory <code class="filename">pkgsrc-2017Q3</code> and is also called <a class="ulink" href="http://cdn.NetBSD.org/pub/pkgsrc/pkgsrc-2017Q3/pkgsrc.tar.gz" target="_top"><code class="filename">pkgsrc.tar.gz</code></a>.</p> |
958 | <p>To download a pkgsrc stable tarball, run:</p> | | 958 | <p>To download the latest pkgsrc stable tarball, run:</p> |
959 | <pre class="screen"> | | 959 | <pre class="screen"> |
960 | <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>/pkgsrc.tar.gz</code></strong></pre> | | 960 | <code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2017Q3/pkgsrc.tar.gz</code></strong></pre> |
961 | <p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the | | | |
962 | stable branch to be downloaded, for example, | | | |
963 | <span class="quote">“<span class="quote">pkgsrc-2016Q4</span>”</span>.</p> | | | |
964 | <p>If you prefer, you can also fetch it using "wget", "curl", | | 961 | <p>If you prefer, you can also fetch it using "wget", "curl", |
965 | or your web browser.</p> | | 962 | or your web browser.</p> |
966 | <p>Then, extract it with:</p> | | 963 | <p>Then, extract it with:</p> |
967 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre> | | 964 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre> |
968 | <p>This will create the directory <code class="filename">pkgsrc/</code> | | 965 | <p>This will create the directory <code class="filename">pkgsrc/</code> |
969 | in <code class="filename">/usr/</code> and all the package source will be | | 966 | in <code class="filename">/usr/</code> and all the package source will be |
970 | stored under <code class="filename">/usr/pkgsrc/</code>.</p> | | 967 | stored under <code class="filename">/usr/pkgsrc/</code>.</p> |
971 | <p>To download pkgsrc-current, run:</p> | | 968 | <p>To download pkgsrc-current, run:</p> |
972 | <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> | | 969 | <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> |
973 | </div> | | 970 | </div> |
974 | <div class="sect2"> | | 971 | <div class="sect2"> |
975 | <div class="titlepage"><div><div><h3 class="title"> | | 972 | <div class="titlepage"><div><div><h3 class="title"> |
976 | <a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div> | | 973 | <a name="getting-via-cvs"></a>2.1.2. Via anonymous CVS</h3></div></div></div> |
977 | <p>To fetch a specific pkgsrc stable branch, run:</p> | | 974 | <p>To fetch a specific pkgsrc stable branch, run:</p> |
978 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r <em class="replaceable"><code>pkgsrc-20xxQy</code></em> -P pkgsrc</code></strong> | | 975 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -r pkgsrc-2017Q3 -P pkgsrc</code></strong> |
979 | </pre> | | 976 | </pre> |
980 | <p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the stable | | | |
981 | branch to be checked out, for example, <span class="quote">“<span class="quote">pkgsrc-2016Q4</span>”</span></p> | | | |
982 | <p>This will create the directory <code class="filename">pkgsrc/</code> | | 977 | <p>This will create the directory <code class="filename">pkgsrc/</code> |
983 | in your <code class="filename">/usr/</code> directory and all the package source | | 978 | in your <code class="filename">/usr/</code> directory and all the package source |
984 | will be stored under <code class="filename">/usr/pkgsrc/</code>.</p> | | 979 | will be stored under <code class="filename">/usr/pkgsrc/</code>.</p> |
985 | <p>To fetch the pkgsrc current branch, run:</p> | | 980 | <p>To fetch the pkgsrc current branch, run:</p> |
986 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong> | | 981 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong> |
987 | </pre> | | 982 | </pre> |
988 | <p>Refer to the <a class="ulink" href="http://www.NetBSD.org/mirrors/#anoncvs" target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p> | | 983 | <p>Refer to the <a class="ulink" href="http://www.NetBSD.org/mirrors/#anoncvs" target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p> |
989 | <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable. E.g.:</p> | | 984 | <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable. E.g.:</p> |
990 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && env CVS_RSH=ssh cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong> | | 985 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && env CVS_RSH=ssh cvs -q -z2 -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout -P pkgsrc</code></strong> |
991 | </pre> | | 986 | </pre> |
992 | <p>Refer to documentation on your command shell how to set CVS_RSH=ssh permanently. | | 987 | <p>Refer to documentation on your command shell how to set CVS_RSH=ssh permanently. |
993 | For Bourne shells, you can set it in your <code class="filename">.profile</code> | | 988 | For Bourne shells, you can set it in your <code class="filename">.profile</code> |
994 | or better globally in <code class="filename">/etc/profile</code>:</p> | | 989 | or better globally in <code class="filename">/etc/profile</code>:</p> |
| @@ -1052,27 +1047,27 @@ release -d | | | @@ -1052,27 +1047,27 @@ release -d |
1052 | </pre> | | 1047 | </pre> |
1053 | <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable as described above. E.g.:</p> | | 1048 | <p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable as described above. E.g.:</p> |
1054 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP</code></strong> | | 1049 | <pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr/pkgsrc && env CVS_RSH=ssh cvs up -dP</code></strong> |
1055 | </pre> | | 1050 | </pre> |
1056 | <div class="sect3"> | | 1051 | <div class="sect3"> |
1057 | <div class="titlepage"><div><div><h4 class="title"> | | 1052 | <div class="titlepage"><div><div><h4 class="title"> |
1058 | <a name="uptodate-cvs-switch"></a>2.2.2.1. Switching between different pkgsrc branches</h4></div></div></div> | | 1053 | <a name="uptodate-cvs-switch"></a>2.2.2.1. Switching between different pkgsrc branches</h4></div></div></div> |
1059 | <p>When updating pkgsrc, the CVS program keeps track of the | | 1054 | <p>When updating pkgsrc, the CVS program keeps track of the |
1060 | branch you selected. But if you, for whatever reason, want to | | 1055 | branch you selected. But if you, for whatever reason, want to |
1061 | switch from the stable branch to the current one, you can do it | | 1056 | switch from the stable branch to the current one, you can do it |
1062 | by adding the option <span class="quote">“<span class="quote">-A</span>”</span> after the | | 1057 | by adding the option <span class="quote">“<span class="quote">-A</span>”</span> after the |
1063 | <span class="quote">“<span class="quote">update</span>”</span> keyword. To switch from the current branch | | 1058 | <span class="quote">“<span class="quote">update</span>”</span> keyword. To switch from the current branch |
1064 | back to the stable branch, add the | | 1059 | back to the stable branch, add the |
1065 | <span class="quote">“<span class="quote">-rpkgsrc-2016Q4</span>”</span> option.</p> | | 1060 | <span class="quote">“<span class="quote">-rpkgsrc-2017Q3</span>”</span> option.</p> |
1066 | </div> | | 1061 | </div> |
1067 | <div class="sect3"> | | 1062 | <div class="sect3"> |
1068 | <div class="titlepage"><div><div><h4 class="title"> | | 1063 | <div class="titlepage"><div><div><h4 class="title"> |
1069 | <a name="uptodate-cvs-changes"></a>2.2.2.2. What happens to my changes when updating?</h4></div></div></div> | | 1064 | <a name="uptodate-cvs-changes"></a>2.2.2.2. What happens to my changes when updating?</h4></div></div></div> |
1070 | <p>When you update pkgsrc, the CVS program will only touch | | 1065 | <p>When you update pkgsrc, the CVS program will only touch |
1071 | those files that are registered in the CVS repository. That | | 1066 | those files that are registered in the CVS repository. That |
1072 | means that any packages that you created on your own will stay | | 1067 | means that any packages that you created on your own will stay |
1073 | unmodified. If you change files that are managed by CVS, later | | 1068 | unmodified. If you change files that are managed by CVS, later |
1074 | updates will try to merge your changes with those that have been | | 1069 | updates will try to merge your changes with those that have been |
1075 | done by others. See the CVS manual, chapter | | 1070 | done by others. See the CVS manual, chapter |
1076 | <span class="quote">“<span class="quote">update</span>”</span> for details.</p> | | 1071 | <span class="quote">“<span class="quote">update</span>”</span> for details.</p> |
1077 | </div> | | 1072 | </div> |
1078 | </div> | | 1073 | </div> |
| @@ -8830,27 +8825,27 @@ place. | | | @@ -8830,27 +8825,27 @@ place. |
8830 | </li> | | 8825 | </li> |
8831 | </ol></div> | | 8826 | </ol></div> |
8832 | </div> | | 8827 | </div> |
8833 | </div> | | 8828 | </div> |
8834 | <div class="chapter"> | | 8829 | <div class="chapter"> |
8835 | <div class="titlepage"><div><div><h2 class="title"> | | 8830 | <div class="titlepage"><div><div><h2 class="title"> |
8836 | <a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div> | | 8831 | <a name="devfaq"></a>Chapter 22. Frequently Asked Questions</h2></div></div></div> |
8837 | <p>This section contains the answers to questions that may | | 8832 | <p>This section contains the answers to questions that may |
8838 | arise when you are writing a package. If you don't find your | | 8833 | arise when you are writing a package. If you don't find your |
8839 | question answered here, first have a look in the other chapters, | | 8834 | question answered here, first have a look in the other chapters, |
8840 | and if you still don't have the answer, ask on the | | 8835 | and if you still don't have the answer, ask on the |
8841 | <code class="literal">pkgsrc-users</code> mailing list.</p> | | 8836 | <code class="literal">pkgsrc-users</code> mailing list.</p> |
8842 | <div class="qandaset"> | | 8837 | <div class="qandaset"> |
8843 | <a name="idm81312272"></a><dl> | | 8838 | <a name="idm79078192"></a><dl> |
8844 | <dt>22.1. <a href="#devfaq.makeflags">What is the difference between | | 8839 | <dt>22.1. <a href="#devfaq.makeflags">What is the difference between |
8845 | MAKEFLAGS, .MAKEFLAGS and | | 8840 | MAKEFLAGS, .MAKEFLAGS and |
8846 | MAKE_FLAGS?</a> | | 8841 | MAKE_FLAGS?</a> |
8847 | </dt> | | 8842 | </dt> |
8848 | <dt>22.2. <a href="#devfaq.make">What is the difference between | | 8843 | <dt>22.2. <a href="#devfaq.make">What is the difference between |
8849 | MAKE, GMAKE and | | 8844 | MAKE, GMAKE and |
8850 | MAKE_PROGRAM?</a> | | 8845 | MAKE_PROGRAM?</a> |
8851 | </dt> | | 8846 | </dt> |
8852 | <dt>22.3. <a href="#devfaq.cc">What is the difference between | | 8847 | <dt>22.3. <a href="#devfaq.cc">What is the difference between |
8853 | CC, PKG_CC and | | 8848 | CC, PKG_CC and |
8854 | PKGSRC_COMPILER?</a> | | 8849 | PKGSRC_COMPILER?</a> |
8855 | </dt> | | 8850 | </dt> |
8856 | <dt>22.4. <a href="#devfaq.bl3flags">What is the difference between | | 8851 | <dt>22.4. <a href="#devfaq.bl3flags">What is the difference between |
| @@ -8875,157 +8870,157 @@ place. | | | @@ -8875,157 +8870,157 @@ place. |
8875 | </dt> | | 8870 | </dt> |
8876 | <dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill. What shall I | | 8871 | <dt>22.9. <a href="#devfaq.too-much-time">I have a little time to kill. What shall I |
8877 | do?</a> | | 8872 | do?</a> |
8878 | </dt> | | 8873 | </dt> |
8879 | </dl> | | 8874 | </dl> |
8880 | <table border="0" style="width: 100%;"> | | 8875 | <table border="0" style="width: 100%;"> |
8881 | <colgroup> | | 8876 | <colgroup> |
8882 | <col align="left" width="1%"> | | 8877 | <col align="left" width="1%"> |
8883 | <col> | | 8878 | <col> |
8884 | </colgroup> | | 8879 | </colgroup> |
8885 | <tbody> | | 8880 | <tbody> |
8886 | <tr class="question"> | | 8881 | <tr class="question"> |
8887 | <td align="left" valign="top"> | | 8882 | <td align="left" valign="top"> |
8888 | <a name="devfaq.makeflags"></a><a name="idm81311888"></a><p><b>22.1.</b></p> | | 8883 | <a name="devfaq.makeflags"></a><a name="idm79077808"></a><p><b>22.1.</b></p> |
8889 | </td> | | 8884 | </td> |
8890 | <td align="left" valign="top"><p>What is the difference between | | 8885 | <td align="left" valign="top"><p>What is the difference between |
8891 | <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and | | 8886 | <code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and |
8892 | <code class="varname">MAKE_FLAGS</code>?</p></td> | | 8887 | <code class="varname">MAKE_FLAGS</code>?</p></td> |
8893 | </tr> | | 8888 | </tr> |
8894 | <tr class="answer"> | | 8889 | <tr class="answer"> |
8895 | <td align="left" valign="top"></td> | | 8890 | <td align="left" valign="top"></td> |
8896 | <td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed | | 8891 | <td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed |
8897 | to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while | | 8892 | to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>, while |
8898 | <code class="varname">MAKE_FLAGS</code> are the flags that are passed to | | 8893 | <code class="varname">MAKE_FLAGS</code> are the flags that are passed to |
8899 | the <code class="varname">MAKE_PROGRAM</code> when building the | | 8894 | the <code class="varname">MAKE_PROGRAM</code> when building the |
8900 | package. [FIXME: What is .MAKEFLAGS for?]</p></td> | | 8895 | package. [FIXME: What is .MAKEFLAGS for?]</p></td> |
8901 | </tr> | | 8896 | </tr> |
8902 | <tr class="question"> | | 8897 | <tr class="question"> |
8903 | <td align="left" valign="top"> | | 8898 | <td align="left" valign="top"> |
8904 | <a name="devfaq.make"></a><a name="idm81307792"></a><p><b>22.2.</b></p> | | 8899 | <a name="devfaq.make"></a><a name="idm79073712"></a><p><b>22.2.</b></p> |
8905 | </td> | | 8900 | </td> |
8906 | <td align="left" valign="top"><p>What is the difference between | | 8901 | <td align="left" valign="top"><p>What is the difference between |
8907 | <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and | | 8902 | <code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and |
8908 | <code class="varname">MAKE_PROGRAM</code>?</p></td> | | 8903 | <code class="varname">MAKE_PROGRAM</code>?</p></td> |
8909 | </tr> | | 8904 | </tr> |
8910 | <tr class="answer"> | | 8905 | <tr class="answer"> |
8911 | <td align="left" valign="top"></td> | | 8906 | <td align="left" valign="top"></td> |
8912 | <td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the | | 8907 | <td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to the |
8913 | <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc | | 8908 | <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is used in the pkgsrc |
8914 | infrastructure. <code class="varname">GMAKE</code> is the path to GNU | | 8909 | infrastructure. <code class="varname">GMAKE</code> is the path to GNU |
8915 | Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to | | 8910 | Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to |
8916 | use that. <code class="varname">MAKE_PROGRAM</code> is the path to the | | 8911 | use that. <code class="varname">MAKE_PROGRAM</code> is the path to the |
8917 | Make program that is used for building the | | 8912 | Make program that is used for building the |
8918 | package.</p></td> | | 8913 | package.</p></td> |
8919 | </tr> | | 8914 | </tr> |
8920 | <tr class="question"> | | 8915 | <tr class="question"> |
8921 | <td align="left" valign="top"> | | 8916 | <td align="left" valign="top"> |
8922 | <a name="devfaq.cc"></a><a name="idm81303440"></a><p><b>22.3.</b></p> | | 8917 | <a name="devfaq.cc"></a><a name="idm79069360"></a><p><b>22.3.</b></p> |
8923 | </td> | | 8918 | </td> |
8924 | <td align="left" valign="top"><p>What is the difference between | | 8919 | <td align="left" valign="top"><p>What is the difference between |
8925 | <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and | | 8920 | <code class="varname">CC</code>, <code class="varname">PKG_CC</code> and |
8926 | <code class="varname">PKGSRC_COMPILER</code>?</p></td> | | 8921 | <code class="varname">PKGSRC_COMPILER</code>?</p></td> |
8927 | </tr> | | 8922 | </tr> |
8928 | <tr class="answer"> | | 8923 | <tr class="answer"> |
8929 | <td align="left" valign="top"></td> | | 8924 | <td align="left" valign="top"></td> |
8930 | <td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C | | 8925 | <td align="left" valign="top"><p><code class="varname">CC</code> is the path to the real C |
8931 | compiler, which can be configured by the pkgsrc user. | | 8926 | compiler, which can be configured by the pkgsrc user. |
8932 | <code class="varname">PKG_CC</code> is the path to the compiler wrapper. | | 8927 | <code class="varname">PKG_CC</code> is the path to the compiler wrapper. |
8933 | <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a | | 8928 | <code class="varname">PKGSRC_COMPILER</code> is <span class="emphasis"><em>not</em></span> a |
8934 | path to a compiler, but the type of compiler that should be | | 8929 | path to a compiler, but the type of compiler that should be |
8935 | used. See <code class="filename">mk/compiler.mk</code> for more | | 8930 | used. See <code class="filename">mk/compiler.mk</code> for more |
8936 | information about the latter variable.</p></td> | | 8931 | information about the latter variable.</p></td> |
8937 | </tr> | | 8932 | </tr> |
8938 | <tr class="question"> | | 8933 | <tr class="question"> |
8939 | <td align="left" valign="top"> | | 8934 | <td align="left" valign="top"> |
8940 | <a name="devfaq.bl3flags"></a><a name="idm81299216"></a><p><b>22.4.</b></p> | | 8935 | <a name="devfaq.bl3flags"></a><a name="idm79065136"></a><p><b>22.4.</b></p> |
8941 | </td> | | 8936 | </td> |
8942 | <td align="left" valign="top"><p>What is the difference between | | 8937 | <td align="left" valign="top"><p>What is the difference between |
8943 | <code class="varname">BUILDLINK_LDFLAGS</code>, | | 8938 | <code class="varname">BUILDLINK_LDFLAGS</code>, |
8944 | <code class="varname">BUILDLINK_LDADD</code> and | | 8939 | <code class="varname">BUILDLINK_LDADD</code> and |
8945 | <code class="varname">BUILDLINK_LIBS</code>?</p></td> | | 8940 | <code class="varname">BUILDLINK_LIBS</code>?</p></td> |
8946 | </tr> | | 8941 | </tr> |
8947 | <tr class="answer"> | | 8942 | <tr class="answer"> |
8948 | <td align="left" valign="top"></td> | | 8943 | <td align="left" valign="top"></td> |
8949 | <td align="left" valign="top"><p>[FIXME]</p></td> | | 8944 | <td align="left" valign="top"><p>[FIXME]</p></td> |
8950 | </tr> | | 8945 | </tr> |
8951 | <tr class="question"> | | 8946 | <tr class="question"> |
8952 | <td align="left" valign="top"> | | 8947 | <td align="left" valign="top"> |
8953 | <a name="devfaq.bl3prefix"></a><a name="idm81297040"></a><p><b>22.5.</b></p> | | 8948 | <a name="devfaq.bl3prefix"></a><a name="idm79062960"></a><p><b>22.5.</b></p> |
8954 | </td> | | 8949 | </td> |
8955 | <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var | | 8950 | <td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var |
8956 | VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> | | 8951 | VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span> |
8957 | say it's empty?</p></td> | | 8952 | say it's empty?</p></td> |
8958 | </tr> | | 8953 | </tr> |
8959 | <tr class="answer"> | | 8954 | <tr class="answer"> |
8960 | <td align="left" valign="top"></td> | | 8955 | <td align="left" valign="top"></td> |
8961 | <td align="left" valign="top"><p>For optimization reasons, some variables are only | | 8956 | <td align="left" valign="top"><p>For optimization reasons, some variables are only |
8962 | available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To | | 8957 | available in the <span class="quote">“<span class="quote">wrapper</span>”</span> phase and later. To |
8963 | <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append | | 8958 | <span class="quote">“<span class="quote">simulate</span>”</span> the wrapper phase, append |
8964 | <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above | | 8959 | <span class="command"><strong>PKG_PHASE=wrapper</strong></span> to the above |
8965 | command.</p></td> | | 8960 | command.</p></td> |
8966 | </tr> | | 8961 | </tr> |
8967 | <tr class="question"> | | 8962 | <tr class="question"> |
8968 | <td align="left" valign="top"> | | 8963 | <td align="left" valign="top"> |
8969 | <a name="devfaq.master_sites"></a><a name="idm81293840"></a><p><b>22.6.</b></p> | | 8964 | <a name="devfaq.master_sites"></a><a name="idm79059888"></a><p><b>22.6.</b></p> |
8970 | </td> | | 8965 | </td> |
8971 | <td align="left" valign="top"><p>What does | | 8966 | <td align="left" valign="top"><p>What does |
8972 | <code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I | | 8967 | <code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I |
8973 | don't understand the <code class="code">:=</code> inside | | 8968 | don't understand the <code class="code">:=</code> inside |
8974 | it.</p></td> | | 8969 | it.</p></td> |
8975 | </tr> | | 8970 | </tr> |
8976 | <tr class="answer"> | | 8971 | <tr class="answer"> |
8977 | <td align="left" valign="top"></td> | | 8972 | <td align="left" valign="top"></td> |
8978 | <td align="left" valign="top"><p>The <code class="code">:=</code> is not really an | | 8973 | <td align="left" valign="top"><p>The <code class="code">:=</code> is not really an |
8979 | assignment operator, although it looks like it. | | 8974 | assignment operator, although it looks like it. |
8980 | Instead, it is a degenerate form of | | 8975 | Instead, it is a degenerate form of |
8981 | <code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>, | | 8976 | <code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>, |
8982 | which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which is | | 8977 | which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> man page and which is |
8983 | commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the | | 8978 | commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the |
8984 | case of <code class="varname">MASTER_SITE_*</code>, | | 8979 | case of <code class="varname">MASTER_SITE_*</code>, |
8985 | <em class="replaceable"><code>old_string</code></em> is the empty string and | | 8980 | <em class="replaceable"><code>old_string</code></em> is the empty string and |
8986 | <em class="replaceable"><code>new_string</code></em> is | | 8981 | <em class="replaceable"><code>new_string</code></em> is |
8987 | <code class="code">package/</code>. That's where the | | 8982 | <code class="code">package/</code>. That's where the |
8988 | <code class="code">:</code> and the <code class="code">=</code> fall | | 8983 | <code class="code">:</code> and the <code class="code">=</code> fall |
8989 | together.</p></td> | | 8984 | together.</p></td> |
8990 | </tr> | | 8985 | </tr> |
8991 | <tr class="question"> | | 8986 | <tr class="question"> |
8992 | <td align="left" valign="top"> | | 8987 | <td align="left" valign="top"> |
8993 | <a name="devfaq.mailinglists"></a><a name="idm81287056"></a><p><b>22.7.</b></p> | | 8988 | <a name="devfaq.mailinglists"></a><a name="idm79044784"></a><p><b>22.7.</b></p> |
8994 | </td> | | 8989 | </td> |
8995 | <td align="left" valign="top"><p>Which mailing lists are there for package | | 8990 | <td align="left" valign="top"><p>Which mailing lists are there for package |
8996 | developers?</p></td> | | 8991 | developers?</p></td> |
8997 | </tr> | | 8992 | </tr> |
8998 | <tr class="answer"> | | 8993 | <tr class="answer"> |
8999 | <td align="left" valign="top"></td> | | 8994 | <td align="left" valign="top"></td> |
9000 | <td align="left" valign="top"><div class="variablelist"><dl class="variablelist"> | | 8995 | <td align="left" valign="top"><div class="variablelist"><dl class="variablelist"> |
9001 | <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt> | | 8996 | <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#tech-pkg" target="_top">tech-pkg</a></span></dt> |
9002 | <dd><p>This is a list for technical discussions related | | 8997 | <dd><p>This is a list for technical discussions related |
9003 | to pkgsrc development, e.g. soliciting feedback for changes to | | 8998 | to pkgsrc development, e.g. soliciting feedback for changes to |
9004 | pkgsrc infrastructure, proposed new features, questions related | | 8999 | pkgsrc infrastructure, proposed new features, questions related |
9005 | to porting pkgsrc to a new platform, advice for maintaining a | | 9000 | to porting pkgsrc to a new platform, advice for maintaining a |
9006 | package, patches that affect many packages, help requests moved | | 9001 | package, patches that affect many packages, help requests moved |
9007 | from pkgsrc-users when an infrastructure bug is found, | | 9002 | from pkgsrc-users when an infrastructure bug is found, |
9008 | etc.</p></dd> | | 9003 | etc.</p></dd> |
9009 | <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt> | | 9004 | <dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a></span></dt> |
9010 | <dd><p>All bug reports in category "pkg" sent with | | 9005 | <dd><p>All bug reports in category "pkg" sent with |
9011 | <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here | | 9006 | <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1.i386+NetBSD-7.1"><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear here. Please do not report your bugs here |
9012 | directly; use one of the other mailing | | 9007 | directly; use one of the other mailing |
9013 | lists.</p></dd> | | 9008 | lists.</p></dd> |
9014 | </dl></div></td> | | 9009 | </dl></div></td> |
9015 | </tr> | | 9010 | </tr> |
9016 | <tr class="question"> | | 9011 | <tr class="question"> |
9017 | <td align="left" valign="top"> | | 9012 | <td align="left" valign="top"> |
9018 | <a name="devfaq.documentation"></a><a name="idm81283216"></a><p><b>22.8.</b></p> | | 9013 | <a name="devfaq.documentation"></a><a name="idm79040944"></a><p><b>22.8.</b></p> |
9019 | </td> | | 9014 | </td> |
9020 | <td align="left" valign="top"><p>Where is the pkgsrc | | 9015 | <td align="left" valign="top"><p>Where is the pkgsrc |
9021 | documentation?</p></td> | | 9016 | documentation?</p></td> |
9022 | </tr> | | 9017 | </tr> |
9023 | <tr class="answer"> | | 9018 | <tr class="answer"> |
9024 | <td align="left" valign="top"></td> | | 9019 | <td align="left" valign="top"></td> |
9025 | <td align="left" valign="top"> | | 9020 | <td align="left" valign="top"> |
9026 | <p>There are many places where you can find | | 9021 | <p>There are many places where you can find |
9027 | documentation about pkgsrc:</p> | | 9022 | documentation about pkgsrc:</p> |
9028 | <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> | | 9023 | <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> |
9029 | <li class="listitem"><p>The pkgsrc guide (this document) is a collection | | 9024 | <li class="listitem"><p>The pkgsrc guide (this document) is a collection |
9030 | of chapters that explain large parts of pkgsrc, but some | | 9025 | of chapters that explain large parts of pkgsrc, but some |
9031 | chapters tend to be outdated. Which ones they are is hard to | | 9026 | chapters tend to be outdated. Which ones they are is hard to |
| @@ -9053,27 +9048,27 @@ do? | | | @@ -9053,27 +9048,27 @@ do? |
9053 | documented</span>”</span>, that is the documentation exists only in the | | 9048 | documented</span>”</span>, that is the documentation exists only in the |
9054 | mind of the developer who wrote the code. To get this | | 9049 | mind of the developer who wrote the code. To get this |
9055 | information, use the <span class="command"><strong>cvs annotate</strong></span> command | | 9050 | information, use the <span class="command"><strong>cvs annotate</strong></span> command |
9056 | to see who has written it and ask on the | | 9051 | to see who has written it and ask on the |
9057 | <code class="literal">tech-pkg</code> mailing list, so that others can | | 9052 | <code class="literal">tech-pkg</code> mailing list, so that others can |
9058 | find your questions later (see above). To be sure that the | | 9053 | find your questions later (see above). To be sure that the |
9059 | developer in charge reads the mail, you may CC him or | | 9054 | developer in charge reads the mail, you may CC him or |
9060 | her.</p></li> | | 9055 | her.</p></li> |
9061 | </ul></div> | | 9056 | </ul></div> |
9062 | </td> | | 9057 | </td> |
9063 | </tr> | | 9058 | </tr> |
9064 | <tr class="question"> | | 9059 | <tr class="question"> |
9065 | <td align="left" valign="top"> | | 9060 | <td align="left" valign="top"> |
9066 | <a name="devfaq.too-much-time"></a><a name="idm81268496"></a><p><b>22.9.</b></p> | | 9061 | <a name="devfaq.too-much-time"></a><a name="idm79034416"></a><p><b>22.9.</b></p> |
9067 | </td> | | 9062 | </td> |
9068 | <td align="left" valign="top"><p>I have a little time to kill. What shall I | | 9063 | <td align="left" valign="top"><p>I have a little time to kill. What shall I |
9069 | do?</p></td> | | 9064 | do?</p></td> |
9070 | </tr> | | 9065 | </tr> |
9071 | <tr class="answer"> | | 9066 | <tr class="answer"> |
9072 | <td align="left" valign="top"></td> | | 9067 | <td align="left" valign="top"></td> |
9073 | <td align="left" valign="top"> | | 9068 | <td align="left" valign="top"> |
9074 | <p>This is not really an FAQ yet, but here's the answer | | 9069 | <p>This is not really an FAQ yet, but here's the answer |
9075 | anyway.</p> | | 9070 | anyway.</p> |
9076 | <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> | | 9071 | <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> |
9077 | <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the | | 9072 | <li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the |
9078 | <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It | | 9073 | <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html" target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It |
9079 | will tell you about newer versions of installed packages that are | | 9074 | will tell you about newer versions of installed packages that are |