Hi, Chris Lamb wrote: > More generally, I can't think of a scenario where the value of > SOURCE_DATE_EPOCH request a timezone implication,
Alain Knaff mentioned mcopy option -m "Preserve the file modification time." which he wants to fulfill the user's expectation that the Y/M/D/h/m/s formatted timestamps show local time. (That's a similar problem as i perceived in xorriso with your wish to make the effects of SOURCE_DATE_EPOCH immutable in xorriso, although a design principle of xorriso is that any setting can be set and revoked by a xorriso command. My solution was to let SOURCE_DATE_EPOCH set the defaults of the various involved settings but to allow the commands to override those defaults, if really desired.) I plan to write a mail to rb-gene...@lists.reproducible-builds.org about my difficulties to justify the demand for a fixed time zone from the specs of https://reproducible-builds.org/specs/source-date-epoch/ I did not find a better motivation than by the specification "Formatting MUST be deferred until runtime if an end user should observe the value in their own locale or timezone." from which i argue: * FAT needs formatting of SOURCE_DATE_EPOCH. * One cannot do this at "runtime" of the FAT filesystem, which in the special case of pcmtest is when EFI reads the filesystem to find and run the \EFI\BOOT\BOOT*.EFI start program. => So one must not let the end user see their own locale or timezone. Have a nice day :) Thomas
