Closed GoogleCodeExporter closed 8 years ago
I don't know which way to go on this. I originally was setting the modification
date of the file ahead by one
second (as opposed to touching - which sets mod date to 'now', but this causes
Time Machine to back up the
entire file again, just to back up 200 bytes of OpenMeta tags, etc. So when I
added OpenMetaBackup, I pulled
out the mod date adjustment.
In any case, I don't think changing the modification date to 'now' with a
classic touch is the right thing?
Note that the 'ctime' from lstat() does change on tagging. But it does not fire
off notifications.
--Tom
Original comment by tom.ande...@gmail.com
on 5 Feb 2009 at 1:29
Makes sense. Though losing the tags on restore from a backup would also not be
ideal. Hopefully good backup
or sync tools, like DropBox, do binary file diffs.
I am not sure if this is possible, but if the folder the file is contained in
could be touched that would cause folder
actions to fire (I think). I am not sure that it has any effect on Time Machine.
Original comment by jhorman
on 12 Feb 2009 at 6:53
I don't think OpenMeta itself should do this. Instead it should be up to the
app implementing OpenMeta to do
so. I can imagine many scenarios where changing the modification date would be
undesirable. If using
OpenMeta forced me to update the mtime on any tagged file, I'd be unhappy.
Original comment by jonstov...@gmail.com
on 15 Feb 2009 at 5:55
Original comment by tom.ande...@gmail.com
on 13 Mar 2009 at 3:49
Original issue reported on code.google.com by
jhorman
on 3 Feb 2009 at 7:22