pkgsrc-Changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
CVS commit: pkgsrc/doc
Module Name: pkgsrc
Committed By: leot
Date: Wed Apr 4 10:24:23 UTC 2018
Modified Files:
pkgsrc/doc: pkgsrc.html pkgsrc.txt
Log Message:
doc/pkgsrc.*: regen
To generate a diff of this commit:
cvs rdiff -u -r1.249 -r1.250 pkgsrc/doc/pkgsrc.html
cvs rdiff -u -r1.245 -r1.246 pkgsrc/doc/pkgsrc.txt
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: pkgsrc/doc/pkgsrc.html
diff -u pkgsrc/doc/pkgsrc.html:1.249 pkgsrc/doc/pkgsrc.html:1.250
--- pkgsrc/doc/pkgsrc.html:1.249 Mon Nov 27 11:52:49 2017
+++ pkgsrc/doc/pkgsrc.html Wed Apr 4 10:24:23 2018
@@ -30,8 +30,8 @@
The pkgsrc Developers
</h3>
</div></div>
-<div><p class="copyright">Copyright � 1994-2017 The NetBSD Foundation, Inc</p></div>
-<div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.31 2017/07/30 22:07:39 jnemeth Exp $</p></div>
+<div><p class="copyright">Copyright � 1994-2018 The NetBSD Foundation, Inc</p></div>
+<div><p class="pubdate">$NetBSD: pkgsrc.xml,v 1.32 2018/01/01 01:26:07 jakllsch Exp $</p></div>
<div><div class="abstract">
<p class="title"><b>Abstract</b></p>
<p>pkgsrc is a centralized package management system for
@@ -488,13 +488,13 @@ packages for himself, which is a time-co
<p>pkgsrc currently contains several thousand packages,
including:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/README.html"; target="_top"><code class="filename">www/apache24</code></a> - The Apache
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/README.html"; target="_top"><code class="filename">www/apache24</code></a> - The Apache
web server</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a> - The Firefox
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a> - The Firefox
web browser</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html"; target="_top"><code class="filename">meta-pkgs/gnome</code></a> - The GNOME
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html"; target="_top"><code class="filename">meta-pkgs/gnome</code></a> - The GNOME
Desktop Environment</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/README.html"; target="_top"><code class="filename">meta-pkgs/kde4</code></a> - The K
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/README.html"; target="_top"><code class="filename">meta-pkgs/kde4</code></a> - The K
Desktop Environment</p></li>
</ul></div>
<p>… just to name a few.</p>
@@ -542,7 +542,7 @@ pkgsrc provides the following key featur
— That means, if a package contains bugs, it's better to find
them and to complain about them rather than to just install the package
and hope that it works. There are numerous checks in pkgsrc that try to
-find such bugs: Static analysis tools (<a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>),
build-time checks (portability
+find such bugs: Static analysis tools (<a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>),
build-time checks (portability
of shell scripts), and post-installation checks (installed files,
references to shared libraries, script interpreters).</p></li>
<li class="listitem"><p><span class="quote">“<span class="quote">If it works, it should work everywhere</span>”</span>
@@ -927,7 +927,7 @@ and dashes.</p>
quarterly basis from the current branch and only gets modified
for security updates. The names of the stable branches are built
from the year and the quarter, for example
- <code class="literal">2017Q3</code>.</p>
+ <code class="literal">2018Q1</code>.</p>
<p>The second step is to decide <span class="emphasis"><em>how</em></span> you
want to download pkgsrc. You can get it as a tar file or via CVS.
Both ways are described here.</p>
@@ -953,11 +953,11 @@ and dashes.</p>
respectively.
</p>
<p>You can fetch the same files using FTP.</p>
-<p>The tar file for the stable branch 2017Q3 is in the
- 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>
+<p>The tar file for the stable branch 2018Q1 is in the
+ directory <code class="filename">pkgsrc-2018Q1</code> and is also called <a class="ulink" href="https://cdn.NetBSD.org/pub/pkgsrc/pkgsrc-2018Q1/pkgsrc.tar.gz"; target="_top"><code
class="filename">pkgsrc.tar.gz</code></a>.</p>
<p>To download the latest pkgsrc stable tarball, run:</p>
<pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2017Q3/pkgsrc.tar.gz</code></strong></pre>
+<code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2018Q1/pkgsrc.tar.gz</code></strong></pre>
<p>If you prefer, you can also fetch it using "wget", "curl",
or your web browser.</p>
<p>Then, extract it with:</p>
@@ -972,7 +972,7 @@ and dashes.</p>
<div class="titlepage"><div><div><h3 class="title">
<a name="getting-via-cvs"></a>2.1.2.�Via anonymous CVS</h3></div></div></div>
<p>To fetch a specific pkgsrc stable branch, run:</p>
-<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -r pkgsrc-2017Q3 -P
pkgsrc</code></strong>
+<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && cvs -q -z2 -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -r pkgsrc-2018Q1 -P
pkgsrc</code></strong>
</pre>
<p>This will create the directory <code class="filename">pkgsrc/</code>
in your <code class="filename">/usr/</code> directory and all the package source
@@ -1057,7 +1057,7 @@ release -d
by adding the option <span class="quote">“<span class="quote">-A</span>”</span> after the
<span class="quote">“<span class="quote">update</span>”</span> keyword. To switch from the current branch
back to the stable branch, add the
- <span class="quote">“<span class="quote">-rpkgsrc-2017Q3</span>”</span> option.</p>
+ <span class="quote">“<span class="quote">-rpkgsrc-2018Q1</span>”</span> option.</p>
</div>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
@@ -1302,7 +1302,7 @@ and you can still use binary packages fr
<a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities"; target="_top">vulnerabilities</a>
file downloaded daily so that
it remains current. This may be done by adding an appropriate entry
- to the root users <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?crontab+5.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
+ to the root users <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?crontab+5.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
</p>
<pre class="screen">
# Download vulnerabilities file
@@ -1331,14 +1331,14 @@ fetch_pkg_vulnerabilities=YES
check_pkg_vulnerabilities=YES
</pre>
<p>
- see <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?daily.conf+5.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a> and
<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?security.conf+5.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for more
details.
+ see <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?daily.conf+5.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">daily.conf</span>(5)</span></a>
and <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?security.conf+5.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">security.conf</span>(5)</span></a> for
more details.
</p>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="pkg_versions"></a>4.1.6.�Finding if newer versions of your installed packages are in pkgsrc</h3></div></div></div>
<p>
- Install <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html"; target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
+ Install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html"; target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
<span class="command"><strong>lintpkgsrc</strong></span> with the <span class="quote">“<span class="quote">-i</span>”</span>
argument to check if your packages are up-to-date, e.g.
</p>
@@ -1366,7 +1366,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
categories. You can browse the online index of packages, or run
<span class="command"><strong>make readme</strong></span> from the <code class="filename">pkgsrc</code>
directory to build local <code class="filename">README.html</code> files for
- all packages, viewable with any web browser such as <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html"; target="_top"><code class="filename">www/lynx</code></a> or <a
href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a>.</p>
+ all packages, viewable with any web browser such as <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html"; target="_top"><code class="filename">www/lynx</code></a> or <a
href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a>.</p>
<p>The default <span class="emphasis"><em>prefix</em></span> for installed packages
is <code class="filename">/usr/pkg</code>. If you wish to change this, you
should do so by setting <code class="varname">LOCALBASE</code> in
@@ -1424,7 +1424,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
and adding the definitions there.</p>
<p>
If a package depends on many other packages (such as
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/README.html"; target="_top"><code class="filename">meta-pkgs/kde4</code></a>), the build process may
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde4/README.html"; target="_top"><code class="filename">meta-pkgs/kde4</code></a>), the build process may
alternate between periods of
downloading source, and compiling. To ensure you have all the source
downloaded initially you can run the command:
@@ -1522,7 +1522,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
help with this.</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
-<p>If you invoke 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>
command with
+<p>If you invoke the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>
command with
<code class="varname">PKG_DEBUG_LEVEL=2</code>, then a huge amount of
information will be displayed. For example,</p>
<pre class="screen"><strong class="userinput"><code>make patch PKG_DEBUG_LEVEL=2</code></strong></pre>
@@ -1530,10 +1530,10 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
including the <span class="quote">“<span class="quote">patch</span>”</span> stage.</p>
</li>
<li class="listitem">
-<p>If you want to know the value of a certain <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>
+<p>If you want to know the value of a certain <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a>
definition, then the <code class="varname">VARNAME</code> definition
should be used, in conjunction with the show-var
- target. e.g. to show the expansion of 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>
+ target. e.g. to show the expansion of the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a>
variable <code class="varname">LOCALBASE</code>:</p>
<pre class="screen">
<code class="prompt">%</code> <strong class="userinput"><code>make show-var VARNAME=LOCALBASE</code></strong>
@@ -1546,11 +1546,11 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
created yourself (see next section), that you put into
pkgsrc/packages manually or that is located on a remote FTP
server, you can use the "bin-install" target. This target will
- install a binary package - if available - via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>,
+ install a binary package - if available - via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>,
else do a <span class="command"><strong>make package</strong></span>. The list of remote FTP
sites searched is kept in the variable
<code class="varname">BINPKG_SITES</code>, which defaults to
- ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>
+ ftp.NetBSD.org. Any flags that should be added to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>
can be put into <code class="varname">BIN_INSTALL_FLAGS</code>. See
<code class="filename">pkgsrc/mk/defaults/mk.conf</code> for more
details.</p>
@@ -1589,7 +1589,7 @@ Version mismatch: 'tcsh' 6.09.00 vs 6.10
<a name="mk.conf"></a><p>The whole pkgsrc system is configured in a single file, usually
called <code class="filename">mk.conf</code>. In which directory pkgsrc looks for
that file depends on the installation. On NetBSD, when you use
-<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> from the base system, it
is in the directory
+<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> from the base system, it
is in the directory
<code class="filename">/etc/</code>. In all other cases the default location is
<code class="literal">${PREFIX}/etc/</code>, depending on where you told the
bootstrap program to install the binary packages.</p>
@@ -1735,7 +1735,7 @@ uid=1000(myusername) gid=100(users) grou
<p>
For the following command, you must be able to gain root
- privileges using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
+ privileges using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
</p>
<pre class="programlisting">
@@ -1836,7 +1836,7 @@ CFLAGS+= -your -flags
<p>Using <code class="varname">CFLAGS=</code> (i.e. without the
<span class="quote">“<span class="quote">+</span>”</span>) may lead to problems with packages that
need to add their own flags. You may want to take a look
- at the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html"; target="_top"><code class="filename">devel/cpuflags</code></a>
+ at the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html"; target="_top"><code class="filename">devel/cpuflags</code></a>
package if you're interested in optimization specifically
for the current CPU. </p>
</div>
@@ -1976,7 +1976,7 @@ PKG_OPTIONS.apache= suexec </pre>
<a name="building-a-single-binary-package"></a>6.1.�Building a single binary package</h2></div></div></div>
<p>Once you have built and installed a package, you can create
a <span class="emphasis"><em>binary package</em></span> which can be installed on
- another system with <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
+ another system with <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>. This saves having to build
the same package on a group of hosts and wasting CPU time. It also
provides a simple means for others to install your package, should
you distribute it.</p>
@@ -1993,7 +1993,7 @@ PKG_OPTIONS.apache= suexec </pre>
it. Binary packages are created by default in
<code class="filename">/usr/pkgsrc/packages</code>, in the form of a
gzipped tar file. See <a class="xref" href="#logs.package" title="B.2.�Packaging figlet">Section�B.2, “Packaging figlet”</a> for a
- continuation of the above <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/misc/figlet/README.html"; target="_top"><code class="filename">misc/figlet</code></a> example.</p>
+ continuation of the above <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/misc/figlet/README.html"; target="_top"><code class="filename">misc/figlet</code></a> example.</p>
<p>See <a class="xref" href="#submit" title="Chapter�21.�Submitting and Committing">Chapter�21, <i>Submitting and Committing</i></a> for information on how to submit
such a binary package.</p>
</div>
@@ -2143,7 +2143,7 @@ temporary filesystems, others must survi
<p>After your pkgsrc bulk-build has completed, you may wish to
create a CD-ROM set of the resulting binary packages to assist
in installing packages on other machines. The
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/cdpack/README.html"; target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/cdpack/README.html"; target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides
a simple tool for creating the ISO 9660 images.
<span class="command"><strong>cdpack</strong></span> arranges the packages on the CD-ROMs in a
way that keeps all the dependencies for a given package on the same
@@ -2393,70 +2393,70 @@ section attempts only to make the reader
they might be useful, and not to duplicate the documentation that comes
with each package.</p>
<p>Utilities used by pkgsrc (automatically installed when needed):</p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/README.html";
target="_top"><code class="filename">pkgtools/x11-links</code></a>:
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/x11-links/README.html";
target="_top"><code class="filename">pkgtools/x11-links</code></a>:
Symlinks for use by buildlink.</p></li></ul></div>
<p>OS tool augmentation (automatically installed when needed):</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/digest/README.html"; target="_top"><code class="filename">pkgtools/digest</code></a>:
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/digest/README.html"; target="_top"><code class="filename">pkgtools/digest</code></a>:
Calculates various kinds of checksums (including SHA3).</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libnbcompat/README.html"; target="_top"><code class="filename">pkgtools/libnbcompat</code></a>:
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libnbcompat/README.html"; target="_top"><code class="filename">pkgtools/libnbcompat</code></a>:
Compatibility library for pkgsrc tools.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/README.html"; target="_top"><code class="filename">pkgtools/mtree</code></a>: Installed on
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/mtree/README.html"; target="_top"><code class="filename">pkgtools/mtree</code></a>: Installed on
non-BSD systems due to lack of native mtree.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a>:
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a>:
Up-to-date replacement for
<code class="filename">/usr/sbin/pkg_install</code>, or for use on operating
systems where pkg_install is not present.</p></li>
</ul></div>
<p>Utilities used by pkgsrc (not automatically installed):</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html"; target="_top"><code class="filename">pkgtools/pkg_tarup</code></a>:
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html"; target="_top"><code class="filename">pkgtools/pkg_tarup</code></a>:
Create a binary package from an
already-installed package. Used by <span class="command"><strong>make replace</strong></span> to
save the old package.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/dfdisk/README.html"; target="_top"><code class="filename">pkgtools/dfdisk</code></a>:
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/dfdisk/README.html"; target="_top"><code class="filename">pkgtools/dfdisk</code></a>:
Adds extra functionality to pkgsrc, allowing it to fetch distfiles
from multiple locations. It currently supports the following
methods: multiple CD-ROMs and network FTP/HTTP connections.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html"; target="_top"><code class="filename">devel/cpuflags</code></a>: Determine
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html"; target="_top"><code class="filename">devel/cpuflags</code></a>: Determine
the best compiler flags to optimise code for your current
CPU and compiler. </p></li>
</ul></div>
<p>Utilities for keeping track of installed packages, being up to date,
etc:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgin/README.html"; target="_top"><code class="filename">pkgtools/pkgin</code></a>: A package
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgin/README.html"; target="_top"><code class="filename">pkgtools/pkgin</code></a>: A package
update tool similar to apt(1). Download, install, and upgrade
binary packages easily.</p></li>
-<li class="listitem"><p><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>: Reports on
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html"; target="_top"><code class="filename">pkgtools/pkg_chk</code></a>: Reports on
packages whose installed versions do not match the latest pkgsrc
entries.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html"; target="_top"><code class="filename">pkgtools/pkgdep</code></a>: Makes
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html"; target="_top"><code class="filename">pkgtools/pkgdep</code></a>: Makes
dependency graphs of packages, to aid in choosing a strategy for
updating.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdepgraph/README.html"; target="_top"><code class="filename">pkgtools/pkgdepgraph</code></a>: Makes
- graphs from the output of <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html"; target="_top"><code class="filename">pkgtools/pkgdep</code></a> (uses
graphviz).</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>: The
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdepgraph/README.html"; target="_top"><code class="filename">pkgtools/pkgdepgraph</code></a>: Makes
+ graphs from the output of <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdep/README.html"; target="_top"><code class="filename">pkgtools/pkgdep</code></a> (uses
graphviz).</p></li>
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>: The
pkglint(1) program checks a pkgsrc entry for errors.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html"; target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a>: The
lintpkgsrc(1) program
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html"; target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a>: The
lintpkgsrc(1) program
does various checks on the complete pkgsrc system.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgsurvey/README.html"; target="_top"><code class="filename">pkgtools/pkgsurvey</code></a>: Report what
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgsurvey/README.html"; target="_top"><code class="filename">pkgtools/pkgsurvey</code></a>: Report what
packages you have installed.</p></li>
</ul></div>
<p>Utilities for people maintaining or creating individual packages:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code class="filename">pkgtools/pkgdiff</code></a>: Automate
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code class="filename">pkgtools/pkgdiff</code></a>: Automate
making and maintaining patches for a package (includes pkgdiff,
pkgvi, mkpatches, etc.).</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code class="filename">pkgtools/url2pkg</code></a>: Aids in
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code class="filename">pkgtools/url2pkg</code></a>: Aids in
converting to pkgsrc.</p></li>
</ul></div>
<p>Utilities for people maintaining pkgsrc (or: more obscure pkg
utilities)</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_comp/README.html"; target="_top"><code class="filename">pkgtools/pkg_comp</code></a>: Build
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_comp/README.html"; target="_top"><code class="filename">pkgtools/pkg_comp</code></a>: Build
packages in a chrooted area.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libkver/README.html"; target="_top"><code class="filename">pkgtools/libkver</code></a>: Spoof
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/libkver/README.html"; target="_top"><code class="filename">pkgtools/libkver</code></a>: Spoof
kernel version for chrooted cross builds.</p></li>
</ul></div>
</div>
@@ -2567,7 +2567,7 @@ but downloading the entire directory may
<p>The answer here is to do a <span class="command"><strong>make fetch-list</strong></span> in
<code class="filename">/usr/pkgsrc</code> or one of its subdirectories, carry the
resulting list to your machine at work/school and use it there. If you
-don't have a NetBSD-compatible <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
+don't have a NetBSD-compatible <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ftp+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">ftp</span>(1)</span></a> (like tnftp) at work, don't
forget to set <code class="varname">FETCH_CMD</code> to something that fetches a
URL:</p>
<p>At home:</p>
@@ -2593,13 +2593,13 @@ by running:</p>
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="tmac.andoc-missing"></a>9.10.�What does <span class="quote">“<span class="quote">Don't know how to make
/usr/share/tmac/tmac.andoc</span>”</span> mean?</h2></div></div></div>
-<p>When compiling the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a>
+<p>When compiling the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a>
package, you get the error from make that it doesn't know how to make
<code class="filename">/usr/share/tmac/tmac.andoc</code>? This indicates that
you don't have installed the <span class="quote">“<span class="quote">text</span>”</span> set (nroff, ...) from
the NetBSD base distribution on your machine. It is recommended to do
that to format man pages.</p>
-<p>In the case of the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you
+<p>In the case of the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a> package, you
can get away with setting <code class="varname">NOMAN=YES</code> either in the
environment or in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p>
</div>
@@ -2619,11 +2619,11 @@ the one that corresponds to your release
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="using-sudo-with-pkgsrc"></a>9.12.�Using 'sudo' with pkgsrc</h2></div></div></div>
<p>When installing packages as non-root user and using the just-in-time
-<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a> feature of pkgsrc, it can
become annoying to type in the root
+<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?su+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a> feature of pkgsrc, it can
become annoying to type in the root
password for each required package installed. To avoid this, the sudo
package can be used, which does password caching over a limited time. To
use it, install sudo (either as binary package or from
-<a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/sudo/README.html"; target="_top"><code class="filename">security/sudo</code></a>) and then put the
+<a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/security/sudo/README.html"; target="_top"><code class="filename">security/sudo</code></a>) and then put the
following into your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, somewhere
<span class="emphasis"><em>after</em></span> the definition of the
<code class="varname">LOCALBASE</code> variable:</p>
@@ -2665,7 +2665,7 @@ maintains a database of known-exploits t
been included in pkgsrc. The database can be downloaded automatically, and
a security audit of all packages installed on a system can take place. To
do this, refer to the following two tools (installed as part of the
-<a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a> package):</p>
+<a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_install/README.html"; target="_top"><code class="filename">pkgtools/pkg_install</code></a> package):</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p><span class="command"><strong>pkg_admin fetch-pkg-vulnerabilities</strong></span>, an easy way to
@@ -2693,7 +2693,7 @@ perform a security check before building
<code class="varname">CFLAGS</code> variable in your
<a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>, these flags are passed in
environment variables to the <code class="filename">./configure</code>
- scripts and to <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>.
Some package authors ignore the
+ scripts and to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a>.
Some package authors ignore the
<code class="varname">CFLAGS</code> from the environment variable by
overriding them in the <code class="filename">Makefile</code>s of their
package.</p>
@@ -3004,7 +3004,7 @@ most likely have a URL from where you ca
code. Starting with this URL, creating a package involves only a
few steps.</p>
<div class="procedure"><ol class="procedure" type="1">
-<li class="step"><p>First, install the packages <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code
class="filename">pkgtools/url2pkg</code></a> and <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code
class="filename">pkgtools/pkglint</code></a>.</p></li>
+<li class="step"><p>First, install the packages <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code
class="filename">pkgtools/url2pkg</code></a> and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code
class="filename">pkgtools/pkglint</code></a>.</p></li>
<li class="step"><p>Then, choose one of the top-level directories as the
category in which you want to place your package. You can also create a
directory of your own (maybe called <code class="filename">local</code>). In that
@@ -3359,7 +3359,7 @@ BUILDLINK_TRANSFORM+= -l:IDL:IDL-2
<code class="filename">libIDL-2.so</code> is available. So I told the compiler
wrapper to rewrite that on the fly.</p>
<p>The next problem was related to a recent change of the FreeType
-interface. I looked up in <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/seamonkey/README.html"; target="_top"><code class="filename">www/seamonkey</code></a>
+interface. I looked up in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/seamonkey/README.html"; target="_top"><code class="filename">www/seamonkey</code></a>
which patch files were relevant for this issue and copied them to the
<code class="filename">patches</code> directory. Then I retried, fixed the
patches so that they applied cleanly and retried again. This time,
@@ -3477,7 +3477,7 @@ converters games mbone
Primary location(s) for distribution patch files (see
<code class="varname">PATCHFILES</code> above) if not found locally.</p></li>
<li class="listitem"><p><code class="varname">PATCH_DIST_STRIP</code>:
- an argument to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> that
sets the pathname strip count to
+ an argument to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a>
that sets the pathname strip count to
help find the correct files to patch. It defaults to
<span class="command"><strong>-p0</strong></span>.</p></li>
</ul></div>
@@ -3487,7 +3487,7 @@ converters games mbone
<li class="listitem"><p><code class="varname">MAINTAINER</code> is the email
address of the person who feels responsible for this package,
and who is most likely to look at problems or questions regarding
- this package which have been reported with <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>.
+ this package which have been reported with <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">send-pr</span>(1)</span></a>.
Other developers may contact the <code class="varname">MAINTAINER</code>
before making changes to the package, but are not required to
do so. When packaging a new program, set <code class="varname">MAINTAINER</code>
@@ -3524,7 +3524,7 @@ converters games mbone
set <code class="varname">WRKSRC</code> to point to the proper name in
<code class="filename">${WRKDIR}</code>, for example
<code class="varname">WRKSRC=${WRKDIR}/${DISTNAME}/unix</code>. See
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/tcl/README.html"; target="_top"><code class="filename">lang/tcl</code></a> and <a
href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/tk/README.html"; target="_top"><code class="filename">x11/tk</code></a> for other examples.</p>
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/tcl/README.html"; target="_top"><code class="filename">lang/tcl</code></a> and <a
href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/tk/README.html"; target="_top"><code class="filename">x11/tk</code></a> for other examples.</p>
<p>The name of the working directory created by pkgsrc is
taken from the <code class="varname">WRKDIR_BASENAME</code>
variable. By default, its value is
@@ -3570,7 +3570,7 @@ converters games mbone
<p>To regenerate the <code class="filename">distinfo</code> file, use the
<span class="command"><strong>make distinfo</strong></span> command.</p>
<p>Some packages have different sets of distfiles depending on
- the platform, for example <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/openjdk7/README.html"; target="_top"><code class="filename">lang/openjdk7</code></a>. These are kept in the
same
+ the platform, for example <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/openjdk7/README.html"; target="_top"><code class="filename">lang/openjdk7</code></a>. These are kept in the
same
<code class="filename">distinfo</code> file and care should be taken when
upgrading such a package to ensure distfile information is not
lost.</p>
@@ -3620,7 +3620,7 @@ converters games mbone
<p>One important thing to mention is to pay attention that no RCS
IDs get stored in the patch files, as these will cause problems when
later checked into the NetBSD CVS tree. Use the
- <span class="command"><strong>pkgdiff</strong></span> command from the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code
class="filename">pkgtools/pkgdiff</code></a> package to avoid these
+ <span class="command"><strong>pkgdiff</strong></span> command from the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code
class="filename">pkgtools/pkgdiff</code></a> package to avoid these
problems.</p>
<p>For even more automation, we recommend using
<span class="command"><strong>mkpatches</strong></span> from the same package to make a
@@ -3647,7 +3647,7 @@ converters games mbone
Many packages still use the previous convention
<code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>,
but new patches should be of the form containing the filename.
- <span class="command"><strong>mkpatches</strong></span> included in <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code
class="filename">pkgtools/pkgdiff</code></a> takes care of the name
+ <span class="command"><strong>mkpatches</strong></span> included in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code
class="filename">pkgtools/pkgdiff</code></a> takes care of the name
automatically.</p>
</div>
<div class="sect2">
@@ -3841,13 +3841,13 @@ monitor_file(...)
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="filename">INSTALL</code></span></dt>
<dd>
-<p>This shell script is invoked twice by <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>.
+<p>This shell script is invoked twice by <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>.
First time after package extraction and before files are
moved in place, the second time after the files to install
are moved in place. This can be used to do any custom
procedures not possible with @exec commands in
- <code class="filename">PLIST</code>. See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a> and
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a> for
more information. See also <a class="xref" href="#files-and-dirs-outside-prefix" title="15.1.�Files and directories outside the installation prefix">Section�15.1, “Files and directories
outside the installation prefix”</a>.
+ <code class="filename">PLIST</code>. See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a> and
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a>
for more information. See also <a class="xref" href="#files-and-dirs-outside-prefix" title="15.1.�Files and directories outside the installation prefix">Section�15.1, “Files and directories
outside the installation prefix”</a>.
Please note that you can modify variables in it easily by using
<code class="varname">FILES_SUBST</code> in the package's
<code class="filename">Makefile</code>:</p>
@@ -3867,8 +3867,8 @@ FILES_SUBST+= SOMEVAR="somevalue"
this script's responsibility to clean up any additional messy details
around the package's installation, since all pkg_delete knows is how to
delete the files created in the original distribution.
- See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
- and <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a>
for more information.
+ See <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a>
+ and <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_create</span>(1)</span></a> for more information.
The same methods to replace variables can be used as for
the <code class="filename">INSTALL</code> file.</p></dd>
<dt><span class="term"><code class="filename">MESSAGE</code></span></dt>
@@ -4007,13 +4007,13 @@ FILESDIR=${.CURDIR}/../xemacs/files
</div>
<p>Pkgsrc consists of many <code class="filename">Makefile</code> fragments,
each of which forms a well-defined part of the pkgsrc system. Using
- 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> system as a
programming language for a big system
+ the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> system as a
programming language for a big system
like pkgsrc requires some discipline to keep the code correct and
understandable.</p>
<p>The basic ingredients for <code class="filename">Makefile</code>
programming are variables (which are actually macros) and shell
commands. Among these shell commands may even be more complex ones
- like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?awk+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make
sure that every shell command runs
+ like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?awk+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">awk</span>(1)</span></a> programs. To make
sure that every shell command runs
as intended it is necessary to quote all variables correctly when they
are used.</p>
<p>This chapter describes some patterns, that appear quite often in
@@ -4027,7 +4027,7 @@ FILESDIR=${.CURDIR}/../xemacs/files
target of a rule, always write the data to a temporary file first
and finally rename that file. Otherwise there might occur an error
in the middle of generating the file, and when the user runs
- <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> for the second time,
the file exists and will not be
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> for the second time,
the file exists and will not be
regenerated properly. Example:</p>
<pre class="programlisting">
wrong:
@@ -4045,11 +4045,11 @@ correct:
<code class="filename">wrong</code> will exist, although there was an error
message in the first run. On the other hand, running <span class="command"><strong>make
correct</strong></span> gives an error message twice, as expected.</p>
-<p>You might remember that <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>
sometimes removes
+<p>You might remember that <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a> sometimes removes
<code class="literal">${.TARGET}</code> in case of error, but this only
happens when it is interrupted, for example by pressing
<code class="literal">^C</code>. This does <span class="emphasis"><em>not</em></span> happen
- when one of the commands fails (like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?false+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">false</span>(1)</span></a> above).</p>
+ when one of the commands fails (like <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?false+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">false</span>(1)</span></a> above).</p>
</li></ul></div>
</div>
<div class="sect1">
@@ -4057,7 +4057,7 @@ correct:
<a name="makefile.variables"></a>12.2.�<code class="filename">Makefile</code> variables</h2></div></div></div>
<p><code class="filename">Makefile</code> variables contain strings that
can be processed using the five operators ``='', ``+='', ``?='',
- ``:='', and ``!='', which are described 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
+ ``:='', and ``!='', which are described in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a> man
page.</p>
<p>When a variable's value is parsed from a
<code class="filename">Makefile</code>, the hash character ``#'' and the
@@ -4077,7 +4077,7 @@ correct:
In the other cases, it is evaluated lazily.</p>
<p>Some of the modifiers split the string into words and then
operate on the words, others operate on the string as a whole. When
- a string is split into words, it is split like in <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sh+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">sh</span>(1)</span></a>.</p>
+ a string is split into words, it is split like in <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sh+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">sh</span>(1)</span></a>.</p>
<p>There are several types of variables that should be handled
differently. Strings and two types of lists.</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
@@ -4157,7 +4157,7 @@ are just copied.</p>
<p>Example 2 quotes the string so that the shell interprets it
correctly. But the echo command may additionally interpret strings with a
leading dash or those containing backslashes.</p>
-<p>Example 3 can handle arbitrary strings, since <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?printf+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">printf</span>(1)</span></a> only
+<p>Example 3 can handle arbitrary strings, since <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?printf+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">printf</span>(1)</span></a> only
interprets the format string, but not the next argument.</p>
<p>In example 4, the <code class="varname">EXAMPLE_ENV</code> does not
need to be quoted because the quoting has already been done
@@ -4201,7 +4201,7 @@ install-examples: # produces a syntax
done
</pre>
<p>The shell only sees the text <code class="code">for egfile in ; do</code>, since
-<code class="code">${EGFILES}</code> is replaced with an empty string by <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>.
+<code class="code">${EGFILES}</code> is replaced with an empty string by <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a>.
To fix this syntax error, use one of the snippets below.</p>
<pre class="programlisting">
EMPTY= # empty
@@ -4251,7 +4251,7 @@ the following code: <code class="code">$
<span class="quote">“<span class="quote">packing list</span>”</span>, i.e. a list of files that belong to
the package (relative to the <code class="filename">${PREFIX}</code>
directory it's been installed in) plus some additional statements
- - see the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a>
man page for a full list.
+ - see the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_create+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">pkg_create</span>(1)</span></a>
man page for a full list.
This chapter addresses some issues that need attention when
dealing with the <code class="filename">PLIST</code> file (or files, see
below!).</p>
@@ -4395,7 +4395,7 @@ adding the RCS ID the space should be om
<p>To use one or more files as source for the <code class="filename">PLIST</code> used
in generating the binary package, set the variable
<code class="varname">PLIST_SRC</code> to the names of that file(s).
- The files are later concatenated using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cat+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
+ The files are later concatenated using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cat+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">cat</span>(1)</span></a>, and the order of things is
important. The default for <code class="varname">PLIST_SRC</code> is
<code class="filename">${PKGDIR}/PLIST</code>.</p>
</div>
@@ -4552,21 +4552,21 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.
<code class="varname">BDB_DEFAULT</code>.</p></li>
<li class="listitem"><p><code class="filename">curses.buildlink3.mk</code>: If the system
comes with neither Curses nor NCurses, this will take care
- to install the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/ncurses/README.html"; target="_top"><code class="filename">devel/ncurses</code></a> package.</p></li>
+ to install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/ncurses/README.html"; target="_top"><code class="filename">devel/ncurses</code></a> package.</p></li>
<li class="listitem"><p><code class="filename">krb5.buildlink3.mk</code> uses the value
of <code class="varname">KRB5_ACCEPTED</code> to choose between
adding a dependency on Heimdal or MIT-krb5 for packages that
require a Kerberos 5 implementation.</p></li>
<li class="listitem"><p><code class="filename">motif.buildlink3.mk</code> checks for a
system-provided Motif installation or adds a dependency on
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/lesstif/README.html"; target="_top"><code class="filename">x11/lesstif</code></a> or <a
href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/motif/README.html"; target="_top"><code class="filename">x11/motif</code></a>. The user can set
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/lesstif/README.html"; target="_top"><code class="filename">x11/lesstif</code></a> or <a
href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/x11/motif/README.html"; target="_top"><code class="filename">x11/motif</code></a>. The user can set
<code class="varname">MOTIF_TYPE</code> to <span class="quote">“<span class="quote">dt</span>”</span>,
<span class="quote">“<span class="quote">lesstif</span>”</span> or <span class="quote">“<span class="quote">motif</span>”</span>
to choose which Motif version will be used.</p></li>
<li class="listitem"><p><code class="filename">readline.buildlink3.mk</code> checks for a
system-provided GNU readline or editline (libedit) installation,
- or adds a dependency on <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/readline/README.html"; target="_top"><code class="filename">devel/readline</code></a>,
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/editline/README.html"; target="_top"><code class="filename">devel/editline</code></a>. The user can set
+ or adds a dependency on <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/readline/README.html"; target="_top"><code class="filename">devel/readline</code></a>,
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/editline/README.html"; target="_top"><code class="filename">devel/editline</code></a>. The user can set
<code class="varname">READLINE_DEFAULT</code> to choose readline implementation.
If your package really needs GNU readline library, its Makefile
should include <code class="filename">devel/readline/buildlink3.mk</code>
@@ -4581,7 +4581,7 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.
the file for more information.</p></li>
<li class="listitem"><p><code class="filename">pthread.buildlink3.mk</code> uses the value of
<code class="varname">PTHREAD_OPTS</code> and checks for native pthreads or adds
- a dependency on <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/pth/README.html"; target="_top"><code class="filename">devel/pth</code></a> as needed.</p></li>
+ a dependency on <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/pth/README.html"; target="_top"><code class="filename">devel/pth</code></a> as needed.</p></li>
<li class="listitem"><p><code class="filename">xaw.buildlink3.mk</code> uses the value of
<code class="varname">XAW_TYPE</code> to choose a particular Athena widgets
library.</p></li>
@@ -4602,7 +4602,7 @@ BUILDLINK_API_DEPENDS.foo+= foo>=1.
<code class="filename">buildlink3.mk</code> files that it needs to find
headers and libraries that it needs in turn.</p>
<p>To generate an initial <code class="filename">buildlink3.mk</code>
- file for further editing, Rene Hexel's <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/createbuildlink/README.html"; target="_top"><code
class="filename">pkgtools/createbuildlink</code></a>
+ file for further editing, Rene Hexel's <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/createbuildlink/README.html"; target="_top"><code
class="filename">pkgtools/createbuildlink</code></a>
package is highly recommended. For most packages, the following
command will generate a good starting point for
<code class="filename">buildlink3.mk</code> files:</p>
@@ -5140,7 +5140,7 @@ set based upon the following variables:<
variable only makes sense in the package's
<code class="filename">Makefile</code> (i.e., it is not user-customizable).</p>
<p>As an example, consider the Apache package,
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/README.html"; target="_top"><code class="filename">www/apache24</code></a>, which places its
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache24/README.html"; target="_top"><code class="filename">www/apache24</code></a>, which places its
configuration files under the
<code class="filename">httpd/</code> subdirectory of
<code class="varname">PKG_SYSCONFBASE</code>. This should be set in the package
@@ -5213,7 +5213,7 @@ during the package installation to updat
<code class="varname">CONF_FILES</code> and <code class="varname">CONF_FILES_PERMS</code> are
used. Check out <a class="xref" href="#files-outside-prefix" title="15.1.2.�File manipulation">Section�15.1.2, “File manipulation”</a> for information
about their syntax and their purpose. Here is an example, taken from the
-<a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/README.html"; target="_top"><code class="filename">mail/mutt</code></a> package:</p>
+<a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/mail/mutt/README.html"; target="_top"><code class="filename">mail/mutt</code></a> package:</p>
<pre class="programlisting">
EGDIR= ${PREFIX}/share/doc/mutt/samples
CONF_FILES= ${EGDIR}/Muttrc ${PKG_SYSCONFDIR}/Muttrc
@@ -5242,7 +5242,7 @@ to:</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem"><p>Store the script inside <code class="filename">${FILESDIR}</code>, with
the <code class="literal">.sh</code> suffix appended. Considering the
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/cups/README.html"; target="_top"><code class="filename">print/cups</code></a> package as an example, it has a
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/cups/README.html"; target="_top"><code class="filename">print/cups</code></a> package as an example, it has a
<code class="filename">cupsd.sh</code> in its files directory.</p></li>
<li class="listitem">
<p>Tell pkginstall to handle it, appending the name of the script,
@@ -5326,7 +5326,7 @@ accomplish this task.</p>
<p>When a package provides a shell interpreter, it has to set the
<code class="varname">PKG_SHELL</code> variable to its absolute file name. This will
add some hooks to the installation scripts to handle it. Consider the
-following example, taken from <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/zsh/README.html"; target="_top"><code class="filename">shells/zsh</code></a>:</p>
+following example, taken from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/zsh/README.html"; target="_top"><code class="filename">shells/zsh</code></a>:</p>
<pre class="programlisting">
PKG_SHELL= ${PREFIX}/bin/zsh
</pre>
@@ -5352,7 +5352,7 @@ where <em class="replaceable"><code>type
installation scripts to run the appropriate commands to update the fonts
database files within each of those directories. For convenience, if the
directory path is relative, it is taken to be relative to the package's
-installation prefix. Consider the following example, taken from <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/fonts/dbz-ttf/README.html"; target="_top"><code
class="filename">fonts/dbz-ttf</code></a>:</p>
+installation prefix. Consider the following example, taken from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/fonts/dbz-ttf/README.html"; target="_top"><code
class="filename">fonts/dbz-ttf</code></a>:</p>
<pre class="programlisting">
FONTS_DIRS.ttf= ${PREFIX}/share/fonts/X11/TTF
</pre>
@@ -5481,7 +5481,7 @@ options are supported by the package, an
if needed.</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem"><p><code class="varname">PKG_OPTIONS_VAR</code> is the name of 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> variable that the user can
set to override the default
+<a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> variable that the user
can set to override the default
options. It should be set to
PKG_OPTIONS.<em class="replaceable"><code>pkgbase</code></em>. Do not set it to
PKG_OPTIONS.${PKGBASE}, since <code class="varname">PKGBASE</code> is not defined
@@ -5699,7 +5699,7 @@ details.</p>
<code class="varname">USE_IMAKE</code> to be installed correctly under
<code class="varname">LOCALBASE</code>.</p></li>
<li class="listitem"><p>Within <code class="filename">${PREFIX}</code>, packages should
- install files according to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?hier+7.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">hier</span>(7)</span></a>, with the exception that
+ install files according to <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?hier+7.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">hier</span>(7)</span></a>, with the exception that
manual pages go into <code class="filename">${PREFIX}/man</code>, not
<code class="filename">${PREFIX}/share/man</code>.</p></li>
</ul></div>
@@ -5980,9 +5980,9 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
<code class="filename">.gz</code> are uncompressed before they are
applied, files ending in <code class="filename">.orig</code> or
<code class="filename">.rej</code> are ignored. Any special options to
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> can be handed in
<code class="varname">PATCH_DIST_ARGS</code>. See <a class="xref" href="#components.patches" title="11.3.�patches/*">Section�11.3, “<code class="filename">patches/*</code>”</a> for
more details.</p>
-<p>By default <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given
special args to make
+<p>By default <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?patch+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">patch</span>(1)</span></a> is given
special args to make
it fail if the patches apply with some lines of fuzz. Please
fix (regen) the patches so that they apply cleanly. The
rationale behind this is that patches that don't apply cleanly
@@ -6161,7 +6161,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
defined.</p>
<p>In the <span class="emphasis"><em>install</em></span> phase, the following
variables are useful. They are all variations of the
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that
have the owner, group and
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">install</span>(1)</span></a> command that
have the owner, group and
permissions preset. <code class="varname">INSTALL</code> is the plain
install command. The specialized variants, together with their
intended use, are:</p>
@@ -6207,7 +6207,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
<p>Some other variables are:</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="varname">INSTALL_UNSTRIPPED</code></span></dt>
-<dd><p>If set to <code class="literal">yes</code>, do not run <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?strip+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">strip</span>(1)</span></a>
+<dd><p>If set to <code class="literal">yes</code>, do not run <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?strip+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">strip</span>(1)</span></a>
when installing binaries. Any debugging sections and symbols present in
binaries will be preserved.
</p></dd>
@@ -6284,13 +6284,13 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
</dd>
<dt><span class="term">deinstall</span></dt>
<dd>
-<p>This target does a <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> in the
+<p>This target does a <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> in the
current directory, effectively de-installing the
package. The following variables can be used to tune the
behaviour:</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><code class="varname">PKG_VERBOSE</code></span></dt>
-<dd><p>Add a "-v" to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
+<dd><p>Add a "-v" to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> command.</p></dd>
<dt><span class="term"><code class="varname">DEINSTALLDEPENDS</code></span></dt>
<dd><p>Remove all packages that require (depend on)
the given package. This can be used to remove any
@@ -6299,7 +6299,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
DEINSTALLDEPENDS=1</strong></span> is done in
<code class="filename">pkgsrc/x11/kde</code>, this is
likely to remove whole KDE. Works by adding
- <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1";><span
class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
+ <span class="quote">“<span class="quote">-R</span>”</span> to the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1.2";><span
class="citerefentry"><span class="refentrytitle">pkg_delete</span>(1)</span></a>
command line.</p></dd>
</dl></div>
</dd>
@@ -6439,7 +6439,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
<dd>
<p>Update the installation of the current package. This
differs from update in that it does not replace dependent
- packages. You will need to install <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html"; target="_top"><code
class="filename">pkgtools/pkg_tarup</code></a> for this
+ packages. You will need to install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_tarup/README.html"; target="_top"><code
class="filename">pkgtools/pkg_tarup</code></a> for this
target to work.</p>
<p><span class="emphasis"><em>Be careful when using this
target!</em></span> There are no guarantees that dependent
@@ -6451,7 +6451,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
recommended for advanced users.</p>
</dd>
<dt><span class="term">info</span></dt>
-<dd><p>This target invokes <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_info</span>(1)</span></a> for the current
+<dd><p>This target invokes <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_info</span>(1)</span></a> for the current
package. You can use this to check which version of a
package is installed.</p></dd>
<dt><span class="term">index</span></dt>
@@ -6478,7 +6478,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
<dd>
<p>This target generates a
<code class="filename">README.html</code> file, which can be
- viewed using a browser such as <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a> or <a
href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/links/README.html"; target="_top"><code class="filename">www/links</code></a>. The generated files
+ viewed using a browser such as <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/firefox/README.html"; target="_top"><code class="filename">www/firefox</code></a> or <a
href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/links/README.html"; target="_top"><code class="filename">www/links</code></a>. The generated files
contain references to any packages which are in the
<code class="varname">PACKAGES</code> directory on the local
host. The generated files can be made to refer to URLs
@@ -6567,7 +6567,7 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
<code class="filename">PLIST</code>. On upgrades, it's useful to
diff the output of this command against an already
existing <code class="filename">PLIST</code> file.</p>
-<p>If the package installs files via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">tar</span>(1)</span></a> or
+<p>If the package installs files via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">tar</span>(1)</span></a> or
other methods that don't update file access times, be
sure to add these files manually to your
<code class="filename">PLIST</code>, as the <span class="quote">“<span class="quote">find
@@ -6594,12 +6594,12 @@ builds)</i></a>).
<dd>
<p>Used during bulk-installs to install required
packages. If an up-to-date binary package is available,
- it will be installed via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>. If not,
+ it will be installed via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a>. If not,
<span class="command"><strong>make bulk-package</strong></span> will be executed,
but the installed binary won't be removed.</p>
<p>A binary package is considered
<span class="quote">“<span class="quote">up-to-date</span>”</span> to be installed via
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> if:</p>
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">pkg_add</span>(1)</span></a> if:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>None of the package's files
(<code class="filename">Makefile</code>, ...) were modified
@@ -6784,7 +6784,7 @@ TOOLS_PLATFORM.true?= true
variables in the file pointed to by <code class="varname">MAKECONF</code>,
which is <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a> by default. When you
want to use those variables in the preprocessor directives 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> (for example <code
class="literal">.if</code> or
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> (for example <code
class="literal">.if</code> or
<code class="literal">.for</code>), you need to include the file
<code class="filename">../../mk/bsd.prefs.mk</code> before, which in turn
loads the user preferences.</p>
@@ -6862,7 +6862,7 @@ INTERACTIVE_STAGE= configure instal
particular license is done by placing the license in
<code class="filename">pkgsrc/licenses</code> and setting the
<code class="varname">LICENSE</code> variable to a string identifying the
- license, e.g. in <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/xv/README.html"; target="_top"><code class="filename">graphics/xv</code></a>:</p>
+ license, e.g. in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/xv/README.html"; target="_top"><code class="filename">graphics/xv</code></a>:</p>
<pre class="programlisting">
LICENSE= xv-license
</pre>
@@ -7024,7 +7024,7 @@ ACCEPTABLE_LICENSES+=xv-license
</pre>
<p>Please note that the <span class="quote">“<span class="quote">pre-req-package-name</span>”</span>
may include any of the wildcard version numbers recognized by
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_info+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">pkg_info</span>(1)</span></a>.</p>
<div class="orderedlist"><ol class="orderedlist" type="1">
<li class="listitem">
<p>If your package needs another package's binaries or
@@ -7063,7 +7063,7 @@ BUILD_DEPENDS+= scons-[0-9]*:../../devel
correctly and if there's no
<code class="filename">buildlink3.mk</code> file, this is specified
using the <code class="varname">DEPENDS</code> variable. The
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/lyx/README.html"; target="_top"><code class="filename">print/lyx</code></a> package needs to
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/lyx/README.html"; target="_top"><code class="filename">print/lyx</code></a> package needs to
be able to execute the latex binary from the tex-latex-bin package
when it runs, and that is specified:</p>
<pre class="programlisting">
@@ -7100,7 +7100,7 @@ DEPENDS+= ImageMagick>=6.0:../.
<p>If your package needs files from another package to build,
add the relevant distribution files to
<code class="varname">DISTFILES</code>, so they will be extracted
- automatically. See the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/ghostscript/README.html"; target="_top"><code class="filename">print/ghostscript</code></a> package for an
example.
+ automatically. See the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/print/ghostscript/README.html"; target="_top"><code class="filename">print/ghostscript</code></a> package for an
example.
(It relies on the jpeg sources being present in source form
during the build.)</p>
</div>
@@ -7119,8 +7119,8 @@ DEPENDS+= ImageMagick>=6.0:../.
shared files), you can set <code class="varname">CONFLICTS</code> to a
space-separated list of packages (including version string) your
package conflicts with.</p>
-<p>For example, if both <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/bar/README.html"; target="_top"><code class="filename">foo/bar</code></a>
- and <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/baz/README.html"; target="_top"><code class="filename">foo/baz</code></a>
+<p>For example, if both <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/bar/README.html"; target="_top"><code class="filename">foo/bar</code></a>
+ and <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/foo/baz/README.html"; target="_top"><code class="filename">foo/baz</code></a>
use the same config file, you would set in
<code class="filename">foo/bar/Makefile</code>:</p>
<pre class="programlisting">
@@ -7156,7 +7156,7 @@ CONFLICTS= bar-[0-9]*
(OS-version-platform) that can use glob-style
wildcards.</p>
<p>Some packages are tightly bound to a specific version of an
- operating system, e.g. LKMs or <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/lsof/README.html"; target="_top"><code class="filename">sysutils/lsof</code></a>. Such binary
packages are not
+ operating system, e.g. LKMs or <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/lsof/README.html"; target="_top"><code class="filename">sysutils/lsof</code></a>. Such binary
packages are not
backwards compatible with other versions of the OS, and should be
uploaded to a version specific directory on the FTP server. Mark
these packages by setting <code class="varname">OSVERSION_SPECIFIC</code> to
@@ -7178,7 +7178,7 @@ CONFLICTS= bar-[0-9]*
be set in the package Makefile. This will be carried into any
binary package that is made from this pkgsrc entry. A
<span class="quote">“<span class="quote">preserved</span>”</span> package will
- not be deleted using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
+ not be deleted using <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_delete+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">pkg_delete</span>(1)</span></a> unless the
<span class="quote">“<span class="quote">-f</span>”</span> option is used.</p>
</div>
<div class="sect2">
@@ -7311,7 +7311,7 @@ SUBST_SED.fix-paths+= -e 's,"/
substitution will take place. The patterns are interpreted
relatively to the <code class="varname">WRKSRC</code> directory.</p>
<p><code class="varname">SUBST_SED.*</code> is a list of arguments to
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sed+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> that specify the actual
substitution. Every sed
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?sed+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">sed</span>(1)</span></a> that specify the
actual substitution. Every sed
command should be prefixed with <code class="literal">-e</code>, so that
all SUBST blocks look uniform.</p>
<p>There are some more variables, but they are so seldomly
@@ -7330,7 +7330,7 @@ SUBST_SED.fix-paths+= -e 's,"/
fetch</strong></span> will call <code class="filename">files/getsite.sh</code>
with the name of each file to download as an argument, expecting
it to output the URL of the directory from which to download
- it. <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/ns-cult3d/README.html"; target="_top"><code class="filename">graphics/ns-cult3d</code></a> is an
+ it. <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/graphics/ns-cult3d/README.html"; target="_top"><code class="filename">graphics/ns-cult3d</code></a> is an
example of this usage.</p>
<p>If the download can't be automated, because the user must
submit personal information to apply for a password, or must pay
@@ -7438,7 +7438,7 @@ EXTRACT_SUFX= .zip
compiler, linker, etc. to get the Right Thing, which can be
pretty annoying especially if you don't have all the machines
at your hand to test things. The
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool/README.html"; target="_top"><code class="filename">devel/libtool</code></a> pkg
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool/README.html"; target="_top"><code class="filename">devel/libtool</code></a> pkg
can help here, as it just <span class="quote">“<span class="quote">knows</span>”</span> how to build
both static and dynamic libraries from a set of source files,
thus being platform-independent.</p>
@@ -7510,7 +7510,7 @@ dynamic linker chooses the library with
</li>
<li class="listitem">
<p>When linking shared object (<code class="filename">.so</code>)
- files, i.e. files that are loaded via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?dlopen+3.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">dlopen</span>(3)</span></a>, NOT
+ files, i.e. files that are loaded via <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?dlopen+3.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">dlopen</span>(3)</span></a>, NOT
shared libraries, use <span class="quote">“<span class="quote">-module
-avoid-version</span>”</span> to prevent them getting version
tacked on.</p>
@@ -7520,7 +7520,7 @@ dynamic linker chooses the library with
<li class="listitem">
<p>When linking programs that depend on these libraries
<span class="emphasis"><em>before</em></span> they are installed, preface
- the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cc+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a
class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span
class="quote">“<span class="quote">${LIBTOOL}
+ the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cc+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">cc</span>(1)</span></a> or <a
class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> line with <span
class="quote">“<span class="quote">${LIBTOOL}
--mode=link</span>”</span>, and it will find the correct
libraries (static or shared), but please be aware that
libtool will not allow you to specify a relative path in
@@ -7537,8 +7537,8 @@ ${LIBTOOL} --mode=link ${CC} -o <em clas
<p>and it will do the right thing with the libraries.</p>
</li>
<li class="listitem">
-<p>When installing libraries, preface the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">install</span>(1)</span></a>
- or <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cp+1.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span
class="quote">“<span class="quote">${LIBTOOL}
+<p>When installing libraries, preface the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?install+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">install</span>(1)</span></a>
+ or <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?cp+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">cp</span>(1)</span></a> command with <span
class="quote">“<span class="quote">${LIBTOOL}
--mode=install</span>”</span>, and change the library name to
<code class="filename">.la</code>. e.g.</p>
<pre class="programlisting">
@@ -7546,7 +7546,7 @@ ${LIBTOOL} --mode=install ${BSD_INSTALL_
</pre>
<p>This will install the static <code class="filename">.a</code>,
shared library, any needed symlinks, and run
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ldconfig+8.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ldconfig+8.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">ldconfig</span>(8)</span></a>.</p>
</li>
<li class="listitem"><p>In your <code class="filename">PLIST</code>, include only
the <code class="filename">.la</code>
@@ -7959,7 +7959,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2
<code class="filename">${PREFIX}/share/doc/html</code> or other
places.</p>
<p>An exception to the above is that library API documentation
- generated with the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/textproc/gtk-doc/README.html"; target="_top"><code class="filename">textproc/gtk-doc</code></a> tools, for use by
special
+ generated with the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/textproc/gtk-doc/README.html"; target="_top"><code class="filename">textproc/gtk-doc</code></a> tools, for use by
special
browsers (devhelp) should be left at their default location, which
is <code class="filename">${PREFIX}/share/gtk-doc</code>. Such
documentation can be recognized from files ending in
@@ -8138,7 +8138,7 @@ PERL5_PACKLIST= auto/Pg/.packlist
default, a minimum version of 3.12 is required. If the system
does not provide a <span class="command"><strong>makeinfo</strong></span> command or if it
does not match the required minimum, a build dependency on the
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/gtexinfo/README.html"; target="_top"><code class="filename">devel/gtexinfo</code></a> package will
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/gtexinfo/README.html"; target="_top"><code class="filename">devel/gtexinfo</code></a> package will
be added automatically.</p>
<p>The build and installation process of the software provided
by the package should not use the
@@ -8420,7 +8420,7 @@ PERL5_PACKLIST= auto/Pg/.packlist
executables for running binaries from a one operating system
on a different one (if the latter supports it). One example
is running Linux binaries on NetBSD.</p>
-<p>The <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/rpm2pkg/README.html"; target="_top"><code class="filename">pkgtools/rpm2pkg</code></a>
+<p>The <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/rpm2pkg/README.html"; target="_top"><code class="filename">pkgtools/rpm2pkg</code></a>
helps in extracting and packaging Linux rpm packages.</p>
<p>The <code class="varname">CHECK_SHLIBS</code> can be set to no to
avoid the <span class="command"><strong>check-shlibs</strong></span> target, which tests
@@ -8494,7 +8494,7 @@ PERL5_PACKLIST= auto/Pg/.packlist
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>Be sure to set <code class="varname">PKG_DEVELOPER=yes</code> in <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>.</p></li>
<li class="listitem">
-<p>Install <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code class="filename">pkgtools/url2pkg</code></a>,
+<p>Install <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/url2pkg/README.html"; target="_top"><code class="filename">pkgtools/url2pkg</code></a>,
create a directory for a new package, change into it, then run
<span class="command"><strong>url2pkg</strong></span>:</p>
<pre class="screen"><code class="prompt">%</code> <strong class="userinput"><code>mkdir /usr/pkgsrc/<em class="replaceable"><code>category</code></em>/<em
class="replaceable"><code>examplepkg</code></em></code></strong>
@@ -8520,7 +8520,7 @@ PERL5_PACKLIST= auto/Pg/.packlist
are modified that shouldn't be, especially during the build
phase. <span class="command"><strong>mkpatches</strong></span>,
<span class="command"><strong>patchdiff</strong></span> and <span class="command"><strong>pkgvi</strong></span> are
- from the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code class="filename">pkgtools/pkgdiff</code></a>
+ from the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/README.html"; target="_top"><code class="filename">pkgtools/pkgdiff</code></a>
package.</p>
</li>
<li class="listitem"><p>Look at the <code class="filename">Makefile</code>, fix if
@@ -8559,7 +8559,7 @@ PERL5_PACKLIST= auto/Pg/.packlist
</li>
<li class="listitem"><p>Play with it. Make sure everything works.</p></li>
<li class="listitem">
-<p>Run <span class="command"><strong>pkglint</strong></span> from <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code
class="filename">pkgtools/pkglint</code></a>, and fix the problems it
+<p>Run <span class="command"><strong>pkglint</strong></span> from <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code
class="filename">pkgtools/pkglint</code></a>, and fix the problems it
reports:</p>
<pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>pkglint</code></strong></pre>
</li>
@@ -8599,15 +8599,15 @@ builds)</i></a>.</p>
<a name="submitting-your-package"></a>21.2.�Submitting source packages (for non-NetBSD-developers)</h2></div></div></div>
<p>First, check that your package is complete, compiles and
runs well; see <a class="xref" href="#debug" title="Chapter�20.�Debugging">Chapter�20, <i>Debugging</i></a> and the rest of this
- document. Next, generate an uuencoded gzipped <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">tar</span>(1)</span></a>
+ document. Next, generate an uuencoded gzipped <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?tar+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">tar</span>(1)</span></a>
archive that contains all files that make up the package.
Finally, send this package to the pkgsrc bug tracking system,
- either with the <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> command, or if you don't have
+ either with the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">send-pr</span>(1)</span></a> command, or if you don't have
that, go to the web page
<a class="ulink" href="http://www.NetBSD.org/support/send-pr.html"; target="_top">http://www.NetBSD.org/support/send-pr.html</a>,
which contains some instructions and a link to a form where you
can submit packages. The
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/gtk-send-pr/README.html"; target="_top"><code class="filename">sysutils/gtk-send-pr</code></a> package is
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/sysutils/gtk-send-pr/README.html"; target="_top"><code class="filename">sysutils/gtk-send-pr</code></a> package is
also available as a substitute for either of the above two tools.
</p>
<p>In the form of the problem report, the category should be
@@ -8799,7 +8799,7 @@ instead of <span class="quote">“<s
<code class="varname">PREV_PKGPATH</code> to the previous category/package
pathname. The <code class="varname">PREV_PKGPATH</code> can be used by tools
for doing an update using pkgsrc building; for example, it can
-search the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_summary+5.i386+NetBSD-7.1";><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a>
database for <code class="varname">PREV_PKGPATH</code>
+search the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_summary+5.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">pkg_summary</span>(5)</span></a>
database for <code class="varname">PREV_PKGPATH</code>
(if no <code class="varname">SUPERSEDES</code>) and then use the corresponding
new <code class="varname">PKGPATH</code> for that moved package. Note that
it may have multiple matches, so the tool should also check on the
@@ -8835,7 +8835,7 @@ place.</p></li>
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="idm79078192"></a><dl>
+<a name="idm80785232"></a><dl>
<dt>22.1. <a href="#devfaq.makeflags">What is the difference between
MAKEFLAGS, .MAKEFLAGS and
MAKE_FLAGS?</a>
@@ -8880,7 +8880,7 @@ do?</a>
<tbody>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.makeflags"></a><a name="idm79077808"></a><p><b>22.1.</b></p>
+<a name="devfaq.makeflags"></a><a name="idm80784848"></a><p><b>22.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
@@ -8889,14 +8889,14 @@ do?</a>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top"><p><code class="varname">MAKEFLAGS</code> are the flags passed
- 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
+ to the pkgsrc-internal invocations of <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a>, while
<code class="varname">MAKE_FLAGS</code> are the flags that are passed to
the <code class="varname">MAKE_PROGRAM</code> when building the
package. [FIXME: What is .MAKEFLAGS for?]</p></td>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.make"></a><a name="idm79073712"></a><p><b>22.2.</b></p>
+<a name="devfaq.make"></a><a name="idm80780880"></a><p><b>22.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
@@ -8905,7 +8905,7 @@ do?</a>
<tr class="answer">
<td align="left" valign="top"></td>
<td align="left" valign="top"><p><code class="varname">MAKE</code> is the path to 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> program that is
used in the pkgsrc
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">make</span>(1)</span></a> program that is
used in the pkgsrc
infrastructure. <code class="varname">GMAKE</code> is the path to GNU
Make, but you need to say <code class="varname">USE_TOOLS+=gmake</code> to
use that. <code class="varname">MAKE_PROGRAM</code> is the path to the
@@ -8914,7 +8914,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.cc"></a><a name="idm79069360"></a><p><b>22.3.</b></p>
+<a name="devfaq.cc"></a><a name="idm80776400"></a><p><b>22.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
@@ -8932,7 +8932,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3flags"></a><a name="idm79065136"></a><p><b>22.4.</b></p>
+<a name="devfaq.bl3flags"></a><a name="idm80772304"></a><p><b>22.4.</b></p>
</td>
<td align="left" valign="top"><p>What is the difference between
<code class="varname">BUILDLINK_LDFLAGS</code>,
@@ -8945,7 +8945,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.bl3prefix"></a><a name="idm79062960"></a><p><b>22.5.</b></p>
+<a name="devfaq.bl3prefix"></a><a name="idm80770000"></a><p><b>22.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>
@@ -8961,7 +8961,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.master_sites"></a><a name="idm79059888"></a><p><b>22.6.</b></p>
+<a name="devfaq.master_sites"></a><a name="idm80766928"></a><p><b>22.6.</b></p>
</td>
<td align="left" valign="top"><p>What does
<code class="code">${MASTER_SITE_SOURCEFORGE:=package/}</code> mean? I
@@ -8974,7 +8974,7 @@ do?</a>
assignment operator, although it looks like it.
Instead, it is a degenerate form of
<code class="code">${LIST:<em class="replaceable"><code>old_string</code></em>=<em class="replaceable"><code>new_string</code></em>}</code>,
- 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
+ which is documented in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?make+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">make</span>(1)</span></a> man page and which is
commonly used in the form <code class="code">${SRCS:.c=.o}</code>. In the
case of <code class="varname">MASTER_SITE_*</code>,
<em class="replaceable"><code>old_string</code></em> is the empty string and
@@ -8985,7 +8985,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.mailinglists"></a><a name="idm79044784"></a><p><b>22.7.</b></p>
+<a name="devfaq.mailinglists"></a><a name="idm80760016"></a><p><b>22.7.</b></p>
</td>
<td align="left" valign="top"><p>Which mailing lists are there for package
developers?</p></td>
@@ -9003,14 +9003,14 @@ do?</a>
etc.</p></dd>
<dt><span class="term"><a class="ulink" href="http://www.NetBSD.org/mailinglists/index.html#pkgsrc-bugs"; target="_top">pkgsrc-bugs</a></span></dt>
<dd><p>All bug reports in category "pkg" sent with
- <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
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?send-pr+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span class="refentrytitle">send-pr</span>(1)</span></a> appear
here. Please do not report your bugs here
directly; use one of the other mailing
lists.</p></dd>
</dl></div></td>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.documentation"></a><a name="idm79040944"></a><p><b>22.8.</b></p>
+<a name="devfaq.documentation"></a><a name="idm80756304"></a><p><b>22.8.</b></p>
</td>
<td align="left" valign="top"><p>Where is the pkgsrc
documentation?</p></td>
@@ -9058,7 +9058,7 @@ do?</a>
</tr>
<tr class="question">
<td align="left" valign="top">
-<a name="devfaq.too-much-time"></a><a name="idm79034416"></a><p><b>22.9.</b></p>
+<a name="devfaq.too-much-time"></a><a name="idm80749776"></a><p><b>22.9.</b></p>
</td>
<td align="left" valign="top"><p>I have a little time to kill. What shall I
do?</p></td>
@@ -9070,7 +9070,7 @@ do?</p></td>
anyway.</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem"><p>Run <span class="command"><strong>pkg_chk -N</strong></span> (from the
- <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
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_chk/README.html"; target="_top"><code class="filename">pkgtools/pkg_chk</code></a> package). It
will tell you about newer versions of installed packages that are
available, but not yet updated in pkgsrc.</p></li>
<li class="listitem"><p>Browse <code class="filename">pkgsrc/doc/TODO</code>
@@ -9136,14 +9136,14 @@ important information regarding their in
<a name="meta-packages"></a>23.1.�Meta packages</h2></div></div></div>
<p>pkgsrc includes three GNOME-related meta packages:</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>: Provides
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>: Provides
the core GNOME desktop environment. It only includes the necessary
bits to get it to boot correctly, although it may lack important
functionality for daily operation. The idea behind this package is
to let end users build their own configurations on top of this one,
first installing this meta package to achieve a functional setup and
then adding individual applications.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html"; target="_top"><code class="filename">meta-pkgs/gnome</code></a>: Provides a
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome/README.html"; target="_top"><code class="filename">meta-pkgs/gnome</code></a>: Provides a
complete installation of the GNOME platform and desktop as defined
by the GNOME project; this is based on the components distributed in
the <code class="filename">platform/x.y/x.y.z/sources</code> and
@@ -9153,8 +9153,8 @@ important information regarding their in
component to work properly. Similarly, packages from the bindings
set (<code class="filename">bindings/x.y/x.y.z/sources</code>) are not pulled
in unless required as a dependency for an end-user component. This
- package "extends" <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>.</p></li>
-<li class="listitem"><p><a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a>:
+ package "extends" <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-base/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-base</code></a>.</p></li>
+<li class="listitem"><p><a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a>:
Installs all the tools required to build a GNOME component when
fetched from the CVS repository. These are required to let the
<span class="command"><strong>autogen.sh</strong></span> scripts work appropriately.</p></li>
@@ -9189,7 +9189,7 @@ USE_TOOLS+=gmake
<pre class="programlisting">
USE_TOOLS+=pkg-config
</pre>
-<p>Also use <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/verifypc/README.html"; target="_top"><code class="filename">pkgtools/verifypc</code></a> at
+<p>Also use <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/verifypc/README.html"; target="_top"><code class="filename">pkgtools/verifypc</code></a> at
the end of the build process to ensure that you did not miss to
specify any dependency in your package and that the version
requirements are all correct.</p>
@@ -9338,7 +9338,7 @@ followed:</p>
<p>Packages not listed in the <code class="filename">list.txt</code> file
should be updated to the latest version available (if found in
pkgsrc). This is the case, for example, of the dependencies on the
- GNU Autotools in the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a> meta
package.</p>
+ GNU Autotools in the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/gnome-devel/README.html"; target="_top"><code class="filename">meta-pkgs/gnome-devel</code></a> meta
package.</p>
</li>
<li class="listitem">
<p>Generate a patch from the modified meta packages and extract the
@@ -9733,7 +9733,7 @@ CFLAGS+= -Wall
<div class="sect1">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="regression.run"></a>25.1.�Running the regression tests</h2></div></div></div>
-<p>You first need to install the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_regress/README.html"; target="_top"><code class="filename">pkgtools/pkg_regress</code></a>
package, which
+<p>You first need to install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkg_regress/README.html"; target="_top"><code class="filename">pkgtools/pkg_regress</code></a>
package, which
provides the <span class="command"><strong>pkg_regress</strong></span> command. Then you
can simply run that command, which will run all tests in the
<code class="filename">regress</code> category.</p>
@@ -9865,7 +9865,7 @@ output_require "^[[:alpha:]+[[:space:]][
platform and add them.</p></dd>
</dl></div>
<p>Now, you should be able to build some basic packages, like
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/perl5/README.html"; target="_top"><code class="filename">lang/perl5</code></a>, <a
href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html"; target="_top"><code class="filename">shells/bash</code></a>.</p>
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/perl5/README.html"; target="_top"><code class="filename">lang/perl5</code></a>, <a
href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html"; target="_top"><code class="filename">shells/bash</code></a>.</p>
</div>
</div>
</div>
@@ -9919,7 +9919,7 @@ INFO_FILES= yes
<a name="example-descr"></a>A.1.2.�DESCR</h3></div></div></div>
<pre class="programlisting">
GNU version of yacc. Can make re-entrant parsers, and numerous other
-improvements. Why you would want this when Berkeley <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?yacc+1.i386+NetBSD-7.1";><span class="citerefentry"><span
class="refentrytitle">yacc</span>(1)</span></a> is part
+improvements. Why you would want this when Berkeley <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?yacc+1.i386+NetBSD-7.1.2";><span class="citerefentry"><span
class="refentrytitle">yacc</span>(1)</span></a> is part
of the NetBSD source tree is beyond me.
</pre>
</div>
@@ -9939,7 +9939,7 @@ share/bison.hairy
<a name="checking-package-with-pkglint"></a>A.1.4.�Checking a package with <span class="command"><strong>pkglint</strong></span>
</h3></div></div></div>
<p>The NetBSD package system comes with
- <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>
+ <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkglint/README.html"; target="_top"><code class="filename">pkgtools/pkglint</code></a>
which helps to check the contents of these
files. After installation it is quite easy to use, just change to the
directory of the package you wish to examine and execute
@@ -10319,7 +10319,7 @@ source packages</h2></div></div></div>
<li class="step"><p>Make sure you have the packages needed to
regenerate the pkgsrc guide (and other XML-based NetBSD
documentation) installed. These are automatically installed when
- you install the <a href="http://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/pkgsrc-guide-tools/README.html"; target="_top"><code class="filename">meta-pkgs/pkgsrc-guide-tools</code></a>
package.</p></li>
+ you install the <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/pkgsrc-guide-tools/README.html"; target="_top"><code
class="filename">meta-pkgs/pkgsrc-guide-tools</code></a> package.</p></li>
<li class="step"><p>Run <span class="command"><strong>cd doc/guide</strong></span> to get to the
right directory. All further steps will take place
here.</p></li>
Index: pkgsrc/doc/pkgsrc.txt
diff -u pkgsrc/doc/pkgsrc.txt:1.245 pkgsrc/doc/pkgsrc.txt:1.246
--- pkgsrc/doc/pkgsrc.txt:1.245 Mon Nov 27 11:52:49 2017
+++ pkgsrc/doc/pkgsrc.txt Wed Apr 4 10:24:23 2018
@@ -12,9 +12,9 @@ Hubert Feyrer
The pkgsrc Developers
-Copyright 1994-2017 The NetBSD Foundation, Inc
+Copyright 1994-2018 The NetBSD Foundation, Inc
-$NetBSD: pkgsrc.xml,v 1.31 2017/07/30 22:07:39 jnemeth Exp $
+$NetBSD: pkgsrc.xml,v 1.32 2018/01/01 01:26:07 jakllsch Exp $
Abstract
@@ -799,7 +799,7 @@ Before you download any pkgsrc files, yo
current branch or the stable branch. The latter is forked on a quarterly basis
from the current branch and only gets modified for security updates. The names
of the stable branches are built from the year and the quarter, for example
-2017Q3.
+2018Q1.
The second step is to decide how you want to download pkgsrc. You can get it as
a tar file or via CVS. Both ways are described here.
@@ -822,12 +822,12 @@ published at pkgsrc.tar.bz2 and pkgsrc.t
You can fetch the same files using FTP.
-The tar file for the stable branch 2017Q3 is in the directory pkgsrc-2017Q3 and
+The tar file for the stable branch 2018Q1 is in the directory pkgsrc-2018Q1 and
is also called pkgsrc.tar.gz.
To download the latest pkgsrc stable tarball, run:
-$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2017Q3/pkgsrc.tar.gz
+$ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2018Q1/pkgsrc.tar.gz
If you prefer, you can also fetch it using "wget", "curl", or your web browser.
@@ -846,7 +846,7 @@ $ ftp ftp://ftp.NetBSD.org/pub/pkgsrc/cu
To fetch a specific pkgsrc stable branch, run:
-$ cd /usr && cvs -q -z2 -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -r pkgsrc-2017Q3 -P pkgsrc
+$ cd /usr && cvs -q -z2 -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -r pkgsrc-2018Q1 -P pkgsrc
This will create the directory pkgsrc/ in your /usr/ directory and all the
package source will be stored under /usr/pkgsrc/.
@@ -928,7 +928,7 @@ When updating pkgsrc, the CVS program ke
But if you, for whatever reason, want to switch from the stable branch to the
current one, you can do it by adding the option "-A" after the "update"
keyword. To switch from the current branch back to the stable branch, add the "
--rpkgsrc-2017Q3" option.
+-rpkgsrc-2018Q1" option.
2.2.2.2. What happens to my changes when updating?
Home |
Main Index |
Thread Index |
Old Index