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/609475fbaae6
branches: trunk
changeset: 396057:609475fbaae6
user: leot <leot%pkgsrc.org@localhost>
date: Mon May 20 18:15:36 2019 +0000
description:
doc/pkgsrc.*: regen
diffstat:
doc/pkgsrc.html | 5477 ++++++++++++++++++++++++++++--------------------------
doc/pkgsrc.txt | 3352 +++++++--------------------------
2 files changed, 3579 insertions(+), 5250 deletions(-)
diffs (truncated from 9022 to 300 lines):
diff -r 2bc40c1435c0 -r 609475fbaae6 doc/pkgsrc.html
--- a/doc/pkgsrc.html Mon May 20 18:14:24 2019 +0000
+++ b/doc/pkgsrc.html Mon May 20 18:15:36 2019 +0000
@@ -3096,12 +3096,21 @@
version of the dependency and where it can be found in pkgsrc. This line
should be placed in the third paragraph. If the dependency is only
needed for building the package, but not when using it, use
-<code class="varname">BUILD_DEPENDS</code> instead of <code class="varname">DEPENDS</code>.
+<code class="varname">TOOL_DEPENDS</code> or <code class="varname">BUILD_DEPENDS</code>
+instead of <code class="varname">DEPENDS</code>.
+The difference between <code class="varname">TOOL_DEPENDS</code> and
+<code class="varname">BUILD_DEPENDS</code> occurs when cross-compiling:
+<code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
+packages, i.e. packages for the architecture where the package
+is built;
+<code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
+packages, i.e. packages for the architecture for which the package
+is built.
Your package may then look like this:</p>
<pre class="programlisting">
[...]
-BUILD_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
+TOOL_DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
DEPENDS+= screen-[0-9]*:../../misc/screen
DEPENDS+= screen>=4.0:../../misc/screen
@@ -5876,39 +5885,76 @@
<code class="varname">MASTER_SITES</code>, which can be used in
packages. The names of the variables should speak for
themselves.</p>
-<pre class="programlisting">
-${MASTER_SITE_APACHE}
-${MASTER_SITE_BACKUP}
-${MASTER_SITE_CYGWIN}
-${MASTER_SITE_DEBIAN}
-${MASTER_SITE_FREEBSD}
-${MASTER_SITE_FREEBSD_LOCAL}
-${MASTER_SITE_GENTOO}
-${MASTER_SITE_GNOME}
-${MASTER_SITE_GNU}
-${MASTER_SITE_GNUSTEP}
-${MASTER_SITE_HASKELL_HACKAGE}
-${MASTER_SITE_IFARCHIVE}
-${MASTER_SITE_KDE}
-${MASTER_SITE_MOZILLA}
-${MASTER_SITE_MOZILLA_ALL}
-${MASTER_SITE_MOZILLA_ESR}
-${MASTER_SITE_MYSQL}
-${MASTER_SITE_NETLIB}
-${MASTER_SITE_OPENOFFICE}
-${MASTER_SITE_OSDN}
-${MASTER_SITE_PERL_CPAN}
-${MASTER_SITE_PGSQL}
-${MASTER_SITE_RUBYGEMS}
-${MASTER_SITE_R_CRAN}
-${MASTER_SITE_SOURCEFORGE}
-${MASTER_SITE_SUNSITE}
-${MASTER_SITE_SUSE}
-${MASTER_SITE_TEX_CTAN}
-${MASTER_SITE_XCONTRIB}
-${MASTER_SITE_XEMACS}
-${MASTER_SITE_XORG}
-</pre>
+<table border="0" summary="Simple list" class="simplelist">
+<tr>
+<td>MASTER_SITE_APACHE</td>
+<td>MASTER_SITE_BACKUP</td>
+</tr>
+<tr>
+<td>MASTER_SITE_CRATESIO</td>
+<td>MASTER_SITE_CYGWIN</td>
+</tr>
+<tr>
+<td>MASTER_SITE_DEBIAN</td>
+<td>MASTER_SITE_FREEBSD</td>
+</tr>
+<tr>
+<td>MASTER_SITE_FREEBSD_LOCAL</td>
+<td>MASTER_SITE_GENTOO</td>
+</tr>
+<tr>
+<td>MASTER_SITE_GITHUB</td>
+<td>MASTER_SITE_GNOME</td>
+</tr>
+<tr>
+<td>MASTER_SITE_GNU</td>
+<td>MASTER_SITE_GNUSTEP</td>
+</tr>
+<tr>
+<td>MASTER_SITE_HASKELL_HACKAGE</td>
+<td>MASTER_SITE_IFARCHIVE</td>
+</tr>
+<tr>
+<td>MASTER_SITE_KDE</td>
+<td>MASTER_SITE_MOZILLA</td>
+</tr>
+<tr>
+<td>MASTER_SITE_MOZILLA_ALL</td>
+<td>MASTER_SITE_MYSQL</td>
+</tr>
+<tr>
+<td>MASTER_SITE_NETLIB</td>
+<td>MASTER_SITE_OPENBSD</td>
+</tr>
+<tr>
+<td>MASTER_SITE_OPENOFFICE</td>
+<td>MASTER_SITE_OSDN</td>
+</tr>
+<tr>
+<td>MASTER_SITE_PERL_CPAN</td>
+<td>MASTER_SITE_PGSQL</td>
+</tr>
+<tr>
+<td>MASTER_SITE_PYPI</td>
+<td>MASTER_SITE_RUBYGEMS</td>
+</tr>
+<tr>
+<td>MASTER_SITE_R_CRAN</td>
+<td>MASTER_SITE_SOURCEFORGE</td>
+</tr>
+<tr>
+<td>MASTER_SITE_SUNSITE</td>
+<td>MASTER_SITE_SUSE</td>
+</tr>
+<tr>
+<td>MASTER_SITE_TEX_CTAN</td>
+<td>MASTER_SITE_XCONTRIB</td>
+</tr>
+<tr>
+<td>MASTER_SITE_XEMACS</td>
+<td>MASTER_SITE_XORG</td>
+</tr>
+</table>
<p>Some explanations for the less self-explaining ones:
<code class="varname">MASTER_SITE_BACKUP</code> contains backup sites
for packages that are maintained in <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/%24%7BDIST_SUBDIR%7D";
target="_top">ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/${DIST_SUBDIR}</a>. <code class="varname">MASTER_SITE_LOCAL</code> contains local
@@ -6668,7 +6714,7 @@
</div>
<p>The <code class="varname">USE_TOOLS</code> definition is used both internally
by pkgsrc and also for individual packages to define what commands
-are needed for building a package (like <code class="varname">BUILD_DEPENDS</code>)
+are needed for building a package (like <code class="varname">TOOL_DEPENDS</code>)
or for later run-time of an installed packaged (such as
<code class="varname">DEPENDS</code>).
If the native system provides an adequate tool, then in many cases, a pkgsrc
@@ -7045,7 +7091,8 @@
<p>Your package may depend on some other package being present
- and there are various ways of expressing this dependency.
pkgsrc supports the <code class="varname">BUILD_DEPENDS</code> and
- <code class="varname">DEPENDS</code> definitions, the
+ <code class="varname">DEPENDS</code> and
+ <code class="varname">TOOL_DEPENDS</code> definitions, the
<code class="varname">USE_TOOLS</code> definition, as well as dependencies
via <code class="filename">buildlink3.mk</code>, which is the preferred way
to handle dependencies, and which uses the variables named above.
@@ -7054,13 +7101,22 @@
follows: The <code class="varname">DEPENDS</code> definition registers
that pre-requisite in the binary package so it will be pulled in
when the binary package is later installed, whilst the
- <code class="varname">BUILD_DEPENDS</code> definition does not, marking a
- dependency that is only needed for building the package.</p>
+ <code class="varname">BUILD_DEPENDS</code> and <code class="varname">TOOL_DEPENDS</code>
+ definitions does not, marking a dependency that is only needed for
+ building the package.</p>
<p>This means that if you only need a package present whilst
you are building, it should be noted as a
- <code class="varname">BUILD_DEPENDS</code>.</p>
-<p>The format for a <code class="varname">BUILD_DEPENDS</code> and a
- <code class="varname">DEPENDS</code> definition is:</p>
+ <code class="varname">TOOL_DEPENDS</code> or
+ <code class="varname">BUILD_DEPENDS</code>. When cross-compiling,
+ <code class="varname">TOOL_DEPENDS</code> are <span class="emphasis"><em>native</em></span>
+ packages, i.e. packages for the architecture where the package
+ is built;
+ <code class="varname">BUILD_DEPENDS</code> are <span class="emphasis"><em>target</em></span>
+ packages, i.e. packages for the architecture for which the package
+ is built.</p>
+<p>The format for <code class="varname">BUILD_DEPENDS</code>,
+ <code class="varname">DEPENDS</code> and <code class="varname">TOOL_DEPENDS</code>
+ definition is:</p>
<pre class="programlisting">
<pre-req-package-name>:../../<category>/<pre-req-package>
</pre>
@@ -7090,11 +7146,14 @@
</li>
<li class="listitem">
<p>If your package needs binaries from another package to build,
- use the <code class="varname">BUILD_DEPENDS</code> definition:</p>
-<pre class="programlisting">
-BUILD_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
+ use the <code class="varname">TOOL_DEPENDS</code> definition:</p>
+<pre class="programlisting">
+TOOL_DEPENDS+= itstool-[0-9]*:../../textproc/itstool
</pre>
</li>
+<li class="listitem"><p>If your package needs static libraries to link against, header
+ files to include, etc. from another package to build,
+ use the <code class="varname">BUILD_DEPENDS</code> definition.</p></li>
<li class="listitem"><p>If your package needs a library with which to link and
there is no <code class="filename">buildlink3.mk</code> file
available, create one. Using
@@ -8883,7 +8942,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="idm75421008"></a><dl>
+<a name="idm74777264"></a><dl>
<dt>24.1. <a href="#devfaq.makeflags">What is the difference between
MAKEFLAGS, .MAKEFLAGS and
MAKE_FLAGS?</a>
@@ -8928,7 +8987,7 @@
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.makeflags"></a><a name="idm75420624"></a><p><b>24.1.</b></p>
+<a name="devfaq.makeflags"></a><a name="idm74776880"></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
@@ -8944,7 +9003,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.make"></a><a name="idm75424848"></a><p><b>24.2.</b></p>
+<a name="devfaq.make"></a><a name="idm74781104"></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
@@ -8962,7 +9021,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.cc"></a><a name="idm75428688"></a><p><b>24.3.</b></p>
+<a name="devfaq.cc"></a><a name="idm74784944"></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
@@ -8980,7 +9039,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3flags"></a><a name="idm75432784"></a><p><b>24.4.</b></p>
+<a name="devfaq.bl3flags"></a><a name="idm74789040"></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>,
@@ -8993,7 +9052,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3prefix"></a><a name="idm75430608"></a><p><b>24.5.</b></p>
+<a name="devfaq.bl3prefix"></a><a name="idm74795056"></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>
@@ -9009,7 +9068,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.master_sites"></a><a name="idm75435728"></a><p><b>24.6.</b></p>
+<a name="devfaq.master_sites"></a><a name="idm74800176"></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
@@ -9033,7 +9092,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.mailinglists"></a><a name="idm75445328"></a><p><b>24.7.</b></p>
+<a name="devfaq.mailinglists"></a><a name="idm74801584"></a><p><b>24.7.</b></p>
</td>
<td align="left" valign="top"><p>Which mailing lists are there for package
developers?</p></td>
@@ -9058,7 +9117,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.documentation"></a><a name="idm75449808"></a><p><b>24.8.</b></p>
+<a name="devfaq.documentation"></a><a name="idm74806064"></a><p><b>24.8.</b></p>
</td>
<td align="left" valign="top"><p>Where is the pkgsrc
documentation?</p></td>
@@ -9106,7 +9165,7 @@
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.too-much-time"></a><a name="idm75451600"></a><p><b>24.9.</b></p>
+<a name="devfaq.too-much-time"></a><a name="idm74828336"></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>
@@ -10361,2580 +10420,2740 @@
The following list contains all help topics that are available
when running <span class="command"><strong>bmake help topic=:index</strong></span>.
</p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p>#!
-</p></li>
-<li class="listitem"><p>-lintl
Home |
Main Index |
Thread Index |
Old Index