From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: pod2mdoc: make it easier to override the POD2MAN and POD2MDOC variables
Date: Fri, 18 Jul 2014 21:31:46 -0400 (EDT) [thread overview]
Message-ID: <201407190131.s6J1Vk8j007218@krisdoz.my.domain> (raw)
Log Message:
-----------
make it easier to override the POD2MAN and POD2MDOC variables
Modified Files:
--------------
pod2mdoc/Regress:
Makefile.inc
Revision Data
-------------
Index: Makefile.inc
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/pod2mdoc/Regress/Makefile.inc,v
retrieving revision 1.2
retrieving revision 1.3
diff -LRegress/Makefile.inc -LRegress/Makefile.inc -u -p -r1.2 -r1.3
--- Regress/Makefile.inc
+++ Regress/Makefile.inc
@@ -1,10 +1,12 @@
# --- utilities ---
-POD2MAN = pod2man -c 'OpenBSD Reference Manual' -d 'July 13, 2014' -r 'OpenBSD ports'
+TESTDATE = -d 'July 19, 2014'
+POD2MAN = pod2man
+POD2MANARGS = -c 'OpenBSD Reference Manual' -r 'OpenBSD ports'
GROFF = groff -Tascii -P -c
MANDOC = mandoc -Tascii
DIFF = diff -u
-POD2MDOC = /co/pod2mdoc/pod2mdoc -d 'July 13, 2014'
+POD2MDOC = /co/pod2mdoc/pod2mdoc
# --- lists ---
@@ -96,7 +98,7 @@ ${t}:${t}.diff
.SUFFIXES: .mdoc .groff_mdoc .mandoc_mdoc
.pod.preman:
- -${POD2MAN} $< > $@
+ -${POD2MAN} ${POD2MANARGS} ${TESTDATE} $< > $@
.preman.man:
../p2m_postproc.pl < $< > $@.part
@@ -115,7 +117,7 @@ ${t}:${t}.diff
@mv $@.part $@
.pod.mdoc:
- ${POD2MDOC} $< > $@.part
+ ${POD2MDOC} ${TESTDATE} $< > $@.part
@mv $@.part $@
.mdoc.groff_mdoc:
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2014-07-19 1:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201407190131.s6J1Vk8j007218@krisdoz.my.domain \
--to=schwarze@mdocml.bsd.lv \
--cc=source@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).