Re: [OT] Best Use of Subversion Branches in Perl Development

You might want to look at SVK, which, although you are not needing to use it offline, does take most of the pain out of maintaining your work in a branch; just use svk pull and svk push.

This can also be completely transparent to the rest of your developers, who are working directly with svn.

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

Comment on Re: [OT] Best Use of Subversion Branches in Perl Development

Replies are listed 'Best First'.
Re^2: [OT] Best Use of Subversion Branches in Perl Development by xdg (Monsignor) on Feb 02, 2007 at 23:16 UTC
I have to second this, as SVK takes care of a lot of merge tracking for you. It does requires some different thinking as it replicates a repository to your computer and then manages the synchronization from there. See the SVK Wiki for more details and some guides. In SVK, people seem to usually make a local branch on their computer rather than a branch in the repository and work there. It might work like this: Read more... (932 Bytes) I think you can also do this entirely on a remote branch, too, like this (though there are other ways): Read more... (1023 Bytes) -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l] [select]
Re^2: [OT] Best Use of Subversion Branches in Perl Development by adrianh (Chancellor) on Feb 03, 2007 at 22:01 UTC
This can also be completely transparent to the rest of your developers, who are working directly with svn. Indeed. Another vote for SVK here. It's become my default subversion "client" for some time and makes the private sandbox way of working very simple. Nice.	[reply]