exclusively lock mechanism for repo tool

[GoogleCodeExporter]

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

Original issue reported on code.google.com by amarg...@gmail.com on 22 Aug 2012 at 4:20

[GoogleCodeExporter]

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.

Original comment by avec...@gmail.com on 22 Aug 2012 at 6:04

[GoogleCodeExporter]

Original comment by sop@google.com on 25 Oct 2012 at 5:56

• Changed state: Invalid

[GoogleCodeExporter]

Why is this considered 'Invalid'?

Original comment by avec...@gmail.com on 14 Nov 2012 at 10:17