File timestamps lost during commit/deploy


Somewhere in the process of commiting a series of files to an ostree,
creating a new empty fs, pulling & deploying from the ostree, the
original timestamps on the files are lost. They are replaced with the
timestamp of when the ostree gets deployed. Is that by design, is
there any way to maintain original timestamps?

This is causing problems for guile-based apps, which install both
source and compiled libraries. As ostree deploys the compiled
libraries before the source, the timestamp on the source files is
newer than the binary. This causes guile to recompile the source,
thinking that the binary is outdated. Compilation is slow, so the apps
take a long time to start, for no good reason.

If maintaining original timestamps isn't possible, perhaps ostree
could at least deploy all files with exactly the exact same timestamp?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]