From: Ricardo Wurmus <rekado@elephly.net>
To: 28241@debbugs.gnu.org
Subject: bug#28241: man page in r-minimal contains timestamp
Date: Sat, 26 Aug 2017 15:11:06 +0200 [thread overview]
Message-ID: <877exqv5hx.fsf@elephly.net> (raw)
In-Reply-To: <878ti6v60s.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> The man page is created with a rule in “doc/Makefile.in”:
>
> @$(HELP2MAN) --include=$(srcdir)/R.aux --no-info --output=R.1 \
> --name="a language for data analysis and graphics" \
> $(top_builddir)/bin/R
>
> “doc/R.aux” does not contain a timestamp, nor does the help output of R
> itself. Is help2man to blame here?
help2man supports SOURCE_DATE_EPOCH and it does the right thing when it
is set.
--8<---------------cut here---------------start------------->8---
$ guix environment --ad-hoc r-minimal help2man
$ help2man --include=R-3.4.0/doc/R.aux --no-info --output foo.1 R
$ grep August foo.1
.TH R "1" "August 2017" "R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"" "User Commands"
$ SOURCE_DATE_EPOCH=0 help2man --include=R-3.4.0/doc/R.aux --no-info --output foo.1 R
$ grep August foo.1
$ grep January foo.1
.TH R "1" "January 1970" "R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"" "User Commands"
--8<---------------cut here---------------end--------------->8---
Is SOURCE_DATE_EPOCH not set at the time help2man runs? “r-minimal”
uses the gnu-build-system, which has a build phase set-SOURCE-DATE-EPOCH
that sets SOURCE_DATE_EPOCH to 1.
Where is this lost?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-26 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 12:59 bug#28241: man page in r-minimal contains timestamp Ricardo Wurmus
2017-08-26 13:11 ` Ricardo Wurmus [this message]
2017-08-27 0:46 ` Ricardo Wurmus
2017-08-28 13:53 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877exqv5hx.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=28241@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).