FS#71154 - man pages are not reproducible
Attached to Project:
Pacman
Opened by Allan McRae (Allan) - Monday, 07 June 2021, 08:58 GMT
Last edited by Allan McRae (Allan) - Thursday, 01 July 2021, 01:55 GMT
Opened by Allan McRae (Allan) - Monday, 07 June 2021, 08:58 GMT
Last edited by Allan McRae (Allan) - Thursday, 01 July 2021, 01:55 GMT
|
Detailsman pages have a date in them.
|
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 01 July 2021, 01:55 GMT
Reason for closing: Fixed
Additional comments about closing: git commit b4383b8d007e28aa76324f45ad19e7878975074a
Thursday, 01 July 2021, 01:55 GMT
Reason for closing: Fixed
Additional comments about closing: git commit b4383b8d007e28aa76324f45ad19e7878975074a
"pacman_date" in turn gets embedded into the man page through doc/asciidoc.conf: https://gitlab.archlinux.org/pacman/pacman/-/blob/542910d684191eb7f25ddc5d3d8fe3060028a267/doc/asciidoc.conf#L53
Pacman 6.0.0-8-ga519 1970-01-01 PACMAN(8)
I've been working on getting more git metadata into the build. I was going to try to see if I can get the date specified via 'git log -1 --format=%cs' and stored in a file for 'git archive' or 'meson dist' and used for the asciidoc build as the logical next step.
The man pages would then do something a bit novel, and guarantee to refer to the date of the code they document, rather than the date that some potentially very old source code got unpacked and compiled. :D
This is not atypical for man pages in projects everywhere. :(