diff INSTALL @ 21343:a3059cd301f1

Remove some directories that don't really work now.

--- a/INSTALL	Thu Apr 02 22:48:51 1998 +0000
+++ b/INSTALL	Fri Apr 03 01:52:38 1998 +0000
@@ -391,33 +391,7 @@
 	path variables - `bindir' and `libexecdir'.
 
 The above variables serve analogous purposes in the makefiles for all
-GNU software; here are some variables specific to Emacs.
-
-`lispdir' indicates where Emacs installs and expects its Lisp library.
-	Its default value, based on `datadir' (see above), is
-	`/usr/local/share/emacs/VERSION/lisp' (where `VERSION' is as
-	described above).
-
-`locallisppath' indicates where Emacs should search for Lisp files
-	specific to your site.  It should be a colon-separated list of
-	directories; Emacs checks them in order before checking
-	`lispdir'.  Its default value, based on `datadir' (see above), is
-	`/usr/local/share/emacs/VERSION/site-lisp:/usr/local/share/emacs/site-lisp'.
-
-`lisppath' is the complete list of directories Emacs should search for
-	its Lisp files; its default value is the concatenation of
-	`locallisppath' and `lispdir'.  It should be a colon-separated
-	list of directories; Emacs checks them in the order they
-	appear.
-
-`etcdir' indicates where Emacs should install and expect the rest of
-	its architecture-independent data, like the tutorial, DOC
-	file, and yow database.  Its default value, based on `datadir'
-	(which see), is `/usr/local/share/emacs/VERSION/etc'.
-
-`lockdir' indicates the directory where Emacs keeps track of its
-	locking information.  Its default value, based on
-	`sharedstatedir' (which see), is `/usr/local/com/emacs/lock'.
+GNU software; this variable is specific to Emacs.
 
 `archlibdir' indicates where Emacs installs and expects the executable
 	files and other architecture-dependent data it uses while
@@ -433,6 +407,11 @@
 directory, but be aware that running the `configure' program erases
 `Makefile' and rebuilds it from `Makefile.in'.
 
+The path for finding Lisp files is specified in src/paths.h,
+a file which is generated by running configure.  To change the path,
+you can edit the definition of PATH_LOADSEARCH in that file
+before you run `make'.
+
 The top-level Makefile stores the variable settings it used in the
 Makefiles for the subdirectories, so you don't have to specify them
 when running make in the subdirectories.