[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Miguel Ángel Arruga Vivas
Subject: [bug #59658] xgettext and msgint don't honor SOURCE_DATE_EPOCH
Date: Fri, 11 Dec 2020 08:19:35 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0


                 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



This is an extension of the problem reported and solved by

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


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]