pkglint.

4 files changed, 9 insertions, 318 deletions

diff --git a/databases/tcl-gdbm/Makefile b/databases/tcl-gdbm/Makefile
index d80ae5a0feb..6f6b953da20 100644
--- a/databases/tcl-gdbm/Makefile
+++ b/databases/tcl-gdbm/Makefile
@@ -1,16 +1,16 @@
-# $NetBSD: Makefile,v 1.1.1.1 1999/07/07 15:14:25 bouyer Exp $
+# $NetBSD: Makefile,v 1.2 1999/07/07 16:07:09 bouyer Exp $
 #
 
 DISTNAME=	Tclgdbm0.6
 PKGNAME=	tcl-gdbm-0.6
 CATEGORIES=	databases
 MASTER_SITES=	http://www.tcltk.com/ftp/ellson/
-EXTRACT_SUFX=	.tar.gz
 
 MAINTAINER=	bouyer@netbsd.org
 
 DEPENDS+=	tcl-8.0.5:../../lang/tcl80	\
 		gdbm-1.7.3:../../databases/gdbm
+
 GNU_CONFIGURE=	yes
 
 .include "../../mk/bsd.pkg.mk"
diff --git a/databases/tcl-gdbm/pkg/DESCR b/databases/tcl-gdbm/pkg/DESCR
index 92401ff2dd8..646c93bb1a4 100644
--- a/databases/tcl-gdbm/pkg/DESCR
+++ b/databases/tcl-gdbm/pkg/DESCR
@@ -1,166 +1,8 @@
-Tclgdbm was hacked together by John Ellson (ellson@lucent.com)
-It was derived from tcl+gdbm by Christian Lindig <lindig@ips.cs.tu-bs.de>
-
-The latest version of Tclgdbm is kept at:
-	
-	http://www.tcltk.com/ftp/ellson/
-	
-
-tclgdbm 0.1.3  - JE - upgrade to tcl7.5 loadable library
-tclgdbm 0.2    - JE - upgrade to tcl7.6 package (loadable library)
-tclgdbm 0.3    - JE - fixes for tcl8.0
-tclgdbm 0.4    - JE - fix mem leak with patch from: t-tange@ats.nis.nec.co.jp
-tclgdbm 0.5    - JE - add gdbm error, and gdbm writemode
-                      with patch from: Scott Beasley <jscottb@InfoAve.Com>
-tclgdbm 0.6    - JE - support for Stubs (8.0.6, 8.1.1, or later)
-
-NOTE: Dynamic loading requires that libgdbm.a be built with -fpic
-   otherwise you may get all kinds of relocation errors from ld.
-
-NOTE: This extension has not yet been converted to use Tcl_Obj
-so the database cannot yet be used to store strings containing NULLs.
-
-
-Tclgdbm
--------
-
 This directory contains the source of tclgdbm, a dynamically loaded
 extension for accessing GNU gdbm files from tcl/tk. GNU gdbm files
 provide persistent mappings from arbitrary keys to values. tclgdbm 
 uses these features to provide mappings from (short) key
-strings to (larger) data strings. The following example illustrates
-the basic new commands, see below for details:
-
-##
-## load dll
-##
-package require Tclgdbm
-
-##
-## open database "test.data" for read/write (create if not existent)
-##
-set db [gdbm open test.data rwc];
-foreach i {1 2 3 4 5 6} {
-   # key is $i, store string "This data for $i"
-   gdbm store $db $i "This data for $i" ;
-}
-
-##
-## gdbm list $db gives list of all keys in $db
-##
-foreach key [lsort [gdbm list $db]] {
-   # retrieve each content and display it
-   puts stdout "$key [gdbm fetch $db $key]" ;
-}
-
-gdbm close $db ;
-
-Commands
---------
-
-gdbm open <file> [r|rw|rwc|rwn]
-
-Opens a gdbm database <file> with an optional mode. If the mode is not
-given it is opened for reading (r). The mode can be (r) (read only),
-(rw) (read,write), (rwc) (read,write and create if not already
-existent), and (rwn) (read,write and create a new database regardless
-if one exists). The command returns a handle <name> which is used to
-refer to the open database.
- 
-gdbm close <name>  
-
-Close a gdbm database with the name <name>.
- 
-gdbm insert <name> <key> <content>  
-
-<name> is the name of a gdbm database previously opened with gdbm
-open.  Inserts the data <content> giving it the key <key>.  If data
-with <key> is already in the database an error is generated. Nothing
-returned.
- 
-gdbm store  <name> <key> <content>  
-
-<name> is the name of a gdbm database previously opened with gdbm
-open.  Inserts <content> to the database. If <key> already exists
-the new <content> replaces the old. Nothing returned.
- 
-gdbm fetch  <name> <key>  
- 
-<name> is the name of a gdbm database previously opened with gdbm
-open.  Searches for <key> in the database and returns the associated
-contents, or returns a tcl error if the key is not found.
- 
-gdbm delete  <name> <key> 
- 
-<name> is the name of a gdbm database previously opened with gdbm
-open.  Searches for <key> and deletes it in the database.  If <key> is
-not found an error is generated.  Nothing returned.
- 
-gdbm list  <name>  
-
-<name> is the name of a gdbm database previously opened with gdbm
-open.  Returns a list of all keys in the database.
- 
-gdbm reorganize  <name>  
-
-<name> is the name of a gdbm database previously opened with gdbm
-open.  This routine can be used to shrink the size of the database
-file if there have been a lot of deletions.  Nothing returned.
-
-gdbm exists <name> <key>
-
-Returns "0" if <key> is not found within the previously opened
-database <name>, "1" otherwise.
-
-gdbm firstkey <name> 
-gdbm nextkey <name> <lastkey>
-
-A first/next scheme permits retrieving all keys from a database in
-sequential (but unsorted!) order. gdbm firstkey <name> returns a
-starting key, which may be used to retrieve the following key with
-nextkey. nextkey returns the next key to a given previous key. When no
-next key is available, the empty string is returned.
-
-
-Speed
------
-
-Here are some (real) execution times on a SparcStation 2 (SunOS
-4.1.1). The file was stored on a local and a remote filesystem.
-See torture.tcl for details.
-
-				local fs	network fs
-
-create 1000 short entries	2.2 sec		50.0 sec
-read 1000 entries (first/next)	1.2 sec		1.5 sec
-read 1000 entries (list)	1.1 sec		1.3 sec
-delete 100 entries out of 1000	8.7 sec		23.2 sec
-lookup 1000 keys out of 900	0.63 sec	0.82 sec
-
-Summary: write access is expensive, especially on remote file
-systems. 
-
-Copyright
----------
-
-see the file COPYRIGHT
-
-History
--------
-
-The first version was derived from tclgdbm1.0 by
-<tdoan@x400gate.bnr.ca> from the tcl distribution. The actual version
-is nearly totally rewritten and uses much more of the data structures
-provided by tcl.
-
-Future Plans
-------------
-
-The current version maps a key string to a data string. Future
-versions should map a key string to a list of datastrings i.e.:
-
-gdbm store <db> <key> <list of strings>		
-gdbm fetch <db> <key> 				returns a list
+strings to (larger) data strings.
 
 Credits
 -------
@@ -168,17 +10,6 @@ Credits
 Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> gave much hints that
 improved portability and elegance of the code.
 
-Bugs
-----
-
-- <key> strings are not allowed to be longer than 1023 Bytes. 	
-- No man page yet - any volunteers?
-- not extensively tested yet
-
-Report bugs, ports, improvements and successful compilation on
-platforms different from the ones mentioned above to the author.
-
-
 Author
 ------
 
diff --git a/www/tcl-cgi/Makefile b/www/tcl-cgi/Makefile
index b42bb5c3996..7170ae5d9de 100644
--- a/www/tcl-cgi/Makefile
+++ b/www/tcl-cgi/Makefile
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.1.1.1 1999/07/07 15:15:12 bouyer Exp $
+# $NetBSD: Makefile,v 1.2 1999/07/07 16:10:42 bouyer Exp $
 #
 
 DISTNAME=	cgi.tcl
@@ -6,12 +6,12 @@ PKGNAME=	tcl-cgi-0.8
 WRKSRC=		${WRKDIR}/cgi.tcl-0.8
 CATEGORIES=	www
 MASTER_SITES=	http://expect.nist.gov/cgi.tcl/
-EXTRACT_SUFX=	.tar.gz
 
 MAINTAINER=	bouyer@netbsd.org
 HOMEPAGE=	http://expect.nist.gov/cgi.tcl/
 
 DEPENDS+=	tcl-8.0.5:../../lang/tcl80
+
 GNU_CONFIGURE=	yes
 
 post-install:
diff --git a/www/tcl-cgi/pkg/DESCR b/www/tcl-cgi/pkg/DESCR
index b506dc95fe4..d25068c791e 100644
--- a/www/tcl-cgi/pkg/DESCR
+++ b/www/tcl-cgi/pkg/DESCR
@@ -1,146 +1,6 @@
-This is the README to cgi.tcl, a library of Tcl procedures to assist
-in writing CGI scripts.  Review the HISTORY file for significant changes.
+cgi.tcl, is a set of procedures for writing CGI scripts in Tcl.  The procedures
+implement the code described in the paper "Writing CGI scripts in Tcl" which
+was published in the Proceedings of the Fourth Tcl Workshop (Tcl '96), and can
+be found at: http://www.nist.gov/msidlibrary/doc/libes96c.ps
 
 The cgi.tcl home page is http://expect.nist.gov/cgi.tcl
-
---------------------
-Introduction
---------------------
-
-This is the README file for cgi.tcl, a set of procedures for writing
-CGI scripts in Tcl.  The procedures implement the code described in
-the paper "Writing CGI scripts in Tcl" which was published in the
-Proceedings of the Fourth Tcl Workshop (Tcl '96).
-
---------------------
-Getting Started
---------------------
-
-First, read the paper "Writing CGI Scripts in Tcl", from Tcl '96.  If
-you can't find the paper in this archive, it can also be found at:
-
-	http://www.nist.gov/msidlibrary/doc/libes96c.ps
-
-That paper will give you a lot of good ideas for using Tcl, not only
-with CGI but plain everyday HTML as well.
-
-Next, try some of the examples in the example directory.  Please read
-the "Instructions" section in example/README first.
-
-A rough draft of complete documentation of the individual functions
-can be found in ref.txt in the doc directory.  
-
-Note that you are expected to understand Tcl.  I'm not going to
-explain how to write Tcl scripts here.  (If you're looking for a Tcl
-tutorial, please consider my Expect book which includes a very nice
-tutorial on Tcl.)
-
-Similarly, you are expected to understand HTML.  There are plenty of
-web tutorials and books on it.  Go read one.  You don't have to become
-an expert on HTML, but it is important to get a feel for it.  (The
-cgi.tcl package will take care of the details.)  If you plan to do
-CGI, you should know a couple more basic things.  Here's a simple CGI
-intro:
-
-	http://hoohoo.ncsa.uiuc.edu/cgi/intro.html
-
-
---------------------
-Status
---------------------
-
-The library is reasonably complete.  It supports forms, tables,
-cookies, Netscape extensions, file upload, plug-ins, etc, etc.  On the
-other hand, there are some things missing - such as certain deprecated
-things in HTML, things I can't believe anyone would use, things that
-are special extensions to a browser I'm not familiar with, etc.
-
-This library should run on any system (UNIX, Win, or Mac) which
-supports Tcl 8.0.
-
-----------------------
-Examples
-----------------------
-
-This distribution contains example scripts.  They can be found in the
-example directory of this distribution.  Please read the
-"Instructions" section in example/README first.
-
---------------------
-Installation
---------------------
-
-If you are on UNIX, read the INSTALL file.
-If you are on W95/NT, read the install.win file.
-If you are on Mac, read the install.mac file.
-
---------------------
-How to get the latest version of this code
---------------------
-
-The latest version of this code may be received from:
-
-	http://expect.nist.gov/cgi.tcl/cgi.tcl.tar.gz
-or	ftp://ftp.nist.gov/mel/div826/subject/expect/cgi.tcl/cgi.tcl.tar.gz
-
-Request email delivery by mailing to "library@cme.nist.gov".  The
-contents of the message should be (no subject line) "send
-pub/cgi/cgi.tcl.tar.gz".
-
---------------------
-Support from Don Libes or NIST
---------------------
-
-Although I can't promise anything in the way of support, I'd be
-interested to hear about your experiences using it (good or bad).  I'm
-also interested in hearing bug reports and suggestions for improvement
-even though I can't promise to implement them.
-
-If you send me a bug, fix, or question, include the version of
-cgi.tcl, version of Tcl, and name and version of the OS that you are
-using.  Before sending mail, it may be helpful to verify that your
-problem still exists in the latest version.  You can check on the
-current release and whether it addresses your problems by retrieving
-the latest HISTORY file (see "History" above).
-
-
-Awards, love letters, and bug reports may be sent to:
-
-Don Libes
-National Institute of Standards and Technology
-Bldg 220, Rm A-127
-Gaithersburg, MD  20899
-(301) 975-3535
-libes@nist.gov
-
-I hereby place this software in the public domain.  NIST and I would
-appreciate credit if this program or parts of it are used.
-
-Design and implementation of this program was funded primarily by
-myself.  Funding contributors include the NIST Automated Manufacturing
-Research Facility (funded by the Navy Manufacturing Technology
-Program), the NIST Scientific and Technical Research Services, the
-ARPA Persistent Object Bases project and the Computer-aided
-Acquisition and the Logistic Support (CALS) program of the Office of
-the Secretary of Defense.
-
---------------------
-Support for Don Libes or NIST
---------------------
-
-NIST accepts external funding and other resources (hardware, software,
-and personnel).  This can be a fine way to work more closely with NIST
-and encourage particular areas of research.
-
-Funding can be earmarked for specific purposes or for less-specific
-purposes.  For example, if you simply like the work I do, you can
-contribute directly to my funding which will reduce the amount of time
-I have to spend writing proposals and submitting them to other people
-for funding on my own.
-
-I can also participate in the NIST Fellows program allowing me to
-spend several months to a year working directly with your company and
-potentially even at your location.  I am also interested in returning
-to an academic program.  I presently have an MS and am hunting for
-Ph.D. topics and advisors.  Let me know if you have ideas or are
-interested in being my advisor.