Using SVK and Subversion to manage distributed branches to Wine CVS

[Troy Rollo]

Over the past few weeks I have been experimenting with SVK and Subversion 
managing a handful of branches to Wine CVS, and it appears to be working 
well. The system is based on a "central" Subversion repository that mirrors 
the Wine CVS tree without any modifications (publicly readable at 
svn://wine-svn.troy.rollo.name/wine/wine/) and is kept up to date within a 
day or so.

Branches are stored in separate Subversion repositories.

I am finding this very convenient. If you have converted from CVS to 
Subversion on other projects, you are probably aware of the huge difference 
it makes. Adding SVK on top of Subversion is another giant leap when you have 
distributed development. In the case of Wine, however, with the CVS 
repository being read-only except to Alexandre, the difference between 
read-only CVS and the combination of Subversion and SVK is even more dramatic 
(I would compare it to the difference between chiselling documents into stone 
tablets and using a word processor).

For anybody who is interested in moving their own Wine development to 
Subversion and SVK, there is a page on the Wiki describing what to do at 
<http://wiki.winehq.com/SVK>

[Mike Hearn]

On Mon, 20 Jun 2005 11:44:11 +1000, Troy Rollo wrote:
> In the case of Wine, however, with
> the CVS repository being read-only except to Alexandre, the difference
> between read-only CVS and the combination of Subversion and SVK is even
> more dramatic (I would compare it to the difference between chiselling
> documents into stone tablets and using a word processor).

+1

Thanks for doing this Troy, I had intended to set up an SVK gateway months
ago and it never happened. It's great to see that I'm not crazy really ;)

thanks -mike