On Thu, Jul 6, 2017, at 12:22 PM, Chris Murphy wrote: > > b. On ostree installations, the time for files is baked into the tree > created server side, The ostree format intentionally *doesn't* store any timestamps, aside from a single timestamp on the commit object, but that's not relevant to the file timestamps. Instead, everything in the immutable set is 0: https://bugzilla.gnome.org/show_bug.cgi?id=720363 For /etc which is writable, see https://bugzilla.redhat.com/show_bug.cgi?id=1229160 For /var, ostree itself (almost) never touches it, we rely on systemd-tmpfiles. One thing that's a bit relevant to this list is that it's now a bug for tools run in %post to rely on file timestamps to determine whether or not something changed. I'm not aware of anything that does today though, most things use file triggers or just run unconditionally. _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
