[bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

[G. Branden Robinson]

Follow-up Comment #3, bug #57218 (project groff):

> I guess we could have a register \n[.utc] which is normally zero but is set
to 1 if SOURCE_DATE_EPOCH is in the environment. 

After thinking about that for 60 more seconds, I retract it.  It would mean
having to insert a layer on top of all those C library time calls in the patch
to choose which ones to use.  Gross.

> \n[dm]

I misspoke here.  They day-of-the-month register is \n[dy].

I think it'd be better if we just decreed that groff 1.23 runs on UTC
henceforth, even in compatibility mode.  If people want to reproduce unaltered
legacy documents with legacy dates, they already have to contrive a fake time
in the system clock anyway.

And if they're doing that, they can finagle that clock by up to 14[*] hours
more to correct for the desired local time.

Also, the registers are writable, so people can just -r their way around the
problem.

And as far as I can reason it out, any document that hard-codes these
registers doesn't have a problem (and it'll certainly be reproducible!).

[*] Aloha from the Line Islands.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57218>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/