[Swan-dev] always generating the man page

Lennart Sorensen lsorense at csclub.uwaterloo.ca
Fri May 8 04:19:57 EEST 2015

On Thu, May 07, 2015 at 06:00:03PM -0400, Paul Wouters wrote:
> Well, if we want to indicate to the users roughly how (un)dated the man
> page is, we have to put something there. I realise my proposal would
> still be able to trigger a mismatch 12 times a year around midnight.
> But the only alternative is to completely leave out a date, and then the
> user has no idea if the man page is a decade outdated or not.
> Of course, if we ship and _not_ regenerate man pages, this problem goes
> away. But then when a patch introduces a new option, we have to not
> forget to regenerate the man page, and of course we will also have the
> date issue again.

Any way to get the last modification date of the document and use that
rather than the build date?  After all that would make more sense.
After all a rebuild of old code today should not look newer than recent
code built last month.

Len Sorensen

More information about the Swan-dev mailing list