On 04/05/2022 15:16, luigi scarso wrote:
On Wed, May 4, 2022 at 3:09 PM Roland Clobus <rclobus@rclobus.nlOn 19/04/2022 09:52, luigi scarso wrote:Thank you very much for your patch, I will check it this weekend.Have you found the time already to review my patch? [1]
Yes, Hans and I are discussing.If possible, I would like to use a --reproducible switch at the command line.
Adding a commandline argument is sometimes proposed by the development teams, instead of using SOURCE_DATE_EPOCH. I would rather suggest to use SOURCE_DATE_EPOCH, which is already in the code base, instead of adding a new code path.
If you find the time, please read the documentation on SOURCE_DATE_EPOCH [1] and the page that mentions a checklist [2].
The short summary: SOURCE_DATE_EPOCH has been standardized and is primarily intended to be used by rebuilders of the binaries, not the developers or end-users.
In the past, when SOURCE_DATE_EPOCH was getting established, texlive additionally added FORCE_SOURCE_DATE=1. Nowadays, if it can be avoided, I would recommend to use only SOURCE_DATE_EPOCH. See [3] for all uses of FORCE_SOURCE_DATE_ in Debian. As you can see, it is mainly used in several tests to ensure that packages have output that can be compared against a reference.
With kind regards, Roland Clobus [1] https://reproducible-builds.org/docs/source-date-epoch/[2] https://wiki.debian.org/ReproducibleBuilds/StandardEnvironmentVariables#Checklist
[3] https://codesearch.debian.net/search?q=FORCE_SOURCE_DATE&literal=0
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature