SVN and SVK
Dear Lazyweb:
I would like to take an existing SVN repository of a project (like say, Typo), check out a tagged version, create local modifications and save the modified version in a local/home SVN repository(my blog). Later, I'd like to sync up the local version to a new tagged version of the original repository (Typo), handle any merges locally and then check in the result into my local repository again. Rinse and repeat, ad infinitum.
Is SVK the right job for this? Has anybody done something like this? Essentially its the equivalent of creating a branch on a SVN repository but having that branch in an entirely separate SVN repository instance. I don't have experience with this, so I'd greatly appreciate any pointers anybody out there might have.
About this entry
You’re currently reading “SVN and SVK,” an entry on Late to the Party by Chris
- Published:
- 1pm on 02/16/07
- Categories:
- Programming, Personal
- Tags:
- development, programming, repository, scm, subversion, svk, svn
1. 'mirror' the source SVN to your SVK repository
2. Take a working copy of the tree
3. Create a 'mirror' of your production SVN
Make changes to your working copy and, when you want, run an 'smerge' to either of the mirrors. When you merge into the mirror, the remote SVN is updated too.
Now the problems: SVK can get confused. I got myself into places where the upload to the remote SVN would break, and I could never recover - SVN properties seemed to cause problems.
SVK doesn't do svn:externals. I worked with this by mirroring every plugin and Rails, and using SVK copy to put a particular version into my working copy.
I no longer use SVK. When it goes wrong, I could find no way to get back on track (other than start from scratch!)