diff options
author | Alexander Larsson <alexl@redhat.com> | 2020-11-02 14:37:26 +0100 |
---|---|---|
committer | Alexander Larsson <alexl@redhat.com> | 2020-11-03 11:44:52 +0100 |
commit | 013417ea72aa767aec15259271ef04846070be64 (patch) | |
tree | ad382749a15a56d34bc1c5e8152faaa695f4b2a3 /glnx-backports.c | |
parent | 1dd01d5ef172fbe7cb385c91ee2a3740962e8074 (diff) | |
download | libglnx-replace-increasing-mtime.tar.gz |
Add GLNX_FILE_REPLACE_INCREASING_MTIMEreplace-increasing-mtime
This make replaced files have a strictly increasing st_mtime. The main
usecase I have for this is to ensure the summary file mtime increases
because the flatpak tests are failing due to the python httpd used
in the tests rely on st_mtime for the http If-Modified-Since header.
For the tests this breaks all the time since we're just doing a lot of
summary updates. However, I can see this accidentally happening in the
wild too, so i think its proper to always ensure the new summary is
"newer", even though it means it will be timestamped slightly in the
future. In practice this will not happen regularly, and the times it
*does* happen we really do need it.
Diffstat (limited to 'glnx-backports.c')
0 files changed, 0 insertions, 0 deletions