go-mtree/updatefuncs_unsupported.go

// +build !linux

package mtree

import "os"

func xattrUpdateKeywordFunc(path string, kv KeyVal) (os.FileInfo, error) {
	return os.Lstat(path)
}
*: 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-15 18:54:58 +00:00			`// +build !linux`

			`package mtree`

			`import "os"`

updatefunc: simplify the function signature Signed-off-by: Vincent Batts <vbatts@hashbangbash.com> 2017-06-26 18:24:10 +00:00			`func xattrUpdateKeywordFunc(path string, kv KeyVal) (os.FileInfo, error) {`
*: 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-15 18:54:58 +00:00			`return os.Lstat(path)`
			`}`