===================================================================
RCS file: /cvs/mandoc/INSTALL,v
retrieving revision 1.15
retrieving revision 1.15.2.4
diff -u -p -r1.15 -r1.15.2.4
--- mandoc/INSTALL	2016/07/14 11:09:06	1.15
+++ mandoc/INSTALL	2017/02/22 09:41:23	1.15.2.4
@@ -1,5 +1,12 @@
-$Id: INSTALL,v 1.15 2016/07/14 11:09:06 schwarze Exp $
+$Id: INSTALL,v 1.15.2.4 2017/02/22 09:41:23 schwarze Exp $
 
+************************************************************************
+* This is a backward compatibility release.
+* Unless you need compatibility with the old SQLite3-based mandoc.db(5)
+* database format, please use the mandoc-1.14.1 release instead:
+* http://mdocml.bsd.lv/snapshots/mdocml-1.14.1.tar.gz
+************************************************************************
+
 About mdocml, the portable mandoc distribution
 ----------------------------------------------
 The mandoc manpage compiler toolset is a suite of tools compiling
@@ -16,7 +23,7 @@ tech@ mailing list, too.
 
 Enjoy using the mandoc toolset!
 
-Ingo Schwarze, Karlsruhe, July 2016
+Ingo Schwarze, Karlsruhe, February 2017
 
 
 Installation
@@ -31,9 +38,9 @@ Regarding how packages and ports are maintained for yo
 system, please consult your operating system documentation.
 To install mandoc manually, the following steps are needed:
 
-1. If you want to build the CGI program, man.cgi(8), too, run the
-command "echo BUILD_CGI=1 > configure.local".  Then run "cp
-cgi.h.examples cgi.h" and edit cgi.h as desired.
+1. If you want to build the CGI program, man.cgi(8), too,
+run the command "echo BUILD_CGI=1 >> configure.local".
+Then run "cp cgi.h.example cgi.h" and edit cgi.h as desired.
 
 2. Run "./configure".
 This script attempts autoconfiguration of mandoc for your system.
@@ -54,25 +61,29 @@ and go back to step 2.
 installed to the intended places.  Otherwise, put some *DIR or *NM*
 variables into "configure.local" and go back to step 2.
 
-5. Run "sudo make install".  If you intend to build a binary
+5. Optionally run the regression suite.
+Basically, that amounts to "cd regress && ./regress.pl".
+But you should probably look at "./mandoc -l regress/regress.pl.1"
+first.
+
+6. Run "sudo make install".  If you intend to build a binary
 package using some kind of fake root mechanism, you may need a
 command like "make DESTDIR=... install".  Read the *-install targets
 in the "Makefile" to understand how DESTDIR is used.
 
-6. If you want to use the integrated man(1) and your system uses
+7. If you want to use the integrated man(1) and your system uses
 manpath(1), make sure it is configured correctly, in particular,
 it returns all directory trees where manual pages are installed.
 Otherwise, if your system uses man.conf(5), make sure it contains
 a "manpath" line for each directory tree, and the order of these
 lines meets your wishes.
 
-7. If you compiled with database support, run the command "sudo
-makewhatis" to build mandoc.db(5) databases in all the directory
-trees configured in step 6.  Whenever installing new manual pages,
-re-run makewhatis(8) to update the databases, or apropos(1) will
-not find the new pages.
+8. Run the command "sudo makewhatis" to build mandoc.db(5) databases
+in all the directory trees configured in step 6.  Whenever installing
+new manual pages, re-run makewhatis(8) to update the databases, or
+apropos(1) will not find the new pages.
 
-8. To set up a man.cgi(8) server, read its manual page.
+9. To set up a man.cgi(8) server, read its manual page.
 
 Note that some man(7) pages may contain low-level roff(7) markup
 that mandoc does not yet understand.  On some BSD systems using