pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc regen
details: https://anonhg.NetBSD.org/pkgsrc/rev/218ea952ea17
branches: trunk
changeset: 641672:218ea952ea17
user: snj <snj%pkgsrc.org@localhost>
date: Fri Nov 14 21:42:29 2014 +0000
description:
regen
diffstat:
doc/pkgsrc.html | 358 +++++++++++++++++++++++++++----------------------------
doc/pkgsrc.txt | 25 +--
2 files changed, 189 insertions(+), 194 deletions(-)
diffs (truncated from 1442 to 300 lines):
diff -r 4c899dacf430 -r 218ea952ea17 doc/pkgsrc.html
--- a/doc/pkgsrc.html Fri Nov 14 21:19:33 2014 +0000
+++ b/doc/pkgsrc.html Fri Nov 14 21:42:29 2014 +0000
@@ -508,13 +508,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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache/README.html"; target="_top"><code class="filename">www/apache</code></a> - The Apache
+<li class="listitem"><p><a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/apache/README.html"; target="_top"><code class="filename">www/apache</code></a> - The Apache
web server</p></li>
-<li class="listitem"><p><a href="ftp://ftp.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="http://ftp.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="ftp://ftp.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="http://ftp.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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html"; target="_top"><code class="filename">meta-pkgs/kde3</code></a> - The K
+<li class="listitem"><p><a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html"; target="_top"><code class="filename">meta-pkgs/kde3</code></a> - The K
Desktop Environment</p></li>
</ul></div>
<p>...just to name a few.</p>
@@ -562,7 +562,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="ftp://ftp.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="http://ftp.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>
@@ -932,14 +932,12 @@
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">2009Q1</code>.</p>
+ <code class="literal">2014Q3</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>
<p>Note that tar archive contains CVS working copy.
Thus you can switch to using CVS at any later time.</p>
-<p>Note also that quarterly branch is not frozen in stone.
- It receives critical updates.</p>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="getting-via-tar"></a>2.1.1. As tar archive</h3></div></div></div>
@@ -960,18 +958,18 @@
respectively.
</p>
<p>You can fetch the same files using FTP.</p>
-<p>The tar file for the stable branch 2013Q1 is in the
- directory <code class="filename">pkgsrc-2013Q1</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2013Q1/pkgsrc.tar.gz"; target="_top"><code
class="filename">pkgsrc.tar.gz</code></a>.</p>
+<p>The tar file for the stable branch 2014Q3 is in the
+ directory <code class="filename">pkgsrc-2014Q3</code> and is also called <a class="ulink" href="ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2014Q3/pkgsrc.tar.gz"; target="_top"><code
class="filename">pkgsrc.tar.gz</code></a>.</p>
<p>To download a pkgsrc stable tarball, run:</p>
<pre class="screen">
<code class="prompt">$</code> <strong class="userinput"><code>ftp ftp://ftp.NetBSD.org/pub/pkgsrc/<em class="replaceable"><code>pkgsrc-20xxQy</code></em>/pkgsrc.tar.gz</code></strong></pre>
<p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the
stable branch to be downloaded, for example,
- <span class="quote">“<span class="quote">pkgsrc-2013Q1</span>”</span>.</p>
-<p>You can use fetch it also using "wget", "curl",
+ <span class="quote">“<span class="quote">pkgsrc-2014Q3</span>”</span>.</p>
+<p>If you prefer, you can also fetch it using "wget", "curl",
or your web browser.</p>
<p>Then, extract it with:</p>
-<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf <em class="replaceable"><code>pkgsrc-20xxQy</code></em>.tar.gz -C /usr</code></strong></pre>
+<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>tar -xzf pkgsrc.tar.gz -C /usr</code></strong></pre>
<p>This will create the directory <code class="filename">pkgsrc/</code>
in <code class="filename">/usr/</code> and all the package source will be
stored under <code class="filename">/usr/pkgsrc/</code>.</p>
@@ -985,14 +983,14 @@
<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 <em
class="replaceable"><code>pkgsrc-20xxQy</code></em> -P pkgsrc</code></strong>
</pre>
<p>Where <em class="replaceable"><code>pkgsrc-20xxQy</code></em> is the stable
- branch to be checked out, for example, <span class="quote">“<span class="quote">pkgsrc-2009Q1</span>”</span></p>
+ branch to be checked out, for example, <span class="quote">“<span class="quote">pkgsrc-2014Q3</span>”</span></p>
<p>This will create the directory <code class="filename">pkgsrc/</code>
in your <code class="filename">/usr/</code> directory and all the package source
will be stored under <code class="filename">/usr/pkgsrc/</code>.</p>
<p>To fetch the pkgsrc current 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 -P pkgsrc</code></strong>
</pre>
-<p>Refer to the <a class="ulink" href="http://www.NetBSD.org/mirrors/"; target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p>
+<p>Refer to the <a class="ulink" href="http://www.NetBSD.org/mirrors/#anoncvs"; target="_top">list of available mirrors</a> to choose a faster CVS mirror, if needed.</p>
<p>If you get error messages from <code class="literal">rsh</code>, you need to set CVS_RSH variable. E.g.:</p>
<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>cd /usr && env CVS_RSH=ssh cvs -q -z2 -d anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot checkout -P
pkgsrc</code></strong>
</pre>
@@ -1042,8 +1040,8 @@
</div>
<p>Note that by default the distfiles and the binary packages
are saved in the pkgsrc tree, so don't forget to rescue them
- before updating. You can also configure pkgsrc to use other than
- the default directories by setting the
+ before updating. You can also configure pkgsrc to store distfiles
+ and packages in directories outside the pkgsrc tree by setting the
<code class="varname">DISTDIR</code> and <code class="varname">PACKAGES</code>
variables. See <a class="xref" href="#configuring" title="Chapter 5. Configuring pkgsrc">Chapter 5, <i>Configuring pkgsrc</i></a> for the details.</p>
<p>To update pkgsrc from a tar file, download the tar file as
@@ -1069,7 +1067,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-2009Q3</span>”</span> option.</p>
+ <span class="quote">“<span class="quote">-rpkgsrc-2014Q3</span>”</span> option.</p>
</div>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
@@ -1372,10 +1370,10 @@
<p>Interix has no native support for audio output. For audio
support, pkgsrc uses the <span class="command"><strong>esound</strong></span> client/server
audio system on Interix. Unlike on most platforms, the
- <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/audio/esound/README.html"; target="_top"><code class="filename">audio/esound</code></a> package does
+ <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/audio/esound/README.html"; target="_top"><code class="filename">audio/esound</code></a> package does
<span class="emphasis"><em>not</em></span> contain the <span class="command"><strong>esd</strong></span>
server component. To output audio via an Interix host, the
- <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/cygwin_esound/README.html"; target="_top"><code class="filename">emulators/cygwin_esound</code></a> package
+ <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/cygwin_esound/README.html"; target="_top"><code class="filename">emulators/cygwin_esound</code></a> package
must also be installed.</p>
</li>
<li class="listitem">
@@ -1423,7 +1421,7 @@
according to your preference. If you do not have a license for the MIPSpro
compiler suite, you can download a gcc tardist file from <a class="ulink" href="http://freeware.sgi.com/"; target="_top">http://freeware.sgi.com/</a>.</p>
<p>Please note that you will need IRIX 6.5.17 or higher, as this is the earliest
- version of IRIX providing support for <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_indextoname+3+NetBSD-5.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">if_indextoname</span>(3)</span></a>, <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_nametoindex+3+NetBSD-5.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">if_nametoindex</span>(3)</span></a>,
+ version of IRIX providing support for <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_indextoname+3+NetBSD-6.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">if_indextoname</span>(3)</span></a>, <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?if_nametoindex+3+NetBSD-6.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">if_nametoindex</span>(3)</span></a>,
etc.</p>
<p>At this point in time, pkgsrc only supports one ABI at a time. That is, you cannot
switch between the old 32-bit ABI, the new 32-bit ABI and the 64-bit ABI. If
@@ -1496,7 +1494,7 @@
provided by icc, so binaries can be run on other systems which do not
have the shared libraries installed.</p>
<p>Libtool, however, extracts a list of libraries from the
- <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-5.0.1+i386";><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> command run when
linking a C++ shared library and
+ <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-6.0.1+i386";><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> command run when
linking a C++ shared library and
records it, throwing away the -Bstatic and -Bdynamic options
interspersed between the libraries. This means that
libtool-linked C++ shared libraries will have a runtime
@@ -1595,7 +1593,7 @@
for building all packages.</p>
<p>It is recommended that an external gcc be used only for bootstrapping,
then either build gcc from
- <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/gcc46/README.html"; target="_top"><code class="filename">lang/gcc46</code></a> or install a binary gcc
+ <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/gcc46/README.html"; target="_top"><code class="filename">lang/gcc46</code></a> or install a binary gcc
package, then remove gcc used during bootstrapping.</p>
<p>Binary packages of gcc can be found through <a class="ulink" href="http://www.sunfreeware.com/"; target="_top">http://www.sunfreeware.com/</a>.</p>
</div>
@@ -1651,13 +1649,13 @@
<p>Sometimes, when using <span class="command"><strong>libtool</strong></span>,
<code class="filename">/bin/ksh</code> crashes with a segmentation fault.
The workaround is to use another shell for the configure
- scripts, for example by installing <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html"; target="_top"><code class="filename">shells/bash</code></a> and adding the
following lines
+ scripts, for example by installing <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html"; target="_top"><code class="filename">shells/bash</code></a> and adding the
following lines
to your <a class="link" href="#mk.conf"><code class="filename">mk.conf</code></a>:</p>
<pre class="programlisting">
CONFIG_SHELL= ${LOCALBASE}/bin/bash
WRAPPER_SHELL= ${LOCALBASE}/bin/bash
</pre>
-<p>Then, rebuild the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool-base/README.html"; target="_top"><code class="filename">devel/libtool-base</code></a> package.</p>
+<p>Then, rebuild the <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool-base/README.html"; target="_top"><code class="filename">devel/libtool-base</code></a> package.</p>
</div>
</div>
</div>
@@ -1831,7 +1829,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">crontab</span>(5)</span></a> entry. For example the entry
</p>
<pre class="screen">
# download vulnerabilities file
@@ -1855,7 +1853,7 @@
<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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/lintpkgsrc/README.html"; target="_top"><code class="filename">pkgtools/lintpkgsrc</code></a> and run
+ Install <a href="http://ftp.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>
@@ -1878,7 +1876,7 @@
<div class="titlepage"><div><div><h3 class="title">
<a name="a-word-of-warning"></a>4.1.8. A word of warning</h3></div></div></div>
<p>Please pay very careful attention to the warnings
- expressed in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-5.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a> manual page about the
+ expressed in the <a class="citerefentry" href="http://netbsd.gw.com/cgi-bin/man-cgi?pkg_add+1+NetBSD-6.0.1+i386";><span class="citerefentry"><span
class="refentrytitle">pkg_add</span>(1)</span></a> manual page about the
inherent dangers of installing binary packages which you did
not create yourself, and the security holes that can be
introduced onto your system by indiscriminate adding of such
@@ -1898,7 +1896,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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html"; target="_top"><code class="filename">www/lynx</code></a> or <a
href="ftp://ftp.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="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/lynx/README.html"; target="_top"><code class="filename">www/lynx</code></a> or <a
href="http://ftp.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
@@ -1956,7 +1954,7 @@
and adding the definitions there.</p>
<p>
If a package depends on many other packages (such as
- <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html"; target="_top"><code class="filename">meta-pkgs/kde3</code></a>), the build process may
+ <a href="http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/meta-pkgs/kde3/README.html"; target="_top"><code class="filename">meta-pkgs/kde3</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:
@@ -2054,7 +2052,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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>
@@ -2062,10 +2060,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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>
@@ -2078,11 +2076,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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>
@@ -2121,7 +2119,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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>
@@ -2275,7 +2273,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><span class="citerefentry"><span class="refentrytitle">su</span>(1)</span></a>
</p>
<pre class="programlisting">
@@ -2365,7 +2363,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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/cpuflags/README.html"; target="_top"><code class="filename">devel/cpuflags</code></a>
+ at the <a href="http://ftp.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>
@@ -2505,7 +2503,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+NetBSD-5.0.1+i386";><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+NetBSD-6.0.1+i386";><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>
@@ -2522,7 +2520,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="ftp://ftp.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="http://ftp.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>
@@ -2672,7 +2670,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="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/cdpack/README.html"; target="_top"><code class="filename">pkgtools/cdpack</code></a> package provides
+ <a href="http://ftp.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
@@ -2930,70 +2928,70 @@
they might be useful, and not to duplicate the documentation that comes
Home |
Main Index |
Thread Index |
Old Index