`E2FSPROGS_FAKE_TIME` not respected when setting time to 0
Closed this issue · 5 comments
Setting E2FSPROGS_FAKE_TIME=0 will lead to the current time being used.
See for example the current line (total 3 findings of similar statements):
Line 1045 in 260dfea
The check will handle E2FSPROGS_FAKE_TIME=0 as if E2FSPROGS_FAKE_TIME is unset.
It is common to set times to unix zero for reproducible builds.
It is common to set times to unix zero for reproducible builds.
Citation needed.
In any case, there is no clean way of doing what you want, so if you want to do "reproducible builds", as the old joke goes, "Doctor, doctor, it hurts when I do this! // Then don't do that!". I will note that in the SOURCE_DATE_EPOCH specification, the recommendation is not to use zero, but...
Distributions could set SOURCE_DATE_EPOCH by using the value of a changelog file. For instance, Debian packages can set it to the value of the latest entry of debian/changelog.
Developers could set SOURCE_DATE_EPOCH to the date of the latest commit in their version control system. In this case, it is recommended to also update all source file timestamps, which git does not do by itself, otherwise old timestamps specific to the developer's working tree may be embedded into the output.
I said it is common, not that it is recommended. ;-)
It is just something you run into easily and it's hard to figure out what's going on. And while there is nothing forcing us to implement this, it is a nice move not letting fellow devs run into the open knife.
In any case, there is no clean way of doing what you want
Not sure why this can't be done in a clean way. The C code snippet suggested by Reproducible Builds handles that case as far as I can tell. Just write that into a function, make it also handle E2FSPROGS_FAKE_TIME env var and call it in the places where we currently do t = fs->now ? fs->now : time(NULL);.
If you like, I can open a PR.
The library interface for libext2fs is fs->now. What you are proposing would require breaking that interface and hacking the environment variable check into libext2fs. Hence, that is not clean; it would be a hack.
I understand the interface needs to stay the same. Why is it hacky to add the check into libext2fs?
We could check for SOURCE_DATE_EPOCH, and set it the way recommended by reproducible builds org. If it is unset, we can use the current fs->now ? fs->now : time(NULL). This should be backwards compatible, as it only changes the behavior in case SOURCE_DATE_EPOCH is set.
SOURCE_DATE_EPOCH has been implementing with timestamp clamping in v1.47.1-rc1+ . This should provide the functionality you want.