pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc doc/pkgsrc.*: regen
details: https://anonhg.NetBSD.org/pkgsrc/rev/b57599df61ec
branches: trunk
changeset: 409651:b57599df61ec
user: rillig <rillig%pkgsrc.org@localhost>
date: Sun Jan 19 14:17:01 2020 +0000
description:
doc/pkgsrc.*: regen
diffstat:
doc/pkgsrc.html | 1502 +++++++++++++++++++++++++++---------------------------
doc/pkgsrc.txt | 716 +++++++++++++-------------
2 files changed, 1120 insertions(+), 1098 deletions(-)
diffs (truncated from 3098 to 300 lines):
diff -r 05ace9ddee78 -r b57599df61ec doc/pkgsrc.html
--- a/doc/pkgsrc.html Sun Jan 19 14:16:58 2020 +0000
+++ b/doc/pkgsrc.html Sun Jan 19 14:17:01 2020 +0000
@@ -1263,7 +1263,8 @@
<span class="command"><strong>su</strong></span> to root first):</p>
<pre class="screen">
<code class="prompt">#</code> <strong class="userinput"><code>PATH="/usr/pkg/sbin:$PATH"</code></strong>
-<code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages/<em class="replaceable"><code>OPSYS</code></em>/<em
class="replaceable"><code>ARCH</code></em>/<em class="replaceable"><code>VERSIONS</code></em>/All/"</code></strong>
+<code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="http://cdn.NetBSD.org/pub/pkgsrc/packages";</code></strong>
+<code class="prompt">#</code> <strong class="userinput"><code>PKG_PATH="$PKG_PATH/<em class="replaceable"><code>OPSYS</code></em>/<em class="replaceable"><code>ARCH</code></em>/<em
class="replaceable"><code>VERSIONS</code></em>/All/"</code></strong>
<code class="prompt">#</code> <strong class="userinput"><code>export PATH PKG_PATH</code></strong>
</pre>
<p>Instead of URLs, you can also use local paths, for example if
@@ -7069,19 +7070,23 @@
are required:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
-<p>Check whether the license qualifies as Free or Open
- Source by referencing <a class="ulink" href="http://www.gnu.org/licenses/license-list.en.html"; target="_top">Various Licenses
- and Comments about Them</a> and <a class="ulink" href="http://opensource.org/licenses/alphabetical"; target="_top">Licenses by Name |
+<p>Check whether the license qualifies as Free or Open Source by
+ referencing <a class="ulink" href="https://www.gnu.org/licenses/license-list.en.html"; target="_top">Various
+ Licenses and Comments about Them</a> and <a class="ulink" href="https://opensource.org/licenses/alphabetical"; target="_top">Licenses by Name |
Open Source Initiative</a>. If this is the case, the filename in
<code class="filename">pkgsrc/licenses/</code> does not need the
<code class="filename">-license</code> suffix, and the license name should be
added to:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in <code class="filename">pkgsrc/mk/license.mk</code></p></li>
-<li class="listitem"><p>default_acceptable_licenses in <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
+<li class="listitem"><p>DEFAULT_ACCEPTABLE_LICENSES in
+ <code class="filename">pkgsrc/mk/license.mk</code></p></li>
+<li class="listitem"><p>default_acceptable_licenses in
+ <code class="filename">pkgsrc/pkgtools/pkg_install/files/lib/license.c</code></p></li>
</ul></div>
</li>
-<li class="listitem"><p>The license text should be added to <code class="filename">pkgsrc/licenses</code> for displaying. A list of known licenses can be seen in this directory.</p></li>
+<li class="listitem"><p>The license text should be added to
+ <code class="filename">pkgsrc/licenses</code> for displaying. A list of known
+ licenses can be seen in this directory.</p></li>
</ol></div>
</div>
<div class="sect3">
@@ -7425,25 +7430,25 @@
<code class="varname">PKGREVISION</code> are:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>Changing <code class="varname">HOMEPAGE</code>,
- <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>,
- or comments in Makefile.</p></li>
-<li class="listitem"><p>
- Changing build variables if the resulting binary package is the same.</p></li>
-<li class="listitem"><p>
- Changing <code class="filename">DESCR</code>.</p></li>
-<li class="listitem"><p>
- Adding <code class="varname">PKG_OPTIONS</code> if the default options don't change.</p></li>
+ <code class="varname">MAINTAINER</code>, <code class="varname">OWNER</code>, or
+ comments in Makefile.</p></li>
+<li class="listitem"><p>Changing build variables if the resulting binary
+ package is the same.</p></li>
+<li class="listitem"><p>Changing
+ <code class="filename">DESCR</code>.</p></li>
+<li class="listitem"><p>Adding <code class="varname">PKG_OPTIONS</code> if the
+ default options don't change.</p></li>
</ul></div>
<p>Examples of changes that do merit an increase to
<code class="varname">PKGREVISION</code> include:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p>
- Security fixes</p></li>
-<li class="listitem"><p>
- Changes or additions to a patch file</p></li>
-<li class="listitem"><p>
- Changes to the <code class="filename">PLIST</code></p></li>
-<li class="listitem"><p>A dependency is changed or renamed.</p></li>
+<li class="listitem"><p>Security fixes</p></li>
+<li class="listitem"><p>Changes or additions to a patch
+ file</p></li>
+<li class="listitem"><p>Changes to the
+ <code class="filename">PLIST</code></p></li>
+<li class="listitem"><p>A dependency is changed or
+ renamed.</p></li>
</ul></div>
<p>PKGREVISION must also be incremented when dependencies have ABI
changes.</p>
@@ -7556,7 +7561,13 @@
including the <code class="filename">nbX</code> suffix) or a date stamp can
be appended, like
<code class="varname">${PKGNAME_NOREV}-YYYYMMDD</code>.</p>
-<p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's name does not contain a version and the distfile is apt to change. In cases where the likelihood of this is very small,
<code class="varname">DIST_SUBDIR</code> might not be required. Additionally, <code class="varname">DIST_SUBDIR</code> must not be removed unless the distfile name changes, even if a package is being
moved or renamed.</p>
+<p><code class="varname">DIST_SUBDIR</code> is also used when a distfile's
+ name does not contain a version and the distfile is apt to change. In
+ cases where the likelihood of this is very small,
+ <code class="varname">DIST_SUBDIR</code> might not be required. Additionally,
+ <code class="varname">DIST_SUBDIR</code> must not be removed unless the
+ distfile name changes, even if a package is being moved or
+ renamed.</p>
<p>Do not forget regenerating the <code class="filename">distinfo</code> file
after that, since it contains the <code class="varname">DIST_SUBDIR</code>
path in the filenames.
@@ -7568,14 +7579,16 @@
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="build.fetch.github"></a>21.2.3. Packages hosted on github.com</h3></div></div></div>
-<p>Helper methods exist for packages hosted on github.com which will often have distfile names that clash with other packages, for example <code class="filename">1.0.tar.gz</code>. Use one of the
three recipes from below:
- </p>
+<p>Helper methods exist for packages hosted on github.com which
+ will often have distfile names that clash with other packages, for
+ example <code class="filename">1.0.tar.gz</code>. Use one of the three recipes
+ from below:</p>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="build.fetch.github.tag"></a>21.2.3.1. Fetch based on a tagged release</h4></div></div></div>
-<p>
- If your distfile URL looks similar to <code class="literal">http://github.com/username/exampleproject/archive/v1.0.zip</code>, then you are packaging a tagged release.
- </p>
+<p>If your distfile URL looks similar to
+ <code class="literal">http://github.com/username/exampleproject/archive/v1.0.zip</code>,
+ then you are packaging a tagged release.</p>
<pre class="programlisting">
DISTNAME= exampleproject-1.0
MASTER_SITES= ${MASTER_SITE_GITHUB:=username/}
@@ -7587,9 +7600,10 @@
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="build.fetch.github.commit"></a>21.2.3.2. Fetch based on a specific commit</h4></div></div></div>
-<p>
- If your distfile URL looks similar to <code class="literal">http://github.com/example/example/archive/988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz</code>, then you are packaging a
specific commit not tied to a release.
- </p>
+<p>If your distfile URL looks similar to
+ <code class="literal">http://github.com​/example​/example​/archive​/988881adc9fc3655077dc2d4d757d480b5ea0e11.tar.gz</code>,
+ then you are packaging a specific commit not tied to a
+ release.</p>
<pre class="programlisting">
DISTNAME= example-1.0
MASTER_SITES= ${MASTER_SITE_GITHUB:=example/}
@@ -7600,9 +7614,9 @@
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="build.fetch.github.release"></a>21.2.3.3. Fetch based on release</h4></div></div></div>
-<p>
- If your distfile URL looks similar to <code class="literal">http://github.com/username/exampleproject/releases/download/rel-1.6/offensive-1.6.zip</code>, then you are packaging a release.
- </p>
+<p>If your distfile URL looks similar to
+ <code class="literal">http://github.com​/username/exampleproject​/releases​/download​/rel-1.6​/offensive-1.6.zip</code>,
+ then you are packaging a release.</p>
<pre class="programlisting">
DISTNAME= offensive-1.6
PKGNAME= ${DISTNAME:S/offensive/proper/}
@@ -9030,7 +9044,7 @@
and if you still don't have the answer, ask on the
<code class="literal">pkgsrc-users</code> mailing list.</p>
<div class="qandaset">
-<a name="idm79113968"></a><dl>
+<a name="idm79547920"></a><dl>
<dt>24.1. <a href="#devfaq.makeflags">What is the difference between
MAKEFLAGS, .MAKEFLAGS and
MAKE_FLAGS?</a>
@@ -9075,7 +9089,7 @@
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.makeflags"></a><a name="idm79113584"></a><p><b>24.1.</b></p>
+<a name="devfaq.makeflags"></a><a name="idm79547536"></a><p><b>24.1.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">MAKEFLAGS</code>, <code class="varname">.MAKEFLAGS</code> and
@@ -9091,7 +9105,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.make"></a><a name="idm79109488"></a><p><b>24.2.</b></p>
+<a name="devfaq.make"></a><a name="idm79543568"></a><p><b>24.2.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">MAKE</code>, <code class="varname">GMAKE</code> and
@@ -9109,7 +9123,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.cc"></a><a name="idm79105136"></a><p><b>24.3.</b></p>
+<a name="devfaq.cc"></a><a name="idm79539088"></a><p><b>24.3.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">CC</code>, <code class="varname">PKG_CC</code> and
@@ -9127,7 +9141,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3flags"></a><a name="idm79100912"></a><p><b>24.4.</b></p>
+<a name="devfaq.bl3flags"></a><a name="idm79534992"></a><p><b>24.4.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">BUILDLINK_LDFLAGS</code>,
@@ -9140,7 +9154,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3prefix"></a><a name="idm79098736"></a><p><b>24.5.</b></p>
+<a name="devfaq.bl3prefix"></a><a name="idm79532816"></a><p><b>24.5.</b></p>
</td>
<td align="left" valign="top"><p>Why does <span class="command"><strong>make show-var
VARNAME=BUILDLINK_PREFIX.<em class="replaceable"><code>foo</code></em></strong></span>
@@ -9156,7 +9170,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.master_sites"></a><a name="idm79095536"></a><p><b>24.6.</b></p>
+<a name="devfaq.master_sites"></a><a name="idm79521424"></a><p><b>24.6.</b></p>
</td>
<td align="left" valign="top"><p>What does
<code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
@@ -9180,7 +9194,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.mailinglists"></a><a name="idm79088752"></a><p><b>24.7.</b></p>
+<a name="devfaq.mailinglists"></a><a name="idm79514512"></a><p><b>24.7.</b></p>
</td>
<td align="left" valign="top"><p>Which mailing lists are there for package
developers?</p></td>
@@ -9205,7 +9219,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.documentation"></a><a name="idm79076720"></a><p><b>24.8.</b></p>
+<a name="devfaq.documentation"></a><a name="idm79510800"></a><p><b>24.8.</b></p>
</td>
<td align="left" valign="top"><p>Where is the pkgsrc
documentation?</p></td>
@@ -9253,7 +9267,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.too-much-time"></a><a name="idm79070192"></a><p><b>24.9.</b></p>
+<a name="devfaq.too-much-time"></a><a name="idm79504272"></a><p><b>24.9.</b></p>
</td>
<td align="left" valign="top"><p>I have a little time to kill. What shall I
do?</p></td>
@@ -11237,1403 +11251,1407 @@
<td>HASKELL_ENABLE_SHARED_LIBRARY</td>
</tr>
<tr>
+<td>HASKELL_OPTIMIZATION_LEVEL</td>
<td>HAS_CONFIGURE</td>
+</tr>
+<tr>
<td>HEADER_TEMPLATES</td>
-</tr>
-<tr>
<td>HG_REPO</td>
+</tr>
+<tr>
<td>HG_REPOSITORIES</td>
-</tr>
-<tr>
<td>HG_TAG</td>
+</tr>
+<tr>
<td>HOST_PKGTOOLS_ARGS</td>
-</tr>
-<tr>
<td>HOST_SPECIFIC_PKGS</td>
+</tr>
+<tr>
<td>HOWL_GROUP</td>
-</tr>
-<tr>
<td>HOWL_USER</td>
+</tr>
+<tr>
<td>ICCBASE</td>
-</tr>
-<tr>
<td>ICECAST_CHROOTDIR</td>
+</tr>
+<tr>
<td>ICON_THEMES</td>
-</tr>
-<tr>
<td>IDOBASE</td>
+</tr>
+<tr>
<td>IGNORE_CCACHE</td>
-</tr>
-<tr>
<td>IGNORE_INFO_DIRS</td>
+</tr>
+<tr>
<td>IGNORE_INTERACTIVE_FETCH</td>
-</tr>
-<tr>
<td>IMAKE</td>
+</tr>
+<tr>
<td>IMAKEOPTS</td>
-</tr>
-<tr>
<td>IMAKE_MAKE</td>
+</tr>
+<tr>
Home |
Main Index |
Thread Index |
Old Index