ts:scripts: Use SOURCE_DATE_EPOCH envionment variable if set #5753
Conversation
See https://reproducible-builds.org/docs/source-date-epoch/ Signed-off-by: Andreas Schneider <[email protected]>
cryptomilk
force-pushed
the
asn-source-date-epoch
branch
from
8bbdebe to
90ed90d
Compare
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Unstale, still valid ... |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Still valid ... |
|
Why was this closed without being merged? |
|
I created #6212 now. |
The Signal team generally uses private repositories for development. They will merge the commit(s) in your PR manually into their private repository, and once a (beta) release is ready, the commits for that release will be pushed to this public repository. Your PR won"t be marked as "merged", it will be closed, but the commit in the repository will have you as the author or co-author. There"s no need to open a duplicate PR. |
First time contributor checklist:
Contributor checklist:
developmentbranchyarn readyrun passes successfully (more about tests here)Description
For packaging you want to use the SOURCE_DATE_EPOCH environment variable as release tarballs don"t inlcude git information. The variable is widely available on different distributions.
Details: https://reproducible-builds.org/docs/source-date-epoch/