You really only need one server for svk normally, which is a plain subversion server, and every developer has his or her own mirror of that server or part of it, on their development machines. As far as the branch per developer thing you suggest, that would work fine with svk and if you really wanted to you could setup servers in the way you describe, but I can't fathom why you'd need such as complicated setup.
<br><br>SVK has no GUI yet that I'm aware of, though if you used svn checkouts from the svk depot you could use a svn GUI client. However you'd still need to use the svk commandline for doing merges, and you'd loose some of the other advantages of svk, like having working copies with no junk meta files in them, when you go this route.
<br><br>Michael<br><br><br><div><span class="gmail_quote">On 6/26/07, <b class="gmail_sendername">Saravanan T S</b> <<a href="mailto:saravanan@k.st">saravanan@k.st</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="font-family: Arial,sans-serif; font-size: 10pt;">Hi All,<br><br>HELP HELP HELP<br><br>I have not used svk. Used vss, cvs and mks. I am evaluating svk for our project distributed development.<br><br>I hope I am mailing to the right mailing list. If not, please let me know, I will backup [politely].
<br><br>I want to do this:<br> Mirror a SVK repository across 3 servers S0, S1, S2.<br> Every developer will be having only one of the servers to commit his/her changes.<br><br> This is my idea to do it.<br><br> S0: Master server has repository.
<br> Two branches are made from the root of repository.<br> Branch B1 for S1<br> and Branch B2 for S2.<br><br> RULES FOLLOWED:<br> --------------<br> Developers Dev0 in S0 will use only S0, Head of main tree
<br> Developers Dev1 in S1 will use only B1, Branch of main tree<br> Developers Dev2 in S2 will use only B2, Branch of main tree<br><br> Note: <br> 1. B1 and B2 are physically separate repositories with ***timestamp*** differences from S0
<br> 2. I want to maintain all history for all the merges without losing any information.<br><br> FROM TIME TO TIME:<br> ------------------<br><br> Merge B1 to S0 using svk merge...<br> Merge B2 to S0 using svk merge...
<br><br> Resolve conflicts if any.<br> Release code from S0.<br><br>QUERIES:<br><br>1. I want to know if there is any problem in doing above using SVK?<br>2. I want to know if there is any way to do it using CVS or SVN if possible
<br>3. Can I use WinSVN or TortoiseSVN for SVK repositories [I am unable to conclude on this from the docs/forum discussions]???<br><br>Any help is greatly appreciated...<br><br>./tss<br><br><br> <br><hr>Powered by the worlds shortest email address ...
<a href="http://www.k.st" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.k.st</a></div><br>_______________________________________________<br>svk-devel mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:svk-devel@bestpractical.com">
svk-devel@bestpractical.com</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel" target="_blank">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel
</a><br><br></blockquote></div><br>