[bug #59658] xgettext and msgint don't honor SOURCE_DATE_EPOCH

[Miguel Ángel Arruga Vivas]

URL:
  <https://savannah.gnu.org/bugs/?59658>

                 Summary: xgettext and msgint don't honor SOURCE_DATE_EPOCH
                 Project: GNU gettext
            Submitted by: m1gu3l
            Submitted on: Fri 11 Dec 2020 02:19:33 PM CET
                Category: Programmer tools
                Severity: 3 - Normal
              Item Group: None
                  Status: In Progress
                 Privacy: Public
             Assigned to: m1gu3l
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

This is an extension of the problem reported and solved by
https://savannah.gnu.org/bugs/?49654

Version 0.20 excluded POT-Creation-Date from generated .mo files, but this
still leads to unreproducible builds when LINGUAS contain automatically
generated PO files (e.g en@quot) and the POT file is generated/updated at
build time (e.g. building from a vcs checkout where the POT file isn't present
or up to date), as the contents of that field are used to fill
PO-Revision-Date when the PO file is created with the --no-translator option.

The attached patch implements the default use-case of SOURCE_DATE_EPOCH, but
it doesn't signal any error from the variable (allowed by the spec) and simply
continues with the usual local timestamp process.  Its value is used to fill
POT-Creation-Date for POT files generated by xgettext, and PO-Revision-Date
for PO files generated by msginit. 

Perhaps the test suite should be extended and/or modified to use more this
feature.  What do you think?




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Fri 11 Dec 2020 02:19:33 PM CET  Name:
0001-xgettext-msginit-Honor-SOURCE_DATE_EPOCH-for-timesta.patch  Size: 7KiB  
By: m1gu3l
Patch v1
<http://savannah.gnu.org/bugs/download.php?file_id=50438>

    _______________________________________________________

Reply to this item at:

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

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