From: Ingo Schwarze <firstname.lastname@example.org>
Subject: call for testing: mandoc-1.13.5 release candidate
Date: Wed, 22 Feb 2017 12:08:02 +0100 [thread overview]
Message-ID: <20170222110802.GA11760@athene.usta.de> (raw)
now that mandoc-1.14.1 is out of the door, i'm planning to release
the SQLite3-compat version mandoc-1.13.5 soon. A release candidate
tarball is available for testing:
Both reports of successes and failures are welcome!
Mandoc 1.13.5 is a backward compatibility maintenance release
containing all the improvements of 1.14.1 except the switch away
from SQLite3 and except catman(8). It is intended exclusively for
-stable operating systems using mandoc-based apropos(1) who cannot
change the database format just like that - notably FreeBSD-stable.
Everybody else is encouraged to use the 1.14 branch instead because
the 1.14 database format is smaller and faster, the 1.14 makewhatis(8)
has some functionality improvements that could not be ported back,
and because the new code got better testing coverage, so there is
a lower risk of bugs in 1.14.1.
In a nutshell, the basic testing procedure is:
$ make regress
For more details, see the INSTALL file in the tarball.
Note that the regression suite does NOT test the database
functionality at all, so please check manually that the database
functionality you need works for you. One minimal way to do that
looks like this:
cp *.1 Test/man1
cp *.3 Test/man3
cp *.5 Test/man5
cp *.7 Test/man7
cp *.8 Test/man8
ln -s mandoc makewhatis
ln -s mandoc man
Then set "export MANPATH=Test" and play around with "./man -k".
Of course, it is better to try something similar with your real
manual page tree.
Optionally, you can run
$ echo BUILD_CGI=1 > configure.local
$ cp cgi.h.example cgi.h
before ./configure, but it is not very important.
I don't expect that anybody will run a 1.13.5 man.cgi(8) server.
Thank you for your support!
To unsubscribe send an email to email@example.com
next reply other threads:[~2017-02-22 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 11:08 Ingo Schwarze [this message]
2017-02-25 12:34 ` Jan Stary
2017-03-20 15:13 ` Ingo Schwarze
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).