[pkgsrc/trunk]: pkgsrc Bang bang, you're dead - point to the new location

[hubertf <hubertf%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/e0f2983e954a
branches:  trunk
changeset: 483850:e0f2983e954a
user:      hubertf <hubertf%pkgsrc.org@localhost>
date:      Sat Nov 20 12:25:27 2004 +0000

description:
Bang bang, you're dead - point to the new location

diffstat:

 Packages.txt |  3860 +---------------------------------------------------------
 1 files changed, 5 insertions(+), 3855 deletions(-)

diffs (truncated from 3867 to 300 lines):

diff -r 27bb436cd965 -r e0f2983e954a Packages.txt
--- a/Packages.txt      Sat Nov 20 10:10:35 2004 +0000
+++ b/Packages.txt      Sat Nov 20 12:25:27 2004 +0000
@@ -1,3858 +1,8 @@
-# $NetBSD: Packages.txt,v 1.363 2004/11/19 18:39:14 peter Exp $
+# $NetBSD: Packages.txt,v 1.364 2004/11/20 12:25:27 hubertf Exp $
 ###########################################################################
 
-                       ==========================
-                          Documentation on the
-                          NetBSD Package System
-                       ==========================
-
-                     Hubert Feyrer, Alistair Crooks
-
-
-Table of contents:
-==================
-
-Run this command to produce a table of contents:
- sed '/^.====/{g;p;};h;d' Packages.txt
-
-
- 0 Intro
- =======
-
-There is a lot of software freely available for Unix based systems, which
-usually runs on NetBSD, too, sometimes with some modifications. The NetBSD
-packages collection incorporates any such changes necessary to make that
-software run on NetBSD, and makes the installation (and re-installation) of
-the software package easy by means of a single command.
-
-The NetBSD package system is used to enable such freely available
-third-party software to be built easily on NetBSD hosts. Once the software
-has been built, it is manipulated with the pkg_* tools so that installation
-and de-installation, printing of an inventory of all installed packages and
-retrieval of one-line comments or more verbose descriptions are all simple.
-
-Both the NetBSD packages collection and the NetBSD package system are
-derived from FreeBSD.
-
-
- 0.1 Overview
- ============
-
-This document is divided into two parts.  The first, "User's Guide",
-describes how one can use one of the packages in the Package
-Collection, either by installing a precompiled binary package, or
-by building one's copy using the NetBSD package system.  The
-second part, "Package Constructor's Guide", explains how to prepare
-a package so it can be easily built by other NetBSD users without
-knowing about the package's building details.
-
-
- 0.2 Terminology
- ===============
-
-There has been a lot of talk about "ports", "packages", etc. so far. Here
-is a description of all the terminology used within this document:
-
- * Package:
-   A set of files and building instructions that describe what's necessary
-   to build a certain piece of software using the NetBSD package
-   system. Packages are traditionally stored under /usr/pkgsrc.
-
- * The NetBSD package system:
-   This is the part of the NetBSD operating system handling building
-   (compiling), installing, and removing of packages.
-
- * Distfile:
-   This term describes the file or files that are provided by the author
-   of the piece of freely available software to distribute his work. All
-   the changes necessary to build on NetBSD are reflected in the
-   corresponding package. Usually the distfile is in the form of a
-   compressed tar-archive, but other types are possible, too. Distfiles
-   are stored below /usr/pkgsrc/distfiles.
-
- * Port:
-   This is the term used by FreeBSD people for what we call a package.
-   In NetBSD terminology, "port" refers to a different architecture.
-
- * Precompiled (binary) package:
-   A set of binaries built by the NetBSD package system from a distfile
-   using the NetBSD package system and stuffed together in a single .tgz
-   file so it can be installed on machines of the same machine architecture
-   without the need to recompile. Packages are generated in
-   /usr/pkgsrc/packages by the NetBSD package system; there is also an
-   archive on ftp.NetBSD.org.
-
-   Sometimes, this is referred to by the term "package" too,
-   especially in the context of precompiled packages.
-
- * Program:
-   The piece of software to be installed which will be constructed from
-   all the files in the Distfile by the actions defined in the
-   corresponding package.
-
- * NetBSD RCS IDs:
-   Some files in a package contain RCS IDs to reflect which version of
-   that file this is (inserted automatically by cvs). These IDs are used
-   in several examples within this document, but as this document itself
-   is managed by CVS, it can't list the RCS IDs in plaintext. Instead, the
-   $s are written as <$>, resulting in <$>NetBSD<$> and <$>Id<$>.
-
-
- 0.3 Typography
- ==============
-
-Right now this document is written in plain ASCII text, and there's not
-much typography applied here. It's being moved to DocBook.
-
-When giving examples for commands, shell prompts are used to show if the
-command should/can be issued as root, or if "normal" user privileges are
-sufficient. We use a "#" for root's shell prompt, and a "%" for users'
-shell prompt, assuming they use the C-shell or tcsh.
-
-
-====================
-Part I: User's Guide
-====================
-
- 1 Installing a precompiled binary package
- =========================================
-
-This section describes how to find, retrieve and install a precompiled
-binary package that someone else already prepared for your type of machine.
-
-
- 1.1 Where to get
- ================
-
-Precompiled packages are stored on ftp.NetBSD.org and its mirrors in the
-directory /pub/NetBSD/packages for anon FTP access. Please pick the right
-subdirectory there as indicated by "uname -p". In that directory, there
-is a subdirectory for each category plus a subdirectory "All" which includes
-the actual binaries in .tgz-files. The category subdirectories use symbolic
-links to those files. (This is the same directory layout as in
-/usr/pkgsrc/packages).
-
-This same directory layout applies for CDROM distributions, only that the
-directory may be rooted somewhere else, probably somewhere below /cdrom.
-Please consult your CDROM's documentation for the exact location!
-
-
- 1.2 How to use
- ==============
-
-If you have the files on a CDROM or downloaded them to your hard disk, you
-can install them with the following command (be sure to su to root first):
-
-       # pkg_add /path/to/package.tgz
-
-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 pkg_add an
-ftp-URL:
-
-       # pkg_add ftp://ftp.NetBSD.org/pub/NetBSD/packages/<OS Ver>/<arch>/All/package.tgz
-
-If there is any doubt, the uname utility can be used to determine the
-<OS Ver>, and <arch> by running "uname -rp".
-
-Also note that any prerequisite packages needed to run the package in
-question will be installed, too, assuming they are present where you install
-from.
-
-After you've installed packages, be sure to have /usr/pkg/bin in your $PATH
-so you can actually start the just installed program.
-
-
- 1.3 A word of warning
- =====================
-
-Please pay very careful attention to the warnings expressed in that 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 files.
-
-
- 2 Installing by Building
- ========================
-
-This assumes that the package is already part of the NetBSD package system.
-If it is not, then you are advised to read part II of this document,
-"Package Constructor's Guide".
-
-
- 2.1 Requirements
- ================
-
-To build packages from source on a NetBSD system the "comp" and the "text"
-distribution sets must be installed. If you want to build X11 related
-packages the "xbase" and "xcomp" distribution sets are required, too.
-
-
- 2.2 Where to get pkgsrc
- =======================
-
-There are three ways to get pkgsrc. Either as a tar file, via SUP, or
-via CVS. All three ways are described here.
-
-To get the package source going, you need to get the pkgsrc.tar.gz file
-from ftp://ftp.NetBSD.org/pub/NetBSD-current/tar_files/pkgsrc.tar.gz and
-unpack it into /usr.
-
-As an alternative, you can get pkgsrc via the Software Update Protocol,
-SUP. To do so, make sure your supfile has a line saying "release=pkgsrc" in
-it, see the examples in /usr/share/examples/supfiles, and that the
-directory /usr/pkgsrc does exist. Then, simply start "sup -v
-/path/to/your/supfile".
-
-To get pkgsrc via CVS, make sure you have cvs installed. If not present on
-your system, it can be found as precompiled binary on ftp.NetBSD.org.
-To do an initial (full) checkout of pkgsrc, do the following steps:
-
-       % setenv CVSROOT anoncvs%anoncvs.NetBSD.org@localhost:/cvsroot
-       % setenv CVS_RSH ssh
-       % cd /usr
-       % cvs checkout -P pkgsrc
-
-This will create the "pkgsrc" directory in your /usr, and all the
-package source will be stored under /usr/pkgsrc.  To update pkgsrc
-after the initial checkout, make sure you have CVS_RSH set as above,
-then do:
-
-       % cd /usr/pkgsrc
-       % cvs -q update -dP
-
-Please also note that it is possible to have multiple copies of the
-pkgsrc hierarchy in use at any one time - all work is done relatively
-within the pkgsrc tree.
-
-
- 2.3 Fetching distfiles
- ======================
-
-There is one gotcha: The distribution file (i.e. the unmodified source)
-must exist on your system for the packages system to be able to build it.
-If it does not, then ftp(1) is used to fetch the distribution files
-automatically.
-
-You can overwrite some of the major distribution sites to fit to sites
-that are close to your own.  Have a look at
-pkgsrc/mk/bsd.pkg.defaults.mk to find some examples - in particular,
-look for the MASTER_SORT, MASTER_SORT_REGEX and INET_COUNTRY
-definitions.  This may save some of your bandwidth and time.
-
-You can change these settings either in your shell's environment, or,
-if you want to keep the settings, by editing the /etc/mk.conf file,
-and adding the definitions there.
-
-If you don't have a permanent Internet connection and you want to know
-which files to download, "make fetch-list" will tell you what you'll need.
-Put these distfiles into /usr/pkgsrc/distfiles.
-
-
- 2.4 How to build and install
- ============================
-
-Assuming that the distfile has been fetched (see previous section), become
-root and change into the relevant directory. Then you can type
-
-       % make
-
-at the shell prompt to build the various components of the package, and
-
-       # make install
-
-at the shell prompt to install the various components into the correct
-places on your system.
-
-Taking the top system utility as an example, we can install it on our
-system by building as shown in appendix A.1.
-
-The program is installed under the default root of the packages tree -
-/usr/pkg. Should this not conform to your tastes, simply set the LOCALBASE
-variable in your environment, and it will use that value as the root of
-your packages tree. So, to use /usr/local, set
-
-       LOCALBASE=/usr/local
-
-in your environment.  Please note that you should use a root which is
-dedicated to packages and not shared with other programs (ie, do not try
-and use LOCALBASE=/usr).  Also, you should not try to add any of your
-own files or directories (such as, for example, src, obj, or pkgsrc) below
-the LOCALBASE tree.  This is to prevent possible conflicts between programs
-and other files installed by the package system and whatever else may have
-been installed there.
-
-There is, of course, one exception to this - X11 packages are traditionally
-installed in the X11 tree. The definition used to identify the root of the
-X11 tree is the X11BASE definition.
-
-It is possible to install X11 packages in the LOCALBASE tree, for
-which you must install the xpkgwedge package
-(pkgsrc/pkgtools/xpkgwedge) - see section 7.1 for further details.
-
-Some packages look in /etc/mk.conf to alter some configuration options
-at build time.  Have a look at pkgsrc/mk/bsd.pkg.defaults.mk to
-get an overview of what will be set there by default.  Environment
-variables such as LOCALBASE, and X11BASE can be set in /etc/mk.conf to