From: Ingo Schwarze <schwarze@usta.de>
To: Michael Stapelberg <stapelberg@debian.org>
Cc: tech@mdocml.bsd.lv
Subject: Re: mandoc-1.14.1 released
Date: Wed, 22 Feb 2017 01:07:46 +0100 [thread overview]
Message-ID: <20170222000746.GC43745@athene.usta.de> (raw)
In-Reply-To: <CANnVG6nym60Ex419W4zzk10oYQ8wmtWzZbK0Zsq=17K11Neapw@mail.gmail.com>
Hi Michael,
Michael Stapelberg wrote on Tue, Feb 21, 2017 at 10:12:33PM +0100:
> using LN="ln -sf" results in an absolute symlink for the whatis.1
> manpage, which we need to then change into a relative one to prevent our
> tooling from choking on them:
> https://anonscm.debian.org/git/collab-maint/mdocml.git/commit/?id=86403b72b1c47780cc626e046d65db04d2e3b622
That was easy to change. 1.14.2 (release not yet planned)
and 1.13.5 (to be released soon) will do it the way you want,
see below.
> The following lintian warning indicates a spelling error:
> I: mandoc: spelling-error-in-manpage usr/share/man/man7/mandoc_roff.7.gz
> parantheses parentheses
Fixed in OpenBSD and bsd.lv HEAD and VERSION_1_13.
Thanks for reporting!
Ingo
Log Message:
-----------
Debian wants relative, not absolute symlinks for man pages;
suggested by Michael Stapelberg
Modified Files:
--------------
mdocml:
Makefile
Revision Data
-------------
Index: Makefile
===================================================================
RCS file: /home/cvs/mdocml/mdocml/Makefile,v
retrieving revision 1.504
retrieving revision 1.505
diff -LMakefile -LMakefile -u -p -r1.504 -r1.505
--- Makefile
+++ Makefile
@@ -397,8 +397,7 @@ base-install: mandoc demandoc soelim
$(INSTALL_MAN) soelim.1 $(DESTDIR)$(MANDIR)/man1/$(BINM_SOELIM).1
$(INSTALL_MAN) man.1 $(DESTDIR)$(MANDIR)/man1/$(BINM_MAN).1
$(INSTALL_MAN) apropos.1 $(DESTDIR)$(MANDIR)/man1/$(BINM_APROPOS).1
- $(LN) $(DESTDIR)$(MANDIR)/man1/$(BINM_APROPOS).1 \
- $(DESTDIR)$(MANDIR)/man1/$(BINM_WHATIS).1
+ cd $(DESTDIR)$(MANDIR)/man1 && $(LN) $(BINM_APROPOS).1 $(BINM_WHATIS).1
$(INSTALL_MAN) man.conf.5 $(DESTDIR)$(MANDIR)/man5/$(MANM_MANCONF).5
$(INSTALL_MAN) mandoc.db.5 $(DESTDIR)$(MANDIR)/man5
$(INSTALL_MAN) man.7 $(DESTDIR)$(MANDIR)/man7/$(MANM_MAN).7
Log Message:
-----------
fix spelling error;
found by Michael <Stapelberg at debian dot org> with Lintian
Modified Files:
--------------
mdocml:
roff.7
Revision Data
-------------
Index: roff.7
===================================================================
RCS file: /home/cvs/mdocml/mdocml/roff.7,v
retrieving revision 1.75
retrieving revision 1.76
diff -Lroff.7 -Lroff.7 -u -p -r1.75 -r1.76
--- roff.7
+++ roff.7
@@ -1780,7 +1780,7 @@ maximum (not available in C)
.El
.Pp
There is no concept of precedence; evaluation proceeds from left to right,
-except when subexpressions are enclosed in parantheses.
+except when subexpressions are enclosed in parentheses.
Inside parentheses, whitespace is ignored.
.Sh ESCAPE SEQUENCE REFERENCE
The
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2017-02-22 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170221023444.GB51369@athene.usta.de>
2017-02-21 21:12 ` Michael Stapelberg
2017-02-22 0:07 ` Ingo Schwarze [this message]
2017-02-27 20:55 ` Michael Stapelberg
2017-03-04 16:55 ` 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=20170222000746.GC43745@athene.usta.de \
--to=schwarze@usta.de \
--cc=stapelberg@debian.org \
--cc=tech@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).