| Issue 121: | exclusively lock mechanism for repo tool | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Request for an enhancement to the repo tool that will be able to exclusively lock files while writing them to the system so that no other process (including other 'repo sync' commands) can try to write/access the same file until the lock is removed. This way we can work on sharing the .repo/projects folder between different project workspaces cleanly without collisions killing the 'repo sync'. Thanks, amargono
Oct 25, 2012
(No comment was entered for this change.)
Status:
Invalid
Nov 14, 2012
Why is this considered 'Invalid'? |
|
| ► Sign in to add a comment |
We want to be able to share the .repo/projects among multiple repo forests that sometimes will use the same repos, so that only 1 projects folder is used for all of them, using this logic: 1. Do repo init 2. Remove .repo/projects directory if present 3. Make symlink to shared projects folder 4. Do repo sync 5. Continue The problem we have experienced is that the #4 step of this sometimes collides when the same repo is updated at the same time, causing the step to fail. This request was made to prevent this by making sure the files are locked from use while being written and unlocked when complete, then the colliding process would wait for the lock to clear before accessing the file.