Added annex.freezecontent-command and annex.thawcontent-command configs
Freeze first sets the file perms, and then runs freezecontent-command. Thaw runs thawcontent-command before restoring file permissions. This is in case the freeze command prevents changing file perms, as eg setting a file immutable does. Also, changing file perms tends to mess up previously set ACLs. git-annex init's probe for crippled filesystem uses them, so if file perms don't work, but freezecontent-command manages to prevent write to a file, it won't treat the filesystem as crippled. When the the filesystem has been probed as crippled, the hooks are not used, because there seems to be no point then; git-annex won't be relying on locking annex objects down. Also, this avoids them being run when the file perms have not been changed, in case they somehow rely on git-annex's setting of the file perms in order to work. Sponsored-by: Dartmouth College's Datalad project
This commit is contained in:
parent
ba62c3467b
commit
4b1b9d7a83
8 changed files with 88 additions and 31 deletions
|
@ -42,3 +42,7 @@ it is that if you explicitly run `chmod +w` on an annexed file in the working
|
|||
tree, this follows the symlink and allows writing to the file. It would be
|
||||
better to make the files fully immutable. But most systems either don't
|
||||
support immutable attributes, or only let root make files immutable.
|
||||
|
||||
The git configs `annex.freezecontent-command` and `annex.thawcontent-command`
|
||||
can be used to run additional commands to further lock down and later thaw
|
||||
the annex object and directory.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue