summaryrefslogtreecommitdiff
path: root/Packages.txt
diff options
context:
space:
mode:
authorhubertf <hubertf@pkgsrc.org>1998-04-17 21:47:26 +0000
committerhubertf <hubertf@pkgsrc.org>1998-04-17 21:47:26 +0000
commit465ad8f20bee3ee0282eb7b14c8fa5bcc757c04d (patch)
treeb0a598978e12a96a868fcaeaac55633efc2ba1de /Packages.txt
parent0990c9899ddfce1224219c4552f32f1a8c2bb617 (diff)
downloadpkgsrc-465ad8f20bee3ee0282eb7b14c8fa5bcc757c04d.tar.gz
Document getting pkgsrc via sup, minor editing.
Diffstat (limited to 'Packages.txt')
-rw-r--r--Packages.txt24
1 files changed, 15 insertions, 9 deletions
diff --git a/Packages.txt b/Packages.txt
index 44e30bd48f4..c14a0e6aba4 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.26 1998/04/17 10:13:20 agc Exp $
+# $NetBSD: Packages.txt,v 1.27 1998/04/17 21:47:26 hubertf Exp $
###########################################################################
==========================
@@ -170,6 +170,11 @@ 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/pkgsrc.
+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".
+
2.2 Fetching distfiles
======================
@@ -255,14 +260,15 @@ Building, installation and creation of a binary package are all controlled
by the package's Makefile.
There is a Makefile for each package. This file includes the standard
-"../../mk/bsd.pkg.mk" file, which sets all the definitions and actions
-necessary for the package to compile and install itself. The mandatory fields
-are the DISTNAME which specifies the base name of the distribution file to be
-downloaded from the site on the Internet, MASTER_SITES which specifies that
-site, CATEGORIES which denotes the categories into which the package falls,
-PKGNAME which is the name of the package and the MAINTAINER name. This is
-so that anyone who quibbles with the (always completely correct) decisions
-taken by the guy who maintains the port can complain vigorously.
+bsd.pkg.mk file (referenced as "../../mk/bsd.pkg.mk"), which sets all the
+definitions and actions necessary for the package to compile and install
+itself. The mandatory fields are the DISTNAME which specifies the base name
+of the distribution file to be downloaded from the site on the Internet,
+MASTER_SITES which specifies that site, CATEGORIES which denotes the
+categories into which the package falls, PKGNAME which is the name of the
+package and the MAINTAINER name. This is so that anyone who quibbles with
+the (always completely correct) decisions taken by the guy who maintains
+the port can complain vigorously.
Currently the following values are available for CATEGORIES. If more than
one is used, they need to be separated by spaces: