From: Jan Stary <hans@stare.cz>
To: discuss@mdocml.bsd.lv
Subject: Re: mandoc-1.13.4 released
Date: Sun, 17 Jul 2016 12:34:32 +0200 [thread overview]
Message-ID: <20160717103432.GA54145@www.stare.cz> (raw)
In-Reply-To: <20160714144820.GA6433@athene.usta.de>
Hi Ingo,
On Jul 14 16:48:20, schwarze@usta.de wrote:
> mandoc = mdocml 1.13.4 is now publicly available
> from <http://mdocml.bsd.lv/>.
testing downstream, it builds and works fine on Debian 7.10.
I have not built CGI though as I don't use it.
See below for a diff fixing a typo.
Also, the example configure.local says
# Force usage of man.conf(5).
# If it does not exist or contains no valid configuration,
^^^^^^^^^^^^^^^^^^^^
# man(1), makewhatis(8), and apropos(1) will not work properly.
HAVE_MANPATH=0
But the presence of man.conf is optional, right?
Jan
Index: configure.local.example
===================================================================
RCS file: /cvs/mdocml/configure.local.example,v
retrieving revision 1.13
diff -u -p -r1.13 configure.local.example
--- configure.local.example 14 Jul 2016 11:09:06 -0000 1.13
+++ configure.local.example 17 Jul 2016 10:13:36 -0000
@@ -198,7 +198,7 @@ BINM_MAKEWHATIS=mandocdb # default is "m
PREFIX="/usr/local"
HOMEBREWDIR="${PREFIX}/Cellar"
-# --- user settings related man.cgi ------------------------------------
+# --- user settings related to man.cgi ---------------------------------
# By default, building man.cgi(8) is disabled. To enable it, copy
# cgi.h.example to cgi.h, edit it, and use the following line.
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2016-07-17 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 14:48 Ingo Schwarze
2016-07-17 10:34 ` Jan Stary [this message]
2016-07-19 18:04 ` Ingo Schwarze
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160717103432.GA54145@www.stare.cz \
--to=hans@stare.cz \
--cc=discuss@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).