RE: svk behaviour
From: Burgess, Glenn <Glenn.Burgess_at_dsto.defence.gov.au>
Date: 2004-02-19 06:51:44 CET
I should add that the SVK FAQ says this:
* Given an svk repository, do you have to use it via svk, or can you use svn programs to access it?
svk doesn't have its own repository format. when you use 'svk depotmap' you actually map svn repositories to names that svk could access. So yes, it is always accessible from svn programs. -- ChiaLiangKao
This possibly answers my question, but I would just like some reassurance from someone who has tried it (or who just knows) that 'always accessible' means it is good and proper (and safe) to do so.
What I mean is, if svk uses an svn repository but adds its own meta-data which it manipulates when you use the provided svk commands (commit, add, rm etc.) will it still work as intended if you use svn commands to commit, add etc. instead?
Thanks again,
-----Original Message-----
Has anyone out there got any experience using svk, if so can you tell me the circumstances under which it is safe to use the normal svn commands, and in particular frontends.
As I understand it svk allows svn repository replication by creating a local (read-only) mirror of a 'master' repo, then a local copy of that to use for stand-alone operation. Then you can merge changes back upstream, or downstream, or both ways at once (sync).
My hope is that you should be able to treat the two repositories (the master and the local copy of the mirrow) as stand-alone svn repositories until you want to sync the two repositories, at which point you simply use the svk commands to do that.
Is this true or is a svk repository different to a svn repository?
I am a newbie, it is true, but I have RT'd as many FMs as I could find. svk doesn't have a lot of docs yet.
If you know of a better place to post this please let me know.
Thanks,
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.