Add support for SOURCE_DATE_EPOCH environment variable #1954
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM. |
birkenfeld
added a commit
that referenced
this pull request
Jul 24, 2015
Add support for SOURCE_DATE_EPOCH environment variable
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Debian, we use this variable to prevent build tools from inserting build timestamps into generated files, and use some deterministic date instead (i.e. date in the changelog).
Support for this variable has already been added to help2man, and submitted to doxygen, epydoc, gcc and txt2man projects.
See https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal for the full story.
I have added support for this to
ustrftimefunction so that it applies to all places where we use the current time, i.e. handling of|today|and the Last Updated string.