Page MenuHomeFreeBSD

groff: use changelog date rather than file modification date in man pages
ClosedPublic

Authored by emaste on Oct 5 2016, 9:23 PM.
Tags
None
Referenced Files
F135435912: D8158.id21087.diff
Sun, Nov 9, 8:40 PM
F135435907: D8158.id21090.diff
Sun, Nov 9, 8:40 PM
F135415925: D8158.id.diff
Sun, Nov 9, 4:19 PM
Unknown Object (File)
Sun, Nov 9, 12:16 PM
Unknown Object (File)
Thu, Nov 6, 10:47 PM
Unknown Object (File)
Wed, Oct 29, 1:12 PM
Unknown Object (File)
Wed, Oct 22, 10:53 PM
Unknown Object (File)
Sep 24 2025, 1:35 AM
Subscribers

Details

Summary

The source checkout date is not particularly relevant, and this makes groff man pages build reproducibly.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste retitled this revision from to groff: use changelog date rather than file modification date in man pages.
emaste updated this object.
emaste edited the test plan for this revision. (Show Details)
emaste added reviewers: bapt, cperciva, allanjude.
emaste added a subscriber: gjb.
bapt edited edge metadata.
This revision is now accepted and ready to land.Oct 5 2016, 9:27 PM

Is there a reason to generate $MDATE via != rather than simply changing the backtick execution within the sed command?

Is there a reason to generate $MDATE via != rather than simply changing the backtick execution within the sed command?

I prefer it for easier debugging the Makefile, and for being clear that it's only being evaluated once per use of Makefile.inc. Because we're going to use one date in common for all manpages there's no need for per-file checking.

This revision was automatically updated to reflect the committed changes.