go-mtree

Commit Graph

Author	SHA1	Message	Date
Vincent Batts	94303e15af	*.go: updated go:build added via gofmt Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>	2022-04-23 12:59:26 -04:00
Tobias Klauser	3fe21921b5	*: use UtimesNanoAt from x/sys/unix Use UtimesNanoAt from golang.org/x/sys/unix instead of manually crafting the syscall. Since UtimesNanoAt is provided for all unix-like OSes, factor out lchtimes to its own file with appropriate build tags. This allows to make use of it on darwin, dragonfly, freebsd, openbsd, netbsd and solaris in addition to linux. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>	2017-10-20 12:31:55 +02:00
Vincent Batts	73be830998	*: update `-u` behavior Fixes #16 In attempt to close https://github.com/vbatts/go-mtree/issues/16 I've uncovered that the update was missing a function for symlink. Additionally the update was not even opperating on the correct directory hierarchy. I've uncovered that os.Chtimes follows the symlink, and presumably only Linux has an obscure way to set the mtime/atime on a symlink itself. So I've made a custom lchtimes(). Also Mode follows through the symlink, and symlinks only ever have a mode of 0777, so don't set them. Lastly, directories need to have their mtime/atime set in a reverse order after all other updates have been done. This is going to require something like a `container/heap` to be unwound. Also, each updateFunc will _only_ perform the update if it is needed. Much less invasive this way. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>	2017-06-30 15:34:44 -04:00
Vincent Batts	9408f0f4c0	updatefunc: simplify the function signature Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>	2017-06-26 14:24:10 -04:00
Vincent Batts	ed464af779	*: xattr can Update() This is a gnarly patchset that has been mashed together. It uncovered that some aspects of Check were never really working correctly for `xattr` keywords, but also the `Update()` had been left undone for a while. This includes some API changes around the `Keyword` and `KeyVal` types. Also I would like to update the signature for the `UpdateKeywordFunc` to just accept a `KeyVal` as an argugment, rather than a keyword AND the value. with this context there would be no need to guess on the value of what's passed to the xattr update function of whether it needs or already is base64 encoded. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>	2017-06-24 15:05:24 -04:00

5 Commits