Re: Dev - Request to Use a Distributed Version ControlSystem When Code Base Changes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Dev - Request to Use a Distributed Version ControlSystem When Code Base Changes

Jacques Le Roux
Administrator
Thanks Vinay this seems very interesting

Jacques

----- Original Message -----
From: "Vinay Agarwal" <[hidden email]>
To: "'OFBiz Project Development Discussion'" <[hidden email]>
Sent: Friday, March 24, 2006 10:46 PM
Subject: Re: [OFBiz] Dev - Request to Use a Distributed Version ControlSystem
When Code Base Changes


> Hello,
>
> I found out how to use SVK for creating local SVN repositories. (Adam thanks
> for the scripts but I didn't spend time on them). I think this method is
> easier than vendor branch. I created a Wiki page which is copied below.
>
> Regards,
> Vinay Agarwal
>
> Creating SVN Mirror Repository Using SVK
>
> This is an alternative to, and hopefully easier than, "vendor branch" method
> for source code management. This method takes a few minutes to complete
> updates and is fully automated except for conflicts. This description does
> not include trunk/branches for simplicity.
>
> 1. Install SVK.
> 2. Create a local SVN (or SVK) repository in your PC/LAN using regular svn
> command.
> 3. Tell SVK about this repository. SVK calls it depot.
>
>     svk depotmap
>
>     An editor will pop-up (which can be changed using $EDITOR environment
> variable). Edit it to point to your repository and save.
>
> 4. Create a mirror of http://svn.ofbiz.org/svn/ofbiz/trunk in your local
> PC/LAN. We will call it uplink.
>
>     svk mirror http://svn.ofbiz.org/svn/ofbiz/trunk //uplink
>
>     svk sync //uplink
>
>     sync operation takes about 3 hours on my system and must be restarted
> several times in order to complete.
>
>     DANGER: Make sure //uplink is never used with any SVN command or it will
> corrupt the mirror capability. You may make a backup of this by using
>
>     svk copy //uplink //uplinkbackup
>
> 5. Create a working repository for SVN users (it uses the same copy command)
>
>     svk copy //uplink //local
>
>     //local is now the SVN local repository.
>
> Usage
> 1. Checkout using SVN (not SVK) from //local
> 2. Make changes as usual
> 3. Use regular svn client commands (e.g. commit, update) for code management
> which now talk to //local repository
> 4. To download updates from OFBiz
>
>     svk sync //uplink
>
> 5. To merge changes to local repository
>
>     svk smerge //uplink //local
>
> 6. To update working copies, use svn update command.
>
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev