keywords: don't fail on presence of "flags"
BSD file's support "flags". These have some similarity with xattr, but for specific features, rather than general purpose key/values. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
This commit is contained in:
parent
84f1e6ebc6
commit
e45837faea
3 changed files with 23 additions and 1 deletions
|
@ -165,7 +165,7 @@ var (
|
|||
BsdKeywords = []string{
|
||||
"cksum",
|
||||
"device",
|
||||
"flags",
|
||||
"flags", // this one is really mostly BSD specific ...
|
||||
"ignore",
|
||||
"gid",
|
||||
"gname",
|
||||
|
@ -226,6 +226,8 @@ var (
|
|||
"sha512": hasherKeywordFunc("sha512digest", sha512.New), // The SHA512 message digest of the file
|
||||
"sha512digest": hasherKeywordFunc("sha512digest", sha512.New), // A synonym for `sha512`
|
||||
|
||||
"flags": flagsKeywordFunc, // NOTE: this is a noop, but here to support the presence of the "flags" keyword.
|
||||
|
||||
// This is not an upstreamed keyword, but used to vary from "time", as tar
|
||||
// archives do not store nanosecond precision. So comparing on "time" will
|
||||
// be only seconds level accurate.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue