pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc doc/pkgsrc.*: regen
details: https://anonhg.NetBSD.org/pkgsrc/rev/8001fc640171
branches: trunk
changeset: 378235:8001fc640171
user: leot <leot%pkgsrc.org@localhost>
date: Wed Apr 04 10:24:23 2018 +0000
description:
doc/pkgsrc.*: regen
diffstat:
doc/pkgsrc.html | 318 ++++++++++++++++++++++++++++----------------------------
doc/pkgsrc.txt | 16 +-
2 files changed, 167 insertions(+), 167 deletions(-)
diffs (truncated from 1274 to 300 lines):
diff -r 7206eae483bc -r 8001fc640171 doc/pkgsrc.html
--- a/doc/pkgsrc.html Wed Apr 04 10:23:17 2018 +0000
+++ b/doc/pkgsrc.html Wed Apr 04 10:24:23 2018 +0000
@@ -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 @@
<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 @@
— 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 @@
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 @@
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 @@
<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 @@
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 @@
<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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
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 @@
<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 @@
<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 @@
<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 @@
<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 @@
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 @@
<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 @@
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; ">
Home |
Main Index |
Thread Index |
Old Index