Index: /trunk/glueforge/INSTALL
===================================================================
--- /trunk/glueforge/INSTALL	(revision 5896)
+++ /trunk/glueforge/INSTALL	(revision 5897)
@@ -1,5 +1,5 @@
-# $Id: INSTALL,v 1.4 2005-07-29 21:46:32 jhoblitt Exp $
+# $Id: INSTALL,v 1.5 2006-01-05 01:03:50 jhoblitt Exp $
 
-Using the psmetadb meta-database API generator
+Using the glueforge meta-database API generator
 --
 
@@ -39,22 +39,26 @@
 - Step 2
 
-Checkout the psmetadb module from Pan-STARRS CVS.  If you need help setting up
-CVS please see this article:
+Checkout the glueforge module from Pan-STARRS CVS and build it.  If you need
+help setting up CVS please see this article:
 
     http://pan-starrs.ifa.hawaii.edu/project/resources/ps-cvs.html
 
-$ cvs co psmetadb
-$ cd psmetadb
+$ cvs co glueforge
+$ cd glueforge
+$ ./autogen.sh
+$ make
 
 - Step 3
 
 Create a MetadataConfig file that describes the table you want to access.  The
-MetadataConfig file syntax is described in the pslib SDRS.  psmetadb specific
-details are included in the "md2db.pl" Pod. For reference, an example named
-foo.md is provided
+MetadataConfig file syntax is described in the pslib SDRS.  glueforge specific
+details are included in the "glueforge" man page. For reference, an example
+named foo.md is provided
 
-$ perldoc md2db.pl
-.
-.
+$ perldoc glueforge
+
+or
+
+$ man glueforge
 
 $ cat foo.md
@@ -68,8 +72,8 @@
 - Step 4
 
-Generate the database bindings with the "md2db.pl" program.  The example foo.md
-file will generate code under the directory "foodb".
+Generate the database bindings with the "glueforge" executable.  The example
+foo.md file will generate code under the directory "foodb".
 
-$./md2db.pl -i foo.md
+$./glueforge -t templates/psdb -i foo.md
 $ cd foodb