On Sat, Jan 19, 2013 at 7:42 AM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
>
> so after thinking about the concept...
> it does not make sense to go further with a shared working copies on a
> network drive there are too many issues (of course, cause SVN is not made
> for such things)..so i will drop the idea...
> Thanks for clearing up...
>
>
>
>>
>> Have you considered other solutions? For example, the ASF CMS maintains
>> one working copy per project, and uses zfs copy-on-write clones to fork
>> off a per-user working copy for each user (even concurrent users) who
>> works on that working copy.
>>
>> https://svn.apache.org/repos/infra/websites/cms/webgui/lib/ASF/CMS.pm
>>
> Does this solutions supports having different working copies per user which
> can access them or are these working copies on a per project base? What
> about locking of files in the working copy (svn:needs-lock) etc. ? How could
> they be accessed ?
>
> Furthermore i have started to think about WebDav (after a hint of a
> colleague of mine) might be a solution on Windows, but i don't know how
> WebDav behave if two people working on the same file and saving the file?
> What about conflicts? What about locking of files ?
What problem are you trying to solve? Normally everyone checks out
their own separate copy and then is free to commit/update on their own
schedule and you can figure out how to fix conflicts after the fact if
you don't communicate well enough to avoid them. It does consume a
lot of disk space but that is usually a cheap commodity and if not you
can trade off deleting workspaces after use and doing a fresh checkout
when needed again.
--
Les Mikesell
lesmikes...@gmail.com
