+ correct a spelling mistake.

+ remind developers about one of the more common (and far-reaching)
problems of "cvs import", namely that files relative to the $cwd are
imported, and the given pathname is so that cvs knows where to store
these files in the repository.
+ clean up example names so that they're a bit less "amateur"

1 files changed, 17 insertions, 11 deletions

diff --git a/Packages.txt b/Packages.txt
index d8363dd9140..854b0570cf3 100644
--- a/Packages.txt
+++ b/Packages.txt
@@ -1,4 +1,4 @@
-# $NetBSD: Packages.txt,v 1.137 2001/02/02 03:42:42 hubertf Exp $
+# $NetBSD: Packages.txt,v 1.138 2001/02/09 14:32:27 agc Exp $
 ###########################################################################
 
 			==========================
@@ -40,11 +40,11 @@ derived from FreeBSD.
 
 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 your own 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.
+Collection, either by installing a precompiled binary package, or
+by building your own 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
@@ -1783,11 +1783,16 @@ You have to separate between binary and "normale" (source) packages here:
  10.2 Committing: Importing the package into CVS
  ===============================================
 
-This section is only of interrest for NetBSD developers with write access
-to the NetBSD pkgsrc repository. Newly created packages should be imported
-with a vendor tag of "TNF" and a release tag of "pkgsrc-base", e.g:
+This section is only of interest for NetBSD developers with write
+access to the NetBSD pkgsrc repository. Please remember that cvs
+imports files relative to the cwd, and that the pathname that you
+give the "cvs import" command is so that it knows where to place
+the files in the repository.  Newly created packages should be
+imported with a vendor tag of "TNF" and a release tag of "pkgsrc-base",
+e.g:
 
-	cvs import pkgsrc/<category>/frobnitz TNF pkgsrc-base
+	cd .../pkgsrc/<category>/<pkgname>
+	cvs import pkgsrc/<category>/<pkgname> TNF pkgsrc-base
 
 Packages derived from a FreeBSD port should be imported with a vendor tag
 of "FREEBSD" and a release tag of "FreeBSD-current-YYYY-MM-DD" (YYYY-MM-DD
@@ -1795,7 +1800,8 @@ being the date when the snapshot of the port were taken form the FreeBSD
 tree), and then doing the necessary modifications by normal CVS operations.
 E.g:
 
-	cvs import pkgsrc/<category>/mumbler FREEBSD FreeBSD-current-1998-04-01
+	cd .../pkgsrc/<category>/<pkgname>
+	cvs import pkgsrc/<category>/<pkgname> FREEBSD FreeBSD-current-1998-04-01
 	cvs rm patches/patch-a
 	cvs add patches/patch-aa
 	cvs ci