[svk-users] using svn to access local svk repo

[Andrew Sasak]

I think I have a similar use case to Faisal: I'd like to use
TortoiseSVN to interface with my svk repo which is a mirror of an svn
repo. Basically I want to pull from svk, create local (not pushed to
the svn repo) branches and commit to them, switch between branches,
etc all using TortoiseSVN. Then I want to be able to use svk to merge
from the branch to the trunk and push the changes to the SVN repo. I'm
new to SVK, but it sounds like my svk repo (depot) is what you call a
mirrored path and I shouldn't do this. It also sounds like the way to
do this is to have two different svk depots, the mirror, and then a
local, does this mean twice the required amount of storage?

On Jan 31, 2008 2:01 PM, Jesse Vincent <jesse at bestpractical.com> wrote:
>
>
>
> On Thu, Jan 31, 2008 at 01:54:09PM -0500, Faisal N Jawdat wrote:
> > Is it a bad idea to use svn to check out from a local svk repository?
> >
> > Scenario:
> >
> > I have an svn repository on, let's say, upstream.com.
> >
> > I have pulled that to //mirror/repository and copied that to //local/
> > repository, both stashed in ~/.svk/local.
> >
> > I have a bunch of tooling that plays well with svn, but doesn't work
> > with svk.  It's possible to 'svn ci' against the local repository (file:///Users/faisal/.svk/local/local/repository/trunk
> > , etc.), which gets the files, and checking back in makes files
> > accessible to svk for checkout, pushing upstream, etc.
>
> mirrored paths: checking out is ok. checking in or making changes will cause the world to end.
>
> local paths: checking out is ok. checking in is ok.
>
> merging: using svk rather than svn will do a better job tracking merge
> data.
>
> Best,
> Jesse
>
> _______________________________________________
> svk-users mailing list
> svk-users at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-users
>