pkgsrc-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[pkgsrc/trunk]: pkgsrc/doc/guide/files Use &cprompt;. Do not mention not-exis...



details:   https://anonhg.NetBSD.org/pkgsrc/rev/9e4ead2185d6
branches:  trunk
changeset: 518594:9e4ead2185d6
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Wed Sep 13 23:39:07 2006 +0000

description:
Use &cprompt;. Do not mention not-existing INET_COUNTRY.
Describe MASTER_SORT and MASTER_SORT_REGEX.

diffstat:

 doc/guide/files/using.xml |  844 +++++++++++++++++++++++----------------------
 1 files changed, 430 insertions(+), 414 deletions(-)

diffs (truncated from 950 to 300 lines):

diff -r a41128679f1d -r 9e4ead2185d6 doc/guide/files/using.xml
--- a/doc/guide/files/using.xml Wed Sep 13 23:38:21 2006 +0000
+++ b/doc/guide/files/using.xml Wed Sep 13 23:39:07 2006 +0000
@@ -1,516 +1,532 @@
-<!-- $NetBSD: using.xml,v 1.25 2006/09/10 19:33:05 wiz Exp $ -->
+<!-- $NetBSD: using.xml,v 1.26 2006/09/13 23:39:07 wiz Exp $ -->
 
 <chapter id="using"> <?dbhtml filename="using.html"?>
 <title>Using pkgsrc</title>
 
-       <para>Basically, there are two ways of using pkgsrc. The first
-       is to only install the package tools and to use binary packages
-       that someone else has prepared. This is the <quote>pkg</quote>
-       in pkgsrc. The second way is to install the <quote>src</quote>
-       of pkgsrc, too. Then you are able to build your own packages,
-       and you can still use binary packages from someone else.</para>
+<para>Basically, there are two ways of using pkgsrc. The first
+is to only install the package tools and to use binary packages
+that someone else has prepared. This is the <quote>pkg</quote>
+in pkgsrc. The second way is to install the <quote>src</quote>
+of pkgsrc, too. Then you are able to build your own packages,
+and you can still use binary packages from someone else.</para>
 
 <sect1 id="using-pkg">
-<title>Using binary packages</title>
+  <title>Using binary packages</title>
 
-       <para>To use binary packages, you need some tools to manage
-       them. On NetBSD, these tools are already installed. On all other
-       operating systems, you need to install them first. For the
-       following platforms, prebuilt versions of the package tools
-       are available and can simply be downloaded and unpacked in the
-       <filename>/</filename> directory:</para>
+  <para>To use binary packages, you need some tools to manage
+  them. On NetBSD, these tools are already installed. On all other
+  operating systems, you need to install them first. For the
+  following platforms, prebuilt versions of the package tools
+  are available and can simply be downloaded and unpacked in the
+  <filename>/</filename> directory:</para>
 
-       <informaltable id="binary-bootstrap-kits">
-       <tgroup cols="2">
-       <thead><row><entry>Platform</entry><entry>URL</entry></row></thead>
-       <tbody>
+  <informaltable id="binary-bootstrap-kits">
+    <tgroup cols="2">
+      <thead><row><entry>Platform</entry><entry>URL</entry></row></thead>
+      <tbody>
        <row><entry>Solaris 9</entry><entry><filename>ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/bootstrap-pkgsrc/</filename></entry></row>
        <row><entry>Solaris 10</entry><entry><filename>http://public.enst.fr/pkgsrc/packages/bootstrap-pkgsrc/</filename></entry></row>
-       </tbody>
-       </tgroup>
-       </informaltable>
+      </tbody>
+    </tgroup>
+  </informaltable>
 
-       <para>These pre-built package tools use
-       <filename>/usr/pkg</filename> for the base directory, and
-       <filename>/var/db/pkg</filename> for the database of installed
-       packages. If you cannot use these directories for whatever
-       reasons (maybe because you're not root), you have to build the
-       package tools yourself, which is explained in <xref
-       linkend="bootstrapping-pkgsrc" />.</para>
+  <para>These pre-built package tools use
+  <filename>/usr/pkg</filename> for the base directory, and
+  <filename>/var/db/pkg</filename> for the database of installed
+  packages. If you cannot use these directories for whatever
+  reasons (maybe because you're not root), you have to build the
+  package tools yourself, which is explained in <xref
+  linkend="bootstrapping-pkgsrc" />.</para>
 
-<sect2 id="finding-binary-packages">
-<title>Finding binary packages</title>
+  <sect2 id="finding-binary-packages">
+    <title>Finding binary packages</title>
 
-       <para>To install binary packages, you first need to know from
-       where to get them. You can get them on CD-ROMs, DVDs, or via FTP
-       or HTTP.</para>
+    <para>To install binary packages, you first need to know from
+    where to get them. You can get them on CD-ROMs, DVDs, or via FTP
+    or HTTP.</para>
 
-       <para>The binary packages can be found at the following
-       locations.</para>
+    <para>The binary packages can be found at the following
+    locations.</para>
 
-       <informaltable id="binary-packages">
-       <tgroup cols="2">
+    <informaltable id="binary-packages">
+      <tgroup cols="2">
        <thead><row><entry>Platform</entry><entry>URL</entry></row></thead>
        <tbody>
-       <row><entry>NetBSD</entry><entry><filename>ftp://ftp.NetBSD.org/pub/NetBSD/packages/</filename></entry></row>
-       <row><entry>Solaris 9</entry><entry><filename>ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/</filename></entry></row>
-       <row><entry>Solaris 10</entry><entry><filename>http://public.enst.fr/pkgsrc/packages/</filename></entry></row>
+         <row><entry>NetBSD</entry><entry><filename>ftp://ftp.NetBSD.org/pub/NetBSD/packages/</filename></entry></row>
+         <row><entry>Solaris 9</entry><entry><filename>ftp://ftp0.mh.bbc.co.uk/pub/pkgsrc/packages/</filename></entry></row>
+         <row><entry>Solaris 10</entry><entry><filename>http://public.enst.fr/pkgsrc/packages/</filename></entry></row>
        </tbody>
-       </tgroup>
-       </informaltable>
+      </tgroup>
+    </informaltable>
 
-       <para>Most of these directories contain binary packages for
-       multiple platforms. Select the appropriate subdirectories,
-       according to your machine architecture and operating system,
-       until you find a directory called <filename>All</filename>. This
-       directory contains all the binary packages. Further, there are
-       subdirectories for categories that contain symbolic links that
-       point to the actual binary package in
-       <filename>../All</filename>. This directory layout is used for
-       all package repositories, no matter if they are accessed via
-       HTTP, FTP, NFS, CD-ROM, or the local filesystem.</para>
+    <para>Most of these directories contain binary packages for
+    multiple platforms. Select the appropriate subdirectories,
+    according to your machine architecture and operating system,
+    until you find a directory called <filename>All</filename>. This
+    directory contains all the binary packages. Further, there are
+    subdirectories for categories that contain symbolic links that
+    point to the actual binary package in
+    <filename>../All</filename>. This directory layout is used for
+    all package repositories, no matter if they are accessed via
+    HTTP, FTP, NFS, CD-ROM, or the local filesystem.</para>
 
-</sect2>
-<sect2 id="installing-binary-packages">
-<title>Installing binary packages</title>
+  </sect2>
+  <sect2 id="installing-binary-packages">
+    <title>Installing binary packages</title>
 
-      <para>If you have the files on a CD-ROM or downloaded them to
-        your hard disk, you can install them with the following command
-        (be sure to <command>su</command> to root first):</para>
+    <para>If you have the files on a CD-ROM or downloaded them to
+    your hard disk, you can install them with the following command
+    (be sure to <command>su</command> to root first):</para>
 
-        <screen><prompt>#</prompt> <userinput>pkg_add /path/to/package.tgz</userinput></screen>
+    <screen>&rprompt; <userinput>pkg_add /path/to/package.tgz</userinput></screen>
 
-      <para>If you have FTP access and you don't want to download the
-        packages via FTP prior to installation, you can do this
-        automatically by giving <command>pkg_add</command> an FTP URL:</para>
+    <para>If you have FTP access and you don't want to download the
+    packages via FTP prior to installation, you can do this
+    automatically by giving <command>pkg_add</command> an FTP URL:</para>
 
-      <screen><prompt>#</prompt> <userinput>pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/All/package</userinput></screen>
+    <screen>&rprompt; <userinput>pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/All/package</userinput></screen>
 
-      <para>Note that any prerequisite packages needed to run the
-        package in question will be installed, too, assuming they are
-        present where you install from.</para>
+    <para>Note that any prerequisite packages needed to run the
+    package in question will be installed, too, assuming they are
+    present where you install from.</para>
 
-      <para>To save some typing, you can set the
-        <varname>PKG_PATH</varname> environment variable to a semicolon-separated
-       list of paths (including remote URLs); trailing slashes are not allowed.
-       </para>
+    <para>To save some typing, you can set the
+    <varname>PKG_PATH</varname> environment variable to a semicolon-separated
+    list of paths (including remote URLs); trailing slashes are not allowed.
+    </para>
 
-      <para>Additionally to the <filename>All</filename> directory
-        there exists a <filename>vulnerable</filename> directory to
-        which binary packages with known vulnerabilities are
-        moved, since removing them could cause missing dependencies. To
-        use these packages, add the <filename>vulnerable</filename>
-        directory to your <varname>PKG_PATH</varname>. However, you should run
-        <filename role="pkg">security/audit-packages</filename> regularly,
-       especially after installing new packages, and verify that the
-       vulnerabilities are acceptable for your configuration. An example
-        <varname>PKG_PATH</varname> would be:
-      <filename>ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/vulnerable</filename>
-        Please note that semicolon (';') is a shell meta-character, so
-        you'll probably have to quote it.</para>
+    <para>Additionally to the <filename>All</filename> directory
+    there exists a <filename>vulnerable</filename> directory to
+    which binary packages with known vulnerabilities are
+    moved, since removing them could cause missing dependencies. To
+    use these packages, add the <filename>vulnerable</filename>
+    directory to your <varname>PKG_PATH</varname>. However, you should run
+    <filename role="pkg">security/audit-packages</filename> regularly,
+    especially after installing new packages, and verify that the
+    vulnerabilities are acceptable for your configuration. An example
+    <varname>PKG_PATH</varname> would be:
+    <filename>ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/&lt;OSVERSION&gt;/&lt;ARCH&gt;/vulnerable</filename>
+    Please note that semicolon (';') is a shell meta-character, so
+    you'll probably have to quote it.</para>
 
-      <para>After you've installed packages, be sure to have
-        <filename>/usr/pkg/bin</filename> and <filename>/usr/pkg/sbin</filename> in your
-        <varname>PATH</varname> so you can actually start the just
-        installed program.</para>
-    </sect2>
+    <para>After you've installed packages, be sure to have
+    <filename>/usr/pkg/bin</filename> and <filename>/usr/pkg/sbin</filename> in your
+    <varname>PATH</varname> so you can actually start the just
+    installed program.</para>
+  </sect2>
 
-<sect2 id="using.pkg_delete">
-<title>Deinstalling packages</title>
+  <sect2 id="using.pkg_delete">
+    <title>Deinstalling packages</title>
 
-       <para>To deinstall a package, it does not matter whether it was
-       installed from source code or from a binary package. The
-       <command>pkg_delete</command> command does not know it anyway.
-       To delete a package, you can just run <command>pkg_delete
-       <replaceable>package-name</replaceable></command>. The package
-       name can be given with or without version number. Wildcards can
-       also be used to deinstall a set of packages, for example
-       <literal>*emacs*</literal>. Be sure to include them in quotes,
-       so that the shell does not expand them before
-       <literal>pkg_delete</literal> sees them.</para>
+    <para>To deinstall a package, it does not matter whether it was
+    installed from source code or from a binary package. The
+    <command>pkg_delete</command> command does not know it anyway.
+    To delete a package, you can just run <command>pkg_delete
+    <replaceable>package-name</replaceable></command>. The package
+    name can be given with or without version number. Wildcards can
+    also be used to deinstall a set of packages, for example
+    <literal>*emacs*</literal>. Be sure to include them in quotes,
+    so that the shell does not expand them before
+    <literal>pkg_delete</literal> sees them.</para>
 
-       <para>The <option>-r</option> option is very powerful: it
-       removes all the packages that require the package in question
-       and then removes the package itself. For example:
+    <para>The <option>-r</option> option is very powerful: it
+    removes all the packages that require the package in question
+    and then removes the package itself. For example:
+
+    <screen>
+&rprompt; <userinput>pkg_delete -r jpeg</userinput>
+    </screen>
 
-<screen>
-    &rprompt; <userinput>pkg_delete -r jpeg</userinput>
-</screen>
+    will remove jpeg and all the packages that used it; this allows
+    upgrading the jpeg package.</para>
+
+  </sect2>
 
-       will remove jpeg and all the packages that used it; this allows
-       upgrading the jpeg package.</para>
+  <sect2 id="using.pkg_info">
+    <title>Getting information about installed packages</title>
 
-</sect2>
+    <para>The <command>pkg_info</command> shows information about
+    installed packages or binary package files.</para>
 
-<sect2 id="using.pkg_info">
-<title>Getting information about installed packages</title>
+  </sect2>
+
+  <sect2 id="vulnerabilities">
+    <title>Checking for security vulnerabilities in installed packages</title>
 
-       <para>The <command>pkg_info</command> shows information about
-       installed packages or binary package files.</para>
-
-</sect2>
-
-<sect2 id="vulnerabilities">
-<title>Checking for security vulnerabilities in installed packages</title>
+    <para>
+      The NetBSD Security-Officer and Packages Groups maintain a list of
+      known security vulnerabilities to packages which are (or have been)
+      included in pkgsrc.  The list is available from the NetBSD
+      FTP site at <ulink url="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities"/>.
+    </para>
 
-<para>
-The NetBSD Security-Officer and Packages Groups maintain a list of
-known security vulnerabilities to packages which are (or have been)
-included in pkgsrc.  The list is available from the NetBSD
-FTP site at <ulink url="ftp://ftp.NetBSD.org/pub/pkgsrc/distfiles/vulnerabilities"/>.
-</para>
+    <para>
+      Through <filename role="pkg">security/audit-packages</filename>, 
+      this list can be downloaded
+      automatically, and a security audit of all packages installed on a system
+      can take place.
+    </para>
 
-<para>
-Through <filename role="pkg">security/audit-packages</filename>, 
-this list can be downloaded



Home | Main Index | Thread Index | Old Index