mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: Having the write bit not set can cause problems with automated usage (e.g. build systems)

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawnLM6CIUo2loSFNTLPDdBgAEoz9ehP2hz8 2014-12-02 23:16:57 +00:00 committed by admin
parent 53ad6cd0cf
commit 2bf81cefd1
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/internals/lockdown/comment_1_caa8b378e8c35177083e6cc2f6937180._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnLM6CIUo2loSFNTLPDdBgAEoz9ehP2hz8"
nickname="Duncan"
subject="Having the write bit not set can cause problems with automated usage (e.g. build systems)"
date="2014-12-02T23:16:57Z"
content="""
I'm using a git-annex to store build artefacts on a remote bare repo. Some of these artefacts are used in subsequent builds, which clone the artefacts repo, and use 'git annex get' to retrieve the artefacts of interest.
Unfortunately, I've had to add a little kludge along the following lines to my build script fragment:
git annex get ${file}
find .git/annex/objects -type d -exec chmod +w {} \;
This is necessary because I need to ensure that the cloned git repo is able to be deleted at all times (I'm using yocto/openembedded and it may want to delete the clone for a variety of reasons).
"""]]